We are closing this bug report because it lacks the information we need
to investigate the problem, as described in the previous comments.
Please reopen it if you can give us the missing information, and don't
hesitate to submit bug reports in the future. To reopen the bug report
you can click on t
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
AR5212 not enabled
https://bugs.launchpad.net/bugs/153376
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
** Changed in: linux (Ubuntu)
Sourcepackagename: None => linux
--
AR5212 not enabled
https://bugs.launchpad.net/bugs/153376
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https:/
Try hardy... maybe the problem is solved
--
AR5212 not enabled
https://bugs.launchpad.net/bugs/153376
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
I have a similar problem with an 8470WD card. ath0 fails to associate.
A simple but inelegant workaround is to do ifdown ath0 followed by ifup
ath0
[EMAIL PROTECTED]:/etc/network# dhclient
There is already a pid file /var/run/dhclient.pid with pid 10383
killed old client process, removed PID file
