From: "GlupFire" <porranenhuma@globo.com>
To: <linux-kernel@vger.kernel.org>
Subject: Kernel Panic: VFS cannot open a root device
Date: Sat, 16 Jul 2005 05:41:10 -0300 [thread overview]
Message-ID: <009b01c589e2$1e96f130$3dfea8c0@glupfire> (raw)
Hi , i have kernel 2.4.29 at slack 10.1 and when I upgrade my kernel to
2.6.11 I get these erros on booting
VFS: Cannot open a root device "301" or unknow block
please append a correct "root" boot option
KERNEL PANIC : not syncing; VFS; Unable to mount root fs on unknown-block
(3,1)
I have compiled my kernel with my IDE support and also with my file system
support with built-in option.
My LILO.CONF
image = /boot/vmlinuz-2.6.11
root = /dev/hda1
label = 2.6.11
initrd = /boot/initrd.gz
read-only
I googled this problem, and I think is a kind of bug, and i tryed to patch
the kernel with Alan Cox patch 2.6.11-ac7.bzip and I get these ::
bzip2 -dc /usr/src/patch-2.6.11.ac7.bzip | patch -p1 -s
1 out of hunk FAILED --saving rejects to file Makefike.rej
and I cat the file Makefile.rej
***************
*** 1,8 ****
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 11
- EXTRAVERSION =
- NAME=Woozy Numbat
# *DOCUMENTATION*
# To see a list of typical targets execute "make help"
--- 1,8 ----
VERSION = 2
PATCHLEVEL = 6
SUBLEVEL = 11
+ EXTRAVERSION = ac7
+ NAME=AC
# *DOCUMENTATION*
# To see a list of typical targets execute "make help"
I'm stuck! The patch dont work fine ( I think the patch is not installed
succesfully on my kernel )
I'm booting with my image of kernel 2.4.29..... i'm 5 days tryng to solve
this problem ...
any kind of help is wellcome... sorry for my english.
next reply other threads:[~2005-07-16 8:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 8:41 GlupFire [this message]
2005-07-16 20:57 GlupFire
[not found] <200507171016.37940.norbert@edusupport.nl>
2005-07-18 0:27 ` porranenhuma
2005-07-18 2:46 ` Fawad Lateef
2005-07-18 11:14 ` Ed Tomlinson
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='009b01c589e2$1e96f130$3dfea8c0@glupfire' \
--to=porranenhuma@globo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®