Wary Puppy 5.1.1 Final

[MorganP]

I have installed an earlier Wary (504) into an ebox 3310 and installed the Wine pet 1.1.39. That works pretty well but there are some details that Wine is having a problem with for me.

I tried to install Wine 1.3.13 which did not report any problems during installation, but the wine menu items are not present and it does not run any Windows apps.
http://208.109.22.214/puppy/viewtopic.p ... a221be84c3

Are those later wine pets compatible with Wary 5? I did not update to Wary 5.1 and try again, but wasn't sure if I had to use a wine specifically built for Wary.

Thanks. I'm really happy with Wary 5 besides my wine problems..

[scsijon]

sorry but with the release build,
the radeon driver doesn't seem to work with my card (ATI HD4350-RV710) either by probe or select, the pre-release build and earlier (wary5.0) has autoselected and "worked out of the box". I shall download the alternate and see if it's just this build later.

regards
scsijon

UPDATE: no, uniprocessor version gives the same result, stuck with xvesa to use.

[Karl Godt]

Code: Select all

grep -n hci /etc/rc.d/rc.sysinit

if [ ! -d /initrd ];then #v423 full hd install.
#v423 have this in 'init', probably need here too...
if [ "`echo "$MODALIASES" | grep 'bc0Csc03i10'`" != "" ];then
modprobe --config /tmp/pup_event_modprobe.conf yenta-socket
[ $? -eq 0 ] && sleep 2
fi
#v423 k2.6.29.6 dmesg has warning that ehci-hcd should load before uhci-hcd and ohci-hid
# this is contrary to my understanding all these years, but oh well, let's do it...
ELSPCI="`elspci -l`" #jesses great little utility.
[ "`echo "$ELSPCI" | grep '0C0320'`" != "" ] && modprobe --config /tmp/pup_event_modprobe.conf ehci-hcd
#...perhaps a udev rule could have done this?

Code: Select all

[ "`echo "$ELSPCI" | grep '0C0310'`" != "" ] && modprobe --config /tmp/pup_event_modprobe.conf ohci-hcd
 [ "`echo "$ELSPCI" | grep '0C0300'`" != "" ] && modprobe --config /tmp/pup_event_modprobe.conf uhci-hcd

fi

I am not running wary but I think to probe for ohci and uhci may be a good idea for rc.sysinit and init@initrd.gz even if it seems a little late

-----------------------------------------------------------------------------------

DdShurick from russian Puppy team have created 3g-modem auto-detection package.

I am using pgprs-shell mostly but thought why not look inside :

#!/bin/sh
if [ -a /dev/ttyUSB2 ]; then #USB2 потому что USB0 и USB1 е

[shinobar]

It is great that the new snapmergepuppy works fast.
But I suppose it has some potential issues.

1. I wonder why we need to save the device nodes under /dev. They will be created after boot with udev architech.
   I am not sure it was the case, but my one laptop failed in sound at a time. It recovered by removing all /dev and reboot.
   I think most of them under /dev also need not in the main sfs.
2. No problem in wary, but serious for some puppy having pup_ro10-19.
3. It is better to give an exit code when saving failed. Of course the rc.shutdown needs to be modified to use it.

Here is my patch.

Code: Select all

