Questions:
Should it say "trying" instead of "try"? as it seems to try it itself anyway.
If 8139too is to be used "instead", then why is 8139cp still shown by lsmod?
Is my system misconfigured? Trust me that I have not been tinkering with
such details that I barely grasp. All I know is how to apt-get things.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Argh, the other way around, of course:
echo "blacklist 8139cp" >> /etc/modprobe.d/blacklist.conf
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
blacklist the 8139too module and be happy.
echo "blacklist 8139too" >> /etc/modprobe.d/blacklist.conf
Michael
apparently because it got loaded but not unloaded
On 24.04.09 08:23, jid...@jidanni.org wrote:
> Now in 2.6.29-1-686 it just says
> 8139cp 0000:00:0f.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too
> I assume "use" here is short for "using" and means "I, the emitter of
> this message, will use", and not "you, the person reading this message,
> should use", and thus I needn't worry about it.
I think that it's the module telling user to try/use another module, but not
loading it. It's other script that loads 8139too.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
Windows found: (R)emove, (E)rase, (D)elete