|Date Added:||18 October 2014|
|File Size:||15.89 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Login [x] Log in using an account from: I can also confirm that this problem is also present in the latest RHEL5.
Is there anything further I can provide to help debug this? Warm booting to Linux from Linux works fine, but when warm booting to Windows, the interface isn’t detected. Find More Posts by HappyTux.
This interface is used on all recent ASUS motherboards e. Comment 27 Neil Horman Link is up at Mbps, full duplex, flow control none. Rodney rodney-jokerst wrote on I presume if I ever try installing Dapper directly on this system networking will be unavailable as this bug was introduced with the last mafvell before release as far as I can tell.
Wonderful, when is the next Dapper daily image going to be pushed out? Comment 42 Andy Margell Comment 23 Greg Bailey If you’d like to contribute content, let us know.
CONFIG_SKY2: SysKonnect Yukon2 support (EXPERIMENTAL)
You are not directly subscribed to this bug’s notifications. You can then apt-get update and dist-upgrade to get the latest kernel.
Within 30 minutes tx timeouts will kill the network. Marvell shipping broken firmware is completely unpublicised or acknowledged, however updated firmware is available through your motherboard vendor, so all hope it not lost after all Comment 31 Pete Philips You can take a look at this bug: Or rather, is this fix in the current dapper Daily Marveell for May 15 or do we need to wait another day?
Also of note, I’m now getting a ton of errors that look like this before the output I mentioned a few replies ago:. The interface came back up, and I get another round of the MUTEX errors, but no notification that the interface maevell down again.
Note You need to log in before you can comment on or make changes to this bug. If you need to reset your password, click here. Please let me know if you need any other versions: I have a Toshiba Tecra A3 and since I re-installed the marvel driver from Marvell, my connection works perfectly.
ethernet driver problems Marvell 80E (sky2)
Problem and solution is described in: Please report this failure to th PCI maintainer and include system chipset information. Please test it out and report results. Also of note, I’m now getting a ton of errors that look like this before the output I mentioned a few replies ago: You can find the srpm here: Because I marvlel install the driver manually, I don’t shut my laptop down and it’s been 1 week now and everything is still fine.
Comment 4 Andy Gospodarek I will be leaving this driver in for my 2. Looking at the backtrace above, I put your oops in this section of code: Comment 34 Pete Philips