Most recent kernel where this bug did not occur:2.6.17.13 Distribution: Crux Hardware Environment: All our P4 and PIII Servers Software Environment: Not software dependable Problem Description: When upgrade to 2.6.17.11 then our servers with multiple NIC's changed the order it was loaded. We use modules for NIC's in kernel config. modprobe.conf are set up as this example. alias eth0 e100 alias eth1 8139too Efter upgrade to 2.6.17.11 the NIC which is first loaded is 8139too (Realtek) which then get eth0 and second is the e100 (INTEL) eth1 Kernel 2.6.17.8 and erlier was loaded in the order of modprobe.conf settings. After upgrade to 2.6.17.13 then the load order of eth modules have change again, and still dont folow the modprobe.conf setting. Efter upgrade to 2.6.17.13 the NIC which now is loaded first is the e100 eth0 (INTEL) and second is 8139too (Realtek) eht1 I have the same problem with 3com and realtek or 3com and Intel NIC's it change the load order and don't folow the modprobe.conf settings. Steps to reproduce: Use to different NIC's and use 2.6.17.8 and config the driver as module in kernel config. use modprobe.conf and config as I have describe. Change then to 2.6.7.11. And then use 2.6.7.13 and see how the the NIC driver are loaded. It seams to work ok with 3com and tulip based (D-LINK 4-port NIC
*** This bug has been marked as a duplicate of 7137 ***