[SOLVED] How To Get Lilo to boot Peppermint 8 that's Alongside Slackware 14.2

Ztcoracat · 12-24-2017, 06:59 AM

Hi & Merry Christimas!

First I installed Peppermint 8 on my Sony Vaio last week.
The following day I performed a fresh installation of Slackware 14.2 and Slackware boots fine from the Lilo bootloader.

I checked to make sure that the partition for Peppermint 8 is still there and it is. Peppermint is on /dev/sda1.

Slackware in on /dev/sda3 *.

Code:

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1       517384192 976771071 459386880 219.1G 83 Linux
/dev/sda2         1026048   3123199   2097152     1G 82 Linux swap
/dev/sda3  *      3123200 517383930 514260731 245.2G 83 Linux

After making this entry in /etc/lilo.conf and re-running Lilo I don't see Peppermint on the front page of LILO while it's booting up.

Code:

# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda3
  label = Linux
  read-only

image = /boot/vmlinuz-Peppermint-4.10.0
  initrd = /boot/initrd-peppermint-4.10.0.gz
  root = /dev/sda1
  label = Peppermint
  read only

IF I use the up and down arrows it makes the time for LILO turn to zero. If I press Enter it automatically boots into Slackware. Than if I press the Tab key it give me an all black screen with a boot prompt.

After making the Peppermint entry and re-running Lilo I had a complaint about line 73.

Code:

Warning: LBA32 addressing assumed
Added Linux  *
Unrecognized token "read" at or above line 73 in file '/etc/lilo.conf'

(not sure what that's about)

How do I boot into Peppermint or what do I need to change or fix in the lilo.conf file so I have the option to boot into Peppermint?

Keruskerfuerst · 12-24-2017, 07:04 AM

You have made a small mistake:
read only
should be
read-only

Ztcoracat · 12-24-2017, 07:56 AM

Quote:

Originally Posted by Keruskerfuerst

You have made a small mistake:
read only
should be
read-only

I fixed it thanks.

I re-ran lilo.....and
Somethings wrong because I'm getting no such file or directory

bash-4.3# lilo
Warning: LBA32 addressing assumed
Added Linux *
Fatal: open /boot/vmlinuz-Peppermint-4.10.0: No such file or directory
bash-4.3#

bassmadrigal · 12-24-2017, 08:49 AM

Your kernel for peppermint needs to be available to the system (so the partition needs to be mounted), and Slackware's lilo needs to reference the location of that file.

So, I'd mount your peppermint partition under something /mnt/tmp, then you'd have your peppermint entry in lilo read

Code:

image = /mnt/tmp/boot/vmlinuz-Peppermint-4.10.0
  initrd = /boot/initrd-peppermint-4.10.0.gz
  root = /dev/sda1
  label = Peppermint
  read-only

NOTE: Anytime you update lilo, you'll need to ensure the peppermint partition is mounted. It might be beneficial to create a directory for it and set up an fstab entry to have it mounted all the time.

Ztcoracat · 12-24-2017, 08:54 AM

Quote:

Originally Posted by bassmadrigal

Your kernel for peppermint needs to be available to the system (so the partition needs to be mounted), and Slackware's lilo needs to reference the location of that file.

So, I'd mount your peppermint partition under something /mnt/tmp, then you'd have your peppermint entry in lilo read

Code:

image = /mnt/tmp/boot/vmlinuz-Peppermint-4.10.0
  initrd = /boot/initrd-peppermint-4.10.0.gz
  root = /dev/sda1
  label = Peppermint
  read-only

NOTE: Anytime you update lilo, you'll need to ensure the peppermint partition is mounted. It might be beneficial to create a directory for it and set up an fstab entry to have it mounted all the time.

I'll try the entry you made.

I'm not good with making entries in the fstab file and have zero practice at it.

I'll have to do some reading. Thanks.

Ztcoracat · 12-24-2017, 09:03 AM

Code:

bash-4.3$ mount /dev/sda1
mount: can't find /dev/sda1 in /etc/fstab
bash-4.3$

I'll have to do some reading about the fstab file and what the entries should be.
Don't know how, never tried it:-

bassmadrigal · 12-24-2017, 09:57 AM

Code:

mount /dev/sda1 /mnt/tmp

Since it isn't in the fstab, you need to specify the device and the mount location.

laprjns · 12-24-2017, 10:01 AM

You need to mount /dev/sda as root. So it should be:

Code:

$ su
# mount /dev/sda1 /mnt/tmp

Ztcoracat · 12-24-2017, 10:06 AM

Could you give me an example of what the argument should be in the fstab file?

I found the UUID for Peppermint:-

Code:

bash-4.3# blkid
/dev/sda1: UUID="609beeff-9175-4337-b121-def387895190" TYPE="ext4" PARTUUID="6efac2b1-01"

Ztcoracat · 12-24-2017, 10:09 AM

Quote:

Originally Posted by laprjns

You need to mount /dev/sda as root. So it should be:

Code:

$ su
# mount /dev/sda1 /mnt/tmp

That worked, thanks.

Re-run Lilo now or make the new entry in fstab first than run Lilo?

laprjns · 12-24-2017, 10:23 AM

You don't need to make an entry into fstab. Make sure that you edited the lilo.conf to have the proper path to the Peppermint image (i.e image = /mnt/tmp/boot/vmlinuz-Peppermint-4.10.0) then run lilo.

Ztcoracat · 12-24-2017, 10:36 AM

Quote:

Originally Posted by laprjns

You don't need to make an entry into fstab. Make sure that you edited the lilo.conf to have the proper path to the Peppermint image (i.e image = /mnt/tmp/boot/vmlinuz-Peppermint-4.10.0) then run lilo.

I edited the lilo.conf file with the path to Peppermint and re-ran Lilo but still have an error--

Code:

bash-4.3# lilo
Warning: LBA32 addressing assumed
Added Linux  *
Fatal: open /mnt/tmp/boot/vmlinuz-Peppermint-4.10.0: No such file or directory
bash-4.3#

What am I doing wrong?

laprjns · 12-24-2017, 10:44 AM

Code:

/mnt/tmp/boot/vmlinuz-Peppermint-4.10.0: No such file or directory

Is there really an uppercase "P" in vmlinuz-Peppermint-4.10.0? Do a directory listing to get the exact name

Code:

# ls /mnt/tmp/boot/

Ztcoracat · 12-24-2017, 11:00 AM

Quote:

Originally Posted by laprjns

Code:

/mnt/tmp/boot/vmlinuz-Peppermint-4.10.0: No such file or directory

Is there really an uppercase "P" in vmlinuz-Peppermint-4.10.0? Do a directory listing to get the exact name

Code:

# ls /mnt/tmp/boot/

No, there isn't an uppercase "P" at all. In fact, there is no mention of peppermint at all. Just the kernel.

Code:

System.map-4.10.0-42-generic  initrd.img-4.10.0-42-generic
System.map-4.8.0-53-generic   initrd.img-4.8.0-53-generic
abi-4.10.0-42-generic	      memtest86+.bin
abi-4.8.0-53-generic	      memtest86+.elf
config-4.10.0-42-generic      memtest86+_multiboot.bin
config-4.8.0-53-generic       vmlinuz-4.10.0-42-generic
grub			      vmlinuz-4.8.0-53-generic

laprjns · 12-24-2017, 11:10 AM

So the Peppermint stanza in lilo.conf should look like this

Code:

image = /mnt/tmp/boot/vmlinuz-4.10.0-42-generic
  initrd = /boot/initrd.img-4.10.0-42-generic
  root = /dev/sda1
  label = Peppermint
  read-only