Comment 28 for bug 714862
Revision history for this message
| AceLan Kao (acelankao) wrote Re: Atheros AR3002 cannot be turned up/is not recognized. | #28 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
James,
Sorry, I didn't followup this issue for a while.
The atheros' engineer is in charge of making the code upstream and he said he already done that.
From what I see, there are 2 kind of chips with the same VID/PID(0cf3:3002) and the code in upstream kernel can enable another chip, but not the one we have.
The code in the dkms package is not possible to upstream, since it modifies the btusb module and will affect other chips.
I'll find out the h/w and do some more test soon to see if I can do any progress on this issue.
David Megginson,
It would be better to file a new bug for another chip, but I think I can give you the answer right away.
There is another dkms package for you, I just guess it might work on you platform, since you didn't give me the usbid, so I'm not sure if that will match.
After installing this dw1703 dkms package, you have to add one more file under /etc/modprobe.d/
cat dw1703.conf
install ath3k modprobe btusb; modprobe --ignore-install ath3k;
Try it, and please file a new bug if this is not working.