> >>> 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.
I don't know how to make a bug report - and I feel very unsecure. If OpenSuse
has a bug or if it's just because maybe I myself am kind of buggy??? ;-)
Anyway: when searching google for "tulip dfme" I found that similar problems
also occure on debian systems.
> > Perhaps a change in /etc/modprob.conf or what ever the file is in SUSE
> > 10. Isn't this where some modules are set to load for certain devices?
>
> Probably the most easiest way is to change /etc/sysconfig/kernel:
>
> MODULES_LOADED_ON_BOOT="dmfe"
>
> This gets loaded at first, before all other non-initrd modules.
> If you have more than one entry there, the load sequence is either
> unpredicted or latest first (I'm only sure that it is not left to right).
>
> Cheers -e
Thanks for all the hints! Before trying out the suggested solutions I tried to
do the following:
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
rebotted the PC - and now the network card works as it should. I've rebotted
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.
Now there is one more thing I wonder:
in the boot log I find following entries now:
---------- from boot log Suse 10: -----------------
Setting up network interfaces:
lo
lo IP address: 127.0.0.1/8
done
Waiting for mandatory devices: eth-id-00:08:a1:35:bf:bc
20 19 Initializing random number generatordone
<notice>startproc: execve (/sbin/resmgrd) [ /sbin/resmgrd ],
[ CONSOLE=/dev/console ROOTFS_FSTYPE=reiserfs TERM=linux SHELL=/bin/sh
ROOTFS_FSCK=0 LC_ALL=POSIX INIT_VERSION=sysvinit-2.85 REDIRECT=/dev/tty1
COLUMNS=158 PATH=/sbin:/usr/sbin:/bin:/usr/bin:/lib/klibc/bin vga=0x31a
RUNLEVEL=5 PWD=/
SPLASHCFG=/etc/bootsplash/themes/SuSE/config/bootsplash-1280x1024.cfg
PREVLEVEL=N acpi=off LINES=59 HOME=/ SHLVL=2 splash=verbose SPLASH=yes
ROOTFS_BLKDEV=/dev/hdg1 _=/sbin/startproc DAEMON=/sbin/resmgrd ]
Starting resource managerdone
eth0 device: Davicom Semiconductor, Inc. 21x4x DEC-Tulip compatible
10/100 Ethernet (rev 40)
eth0 configuration: eth-id-00:08:a1:35:bf:bc
eth0 IP address: 192.168.2.2/24
done
--------------------------------------------
while the antries in Suse 9 are much shorter:
-------------- from boot log of Suse 9 (kernel 2.4): ----------------------
Setting up network interfaces:
lo done
eth0 IP/Netmask: 192.168.2.2 / 255.255.255.0 done
<notice>exit status of (network) is (0)
----------------------------------
Maybe the new kernel 2.6 has longer (and a bit mixed up) messages - but maybe
there is still something as it should not? I wonder about eth0 showing up 3
times and about the "Waiting for mandatory devices:
eth-id-00:08:a1:35:bf:bc".
Does this have any meaning or can I just forget about it?
kind regards, Daniel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
