Can i set lilo.conf boot from different linux kernel?
i am multiboot with LILO for Slackware 14.0, -current.
I created lilo.conf when i last install Slackware-current.
My problem is when i select to boot slackware 14.0, it boot and bring me to the "darkstar login:", after that i can not have any access to my keyboard to type commands. i force shut down.
However,i can boot-in to Slackware14 using USB boot stick.
One thing i noticed is my Slackware Current is Linux 3.2.26, it use .26 to boot the Slackware14 but when i boot with USB stick it use Linux 3.2.29 and it boot smoothly.
How to correct my lilo.conf so that my slackware14 will boot with Linux 3.2.29 instead of 3.2.26?
The problem is that when you run lilo from -current, with the following lines for your Slackware-14 boot...
If you want -current to manage the MBR then you have two choices:
1. Mount the slackware-14 kernel so it is visible from -current, then change lilo.conf to use it for the Slackware-14 boot stanza
2. Create a lilo.conf within Slackware-14 to install lilo to its own partition, then chain boot that from -current
The first one might be done like this (provide your own paths)
I always prefer the chain boot methods for my own systems.
That way, there is never any confusion about which OS instance owns the MBR, and no requirement to mount other boot partitions when I run lilo.
Hey it works. I take the second choice.
Thank you astrogeek!
|All times are GMT -5. The time now is 07:42 PM.|