As far as I can see, 2.2 driver still contains this bug, once the freqs go to the maximum, they never go back. Just a report.
Yeah, the fix didn’t make it into 2.2.
As far as I can see, 2.2 driver still contains this bug, once the freqs go to the maximum, they never go back. Just a report.
Yeah, the fix didn’t make it into 2.2.