Sorry for the late answer, I was on holiday. removing the madwifi and updateing to the latest version of the restricted modules worked.
When I installed it the WLAN had some very hidden issues. I could connect to a network and once I had connected, the networkmanager saved the profile and everything was fine. But when I entered the wrong values into the network manager, e.g. AES instead of tkip, the card failed to do anything, anymore. e.g. iwlist scan wouldn't work anymore, connecting to newtowrks wouldn't work anymore. Even after a restart, it was sometimes impossible to connect again. I disabled some things in the BIOS (like Don't put my pci devices to sleep) and now it works. I really have a lot more trouble with other tasks like hibernate, flickering flash with fullscreen movies, long boot time, etc. But I will fix that peu a peu. Thanks for your help, I really have some more trust now in the autoupdate function, since I realize, that it probally was a conflict caused by me installing the madwifi. by the way here is a comic, which pretty much accounts for me, too (approximately week six now) (Don' forget to hove your mouse pointer over it, to see the 'hidden' extra) http://xkcd.com/456/ Thanks you, Sebastian Dimitrios Symeonidis wrote: > I would suggest you remove the built-from-source version (run 'sudo make > uninstall' in the directory of the madwifi source code you used). > Then upgrade again to the latest version of the restricted modules, and type > 'sudo modprobe ath_pci' to load the module... > -- Support bottom-up innovation http://wiki.cofundos.org/About -- AR5212/AR5213 driver failure after update today from .13-19.44 to 45 https://bugs.launchpad.net/bugs/247577 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
