Re: not an 8139C+ compatible chip, Try the "8139too" driver instead
On 24.04.09 03:24, email@example.com wrote:
> At boot with Linux 2.6.26-2-686 I see
> 8139cp 0000:00:0f.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
> 8139cp 0000:00:0f.0: Try the "8139too" driver instead.
> 8139too Fast Ethernet driver 0.9.28
> ACPI: PCI Interrupt 0000:00:0f.0[A] -> GSI 18 (level, low) -> IRQ 18
> eth0: RealTek RTL8139 at 0xe000, 00:0c:76:7d:c6:7d, IRQ 18
> eth0: Identified 8139 chip type 'RTL-8101'
> $ lsmod|grep 8139
> 8139too 20320 0
> 8139cp 16800 0
> mii 4896 2 8139too,8139cp
> 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?
apparently because it got loaded but not unloaded
On 24.04.09 08:23, firstname.lastname@example.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, email@example.com ; 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