mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Simen Thoresen <simentt@dolphinics.no>
Cc: devesh28@gmail.com, linux-kernel@vger.kernel.org
Subject: Re: Issues in Booting kernel 2.6.13
Date: Sat, 8 Oct 2005 12:31:31 -0700	[thread overview]
Message-ID: <20051008123131.41d85d45.rdunlap@xenotime.net> (raw)
In-Reply-To: <43481D0F.9020407@dolphinics.no>

On Sat, 08 Oct 2005 21:25:03 +0200 Simen Thoresen wrote:

> Hi Randy,
> 
> Randy.Dunlap wrote:
> > On Thu, 6 Oct 2005 10:46:37 +0530 devesh sharma wrote:
> > 
> > 
> >>Hi all,
> >>I have compiled 2.6.13 kernel on a opteron machine with 1 GB physical
> >>memory, Whole compilation gose well but at the last step
> >>make install I am getting a warning
> >>WARNING: No module mptbase found for kernel 2.6.13, continuing anyway
> >>WARNING: No module mptscsih found for kernel 2.6.13, continuing anyway
> > 
> > 
> > If you need mpt drivers, there were some changes in the
> > FUSION MPT driver options that may be causing them not to be
> > built for you as you were expecting.
> 
> I ran into this (2.6.13.3) on Friday as well, but I have not yet examined it 
> in detail.
> 
> Do you have any pointers to the relevant postings or information?

No, I just recall seeing a few other problem reports and answers about it,
and then I compared the 2.6.12 and 2.6.13 .config files following
'make defconfig'.

> I've used the 'mkinitrd' tool to generate a 'proper' initrd, and I see both 
> mptbase and mptscsih loading, but mptscsih never picks up any actual 
> controllers or disks. Thus the same problem on my system.
> 
> To me, this signifies that RHs mkinitrd is broken for this kernel, but I 
> don't know the details of why yet.

so maybe someone from Red Hat can answer/clarify.

> Yours,
> -S
> 
> 
> >>now when I boot my kernel, panic is received
> >>Booting the kernel.
> >>Red Hat nash version 4.1.18 starting
> >>mkrootdev: lable / not found
> >>mount: error 2 mounting ext3
> >>mount: error 2 mounting none
> >>switchroot: mount failed : 22
> >>umount : /initrd/dev failed : 22
> >>kernel panic - not syncing : Attempted to kill init
> >>
> >>What could be the problem?
> >>I have RHEL 4 base release already installed on which I have compiled
> >>this image.


---
~Randy

  reply	other threads:[~2005-10-08 19:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-06  5:16 devesh sharma
2005-10-07  2:08 ` Randy.Dunlap
2005-10-08 19:25   ` Simen Thoresen
2005-10-08 19:31     ` Randy.Dunlap [this message]
2005-10-10  8:17       ` Simen Thoresen
     [not found]         ` <309a667c0510100215wcf311bcr3cc0555cc4557d39@mail.gmail.com>
2005-10-10  9:28           ` Devesh Sharma
2005-10-10  9:48             ` Simen Thoresen
2005-11-03 15:16               ` Simen Thoresen

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=20051008123131.41d85d45.rdunlap@xenotime.net \
    --to=rdunlap@xenotime.net \
    --cc=devesh28@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=simentt@dolphinics.no \
    /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®