Hello,
Am Mittwoch, 21. Dezember 2005 16:08 schrieb Daniel Bauer:
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?
Even if it is not nice, you could write the rmmod and modprobe command to /etc/init.d/boot.local. Maybe the network script is working correct then. (If not, write a small initscript based on /etc/init.d/skeleton which calls the commands and add Required-Start: network to ensure it is run late enough.)
Oh, and please make an entry in bugzilla - this sounds like a bug. Perhaps a change in /etc/modprob.conf or what ever the file is in SUSE
On Wed, 2005-12-21 at 18:18 +0100, Christian Boltz wrote: 10. Isn't this where some modules are set to load for certain devices? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998