Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

not an 8139C+ compatible chip, Try the "8139too" driver instead

93 views
Skip to first unread message

jid...@jidanni.org

unread,
Apr 23, 2009, 6:10:10 PM4/23/09
to
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

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

jid...@jidanni.org

unread,
Apr 23, 2009, 8:40:10 PM4/23/09
to
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.

Michael Biebl

unread,
Apr 24, 2009, 12:10:09 AM4/24/09
to
Michael Biebl wrote:

> 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.
>
> blacklist the 8139too module and be happy.
>
> echo "blacklist 8139too" >> /etc/modprobe.d/blacklist.conf
>

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?

signature.asc

Michael Biebl

unread,
Apr 24, 2009, 12:10:09 AM4/24/09
to
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.

blacklist the 8139too module and be happy.

echo "blacklist 8139too" >> /etc/modprobe.d/blacklist.conf

Michael

signature.asc

jid...@jidanni.org

unread,
Apr 28, 2009, 10:40:07 PM4/28/09
to
Michael Biebl <bi...@debian.org> writes:
> echo "blacklist 8139cp" >> /etc/modprobe.d/blacklist.conf
Now with the 2.6.29-1-686 kernel none of this is needed! The errors are gone.

Matus UHLAR - fantomas

unread,
May 10, 2009, 1:30:17 PM5/10/09
to
On 24.04.09 03:24, jid...@jidanni.org 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
>
> 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?

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

0 new messages