Module Version
I'm a bit of a Linux & Debian Newbie, so excuse me if this is a bit of a
dumb question.
I've recently changed the setup if my machine. I have two IDE hard disks
and an IDE CD-ROM drive (Oh I wish I could afford SCSI).
My motherboard is a Pentium Triton type thing with two on-board IDE
channels. I also have an AWE32 Plug and Pray card. I had been using DOS
& Loadlin to initialize the cards and then boot into Linux, but I got
bored with that.
My original setup was.
Motherboard -> IDE Primary -> Hard disk 1 -> Hard disk 2
Motherboard -> IDE Secondary -> CDROM
AWE32 -> IDE Tertiary -> Not used.
After reading various documents about IDE and SCSI I decided (rightly or
wrongly) That I would get better performance by changing to the
following setup.
Motherboard -> IDE Primary -> Hard disk 1
Motherboard -> IDE Secondary -> Hard disk 2
AWE32 -> IDE Tertiary -> CDROM
So I did this. I also installed LILO to boot directly into Linux, set up
isapnp and Installed that into the startup scripts using the <install>
thingy that I forget the name of now because I'm at work.
Now my problem was, the IDE controller on the AWE32 is PnP. So it is not
initialized until the isapnp script is run. And this is run after the
Kernel is booted, so it doesn't spot the CDROM because the controller
doesn't "exist" so to speak.
Excuse me if this is a bit long winded, but I'm getting to the point.
After reading some more Documentation to do with isapnp I found a little
'c' prog in one of the README files (README.ide I think) that acted like
a module, but just told the kernel that the IDE controller existed after
it had been set up by isapnp.
I compiled the 'module' and did an insmod. Lo and Behold my CDROM drive
worked. I'm impressed. It took some digging, but I got it to work.
Now. The only problem I have is that when I insmod the 'module' I get a
warning saying that it was compiled under kernel version 2.0.29 and I
have to force it to load.
Am I right in thinking that this is because of the headers of libc5 (I
read the unofficial e-mail from Linus about Debians attitude towards
kernel headers). And if so, is there any way that I can compile this
module so that it doesn't matter what kernel version I am running?
Would it be all right to do this? The module is only about 4-5 lines of
code. I could always just put up with the warning, but I prefer to have
things tidy.
What is the "Proper way (tm)" of doing this.
Thanks for your time,
--
Matthew Collins
Mitral Systems Ltd
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: