Jump to content
Posted 15 January 2012 - 01:37 PM
Posted 16 January 2012 - 05:57 AM
Posted 16 January 2012 - 10:50 AM
I'm answering because you got no others. I'm not sure I can help. But I have a couple of suggestions.
You may need to use a different driver. Sometimes it happens that the wrong driver is selected by the OS. When that happens you have to manually make it select the right one, then mask the wrong one out so it doesn't keep picking it up. I don't know what driver that chip should use. But there are plenty of sites on google that can explain how to do the work, and there should be some that discuss that particular chipset.
I take it you're running network-manager (the default). Try replacing it with wicd and see if you still have the problem. I've had one of those packages flake out on me before, where the other would work fine.
Posted 16 January 2012 - 04:44 PM
Posted 16 January 2012 - 04:55 PM
If you download wicd from the repositories, it will uninstall network-manager. Rather, I should say they couldn't both exist on the same install in the past. Maybe that's changed since I last used anything where I wanted to use wicd.
Posted 25 January 2012 - 08:55 AM
It will be interesting to see what happens if auto ethernet decides to take the day off again.
0 members, 0 guests, 0 anonymous users