Puppy 3.00beta2 bug reports here
Puppy 3.00beta2 bug reports here
How about a new thread for Beta 2 bugs:
Added a new printer to CUPS, but had to kill cupsd and restart it to get any jobs to print. Jobs would just vanish. Log shows error "PID 13554 stopped with status 127!" Works after restarting though.
I'll try again tomorrow.
Boots up nice now. Looking good so far.
Added a new printer to CUPS, but had to kill cupsd and restart it to get any jobs to print. Jobs would just vanish. Log shows error "PID 13554 stopped with status 127!" Works after restarting though.
I'll try again tomorrow.
Boots up nice now. Looking good so far.
Edited:
Just had a quick test....Beta2.
As reported by klhrevolutionist
Xvesa wizard: Still must press test instead of okay.
Yes this is annoying.
Always used Xvesa...with every Puppy release... no problems,
but now it has this issue.
Gxine won't open in full view....hangs....runs OK in smaller view.
First time ever....I wonder if it is related to Xvesa....never thought to try Xorg.
Couldn't say I am over impressed by the network wizard.
Connects OK etc....but seems more complicated for First Timers.
I thought the interface for the drives was a bit backward.
Everything works...copy..delete to NTFS....just not as intuitive as 2.17.
( Please disregard this comment...)
I picked puppy pfix=ram...definitely slower to boot first time.
Regards Chris
Just had a quick test....Beta2.
As reported by klhrevolutionist
Xvesa wizard: Still must press test instead of okay.
Yes this is annoying.
Always used Xvesa...with every Puppy release... no problems,
but now it has this issue.
Gxine won't open in full view....hangs....runs OK in smaller view.
First time ever....I wonder if it is related to Xvesa....never thought to try Xorg.
Couldn't say I am over impressed by the network wizard.
Connects OK etc....but seems more complicated for First Timers.
I thought the interface for the drives was a bit backward.
Everything works...copy..delete to NTFS....just not as intuitive as 2.17.
( Please disregard this comment...)
I picked puppy pfix=ram...definitely slower to boot first time.
Regards Chris
Last edited by cthisbear on Fri 28 Sep 2007, 01:39, edited 1 time in total.
I very hopefully burned the new beta, and tried it in the SCSI CD drive connected via PCMCIA. The kernel still can't find the CD because the initramfs still does not contain the i82365 and aha152x_cs modules. It still can't read the hard disk because that same initramfs still does not contain the jfs module. PLEASE add those modules to 3.00Beta3's initramfs!! How long must this Puppy beg? Thanks.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
It would be good if we could come to some understanding of what is going on here. Why would you have to kill the daemon and restart it?....iscraigh wrote:I reported that problem a couple of version ago, never got it figured out ended up jut putting an icon on my desktop to rune a script to restart cups.
Craig
In my case (Brother HL2040 Laser) it prints without any problems.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
Xvesa starts up in 640x480, same as always, which is why you have to press the TEST button to choose something higher. All previous Puppies worked this way.cthisbear wrote:Just had a quick test....Beta2.
As reported by klhrevolutionist
Xvesa wizard: Still must press test instead of okay.
Yes this is annoying.
Always used Xvesa...with every Puppy release... no problems,
but now it has this issue.
Gxine won't open in full view....hangs....runs OK in smaller view.
First time ever....I wonder if it is related to Xvesa....never thought to try Xorg.
Couldn't say I am over impressed by the network wizard.
Connects OK etc....but seems more complicated for First Timers.
I thought the interface for the drives was a bit backward.
Everything works...copy..delete to NTFS....just not as intuitive as 2.17.
I picked puppy pfix=ram...definitely slower to boot first time.
Regards Chris
Gxine not open in full view? ....aargh! surely not. this was an old bug that plagued us for ages, I complained for ages to the developers, and it did get fixed a few versions back. Is the bug back again? If so, then I'm really disappointed in Gxine. Either we have to go back to an earlier version, or use something else.
Does anyone remember anything about this? ...maybe a search back hrough the forum would help ...there was something that could be set to make it go into full-screen okay, as I recall.
The Network Wizard is supposed to be easier to use. I need feedback on this. Is the new design troublesome, did you prefer the one in 2.17?
"I thought the interface for the drives was a bit backward.
Everything works...copy..delete to NTFS....just not as intuitive as 2.17."
-- I don't understand what you are referring to here.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
PCMCIA total overhaul is scheduled for pup 3.01. However, booting from PCMCIA drives is a very low priority. JFS? ...dunno anything about it, so zero priority.dgi wrote:I very hopefully burned the new beta, and tried it in the SCSI CD drive connected via PCMCIA. The kernel still can't find the CD because the initramfs still does not contain the i82365 and aha152x_cs modules. It still can't read the hard disk because that same initramfs still does not contain the jfs module. PLEASE add those modules to 3.00Beta3's initramfs!! How long must this Puppy beg? Thanks.
Re: PCMCIA overhaulBarryK wrote:PCMCIA total overhaul is scheduled for pup 3.01. However, booting from PCMCIA drives is a very low priority. JFS? ...dunno anything about it, so zero priority.dgi wrote:I very hopefully burned the new beta, and tried it in the SCSI CD drive connected via PCMCIA. The kernel still can't find the CD because the initramfs still does not contain the i82365 and aha152x_cs modules. It still can't read the hard disk because that same initramfs still does not contain the jfs module. PLEASE add those modules to 3.00Beta3's initramfs!! How long must this Puppy beg? Thanks.
- Thanx!
- The machine is a Toshiba Satellite 105CS made in 1996, maxed out to 40MB RAM, so I felt that the only real choice for a filesystem on the HD is the lightning-fast JFS. I wouldn't consider ext2/3 or reiserfs to really be feasible on a 75MHz CPU, and vfat just isn't good enough.
- BarryK
- Puppy Master
- Posts: 9392
- Joined: Mon 09 May 2005, 09:23
- Location: Perth, Western Australia
- Contact:
iscraig, I just had a thought what the cause of the problem might be. What exact command do you use to kill and/or start/restart cupsd?iscraigh wrote:I reported that problem a couple of version ago, never got it figured out ended up jut putting an icon on my desktop to rune a script to restart cups.
Craig
WPA wireless using Zydas USB Dongle
Hi
I am using a wireless usb dongle with the Zydas 1211b chipset that worked fine in 2.17.1 using WPA encryption. Unfortunatly in 3.00 it is no go because when I use the network wizard is states that WPA cannot be used with the zd1211rw. Strange because it was fine in 2.17.1.
Thank you
Richard
I am using a wireless usb dongle with the Zydas 1211b chipset that worked fine in 2.17.1 using WPA encryption. Unfortunatly in 3.00 it is no go because when I use the network wizard is states that WPA cannot be used with the zd1211rw. Strange because it was fine in 2.17.1.
Thank you
Richard
Network wizard gives invalid "success" result
I use several Homeplug modules to extend my LAN. The one I use on my test PC is problematic in that a momentary power loss prevents it from connecting correctly. After this happens, pre-2.17, the wizard would report the i/f test as OK but autodhcp would time out after a minute and indicate "unsuccessful"; this is what I would expect.
The beta2 wizard (actually dhcpcd 3.1.0) in tha same situation shows success in both the test and autodhcp; ifconfig shows eth0 erroneously assigned to ip address 169.254.184.245 (which should be 192.168.0.1xx on my LAN). When running the wizard from the command line, two message lines are issued:The timeout period was only about 20 seconds.
As an experiment, I substituted the pre-2.17 version of dhcpcd (1.3.22), which restored the behavior to that of pre-2.17. Experimenting further, I substituted the slackware 12 version (2.0.4), which reported a successful i/f test and autodhcp after a one-minute wait, but did not issue the two "Error, eth0" messages; ifconfig did not show an eth0 entry, which is consistent with the timeout.
So, the erroneous "autodhcp success" already occurs with dhcpcd 2.0.4 (which is 1.3.22 plus many patches); but with 3.1.0 (in beta2 & 2.17), in addition, the bogus ip address gets assigned to the unconnected interface. The beta2 situation where the Homeplug device is connected but not functioning (or is actually disconnected from the wall plug), then, is that eth0 appears to be set up correctly but the browser mysteriously cannot connect to any web site. This is the second malfunction I have found that makes dhcpcd 3.1.0 harmful to Puppy's reputation for safety.
To net it out, for a nonfunctioning Homeplug ethernet interface device, beta2 autodhcp:
- waits only about 20 seconds for response from dhcp service.
- after announced timeout, displays "successful" dhcp receipt.
- assigns bogus ip address to eth0 and activates it (shown by ifconfig).
Richard
The beta2 wizard (actually dhcpcd 3.1.0) in tha same situation shows success in both the test and autodhcp; ifconfig shows eth0 erroneously assigned to ip address 169.254.184.245 (which should be 192.168.0.1xx on my LAN). When running the wizard from the command line, two message lines are issued:
Code: Select all
Error, eth0: timed out
Error, eth0: lease information file `/etc/dhcpc//dhcpcd-eth0.info does not exist
As an experiment, I substituted the pre-2.17 version of dhcpcd (1.3.22), which restored the behavior to that of pre-2.17. Experimenting further, I substituted the slackware 12 version (2.0.4), which reported a successful i/f test and autodhcp after a one-minute wait, but did not issue the two "Error, eth0" messages; ifconfig did not show an eth0 entry, which is consistent with the timeout.
So, the erroneous "autodhcp success" already occurs with dhcpcd 2.0.4 (which is 1.3.22 plus many patches); but with 3.1.0 (in beta2 & 2.17), in addition, the bogus ip address gets assigned to the unconnected interface. The beta2 situation where the Homeplug device is connected but not functioning (or is actually disconnected from the wall plug), then, is that eth0 appears to be set up correctly but the browser mysteriously cannot connect to any web site. This is the second malfunction I have found that makes dhcpcd 3.1.0 harmful to Puppy's reputation for safety.
To net it out, for a nonfunctioning Homeplug ethernet interface device, beta2 autodhcp:
- waits only about 20 seconds for response from dhcp service.
- after announced timeout, displays "successful" dhcp receipt.
- assigns bogus ip address to eth0 and activates it (shown by ifconfig).
Richard
Roaring Penguin works fine. The problem is that 'eth0' Ethernet Interface is not detected.BarryK wrote:Leon, please run Roaring Penguin from a terminal and report any error messages.
My D-Link DFE-530TX PCI Fast Ethernet Adapter (rev.C) and Intel(r)82801BA/BAM AC'97 Audio Controller was autodetected in all previous versions.BarryK wrote:Leon, when you state that you "can't setup alsa sound", what do you mean? Was sound auto-detected in previous puppies? In this beta2 are there sound modules loaded? (run lsmod).
Here are lsmod reports from Puppy 2.17.1 and from Puppy 3.00.beta2:
Puppy 2.17.1
# lsmod
Module Size Used by
snd_pcm_oss 46144 0
bsd_comp 6144 0
ipt_LOG 6912 3
n_hdlc 9356 1
ppp_synctty 9728 1
ppp_async 11780 0
crc_ccitt 2304 1 ppp_async
ppp_generic 27412 7 bsd_comp,ppp_synctty,ppp_async
slhc 6912 1 ppp_generic
usb_storage 86464 0
iptable_mangle 2944 0
iptable_nat 7812 0
ip_nat 17708 1 iptable_nat
xt_state 2560 0
ipt_REJECT 4736 1
ip_conntrack_ftp 7984 0
ip_conntrack_irc 7216 0
iptable_filter 3204 1
ip_conntrack 47376 5 iptable_nat,ip_nat,xt_state,ip_conntrack_ftp,ip_conntrack_irc
ip_tables 13528 3 iptable_mangle,iptable_nat,iptable_filter
snd_mixer_oss 17536 2 snd_pcm_oss
lp 12744 0
parport_pc 32996 1
parport 35784 2 lp,parport_pc
usblp 14340 0
via_rhine 24728 0
mii 6016 1 via_rhine
snd_intel8x0 34500 1
snd_ac97_codec 97700 1 snd_intel8x0
ac97_bus 2432 1 snd_ac97_codec
snd_pcm 78992 3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer 23432 1 snd_pcm
snd 52324 6 snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore 7904 2 snd
snd_page_alloc 10248 2 snd_intel8x0,snd_pcm
i2c_i801 8848 0
i2c_core 22672 1 i2c_i801
intel_agp 24860 1
agpgart 36176 1 intel_agp
usbhid 25568 0
fuse 46100 0
aufs 113036 1
nls_iso8859_1 4352 1
nls_cp437 6016 1
ehci_hcd 32408 0
ohci_hcd 22284 0
uhci_hcd 25364 0
usbcore 132252 7 usb_storage,usblp,usbhid,ehci_hcd,ohci_hcd,uhci_hcd
sr_mod 17832 0
ide_cd 40328 0
cdrom 40384 2 sr_mod,ide_cd
squashfs 48264 4
sqlzma 4356 1 squashfs
unlzma 4608 1 sqlzma
Puppy 3.00.beta2
# lsmod
Module Size Used by
iptable_mangle 2944 0
iptable_nat 7428 0
ip_nat 17324 1 iptable_nat
xt_state 2432 4
ipt_REJECT 4608 1
ip_conntrack_ftp 7568 0
ip_conntrack_irc 6800 0
iptable_filter 3072 1
ip_conntrack 46348 5 iptable_nat,ip_nat,xt_state,ip_conntrack_ftp,ip_conntrack_irc
ip_tables 12744 3 iptable_mangle,iptable_nat,iptable_filter
parport_pc 31716 1
lp 12616 0
parport 35528 2 parport_pc,lp
usblp 14080 0
fuse 44052 0
unionfs 83732 1
nls_iso8859_1 4224 1
nls_cp437 5888 1
usbhid 24928 0
usb_storage 83264 0
ehci_hcd 31116 0
ohci_hcd 21252 0
uhci_hcd 24076 0
usbcore 127128 7 usblp,usbhid,usb_storage,ehci_hcd,ohci_hcd,uhci_hcd
sr_mod 17188 0
ide_cd 39200 0
cdrom 36768 2 sr_mod,ide_cd
squashfs 47620 3
Last edited by Leon on Thu 27 Sep 2007, 18:58, edited 1 time in total.
- Lobster
- Official Crustacean
- Posts: 15522
- Joined: Wed 04 May 2005, 06:06
- Location: Paradox Realm
- Contact:
booted up with beta 2 OK
Seemed more complete, working etc
decided to try a Dougal remaster . . .
(that should push it)
It reported that I did not have enough memory
whilst I was copying files into the tmp folder (during the running of the remaster script)
I did have enough memory on the hard disk but I was not using a swap file (I have 512MB of ram but this might not be enough?)
Anyway I went ahead and the remaster was created but imperfect (missing icons and programs)
So I rebooted from Beta 2
and got . . .
I was loading the pup-save-photon.sfs
So I went back to using Tmxxine Prism (based on Puppy 2.17.1) and was able to load the pup-save-photon.sfs and its settings
Hope this info is useful.
Seemed more complete, working etc
decided to try a Dougal remaster . . .
(that should push it)
It reported that I did not have enough memory
whilst I was copying files into the tmp folder (during the running of the remaster script)
I did have enough memory on the hard disk but I was not using a swap file (I have 512MB of ram but this might not be enough?)
Anyway I went ahead and the remaster was created but imperfect (missing icons and programs)
So I rebooted from Beta 2
and got . . .
I was loading the pup-save-photon.sfs
So I went back to using Tmxxine Prism (based on Puppy 2.17.1) and was able to load the pup-save-photon.sfs and its settings
Hope this info is useful.
The full screen mode (ctrl-f) for Gxine does work if the Gxine window is maximized first. If the Gxine window is not full size before hitting ctrl-f it just flashes and remains the same size.
The Cups problem I reported last night is not a problem on the printer I just tried booting ram-only. I did set this one up as a raw printer, didn't use the Gutenprint ppd as I did last night. I'll try again at home both ways. Might be a non-problem
Should also mention, beta2 fixed:
Boot problems.
Modem problems.
WPA (small) problem.
And I think the new Network wizard is much better, please keep it.
The Cups problem I reported last night is not a problem on the printer I just tried booting ram-only. I did set this one up as a raw printer, didn't use the Gutenprint ppd as I did last night. I'll try again at home both ways. Might be a non-problem
Should also mention, beta2 fixed:
Boot problems.
Modem problems.
WPA (small) problem.
And I think the new Network wizard is much better, please keep it.
does anyone else encounter a problem with gxine freezing when playing mp3 files, in beta2?
barry, please add a stupid mode option to pupdial or add gtkdial as an option to the internet connection wizard.
barry, please add a stupid mode option to pupdial or add gtkdial as an option to the internet connection wizard.
[img]http://img230.imageshack.us/img230/8595/ubd6467dp2.png[/img]
[url=http://www.tinyurl.com/54tu74]Visit The Repository[/url] - Helpful and hard-to-find treats for Puppy 3.
[url=http://www.tinyurl.com/c5a68f]Click Here for Puppy Support Chat, + Helpful Links.[/url]
[url=http://www.tinyurl.com/54tu74]Visit The Repository[/url] - Helpful and hard-to-find treats for Puppy 3.
[url=http://www.tinyurl.com/c5a68f]Click Here for Puppy Support Chat, + Helpful Links.[/url]
Hi all!
I'm testing puppy beta2 frugal install on an Acer223x laptop.
First I tried to place all necessary files into a folder named "puppybeta2test" on my first partition (2Gb ext2 with a 2.17 frugal install on it), edited grub and rebooted. Puppy started well but was unable to load a driver for my network card. Then I placed the files to the root of my original puppy partition, only renamed the "vmlinuz" file to "vmlinuz1", edited grub and rebooted. Under these conditions puppy was able to detect my network card and autoDHCP worked as well.
I have the same the gxine full-screen problem,too (same conditions: XVesa, hangs on changing to full-screen mode). Another thing is that I cannot install either Adblock Plus or Falshblock and Noscript from the Seamonkey official addon site. I got the "Unexpected error -201 message", and googling didn't have any relevant results for this. Under 2.17 and Seamonkey 1.08 everything works fine with these extensions.
Best,
Matu
I'm testing puppy beta2 frugal install on an Acer223x laptop.
First I tried to place all necessary files into a folder named "puppybeta2test" on my first partition (2Gb ext2 with a 2.17 frugal install on it), edited grub and rebooted. Puppy started well but was unable to load a driver for my network card. Then I placed the files to the root of my original puppy partition, only renamed the "vmlinuz" file to "vmlinuz1", edited grub and rebooted. Under these conditions puppy was able to detect my network card and autoDHCP worked as well.
I have the same the gxine full-screen problem,too (same conditions: XVesa, hangs on changing to full-screen mode). Another thing is that I cannot install either Adblock Plus or Falshblock and Noscript from the Seamonkey official addon site. I got the "Unexpected error -201 message", and googling didn't have any relevant results for this. Under 2.17 and Seamonkey 1.08 everything works fine with these extensions.
Best,
Matu
pfix=ram
Hi Barry -
During boot-up from live-cd, with a setting of 'puppy pfix=ram' puppy still ransacked the harddisk and did an upgrade of my version 2.17 to 3.00. Gave me quite a suprise! Good thing the old version was just for testing.
Don
During boot-up from live-cd, with a setting of 'puppy pfix=ram' puppy still ransacked the harddisk and did an upgrade of my version 2.17 to 3.00. Gave me quite a suprise! Good thing the old version was just for testing.
Don
puppy3 bugs
Compaq Evo N600c laptop
ATI Radeon Mobility (16mb)
xvesa works fine; xorg doesn't work at all
xorg works in 2.17
what happened to wmpower? any other convenient (other than reading procs entries) way to monitor battery and temp?
ATI Radeon Mobility (16mb)
xvesa works fine; xorg doesn't work at all
xorg works in 2.17
what happened to wmpower? any other convenient (other than reading procs entries) way to monitor battery and temp?