25a26
> #110222 shinobar: remove all /dev, allow 'pup_ro10-19', exit code for no space
103,104c104,105
< #w003 /dev/.udev also needs to be screened out... 100820 added var/tmp
< find . -mount -type d | tail +2 | sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^root/tmp|^\.wh\.|/\.wh\.|^dev/\.|^dev/fd|^dev/pts|^dev/shm|^var/tmp' |
---
> #w003 /dev/.udev also needs to be screened out... 100820 added var/tmp #110222 shinobar: remove all /dev
> find . -mount -type d | tail +2 | sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^root/tmp|^\.wh\.|/\.wh\.|^dev/|^var/tmp' |
120,123c121,124
< FREEBASEK=`df -k | grep "$BASE" | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah
< 
< #Copy Files... v409 remove '^var'. w003 screen out some /dev files. 100222 shinobar: more exclusions. 100422 added ^root/ftpd. 100429 modify 'trash' exclusion. 100820 added var/tmp
< find . -mount -not \( -regex '.*/\.wh\.[^/]*' -type f \) -not -type d |  sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^pup_|^zdrv_|^root/tmp|_zdrv_|^dev/\.|^dev/fd|^dev/pts|^dev/shm|^\.wh\.|^var/run|^root/ftpd|^var/tmp' | grep -v -E -i '\.thumbnails|\.trash|trash/|\.part$'  |
---
> FREEBASEK=`df -k | grep -w "$BASE"| head -n 1 | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah #110222 shinobar
> rm -f /tmp/snapmergepuppy-nospace #110222 shinobar
> #Copy Files... v409 remove '^var'. w003 screen out some /dev files. 100222 shinobar: more exclusions. 100422 added ^root/ftpd. 100429 modify 'trash' exclusion. 100820 added var/tmp #110222 shinobar: remove all /dev
> find . -mount -not \( -regex '.*/\.wh\.[^/]*' -type f \) -not -type d |  sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^pup_|^zdrv_|^root/tmp|_zdrv_|^dev/|^\.wh\.|^var/run|^root/ftpd|^var/tmp' | grep -v -E -i '\.thumbnails|\.trash|trash/|\.part$'  |
142c143
<   FREEBASEK=`df -k | grep "$BASE" | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah: this is very slow; try not to check every iteration
---
>   FREEBASEK=`df -k | grep -w "$BASE" | head -n 1 | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah: this is very slow; try not to check every iteration #110222 shinobar: fix for pup_ro10 and more
149a151
>    touch /tmp/snapmergepuppy-nospace  #110222 shinobar
182a185
> [ -f /tmp/snapmergepuppy-nospace ] && exit 1 #110222 shinobar

[BarryK]

PPM cursor
Hi Barry

Puppy Package Manager when no package found

The cursor shows when over the desktop,
then disappears behind the main PPM window,
then shows again if you hit the
"Sorry, no matching package name" red dialog.

Ahhh! switching back to PPM from Seamonkey after copying the text in the red dialog without closing the dialog, the whole PPM window is blank. If I move it out of the way I can see the red dialog, click "okay" then PPM window displays.

Is it possible to have <return> trigger the "okay" as well as the mouse?

-Bill

Fixed, see:
http://bkhome.org/blog/?viewDetailed=02157

[BarryK]

