Re: 8139cp 0000:03:08.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip

Adrian Levi a écrit :
On 01/03/2008, stephane lepain <penguindeb@xxxxxxxxx> wrote:
Hi,

I have had this error message coming up every time I start my PC where
it seems to be searching for the right driver. The problem is that it
takes a while at start time for my box to switch from "8139cp" to "8139too"
Is there a way I could tell my box to use the driver 8139too instead of
it choosing the 8139cp?

Sorry if I am not being clear and concise. I have just started with
Linux and I am learning at the moment.

Welcome to the community,

For your problem you could try placing 8139too into
/etc/modules

That might see that your 8139too driver gets loaded first.
Incidentally comment any references to 8139cp that you run across. HTH

Adrian

After one day of trying to dig up a solution for my problem. I have given up

Nothing seems to be working. I still get the same error message
"8139cp 0000:03:08.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip"

There seems to be a bug with the driver 8139too with realtek ethernet card.

http://groups.google.fr/group/comp.os.linux.hardware/browse_thread/thread/7cc2d557544f3228/ca5ce7244b8e55a8?hl=fr&lnk=st&q=8139cp+This+is+not+an+8139C%2B+compatible+chip#ca5ce7244b8e55a8

My biggest trouble is that I haven't found any fix for it.

What is hard to understand is that when I do a lspci -v I can clearly see that the two modules are loaded (8139cp, and 8139too). So why on earth would I still get this error message if the module 8139too is loaded in the kernel. My network card should be up and working. Shouldn't it. Unfortunatly, I am not experienced enough to dig deeper than that. Hope someone could give me hand here :)

03:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: medium devsel, IRQ 16
I/O ports at ac00 [size=256]
Memory at fdefe000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Kernel modules: 8139cp, 8139too



--
To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". Trouble? Contact listmaster@xxxxxxxxxxxxxxxx

Relevant Pages

  • Re: System Information: Error Control
    ... The driver is isapnp.sys is shown as Critical on my system as well as one ... as you will need it later for this step to copy the error message on ... see Help and Support Center at ... Event Source: ...
    (microsoft.public.windowsxp.general)
  • Re: Nv4_disp
    ... Do you have another working monitor you could use to test whether your ... I'm wondering if need to update that graphics driver at all; ... Have a look in the Event Viewer and send us the error messages you ... need it later for this step to copy the error message on it. ...
    (microsoft.public.windowsxp.general)
  • Re: 8139cp 0000:03:08.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
    ... I have had this error message coming up every time I start my PC where ... it seems to be searching for the right driver. ... (If you already know how to use one of the various text editors ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
    (Debian-User)
  • RE: Blue screen of death
    ... A problem has been detected and windows has been shut down to prevent damage ... If a driver in identified in ... Random "0x0000008E" Error Message on a Blue Screen in Windows XP ... View and Manage Event Logs in Event Viewer in Windows XP ...
    (microsoft.public.windowsxp.help_and_support)
  • RE: Blue screen multiple IRP requests stop: 0X00000044 (0X875DDD38
    ... - Event Type: Error ... Event Source: Service Control Manager ... It looks like this is a driver that is failing to startup - dgivecp.sys. ... later for this step to copy the error message on it. ...
    (microsoft.public.windowsxp.perform_maintain)