LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 05-28-2007, 08:33 PM   #1
ghostrider.002
LQ Newbie
 
Registered: May 2007
Posts: 21

Rep: Reputation: 15
Multi-Boot install, Kernel panic, Lilo problem


Hell once again
I have 2 problems

I have a Tri-boot setup. hda = Windows, hdb = opensuse, sda = slackware 11
boot loader = Lilo
previously I had just a dual boot with windows and suse, i added a Sata hdd and installed slackware and after i installed it i rebooted and i have the following errors.

1. I rebooted after a fresh install on a sata hdd and it states:
kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device "801" or "08:01
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 08:01


2. When Lilo menu comes up it only lists 2 boot options:
1. Windows
2. Linux



Now I am going to remove suse but i still have a little more data on it.
Should I just disconnect the Sata (Slack) hdd and boot suse and finish there then remove that drive and reattach the Sata (Slack) hdd and reboot?

Thanks
 
Old 05-28-2007, 08:43 PM   #2
thloh85
Member
 
Registered: Apr 2006
Location: Earth
Distribution: BLFS customized
Posts: 160

Rep: Reputation: 31
I don't really understand your question 1.
For question 2, you can always add a boot option for your unix(linux).
Just put in the title, root, etc. in your /boot/grub/menu.lst(might be different for you, look for the menu.lst file, its the GRUB bootloader configuration file) and you're ready to go... Google for it if you don't know how...
 
Old 05-28-2007, 08:55 PM   #3
ghostrider.002
LQ Newbie
 
Registered: May 2007
Posts: 21

Original Poster
Rep: Reputation: 15
I should have the two questions reversed.

For the Lilo problem I thought that I would have 3 entries in the Lilo boot menu, (windows, suse, slack) but it only has 2 entries. And I just wondered why i didnt, normally it would auto detect all OS's. the install detected them but i dont think Lilo did. I was running grub but slack installs lilo. I also installed Lilo in the MBR (option 3 of the installer).

As for the errors, i get then after i select the Linux boot option, I believe it is called verbose mode when everything scrolls up on the screen as Linux is booting. it posted the last 4 lines then it goes into kernel panic and locks up the pc.
 
Old 05-28-2007, 08:59 PM   #4
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
Which kernel are you using ? and which filesystem ?

You'll probably have to edit '/etc/lilo.conf' manually and add opensuse, then run 'lilo'.

You could also use a live CD, as I hear you'll soon get rid of opensuse anyway, no need to bother getting it to boot this way.
 
Old 05-28-2007, 09:38 PM   #5
ghostrider.002
LQ Newbie
 
Registered: May 2007
Posts: 21

Original Poster
Rep: Reputation: 15
Yes I am getting rid of suse. As a matter of fact I disconnected the suse drive all together.

I have hda = windows
sda = slack


upon rebooting after disconnecting the suse hdd, i still get the 4 errors/panic listed in the first post.

as for the kernel i used test26.s to install with. but if i boot into the slack live cd what command can i use to verify this with?

File system is type ext3, if i remember correctly when i ran cfdisk i choose 83.

Should I just reinstall? I rather not have to if at all possible.

Last edited by ghostrider.002; 05-28-2007 at 09:41 PM.
 
Old 05-28-2007, 09:49 PM   #6
H_TeXMeX_H
Guru
 
Registered: Oct 2005
Location: $RANDOM
Distribution: slackware64
Posts: 12,928
Blog Entries: 2

Rep: Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269Reputation: 1269
It might be something wrong in lilo.conf ... I mean:

"hda = Windows, hdb = opensuse, sda = slackware 11"

Maybe the one for slackware says hda instead of sda ?

You could use a live cd, go in there and make sure it is right, then chroot into there and run '/sbin/lilo'.
 
Old 05-28-2007, 09:53 PM   #7
ghostrider.002
LQ Newbie
 
Registered: May 2007
Posts: 21

Original Poster
Rep: Reputation: 15
ok, I am going to try the live cd route and post back.\

Thanks
 
Old 05-29-2007, 01:01 AM   #8
ghostrider.002
LQ Newbie
 
Registered: May 2007
Posts: 21

Original Poster
Rep: Reputation: 15
Fixed. unfortuniatly I did a reinstall and it works. Thanks for the help
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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
kernel panic boot problem tshontikidis Linux - General 6 09-05-2005 03:56 PM
Kernel panic on Debian multi-boot coldsalmon Debian 5 06-06-2005 07:13 AM
newbie boot problem- kernel panic nekid Linux - General 4 05-04-2004 12:55 PM
LILO-related Kernel Panic on Boot sarboras Slackware - Installation 7 04-28-2004 04:28 PM
Lilo / Kernel Panic problem oulevon Linux - General 1 11-20-2002 08:53 AM


All times are GMT -5. The time now is 04:24 AM.

Main Menu
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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration