4.1full install does not boot after power loss (USB related)

Message

edoc · #16 Post by **edoc** » Fri 06 Feb 2009, 15:29

I guess that I can reformat the HDD and start truly fresh and in that way begin to eliminate the hardware as the source of the problem.

I am guessing that BIOS is not involved as this appears to be well after BIOS in the boot process.

Stevo954 · #17 Post by **Stevo954** » Mon 09 Feb 2009, 02:31

I don't know what causes this problem, but I know how to get the computer booted up again. At the prompt type startx, which will bring up the desktop, but you will not have USB or network capabilities. Go to the menu and reboot the system. At this point everything should be fine. This at least works for me, hopefully for you too. Running puppy 4.1, if that makes any difference.

edoc · #18 Post by **edoc** » Mon 09 Feb 2009, 02:58

Do you mean at the prompt for the Puppy boot disk or some other prompt, please?

I tried it at the Puppy prompt and got an error that such a kernel was not available - then it booted from the CD.

vtpup · #19 Post by **vtpup** » Mon 09 Feb 2009, 04:24

Replace your vmlinuz and intird.gz with the ones on the CD.

Also be sure that your Grub is pointing to the right one of these if you have several in puplet directories, and one outside of them. Look at your menu.lst carefully for typos.

Initrd.gz and vmlinuz must be the correct ones for your sfs version. Unfortunately they all have the same name.

I'm going to guess your vmlinuz is bad or wrong or not pointed to correctly.

SmartCyber · #20 Post by **SmartCyber** » Mon 09 Feb 2009, 12:11

Code: Select all

