Am 03.05.2013 um 09:01 schrieb Stan Hoeppner:
On 5/2/2013 8:24 AM, Lukáš Zíta wrote:
I can not think another way to handle this, so I will have to
switch toa card from Intel.
To those people who may wonder why/how others often end up with boxes
full of brand new 'perfectly good'
On 5/2/2013 8:24 AM, Lukáš Zíta wrote:
After some more tests, I have discovered, that those missing
patches are part of BQL backport to 3.2 kernel (therefore their absence
in upstream 3.2). In the end it turned out, that the NIC is buggy even
with BQL disabled. Strange thing is, that the bug
After some more tests, I have discovered, that those missing
patches are part of BQL backport to 3.2 kernel (therefore their absence
in upstream 3.2). In the end it turned out, that the NIC is buggy even
with BQL disabled. Strange thing is, that the bug only appears on newer
types of Dell
Dne 26.4.2013 19:13, Lukas Zita napsal(a):
Then I have noticed small patch in 3.2.43: tg3: fix length overflow in VPD
firmware parsing, so I have compiled vanilla kernel and got the NIC working
correctly. I will yet try to apply this patch on stock Wheezy kernel, but I
believe that the problem
to break the driver, but who knows.
--
View this message in context:
http://debian.2.n7.nabble.com/Wheezy-issue-with-broadcom-5720-nic-on-new-dell-PowerEdge-R720-tp2892237p2922675.html
Sent from the Debian User mailing list archive at Nabble.com.
--
To UNSUBSCRIBE, email to debian-user-requ
On 03/17/2013 05:12 PM, Stan Hoeppner wrote:
Which has alway been my understanding of it until so far. But I like to
repeat from my first email: I tried the debian installer again, but
even then it's not able to get a DHCP IP address using eth0. eth1 is
working fine. This is after a cold boot.
On 3/18/2013 3:57 AM, Casper Langemeijer wrote:
If I ifup both eth0 and eth1, ifconfig shows both interfaces. No
difference between output for them. (except ip/mac of course) The
counters get reset every few seconds for the broken eth0. Also: ethtool
shows nothing out off the ordinary except
On 03/18/2013 12:57 PM, Stan Hoeppner wrote:
On 3/18/2013 3:57 AM, Casper Langemeijer wrote:
If I ifup both eth0 and eth1, ifconfig shows both interfaces. No
difference between output for them. (except ip/mac of course) The
counters get reset every few seconds for the broken eth0. Also:
On 03/18/2013 02:23 PM, Casper Langemeijer wrote:
It gets even more weird: I had the NIC daughter card replaced, and the
problem still exists. I think I will use the machine in production as
it is now. Since I'm not using 4 ethernet ports, for me the issue is
not blocking. I hope someday
On 3/18/2013 2:44 PM, Casper Langemeijer wrote:
On 03/18/2013 02:23 PM, Casper Langemeijer wrote:
It gets even more weird: I had the NIC daughter card replaced, and the
problem still exists. I think I will use the machine in production as
it is now. Since I'm not using 4 ethernet ports, for
On 03/16/2013 07:19 PM, Brian wrote:
From that moment on eth0 is not working anymore. I get these kernel
messages:
[ 1796.583881] tg3 :01:00.0: eth0: transmit timed out, resetting
A search with tg3 transmit timed out resetting turns up some
possibilities for you to investigate.
Seriously?
On 3/17/2013 10:34 AM, Casper Langemeijer wrote:
Which has alway been my understanding of it until so far. But I like to
repeat from my first email: I tried the debian installer again, but
even then it's not able to get a DHCP IP address using eth0. eth1 is
working fine. This is after a cold
Hi List,
I've run into an issue trying to install a new PowerEdge R720 server
that arrived this week. It is equipped with a broadcom 5720 quad port
network interface daughter card. I installed wheezy on it. No problems!
The network interface works, and does not require any non-free firmware.
On Sat 16 Mar 2013 at 12:08:19 +0100, Casper Langemeijer wrote:
[Snip]
From that moment on eth0 is not working anymore. I get these kernel
messages:
[ 1796.583881] tg3 :01:00.0: eth0: transmit timed out, resetting
A search with tg3 transmit timed out resetting turns up some
14 matches
Mail list logo
