> In SUSE 10 unload the tulip driver and then load the dmfe first. This > sounds like a driver issue. Looking at the docs this does not appear to > be a tulip family driver. If you have the kernel sources installed look > in /usr/src/linux/Documentation/networking for more information. > On the SuSE 9.x box show the results of lsmod | grep tulip.
Ok, thanks! This works so far, it seems that Suse10 recognises the Davicom card wrongly. I typed: rmmod tulip modprobe dmfe ifconfig eth0 up Then ping (and internet access) works. So, I went to Yast/network devices/network card and changed the "hardware details" of the card: - gave it a new name "Davicom" - deleted the entry for the driver "tulip" and entered "dmfe" instead After finishing Yast, network connection was gone again and lsmod showed "tulip" again. Went to Yast again to check if it has saved my entries - it did. I rebooted, but same result: module "tulip" loaded as unused, "dmfe" not in the list. With rmmod/modprobe/ifconfig as above I can make the network running again. So, my only problem - for the moment ;-) is: how can I make the change definitive, so that "dmfe" will be loaded at boot and "tulip" not? regards, Daniel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
