[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

RE: new kernel, now no network

> -----Original Message-----
> From: Kevin McKinley [mailto:ronin2@bellatlantic.net]
> Sent: Thursday, April 17, 2003 2:07 PM
> To: debian-user@lists.debian.org
> Subject: Re: new kernel, now no network
> On Thu, 17 Apr 2003 12:37:04 -0400
> "Fitz Hugh Ludlow" <fhludlow@sbcglobal.net> wrote:
> > Now the module loads, but says "unused" in lsmod.  dmesg has
> zero info.  I
> > can't find any mention of it whatsoever in /var/log/ either.
> >
> > Should the mere act of loading the module cause it to probe and look for
> > the nic?  Will this activity be logged anywhere?  Should
> > /etc/init.d/networking restart cause it to look for the nic?
> > It says,
> > eth1: ERROR while getting interface flags no such device
> > bind socket to interface: no such device
> >
> > It's now eth1 since I got the onboard nforce nic working as eth0.  Would
> > it be productive to disable the onboard nic and try to get this working
> > again as eth0?
> >
> > Is there anything else one must do when installing a second pci nic?
> Well, yes.
> It looks like what's happening now is that your NIC is being seen and a
> driver is loaded for it. Since it isn't bound to an interface
> lsmod reports
> the driver is unused.
> You need to another stanza in /etc/network/interfaces for eth1.
> Kevin

Forgot to mention that - I already have it in there.

I booted into the old kernel and lsmod does not show the driver, so it was
compiled into the old kernel evidently.  The config file for the new kernel
shows net_vendor_3com=y

How can I tell if the 3c59x module is actually compiled into the new kernel?

I did discover a line in /var/log/syslog.0 that says "modprobe: can't locate
module eth1"
In modules.conf I have
alias eth1 3c59x

I put append="ether=0,0,eth1" in lilo.conf and ran lilo, rebooted.  No

Reply to: