can't ifconfig after loading new 3c59x module
"James S. Johnson" <[email protected]>
| Newsgroups | gmane.linux.drivers.vortex.devel |
|---|---|
| Message-ID | <[email protected]> |
All, 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: mkdir netdrivers-3.4 cd netdrivers-3.4 tar -xvf ../netdrivers-3.4.tar KERNVER=2.4.20vlan EXTRAFLAGS=-DCONFIG_VLAN make install -m 644 pci-scan.o 3c59x.o /lib/modules/2.4.20vlan/kernel/drivers/net/ depmod -a 2.4.20vlan Here's what happens at boot with the new 3c59x module: ... INIT: Entering runlevel: 3 Going multiuser... 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 SIOCSIFADDR: No such device modprobe: modprobe: Can't locate module eth1 eth1: unknown interface: No such device modprobe: modprobe: Can't locate module eth1 SIOCSIFBRDADDR: No such device modprobe: modprobe: Can't locate module eth1 eth1: unknown interface: No such device modprobe: modprobe: Can't locate module eth1 SIOCSIFNETMASK: No such device ... 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. Any ideas what I've done wrong, so the eth1 interface can no longer be configured with the new driver? James _______________________________________________ vortex mailing list [email protected] http://www.scyld.com/mailman/listinfo/vortex