[EMAIL PROTECTED] wrote:
>-snip-<
The solution was to place aha152x in the /etc/modules file. Now, what I
do not understand is why that line was not required in /etc/modules for
it to be recognised under 2.2.20, but was needed in 2.4.18. My problem
is no longer the machine not working, but me not understanding. Can
someone explain the variable treatment of /etc/modules between 2.2.20
and 2.4.18?
Check out the config file for your 2.2.20 kernel. I will bet you will
find the aha152x driver compiled into the kernel rather than as a
module. I am not 100% certain of this, so you will have to check, but
you would NOT be able to use it unless it is loaded somewhere.
An alternative would be to checkout your /etc/modules.conf file and see
if it is being loaded as a module there. A third possibility is that
you are using an initrd image with the 2.2.20 kernel and it is being
loaded there. One of these three should answer your question.
The same things work for the 2.4.X kernels. You probably got a kernel
image that wasn't setup to support the aha152x card "out of the box".
The same thing "could" have happened on your 2.2.20 kernel... you just
got lucky the packager thought support for it was important!
Cheers,
-Don Spoon-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
