All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex <alex@meerkatsoft.com>
To: linux-kernel@vger.kernel.org
Subject: Cannot boot after new Kernel Build
Date: Sat, 10 Jan 2004 17:21:32 +0900	[thread overview]
Message-ID: <3FFFB60C.9010309@meerkatsoft.com> (raw)

Hi,
I am trying to build a new kernel but what ever version 2.4.24, 2.6.0,
2.6.1 i am trying to build I come across the same problem.

when doing a "make install" i get the following error.

/dev/mapper/control: open failed: No such file or directlry
Is device-mapper driver missing from kernel?
Comman failed.

I have installed the lates packages
device mapper 1.00.07
initscripts 7.28.1
modutils, lvm2.2.00.08
mkinitrd-3.5.15.1-2

If I just ignore the message and try to boot the machine with the new
kernel then I get a Kernel Panic.

VFS: Cannot open root device "LABEL=/" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic: VFS: Unapble to mount root fs on unknown-block(0,0).

The boot command in grub is
root (hd0,0)
kernel /vmlinuz-2.6.1 ro root=LABEL=/ hdc=ide-scsi
initrd /initrd-2.6.1.img

It is basically the same (except the version) as I use for 2.4.20-28 so
I assume the label is correct.

I saw quite a few messages of similar type but no real answer to the
problem. Any Ideas what it could be ?  I am using RH9.0

Thanks
Alex







             reply	other threads:[~2004-01-10  8:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-10  8:21 Alex [this message]
2004-01-10  9:37 ` Cannot boot after new Kernel Build Bongani Hlope
2004-01-10 15:08 ` Christian Kivalo
2004-01-10 15:43   ` Alex
2004-01-10 16:10     ` Christian Kivalo
2004-01-10 16:19       ` Alex
2004-01-11  5:34 ` Joseph Fannin
2004-01-11  6:04   ` Kernel 2.4.20 RH Cannot set DMA Alex
  -- strict thread matches above, loose matches on Subject: below --
2004-01-11  3:33 Cannot boot after new Kernel Build Zhu, Yi

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=3FFFB60C.9010309@meerkatsoft.com \
    --to=alex@meerkatsoft.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.