1:56 a.m.
Hello,
I'm trying to compile the 2.6.1 kernel on Cedora Core 1. I've downloaded
the source from kernel.org, and try to follow the readme for installing.
a did make menuconfig, select the things I need (ex3 extended
attributes and posix ACL among them), then make, make bzImage, make
modules make modules_install, make install.
Before make install I've loaded the loop kernel module.
When I try to boot the new kernel it hangs with the folloving error:
VFS: cannot open root device "LABEL=/" or unknown-block (0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: unable to mount root fs on unknown-block (0,0)
I did try to specify root=0803 in grub.conf but the message now is: VFS:
cannot open root device "0803" or unknown-block (8,3)
Please append a correct "root=" boot option
Kernel panic: VFS: unable to mount root fs on unknown-block (8,3)
What can be done?
thank you,
Laszlo
2:10 a.m.
On Fri, 2004-02-06 at 09:56 +0200, Budai Laszlo wrote:
Hello,
I'm trying to compile the 2.6.1 kernel on Cedora Core 1. I've downloaded
the source from kernel.org, and try to follow the readme for installing
6:10 a.m.
On Fri, 2004-02-06 at 02:56, Budai Laszlo wrote:
Hello,
I'm trying to compile the 2.6.1 kernel on Cedora Core 1. I've downloaded
the source from kernel.org, and try to follow the readme for installing.
a did make menuconfig, select the things I need (ex3 extended
attributes and posix ACL among them), then make, make bzImage, make
modules make modules_install, make install.
Before make install I've loaded the loop kernel module.
When I try to boot the new kernel it hangs with the folloving error:
VFS: cannot open root device "LABEL=/" or unknown-block (0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: unable to mount root fs on unknown-block (0,0)
I did try to specify root=0803 in grub.conf but the message now is: VFS:
cannot open root device "0803" or unknown-block (8,3)
Please append a correct "root=" boot option
Kernel panic: VFS: unable to mount root fs on unknown-block (8,3)
What can be done?
thank you,
Laszlo
In grub.conf, try changing LABEL=/ to the real device name (e.g.
/dev/hda1) of your / partition. Something like:
kernel /vmlinuz-2.6.2 ro root=/dev/hda1
However labels work okay for me with the 2.6.2 kernel.
Bob...
6:20 a.m.
In grub.conf, try changing LABEL=/ to the real device name (e.g.
/dev/hda1) of your / partition. Something like:
kernel /vmlinuz-2.6.2 ro root=/dev/hda1
However labels work okay for me with the 2.6.2 kernel.
Bob...
I did try:
kernel /vmlinuz-2.6.1 ro root=/dev/sda3
but still the same ... :(
I don't know maybe something else is wrong. I keep digging.
Laszlo
6:50 a.m.
Em Sex, 2004-02-06 às 09:20, Budai Laszlo escreveu:
I did try:
kernel /vmlinuz-2.6.1 ro root=/dev/sda3
but still the same ... :(
I don't know maybe something else is wrong. I keep digging.
My one just got working if I put this:
title Fedora Core (2.4.22-1.2140.nptl)
root (hd0,0)
kernel /vmlinuz-2.4.22-1.2140.nptl ro root=/dev/hda2
hdc=ide-scsi rhgb vga=791
initrd /initrd-2.4.22-1.2140.nptl.img
title Fedora Core (2.6.1-1.126)
root (hd0,0)
kernel /vmlinuz-2.6.1-1.126 ro root=/dev/hda2 hdc=ide-scsi rhgb
vga=791
initrd /initrd-2.6.1-1.126.img
--
[]s
Alexandre Ganso
500 FOUR vermelha - Diretor Steel Goose Moto Group
6:49 a.m.
Em Sex, 2004-02-06 às 09:10, Bob Chiodini escreveu:
> VFS: cannot open root device "LABEL=/" or
unknown-block (0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: unable to mount root fs on unknown-block (0,0)
> I did try to specify root=0803 in grub.conf but the message now is: VFS:
> cannot open root device "0803" or unknown-block (8,3)
> Please append a correct "root=" boot option
> Kernel panic: VFS: unable to mount root fs on unknown-block (8,3)
>
> What can be done?
In grub.conf, try changing LABEL=/ to the real device name (e.g.
/dev/hda1) of your / partition. Something like:
kernel /vmlinuz-2.6.2 ro root=/dev/hda1
However labels work okay for me with the 2.6.2 kernel.
This was posted at fedora-users some time ago by me. Not 2.6-related,
here it happens with ANY kernel. souns more like mkinitrd stuff
--
[]s
Alexandre Ganso
500 FOUR vermelha - Diretor Steel Goose Moto Group
6:28 a.m.
I'm not clear on whether you have things built into the kernel or built
as modules. However recently when I have seen that sort of problem its
often been down to a broken mkinitrd. It might be worth checking you
have a recent version.
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham(a)InTechnology.co.uk ]
[ - Comments in this message are my own and not ITO opinion/policy - ]
6:43 a.m.
Nigel Metheringham wrote:
I'm not clear on whether you have things built into the kernel or
built
as modules. However recently when I have seen that sort of problem its
often been down to a broken mkinitrd. It might be worth checking you
have a recent version.
Nigel.
I have:
mkinitrd: version 3.5.14
Laszlo
6:44 a.m.
On Fri, Feb 06, 2004 at 09:56:12AM +0200, Budai Laszlo wrote:
Hello,
I'm trying to compile the 2.6.1 kernel on Cedora Core 1. I've downloaded
the source from kernel.org, and try to follow the readme for installing.
a did make menuconfig, select the things I need (ex3 extended
attributes and posix ACL among them), then make, make bzImage, make
modules make modules_install, make install.
Before make install I've loaded the loop kernel module.
When I try to boot the new kernel it hangs with the folloving error:
VFS: cannot open root device "LABEL=/" or unknown-block (0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: unable to mount root fs on unknown-block (0,0)
This is taking a complete stab in the dark, but by any chance does your
machine need an initrd in order to boot? Boot back into a kernel which is
working, and check out the /boot directory and see if you see a file there
of the form "initrd-<some version number>" If you don't have an
initrd for
the version of 2.6 that you compiled from kernel.org, and you didn't
compile support for all the modules you need into the kernel, you'll
probably want to create an initrd. Just run "mkinitrd" as root at a prompt
and it will return showing you an example which should help. Basically
you'll run something like this:
mkinitrd /boot/initrd-<kernel version>.img <kernel version>
- jkt
--
--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*--*
Jay Turner, QA Technical Lead jkt(a)redhat.com Red Hat, Inc.
Reality is merely an illusion, albeit a very persistent one.
- Albert Einstein
6:53 a.m.
Budai Laszlo wrote:
Hello,
I'm trying to compile the 2.6.1 kernel on Cedora Core 1. I've downloaded
the source from kernel.org, and try to follow the readme for installing.
[snip]
What can be done?
This is _completely_ off topic for this list. If you want to run 2.6,
get the rawhide rpm or wait for FC2. If you absolutely, positively want
to compile your own kernel, start with the FC config, found in the
configs/ subdir of the kernel-source rpm.
/Peter
7:39 a.m.
Peter Backlund wrote:
Budai Laszlo wrote:
> Hello,
>
> I'm trying to compile the 2.6.1 kernel on Cedora Core 1. I've
> downloaded the source from kernel.org, and try to follow the readme
> for installing.
[snip]
> What can be done?
This is _completely_ off topic for this list. If you want to run 2.6,
get the rawhide rpm or wait for FC2. If you absolutely, positively want
to compile your own kernel, start with the FC config, found in the
configs/ subdir of the kernel-source rpm.
/Peter
Sorry for being off topic. I did try to install the rawhide rpm but the
result was the same ... :(
Anyway I'll try with the kernel source rpm.
Tahnks,
Laszlo
6:25 p.m.
I hate to disagree, but I had this same problem, and it does seem
relevant to this list. When I first saw the email I said, "What is this
doing on the list?" But then when I thought about it and realized it
may be a legitimate grub/grub.conf bug, I think it does deserve some
discussion. As far as I know RedHat has historically used the
root=LABEL=/ tag for a very long time. Now I went through too much to
narrow it down to a bug report, and I don't remember all of it, but here
goes:
I used to run RH9+fedora.us, then I bought a new HD controller (promise)
and a new HD. I started using that drive as a boot drive. I set the
bios to boot it first, but it still shows up as hde. I installed RH9
and had to teach lilo.conf:
disk=/dev/hde
bios=0x80
Because grub wouldn't boot, I used lilo. Perhaps I have a weird
configuration, but I needed to do this by hand. Recently I decided to
move back to grub. I manged it by considering hde to be hd0. I'm
alright with doing all this by hand, but it may be a problem for other
people.
When I turned grub to hd0, it could find the kernel. However, the
kernel gave the same root not found message. It required changing
root=LABEL=/ to root=/dev/hde1. However, lilo.conf uses root=LABEL=/
and works fine. I modified /boot/grub/device.map to say
(fd0) /dev/fd0
(hd0) /dev/hde
(hd1) /dev/hda
(hd2) /dev/hdb
with no success. Now when I get a chance in the next couple of months I
will probably format and install from an FC2 CD. I will probably file a
bug report if the CD doesn't set up my computer to boot, and it seems
fixable. But the reason I bring this up for the list is because I think
all future kernel rpms should instead of setting in grub.conf
root=LABEL=/, it should set something like root=/dev/xxx where xxx is
something like `mount |awk '/ \/ / {print $1}'`.
Now like I said, I wish I could narrow down where the problems are.
Maybe its just a bug in grub that they could fix easily. Maybe I have
two partitions labeled /. But I just thought I'd bring this up as an
issue.
-Eric Hattemer
Peter Backlund wrote:
This is _completely_ off topic for this list. If you want to run 2.6,
get the rawhide rpm or wait for FC2. If you absolutely, positively want
to compile your own kernel, start with the FC config, found in the
configs/ subdir of the kernel-source rpm.
/Peter
7395
days inactive
7396
days old
11 comments
8 participants
participants (8)
-
Alexandre Strube -
Bob Chiodini -
Budai Laszlo -
Eric Hattemer -
Jay Turner -
Michel Alexandre Salim -
Nigel Metheringham -
Peter Backlund