LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 01-22-2005, 10:26 AM   #1
xgreen
Member
 
Registered: Aug 2003
Distribution: Slackware,Arch
Posts: 389

Rep: Reputation: 30
Lilo


hi,

i just installed Suse 9.1 beside slackware & window. i am using lilo as a loader but when i trying to boot Suse, it's boot with 2.4.26 kernel from slackware instead of kernel 2.6.4.
any idea??

my lilo.conf :

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
append="hdc=ide-scsi"
boot = /dev/hda
#compact # faster, but won't work on all systems.
prompt
#timeout = 300
# VESA framebuffer console @ 1024x768x256
vga = 773
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769
# ramdisk = 0 # paranoia setting
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hda2
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/hdb1
label = SuSE
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
~
~
 
Old 01-22-2005, 10:37 AM   #2
MBH
Member
 
Registered: Sep 2003
Location: Kuwait
Distribution: Slack 10.0 @ Kernel 2.4.27
Posts: 63

Rep: Reputation: 15
image = /boot/vmlinuz
root = /dev/hda2
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz

I donno if this helps, but try renaming the vmlinuz file in one of the distro's
For example, in Slackware, rename it to vmlinuzSlack and make sure you update your lilo.conf

===

Which partition do you have flagged bootable? (run your shell and type cfdisk -- that will show a list of partitions of /dev/hda ... the bootable partition has a star next to it.
 
Old 01-22-2005, 10:41 AM   #3
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
don't think that helps.

before running " lilo " make sure the suse-part. is mounted.

change

image = /boot/vmlinuz

to

image = /moutpoint-of-suse/boot/vmlinuz

so lilo can find the other kernel.

egag

Last edited by egag; 01-22-2005 at 10:44 AM.
 
Old 01-22-2005, 10:53 AM   #4
xgreen
Member
 
Registered: Aug 2003
Distribution: Slackware,Arch
Posts: 389

Original Poster
Rep: Reputation: 30
MBH suggestion does not work.... (tq anyway)

egag, i've done your suggestion but with no luck....it is ok when running lilo but after booting kernel panic message appearred & complaining hdb root was not found..

this is my last lilo.conf

image = /boot/vmlinuz
root = /dev/hda2
label = Slackware
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /mnt/suse/boot/vmlinuz-2.6.4-52-default
root = /dev/hdb1
label = SuSE
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/hda1
label = Windows
table = /dev/hda
# Windows bootable partition config ends
 
Old 01-22-2005, 10:54 AM   #5
xgreen
Member
 
Registered: Aug 2003
Distribution: Slackware,Arch
Posts: 389

Original Poster
Rep: Reputation: 30
or should i go for grub ???
 
Old 01-22-2005, 11:08 AM   #6
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
well...i think your lilo-prob is solved ( if hdb1 is your root part. for suse ? )
but maybe suse uses an " initrd " to boot ?

if so , i think you have to add that in the lilo.conf ?

edit : add such a line for initrd-use :

initrd = /mnt/suse/boot/initrd.gz



egag

Last edited by egag; 01-22-2005 at 11:13 AM.
 
Old 01-22-2005, 11:13 AM   #7
xgreen
Member
 
Registered: Aug 2003
Distribution: Slackware,Arch
Posts: 389

Original Poster
Rep: Reputation: 30
"but maybe suse uses an " initrd " to boot ?"

can you explain more....
 
Old 01-22-2005, 11:17 AM   #8
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
look in the suse /boot/ -dir. if there's a file named " initrd........ "
if so, add a line like :

initrd = /mnt/suse/boot/initrd........

in the suse part of lilo.conf.

then rerun lilo.

egag

Last edited by egag; 01-22-2005 at 11:22 AM.
 
Old 01-22-2005, 11:24 AM   #9
xgreen
Member
 
Registered: Aug 2003
Distribution: Slackware,Arch
Posts: 389

Original Poster
Rep: Reputation: 30
i've edit my lilo.conf as below

image = /mnt/suse/boot/initrd
root = /dev/hdb1
label = SuSE
read-only # Non-UMSDOS filesystems should be mounted read-only for checking

and i got this when rerun lilo

Added Slackware *
Fatal: Setup length exceeds 31 maximum; kernel setup will overwrite boot loader
 
Old 01-22-2005, 11:33 AM   #10
egag
Senior Member
 
Registered: Jul 2004
Location: Netherlands
Distribution: Slackware
Posts: 2,721

Rep: Reputation: 53
sorry for being not to clear....

# Linux bootable partition config begins
image = /mnt/suse/boot/vmlinuz-2.6.4-52-default
root = /dev/hdb1
label = SuSE
initrd = /mnt/suse/boot/initrd........
read-only # Non-UMSDOS filesystems should be mounted read-only for checking
# Linux bootable partition config ends

note that the " initrd...... " should match the file in the suse /boot/ dir.

egag

Last edited by egag; 01-22-2005 at 12:09 PM.
 
Old 01-22-2005, 11:42 AM   #11
xgreen
Member
 
Registered: Aug 2003
Distribution: Slackware,Arch
Posts: 389

Original Poster
Rep: Reputation: 30
ok my problem solved...
tq very much....
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Switching from grub to lilo, messed up Lilo.conf, rescuing via Knoppix. SonicGT Debian 2 08-21-2005 01:15 PM
Upgraded kernel, lilo.conf, didn't run /sbin/lilo dtashima Linux - Newbie 4 10-18-2004 11:21 AM
Lilo lost, Install disk failing to restore Lilo on dual boot? Dobie Linux - Newbie 2 05-05-2004 05:00 PM
new kernel causes lilo crash; /sbin/lilo = Warning: device 0x0305 exceeds 1024 cylind dandysf Linux - Software 0 08-26-2003 04:50 PM
Made a bootdisk with RedHat 7.1 to boot: Gave me SYSLINUX, not LILO:Want to use LILO Colonel Panic Linux - Software 0 08-17-2001 06:21 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:52 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration