On 09 Aug 2001 19:11:22 +0200, Stefan Baums wrote:
> Using the separate package with 2.4 kernels is inconvenient because
> you have to compile and install two packages where one can be enough.
Nice to hear you got it to work. I never considered the 2 packages thing
a problem, make-kpkg modules_im
On Thursday, 9 August 2001, Mario Vukelic wrote:
> I don't think it's worth the trouble to try and get it to work with
> 2.4.x drivers if they work the other way anyhow.
Using the separate package with 2.4 kernels is inconvenient because
you have to compile and install two packages where one can
On Thursday, 9 August 2001, Michael Heldebrant wrote:
> For one thing you just said you were running 2.4.6. The
> /lib/modules/2.4.7 is most likely not there.
Sorry, I was trying it out with both 2.4.6 and 2.4.7, and mixed them
up in my email.
> Secondly:
> Your kernel is probably not set to ac
On 09 Aug 2001 18:25:29 +0200, Stefan Baums wrote:
> If, however, I compile the separate pcmcia-source package for use with
> the 2.4 kernel, everything works just fine.
I don't have access to my laptop now, but I remember to have read
(probably in README of pcmcia-source package) that If you wan
For one thing you just said you were running 2.4.6. The
/lib/modules/2.4.7 is most likely not there.
Secondly:
Your kernel is probably not set to accept module symbols from other
compiled modules. This is actually something that you can solve in two
ways I beleive. 1. Compile it yourself (safe
Hi all,
I am having problems getting the PCMCIA code included in the 2.4
kernels to work. If I compile it in as modules and then reboot to the
new kernel, I get the error message
Starting PCMCIA services: modules/lib/modules/2.4.7/pcmcia/i82365.o:
init_module: No such device
Hint: insmod
6 matches
Mail list logo
