Upup Raring 3.9.9.2 with non-PAE 3.9.9 kernel. 13 July 2013
- charlie6
- Posts: 1230
- Joined: Mon 30 Jun 2008, 04:03
- Location: Saint-Gérard / Walloon part of Belgium
Hi James,
and also to happy Brookdale owners/users
thanks for your post !
Here are some workarounds:
http://murga-linux.com/puppy/viewtopic. ... 4&start=63
http://murga-linux.com/puppy/viewtopic. ... &start=133
This last is the best for me in raring-3.9.9.X, as it allows to use the intel driver, and also might even work in other late puppies.
[*][/b] «properly»[/u]: for what i need, and imho, a test to check if mesa runs OK is to load the gCAD3D-2.00.pet given along the post at the second link above, and to check how fast the displayed house moves according to mouse motions (just keep Ctrl-key pressed and move the mouse cursor on the house) : if slow or even very slow, then «no success».
Hope this helps
Charlie
ps: modesetting's xorgwizard setting (reported on page22) does not «pass» the above check test ... as it uses the vesa driver
and also to happy Brookdale owners/users
thanks for your post !
Here living with that ...goooood oooold Brook→:twisted: ... and have digged ... to get mesa properly [*][/b][/u] running on it:James C wrote:Good old Brookdale.
Booted to a black screen with a few icons.Ctrl/Alt/Bksp to xorgwizard....chose "modesetting" driver.....got correct screen resolution and correct working desktop...etc...
Here are some workarounds:
http://murga-linux.com/puppy/viewtopic. ... 4&start=63
http://murga-linux.com/puppy/viewtopic. ... &start=133
This last is the best for me in raring-3.9.9.X, as it allows to use the intel driver, and also might even work in other late puppies.
[*][/b] «properly»[/u]: for what i need, and imho, a test to check if mesa runs OK is to load the gCAD3D-2.00.pet given along the post at the second link above, and to check how fast the displayed house moves according to mouse motions (just keep Ctrl-key pressed and move the mouse cursor on the house) : if slow or even very slow, then «no success».
Hope this helps
Charlie
ps: modesetting's xorgwizard setting (reported on page22) does not «pass» the above check test ... as it uses the vesa driver
The interest in Intel Brookdale video driver led me to make a download available of
the driver that works for me with pemasu's 3992. It's the driver that I copied from
Barry's recent Raring pup. The driver name is intel_drv.so and it's location is
/usr/lib/xorg/modules/drivers
The file length is 1296092 bytes
http://home.epix.net/~artnpeg/
Art
the driver that works for me with pemasu's 3992. It's the driver that I copied from
Barry's recent Raring pup. The driver name is intel_drv.so and it's location is
/usr/lib/xorg/modules/drivers
The file length is 1296092 bytes
http://home.epix.net/~artnpeg/
Art
Back again with Raring on another semi-old Nvidia box. Everything working and correct on initial boot.
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Drivers requested to be loaded: nouveau
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri exa extmod fb glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
377 frames in 5.0 seconds = 75.206 FPS
376 frames in 5.0 seconds = 75.032 FPS
376 frames in 5.0 seconds = 75.024 FPS
376 frames in 5.0 seconds = 75.028 FPS
376 frames in 5.0 seconds = 75.039 FPS
-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Memory : 903MB (196MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Thu 29 Aug 2013 11:13:44 PM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on NV67
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: NVIDIA Corporation C68 [GeForce 7050 PV / nForce 630a] (rev a2)
Requested by /etc/X11/xorg.conf:
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Drivers requested to be loaded: nouveau
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri exa extmod fb glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
377 frames in 5.0 seconds = 75.206 FPS
376 frames in 5.0 seconds = 75.032 FPS
376 frames in 5.0 seconds = 75.024 FPS
376 frames in 5.0 seconds = 75.028 FPS
376 frames in 5.0 seconds = 75.039 FPS
-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
Memory : 903MB (196MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Thu 29 Aug 2013 11:13:44 PM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on NV67
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia
Code: Select all
# free
total used free shared buffers
Mem: 903020 649724 253296 0 73060
-/+ buffers: 576664 326356
Swap: 0 0 0
#
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series]
Display controller: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series] (Secondary)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): ati
Loaded modules: dbe dri2 exa extmod fb fbdevhw glx kbd mouse radeon ramdac
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
326 frames in 5.0 seconds = 65.138 FPS
376 frames in 5.0 seconds = 75.029 FPS
376 frames in 5.0 seconds = 75.030 FPS
376 frames in 5.0 seconds = 75.026 FPS
376 frames in 5.0 seconds = 75.032 FPS
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3400+
Memory : 967MB (205MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Fri 30 Aug 2013 01:29:06 AM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on ATI RS480
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ATIIXP - ATI IXP
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series]
Display controller: Advanced Micro Devices [AMD] nee ATI RS480 [Radeon Xpress 200 Series] (Secondary)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): ati
Loaded modules: dbe dri2 exa extmod fb fbdevhw glx kbd mouse radeon ramdac
Actual rendering on monitor:
Resolution: 1024x768 pixels (270x203 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
Running synchronized to the vertical refresh. The framerate should be
approximately the same as the monitor refresh rate.
326 frames in 5.0 seconds = 65.138 FPS
376 frames in 5.0 seconds = 75.029 FPS
376 frames in 5.0 seconds = 75.030 FPS
376 frames in 5.0 seconds = 75.026 FPS
376 frames in 5.0 seconds = 75.032 FPS
-Computer-
Processor : AMD Athlon(tm) 64 Processor 3400+
Memory : 967MB (205MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Fri 30 Aug 2013 01:29:06 AM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Gallium 0.4 on ATI RS480
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ATIIXP - ATI IXP
Code: Select all
# free
total used free shared buffers
Mem: 967548 649216 318332 0 73620
-/+ buffers: 575596 391952
Swap: 0 0 0
#
Two questions to do with the default version of jwm:
1) How do I tell which version of jwm is installed?
2) It seems that this version of jwm does not allow windows to maximise or open up any bigger than the actual desktop size (which might seem practical, but is different to what I have experienced on other puppies). This is problematic on my netbook because some large dialog windows are taller than my 1024x600 screen, and have to be manually dragged upwards and the manually resized by grabbing the bottom right corner then dragged up again before i can see the buttons at the bottom of the dialog window.
Is this behaviour able to be changed by some setting within jwm?
On other puppies the window manager seems to allow the same dialogs to open up (or be maximised to...) full window height (even if that is bigger than desktop size) and all i need to do is to drag the window upwards and I can see the buttons without resizing.
The pic shows an example of a dialog window that becomes truncated and distorted by being forced to fit between the top of the screen and the jwm tray (I could set the tray to auto hide and that does give some benefit, but still does not allow the window to be any bigger than the bottom of the screen). I really want to allow the dialogs to default to their normal native size.
1) How do I tell which version of jwm is installed?
2) It seems that this version of jwm does not allow windows to maximise or open up any bigger than the actual desktop size (which might seem practical, but is different to what I have experienced on other puppies). This is problematic on my netbook because some large dialog windows are taller than my 1024x600 screen, and have to be manually dragged upwards and the manually resized by grabbing the bottom right corner then dragged up again before i can see the buttons at the bottom of the dialog window.
Is this behaviour able to be changed by some setting within jwm?
On other puppies the window manager seems to allow the same dialogs to open up (or be maximised to...) full window height (even if that is bigger than desktop size) and all i need to do is to drag the window upwards and I can see the buttons without resizing.
The pic shows an example of a dialog window that becomes truncated and distorted by being forced to fit between the top of the screen and the jwm tray (I could set the tray to auto hide and that does give some benefit, but still does not allow the window to be any bigger than the bottom of the screen). I really want to allow the dialogs to default to their normal native size.
- Attachments
-
- jwm maxout.jpg
- (76.69 KiB) Downloaded 973 times
Greengeek wrote:
> The pic shows an example of a dialog window that becomes truncated and distorted by being forced to fit between the top of the screen
Yeah the GTK dialog does that. That's why I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.
Or the GTK programmer should have calculated the Height and Width of the window as a proportion : (H-50)x(w-50) or something like that, instead of a predefined HxW. The H and W of a screen can be extracted as variables from /etc/xorg.conf and then processed with the expr utility. It's a little work, but it's not hard to do.
BFN.
musher0
> The pic shows an example of a dialog window that becomes truncated and distorted by being forced to fit between the top of the screen
Yeah the GTK dialog does that. That's why I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.
Or the GTK programmer should have calculated the Height and Width of the window as a proportion : (H-50)x(w-50) or something like that, instead of a predefined HxW. The H and W of a screen can be extracted as variables from /etc/xorg.conf and then processed with the expr utility. It's a little work, but it's not hard to do.
BFN.
musher0
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Fresh manual frugal install and all is well.
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768x16
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri exa extmod fb fbdevhw glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1440x900 pixels (380x238 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
1156 frames in 5.0 seconds = 231.026 FPS
1342 frames in 5.0 seconds = 268.347 FPS
1354 frames in 5.0 seconds = 270.615 FPS
1330 frames in 5.0 seconds = 265.875 FPS
1355 frames in 5.0 seconds = 270.978 FPS
-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory : 3373MB (220MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Sat 31 Aug 2013 02:17:09 AM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 3.2, 128 bits)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia
EDIT:
Added screenshot.
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2)
Requested by /etc/X11/xorg.conf:
Resolution (widthxheight, in pixels): 1024x768x16
Depth (bits, or planes): 24
Modules requested to be loaded: dbe
Probing Xorg startup log file (/var/log/Xorg.0.log):
Driver loaded (and currently in use): nouveau
Loaded modules: dbe dri exa extmod fb fbdevhw glx kbd mouse shadowfb
Actual rendering on monitor:
Resolution: 1440x900 pixels (380x238 millimeters)
Depth: 24 planes
...the above also recorded in /tmp/report-video
# glxgears
1156 frames in 5.0 seconds = 231.026 FPS
1342 frames in 5.0 seconds = 268.347 FPS
1354 frames in 5.0 seconds = 270.615 FPS
1330 frames in 5.0 seconds = 265.875 FPS
1355 frames in 5.0 seconds = 270.978 FPS
-Computer-
Processor : 2x AMD Athlon(tm) 64 X2 Dual Core Processor 5200+
Memory : 3373MB (220MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Sat 31 Aug 2013 02:17:09 AM CDT
-Display-
Resolution : 1440x900 pixels
OpenGL Renderer : Gallium 0.4 on llvmpipe (LLVM 3.2, 128 bits)
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : HDA-Intel - HDA NVidia
Code: Select all
# free
total used free shared buffers
Mem: 3373852 683624 2690228 0 74216
-/+ buffers: 609408 2764444
Swap: 6211580 0 6211580
#
Added screenshot.
- Attachments
-
- Raring 3.9.9.2.jpg
- (37.13 KiB) Downloaded 799 times
Last edited by James C on Sat 31 Aug 2013, 07:25, edited 1 time in total.
Thanks Jasper. That command shows that UpupRaring3992 has jwm 835 so I decided to "borrow" a jwm from a different puppy and it has solved my problem.Jasper wrote:jwm -h when typed in your terminal will show your JWM version.
If you visit Joe's Change Log I vaguely recall v 851 (or other recent change) refers to your second item.
I wasn't sure of the proper way to do this, but I just grabbed the /usr/bin/jwm file from a Puppy MagooV6 install (seems to be jwm version 574) and copied it into UpupRaring instead of the default file. (It sounds like a major step backwards to go from 835 to 574, but I can't figure out the changelog info to decide which versions are the best so I'm just happy that it has cured my problem anyway).
Here is jwm binary version 855.
The pet installs just /usr/bin/jwm binary.
To test with small resolution problems.
The pet installs just /usr/bin/jwm binary.
To test with small resolution problems.
- Attachments
-
- jwm-binary-855.pet
- (83.87 KiB) Downloaded 277 times
-
- Posts: 68
- Joined: Sun 22 Feb 2009, 10:00
less
http://linux.die.net/man/1/lessgreengeek wrote:What is "less"?musher0 wrote:...
I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.
Thanks Pemasu. I tried the 855 pet but it has not changed the symptom unfortunately. It seems like Joe Wing has been making some changes to jwm to make various oversized dialog windows fit into the smaller resolution but I think it just makes some of the window layouts become distorted. The recent changes seem to have been good for Abiword dialogs though - they do seem to fit better.pemasu wrote:Here is jwm binary version 855.
To test with small resolution problems.
I will stick with 574 for now, even though this older version does allow some of the Abiword dialogs to be offscreen and oversized, but will try to find some other jwm versions aswell and see if I can hit on one that is best overall.
In my particular modified 3992 puplet (switchpup) it is easier for me to "drag" an oversized window than to go through the extra steps required by the smaller yet distorted window.
Comparison of 574 and 855 below:
- Attachments
-
- jwm855_still_have_problem.jpg
- (76.08 KiB) Downloaded 732 times
-
- jwm574_window_ok.jpg
- (80.06 KiB) Downloaded 713 times
Greengeek. Joe Wing reads his mail. You could post to him your expriments with problem report. For example by pointing to your posts.
Just right click the Posted icon and copy the url link.
http://joewing.net/projects/jwm/
joewing@joewing.net
http://murga-linux.com/puppy/viewtopic. ... 045#723045
People with those small resolution netbooks etc are best to test the changes in different jwm versions. I dont have small size laptops. Only 15.6 ".
Just right click the Posted icon and copy the url link.
http://joewing.net/projects/jwm/
joewing@joewing.net
http://murga-linux.com/puppy/viewtopic. ... 045#723045
People with those small resolution netbooks etc are best to test the changes in different jwm versions. I dont have small size laptops. Only 15.6 ".
Re: less
Thanks for the reference, cinclus_cinclus.cinclus_cinclus wrote:http://linux.die.net/man/1/lessgreengeek wrote:What is "less"?musher0 wrote:...
I prefer to have messages go through less: less has nothing to distort, it just displays the text it is given.
@greengeek:
You'll find the latest version of less at http://www.greenwoodsoftware.com/less/.
Less is a console text reader, like cat or more. But much more powerful. For ex.,
- it can also be used as a launcher.
Or you can ask it to highlight some text.
You can have it display a footer if you need to.
You can display the text it carries in a regular X-window through a command such asYou can then trigger that reader script with a right-click on a lot of document and text files.Code: Select all
urxvt [some urxvt parameters] -e less [some less paramaters] text.txt
It can read some executable codes, at least the text part, which most text editors can't do.
You can hook it up to an editor to help you review your editing / writing as you go.
It also has a couple of plugins that allow you to read html, doc or rtf files, or the contents of an archive.
From what I know of yad, it's a X-dialog kind of program. It shows user options and command buttons in a graphic environment.
Less is completely different. It's a console app, but it's very adaptable and very rich in features.
BFN.
musher0
- Attachments
-
- less-example.jpg
- (32.46 KiB) Downloaded 684 times
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
a few backgrounds.
- Attachments
-
- upupjy29,1a.jpg
- http://www.mediafire.com/?x4v77bi1p58ox
- (14.97 KiB) Downloaded 590 times
-
- upupjy29,1.jpg
- http://www.mediafire.com/?x4v77bi1p58ox
- (11.66 KiB) Downloaded 568 times
-
- upupau3.jpg
- http://www.mediafire.com/?x4v77bi1p58ox
- (8.95 KiB) Downloaded 581 times