Arch Linux

intrinsic

Member

Registered: 2004-03-16

Posts: 21

Custom built kernel 2.6.8

i am upgrading from a custom built 2.6.7 to a custom built 2.6.8 and having problems.
first i notice the kernel is now seeing my SATA drive as /dev/sda, before it was /dev/hde and now the devfs name is /dev/scsi/host0/... as opposed to /dev/ide/host0/...
this name change i believe is the source of the problem because now i am getting:
vfs: cannot open root device
please append a correct "root=" boot option
kenel panic: vfs: unable to mount root fs on unknown-block
my lilo.conf uses the standard boot=/dev/discs/disc0/disc and root=/dev/discs/disc0/part3.

any ideas?

hypermegachi

Member

Registered: 2004-07-25

Posts: 311

Re: Custom built kernel 2.6.8

change your lilo entry

kakabaratruskia

Member

From: Santiago, Chile

Registered: 2003-08-24

Posts: 596

Re: Custom built kernel 2.6.8

I've never been able to compile my own kernel in this PC, with the same problem (also a SATA drive). I've tryed every possible entry for lilo. If you find out what's wrong, please post it.

---

And where were all the sportsmen who always pulled you though?
They're all resting down in Cornwall
writing up their memoirs for a paper-back edition
of the Boy Scout Manual.

hypermegachi

Member

Registered: 2004-07-25

Posts: 311

Re: Custom built kernel 2.6.8

i ran into problems when i upgraded to udev.
just make sure your lilo/grub config files are consistent with the new location of the partition.  fstab should be updated also.

intrinsic

Member

Registered: 2004-03-16

Posts: 21

Re: Custom built kernel 2.6.8

i hear that but how do i change lilo when the /dev entries don't show up unless i boot using said kernel?
when i boot using the 2.6.7 kernel and try to change lilo it gives me an error saying no such device.
will i have to make a boot disk using the same 2.6.8 custom kernel so i can pass "root=" option to it or is there an easier way.

hypermegachi

Member

Registered: 2004-07-25

Posts: 311

Re: Custom built kernel 2.6.8

try grub instead.
all you have to do is edit the grub config file at /boot/grub/menu.lst

the advantages are you don't need to run "lilo" every time you upgrade a kernel.  grub just looks in menu.lst for any kernel.

anywho, the biggest advantage is the ability to edit boot entries before you boot.  so if you get the wrong 'root' you can change it on the fly.

if you're intent on stickin with lilo, then try using a bootdisk.  boot into the new kernel and change everything soit works.

intrinsic

Member

Registered: 2004-03-16

Posts: 21

Re: Custom built kernel 2.6.8

thanks! it worked like a charm.
grub has always been foreign to me it seems i've been living in the dark ages all this time.

aminalshmu

Member

From: Tallahassee, FL, USA

Registered: 2004-08-14

Posts: 5

Re: Custom built kernel 2.6.8

i've been having this problem today also... and i'm confused (linux newbie as of about 2 weeks ago).

i have an SATA drive and am recompiling kernel 2.6.8rc4 (whoops, just checked kernel.org... guess i can use the new 2.6.8.1 sources now) because i'm the kind of person that has to have the most up to date everything, as it looks like most of the arch community is. also i need support for my netgear ma101b wireless adapter which is proving to be a pain...

anyways, i get the kernel panic message when i boot my recompiled kernel... apparently because it mounts the SATA drive in a different location than in the previous kernel, i guess. but what do i change the root= option in grub to? and what do i need to update in fstab?

thanks in advance,
jordan

update:

i compiled with new kernel sources and changed grub's root= for the new kernel to /dev/hdc3 which was what i saw the system detecting the hard drive as when loading the new kernel. now it hangs at "warning: unable to open an initial console."

help?

update 2:

read through arch install guide and found that i needed to enable devfs support in the kernel... whoops. fixed. now if i can only get my atmel driver to install for my netgear wireless adapter...

---

sigs are for l4m3rs

wintermute

Member

Registered: 2004-03-23

Posts: 21

Re: Custom built kernel 2.6.8

My network stopped working after I compiled 2.6.8.1!

I don't know enough about kernel internals so I switched back to 2.6.7.

---

"I propose we leave math to the machines and go play outside." -- Calvin

xerxes2

Member

From: Malmoe, Sweden

Registered: 2004-04-23

Posts: 1,249

Website

Re: Custom built kernel 2.6.8

i just compiled it and it works for me

first time I enabled athlon config, it boots a few seconds faster.....

---

arch + gentoo + initng + python = enlisy

tranquility

Member

From: Portugal

Registered: 2004-08-06

Posts: 136

Re: Custom built kernel 2.6.8

thanks! it worked like a charm.
grub has always been foreign to me it seems i've been living in the dark ages all this time.

Could you post the changes you made? I just installed the stock 2.6.8 and I get the same VFS no root error. I was usign root=/dev/discs/disc0/part5.
What do I need to change? I already searched for udev naming conventions for the new scsi emulation, but found nothing 

dp

Member

From: Zürich, Switzerland

Registered: 2003-05-27

Posts: 3,378

Website

Re: Custom built kernel 2.6.8

My network stopped working after I compiled 2.6.8.1!

I don't know enough about kernel internals so I switched back to 2.6.7.

what nic driver do you use?

---

The impossible missions are the only ones which succeed.

intrinsic

Member

Registered: 2004-03-16

Posts: 21

Re: Custom built kernel 2.6.8

Could you post the changes you made? I just installed the stock 2.6.8 and I get the same VFS no root error. I was usign root=/dev/discs/disc0/part5.
What do I need to change? I already searched for udev naming conventions for the new scsi emulation, but found nothing 

mine is root=/dev/scsi/host0/bus0/target0/lun0/part3

tranquility

Member

From: Portugal

Registered: 2004-08-06

Posts: 136

Re: Custom built kernel 2.6.8

Could you post the changes you made? I just installed the stock 2.6.8 and I get the same VFS no root error. I was usign root=/dev/discs/disc0/part5.
What do I need to change? I already searched for udev naming conventions for the new scsi emulation, but found nothing 

mine is root=/dev/scsi/host0/bus0/target0/lun0/part3

Thanks, but I already tried that . As much as I could see my SATA controller was not being recognised at all. Meanwhile I have the problem solved with the help of my trustworthy archlinux cd Thanks for your input