Welcome to the most active Linux Forum on the web.
Go Back > Forums > Linux Forums > Linux - Distributions > Puppy
User Name
Puppy This forum is for the discussion of Puppy Linux.


  Search this Thread
Old 01-09-2019, 07:29 PM   #1
LQ Newbie
Registered: Oct 2015
Posts: 18

Rep: Reputation: Disabled
wont boot, can not find find the kernel/file

Yesterday while trying to install a distro on sda1, I wiped sdb1.

Easy fixed I'll just put the latest xenial puppy back on sdb1.

Alas it won't boot as the menu.lst isn't finding the file/kernel.

I'm running an MSI board, i3 with 4g ram, all bought last year.

the menu.list is in part
# menu.lst produced by grub4dosconfig-v1.9.2
color white/blue black/cyan white/black cyan/black
timeout 5
default 0

title woof
#root (hd0,0) <-- GRUB legacy, ex: (hd1,0)
uuid ca50481b-1e30-4756-9d3a-01fe8af807a0
kernel /boot/vmlinuz fullinstall root=UUID=ca50481b-1e30-4756-9d3a-01fe8af807a0 pmedia=atahd 
#                                root=/dev/sdb1
initrd /boot/initrd.gz

I figure the problem is in there somewhere, but I do not know where.

Yet the boot folder hold only two files. config-4.9.58 and

Any help is appreciated.
Old 01-10-2019, 04:32 AM   #2
Senior Member
Registered: Dec 2002
Location: Mosquitoville
Distribution: RH 6.2, Gen2, Knoppix,arch, bodhi, studio, suse, mint
Posts: 3,279

Rep: Reputation: 62
why would you guess that vmlinuz and initrd.gz don't exist in the boot folder? try putting a vmlinuz and initrd.gz in that folder.
Old 01-11-2019, 09:30 PM   #3
LQ Newbie
Registered: Oct 2015
Posts: 18

Original Poster
Rep: Reputation: Disabled
Originally Posted by whansard View Post
why would you guess that vmlinuz and initrd.gz don't exist in the boot folder? try putting a vmlinuz and initrd.gz in that folder.
Fixing the problem wasn't quite that easy, but youpointed me in the right direction. Thanks.

There was entire line missing from the menu.lst.

Problem now solved.
Old 01-12-2019, 07:58 AM   #4
Registered: Jul 2017
Location: King's Lynn, UK
Distribution: Puppy Linux, AntiX
Posts: 277

Rep: Reputation: 127Reputation: 127
Originally Posted by whansard View Post
why would you guess that vmlinuz and initrd.gz don't exist in the boot folder? try putting a vmlinuz and initrd.gz in that folder.
Just for information, the way Puppy works is rather different to most Linux distros. Puppy doesn't use a 'boot directory'. At all. Vmlinuz and initrd.gz always sit at the root of the partition where Puppy is installed to.

I know it sounds peculiar, but that's just the way Puppy works.

(And before anybody else chirps up with 'Grub4DOS is deprecated and isn't safe'.....NO. The Puppy fork of the Grub4DOS bootloader is specifically 'tweaked' to work with Pup's unique way of doing things.....and is regularly maintained by the Woof-CE team over at GitHub. The most recent patched version was released just 4 months ago...)

Attached below is a fairly typical Puppy partition/sub-directory layout - a 'backup' copy, but it gives the idea (Pup can be installed to a directory within the partition, since the Grub4DOS bootloader searches 'two-deep' for the kernel and system SFS files)....


The initrd.gz is decompressed into RAM at boot (space permitting), creating the 'virtual RAM-disk' where Puppy lives for the duration of the session. Then, the main Puppy SFS file is decompressed and written to the RAM-disk. The 'save-file' (where personal changes/configurations are stored) is also decompressed, and, due to the union aufs file-system layering, is combined with the system files to present a homogeneous 'whole' OS to the user.

The system file SFS is 'read-only', and thus Puppy always boots with a 'clean' install. At shutdown, any personal changes are written back to the 'save-file', which is then re-compressed, and overwrites the existing version. The 'system' stuff disappears into thin air, and is replaced anew at the next boot.

Additional SFS program files can be loaded/unloaded 'on-the-fly', as & when required.

This is known as the 'frugal' install, and is the preferred method for running Puppy. The only time a traditional 'full' install is ever recommended is for seriously 'RAM-challenged' hardware, where there isn't sufficient room to load Puppy to RAM in its entirety.

The way Puppy is designed, the 'frugal' install has many advantages that the 'full' version simply doesn't have access to (chief among which is Puppy's blazing speed!).....since Puppy was always intended, right from the outset back in 2004, to be installed to a flash drive, not a HDD.

Attached Thumbnails
Click image for larger version

Name:	image-67.png
Views:	5
Size:	65.1 KB
ID:	29452  

Last edited by Mike_Walsh; 01-12-2019 at 03:46 PM.


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] Custom kernel wont boot can not find sda error bagginmtdoom Debian 12 08-21-2015 12:53 PM
Win8 wont boot or recover/ wont allow cd or usb boot of Linux/ can not reach bios Bhakta Neal Linux - Newbie 7 01-03-2013 04:17 AM
RTAI kernel can't find hard disk at boot, but normal kernel can jamwaffles Linux - Software 0 04-08-2009 02:44 PM
install Suse, xp wont boot, repair xp suse wont boot Tangz Linux - Newbie 10 07-16-2004 06:37 PM
Suse 9, RH9 wont install properly. Mandrake 9 wont boot properly? Help. l2ich84 Linux - Newbie 1 01-31-2004 12:02 PM > Forums > Linux Forums > Linux - Distributions > Puppy

All times are GMT -5. The time now is 03:00 PM.

Main Menu
Write for LQ is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration