linux-kernel - Re: Still cant boot 2.6.20

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-id: <45CEC454.9020705@shaw.ca>
Date:	Sun, 11 Feb 2007 01:23:00 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	clemens@....com
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Still cant boot 2.6.20

clemens@....com wrote:
> I have built a number of previous kernels, but am having problems with
> 2.6.20.
> 
> I initially  tried just changing only the Processor type (so what I had done 
> would be easy to describe). Someone on this list was kind enough to tell
> me that the SATA/PATA drivers were not on by default, and I got past 
> that problem.
> 
> As a second attempt (well 3rd or 4th) I have done a normal config, trying to
> delete as many things as possible to speed up the compile time.
> 
> I have now got by the dreaded /dev/root error I had with no drivers, but have
> a new problem.  The boot looks like this (typed from my notes, so probably
> not exact)
> 
> ---
> 
>   Booting 'Fedora Core (2.6.20)'
> 
> root (hd1,6)
>  Filesystem type is ext2fs, partition type 0x83
> Kernel /boot/vmlinuz-2.6.20 ro root=/dev/sda7 rhgb quiet
>    [Linux-bzImage, setup=0x1e00, size=0x186210]
> initrd /boot/initrd-2.6.20.img
>    [Linux-initrd @ 0x37e93000, 0x151c52 bytes]
> 
> Uncompress ...
> PCI BiosBug: MCFG area @f000000 not E820-reserved
> PCI Not using MMCONFG
> PCI Failed to allocate mem resource #6: 20000@...00000 for 0000:01:00.0
> audit cannot initalize inotify handle
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> <and its dead>

Take the "quiet" option off the kernel command line (in /etc/grub.conf) 
so you can actually see all the messages that are being output. 
Presumably you haven't selected something that you need in order to 
mount the root filesystem..

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@...pamshaw.ca
Home Page: http://www.roberthancock.com/

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/