l...@gnu.org (Ludovic Courtès) writes:
> l...@gnu.org (Ludovic Courtès) skribis:
>
>> When switching from 4.0.5 to 4.1.2, I noticed that my ath9k-based
>> ThinkPenguin WiFi dongle would no longer work (“Resource unavailable”
>> when running ‘iwlist xxx scan’, etc.)
>
> I’m happy to report that thi
l...@gnu.org (Ludovic Courtès) skribis:
> When switching from 4.0.5 to 4.1.2, I noticed that my ath9k-based
> ThinkPenguin WiFi dongle would no longer work (“Resource unavailable”
> when running ‘iwlist xxx scan’, etc.)
I’m happy to report that this is fixed by upgrading the ath9k firmware
from 1
Hello,
Sorry, can't help really, but…
Ludovic Courtès writes:
> l...@gnu.org (Ludovic Courtès) skribis:
>
>> When switching from 4.0.5 to 4.1.2, I noticed that my ath9k-based
>> ThinkPenguin WiFi dongle would no longer work (“Resource unavailable”
>> when running ‘iwlist xxx scan’, etc.)
>
> Thi
l...@gnu.org (Ludovic Courtès) skribis:
> When switching from 4.0.5 to 4.1.2, I noticed that my ath9k-based
> ThinkPenguin WiFi dongle would no longer work (“Resource unavailable”
> when running ‘iwlist xxx scan’, etc.)
This is still broken in 4.1.6. Is anyone using a similar setup?
Ludo’.
l...@gnu.org (Ludovic Courtès) writes:
> l...@gnu.org (Ludovic Courtès) skribis:
>
>> With all that in mind, I’m inclined to use 4.0.8 as the default kernel
>> for the release (specifically, as the default value of the ‘kernel’
>> field.)
>
> Done in dcd9c25.
>
> We’ll of course revisit that after
l...@gnu.org (Ludovic Courtès) skribis:
> With all that in mind, I’m inclined to use 4.0.8 as the default kernel
> for the release (specifically, as the default value of the ‘kernel’
> field.)
Done in dcd9c25.
We’ll of course revisit that after the release.
Ludo’.
Hello!
When switching from 4.0.5 to 4.1.2, I noticed that my ath9k-based
ThinkPenguin WiFi dongle would no longer work (“Resource unavailable”
when running ‘iwlist xxx scan’, etc.)
For a while, I suspected a firmware miscompilation but then noticed that
using the previous, known-good firmware did