Damian Gerow wrote:
: It's a Tyan Toledo i3210W.
And which firmware revision? It looks like they've had a few problematic
releases; might be worth updating to the latest one.
It's v1.06, and none of the BIOS updates since then appear to address
broken networking of this type.
I'm not that keen on updating the BIOS unless it's absolutely necessary
(i.e. if it goes bad I hose the mainboard and void the warranty).
: > On a parting note, you're not the only one with 82573 problems in Ubuntu.
: > Which driver are you using? I believe (and I could very well be wrong)
: > there are two different drivers in the tree that may work with the 82573:
: > e1000, and e1000e. Additionally, which kernel are you using? I'm assuming
: > 2.6.30 at this point?
:
: I'm using a 2.2.28 kernel and the e1000e drivers.
:
: The weird thing is that it's not a new controller. It's been on the
: market for four years now, and apparently it has worked in the past.
Which means it's likely either an issue with the specific revision of the
driver you're using, or your firmware (or both). Especially if both
interfaces are misbehaving the same way.
When you say there's no network activity, can other nodes on the network
successfully perform ARP requests against the server in question, or do
those fail as well?
I didn't try to arp it from other machines. As far as I recall, it was
visible on the local network and it behaved more like the routing was
broken on it (but that wasn't it).
I strongly suspect broken driver here, as I have another machine on the
same network with the same distro, same kernel that works perfectly. The
only difference is the NIC.
Anyway, I was more interested in finding out if anyone else had issues
with this controller.