Used Wary-510-k2.6.31.14-uniproc-ide.iso to make a CD-RW.
[The more up-to-date kernel wouldn't boot on my 2003 desktop PC]

FEATURE:
1. I notice that this Wary searches deeper than where the pupsave files are located [In case there might be more?]

BUG?
1. It lists TWO of everything it finds.
i.e. If there are 2 pupsave files; one on the HDD and one on a Flash Drive, it lists them as items 1 and 2, then lists them again as 3 and 4.

Fix:
http://bkhome.org/blog/?viewDetailed=02155

[BarryK]

It is great that the new snapmergepuppy works fast.
But I suppose it has some potential issues.

1. I wonder why we need to save the device nodes under /dev. They will be created after boot with udev architech.
   I am not sure it was the case, but my one laptop failed in sound at a time. It recovered by removing all /dev and reboot.
   I think most of them under /dev also need not in the main sfs.
2. No problem in wary, but serious for some puppy having pup_ro10-19.
3. It is better to give an exit code when saving failed. Of course the rc.shutdown needs to be modified to use it.

Here is my patch.

Code: Select all

25a26
> #110222 shinobar: remove all /dev, allow 'pup_ro10-19', exit code for no space
103,104c104,105
< #w003 /dev/.udev also needs to be screened out... 100820 added var/tmp
< find . -mount -type d | tail +2 | sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^root/tmp|^\.wh\.|/\.wh\.|^dev/\.|^dev/fd|^dev/pts|^dev/shm|^var/tmp' |
---
> #w003 /dev/.udev also needs to be screened out... 100820 added var/tmp #110222 shinobar: remove all /dev
> find . -mount -type d | tail +2 | sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^root/tmp|^\.wh\.|/\.wh\.|^dev/|^var/tmp' |
120,123c121,124
< FREEBASEK=`df -k | grep "$BASE" | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah
< 
< #Copy Files... v409 remove '^var'. w003 screen out some /dev files. 100222 shinobar: more exclusions. 100422 added ^root/ftpd. 100429 modify 'trash' exclusion. 100820 added var/tmp
< find . -mount -not \( -regex '.*/\.wh\.[^/]*' -type f \) -not -type d |  sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^pup_|^zdrv_|^root/tmp|_zdrv_|^dev/\.|^dev/fd|^dev/pts|^dev/shm|^\.wh\.|^var/run|^root/ftpd|^var/tmp' | grep -v -E -i '\.thumbnails|\.trash|trash/|\.part$'  |
---
> FREEBASEK=`df -k | grep -w "$BASE"| head -n 1 | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah #110222 shinobar
> rm -f /tmp/snapmergepuppy-nospace #110222 shinobar
> #Copy Files... v409 remove '^var'. w003 screen out some /dev files. 100222 shinobar: more exclusions. 100422 added ^root/ftpd. 100429 modify 'trash' exclusion. 100820 added var/tmp #110222 shinobar: remove all /dev
> find . -mount -not \( -regex '.*/\.wh\.[^/]*' -type f \) -not -type d |  sed -e 's/\.\///' | grep -v -E '^mnt|^initrd|^proc|^sys|^tmp|^pup_|^zdrv_|^root/tmp|_zdrv_|^dev/|^\.wh\.|^var/run|^root/ftpd|^var/tmp' | grep -v -E -i '\.thumbnails|\.trash|trash/|\.part$'  |
142c143
<   FREEBASEK=`df -k | grep "$BASE" | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah: this is very slow; try not to check every iteration
---
>   FREEBASEK=`df -k | grep -w "$BASE" | head -n 1 | tr -s ' ' | cut -f 4 -d ' '` #110212 Jemimah: this is very slow; try not to check every iteration #110222 shinobar: fix for pup_ro10 and more
149a151
>    touch /tmp/snapmergepuppy-nospace  #110222 shinobar
182a185
> [ -f /tmp/snapmergepuppy-nospace ] && exit 1 #110222 shinobar

Great stuff! Applied:
http://bkhome.org/blog/?viewDetailed=02156

[Shep]

I've been using Wary 104 with a few added packages plus Barry's zzz .pet to endow it with 3G modem capability. It operated nicely indeed on my veteran 560MHz PIII desktop. But I decided to try the upgrade, so burnt the CD for Wary 5.1, and rebooted. Horror!

Code: Select all

You will either have to uninstall the Puppy 2 packages or install missing dependencies

gtk+12 gtkxft gtk_pixbuf10 glib12
tk tcl tix uri tktable tablelist tile trf combobox gnocl img
qt 
imlib libx aw95_DEP4
speex libosp[2 cdr dao SOX
libidn fig2dev pstoedit mtools

I didn't even know I had any puppy 2 packages installed. Which were they?
And I think there was a further alert came up, but it disappeared while I was busy writing down that first list of things I'd have to fix.
Then when the desktop came up, it had no volume control. Music player pmusic did play, but at zero volume. And worst of all, my 3G modem was not recognized. I switched off, and went to the pub.

Next day when I switched it on, fearing what else could be awry, there were no messages about missing dependencies, and the volume control had returned. See, there are good elves like the shoemaker said!!

But still no go with the modem, so I ran the zzz_scripts_simple_bk-201011.pet which I'd kept a copy of, and now the modem was all go. I notice that after unplugging and reinserting the usb modem I no longer get the green overlay message saying "modem is now ready for use" or words to that effect. The main thing is that it does work. I found PPM listed zzz TWICE in the installed packages. I uninstalled one of them and they both uninstalled. So I reinstalled it, and again it's listed twice. No big deal.

The upshot: all seems well and good. I particularly like the new pmusic which can be accessed via an icon on the tray beside the volume control; it sure beats having to do to rxvt to kill the player. And now, each mouse click adds a music file to a playlist.

Wary 5.1 -- I like it!

[BongoPlayer]

Thanks Barry,

Even though I had to disconnect my noisy (failing) hard drives, I can still browse the net, do online banking, receive and send e-mail (Hotmail) with your Puppy Linux 4.3.1 and an 8GB USB Pen Drive.

With both versions of Wary 510 (k2.6.32.28 and k2.6.31.14-uniproc-ide), the browser (Seamonkey) crashes.

FROM: /errs.log

"(seamonkey-bin:2731): Gdk-WARNING **: XID collision, trouble ahead

(seamonkey-bin:2731): Gdk-WARNING **: XID collision, trouble ahead
/usr/lib/seamonkey/run-mozilla.sh: line 131: 2731 Killed "$prog" ${1+"$@"}"

FROM: /var/log/messages:

Feb 23 11:49:50 puppypc user.warn kernel: seamonkey-bin invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
Feb 23 11:49:50 puppypc user.warn kernel: Pid: 14359, comm: seamonkey-bin Tainted: P 2.6.32.28 #1
Feb 23 11:49:50 puppypc user.warn kernel: Call Trace:
Feb 23 11:49:50 puppypc user.warn kernel: [<c104c911>] ? oom_kill_process+0x59/0x1fa
Feb 23 11:49:50 puppypc user.warn kernel: [<c104ce77>] ? __out_of_memory+0xf4/0x107
Feb 23 11:49:50 puppypc user.warn kernel: [<c104cee4>] ? out_of_memory+0x5a/0x7c
Feb 23 11:49:50 puppypc user.warn kernel: [<c104f6d4>] ? __alloc_pages_nodemask+0x3e2/0x4a0
Feb 23 11:49:50 puppypc user.warn kernel: [<c105b285>] ? handle_mm_fault+0x1a1/0x550
Feb 23 11:49:50 puppypc user.warn kernel: [<c1045f93>] ? handle_IRQ_event+0x1a/0x95
Feb 23 11:49:50 puppypc user.warn kernel: [<c1016dc9>] ? do_page_fault+0x1db/0x1ea
Feb 23 11:49:50 puppypc user.warn kernel: [<c1016bee>] ? do_page_fault+0x0/0x1ea
Feb 23 11:49:50 puppypc user.warn kernel: [<c1289546>] ? error_code+0x66/0x70
Feb 23 11:49:50 puppypc user.warn kernel: [<c1016bee>] ? do_page_fault+0x0/0x1ea
Feb 23 11:49:50 puppypc user.info kernel: Mem-Info:
Feb 23 11:49:50 puppypc user.warn kernel: DMA per-cpu:

jp

[MorganP]

I have installed an earlier Wary (504) into an ebox 3310 and installed the Wine pet 1.1.39. That works pretty well but there are some details that Wine is having a problem with for me.

I tried to install Wine 1.3.13 which did not report any problems during installation, but the wine menu items are not present and it does not run any Windows apps.
http://208.109.22.214/puppy/viewtopic.p ... a221be84c3

Are those later wine pets compatible with Wary 5? I did not update to Wary 5.1 and try again, but wasn't sure if I had to use a wine specifically built for Wary.

I went ahead and loaded 5.1. No problems in general except the dual save-file issue. I tried to install Wine 1.3.13 into this version but as I assumed, it did not work. After installation I get the message that the menus are being updated at the end of installation but no Wine menus were present. I did find wine bin files where expected.

Am I limited to installing Wine 1.1.39?

[BarryK]

I've been using Wary 104 with a few added packages plus Barry's zzz .pet to endow it with 3G modem capability. It operated nicely indeed on my veteran 560MHz PIII desktop. But I decided to try the upgrade, so burnt the CD for Wary 5.1, and rebooted. Horror!

Code: Select all

You will either have to uninstall the Puppy 2 packages or install missing dependencies

gtk+12 gtkxft gtk_pixbuf10 glib12
tk tcl tix uri tktable tablelist tile trf combobox gnocl img
qt 
imlib libx aw95_DEP4
speex libosp[2 cdr dao SOX
libidn fig2dev pstoedit mtools

I didn't even know I had any puppy 2 packages installed. Which were they?
And I think there was a further alert came up, but it disappeared while I was busy writing down that first list of things I'd have to fix.
Then when the desktop came up, it had no volume control. Music player pmusic did play, but at zero volume. And worst of all, my 3G modem was not recognized. I switched off, and went to the pub.

Next day when I switched it on, fearing what else could be awry, there were no messages about missing dependencies, and the volume control had returned. See, there are good elves like the shoemaker said!!

But still no go with the modem, so I ran the zzz_scripts_simple_bk-201011.pet which I'd kept a copy of, and now the modem was all go. I notice that after unplugging and reinserting the usb modem I no longer get the green overlay message saying "modem is now ready for use" or words to that effect. The main thing is that it does work. I found PPM listed zzz TWICE in the installed packages. I uninstalled one of them and they both uninstalled. So I reinstalled it, and again it's listed twice. No big deal.

The upshot: all seems well and good. I particularly like the new pmusic which can be accessed via an icon on the tray beside the volume control; it sure beats having to do to rxvt to kill the player. And now, each mouse click adds a music file to a playlist.

Wary 5.1 -- I like it!

Thanks for the feedback. Wary 5.1 already has the 'zzz' package installed. What was missing was the 'jimtcl' package that 'zzz' needs, as reported in an above post.

Hmmm, the upgrade is still not working properly. It looks like the old /etc/rc.d/rc.update script is running instead of the new one (I don't know why). You can ignore all those messages.
Anyway, the next time that you upgrade it should be ok.

[BarryK]

Thanks Barry,

Even though I had to disconnect my noisy (failing) hard drives, I can still browse the net, do online banking, receive and send e-mail (Hotmail) with your Puppy Linux 4.3.1 and an 8GB USB Pen Drive.

With both versions of Wary 510 (k2.6.32.28 and k2.6.31.14-uniproc-ide), the browser (Seamonkey) crashes.

FROM: /errs.log

"(seamonkey-bin:2731): Gdk-WARNING **: XID collision, trouble ahead

(seamonkey-bin:2731): Gdk-WARNING **: XID collision, trouble ahead
/usr/lib/seamonkey/run-mozilla.sh: line 131: 2731 Killed "$prog" ${1+"$@"}"

FROM: /var/log/messages:

Feb 23 11:49:50 puppypc user.warn kernel: seamonkey-bin invoked oom-killer: gfp_mask=0x280da, order=0, oom_adj=0
Feb 23 11:49:50 puppypc user.warn kernel: Pid: 14359, comm: seamonkey-bin Tainted: P 2.6.32.28 #1
Feb 23 11:49:50 puppypc user.warn kernel: Call Trace:
Feb 23 11:49:50 puppypc user.warn kernel: [<c104c911>] ? oom_kill_process+0x59/0x1fa
Feb 23 11:49:50 puppypc user.warn kernel: [<c104ce77>] ? __out_of_memory+0xf4/0x107
Feb 23 11:49:50 puppypc user.warn kernel: [<c104cee4>] ? out_of_memory+0x5a/0x7c
Feb 23 11:49:50 puppypc user.warn kernel: [<c104f6d4>] ? __alloc_pages_nodemask+0x3e2/0x4a0
Feb 23 11:49:50 puppypc user.warn kernel: [<c105b285>] ? handle_mm_fault+0x1a1/0x550
Feb 23 11:49:50 puppypc user.warn kernel: [<c1045f93>] ? handle_IRQ_event+0x1a/0x95
Feb 23 11:49:50 puppypc user.warn kernel: [<c1016dc9>] ? do_page_fault+0x1db/0x1ea
Feb 23 11:49:50 puppypc user.warn kernel: [<c1016bee>] ? do_page_fault+0x0/0x1ea
Feb 23 11:49:50 puppypc user.warn kernel: [<c1289546>] ? error_code+0x66/0x70
Feb 23 11:49:50 puppypc user.warn kernel: [<c1016bee>] ? do_page_fault+0x0/0x1ea
Feb 23 11:49:50 puppypc user.info kernel: Mem-Info:
Feb 23 11:49:50 puppypc user.warn kernel: DMA per-cpu:

jp

I have no idea why that is happening, but I have a suggestion. Click on the 'setup' icon on the desktop and choose 'Upgrade X drivers' then install the Xorg 7.5 upgrade PET. It will be interesting to find out if that makes any difference.

[rodin.s]

I guess ffmpeg compiled for i686. http://bkhome.org/blog/?viewDetailed=02064 so pmusic doesn't work on i586. I put mplayer binary from PuppyRus Jeans to my-applications/bin and use it for music and internet radio.

[Doglover]

Nice job Barry, but my wireless network settings are not saved when rebooting or shutdown. I'm using the standard Network Wizard. Everything else works great.

[ravensrest]

Upgraded from 5.0 to 5.1 by just moving vmlinuz, initrd and wary_510 to my Wary 5.0 partition. All seems OK except I am under the distinct impression that Seamonkey 2.0.xx in Wary 5.1 and Wary 5.0 are slower and more uncertain of operation than version 1.1.18 in Puppy 431. The apparent degradation re the earlier version seems to be url dependent. It is difficult to obtain hard numbers as I generally don't know how fast my DSL channel is at any particular time, but I have switched back and forth between the two systems many times now and definitely feel Puppy431/Seamonkey 1.1.18 is preferable.

Anyone else notice this?

BS

[James C]

Did a fresh manual frugal install of Wary 5.11 on my main Linux box. Everything working on initial boot(sound,internet and display) and no problems yet.

[gcmartin]

I downloaded to test this version and found several items to note.

1. The XVesa video support seems to be broken as

• drag and drop doesnt work properly
• middle mouse button doesn't do what I had expected in pasting from one window to another

2. When I tried to run glxgears from a terminal window I get the followiing messages:

Code: Select all

#glxgears
Xlib: extension "GLX" missing on display ":0.0".
Error: couldn't get an RGB, Double-buffered visualXlib

It appears that to run LiveCD, I cannot go to XVesa for full desktop use. Further in order to run glxgears, I MUST Probe for a video before I can use glxgears., then I can go to XVesa to run glxgears. BUT, the other items I report still remain.

Lastly the PPM drivers for this intel card does not reflect that one is dependent upon the other. Each driver is s minor order improvement when I move from Pristine to each of the listed drivers on LiveCD.

What was surprising is that the XVesa was a order above the Intel dirvers in the PPMs. I didn't expect to see this.

I wonder how many other users have run glxgears with and without Xvesa and have seen a surprisingly faster video report?

Code: Select all

-Computer-
Processor		: 2x Genuine Intel(R) CPU           T2080  @ 1.73GHz
Memory		: 1545MB (280MB used)
Operating System		: Puppy Linux 0.51
User Name		: root (root)
Date/Time		: Fri 25 Feb 2011 01:30:05 AM UTC
-Display-
Resolution		: 1440x900 pixels
OpenGL Renderer		: Mesa GLX Indirect
X11 Vendor		: The X.Org Foundation
-Multimedia-
Audio Adapter		: HDA-Intel - HDA Intel
-Input Devices-
 AT Translated Set 2 keyboard
 SynPS/2 Synaptics TouchPad
 CHICONY HP Basic USB Keyboard
 Power Button
 Sleep Button
 Lid Switch
 Power Button
 Video Bus
 PC Speaker
-Printers (CUPS)-
CUPS-PDF		: <i>Default</i>
-SCSI Disks-
Optiarc DVD RW AD-7560A
USB 2.0 USB Flash Drive
-Computer-
Processor		: 2x Genuine Intel(R) CPU           T2080  @ 1.73GHz
Memory		: 1545MB (280MB used)
Operating System		: Puppy Linux 0.51
User Name		: root (root)
Date/Time		: Fri 25 Feb 2011 01:30:05 AM UTC
-Display-
Resolution		: 1440x900 pixels
OpenGL Renderer		: Mesa GLX Indirect
X11 Vendor		: The X.Org Foundation
-Multimedia-
Audio Adapter		: HDA-Intel - HDA Intel
-Input Devices-
 AT Translated Set 2 keyboard
 SynPS/2 Synaptics TouchPad
 CHICONY HP Basic USB Keyboard
 Power Button
 Sleep Button
 Lid Switch
 Power Button
 Video Bus
 PC Speaker
-Printers (CUPS)-
CUPS-PDF		: <i>Default</i>
-SCSI Disks-
Optiarc DVD RW AD-7560A
USB 2.0 USB Flash Drive

This si a laptop.

Hope this helps.

[sansinspiration]

machine: hp pavilion 7927.

while trying wary 5.1.1, the keyboard (ps/2) disconnects at the beginning of the boot-up process; further input is impossible.

(on the same computer puppy 4.3.1 works fine).

[FeodorF]

Dear Barry,

I experienced the same problem as rodin.s - Seamonkey crashes.

I followed your advice about upgrading the display driver to Xorg 7.5 .

I worked with SM after the upgrade for hours - success! No more problems.

MoBo is a SiS 740/962 with 1GB(RAM), 128KB(VGA).

Cheers, FeodorF

[BongoPlayer]

Hi Barry,

I'll be sticking with Puppy Linux 4.3.1 for now.

At least until I can upgrade my hardware.

Thanks for your response earlier on.

jp