LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - General
User Name
Password
Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices


Reply
  Search this Thread
Old 06-20-2003, 10:37 AM   #1
jkobrien
Member
 
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slackware, LFS, Ubuntu, RedHat, Slamd64
Posts: 507

Rep: Reputation: 30
root=805


Hi

I'm trying to compile the kernel but no matter what I try the reboot freezes at the following messages...

kmod: failed to exec /sbin/modprobe -s -k block-major-8, errno = 2
VFS: Cannot open root device "805" or 08:05
Please append a correct "root=" boot option
kernel panic: VFS: unable to mount root fs on 08:05

Having read around a bit, I think this means that I have to change the "root = /dev/sda5" line in /etc/lilo.conf

My question is: to what?

I have four scsi disks and an Integrated Ultra 320/M RAID 0 controller. On my MS-Win partition this has the affect of making all the disks appear as one and apparently does the same for linux.

When I installed linux (slack 9) I had to use the raid.s boot option and had to use fdisk /dev/ida/c0d0. (This was by a process of elimination rather than any deep technical knowledge on my part.) The installation went fine, though there are some configuration problems which is why I want to recompile.

I've tried changing the root= to various things (including /dev/ida/c0d0) but all that does is change the 805 code above to some other number. Also when I boot with the original vmlinuz, root=/dev/sda5 seems to cause no problem at all.

fdisk -l gives this...

Disk /dev/sda: 145.4 GB, 145450074112 bytes
255 heads, 63 sectors/track, 17683 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/sda1 1 6 48163+ de Dell Utility
/dev/sda2 * 7 8628 69256215 c Win95 FAT32 (LBA)
/dev/sda3 8890 17683 70637805 5 Extended
/dev/sda4 8629 8889 2096482+ 82 Linux swap
/dev/sda5 8890 9498 4891761 83 Linux
/dev/sda6 9499 17683 65745981 83 Linux

Partition table entries are not in disk order

What should I set the root= parameter to? Or am I completely on the wrong track?

Thanks in advance,

John
 
Old 06-20-2003, 01:14 PM   #2
mikeyt_333
Member
 
Registered: Jun 2001
Location: Up in the clouds
Distribution: Fedora et al.
Posts: 353

Rep: Reputation: 30
is there already a root parameter in your lilo.conf? And if so is it what you wrote:

root = /dev/sda5

If it is that, then try this:

root=/dev/sda5

You can't have spaces when assigning that.

HTH, if not post back, with a list of your partitions from fdisk, and your current lilo.conf.

Mike.
 
Old 06-23-2003, 05:14 AM   #3
jkobrien
Member
 
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slackware, LFS, Ubuntu, RedHat, Slamd64
Posts: 507

Original Poster
Rep: Reputation: 30
Hi Mike, many thanks for the reply, but no joy, I'm afraid.

I did have spaces around the = sign but I've removed them now and it made no difference.

The fdisk information is in my original post, my lilo.conf is below.

I'd be grateful for any other ideas, I'm really stumped! Does it matter that / is mounted on a logical partition?

Thanks again,

John

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
lba32
boot = /dev/sda
message = /boot/boot_message.txt
prompt
#timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
reset
# Normal VGA console
vga = normal
# End LILO global section
# DOS bootable partition config begins
other=/dev/sda2
label=DOS
table=/dev/sda
# DOS bootable partition config ends
# Linux bootable partition config begins
image=/boot/vmlinuz
root=/dev/sda5
label=Linux
read-only
image=/boot/vmlinuz.orig
root=/dev/sda5
label=Linux_orig
read-only
# Linux bootable partition config ends
 
Old 07-04-2003, 09:21 AM   #4
jkobrien
Member
 
Registered: Jun 2003
Location: Dublin, Ireland
Distribution: Slackware, LFS, Ubuntu, RedHat, Slamd64
Posts: 507

Original Poster
Rep: Reputation: 30
Hi,

So 50 reads and only one reply tells me that I'm not the only one stumped. I figure either I'm doing something wrong with the kernel compile or this is a bug of some sort, which leads me to two new questions...

I compile using the instructions in the Slackware Linux Essentials book, so I don't think I'm doing anything procedurally wrong, all I can think is that I'm including or omitting some module that is causing the problem. I've tried leaving out some modules that seemed likely to me but get the same result each time and there's too many of them to work through them all (I have to get some work done inbetween compiles :->).

So the question is, how can I compare the configuration from the working kernel with any of my compiled kernels and will this help me narrow down what is causing the problem? Obviously I have the .config file from the latter, but I presume the original .config from when I installed the source package is just a set of typical defaults and doesn't have anything to do with the kernel that I installed with? (Remembering that I installed with raid.s).

The second question is, could this be a bug, and if so how do I report it? I can't see anything at the slackware webpage.

Thanks,

John
 
Old 07-04-2003, 01:42 PM   #5
camelrider
Member
 
Registered: Apr 2003
Location: Juneau, Alaska
Posts: 251

Rep: Reputation: 32
You could compare the config files generated by "make menuconfig" or "make xconfig" for each kernel version.

Have you tried putting the config file from your old kernel in the directory with your new kernel's source and running "make oldconfig"? This will cause the same options to be chosen as were in your old kernel and then allow you to choose options that have been added to the new kernel source.
 
  


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 On
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
RHEL3 Mounting USB after reboot and between reboots: root and non-root users Luis Nunes Linux - Hardware 0 07-20-2005 08:32 AM
IntelliMouse thumb buttons work as root, broken as non-root user, wheel works always digital vortex Linux - Hardware 7 03-02-2004 04:14 PM
root files: create as root:root or root:wheel? pcass Linux - Security 1 02-07-2004 04:14 PM
cant resize root thru rescue, auto mounts root dir absolutal Linux - Newbie 0 06-18-2003 03:06 PM
Why does kppp.desktop require root userid for non-root user? rdaves@earthlink.net Linux - Networking 4 08-27-2001 09:18 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - General

All times are GMT -5. The time now is 04:27 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