ould be fixed.
you are right. it's related to my other post on /lib confusion... i
still had the older (incompatible) pcmcia-cs modules in
/lib/modules/2.4.17/pcmcia, since pcmcia-cs decided to install in
/lib/modules/2.4.17+fishbowl/pcmcia (i am using flavours to indicate
machine names).
On Friday 28 December 2001 02:22 am, k l u r t wrote:
> On Thursday 27 December 2001 11:55 pm, martin f krafft wrote:
> > even though modprobe seemingly only bitches about tainting when ds.o,
> > cb_enabler.o, and i82365.o are loaded (they load fine), tulip_cb.o (or
> > any other high-level module
tainting doesn't prevent any modules from loading. If your modules are
not loading, its something else. Modules that "taint" the kernel, but
shouldn't (like pcmcia-cs) are buggy and should be fixed.
IMHO, there's no reason to bitch about this.
On Fri, 2001-12-28 at 02:22, k l u r t wrote:
> On
On Thursday 27 December 2001 11:55 pm, martin f krafft wrote:
> what's this business about tainting the kernel with non-GPL modules???
> more importantly, how do i disable/go around it.
>
> i am *only* trying to install pcmcia-modules from unstable (3.1.29)
> with my 2.4.17 kernel, and this is anno
what's this business about tainting the kernel with non-GPL modules???
more importantly, how do i disable/go around it.
i am *only* trying to install pcmcia-modules from unstable (3.1.29)
with my 2.4.17 kernel, and this is annoying!!!
even though modprobe seemingly only bitches about tainting whe
5 matches
Mail list logo
