Hello, I am so surpried that you just have the same problem with me (and obviously Fedora Core 3, of course). I found the same post as you just provided yesterday and updated my udev too. The problem still exists. then I build a initrd via make modules, make ...blah blah, as you guess, it works. the udev seems to control the /dev/files creating and destructing and it needs the initrd to make it works properly in Fedora Core 3. I test the same kernel config and image file on RH 9 without the initrd, it boots well. PS: debian works too. P.F. Tsai ----- Original Message ----- From: "A" <ahmedcali@xxxxxxxxx> To: <kernelnewbies@xxxxxxxxxxxx> Sent: Friday, March 25, 2005 12:34 PM Subject: Re: Getting a Kernel panic while booting kernel.. > Hi, > > Thank you. Using the kernel option root=/dev/hda5 > worked. The bootup progresses further. However, > after a while the kernel freezes.... > > VFS: Mounted root (ext3 filesystem) readonly > Freeing unused kernel memory: 140K > Warning: unable to open an initial console > SELinux: Disabled at runtime > SELinux: Unregistering netfilter hooks. > > After some googling, I noticed some info on this error > at > http://www.issociate.de/board/goto/560509/Kernel_2.6.10_Can't_Open_Initial_Console_on_FC3.html#msg_560509 > > My question is, how can I tell if the devices in my > machine are managed by udev? And, do I "really" need > an initrd file? What is the connection between udev > and initrd? > > In my .config file, the following is stated: > CONFIG_BLK_DEV_INITRD=y > > Does this mean that the kernel absolutely needs an > initrd file, and if it cannnot find one, it will barf? > Can I just unset the above? > > Thank you, > Aha > > > > > > Thank you, > Aha. > > --- William J Beksi <wjbeksi@xxxxxxxxxxx> wrote: > > A wrote: > > > Hello, > > > > > > I have EXT3 built into the kernl. My grub file > > > section for this kernel looks as follows: > > > > > > title 2.6.9-prep > > > root (hd0,4) > > > kernel /boot/vmlinuz-2.6.9-prep ro > > > root=hda4 > > > > > > I have tried a few combination of root=hda4, > > > root=hda5, root=(hd0,4). All gives me the same > > error > > > msg as follows: > > > > > > VFS: Cannot open root device "hda4" or > > > unknown-block(0,0) > > > Please append a correct "root=" boot option > > > Kernel panic - not syncing: VFS: Unable to mount > > root > > > fs on unknown-block(0,0) > > Try using the full path name, i.e. /dev/hda4 > > > > -- > > William J Beksi > > <wjbeksi@xxxxxxxxxxxxxxxxxxxxx> > > GPG Key Fingerprint = ED4B 32C3 69E6 C2B7 705C 263F > > CB2F 3253 E7E1 DB3B > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Small Business - Try our new resources site! > http://smallbusiness.yahoo.com/resources/ > > -- > Kernelnewbies: Help each other learn about the Linux kernel. > Archive: http://mail.nl.linux.org/kernelnewbies/ > FAQ: http://kernelnewbies.org/faq/ > -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
