Online updates fixed the problem.   The computers now boot directly into 
a working WIFI state.

Thanks,
Ian Soutar


Ian Soutar said the following on 01/04/07 11:03 AM:
> Thanks for the change ...
>
> Tut there are three more details.
>
> 1/ The same problem occurs on the 5000 model.  You have to suspend and 
> wake the machine to get WIFI working. 
> 2/ The windows driver tool that configures ndiswrapper claims the 
> hardware does not exist with "Hardware no" message ... yet it installs.
> 3/ The etc/modules file needs to have ndiswrapper added to it before it 
> works after a boot ... although you still have to suspend the machine 
> and resume it before the WIFI comes alive. 
>
> The models once again are the Acer Aspire 3000 and the Acer Aspire 5000.
>
> Other than those bugs I have tried a lot of features in Feisty and they 
> all work beautifully.   In fact this is the ONLY distro besides puppy 
> linux that sees the WIFI internal modem.   I have tried Suse, Knoppix, 
> Fedora, Slax, DSL, Kanotix, Sidux and Linspire without any luck.   Puppy 
> linux worked because it disables ACPI and turns everything on.   Feisty 
> is the first that works 100% on WIFI except for the boot problem.   A 
> minor issue once you get it running.
>
> Thanks for a favourite distro.   I am a firmware developer and am 
> interested in helping.   I do microcontrollers and real time systems.   
> I also invent new machines for various industries and consumer 
> products.   Is there any area that might need some help (I am volunteering).
>
> http://www.microsec.net
>
> Ian Soutar
> Victoria BC Canada.
>
> Sitsofe Wheeler said the following on 01/04/07 12:23 AM:
>   
>> ** Summary changed:
>>
>> - ACPI-ndiswrapper on Aspire 3000 laptop doesn't wake until function button 
>> pressed
>> + bcm43xx using ndiswrapper does not work until after suspend and resume 
>> (Aspire 3000 laptop)
>>
>>
>>     
>
>

-- 
bcm43xx using ndiswrapper does not work until after suspend and resume (Aspire 
3000 laptop)
https://bugs.launchpad.net/bugs/38540
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to