i install a debian base linux in sda1 and bootloader
and now i install porteus 5.0 in sda7 but i dont install bootloader because i want debian bootloader
and now porteus isnt in boot menu
how i can add porteus in boot menu
i test grub customizer:
set root='(hd0,7)'
search --no-floppy --fs-uuid --set=root 153c0a05-0d38-4197-8a8f-000d40667feb
linux file:///media/farid/Porteus/boot/syslinux/vmlinuz root=UUID=153c0a05-0d38-4197-8a8f-000d40667feb
initrd file:///media/rahimi/Porteus/boot/syslinux/initrd.xz
but when start i give this error: invalid file name: file:///media/farid/Porteus/boot/syslinux/vmlinuz
you must load kernal first
two linux grub menu
- Rava
- Contributor
- Posts: 5401
- Joined: 11 Jan 2011, 02:46
- Distribution: XFCE 5.01 x86_64 + 4.0 i586
- Location: Forests of Germany
two linux grub menu
I do not know how "grub customizer" works.
Where do you get the paths "/media/farid/" from?
Is it how sda7 is mounted in your debian base linux when that's started from sda1?
I have two suggestions.
Try
when what you wrote was meant as one line
or try
Same with the initrd.
When that is not working, copy and rename the initrd and vmlinuz into something unique e.g. copy initrd.xz as initrd_porteus.xz and vmlinuz as vmlinuz_porteus
Copy both files into the same place on sda1 where your vmlinuz and initrd from debian base are sitting, where ever that might be.
Then usebut also use the cheatcodes from Porteus - specifically the UUID= one.
Look how the kernel parameter are given to the debian base kernel and copy the approach for your Porteus kernel.
How does your path to porteus/base looks like on sda7?
Is it just /mnt/sda7/porteus/base and /mnt/sda7/porteus/modules ?
Does /mnt/sda7/porteus/porteus-v5.0-x86_64.cfg exist?
If not, e.g. when your base folder looks like so
/mnt/sda7/Porteu5.0/
then you have to add some info into your grub menu.
And use the cheatcode for the UUID of
Cave! The "APPEND=" syntax is the one used in porteus.cfg to give additional instructions to the kernel.
Most likely your grub menu file will need another way of giving to the kernel.
And Cave² - my above "APPEND=" line presumes you copied initrd.xz as initrd_porteus.xz to where the initrd from debian base are.
when debian base initrd and vmlinuz are not on the same place, 1st try to copy the Porteus initrd as "initrd_porteus.xz" into the same location where the debian base vmlinuz sits, and also copy the Porteus kernel into that place as vmlinuz_porteus
Make sure your setup via grub addresses the Porteus files the same way you renamed them (e.g. like I suggested: as initrd_porteus.xz and as vmlinuz_porteus)
Where do you get the paths "/media/farid/" from?
Is it how sda7 is mounted in your debian base linux when that's started from sda1?
I have two suggestions.
Try
Code: Select all
linux file:///media/sda7/Porteus/boot/syslinux/vmlinuz root=UUID=153c0a05-0d38-4197-8a8f-000d40667feb
or try
Code: Select all
linux file:///mnt/sda7/Porteus/boot/syslinux/vmlinuz root=UUID=153c0a05-0d38-4197-8a8f-000d40667feb
When that is not working, copy and rename the initrd and vmlinuz into something unique e.g. copy initrd.xz as initrd_porteus.xz and vmlinuz as vmlinuz_porteus
Copy both files into the same place on sda1 where your vmlinuz and initrd from debian base are sitting, where ever that might be.
Then use
Code: Select all
root='(hd0,1)'
Look how the kernel parameter are given to the debian base kernel and copy the approach for your Porteus kernel.
How does your path to porteus/base looks like on sda7?
Is it just /mnt/sda7/porteus/base and /mnt/sda7/porteus/modules ?
Does /mnt/sda7/porteus/porteus-v5.0-x86_64.cfg exist?
If not, e.g. when your base folder looks like so
/mnt/sda7/Porteu5.0/
then you have to add some info into your grub menu.
And use the cheatcode for the UUID of
Code: Select all
APPEND initrd=initrd_porteus.xz from=UUID:153c0a05-0d38-4197-8a8f-000d40667feb
Most likely your grub menu file will need another way of giving
Code: Select all
initrd=initrd_porteus.xz from=UUID:153c0a05-0d38-4197-8a8f-000d40667feb
And Cave² - my above "APPEND=" line presumes you copied initrd.xz as initrd_porteus.xz to where the initrd from debian base are.
when debian base initrd and vmlinuz are not on the same place, 1st try to copy the Porteus initrd as "initrd_porteus.xz" into the same location where the debian base vmlinuz sits, and also copy the Porteus kernel into that place as vmlinuz_porteus
Make sure your setup via grub addresses the Porteus files the same way you renamed them (e.g. like I suggested: as initrd_porteus.xz and as vmlinuz_porteus)
Cheers!
Yours Rava
Yours Rava
- Ed_P
- Contributor
- Posts: 8368
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
two linux grub menu
I would try:
Code: Select all
# set root='(hd0,7)'
search --no-floppy --fs-uuid --set=root 153c0a05-0d38-4197-8a8f-000d40667feb
linux /Porteus/boot/syslinux/vmlinuz root=UUID=153c0a05-0d38-4197-8a8f-000d40667feb
initrd /Porteus/boot/syslinux/initrd.xz
-update-
Actually I would leave the vmlinuz root= parm off altogether. root is already set to that drive via the search command.
Code: Select all
# set root='(hd0,7)'
search --no-floppy --fs-uuid --set=root 153c0a05-0d38-4197-8a8f-000d40667feb
linux /Porteus/boot/syslinux/vmlinuz
initrd /Porteus/boot/syslinux/initrd.xz
Ed
two linux grub menu
solved with this command in grub customizer: name:Porteus type:other
insmod part_msdos
insmod ext2
set root='hd0,7'
linux /boot/syslinux/vmlinuz login=guest changes=/porteus
initrd /boot/syslinux/initrd.xz
insmod part_msdos
insmod ext2
set root='hd0,7'
linux /boot/syslinux/vmlinuz login=guest changes=/porteus
initrd /boot/syslinux/initrd.xz
- Ed_P
- Contributor
- Posts: 8368
- Joined: 06 Feb 2013, 22:12
- Distribution: Cinnamon 5.01 ISO
- Location: Western NY, USA
two linux grub menu
Good for you Farid.
I would still go witha search command rather than the set root one. That way the menu automatically works if you move Porteus to a different drive.
BTW The c:/grub2/grub.cfg file can be manually edited with a text editor, which allows you to make changes to it while in linux or Windows.
I would still go witha search command rather than the set root one. That way the menu automatically works if you move Porteus to a different drive.
BTW The c:/grub2/grub.cfg file can be manually edited with a text editor, which allows you to make changes to it while in linux or Windows.
Ed