#If we were not shutdown cleanly, try and recover 
if [ -f /tmp/RUNNING ];then 
 echo -n "(Cleaning up after unclean shutdown)" >/dev/console 
 rm -f /var/log/X* 
 rm -rf /tmp/* 
 rm -f /var/lock/LCK* 
 rm -f /var/run/*.pid 
 rm -rf /root/tmp 2> /dev/null 
 rm -rf /root/.thumbnails/* 2> /dev/null 
fi 

#create a file in tmp that should be deleted on a clean shutdown 
echo 'this file is deleted during a clean shutdown' > /tmp/RUNNING

This seems to solve all my problems but one thing missing I don't see RUNNING in /tmp anyone?

SmartCyber

edoc · #21 Post by **edoc** » Mon 09 Feb 2009, 16:56

vtpup wrote:Replace your vmlinuz and intird.gz with the ones on the CD.
Also be sure that your Grub is pointing to the right one of these if you have several in puplet directories, and one outside of them. Look at your menu.lst carefully for typos.
Initrd.gz and vmlinuz must be the correct ones for your sfs version. Unfortunately they all have the same name.
I'm going to guess your vmlinuz is bad or wrong or not pointed to correctly.

OK, checked GRUB, all was well there.

Cleaned up all of the save file debris and any other non-essentials.

Verified that the operating files are all identical with the CD.

Lost of the installed non-stock apps and games and updates but the boot problem appear to be solved.

THANKS!

vtpup · #22 Post by **vtpup** » Mon 09 Feb 2009, 17:25

You're welcome edoc.

SmartCyber · #23 Post by **SmartCyber** » Mon 09 Feb 2009, 19:07

ok I took on this instead same but just outside /tmp

Code: Select all

##############SHUTDOWN RECOVERY Add to /etc/rc.d/rc.sysinit################
#If we were not shutdown cleanly, try and recover 
if [ -f /RUNNING ];then 
 echo -n "(Cleaning up after Unclean SHUTDOWN)" >/dev/console 
 rm -f /var/log/X* 
 rm -f /RUNNING
 rm -rf /tmp/* 
 rm -f /var/lock/LCK* 
 rm -f /var/run/*.pid 
 rm -rf /root/tmp 2>/dev/null 
 rm -rf /root/.thumbnails/* 2>/dev/null 
fi 

###################Detect Bad Shut######################
#create a file in tmp that should be deleted on a clean shutdown
if [ ! -f /RUNNING ];then
 echo 'this file is deleted during a clean shutdown' > /RUNNING
fi

Code: Select all

###################### add to /etc/rc.d/rc.shutdown#######################
rm -f /RUNNING
echo "Puppy is deleting RUNNING..." > /dev/console

Thanks

SmartCyber

bugman · #24 Post by **bugman** » Sat 28 Feb 2009, 17:12

viperpiper wrote:

Code: Select all

#If we were not shutdown cleanly, try and recover
if [ -f /tmp/RUNNING ];then
 echo -n "(Cleaning up after unclean shutdown)" >/dev/console
 rm -f /var/log/X*
 rm -rf /tmp/*
 rm -f /var/lock/LCK*
 rm -f /var/run/*.pid
 rm -rf /root/tmp 2> /dev/null
 rm -rf /root/.thumbnails/* 2> /dev/null
fi

#create a file in tmp that should be deleted on a clean shutdown
echo 'this file is deleted during a clean shutdown' > /tmp/RUNNING

PURE NICENESS!!!

[thanks]

DerakB · #25 Post by **DerakB** » Fri 24 Jul 2009, 22:33

I have tried all the tricks that you have suggested but I am still having trouble with the system "simply" restarting from an unexpected power-off. I am running a Gateway E-3400(very old) with only 128 meg of ram. I started with an USB Keyboard and a USB Mouse but this issue has caused me to use a PS2 keyboard and a USB mouse. I have set the grup to
timeout 5
Which will force the system to restart even if a usb keyboard is being used. In my case the system will reload to a command prompt but the USB will not function. I get this annoying
Waiting for modules to complete loading... usb 1 2 3 4 5 6 7 8 9 10 done
Which assures me that the USB is not working.

Next I enter a simple
reboot

When the computer comes up again the USB is working and all is well.

My wish is to have the USB reset and functioning without having to issue the additional "reboot" command and the boot time associated with it.

Does anyone know how to reset the "USB" to accomplish this?
Also, I noticed that if you have a USB keyboard when you do the initial boot-up the keyboard will not work to allow you to push the enter key. Do you know if there is a fix for this as well. I mentioned the Time-out adjustment in the grub but is there another way to get the job done.

I really love Puppy Linux and I will continue to use it. I really surprised how annoying this is to those of us that want to use a USB device.

Thanks Guys.

Aitch · #26 Post by **Aitch** » Sat 25 Jul 2009, 18:28

DerakB/edoc

Hi guys, maybe this...

MU wrote:Might be a filesystem-error.

run Puppy with the option

puppy pfix=ram

Then mount the drive that holds pup_save.2fs

Then run from a consolewindow:
e2fsck -p /mnt/hdax/pup_save.2fs

(hdax must be hda1 or so, depending where it is stored).

Since Puppy 3.02, a filesystemcheck is added again to the startup.
Mark

edoc

In your case it sounds as though the usb drivers aren't loading properly/early enough [if not corrupted and cured by Mark's suggestion]
Maybe someone knows where you could add a script to bring them, OHCI. & EHCI, up earlier

All

Re: unexpected power-off

try using an UPS

Aitch

DerakB · #27 Post by **DerakB** » Tue 28 Jul 2009, 17:44

Thank you for the Response Aitch.

I have Puppy running on 6 Seperate antique computers with 128 meg of ram and from 400Mhz to 1Ghz.

I am running Version 4.2.1.

I have a variety of kids running Flash Games on them and they lock up frequently so Unclean Reboots are just a part of life.

Like I mentioned, what I would like is to be able to reset the USB and only have to power-off the unit and have it come up functional. Now I have to boot to a command prompt, then type reboot to have a functional unit.

Thanks if you have any additional thoughts.

Derak

Aitch · #28 Post by **Aitch** » Tue 28 Jul 2009, 22:36

Derak
2 thoughts - if possible try to upgrade the 128Mb ram, less likely to crash with any Puppy/kids use
I'd say fixing the browser/flash crashes, is probably worth a try, too

Have you tried ttuuxxx's firepup? I believe he sorted the flash/crash problem? and it runs faster, too, I can vouch for that

http://www.murga-linux.com/puppy/viewtopic.php?t=34876

Someone probably knows where/how to add a script to do a filesystem check/restore on reboot - but not me....

I also seem to remember a post about getting the usb module to load earlier, though I've seen USB keyboard/mouse problems with all sorts of OSes
Good Luck

Aitch

(old)Puppy Linux Discussion Forum

(old)Puppy Linux Discussion Forum

4.1full install does not boot after power loss (USB related)