Excerpts from Anthony Campbell's message of 2011-06-23 13:06:54 +0200: > On 23 Jun 2011, Philipp Überbacher wrote: > > Hi Anthony, > > I had similar problems in the past. Seemingly working wireless but not > > really. In my case it boiled down to drivers that didn't really work, > > but this was a broadcom chip. I guess the semi-open drivers still don't > > work for BCM4312 LP-PHY, although they should since a couple of kernel > > versions. > > > > Anyway, wicd didn't help when troubleshooting and on IRC I met a guy who > > said he was the maintainer and using networkmanager himself.. > > > > My suggestion is to, somehow, make sure the driver works for your chip > > and then configure everything manually, using wpa_supplicant directly if > > necessary (not THAT hard). If you can't get it to work that way it won't > > work any other way. > > > > Once it works you can use whatever suits best. Personally I don't use > > wicd anymore but a (possibly Arch Linux specific) script called netcfg > > which is simple and sufficient for most use cases. > > > > Regards, > > Philipp > > > > > Thanks, Philipp - you were right and gave me the clue. There are two > modules available, ath5k and ath9k. I was using ath5k because that is > what the docs talk about, but when I changed to ath9k the connection > came up correctly. Excellent! > > Anthony
Glad to be of help :) Regards, Philipp -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1308829234-sup-5222@eris
