I got a Dell last summer, in which I couldn't get the network chip
running, so I bought a cheap Via Rhine PCI network card and used that
for almost a year. I finally got the built-in chip working today on the
older 530. This post is being sent on it. It's a bastardized Intel
chip that shows up as "Intel Corporation 82562V-2 10/100 Network
Connection (rev 02)" under lspci, but uses gigabit driver (e1000e). Go
figure.
I finally stumbled across the *REAL* reason I couldn't get it working.
I always tried configuring eth0 for it... silly me. Apparently, the
chip *ALWAYS* comes up as eth1. Here are a couple of excerpts from
dmesg. The 1st one is about halfway through dmesg...
e1000e: Intel(R) PRO/1000 Network Driver - 0.2.0
e1000e: Copyright (c) 1999-2007 Intel Corporation.
ACPI: PCI Interrupt 0000:00:19.0[A] -> GSI 20 (level, low) -> IRQ 17
PCI: Setting latency timer of device 0000:00:19.0 to 64
Switched to high resolution mode on CPU 1
Switched to high resolution mode on CPU 0
0000:00:19.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:1a:a0:8c:0d:b2
0000:00:19.0: eth0: Intel(R) PRO/10/100 Network Connection
0000:00:19.0: eth0: MAC: 5, PHY: 7, PBA No: ffffff-0ff
The next one is at the very end...
0000:00:19.0: eth1: Link is Up 100 Mbps Full Duplex, Flow Control: RX
0000:00:19.0: eth1: 10/100 speed: disabling TSO
0000:00:19.0: eth1: changing MTU from 1500 to 1452
0000:00:19.0: eth1: Link is Up 100 Mbps Full Duplex, Flow Control: RX
0000:00:19.0: eth1: 10/100 speed: disabling TSO
Here's /etc/conf.d/net I left in the eth0 entry. It generates an
error message, but doesn't cause any problems. And yes, *THE NETMASK
IS CORRECT*
config_eth1="192.168.123.250 broadcast 192.168.123.255 netmask 255.255.255.248
mtu 1452"
routes_eth1=("default via 192.168.123.254")
config_eth0="192.168.123.250 broadcast 192.168.123.255 netmask 255.255.255.248
mtu 1452"
routes_eth0=("default via 192.168.123.254")
I've made 4 changes in iptables to accomadate the change, but I'd
really like to know what's going on, and revert to eth0 if possible.
I've appended "nofirewire" to the boot paramters in lilo, but it doesn't
help.
--
Walter Dnes <[EMAIL PROTECTED]>
--
gentoo-user@lists.gentoo.org mailing list
