Mailinglist Archive: opensuse (3100 mails)

< Previous Next >
Re: [SLE] GVC Ethernet PCI Adapter linux
  • From: "Peter Van Lone" <petervl@xxxxxxxxx>
  • Date: Sat, 4 Mar 2006 14:00:58 -0600
  • Message-id: <68b791330603041200j652c587aoa7f0a378c84a376c@xxxxxxxxxxxxxx>
On 3/4/06, Daniel Bauer <linux@xxxxxxxxxxxxxxxx> wrote:

> "In Yast I deleted the network card and finished Yast. Then opened Yast again
> and "installed" the network card again, leaving the name, that yast gave her
> untouched, just overwriting "tulip" by "dmfe" (in hardware details).
>
> After this eth0 was not on the list given by "infconfig" (only lo appeared). I
> rebooted the PC - and now the network card works as it should. I've rebooted
> twice, to see, if was only an accident - but it seems that first deleting and
> then adding the card again works better than just changing the settings."
>
> Since then my card works perfect...

Daniel, that appears to have done it! Thank you so much .. I also saw
the following items from a google of the tulip error:

"One person found that the follwoing procedure worked:
ifdown eth0
rmmod tulip
rmmod dmfe
modprobe dmfe
ifup eth0"

and the debian bug list reported this in a bug about tulip not working
with the davicom chipset::

"The problem with this is, that after another bugreport (see
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=284730) the kernel
module for this device was changed from dmfe to tulip. It seems that
some devices work with the dmfe module while others work with tulip, but
yet they both use the same PCI ID. I really don't know what to do in
this case."

So -- I followed your suggestions and replaced "tulip" with "dmfe" in
the hardware details after removing and then re-adding the nic. I did
not do a restart, but ratther rmmod tulip rmmod dmfe modprobe dmfe
ifup eth0

after serveral reboots to check ... all now appears good. Thank you much!

Peter

< Previous Next >