grub(SuSE)/Lilo(Slackware) chain loader problems

The Chain · 10-18-2004, 11:24 PM

The slackware installation loaded and I installed pretty easily. Now the problem is that I have the first grub from SuSE in the system taking control. Slackware comes with Lilo but I put that in /hda5 with Slackware.

My menu.lst grub file has the following:

# Modified by YaST2. Last modification on Mon Oct 18 01:26:01 2004

color white/blue black/light-gray
default 0
timeout 8
gfxmenu (hd0,0)/boot/message

###Don't change this comment - YaST2 identifier: Original name: linux###
title Linux
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x31a splash=silent desktop resume=/dev/hda2 showopts
initrd (hd0,0)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: floppy###
title Floppy
root (fd0)
chainloader +1

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe
kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3
initrd (hd0,0)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: Slackware###
title Slackware
kernel (hd0,4)/boot/vmlinuz root=/dev/hda5
initrd (hd0,4)/boot/initrd

The last part that says slackware I put it myself to see if I was able to boot. I also tried to do chainloader before with:

###Slackwares###
title Linux2
rootnoverify (hd0,4)
makeactive
chainloader +1
boot

However this didn't work either. Can someone help me out with chainloader instructions for grub that comes with SuSE.

Thanks in advance

bigrigdriver · 10-19-2004, 12:47 AM

