I wrote:
Jeremy Huntwork wrote:
Sorry, not familiar with the blacklist concept. Mind explaining that
one a little further? I'm guessing that means that hotplug won't start
that module, but that you can manually load it if you prefer to use it.
Your guess is correct - but I still have to test that blacklisting one
module still allows the other one to be loaded. This is certainly true
for Debian's hotplug, not sure about LFS.
Too bad, LFS stops if it finds a blacklisted PCI module and doesn't try
other possible drivers. So I have the following choice:
a) drop 8139cp (in preference to 8139too), eepro100 (in preference to
e100), dmfe (in preference to tulip), xircom_tulip_cb (in preference to
xircom_cb, and it doesn't load anyway because of missing symbols). If
you disagree because this breaks your network access, please tell.
b) apply Debian patch (attached) that causes hotplug to try loading all
matching PCI drivers instead of stopping at the first one (even if it is
blacklisted). Amend the blacklist. Requires testing by owners of
RTL-8139C+ cards for which both drivers work.
What is more correct here?
--
Alexander E. Patrakov
diff -ruN hotplug-2004_01_05.orig/etc/hotplug/pci.agent
hotplug-2004_01_05/etc/hotplug/pci.agent
--- hotplug-2004_01_05.orig/etc/hotplug/pci.agent 2004-02-03
00:36:16.000000000 +0100
+++ hotplug-2004_01_05/etc/hotplug/pci.agent 2004-02-03 00:33:44.000000000
+0100
@@ -122,7 +122,6 @@
if [ $class_temp -eq $class ]; then
DRIVERS="$module $DRIVERS"
: drivers $DRIVERS
- break
fi
done
}
--
http://linuxfromscratch.org/mailman/listinfo/livecd
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
