Phil,<br><br>Thanks for your response. I appreciate the work you're doing. Good luck fixing it.<br><br>The output of 'lsusb' is as follows:<br><br>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub<br>Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub<br>Bus 002 Device 002: ID 05ac:8300 Apple, Inc. Built-in iSight (no firmware loaded)<br>Bus 007 Device 004: ID 05ac:8242 Apple, Inc. IR Receiver [built-in]<br>
Bus 007 Device 003: ID 05ac:0229 Apple, Inc. Internal Keyboard/Trackpad (MacBook Pro) (ANSI)<br>Bus 003 Device 003: ID 05ac:8205 Apple, Inc. Bluetooth HCI<br>Bus 002 Device 006: ID 0cf3:9271 Atheros Communications, Inc. AR9271 802.11n<br>
<br><div class="gmail_quote">On Fri, Aug 3, 2012 at 2:40 AM, Phil Perry <span dir="ltr"><<a href="mailto:phil@elrepo.org" target="_blank">phil@elrepo.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">
<br></div></div>
Hi Andrew,<br>
<br>
It's also the same as this issue here:<br>
<br>
<a href="http://lists.elrepo.org/pipermail/elrepo/2012-August/001338.html" target="_blank">http://lists.elrepo.org/<u></u>pipermail/elrepo/2012-August/<u></u>001338.html</a><br>
<br>
so my reply to that is equally applicable.<br>
<br>
Can you post the output from running the 'lsusb' command, so we have the full details for your wireless controller.<br>
<br>
I'm hoping to find some time to look at this issue early next week (it's very much top of my list) to see if we can get it working again on 6.3 (no promises) as it seems to be affecting quite a few people.<br>
<br>
In the meantime I have no immediate workaround for you other than running the old kernel from before it broke, and as you recognise above there is a security risk involved with this. The level of risk will depend upon your individual circumstances and how you use your system so that is something for you to assess.<br>
<br>
Sorry we can't offer more by way of an immediate solution at the moment.<br>
<br>
Phil<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
elrepo mailing list<br>
<a href="mailto:elrepo@lists.elrepo.org" target="_blank">elrepo@lists.elrepo.org</a><br>
<a href="http://lists.elrepo.org/mailman/listinfo/elrepo" target="_blank">http://lists.elrepo.org/<u></u>mailman/listinfo/elrepo</a><br>
</blockquote></div><br>