Mailinglist Archive: opensuse (3100 mails)

["Peter Van Lone" <petervl@xxxxxxxxx>]

On 3/4/06, Per Jessen <per@xxxxxxxxxxxx> wrote:
> Peter Van Lone wrote:
>
> > 1)the OS has an outdated driver for the device it had correctly
> > detected, or 2)the OS has incorrectly detected the device, and
> > therefore the driver being used is wrong
>
> 1) is a possibility, but given that the PCI ids are a match, I doubt it.
> And certainly not 2).

if you look at my last post on this, from the debian buglist entry
makes it clear that some davicom devices work with tulip and not dmfe,
and some the other way around. And they share a PCI device ID.

> > If I wanted to try, say, the DMFE driver instead of tulip (is this
> > even an option???) how would I do that?

> To be honest, I'm not sure.  It used to be a simple edit
> of /etc/module.conf, now /etc/modprobe.conf, but I haven't really
> worked enough with 2.6 to know my way around.  I'm sure someone can
> tell you how to specify you want to use dmfe instead of tulip.  In the
> meantime, you could just unload the tulip module (rmmod tulip) and load
> the dmfe instead (modprobe dmfe).

simply changing the module name in yast/network devices/<your
nic>/hardware details seems to have done it


Thank you so much Per for sticking with me on this thread! The support
and good will generated by folks like you and Daniel is quite amazing!

Peter