> You don't have a module because you did CONFIG_VORTEX=y instead of > CONFIG_VORTEX=m. If you had built the driver as a module then "modprobe > 3c59x" would work. > Now I recompiled kernel with CONFIG_VORTEX=m. Rebooted tge system and did modprobe 3c59x. It gave me no errors. Thought it goes fine... /var/log/messages: ... Jun 27 13:01:35 server 3c59x: Donald Becker and others. www.scyld.com/network/vortex.html Jun 27 13:01:35 server 0000:02:06.0: 3Com PCI 3c905 Boomerang 100baseTx at 0xc000. Vers LK1.1.19 Jun 27 13:01:35 server eth0: Dropping NETIF_F_SG since no checksum feature. Jun 27 13:01:35 server PPP generic driver version 2.4.2 Jun 27 13:01:35 server 8139too Fast Ethernet driver 0.9.27 Jun 27 13:01:35 server ACPI: PCI interrupt 0000:02:07.0[A] -> GSI 18 (level, low) -> IRQ 18 Jun 27 13:01:35 server eth1: RealTek RTL8139 at 0xc400, 00:e0:7d:ff:6d:5c, IRQ 18 Jun 27 13:01:35 server eth1: Identified 8139 chip type 'RTL-8100B/8139D' ... But it's strange - in my pc eth0 is Realtek, and eth1 is 3Com. I tried to start those interfaces with dhcp. Realtek obtained ip address, but 3Com did not..
askar > What about "dmesg | grep eth"? Did that turn up anything? > > Zac > > Zac > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list
