Re: 8139cp 0000:03:08.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip
On Sat, Mar 01, 2008 at 11:52:50 +0100, stephane lepain 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.
>
> _My Config_
>
> Hardware: AMD64 3800+
> OS: Debian testing
>
> *Mar 1 10:50:52 margoullat kernel: ata4: SATA link down (SStatus 0
> SControl 310)
> Mar 1 10:50:52 margoullat kernel: 8139cp 0000:03:08.0: This (id
> 10ec:8139 rev 10) is not an 8139C+ compatible chip
> Mar 1 10:50:52 margoullat kernel: 8139cp 0000:03:08.0: Try the
> "8139too" driver instead.
> Mar 1 10:50:52 margoullat kernel: 8139too Fast Ethernet driver 0.9.28*
Please tell me if I understand you correctly: Your RTL8139 does work
once the system comes up; your only problem is getting rid of the
message and the delay during boot?
Try to unload the 8139cp module after the system has booted by running
this command as root:
modprobe -rv 8139cp
Do you get any error messages? Check with "lsmod | grep 8139" and make
sure that 8139cp is really gone and only 8139too is still loaded. Verify
that your network still works, e.g. by running "ping www.kernel.org".
Assuming that this is all OK, you then have to generate a file that
tells modprobe not to load the 8139cp anymore during boot. To do this,
you can run (again as root):
echo -e "blacklist 8139cp\ninstall 8139cp /bin/true" > /etc/modprobe.d/local-8139cp
This should create the file /etc/modprobe.d/local-8139cp containing
these two lines:
blacklist 8139cp
install 8139cp /bin/true
Check with "cat /etc/modprobe.d/local-8139cp" if this was successful.
(If you already know how to use one of the various text editors
available under Linux then you can of course also create the file by
entering these two lines in your editor of choice and saving the
result.)
Then reboot and test if your system behaves properly now. Report back if
it does not; in that case we will have to take a closer look at your
initrd and maybe also at modules.dep.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
Reply to: