Puppy 501 won't load

BobbyDing · 06-04-2010, 10:37 PM

Just FYI...
I just spent an evening trying to load puppy 501 on a thinkpad 600 and was getting the same error 'cannot load lupu-501.sfs. I created a fat32 2gb partition and copied lupu-501.sfs over to it, but it would not see that either.

The eventual fix was to add 'acpi=force' to the command line.

So you hit F2 when puppy cd boots, then type 'puppy acpi=force'.

It booted saying it is iqnoring IRQ10, but it booted up great!

It sees my Dynex ethernet pcmcia. The display looks great. Only the sound doesn't work, which is not a deal breaker for me.

Hope that helps somebody down the road.

Bobby

riki · 06-05-2010, 01:32 AM

Quote:

Originally Posted by BobbyDing

Just FYI...
I just spent an evening trying to load puppy 501 on a thinkpad 600 and was getting the same error 'cannot load lupu-501.sfs. I created a fat32 2gb partition and copied lupu-501.sfs over to it, but it would not see that either.

The eventual fix was to add 'acpi=force' to the command line.

So you hit F2 when puppy cd boots, then type 'puppy acpi=force'.

It booted saying it is iqnoring IRQ10, but it booted up great!

It sees my Dynex ethernet pcmcia. The display looks great. Only the sound doesn't work, which is not a deal breaker for me.

Hope that helps somebody down the road.

Bobby

Tried your fix typing puppy acpi=force
but still no joy. In other words, it won't work, won't boot. Goes to show that what works for some doesn't for others.

Terris · 03-08-2011, 01:10 PM

Quote:

Originally Posted by riki

I haven't encountered any booting/loading issues with other CDs. The problem with Puppy is that it starts loading OK. See below:

Loading drivers needed to access disk drives....DONE

Searching for Puppy files in computer disk drives... lupu-501.sfs not found. Drop ping out to initial-ramdisk console...
/bin/sh: can't access tty: job control turns off.
#_

I found this thread after encountering this exact same problem on a Toshiba Portégé R500. I tried all the cheat codes to fix it, I read all the suggestions in another forum about checking that the files were correctly named with lower case letters and a dash, not an underscore. Nothing worked.

I assumed that what was happening was that the boot process was not finding the lupu-501.sfs file on the LiveCD for some reason. I simply used another computer running Linux (and therefore able to read the Linux file system) and copied lupu-501.sfs to an SD card (since the Portégé R500 has an SD card slot). Now, when I boot Puppy from the CD it does find lupu-501.sfs, copies it to RAM, and continues normally.

I'm not sure if there is any other way to get past this error, but to anyone with this issue that wants a quick fix, I would suggest:

1) Copy that lupu-501.sfs file to any other device, such as a USB drive if you can.
2) Insert that drive in the intended sytem.
3) Boot normally from the Puppy 501 CD as usual.

This way, the missing lupu-501 file should get discovered during the boot process from the LiveCD. You will still need the LiveCD.

My next step, if I can, will be to discover how to install Puppy 501 completely on the SD card, so I don't need the CD drive any more.

grevillea · 08-03-2011, 06:03 PM

I was experiencing the same problem with attempting to load Puppy 5.1.2 Wary and Puppy 4.3.1 on Portege R700. Seems the problem in my case was caused by having a USB hard drive connected during boot. Without the drive connected, puppy found the sfs file and loaded it from the CD correctly.