Check your Slackware and see if it comes with grub but just doesn't install it.
Since it's now setup for lilo, grub can't find the parts of itself to finish the boot into Slack (no chainloader needed. grub boots Linux natively; chainloaders are need to boot other OS's; like ms or os/2).
If Slack has grub, you will need to boot from the installation cd, then install grub into the Slack partition. If you allow that installation to write to the MBR, then the Slack version of grub would be the bootloader instead of the SuSE installation. Copy the info from the Suse /boot/grub/menu.lst and paste into the Slack /boot/grub/menu.lst, with any necessary edits, and you should be good to go.
Otherwise, install grub entirely in Slack, and edit the Suse menu.lst (copy the SuSE linux info and edit appropriately) to show the Slack menu item.

The Chain · 10-19-2004, 12:13 PM

Alright, I was looking for a less radical solution but I'm pretty sure it's going to take an entire installation of grub in Slack. I was trying to boot into slack and so far the only way i got in was through command line. I could even browse the web in command line but it's not much fun when you have to read all of the source code of the page heh. Well let me see what the cd shows me and I'll update you on it. Thanks for helping

The Chain · 10-19-2004, 12:37 PM

Okay I tried one last thing:

###Don't change this comment - YaST2 identifier: Original name: Slackware###
title Slackware
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5 ro

and it booted but into command line mode again. What do I need to add to load KDE?

The Chain · 10-19-2004, 01:48 PM

I also just tried
###Don't change this comment - YaST2 identifier: Original name: Slackware###
title Slackware
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5 ro hdd=scsi
savedefault
boot

but I got command line mode again

The Chain · 10-19-2004, 02:15 PM

OKAY I FINALLY SOLVED IT. Any one following my footsteps listen up:

(First even if you install Lilo from the install cds from Slackware don't save lilo in the MBR save it in the partition that you installed Slackware. That way you'll be able to boot SuSE okay it's very important)

If you're in SuSE and installed Slackware in a different partition add this into your menu.lst file from grub that can be found in the Yast configurator.

Put this in provided you put your correct partition of course. In this case I installed Slackware in my /hda5 partition (also called hd0,4)

Code:

# Modified by YaST2. Last modification on Mon Oct 18 01:26:01 2004
 
 
 color white/blue black/light-gray
 default 0
 timeout 8
 gfxmenu (hd0,0)/boot/message
 
 ###Don't change this comment - YaST2 identifier: Original name: linux###
 title Linux
 kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 vga=0x31a splash=silent desktop resume=/dev/hda2 showopts
 initrd (hd0,0)/boot/initrd
 
 ###Don't change this comment - YaST2 identifier: Original name: floppy###
 title Floppy
 root (fd0)
 chainloader +1
 
 ###Don't change this comment - YaST2 identifier: Original name: failsafe###
 title Failsafe
 kernel (hd0,0)/boot/vmlinuz root=/dev/hda1 showopts ide=nodma apm=off acpi=off vga=normal noresume nosmp noapic maxcpus=0 3
 initrd (hd0,0)/boot/initrd

###Don't change this comment - YaST2 identifier: Original name: Slackware###
 title Slackware
 root (hd0,4)
 kernel /boot/vmlinuz root=/dev/hda5 ro hdd=scsi
 savedefault
 boot

Okay then you'll boot into command line mode it will ask you:

Login:

So you type: Root
Press enter, then your password

then you're logged in and your greeted with command line email from some guy trying to be funny. Okay ignore it lol

then type: startx

Then the kde menu pops up asking you how you want your menus to look. You can choose from several colors, etc. Then click Finish and congrats you're running Slackware!

It took me forever but I finally made it. Email advocateofreason@yahoo.com if you have questions. I'm a newbee but I'm learning fast so I'll share what I know with you.

youknowwho · 10-20-2004, 03:21 AM

change the initt in /etc/inittab to 4

shane2peru · 10-08-2006, 08:03 AM

Thanks Chain,

This is what I have been looking for. I currently have XP, Mepis, and want to install Slackware. So I should install lilo at all right? Or install it to the hdd where Slackware is installed and not to the MBR. Then edit my menu.lst with Mepis and add those lines of course editing the hdd's to fit my setup? Is this correct! Thanks for leaving a bread crumb trail.

Shane

saikee · 10-08-2006, 11:00 AM

You can have any number of Linux and Windows in the PC but there is only one MBR at the beginning of the first bootable disk.

You can elect any of the boot loader into the MBR so that it boots the rest.

Generally speaking the easiest way to multi-boot is install every boot loader of each Linux, except the one controlling the MBR, in its own root partition. If every Linux from say hda5 to hda9 has its boot loader inside then amending the boot loader controlling the MBR is all that is needed.

If Lilo is used then these lines in /etc/lilo.conf of the Linux controlling the MBR should fire up the Linux hda5 to hda9

Code:

other=/dev/hda5
label=Linux_in_hda5 

other=/dev/hda6
label=Linux_in_hda6 

other=/dev/hda7
label=Linux_in_hda7 

other=/dev/hda8
label=Linux_in_hda8

other=/dev/hda9
label=Linux_in_hda9

If Grub is used the corresponding lines in /boot/grub/menu.lst are

Code:

title Linux in hda5
root (hd0,4)
chainloader +1

title Linux in hda6
root (hd0,5)
chainloader +1

title Linux in hda7
root (hd0,6)
chainloader +1

title Linux in hda8
root (hd0,7)
chainloader +1

title Linux in hda9
root (hd0,8)
chainloader +1

Grub counts from 0 so (hd0,8) is the 9th partition of the 1st disk.

The above is the exact method a Linux boots a Windows. However Every Linux can be booted by another Linux. The only necessary condition is to have the boot loader of the Linux, which can be either Lilo or Grub, installed inside its root partition. A MS system always installs it boot loader insdie its root partition.

There is nothing simpler or more powerful in Linux booting so enjoy it.

shane2peru · 10-09-2006, 09:02 AM

Thanks for the help. Here is the situation again. I couldn't get Slackware installed, so I went with Mandriva instead to give that a try. I thought I had Mandriva install its grub in the MBR, but apparently that didn't happen. When I rebooted, Mepis still had controll of the MBR and grub. I also have XP installed. Here is what my Mepis grub menu.lst looks like:

Code:

timeout 15
color cyan/blue white/blue
foreground ffffff
background 0639a1

gfxmenu /boot/grub/message

title MEPIS at hda2, kernel 2.6.15-26-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.15-26-386 root=/dev/hda2 nomce quiet vga=791 
boot

title Windows at hda1
rootnoverify (hd0,0)
chainloader +1

title Mandriva
root (hd0,3)
kernel (hd0,3)/boot/vmlinuz root=/dev/hda4  splash=silent vga=788
initrd (hd0,3)/boot/initrd.img


title Mandriva2
root (hd0,3)
kernel /boot/vmlinuz-2.6.17-5mdv root=/dev/hda4 nomce quiet vga=788
initrd /boot/initrd-2.6.17-5mdv.img


title Mandriva3
root (hd0,3)
chainloader +1


title MEMTEST
kernel /boot/memtest86+.bin

I use three entries to try different things faster, when I get a winner, I will delete the others. Here are the erros I get:

For Mandriva3 I get:
root (hd03)
Filesystem type unknown, partition type 0xb
Chainloader +1
Error 13: Invalid or unsupported executable format

I get the following error message for Mandriva and Mandriva2:

Booting 'Mandriva'
root (hd0,3)
Filesystem type unknown, partition type 0xb
kernel (hd0,3)/boot/vmlinuz root=/dev/hda4 splash=silent vga=788
Error 17: Cannont mount selected partition

Ok, one more thing here is what the grub menu list looks like inside Mandriva's partition (I can mount it from Mepis and see its files):

Code:

timeout 10
color black/cyan yellow/cyan
shade 1
viewport 3 2 77 22
splashimage (hd0,3)/boot/grub/splash.xpm.gz
default 0

title Mandriva
kernel (hd0,3)/boot/vmlinuz root=/dev/hda4  splash=silent vga=788
initrd (hd0,3)/boot/initrd.img

title linux-nonfb
kernel (hd0,3)/boot/vmlinuz root=/dev/hda4 
initrd (hd0,3)/boot/initrd.img

title failsafe
kernel (hd0,3)/boot/vmlinuz root=/dev/hda4  failsafe
initrd (hd0,3)/boot/initrd.img

title windows
root (hd0,0)
makeactive
chainloader +1

title Mepis
kernel (hd0,3)/boot/vmlinuz-2.6.17-5mdv root=/dev/hda5 splash=silent
initrd (hd0,3)/boot/initrd.img

I have tried copying the boot menu list for Mandriva out of here and pasting it into the Mepis one, it didn't work either for the record. HELP! Thanks!

Shane

saikee · 10-09-2006, 10:00 AM

Your problem is Mandriva installation was unsuccessful. Why? It should not be installed in hda4 if it has a partition type 0xb. Type 0xb or b is Fat32. You should have installed a Linux in type 83 partition which is for native Linux.

To install a Linux you should ideally use a Linux partitioning program, like cfdisk which is available in terminal mode of every Linux. In your case if there is no data inside hda4 you can use cfdisk inside Mepis to alter the partition type from b to 83 (you need to click "write" in order to finalise the partition table). Thereafter Mandriva installer will find it. Just select hda4 partition inside Mandriva installer for "edit", choose it for mounting "/" which is the root of Mandriva and format it in ext3. You will find Linux will be installed faultlessly in such a setup.

If you still have a problem list here the content of the terminal command

Code:

fdisk -l

shane2peru · 10-09-2006, 03:20 PM

Saikee,

Thanks for the help. This is weird, and I'm a bit perturbed at QTParted. I don't think I have ever used it and had it work, on any Linux distro. I re-formated that partition with Qt Parted to ext3, before it was FAT32. I even commited the chagnes it said everything worked correctly. I then attempted to install Slackware, and it didn't bring up hda4 as ext3 it only brought up my others that already had Linux on them. It also didn't ask me about formating any of the existing partitions. When I tried Mandriva (with its super nice installation procedure) it 'said' it formated the partition as ext3 as well. No here is my fdisk -l

Code:

fdisk -l

Disk /dev/hda: 40.0 GB, 40007761920 bytes
255 heads, 63 sectors/track, 4864 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1        2493    20024991    7  HPFS/NTFS
/dev/hda2            3826        4463     5124735   83  Linux
/dev/hda3            4464        4863     3213000    5  Extended
/dev/hda4            2494        3825    10699290    b  W95 FAT32
/dev/hda5            4464        4830     2947896   83  Linux
/dev/hda6            4831        4863      265041   82  Linux swap / Solaris

Go figure??? How can I format this as ext3. Also what is really wierd is that Mandriva did install because I can mount that partition and see the files that are on there. Did Mandriva install onto fat32? I wouldn't think it would be allowed because fat32 doesn't contain the permissions like ext3 does. Is gparted any better? Do I need to re-install Mandriva? I don't know anything about cfdisk, and am leary of cli programs for formatting disks, it is just a little too easy to mess up. However if it works, I may be willing to try it, I will need some documentation with Ex. on how to use it though. Thanks!

Shane

shane2peru · 10-09-2006, 03:58 PM

Ok, sorry for the double post. Now I really broke my system. "If it ain't broke, tweak it!" - I just keep playing around, and now I can't boot into Mepis, or Mandriva! Guess I should burn Slackware disks and install it. I can boot into XP. Here is what I did. I figured it was just the partition table that needed change/corrected. So I ran cfdisk to see what happens. It was easy, I just changed the partition type to ext3 - 83. When I rebooted, it almost booted into Mandriva, the boot screen came up, and everything, and it hung there. I tried the Mandriva2 boot option, and it gave me the boot screen and I can see where it hung. It hung on the setting the localhost name, or something like that. Maybe it was the server name? I don't remember. Sorry. Anyway, it hung. I shut it off and booted off the Mandriva CD I thought maybe I need to re-install grub.
I re-installed grub, and rebooted. Mandriva now has control of the grub, and I can't boot into either. Well, Mandriva leaves me hanging at the login prompt, with NO GUI. Sorry, I'm not that good at linux. Tried startx and it gave me an entire page of reasons it couldn't start the GUI. Too bad Mandriva doesn't have apt-get, I would have fixed that right away. I tried to boot into Mepis, and get the kernel panic error, couldn't sync or something. Instead of triple booting, I'm now single booting!

I can access ext3 on my XP, but I don't know if I can edit the files I need to correctly. That may take me from bad to worse. HELP! Any suggestions? Also, can Mandriva and Mepis share the /home ? I attempted to have them share, and am wondering if this is not a problem? Thanks!

Shane

saikee · 10-09-2006, 06:00 PM

Please remember for any partition there is a partition type which is your responsibility to create. Generally you need to click a "confirm" button or some kind before Linux would write the partition table.

To format it is normally the responsibility of the installer. No sane installer or any installer in its right mind will trust you to do a formatting. It should always format the partition itself so that it is safe for the system to reside in.

You should learn to use cfdisk as it is available in every Linux (although the Red Hat family distros use sfdisk).

My guess is your Mandriva partition is faulty because its filing system index was possibly set up according to Fat32 (Type b). When you change it to type 83 the filing idexing system will change resulting all files have the wrong addresses. When Grub tried to load Mandriva it would be a miracle if it did not hang.

Now it is high time you learn how to boot the systems manually.

Mandriva does not use gfxmenu (the 5th line of your Mepis indicates Mepis uses it). This mean if you see Mandriva's Grub by press "c" you will get a Grub prompt. In a Grub prompt you are in the terminal mode with Grub and deal with it directly. That is how you sort out this bugger once and for all. Type "help" to see all the commands you can run in Grub. It is 10 times more difficult to hang a Grub so keep trying until everything works for you. Trial and error is a VERY decent method of learning with computer.

Print out the Mepis /boot/grub/menu.lst and use the instruction there to boot XP and Mepis. You only need to miss the "title" statement and finish every system with an extra "boot" command. There is a lot of errors in your menu.lst according to the fdisk-l information so I correct them as follow

For example if you want to boot Mepis, which is in hda2 and not hda1, in a Grub prompt, type these lines

Code:

root (hd0,1)
kernel /boot/vmlinuz root=/dev/hda2 vga=0x31a ro
initrd /boot/initrd
boot

Your Windows is in hda1 or (hd0,0) to GRub and so it should boot by

Code:

root (hd0,0)
chainloader +1
boot

Try them and let us know the result.

shane2peru · 10-09-2006, 07:12 PM

Ok, the saga continues. I did get to boot into Mepis, I logged into XP, I can read/write ext3 with windows thanks to a nifty little ext3 application. Can't remember the name right now. I did edit the grub again, and got into Mepis. I have edited the grub with the 'c' to play around with the menu.lst from grub. I also have used the 'e' to change a line. My problem is I usually need another example from another menu.lst - whether from the web, or from another distro on my machine.
I ran cfdisk, fixed the partition table. Re-installed Mandriva - a new install. and it still hangs on boot up. This time it is not a grub issue, it is a mandriva issue. Slackware disks are burning as I type. However now I want Mepis back in charge of the grub, and I probably can't do that without a new install of Mepis? If so I will try Slackware again, now that my partition tables are corrected. If Slackware doesn't do a good job of running Grub, that is ok, I'm feeling more comfortable with editing and fixing grub issues. And further more, I am triple booting!!! That is great. Well, technically, only dual for the moment, but that is Mandriva's fault for not installing correctly, and not fixing the partition. It asked me if I wanted to format the partition, and I told it yes, and it went throught the procedure. Oh well. Water under the bridge now. Thanks for the help.

Shane
I have successfully been dual booting for a while. I have had installed Mandrake (1 month), Suse (2 month), Ubuntu/Kubuntu (1.5 years), Debian (2 days), Mepis (1 month+), FC5 (2 weeks), and now we are going to give Slackware a try, and stay with Mepis for a while.