[NCLUG] Oracle system help
Mark Fassler
fassler at monkeysoft.net
Thu Jan 31 23:41:00 MST 2002
On Thu, Jan 31, 2002 at 11:15:28PM -0700, Steve Roths wrote:
> Right now, I seem to have lost eth0 altogether. I found this out while
> tinkering with the oracle networking configs. I couldn't connect with
> 192.168.0.100 any more. It had been working up until this morning, and
> I had a web site up for several days with Apache. (not the oracle
> Apache, but I did enable that this morning, also, just couldn't connect
> with it)
>
> ifconfig returns only for 127.0.0.1
>
> ping 192.168.0.100 returns 'Network is unreachable'
>
> linuxconf and the gnome control-panel settings are the same as when the
> connection was working, but I'm getting 'Delaying eth0 initialization'
> errors at reboot and when I 'activate' the interface with
> control-panel.
I get that error when the OS can't get the driver to talk the hardware.
If you're running a standard RedHat the kernel is probably modular, so
most of the drivers are loaded as modules and not built into the kernel.
As root, do "lsmod". You should see a listing of modules. I *think* that
your ethernet card uses the ne2k-pci module. (It might be the 8139too
module.)
If either of these aren't listed, you can try to load the drivers by hand,
for example: "modprobe ne2k-pci". If you don't get an error message, it
probably worked and you can do an "lsmod" to see it. Otherwise the error
message might give you a hint.
By default, error messages go into /var/log/messages. Look in the end of
that file for any clues.
One handy source of info is the file /proc/pci -- this will list all the
PCI devices on your system. It's mostly human readable (well, totally
human readable if you understand the PCI spec... :-)
One file to check is /etc/modules.conf -- there should be a line in there
like this:
alias eth0 ne2k-pci
If all else fails, you can try to use your GUI tools to delete the
interface and re-add it.
--
Mark Fassler
fassler at monkeysoft.net
More information about the NCLUG
mailing list