9 replies to this topic

[911CD.net]

'lo again. 

 

I have an old Dell Latitude D610 Windows XP notebook.  I'm trying to boot a Linux system on it which will allow the grandkids to access their school work from home. The schools are all closed here. The Linux systems I'm testing are having wifi problems and I'm working on debugging them.  But the grub4dos boot menu is not working with the kernel override I'm trying to load.  Booting keeps giving me File Not Found errors.

set ISO4=Porteus-CINNAMON-v4.0-k4.19.113-i586.iso

title Porteus 4.0   changes=EXIT\n 330MB\n %ISO4%\n Run 'blkid' as root to find all info about drives and partitions.
# http://www.911cd.net/forums/index.php?s=&showtopic=25876&view=findpost&p=176070
find --set-root /ISOs/%ISO4%
map --heads=0 --sectors-per-track=0  /ISOs/%ISO4% (0xff)
map --hook
root (0xff)
#kernel (0xff)/boot/syslinux/vmlinuz
kernel /mnt/sda6/porteus40/vmlinuz from=/ISOs/%ISO4%  changes=EXIT:/porteus40/changes/porteussave.dat extramod=/porteus40/Modules volume=20
initrd (0xff)/boot/syslinux/initrd.xz

The porteus40 folder is on the same drive as the ISOs folder and I've tried numerous ways of coding the /porteus40/vmlinux location to no avail.

 

Now the grub4dos system on the Dell is old, Grub4DOS 0.4.5c 2013-03-03, just like the notebook and Windows XP, but worked well up until this adventure.  What release can I upgrade to that will support the kernel override and not require a rewrite of all the menus?  Or is there is a menu coding trick that will fix the problem?

 

Thank you.

[Wonko the Sane]

As always, try on command line.

 

Or add echo and pause commands to the menu entry, so that you know which file is not found.

 

Very likely  it is the 

/mnt/sda6/porteus40/vmlinuz

that cannot be found, for several reasons, the main one being that THAT IS NOT A GRUB4DOS PATH!

 

A grub4dos path will be something *like*

(hd0,5)/porteus40/vmlinuz

 

In the menu entry you posted, you :

1) first establish root to (0xff)

2) attempt chainloading /mnt/sda6/porteus40/vmlinuz

and that (obviously) makes grub4dos look for the path/file (literally):

(0xff)/mnt/sda6/porteus40/vmlinuz

 

Wonko

[steve6375]

Looks to me like you need to change the kernel line to...

kernel (0xff)/boot/syslinux/vmlinuz from=/ISOs/%ISO4%  changes=EXIT:/porteus40/changes/porteussave.dat extramod=/porteus40/Modules volume=20

[911CD.net]

Very likely  it is the 

/mnt/sda6/porteus40/vmlinuz

that cannot be found, for several reasons, the main one being that THAT IS NOT A GRUB4DOS PATH!

 

A grub4dos path will be something *like*

(hd0,5)/porteus40/vmlinuz

 

Yup. 

 

As always, my mentor. 

 

And thanks for the suggestion steve6375 but Wonko's post was right on. 

[steve6375]

ok, sorry, I missed this bit of your post...

The porteus40 folder is on the same drive as the ISOs folder

[Wonko the Sane]

OK, so the "right" way (portable) should be:

 

 

set ISO4=Porteus-CINNAMON-v4.0-k4.19.113-i586.iso

title Porteus 4.0 changes=EXIT\n 330MB\n %ISO4%\n Run 'blkid' as root to find all info about drives and partitions.
# http://www.911cd.net...ndpost&p=176070
find --set-root /ISOs/%ISO4%
map --heads=0 --sectors-per-track=0 /ISOs/%ISO4% (0xff)
map --hook
kernel /porteus40/vmlinuz from=/ISOs/%ISO4% changes=EXIT:/porteus40/changes/porteussave.dat extramod=/porteus40/Modules volume=20

root (0xff)
initrd /boot/syslinux/initrd.xz

 

Wonko

 

 

[911CD.net]

Trust me Wonko if that format worked I wouldn't have posted for help.  It's the one I stated with and when it didn't work I tried:

 

kernel /mnt/sda6/porteus40/vmlinuz

kernel /dev/sda6/porteus40/vmlinuz

kernel /mnt/sda5/porteus40/vmlinuz

kernel /mnt/sda5/porteus40/vmlinuz

 

kernel (hd0,5)/porteus40/vmlinuz was the format that worked.

 

[911CD.net]

Oh wait.  I see what you did.  You moved the root (0xff) command past the kernel command.   

 

Thank you Wonko.  

[Wonko the Sane]

Sure.

"(hd0,5)" is simply grub4dos syntax corresponding to the Linux "/mnt/sda6"

But since:

 

 

 

The porteus40 folder is on the same drive as the ISOs folder and I've tried numerous ways of coding the /porteus40/vmlinux location to no avail.

 

the moment you do:

find --set-root /ISOs/%ISO4%

you are setting root to that volume, which, more generally, is always"the same drive as the ISOs folder"..

If you prefer, this:

 

set ISO4=Porteus-CINNAMON-v4.0-k4.19.113-i586.iso

title Porteus 4.0 changes=EXIT\n 330MB\n %ISO4%\n Run 'blkid' as root to find all info about drives and partitions.
# http://www.911cd.net...ndpost&p=176070
find --set-root /ISOs/%ISO4%

root

pause
map --heads=0 --sectors-per-track=0 /ISOs/%ISO4% (0xff)
map --hook
kernel /porteus40/vmlinuz from=/ISOs/%ISO4% changes=EXIT:/porteus40/changes/porteussave.dat extramod=/porteus40/Modules volume=20

root (0xff)
initrd /boot/syslinux/initrd.xz

 

will show you which grub4dos volume it is.

 

So you have to chainload a kernel that is on the same volume as the ISO's (and to which you have already established root) so that you can use a relartive path such as:

/porteus40/vmlinuz

or (more properly):

()/porteus40/vmlinuz

 

and then you have to chainload an initrd that you know (because you just mapped the ISO to it) is on (0xff), an that can be:

(0xff)/boot/syslinux/initrd.xz

or

 

root (0xff)
initrd /boot/syslinux/initrd.xz

 

or (again unneded, but more proper):

 

root (0xff)
initrd ()/boot/syslinux/initrd.xz

 

Wonko

[911CD.net]

My mentor  jaclas.