tg3 Drivers kernel 2.4.18-10smp
fluke at gibson.mw.luc.edu
Sun Jan 12 14:13:00 CST 2003
If you are looking to continue to get support from RH or Dell then you
should upgrade the tg3 driver with the 2.4.18-19.7.x package. If the PE
2650s came with RH pre-installed then they should have come with
activation codes to get RHN basic service. This allows the kernel to be
updated with up2date such as: up2date -f kernel-smp
But, if reliablity is more important than speed then you should switch the
network connection to the second port and use the e100 driver. We also
bought several PE 2650s and discovered that for *both* Linux and Novell
Netware that the Broadcom gigabyte NIC drivers suck. Dell's primary
customer is still people that mostly buy into Wintel. For the rest of us
that are interested in "alternatives" such a Linux, PPC,
x86-64/Sledgehammer, etc. then it might be time to move on.
On Fri, 10 Jan 2003, Jared Saul wrote:
> Back in August I installed 16 poweredge 2650s. We made the (then
> unknown) discovery that the bcomm drivers were non-functional and
> updated the kernel/redhat to use tg3 drivers (had to update everything
> to keep the openmanage compatable).
> Anyway, the tg3 seem to work... more or less. I have intermitten kernel
> freezes on a couple of machines and have noticed the Octet count doesn't
> report correctly along with some other flakey behaviors that are
> tempting to atttribute to the network driver.
> So, my question is:
> Should I change the network drivers when I'm onsite next week?
> If so, to what (tg3 or bcomm)
> And, what's the easiest way to do this? Will I need to reload the
> kernel, compile to drivers? Can I just drop them in and load them as a
> kernel module with insmod?
More information about the Linux-PowerEdge