[NCLUG] Oracle system help

Steve Roths sroths1 at attbi.com
Fri Feb 1 10:31:46 MST 2002


(OK, it's not really an oracle system, but the thread is easy to pick out)

Thanks, Mark for the tips.  None of it has worked, here's what I've found
out:

You were right on for the module, 'ne2k-pci' was it and the alias was
present in /etc/conf.modules

/proc/pci listed the card, too

lsmod had no reference to the module (it's a short list, the NIC is my only
PCI device)

could not install the module with modprobe - error was 'invalid parameter
io'

used the GUI to remove the interface and rebooted - no luck.

removed the card altogether and let the machine know it was really gone and
no bootup errors were reported.

Then tried an old 3com card i had lying about, referenced its module in
linuxconf and still no joy.

3com is now the alias in /etc/conf.modules and /proc/pci

still won't load the module on boot or manually; errors from
/var/log/messages:

sysquery: sendto ([128.9.0.107].53):Network is unreachable   {just who is
that address, anyway?}
...
insmod:/lib/modules/2.2.5-15/net/net2k-pci.o:invalid parameter io     (same
with 3c59x.o)
ifup:Delaying eth0 initialization
network:Bringing up interface eth0 failed

What do I do now?  Where is this io parameter setting?
And just for sport, does anyone know why this happened?  Certainly futzing
with listener.ora and tnsnames didn't do it.

Steve

----- Original Message -----
From: Mark Fassler <fassler at monkeysoft.net>
To: <nclug at nclug.org>
Sent: Thursday, January 31, 2002 11:41 PM
Subject: Re: [NCLUG] Oracle system help


> 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
> _______________________________________________
> NCLUG mailing list
> NCLUG at nclug.org
> http://www.nclug.org/mailman/listinfo/nclug




More information about the NCLUG mailing list