[SuSE Linux] 2.2.1 on SuSE 6.0
Well, I've blasted my installation and put SuSE 6.0 on it from scratch - to be precise, the installation from the 6.0-evaluation directory, which was a reasonable size to mirror locally for the process. It works very nearly perfectly, except for the following: Running YAST resets KDM's backdrop settings to their defaults, overriding what's been set. Just the backdrop setting as far as I can tell. There were a couple of other oddities but they were probably my fault. :-} Then, with everything working fine (I like the "done" messages in green), I installed kernel 2.2.1 This seems to be working fine except: 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. :-) -- 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>>
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# - 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>>
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>>
Rachel Greenham wrote:
zentara wrote:
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.
I'm still waiting for my disks, so I'm just guessing. :-) Is it pnp? Maybe the card isn't getting setup right with the new "built-in-pnp" feature of the new kernel. Do the boot messages show the card being initialized? Did you enable the pnp feature of the 2.2.1 kernel? - 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>>
zentara wrote:
Rachel Greenham wrote:
zentara wrote:
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.
I'm still waiting for my disks, so I'm just guessing. :-)
Is it pnp? Maybe the card isn't getting setup right with the new "built-in-pnp" feature of the new kernel. Do the boot messages show the card being initialized? Did you enable the pnp feature of the 2.2.1 kernel?
PNP is not enabled at any stage. I can't remember right now if it reads the card details during bootup. -- 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>>
participants (2)
-
rachel＠epinet.co.uk -
zentara＠mindspring.com