Sk98lin driver

So did same thing, rebooted back to my normal working grub line to same kernel and didn't come up again. So did same thing as last time, rebooted to another system this time same system, but with the kernel with the sk98lin version 8. It came back up again and using it right now. So, the skge driver, though works, still has the same problem as was happening with the older drivers.

IF the Marvell Ethernet Controller doesn't come up, the skge won't wake it up. So, for the time being, sticking with the 8. Any further instructions? He is busy for the next 2 weeks but hopefully he'll come up with something after. Comment 10 Decibels UTC Thanks, maybe make a note to him that during my observations with this problem.

That anytime one of the drivers didn't work, Rebooting doesn't wake it back up! The only thing that consistently worked was to run the SysKonnect Diagnostics from Win2k. Sometime would have to run it a couple times, always passed, but when rebooted to Win2k or Gentoo it would start working again. Not too bad if in Windows all the time, but if run Linux most of the time or don't have Windows, then problem. It would be helpful if you could define "doesnt work" by posting things like dmesg, lspci -vv output, etc.

Then hopefully the skge author will be able to have a look. I haven't understood if the 0. Here is what is happening: 1. Most likely the PHY interrupt as result of auto-negotiation isn't happening, or there is a bug in the decode of the result. Or maybe you are connecting to an old box that doesn't do autonegotiation correctly driver should still be fixed. Must have done something wrong. Recompiled the kernel with skge as a module. Actually still had it in there, just stopped letting it load.

I'm not sure if module autoload files will obey parameters like that, so for now, make sure you are modprobing it manually with the debug param. The two log excerpts that you pasted show the exact same lines according to the timestamps suggesting that no output was produced the second time you loaded the module maybe the hardware was hung or something..?

Then check the debug stuff in the logs. That is why did it the other way also and got the second results in the other post. I did that last time also. This time I tried it again fresh reboot , with both skge and sk98lin commented out, removed net. Same results. It appears to load and nothing ie. However, after reboot into a dual boot alternative OS e. Even a hard reset or disconnecting the hardware from the power outlet revives the NIC.

Only booting back into linux 2. The only way to get the NIC back to work under Windows is to push the reset button after the successful initialization under 2. Other people seem to have the same problem. Without this patch, chip gets stuck in low power mode and never boots. Newer SysKonnect vendor code already had same patch. At least in my case power disconnect cured the problem. I have been using mainly debian based distros and all have been working to my ADSL capacity about KB download when updating packages etc.

Is this a driver problem, config problem or slow servers? I am really getting to like the Arch experience and solved a few problems by running Archie and working out why it would work and Arch wouldn't. Not sure why your downloads are so slow but all I can suggest is to try using the skge module instead of sk98lin. This module is available in kernel 2.

The skge module is a newer version of sk98lin and is supposed to offer better performance but does lack some of the features of the sk98lin module. I might give that a try thanks for the quick reply. I don't know why it is so slow when the other distros are ok. Kanotix is my current main distro great hardware support.