PuppyThis forum is for the discussion of Puppy Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm currently running 4.21 (I tried 4.31 but the Multisession CD never would boot i've reported this as a bug and is neither here nor there)
During the boot it hangs for several minutes (almost 10) while scanning for pup_save files, presumably on the hard disk, which is physically damged which is why i'm running multi session CD to begin with.
Eventually it gives up then loads the save file from itself then eerythign works fine once it boots to RAM.
There has to be someway I can get it to automatically look on itself first...why this isn't the default when you create multi session CD is beyond me.
There isn't a pupp pfix command that I can find to get it to do that, or a way to create a new live cd without the need for the command (preferred), any help would be appreciative, been searching off and on for days.
First, a lot of options are removed and/or set to the "default of the masses" with Puppy to keep it small enough to fit into RAM, hence the blazing speed for which it's so well known.
And secondly, the culprit is the broken HDD. If it's unreadable and an access command is passed to the on-board controller, it will try for a long, long time before finally timing out and passing control back to BIOS.
My suggestion is to pull the plug on the HDD, and set BIOS to ignore HDD errors.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.