Upup Raring 3.9.9.2 with non-PAE 3.9.9 kernel. 13 July 2013
While I'm digging out old hardware...... an even older Nvidia card.
Raring 3.9.9.2 live....... working well.
-Computer-
Processor : AMD Athlon(tm) Processor
Memory : 253MB (130MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Mon 26 Aug 2013 05:12:10 PM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI nv05 x86/MMX+/3DNow!+
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : VIA686A - VIA 82C686A/B rev20
-Processor-
Name : AMD Athlon(tm) Processor
Family, model, stepping : 6, 4, 2 (AMD Athlon (Thunderbird))
Vendor : AuthenticAMD
-Configuration-
Cache Size : 256kb
Frequency : 851.49MHz
BogoMIPS : 1703.94
Byte Order : Little Endian
Raring 3.9.9.2 live....... working well.
Code: Select all
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: NVIDIA Corporation NV5 [Riva TNT2 / TNT2 Pro] (rev 15)
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): nouveau
Loaded modules: dbe dri exa extmod fb fbdevhw 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.
674 frames in 5.0 seconds = 134.797 FPS
784 frames in 5.0 seconds = 156.784 FPS
808 frames in 5.0 seconds = 161.492 FPS
796 frames in 5.0 seconds = 159.071 FPS
803 frames in 5.0 seconds = 160.581 FPS
Processor : AMD Athlon(tm) Processor
Memory : 253MB (130MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Mon 26 Aug 2013 05:12:10 PM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI nv05 x86/MMX+/3DNow!+
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : VIA686A - VIA 82C686A/B rev20
-Processor-
Name : AMD Athlon(tm) Processor
Family, model, stepping : 6, 4, 2 (AMD Athlon (Thunderbird))
Vendor : AuthenticAMD
-Configuration-
Cache Size : 256kb
Frequency : 851.49MHz
BogoMIPS : 1703.94
Byte Order : Little Endian
Code: Select all
# free
total used free shared buffers
Mem: 253840 243148 10692 0 17584
-/+ buffers: 225564 28276
Swap: 1076316 752 1075564
#
Take a Shot (TAS) has been upgraded to 1.3
http://www.murga-linux.com/puppy/viewtopic.php?t=84528
Bulldog finder has been upgraded to 3.4
http://www.murga-linux.com/puppy/viewtopic.php?t=78592
____________________________________________
http://www.murga-linux.com/puppy/viewtopic.php?t=84528
Bulldog finder has been upgraded to 3.4
http://www.murga-linux.com/puppy/viewtopic.php?t=78592
____________________________________________
LFS - that's where I learned about xorg protocol headers
I have already upgraded a lot of x related stuff following their instructions. Now I want to start over from scratch - latest x-server first and compile stuff against it.
Thank you once again.
edit: "from scratch" does not mean I'm rebuilding everything. That will be a long term goal.
For the time being, I'm only recompiling stuff related to x and some other items.
.
.
I have already upgraded a lot of x related stuff following their instructions. Now I want to start over from scratch - latest x-server first and compile stuff against it.
Thank you once again.
edit: "from scratch" does not mean I'm rebuilding everything. That will be a long term goal.
For the time being, I'm only recompiling stuff related to x and some other items.
.
.
Last edited by anikin on Wed 28 Aug 2013, 15:28, edited 1 time in total.
Raring 3.9.9.2 live pfix=ram on another old backup box......
All good on boot, needed to use SNS to connect to internet.Everything appears to be working fine.
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
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): intel
Loaded modules: dbe dri2 extmod fb fbdevhw glx kbd mouse
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.236 FPS
376 frames in 5.0 seconds = 75.127 FPS
376 frames in 5.0 seconds = 75.148 FPS
376 frames in 5.0 seconds = 75.143 FPS
376 frames in 5.0 seconds = 74.988 FPS
377 frames in 5.0 seconds = 75.316 FPS
-Computer-
Processor : 2x Intel(R) Pentium(R) 4 CPU 3.00GHz
Memory : 1000MB (186MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Wed 28 Aug 2013 12:32:24 AM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI Intel(R) 865G x86/MMX/SSE2
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ICH4 - Intel ICH5
Multimedia audio controller : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
Ethernet controller : Intel Corporation 82541EI Gigabit Ethernet Controller
All good on boot, needed to use SNS to connect to internet.Everything appears to be working fine.
# report-video
VIDEO REPORT: Upup Raring, version 3.9.9.2
Chip description:
VGA compatible controller: Intel Corporation 82865G Integrated Graphics Controller (rev 02)
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): intel
Loaded modules: dbe dri2 extmod fb fbdevhw glx kbd mouse
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.236 FPS
376 frames in 5.0 seconds = 75.127 FPS
376 frames in 5.0 seconds = 75.148 FPS
376 frames in 5.0 seconds = 75.143 FPS
376 frames in 5.0 seconds = 74.988 FPS
377 frames in 5.0 seconds = 75.316 FPS
-Computer-
Processor : 2x Intel(R) Pentium(R) 4 CPU 3.00GHz
Memory : 1000MB (186MB used)
Machine Type : Physical machine
Operating System : Upup Raring - 3.9.9.2
User Name : root (root)
Date/Time : Wed 28 Aug 2013 12:32:24 AM CDT
-Display-
Resolution : 1024x768 pixels
OpenGL Renderer : Mesa DRI Intel(R) 865G x86/MMX/SSE2
X11 Vendor : The X.Org Foundation
-Audio Devices-
Audio Adapter : ICH4 - Intel ICH5
Multimedia audio controller : Intel Corporation 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02)
Ethernet controller : Intel Corporation 82541EI Gigabit Ethernet Controller
Code: Select all
# free
total used free shared buffers
Mem: 1000460 651440 349020 0 67468
-/+ buffers: 583972 416488
Swap: 2150396 0 2150396
#
What follows isn't Raring 3.9.9.2 specific but merely some comments from a total
noob when it comes to installing a printer on any pup. I purchased a Hp Deskjet
1000 and decided to get my feet wet installing it on 3992. The situation didn't look
promising and I went down some useless roads. What saved the day is the very
useful info (and pet) supplied by rcrsn51 here:
http://www.murga-linux.com/puppy/viewtopic.php?t=59015
I first run the hplip_print-3.13.7.pet and then aim a browser at localhost:631
and select "Adding Printers and Classes" ... then just follow through until the final
"Add Printer".
After using the printer on 3992 I went ahead and installed the printer on eight more
pups I have frugally installed on my main test PC without a hitch.
Hope some other first-time printer user on Puppys finds this info useful.
Art
noob when it comes to installing a printer on any pup. I purchased a Hp Deskjet
1000 and decided to get my feet wet installing it on 3992. The situation didn't look
promising and I went down some useless roads. What saved the day is the very
useful info (and pet) supplied by rcrsn51 here:
http://www.murga-linux.com/puppy/viewtopic.php?t=59015
I first run the hplip_print-3.13.7.pet and then aim a browser at localhost:631
and select "Adding Printers and Classes" ... then just follow through until the final
"Add Printer".
After using the printer on 3992 I went ahead and installed the printer on eight more
pups I have frugally installed on my main test PC without a hitch.
Hope some other first-time printer user on Puppys finds this info useful.
Art
- 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)