Thanks for the very long and thorough reply, I was unaware of all this
stuff... good to know now though.
I managed to "fix" the "problem", though I don't understand exactly how.
> Are you _sure_ the problem is
> with ne.o?
The thing was, the network card still worked, it was just that there
error messages during boot (and before /var/log/boot.msg starts
they went something like...
loading module ne from /lib/modules/2.2.13/net/ne.o
in /lib/modules/2.2.13/net/ne.o unresolved symbol ei_open
..... ns8390_init (which ties in with Fergal's response)
later on in the boot process, the eth0 service started without problems
(obviously the module WAS loaded).
The messages were due to a line in my lilo.conf:
which i have now commented out (getting rid of the error messages). I've
looked at initrd's man page, but it is slightly above my current level.
case, it appears to have done no harm.
Anyway, that was my solution, I'd be grateful for an explanation if
(almost a functioning linux user)
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!