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

RE: new kernel, now no network

-----Original Message-----
From: David Z Maze [mailto:dmaze@debian.org]
Sent: Thursday, April 17, 2003 10:19 AM
To: debian-user@lists.debian.org
Subject: Re: new kernel, now no network

"Fitz Hugh Ludlow" <fhludlow@sbcglobal.net> writes:

> I got a new kernel installed (woody from 2.2.20 to 2.4.20) following
> these instructions
> http://newbiedoc.sourceforge.net/system/kernel-pkg.html

> Ifconfig says device not found.

That's probably the best indicator that the kernel doesn't have a
network driver it believes in.  Do the boot messages (or 'dmesg') say
anything informative?  'lspci' shows that the card exists, right?

lspci shows it.  It's a 3c905 - TX.  I'm pretty sure I didn't do all the
steps to actually get it into the kernel.

So I downloaded, compiled and installed the 3c59x module.  Then installed
the pci-scan module that it is evidently dependant on.  I put lines in
/etc/modules/aliases and ran update-modules to get them into the
modules.conf.  I added lines to /etc/network/interfaces and /etc/modules

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?

Reply to: