Re: can't ifconfig after loading new 3c59x module

Donald Becker <[email protected]>
Newsgroups gmane.linux.drivers.vortex.devel
Message-ID <[email protected]>
On Fri, 9 May 2003, James S. Johnson wrote:

> I'm trying to install a new 3c59x driver on a Slackware 9.0 machine to use 
> with a 802.1Q vlan interface.  Before trying to install it, I compiled a 
> 2.4.20 kernel with vlan capability, with the kernel's top level Makefile 
> EXTRAVERSION=vlan.  That kernel, with its original 3c59x driver, can access 
> the network without any problems.  However, when I build and install a new 
> 3c59x driver, ifconfig can't start up a new interface.
> 
> Here's how the driver is built:
..
> Here's what happens at boot with the new 3c59x module:
> Configuring eth1:
> ifconfig eth1 192.10.30.250 broadcast 192.10.30.255 netmask 255.255.255.0
> modprobe: modprobe: Can't locate module eth1

This means that the 3c59x driver either
   was not loaded
   did not find the NIC

You can read the kernel messages (usually /var/log/messages) to see
which was the case.

> Installing the modules from the command line with "insmod pci-scan 
> msg_level=4" and "insmod 3c59x debug=7" and then running ifconfig gives the 
> same error messages, except for the modprobe lines.

What were the kernel messages from this?

-- 
Donald Becker				[email protected]
Scyld Computing Corporation		http://www.scyld.com
914 Bay Ridge Road, Suite 220		Scyld Beowulf cluster system
Annapolis MD 21403			410-990-9993

_______________________________________________
vortex mailing list
[email protected]
http://www.scyld.com/mailman/listinfo/vortex
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.