Driver conflicts - force loading dmfe after tulip?

In one machine I have a 3com card using the tulip driver as eth0 and a
Davicom DM9102 card as eth1. Everything has been working fine with my
10mbit switch. Today I upgraded to 100mbit, and the Davicom card shuts
down under heavy load with messages like:

NETDEV WATCHDOG: eth1: transmit timed out
eth1: transmit timed out, switching to MII media.

Does anybody know how I can force my system to use the dmfe driver for
eth1 even after the tulip driver has been loaded for eth0?

I've tried "alias eth1 dmfe" in modules.conf, but it does not seem to
work (it seems tulip is being used for both devices after being loaded)?

Is the only way to comment out Davicom related settings in the tulip
driver source?

Thanks,

Marius K.


_______________________________________________
tulip mailing list, [email protected]
To change to digest mode or unsubscribe visit
http://www.scyld.com/mailman/listinfo/tulip