public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hulin Thibaud <hulin.thibaud@wanadoo.fr>
To: linux-kernel@vger.kernel.org
Subject: kernel panic - not syncing: VFS - unable to mount root fs on unknown-block
Date: Mon, 14 Aug 2006 03:17:20 +0200	[thread overview]
Message-ID: <44DFCF20.9030202@wanadoo.fr> (raw)

Hello !
I'm trying to compile my own kernel for drivers on two computers, but 
that fails. A the boot, I have this error :
kernel panic - not syncing: VFS Unable to mount root fs on unknow-block 
(3.69)

I'm using the kernel 2.6.19 with Ubuntu Dapper. I use the old boot 
config and I type make oldconfig, so I don't understand why there are an 
error with the near same configuration.
I suppose that I must compile not in module but in hard support for my 
IDE chipset, harddisk and file system. Probably, I don't understand how 
do exactly. I do that :
lspci |grep IDE
0000:00:11.1 IDE interface: VIA Technologies, Inc. 
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
make xconfig
-Device Drivers
--* ATA/ATAPI/MFM/RLL support
--- * Enhanced IDE/MFM/RLL disk/cdrom/tape/floppy support
--- * Include IDE/ATA-2 DISK support
--- * PCI IDE chipset support
---- * Generic PCI IDE Support
----- * VIA82CXXX chipset support
- File systems
-- * Ext3 journalling file system support
--- * Ext3 extended attributes
---- * Ext3 POSIX Access Control Lists
---- * Ext3 Security Labels

Have I forgot anything ?

Thanks very much,
Thibaud.

             reply	other threads:[~2006-08-14  1:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14  1:17 Hulin Thibaud [this message]
2006-08-14  1:33 ` kernel panic - not syncing: VFS - unable to mount root fs on unknown-block Nick Manley
2006-08-14 13:32 ` Jiri Slaby
2006-08-14 14:44   ` Hulin Thibaud
2006-08-14 14:52     ` Jiri Slaby
2006-08-14 14:52     ` Reinaldo Carvalho
2006-08-14 19:46       ` Jiri Slaby
2006-08-14 18:06     ` Phillip Susi
2006-08-14 21:15     ` Hulin Thibaud
2006-08-14 21:35       ` Jiri Slaby

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=44DFCF20.9030202@wanadoo.fr \
    --to=hulin.thibaud@wanadoo.fr \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox