bcm43xx using ndiswrapper does not work until after suspend and resume (Aspire 3000 laptop)

On small addition ...

Is there a shell command that will wake the machine???

Ian.

Not a malone bug

Please forward this bug report to the correct website .. what is malone? I was told it was for Dapper Drake bugs.

(Ian: You had the correct "website" but you filed the bug against the wrong package. The Malone package is for bugs in the bug tracking website itself...)

Thanks ... I was directed to post there by a "helpful" person. I guess
I should study the site first.

Ian.

Sitsofe Wheeler wrote:
> (Ian: You had the correct "website" but you filed the bug against the wrong package. The Malone package is for bugs in the bug tracking website itself...)
>

There appear to be two issues here:
1. ndiswrapper does not wake up 'till you hit the Fn plus Sleep (Z) button with broadcom modem
2. ndiswrapper is not loaded automatically at boot.

Just out of interest, can you include the output of
lspci
?

Ian:

I forgot to mention that bugs that have more than one issue within them are less likely to be resolved. Your best bet is to spin out one of the issues into its own bug and dedicate the bug to the remaining issue.

I am now using an Aspire 5000 ... very similar but I cannot get the ACPI
sleep command to work and therefore cannot get the ndiswrapper to work
at all. Previously I had been placing ndiswrapper in the /etc/modules
file. This saved me from typing modprobe ndiswrapper before using the
wifi. I will run your test later tonight.

Ian.

Sitsofe Wheeler wrote:

>There appear to be two issues here:
>1. ndiswrapper does not wake up 'till you hit the Fn plus Sleep (Z) button with broadcom modem
>2. ndiswrapper is not loaded automatically at boot.
>
>Just out of interest, can you include the output of
>lspci
>?
>
>
>

Basically the main bug is that the wifi card does not normally wake up!

Thanks,
Ian

Sitsofe Wheeler wrote:

>Ian:
>
>I forgot to mention that bugs that have more than one issue within them are less likely to be resolved. Your best bet is to spin out one of the issues into its own bug and dedicate the bug to the remaining issue.
>
>
>

Now I am on an Aspire 5003WLMi and the same problem.

Here is the result of your command ... hope it helps

0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] 760/M760 Host
(rev 03)
0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS] SG86C202
0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL
Media IO] (rev 25)
0000:00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus
Controller
0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE]
0000:00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem
Controller (rev a0)
0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems
[SiS] Sound Controller (rev a0)
0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 0f)
0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0
Controller (rev 0f)
0000:00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 2.0
Controller
0000:00:04.0 Ethernet controller: Silicon Integrated Systems [SiS]
SiS900 PCI Fast Ethernet (rev 91)
0000:00:06.0 CardBus bridge: Texas Instruments PCI1410 PC card Cardbus
Controller (rev 02)
0000:00:0b.0 Network controller: Broadcom Corporation BCM4318 [AirForce
One 54g] 802.11g Wireless LAN Controller (rev 02)
0000:00:18.0 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] HyperTransport Technology Configuration
0000:00:18.1 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Address Map
0000:00:18.2 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] DRAM Controller
0000:00:18.3 Host bridge: Advanced Micro Devices [AMD] K8
[Athlon64/Opteron] Miscellaneous Control
0000:01:00.0 VGA compatible controller: Silicon Integrated Systems [SiS]
661/741/760/761 PCI/AGP VGA Display Adapter

Ian

Sitsofe Wheeler wrote:
> There appear to be two issues here:
> 1. ndiswrapper does not wake up 'till you hit the Fn plus Sleep (Z) button with broadcom modem
> 2. ndiswrapper is not loaded automatically at boot.
>
> Just out of interest, can you include the output of
> lspci
> ?
>
>

Thanks for that ... things have not changed. Hopefully the new release
will have that bug fixed.

Ian.

Matthew Lange wrote:
> ** Summary changed:
>
> - ACPI-ndiswrapper on Aspire 3000 lap.
> + ACPI-ndiswrapper on Aspire 3000 laptop doesn't wake until function button pressed
>
>

This shouldn't be an issue any more as Broadcom cards should be using the include Broadcom drivers now, no longer needing ndiswrapper.

Can anyone still confirm this issue on the current stable releases?

I strongly recommend to open one bug per issue.

Please give more info and test with the latest version. The output of dmesg after waking up and hitting the button may be useful.

this must be from a year ago. The problem persists ... But I don't mind it.

Ian

(palm cell mail)

-----Original Message-----

From: Andreas Gnau <email address hidden>
Subj: [Bug 38540] Re: ACPI-ndiswrapper on Aspire 3000 laptop doesn't wakeuntil function button pressed
Date: Tue Mar 27, 2007 5:31 pm
Size: 300 bytes
To: <email address hidden>

I strongly recommend to open one bug per issue.

Please give more info and test with the latest version. The output of
dmesg after waking up and hitting the button may be useful.

--
ACPI-ndiswrapper on Aspire 3000 laptop doesn't wake until function button pressed
https://launchpad.net/bugs/38540

Ian:

