From: "Tony.Ho" <linux@idccenter.cn>
To: albcamus <albcamus@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Why can't I build a running Kernel?
Date: Tue, 13 Feb 2007 12:20:35 +0800 [thread overview]
Message-ID: <45D13C93.6010400@idccenter.cn> (raw)
In-Reply-To: <45D129DA.1040306@idccenter.cn>
In addition....
This problem is not appear on another PC host with the same
hardware(CPU,HD) except MEM is 2G.
OS is origin RHEL4 without updates.
Tony.Ho wrote:
> I have the same problem with 2.6.20.
> My host is dell PE850: pemtiumD 2.8G X1, MEM 1G X4, SATA 73G X1.
>
> albcamus wrote:
>> 2007/2/9, Jiri Slaby <jirislaby@gmail.com>:
>>> Reg Clemens napsal(a):
>>> > Why can't I build a running Kernel?
>>> > I have in the past, but since some time in the 2.6.19 series,
>>> > I have got the following series of errors.
>>> > Same thing now with 2.6.20.
>>> >
>>> > I build with:
>>> >
>>> > make xconfig
>>> >
>>> > changing only the Processor type to Pentium4,
>>> > then I
>>> >
>>> > make bzImage
>>> > make modules
>>> > make modules_install
>>> > make install
>>> >
>>> > Fine everything builds, no errors.
>>> > I then try booting, and I get 4 or 5 lines and then
>>> >
>>> > Unable to access resume device (/dev/sda5)
>>> > mount: could not find filesystem '/dev/root'
>>> > < 4 more lines with setuproot and switchroot >
>>> >
>>> > and then
>>> >
>>> > Kernel panic - not syncing: Attempting to kill init!
>>> >
>>> > Sigh.
>>> > What has changed, what do I need to do to get this thing to boot?
>>>
>> I have the same problem with 2.6.19 and later. The previous kernel with
>> same .config works, but it's not true for 2.6.19 and 2.6.30.
>>
>>
>>
>>
>>> Re-enable sata/scsi/usb/whatever is your root behind stuff back
>>> again? What
>>> does
>>> your .config look like?
>>>
>>> regards,
>>
>> I selected everything about ATA to <*> or <M>, and made initrd for the
>> newly-built kernel, still unable to boot.
>>
>> The .config was attached, I have kdb-4.4 patched.
>>
>> Thanks and Regards,
>> albcamus <albcamus@gmail.com>
>
> -
> To unsubscribe from this list: send the line "unsubscribe
> linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
prev parent reply other threads:[~2007-02-13 4:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-08 18:17 Why can't I build a running Kernel? Reg Clemens
2007-02-08 19:28 ` Jiri Slaby
2007-02-12 8:36 ` albcamus
2007-02-12 11:27 ` Jiri Slaby
2007-02-13 2:16 ` albcamus
2007-02-13 11:41 ` Jiri Slaby
2007-02-13 3:00 ` Tony.Ho
2007-02-13 4:20 ` Tony.Ho [this message]
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=45D13C93.6010400@idccenter.cn \
--to=linux@idccenter.cn \
--cc=albcamus@gmail.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