Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#1712 - kernel module 8139cp conflicts with 8139too
Attached to Project:
Arch Linux
Opened by Tobias Powalowski (tpowa) - Monday, 01 November 2004, 09:20 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 28 July 2005, 06:35 GMT
Opened by Tobias Powalowski (tpowa) - Monday, 01 November 2004, 09:20 GMT
Last edited by Tobias Powalowski (tpowa) - Thursday, 28 July 2005, 06:35 GMT
|
Detailshi again
i had this issue on my laptop: hotplug tries to load 8139cp instead of 8139too here is the source of the problem: 8139cp has exatcly the same entry in modules.pcimap as the 8139too, hotplug founds "cp" module first because it's listed before "too" module loads it and it fails 8139too will not be loaded if you blacklist 8139cp you can find this file at /lib/modules/2.6.9-ARCH/ i googled around and it seems to be a known problem. i found that it's from 2002: http://fr.rpmfind.net/linux/RPM/suse/8.1/i386/suse/i586/hotplug-2002_04_01-45.i586.html --snip usb-blacklist-8139cp.diff adds 8139cp to the blacklist. 8139cp.o is listed only once in modules.pcimap. And for exactly this device there is also an entry with 8139too, which works better. ---snap http://lists.asu.edu/cgi-bin/wa?A2=ind0309&L=asulug&F=&S=&P=2957 ---snip If that doesn't work I would suggest using the 2.4 boot floppy kernel which has it statically compiled in, or install the latest 2.4 kernel deb which has it compiled as a module. There are two modules in the 2.4 kernel for the RTL8139. The best one to use is 8139too, you should only use the 8139cp if the former doesn't work. The 8139cp module handles the some versions of the RTL8139c revision that had some hardware implementation bugs. ---snap suggestion: we can disable 8139C module then the conflict may not arise or the people have to load the 8139too explicitly greetings tpowa |
This task depends upon
Any other way for these two to coexist?
hotplug needs to be concerned that if 8139cp is blacklisted
it should load 8139too, have to do some reasearch on that
btw, it's stupid to let two cards make the same entry in modules.pcimap
temporary workaround for that is disabling the 8139cp line in modules.pcimap
in this case 8139cp is loaded first and after that 8139too
i think when 8139cp will work it cannot load 8139too after it
for me now 8139cp gives me "please try 8139too" which is loaded after 8139cp is tried to load :)
if you would add this to modprobe.conf:
install 8139cp /sbin/modprobe -i 8139cp ; /sbin/modprobe 8139too
I had the same issue on my computer too.
Adding MODULES=(... 8139too ...) in /etc/rc.conf solved the problem for me.
Regards,
Benoit FAY
modules.pcimap doesn't it? This gave me a run-around with LFS awhile back.