From: "p b" <bustedkernel@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: 2.4.18-14 rebuild problems
Date: Thu, 13 Mar 2003 03:04:48 +0000 [thread overview]
Message-ID: <BAY1-F71mdiR1P30H8F00036c26@hotmail.com> (raw)
I've been trying to compile the Linux kernel to no avail. I've been
following the Linux kernel howto's fairly closely. Here's my scenario.
I need to set a few memory and semaphore parameters to accommodate an Oracle
9i database installation and need to rebuild the kernel as a result.
I'm using RDH 8.0, and a stock kernel 2.4.18-14 on a HP LPR machine w a
sym53c8xx scsi card. Nothing's special. Virtually all the steps complete
successfully but for a small wrinkle.
The "make install" piece sez it can't find the sym53c8xx scsi modules. Sure
enough, perusing the lib/modules/2.4.18.x library indicates no entries for
/kernel/drivers/scsi/sym53xx.
If I look at an earlier build, the pieces are there. Ive tried fudging the
install by copying them over to my new
/lib/modules/2.4.18.x/kernel/drives/scsi. But then I get unresolved symbol
errors upon a make install and of course make modules_install scrubs my
fudged entries.
I successfully (?) compiled on one occasion, only to encounter a scream
panic trap indicating I had a missing root, just at about the spot I would
anticipate the kernel is engaging the sym53c8xx card.
Ive also tried a 2.4.19 kernel and ran into the same problem.
I got about a week into this and am still hopeful
or perhaps totally
misguided.
Clearly somebodys (RDH) been able to compile this kernel, how can I?
Please cc me directly, if that's ok?
Thanks for your time.
PB
_________________________________________________________________
Help STOP SPAM with the new MSN 8 and get 2 months FREE*
http://join.msn.com/?page=features/junkmail
reply other threads:[~2003-03-13 2:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=BAY1-F71mdiR1P30H8F00036c26@hotmail.com \
--to=bustedkernel@hotmail.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®