zentara wrote:
Rachel Greenham wrote:
Loading of the network modules didn't work. The dummy and ne modules which are all I use didn't load on startup and those parts of the boot showed "Failed". This was fixed for the real network card by adding "modprobe 8390<lf>modprobe ne<lf>" at the start of /etc/rc.d/network - this may not be the best way of adding things to those scripts, but it does solve the problem for now. Definitive fix?
However, it doesn't solve the Dummy driver not loading. "modprobe dummy" has no apparent effect in the same place. I'm not terribly worried about this as it doesn't seem to do very much at the best of times, but it's slightly irritating to see a failure notice. :-)
I know that the ne module should be set up in /etc/conf.modules to make it work as advertised.
There should be 2 lines: alias etho ne
and
ne irq# and ioport#
Hmm. My /etc/conf.modules does indeed hold the following: alias eth0 ne options ne io=0x220 The fact remains that with the exact same scripts and conf.-files 2.2.1 exhibits a fault that 2.0.36 doesn't. Albeit not a showstopper. -- Rachel - To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archiv at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>