Damian Gerow wrote:
Milan Budimirovic wrote:
: Has anyone else had trouble with this particular ethernet controller?
Nothing obvious springs to mind, no. Which revision of the controller are
you using? There's at least E, V, and L.
It has two controllers. One's an 82573L and the other's a 82573V
: I managed to get it working (sort of) on Ubuntu 9.04, but it took a bit
: of work. The device driver does not work out of the box on the install
: CD. Once you upgrade the kernel it works with DHCP, but not if you try
: to assign it a static IP address (figure that one out). I managed to
: work around the problem by using DHCP and assigning a static IP to the
: controller's MAC address on the DHCP server. :P
This is actually how I run my entire home network. It makes
re-configuration of network parameters (re-IP-ing, NTP servers, WINS
servers, etc.) much easier. Of course, that's not really helping solve the
root problem.
It's fine for my needs but this is ostensibly a server board.
I had the exact opposite problem with Fedora last year. I did a security
update and all of a sudden I couldn't get my Realtek card to work as a
DHCP client.
: I'm a little cheesed right now because (a) Tyan put cheapoid ethernet
: controllers on an otherwise excellent mainboard, and (b) the driver
: seems to work on some versions of the kernel and not others.
I'm glad to meet another Tyan user! Their motherboards are generally fairly
good, so I'm also surprised that they've chosen the 82573 -- which board is
it?
It's a Tyan Toledo i3210W.
http://www.tyan.com/product_board_detail.aspx?pid=591
It's not a high-end board by Tyan standards, but still...
It looks like drivers for Linux have been around since 2.6.16, and I'm
pretty sure Ubuntu 9.04 is well beyond that. Have you tried upgrading to
the latest firmware? Tyan does have a nasty habit of shipping boards with
firmware revisions that are fairly old; I recently purchased an S2932 with a
firmware from 2006, so the CPUs I bought aren't detected.
Aside from firmware updates, what actually happens when you try to assign a
static address? Kernel panic, address gets assigned with no network
responsiveness, ifconfig error, watchdog timeouts...?
ifconfig looks normal, but the networking just does not work.
Likely unrelated, it looks like the FreeBSD folks ran into an issue with the
NIC PROM a while back[1]. There is apparently a fix[2], but the site has
been down at least all weekend, if not longer. Given that this was FreeBSD,
it's not likely to be related to your issue.
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.