The problem still persists in Feisty?

I have not run Feisty yet.

Ian.

Sitsofe Wheeler said the following on 28/03/07 12:31 AM:
> Ian:
>
> The problem still persists in Feisty?
>
>

Maybe I'm a little bit confused, tired or maybe it is my lack of language skills, but could you please outline the problem again? Is this rather an ACPI-problem or an ndiswrapper-problem?

From what I understood your wifi (or is it the modem?) which you are running with ndiswrapper works without any problems, but you have to push a keycombo in order to make it work again after waking the laptop up. Please provide lspci and lspci -n, urls to the driver(s) and the output of dmesg after enabling it again after waking up.

I believe it is an ACPI problem. The WIFI modem is normally asleep and
cannot be used until the computer is put to sleep and awakened again.
It is not an ndiswrapper issue although it is necessary to use
ndiswrapper. There is a light on the computer that shows the WIFI is
awake and running. After a cold boot you cannot use the WIFI until you
do the sleep / wake thing.

I will try the test when I get home ... both the Acer 3000 and Acer 5000
face the same problem.

Ubuntu is the ONLY distro that allows the WIFI to wake up ... so you
guys have it almost right!

Actually that is not quite true ... Puppy linux, when you use the kernel
command acpi=off causes all peripherals to wake up. In this case it
works fine but of course the computer cannot be put to sleep or to
hibernate.

Ian.

Andreas Gnau said the following on 28/03/07 11:20 AM:
> Maybe I'm a little bit confused, tired or maybe it is my lack of
> language skills, but could you please outline the problem again? Is this
> rather an ACPI-problem or an ndiswrapper-problem?
>
> >From what I understood your wifi (or is it the modem?) which you are
> running with ndiswrapper works without any problems, but you have to
> push a keycombo in order to make it work again after waking the laptop
> up. Please provide lspci and lspci -n, urls to the driver(s) and the
> output of dmesg after enabling it again after waking up.
>
>

I did a clean install of Feisty Beta and the problem still happens.
Ndiswrapper was required to get the WIFI internal modem working.

But in addition, upon a new boot it does not work. You have to sleep
the machine and wake it up ... then the lights flash on the front and it
works.

This is true for both an Acer Aspire 3000 and an Aspire 5000.

So in summary you have to put the machine into a suspend mode and wake
it up. Suddenly the WIFI works. So on a clean boot the ACPI works
for all the peripherals to bring them on line except the WIFI card.
Suspend the machine and wake it up and ... it works. But on the next
clean boot it is asleep again.

Ian.

Ian Soutar said the following on 28/03/07 11:37 AM:
> I believe it is an ACPI problem. The WIFI modem is normally asleep and
> cannot be used until the computer is put to sleep and awakened again.
> It is not an ndiswrapper issue although it is necessary to use
> ndiswrapper. There is a light on the computer that shows the WIFI is
> awake and running. After a cold boot you cannot use the WIFI until you
> do the sleep / wake thing.
>
> I will try the test when I get home ... both the Acer 3000 and Acer 5000
> face the same problem.
>
> Ubuntu is the ONLY distro that allows the WIFI to wake up ... so you
> guys have it almost right!
>
> Actually that is not quite true ... Puppy linux, when you use the kernel
> command acpi=off causes all peripherals to wake up. In this case it
> works fine but of course the computer cannot be put to sleep or to
> hibernate.
>
> Ian.
>
>
> Andreas Gnau said the following on 28/03/07 11:20 AM:
>
>> Maybe I'm a little bit confused, tired or maybe it is my lack of
>> language skills, but could you please outline the problem again? Is this
>> rather an ACPI-problem or an ndiswrapper-problem?
>>
>> >From what I understood your wifi (or is it the modem?) which you are
>> running with ndiswrapper works without any problems, but you have to
>> push a keycombo in order to make it work again after waking the laptop
>> up. Please provide lspci and lspci -n, urls to the driver(s) and the
>> output of dmesg after enabling it again after waking up.
>>
>>
>>
>
>

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)
>
>

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)
>>
>>
>>
>
>

Ian:
Thanks for reporting back on this. It would be useful if you could visit https://bugs.launchpad.net/malone/+bug/38540 , click on the arrow to the left of ndiswrapper at the top and change the Status dropdown to "fix released" before clicking on save changes.

Your offer for help is much appreciated but I fear it might have been posted to the wrong forum (in a bug tracker it is too easy to overlook). I would suggest that a better place to post something like this might be one of the mailing lists like this one: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss or if you can get specs for the hardware that you are building firmware for then I recommend talking to Greg KH - http://www.kroah.com/log/linux/free_drivers.html because the Linux community will build and maintain drivers for it. There is also bug squashing of various forms which can be read about here https://wiki.ubuntu.com/HelpingWithBugs . More about the different ways to participate in Ubuntu can be read on http://www.ubuntu.com/community/participate

I'm sure your help is wanted - it's just working out the best place to apply it!

It looks like this was not an ndiswrapper-problem, rather an ACPI-one. The reporter didn't specify which package fixed it.