Bug#681089: Some progress
On 23/07/12 07:58, Berni Elbourn wrote:
The combination of Squeeze, and the current "driver" from Broadcom seems to be stable. Note: The hardware is a HP ML115.
$ sudo ifconfig eth0
[sudo] password for elbournb:
eth0 Link encap:Ethernet HWaddr 00:21:5a:d3:d0:0c
inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::221:5aff:fed3:d00c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:175382 errors:0 dropped:0 overruns:0 frame:0
TX packets:234297 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:23169470 (22.0 MiB) TX bytes:199392368 (190.1 MiB)
Although this is only after an hour of runtime, I ran this system for two days without a single error or dropout.
elbournb@red:~$ sudo ethtool -i eth0
firmware-version: 5722-v3.07, ASFIPMI v6.02
$ cat /proc/version
Linux version 2.6.32-5-amd64 (Debian 2.6.32-45) (email@example.com) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun May
6 04:00:17 UTC 2012
So on this machine at least the Broadcom software is not stable on the Kernel backported from Wheezy. Also the current
"firmware" for squeeze, or backported from wheezy is not stable.
Erm. To clarify that last missmash.
tg3 driver in linux-firmware-nonfree with Squeeze or Squeeze-backport kernel is not stable
3.122n driver from Broadcom with Squeeze kernel is stable
3.122n driver from Broadocm with Squeeze-backport kernel is not stable <- so this does not look good for wheezy ??
"Confidence is what you have before you understand a problem" - Woody Allen