LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Dual boot Slack 32 bit and Slack 64 bit on two drives - lilo config? (http://www.linuxquestions.org/questions/slackware-14/dual-boot-slack-32-bit-and-slack-64-bit-on-two-drives-lilo-config-4175430505/)

camorri 10-04-2012 10:44 AM

Dual boot Slack 32 bit and Slack 64 bit on two drives - lilo config?
 
I had a dual boot setup working using grub 1 on sda mbr. I was using Magia 2, and gurb 1 for booting Magia on sda1 and Slackware 13.37, 64 bit on sdb1. I could boot either system.

For a number of reasons, I decided to get rid of Magia, and install Slackware 14, 32 bit version in Magia's place.

Before I formatted sda1, I installed lilo on the mbr on sdb, configure lilo. To make that work, I have to hit F12 during the BIOS startup, select the second drive as the boot drive, then lilo on sdb takes over and I can boot Slackware 13.37 64 bit.

I'm now trying to boot both slackware installs from lilo on the mbr on hda. I can boot sda1, the new install of Slackware 14, but can not get my older Slackware on sdb1 to boot form sda mbr.

Here is my current ( last attempt ) of lilo.conf from sda1.

Code:

boot = /dev/sda
compact        # faster, but won't work on all systems.
  bitmap = /boot/slack.bmp
  bmp-colors = 255,0,255,0,255,0
  bmp-table = 60,6,1,16
  bmp-timer = 65,27,0,255
append=" vt.default_utf8=0"
prompt
timeout = 50
# VESA framebuffer console @ 1024x768x32k
vga = 790
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sda1
  label = Slackware14-32
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz-custom-3.2.7
  initrd = /boot/initrd.gz
  root = /dev/sdb1
  label = Slackware13-37
  read-only  # Partitions should be mounted read-only for checking
# Linux bootable partition config ends

Right now I get a 'not found' type message. That leads me to believe lilo is looking in the /boot directory for kernel name vmlinuz-custom-3.2.7 ( my 64 bit kernel on sdb1 boot dir. )

My question is how to get lilo on sda to look in the /boot dir in sdb1 for the correct kernel and initrd.gz files?

All the How to's I have found think dual booting is a linux system and a windows system. They don't help much.

I also tried lilo.config expert mode. I'm no expert at lilo. Simply put, that didn't work, it did not pick up the name of the kernel I'm using on the 64 bit system.

Your help is always appreciated.

Drakeo 10-04-2012 10:53 AM

when you run /sbin/lilo what is the feed back. or is there a error

camorri 10-04-2012 12:24 PM

I just re-ran lilo, here are the results.

Quote:

root@duelie:~# lilo
Warning: LBA32 addressing assumed
Added Slackware14-32 *
Fatal: open /boot/vmlinuz-custom-3.2.7: No such file or directory
As you can see, the kernel on sdb1 /boot dir is not seen, hence my question in post #1.

One thing I thought of trying is to copy the kernel and initrd.gz files to the /boot dir on sda1. I have no idea if this would work, or if other files like the system.map would be required as well. I thought this might also cause problems for maintenance.

In the not too distant future, I want to update the 64 bit system to version 14 as well. I want to get the 32 bit version working and configured in the short term.

colorpurple21859 10-04-2012 12:44 PM

mount the second hard drive installation (say /mnt ) and edit lilo.conf to
Code:

image = /mnt/boot/vmlinuz-custom-3.2.7
  initrd = /mnt/boot/initrd.gz

rerun lilo
The way you have it now lilo is pointing to your 1st drives /boot

This will work too.
Quote:

copy the kernel and initrd.gz files to the /boot dir on sda1

Drakeo 10-04-2012 02:13 PM

Quote:

Before I formatted sda1, I installed lilo on the mbr on sdb, configure lilo.
go in to bios set up make sure your drive are in sync with the lilo. because lilo is looking for at sdb1 /boot/vmlinuz. but if your bios have it set as a different drive then this will cause it lilo was mapped for the other drive.
most likely sdb is sda now to lilo let me know. or you may just pop in supper grub or a puppy linux and sort it out. let me know.

colorpurple21859 10-04-2012 02:19 PM

Chainloading is another way to go. You may have to reinstall lilo from the slackware64 back into it's MBR with both hard drives attached to work.

camorri 10-04-2012 02:44 PM

colorpurple21859

Took your first suggestion in post #4, it worked like a charm. Thank-you.

I think chain loading would work also, just a little to windoze like.

This is what lilo.conf looks like now.

Quote:

image = /mnt/sdb1/boot/vmlinuz-custom-3.2.7
initrd = /mnt/sdb1/boot/initrd.gz
root = /dev/sdb1
label = Slackware13-37
read-only

Drakeo 10-04-2012 04:55 PM

why not just copy the kernel image and the intrd image to your sda1 /boot folder then tell it sdb1 is root then run /sbin/lilo because thats what it will look for the /etc/fstab that has worked for me many times.

Quote:

image = /mnt/sdb1/boot/vmlinuz-custom-3.2.7
initrd = /mnt/sdb1/boot/initrd.gz
root = /dev/sdb1
label = Slackware13-37
read-only
If that works great

colorpurple21859 10-04-2012 07:50 PM

I Chainload most of the time. It makes it easier when I'm doing a lot of distro hopping/testing


All times are GMT -5. The time now is 02:19 AM.