If you've got the firmware enabled then that should be all you need. Is
it just that the scan doesn't work? Can you manually connect to the
nearest access point?
Chris
michael37 wrote:
>> Hi,
>>
>> Did you use the restricted drivers manager to reload the firmware? If
>> you look at the dmesg output you'll probably see that the firmware has
>> changed from the 2.6.22-12 kernel.
>>
>> Chris
>>
>
> I never had 2.6.22-12 kernel installed -- my initial upgrade to Gusty
> came with 2.6.22-13 kernel.
>
> I looked through dmesg and it doesn't say anything about firmware
> version unless firmware loading fails.
>
> I confirmed that firmware is enabled in the restricted drivers manager
> and that I am using the "blessed" version 3 of the firmware from
> http://linuxwireless.org/en/users/Drivers/b43#devicefirmware
>
>
Hi Michael,
If you've got the firmware enabled then that should be all you need. Is
it just that the scan doesn't work? Can you manually connect to the
nearest access point?
Chris
michael37 wrote: linuxwireless. org/en/ users/Drivers/ b43#devicefirmw are
>> Hi,
>>
>> Did you use the restricted drivers manager to reload the firmware? If
>> you look at the dmesg output you'll probably see that the firmware has
>> changed from the 2.6.22-12 kernel.
>>
>> Chris
>>
>
> I never had 2.6.22-12 kernel installed -- my initial upgrade to Gusty
> came with 2.6.22-13 kernel.
>
> I looked through dmesg and it doesn't say anything about firmware
> version unless firmware loading fails.
>
> I confirmed that firmware is enabled in the restricted drivers manager
> and that I am using the "blessed" version 3 of the firmware from
> http://
>
>