Lucid Puppy 5.2.8 - Updated ISO Version 005 - APR 05 2012

[shinobar]

i don't know fuzzy's case, but Barry pointed out that the problem occurs when no save at shutdown.
http://bkhome.org/blog/?viewDetailed=02623
EDIT: i cannot find the code deleting /dev/snd in the rc.shutdown in woof. But as Barry comments, there are lines in the rc.sysinit:

Code: Select all

rm -f /dev/mixer 2>/dev/null #110113 make sure removed, see test in /etc/init.d/10alsa. 
rm -f /dev/snd/* #110304 after a reboot, some of these may be wrong.

These code may be a help for the sound module recognition(relating with the 10alsa) but seems not solve the whiteout problem.

I think the snapmergepuppy still need to update to allow no save and also for the sake of potential problem other than sound. My treating /dev and rerwin's treating whiteout in the test-2 iso shall solve them.

[rincon155]

This is to comment about a keyboard problem surely related to software that happened with my Puppy Linux 5.2.8. I use Puppy from the CD, and a lupu-file in HDD. My Puppy 5.2.8 is the original download plus update 002. Up to this point Puppy was working very well without any problem at all.
What happened is that I turned on my PC with the Puppy CD, and immediately proceeded to install Chromium. Once I did it, when I tried to use the keyboard, it did not respond.
I checked cables and connections, and everything was in order. Then I decided to reboot to my HDD Distro: PCLinuxOS LXDE 2011-09, and the keyboard was fine. Then reboot with my old Puppy 5.2 CD, and again, the keyboard was fine. Then, once more I rebooted with Puppy 5.2.8 and the keyboard was dead.
After that I rebooted with Slacko 5.3 CD and keyboard was ok.
Then I used Puppy 5.2.8 update 003 CD, rebooted, and keyboard didn't respond.
With this Puppy version functioning I uninstalled several packages, rebooted and the problem persisted.
I posted this problem in a thread "Is it possible to re-enable keyboard?" (http://www.murga-linux.com/puppy/viewto ... 077#589077) In which I received the suggestion to post in this thread.
I consider myself a Linux newbie, with user experience of 18 months with Ubuntu 10.04, Puppy Linux 5.2, 5.2.8 and PCLinuxOS LXDE 2011-09. I understand that participants in this thread are knowledgeable in Linux and in particular with Puppy. So if this report is of any help for further improvements in Puppy, I'll be very happy.
In my specific case, now that I tried Slacko 5.3, I'll move to it. Meanwhile I'll keep my Puppy 5.2.8 just in case any of you indicate me to apply any suggestion you might have related to the keyboard problem. Thank you.

[shinobar]

How much have you made the size of lupusave? It may easily filled up.
Standard size is 512MB, but it may not be enough for chromium.
Some informations:
http://www.murga-linux.com/puppy/viewtopic.php?t=62110
http://www.murga-linux.com/puppy/viewto ... 721#468721

Then I used Puppy 5.2.8 update 003 CD

After 'boot:' is displayed, type 'pfix=ram' to avoid using the old lupusave.
Then shutdown to create new upusave.

[shinobar]

Dupe... Deleted.

[Sylvander]

A. Posting this from test02-lupu-528x after Reboot-11.

All is looking good, and working well.

B. Steps completed so far:
1. Enable firewall.
2. Switch to JWM.
3. Install Pupsaveconfig-1.9.9
4. Make lupusave & Reboot-1.
5. Configure: Pinboard = medium.
6. Switch to JWM & restart-X.
7. Configure choices in Retrovol.
8. Change desktop icons.
9. Click "Save" & Reboot-2 [it auto-saved at shut-down, no choice offered]
10. Installed xfe-1.32.2-lucid52.
11. Click "Save" & Reboot-3 [auto-saved, no choice]
12. Installed Firefox-3.6.13-lucid, updated to 3.6.24.
13. Configured 0 save interval in Pupsaveconfig.
14. Click "Save" & Reboot-4, chose "Save" at shut-down.
15. Installed Parcellite-0.9.3-lucid.
16. Click "Save" & Reboot-5, chose "Save" at shut-down.
17. Click "Save" & Reboot-6, chose "Save" at shut-down.
18. Reboot-7, no saves.
19. Installed smm-1.0rc1.
20. Click "Save"& Reboot-8, no save at shut-down.
21. Installed Flashplayer-10.3.183.5-lucid.
22. Installed Flashplayer-10.3.181.34-lucid.
23. Click "Save" & Reboot-9, save at shut-down failed to complete, power-off & pfix=fsck at next boot.
24. Reboot-10, no saves.
25. Installed Firefox add-ons = Addblock+ and its popup blocked, Betterprivacy, Flashblock, Ghostery, Easy YouTube Video Downloader.
26. Click "Save" and Reboot-11.

[playdayz]

What happened is that I turned on my PC with the Puppy CD, and immediately proceeded to install Chromium. Once I did it, when I tried to use the keyboard, it did not respond.

rincon155, Sometimes that happens to me, that the keyboard is not recognized. This is what I do--I unplug the USB cable from the keyboard to the computer and plug it back in to a different USB port. That always fixes it for me, although very occasionally I might have to do it twice. I do not know how installing Chromium could cause that problem, but you might uninstall it and see if that changes anything. Finally, just in case the lupusave file got corrupted you might do what shinobar recommends in the message above. I recommend that you use the browser pets made for Lucid--although it usually works to install the binary released by the browser publishers. http://www.murga-linux.com/puppy/viewto ... 868#584868

i don't know fuzzy's case,

shinobar, fuzzy is reporting that using test02-lupu528x.iso is solving the problem with usb-flash/sound disappearing. test02-lupu528x has the fix that you posted on p.52 http://www.murga-linux.com/puppy/viewto ... 750#587750 Sylvander is also reporting that using test02-lupu-528x he has rebooted 11 times without losing sound. Thanks. BTW, i still intend to work on ffmpeg/ffconvert when the usb-flash/sound issue is settled.

.

[Sylvander]

test02-lupu-528x

I've now rebooted 14 times and all's well.

[rincon155]

How much have you made the size of lupusave? It may easily filled up.
Standard size is 512MB, but it may not be enough for chromium.
Some informations:
http://www.murga-linux.com/puppy/viewtopic.php?t=62110
http://www.murga-linux.com/puppy/viewto ... 721#468721

Then I used Puppy 5.2.8 update 003 CD

After 'boot:' is displayed, type 'pfix=ram' to avoid using the old lupusave.
Then shutdown to create new upusave.

Thank you shinobar for your post. My lupusave is 2.95 Gb. I will uninstall other packages to see if this solve the problem and if not I'll create a new lupusave.

[shinobar]

@rincon155
Is your keyboard PS/2 or USB?
How about at the prompt(without X)? i mean Menu>>Shutdown>>Exit to prompt.

If you can use mouse, you can see the logs after boot.
Such as /tmp/bootkernel.log, /var/log/Xorg.0.log...

[Sylvander]

test02-lupu-528x
Still looking good and working well.

A. Now up to Step:
49. Reboot-18 to Wary-522, moved Lupusave to a folder in an ext3 partition on the 2nd internal HDD.

B. Now booting using a CD-RW disk made using test02-lupu-528x-ataflash.iso
To make this I added "pmedia=ataflash" setting to the "isolinux.cfg" file included in the test02-lupu-528x.iso file.
This treats the lupusave file on the HDD as though it's a lupusave on a Flash Drive.

C. This Lupu [from my point of view], is now in a fully completed build state.
All desirable/needed packages have been installed, and configurations and code changes made.

D. Only thing I can detect that isn't as I'd like:
Pwidgets Calendar: The present day is not highlighted.

[playdayz]

Thank you Sylvander. This is the farthest we have gotten since 5.2.6. What I will do now is to make a release iso. My fingers are still crossed.

[Sylvander]

A. By-the-way...

I installed "Psip Puppy Phone" version 0.26, and gave it a try.

PuppyLuvr called me, I took the call, he reported severe echo at his end.
My end was fine.
After a while...
Not having made ANY change...
The echo ceased.

Might this perhaps be...
That my on-board-sound + sound card [both enabled]...
Is causing echo at the other persons end?

Any thoughts?

B. Will I be able to use your new-release ISO file to update my lupusave contents?

[bigpup]

Thank you Sylvander. This is the farthest we have gotten since 5.2.6. What I will do now is to make a release iso. My fingers are still crossed.

Great to see you are making progress on sound issue. Seems you have found cure.
Not knowing what changes you have made to Lucid Puppy 528, with test02-lupu-528x.
I hope you have considered, that those changes, did not remove a fix for other problems.
The simple fix is not always the best one.

Thanks for your continuing efforts to improve Lucid Puppy 528.

[rincon155]

@rincon155
Is your keyboard PS/2 or USB?
How about at the prompt(without X)? i mean Menu>>Shutdown>>Exit to prompt.

If you can use mouse, you can see the logs after boot.
Such as /tmp/bootkernel.log, /var/log/Xorg.0.log...

It is a wireless device with PS/2 and USB connection. Initially it was installed using PS/2, then I changed to USB directly. No difference. But again, using any other OS (Puppy's or different Distros: in HDD and LiveCD's), in both case PS/2 and USB keyboard worked fine.
I uninstalled several packages in Puppy 5.2.8, and tried keyboard one by one, but the problem stayed. After so many uninstall's I concluded that my customized lupusave lost any sense, so I deleted it and I am now using Slacko 5.3 with everything fine. May be lupufile was corrupted, but why it occurred just after Chromiun install, being the first action after PC startup?

[Brown Mouse]

What I will do now is to make a release iso.

Are you planning on including a fix that will be included for the main release 528.iso or is this a separate issue?

[rhadon]

@shinobar
the last days I was playing with pmedia=ataflash instead of atahd (Slacko 5.3). Also played with rc.shutdown, but often changes in rc.shutdown were not saved at the end of the session. Other changes like copying or deleting got saved.

Since I use alsa_snapmergepuppy-20111210-shinobar.tar.gz, everything seems to work fine.

Thank you
Rolf

[playdayz]

Are you planning on including a fix that will be included for the main release 528.iso or is this a separate issue?

Brown Mouse, I think you are asking about this.

Release Candidate for Lucid 5.2.8-004
This has the same fixes as the test02-lupu-528x.iso, specifically shinobar and rerwin's repairs to snapmergepuppy and 10alsa. It appears to fix the problem with usb-flash/sound disappearing, as well as possibly other problems, as in rhadon's message above. It also has the latest Install Flashplayer to adjust to the fact that Adobe has started moving the flashplayer binary around. Apart from those changes it contains Instant Update 002. No other changes are included as the main purpose is to consolidate a fix for the usb-flash/sound issue.

http://diddywahdiddy.net/Puppy500/lupu-528.004.iso
4d8c53f27d605775b1791fb32791c704
.

[kevin bowers]

Playdayz,
After all these fixes and retractions and more fixes, which DevX file should go with lupu-528.004? Or does it need its own? BTW, I'm in awe of the Puppy developer team, especially you, Shinobar, Rerwin, and Smokey01, you guys busted tail for what looked like about a half-dozen Puppy users with sound problems. OK, maybe it was for the sake of a job well done, equally admirable. Thanks and kudos!

[Sage]

Exactly what is the strategy? A gold version soon? And how does this affect 3HD?
Whatever, must echo the congratulatory. Polishing brings an inner glow - very professional to dot the 't' s and cross the 'i' s, so to speak!

[Sylvander]

A. Downloaded the Lupu-528.004.iso file.

B. Edited the isolinux.cfg file on the iso, and renamed it Lupu-528.004-ataflash.iso

C. Made a CD-RW using Lupu-528.004-ataflash.iso

D. Deleted the "old" SFS file beside the lupusave file, and copied the "new" SFS into its place.

E. Rebooted using the Lupu-528.004-ataflash CD-RW.
It found and used the "old" lupusave file.
There was no notification of a need to update the lupusave file.
Is this because...
Lupu-528.004.iso
Is IDENTICAL to...
test02-lupu-528x.iso ?

F. Anyway...
It's working just as well as before.
Unable to tell any difference.