From: Richard Adams <pa3gcu@zeelandnet.nl>
To: kernel kernel <unix.hacker@gmail.com>
Cc: newbie <linux-newbie@vger.kernel.org>
Subject: Re: Unable to make kernel 2.6.8 up
Date: Thu, 21 Oct 2004 07:53:02 +0200 [thread overview]
Message-ID: <200410210753.02042.pa3gcu@zeelandnet.nl> (raw)
In-Reply-To: <104ee7a5041020205740020828@mail.gmail.com>
On Thursday 21 October 2004 05:57, kernel kernel wrote:
> Hi Richard,
> I was able to build it.
> But while, boot up it is giving the error message init not found.
This could be cause by many things, but considering you mentioned SATA and
then SCSI leads me to belive your new kernel is looking for a partition on a
differently named drive than you think it is.
For example, some SATA drivers use scsi (emulation) meaning your old system
has disks defined as /dev/hdX and the new kernel with SCSI or SATA devices
looks for /dev/sdX
Without knowing what you are doing no one can really say what you need to do.
I can point you to a search engine use "google.com/linux" as the address and
type, "no init found" in the search engine, you will get a lot of information
which may help you.
> Thanks
> Amrith
--
If the Linux community is a bunch of thieves because they
try to imitate windows programs, then the Windows community
is built on organized crime.
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" 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.linux-learn.org/faqs
next prev parent reply other threads:[~2004-10-21 5:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 16:17 Unable to make kernel 2.6.8 up kernel kernel
2004-10-19 19:36 ` Richard Adams
2004-10-20 3:52 ` kernel kernel
2004-10-20 5:40 ` Richard Adams
2004-10-21 3:57 ` kernel kernel
2004-10-21 5:53 ` Richard Adams [this message]
2004-10-21 6:40 ` kernel kernel
2004-10-21 16:14 ` Richard Adams
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=200410210753.02042.pa3gcu@zeelandnet.nl \
--to=pa3gcu@zeelandnet.nl \
--cc=linux-newbie@vger.kernel.org \
--cc=unix.hacker@gmail.com \
/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