So this problem is probably that the Marvell yukon ethernet controllers do not resume from suspend within the time allotted by spec, which sometimes is masked by other devices like an extra sata controller in my case and apparently was also previously masked by the calibration delay that mlx git bisected down to. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the ‘needs- upstream- testing’ text. Just in case here are my outputs for the following commands, it might give some more info: November 25th, 5. Enter “modprobe sk98lin” Have fun This package provides the sk98lin kernel module s for Marvell:
|Date Added:||1 March 2007|
|File Size:||46.73 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
Ubuntu Manpage: msk — Marvell/SysKonnect Yukon II Gigabit Ethernet adapter driver
Bug tracking moved to ykkon November 24th, 3. You need to log in to change this bug’s status. To post a comment you must log in. To load the module manually, proceed as follows: Then when I performed the bisection, the kernel version according to Makefile was 3.
[SOLVED] Marvell Yukon for Scientific Linux
This information was last pulled 21 hours ago. If you need to reset your password, click here. If the mainline kernel does not fix this bug, please add the tag: This package provides the sk98lin kernel module s for Marvell: The ubuntu-kernel-team is being unassigned from this bug report.
Compile the kernel error [ failed ] I have no internet connection so how can I install “sudo apt-get install ethtool” from Ubuntu. Fix was commited as cc7cbc56f72 d28baaa6 a0ca Sat Jun 2 November 25th, 5.
CONFIG_SKY2: SysKonnect Yukon2 support (EXPERIMENTAL)
I finally plugged in LAN cable and was henceforth able to connect to internet. As you see everything went right, it even told me to have fun, with what i have problems. You need to log in to change this bug’s status. I post the results of various different commands: If so, could you please test for this with the latest development release of Ubuntu?
The information about this bug in Launchpad is automatically pulled daily from the remote bug. You are not directly subscribed to this bug’s notifications. Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part limux the bug triage process.
To post a comment you must log in. That commit for Hardy was actually in Ubuntu- 2. No bug has been created upstream. November 24th, 4.
Leann Ogasawara leannogasawara on The problem only seems to occur when I wake up the system by opening the lid. Brad Figg brad-figg on This information was last pulled 6 hours ago. I should also note that this appears to affect more than just Linux.
Here’s dmesg grepped for sky2. You are not directly subscribed to this bug’s notifications. I just realized something I changed on my system when I reconfigured it which turns out to have allowed the nic to work previously.
The solution is to simply patch the binary kernel driver sky2.