Therefore, to directly create a pupsave file compatible with Precise, I would have added to the pupsave, the file /etc/gtk-2.0/gdk-pixbuf.loaders

Problem: I know how to create a blank pupsave, but I do not know how to create a pupsave containing a file (/etc/gtk-2.0/gdk-pixbuf.loaders).
If anyone knows how to do, I thank in advance for information.

I'm using the precise 5.7.1 retro build live on an HP dv1250 laptop. It hangs on shutdown in /etc/init.d/10alsa stop called by /etc/rc.d/rc.shutdown. I did some debugging and it appears that the command modprobe -rv snd_intel8x0 hangs. I tried it from a terminal and it hangs there as well. It doesn't hang when other five snd_* kernel modules get removed. For now I have commented out the outer while loop that calls modprobe -rv in /etc/init.d/10alsa stop. If anyone knows how to permanently fix this issue I welcome some help.
I suppose I can't blacklist snd_intel8x0 because it provides the actual sound system, but I'm not positive.
I tried a precise 5.6.1 live and it hangs in the same way.
My hardware:
# lspci | grep audio
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)Last edited by step on Thu 22 May 2014, 13:07; edited 1 time in total

I boot, configure eth0 and eth1 with network-wizard, then reboot and I find that only eth0 is connected, while eth1 isn't even up, even though I had also saved its configuration in network-wizard. So this issue can be described as network wizard not being able to fully restore a previously saved configuration when two wired NICs are involved. The configuration seems to be saved correctly, but it isn't restored.
When the system reboots eth0 is correctly configured. Manually executing ifconfig eth1 up starts the interface but without IP address.
Please look at the linked thread for configuration details, because a cable modem/router and a LAN router are both involved.

I'm using the precise 5.7.1 retro build live on an HP dv1250 laptop. It hangs on shutdown in /dev/init.d/10alsa stop called by /etc/rc.d/rc.shutdown. I did some debugging and it appears that the command modprobe -rv snd_intel8x0 hangs. I tried it from a terminal and it hangs there as well. It doesn't hang when other five snd_* kernel modules get removed. For now I have commented out the code loop in /dev/init.d/10alsa stop that calls modprobe -rv. If anyone knows how to permanently fix this issue I welcome some help.
I suppose I can't blacklist snd_intel8x0 because it provides the actual sound system, but I'm not positive.
I tried a precise 5.6.1 live and it hangs in the same way.
My hardware:
# lspci | grep audio
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)

Thank god someone finally found this. This problem was occurring on my Inspiron 700m as well, requiring me to use a different version of Puppy. Commenting out that modprobe -rv line in /etc/init.d/10alsa seems to fix the shutdown problem. A proper fix would be most appreciated.

Thank god someone finally found this. This problem was occurring on my Inspiron 700m as well, requiring me to use a different version of Puppy. Commenting out that modprobe -rv line in /etc/init.d/10alsa seems to fix the shutdown problem. A proper fix would be most appreciated.

Thank god someone finally found this. This problem was occurring on my Inspiron 700m as well, requiring me to use a different version of Puppy. Commenting out that modprobe -rv line in /etc/init.d/10alsa seems to fix the shutdown problem. A proper fix would be most appreciated.

I'm not having any sound problems at all with Precise 5.6.1
on my Inspiron 700M

Sound problems aren't the issue, shutting down is the issue. Mine freezes with both versions and this edit is the only fix I've found.

I HAVE BEEN PUPPY DISTRO HOPPING FOR ABOUT THREE YEARS NOW,USING 5.7.1 ON MY ASUS 1005HAG NETBOOK I CAN FIND NO PROBLEMS. THIS DISTRO APPEARS TO BE STABLE,CAN BE INSTALLED AS A DUAL BOOT WITH THE EXE INSTALLER OR RUN EQUALLY WELL FROM MY FLASH DRIVE.NO MORE HOPPING FOR ME,THANK YOU TO ALL INVOLVED.

Both full hard drive and frugal USB installs hang at shutdown after X shuts down.

Once "Precise Puppy is Shutting Down" appears on the screen, my Latitude D400 (1.4 Pentium M, 1 GB RAM) hangs there until the power button is held down for several seconds.

Edit - Looks like this is the same bug noted by posters step and yin a little earlier in this thread... Sorry for not paying more attention!

step wrote:

I'm using the precise 5.7.1 retro build live on an HP dv1250 laptop. It hangs on shutdown in /dev/init.d/10alsa stop called by /etc/rc.d/rc.shutdown. I did some debugging and it appears that the command modprobe -rv snd_intel8x0 hangs. I tried it from a terminal and it hangs there as well. It doesn't hang when other five snd_* kernel modules get removed. For now I have commented out the code loop in /dev/init.d/10alsa stop that calls modprobe -rv. If anyone knows how to permanently fix this issue I welcome some help.
I suppose I can't blacklist snd_intel8x0 because it provides the actual sound system, but I'm not positive.
I tried a precise 5.6.1 live and it hangs in the same way.
My hardware:
# lspci | grep audio
00:1f.5 Multimedia audio controller: Intel Corporation 82801DB/DBL/DBM (ICH4/ICH4-L/ICH4-M) AC'97 Audio Controller (rev 03)

yin wrote:

Thank god someone finally found this. This problem was occurring on my Inspiron 700m as well, requiring me to use a different version of Puppy. Commenting out that modprobe -rv line in /etc/init.d/10alsa seems to fix the shutdown problem. A proper fix would be most appreciated.

A Live CD version of Precise 5.7.1 Retro boots up OK & runs H/W fine. Installing to USB stick also works for the first boot.

clicking on Menu->shutdown brings up a sequence of dialogs about setting up a personal save file. All this works OK too. Then X shuts down and the computer hangs, showing the message "precise puppy is now shutting down".

Holding the power button down does eventually cause the computer to shut down.

When attempting to do the second boot the OS shows all the normal startup messages until it tries to load the save file. Then it generates a kernel panic and hangs. Message sequence: Not syncing; attempted to kill init.

If the save file is renamed or deleted Precise always boots OK.

This behavior also is exhibited when booting a Frugal install that has a save file.

The problem occurs regardless of the file format chosen for the save file (ext2, ext3 etc). The size of the file also does not appear to influence this behavior.

Opening the save file shows that it contains one folder called "lost+found" and nothing else.

Back when I had a working spare internal HD I installed Precise on it with no problems so I don't believe the problem is a hardware or BIOS incompatibility issue.

I'm currently using Wary but thought a bug report might help the community of Precise users. My take on the problem is that the shutdown script used for a Frugal or flash drive install has a problem in the section that writes data to the save file.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum