public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tom Barnes-Lawrence <tomble@usermail.com>
To: linux-kernel@vger.kernel.org
Subject: IDE compilation(etc) errors
Date: Fri, 23 Jan 2004 04:21:35 +0000	[thread overview]
Message-ID: <20040123042135.GA834@darius> (raw)

(NOTE: please CC any replies to me, I'm not on the list)
Hi, I'm a long-term Linux user, but when I recently installed
2.6 I hadn't compiled a kernel for a long time, so I couldn't
remember stuff. Apologies if this issue has been addressed before,
I couldn't find it in the archives or the FAQs, etc.

OK: I use SCSI, I have various SCSI devices, and I *boot* from
SCSI. but I also have an IDE DVD drive.

I'm not using an initrd image (because you lot neglected to mention
which damned mkinitrd version I'd need for it) and therefore I
installed my kernel the old fashioned way: stuff necessary
for booting compiled in, everything else as modules under
/lib/modules, and yes, I *did* install the kernel too.

So: SCSI, my adapter, and sd are compiled in, and (the first
attempt, at least) IDE, and everything IDE related I built
as *modules*. When I did make modules_install, it churned
out a lot of warnings about various functions not being found
for the modules. I assumed they would be found later.

Then, when I rebooted with the new kernel, sure enough, I found
*no* IDE related kernel module I could load that didn't have
unresolved symbols. Perhaps there was supposed to be some
weird invocation of modprobe or insmod to load them all at
once or something, but if so, news to me.

When 2.6.1 came out, I installed it (partly as I also thought I was
leaking memory) and tried some other compile options, but these
didn't help. I then tried compiling the base IDE support as
compiled-in rather than a module. But doing this, the actual
kernel compilation crashed near the end, something about compiling
built-in/init or something like that.

 I logged (most of) the errors produced from that, I have
/proc/config.gz (with the IDE as modules setting), and I
probably still have the .config file for the failed compilation
(with IDE compiled-in). If anybody on the list thinks any of these
would be of use, they should let me know which, and whether
to send the info to them directly or to the whole list.

 I figure that either this situation I've found is a bug, or
if the set of compilation-options I chose is inappropriate, then
the config scripts must be wrong for letting me make it
(hence another bug), or the configuration help or other
documentation needs improving. Apart from that, I'd quite like
to know what I should have done right.

Thanks in advance,
 Tom Barnes-Lawrence
(to reiterate: please CC me replies, I'm not on the list)

             reply	other threads:[~2004-01-23  4:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23  4:21 Tom Barnes-Lawrence [this message]
2004-01-23  6:44 ` IDE compilation(etc) errors Martin J. Bligh

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=20040123042135.GA834@darius \
    --to=tomble@usermail.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