Hi Richard, Thanks for your report. Unfortunately, this issue is pretty well known (check out the bug 334104, for example), and so far we have failed to come up with a decent solution to it. The problem is that both dmfe and tulip cards advertise support for this particular PCI id. The sad part is that there are some cards out there, having the same PCI id, but requiring different drivers to work!
So far I could not come up with anything better than patching both modules to introduce a parameter which can be used to prevent them from initializing any devices. Unfortunately, it will still be up to user to recognize that the problem comes from tulip/dmfe driver conflict, and disable the "faulty" one. Best regards, -- Jurij Smakov [EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
