All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Hancock <hancockr@shaw.ca>
To: clemens@dwf.com
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Still cant boot 2.6.20
Date: Sun, 11 Feb 2007 01:23:00 -0600	[thread overview]
Message-ID: <45CEC454.9020705@shaw.ca> (raw)
In-Reply-To: <fa.lMccRNOAss6zgWj6JUPSrPO11PY@ifi.uio.no>

clemens@dwf.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@48000000 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@nospamshaw.ca
Home Page: http://www.roberthancock.com/


       reply	other threads:[~2007-02-11  7:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.lMccRNOAss6zgWj6JUPSrPO11PY@ifi.uio.no>
2007-02-11  7:23 ` Robert Hancock [this message]
2007-02-11  6:20 Still cant boot 2.6.20 clemens
2007-02-11  7:02 ` lkml
2007-02-11  7:12   ` Randy Dunlap
2007-02-11  7:37     ` lkml
2007-02-11  8:37       ` Willy Tarreau
2007-02-11 17:16         ` Randy Dunlap

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45CEC454.9020705@shaw.ca \
    --to=hancockr@shaw.ca \
    --cc=clemens@dwf.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.