wireless not responding with soft/hard switches on AsusPro57sn

[Silvio]

I am testing on Ubuntu Hardy64 version full upgraded. the acpi.support is 0.108
The asus I am testing is a Pro57sn (alias M51Sn Santarosa/T9300)
Net configuration is : roaming

keyboard Functionkey+F2 button is not properly working.
out of my tests I can say that the first keypress (Fn+F2) it disable the wole wireless + BT systems and the light goes off.
Pressing again as second time the fn+2f2 the lights will go ON for both WIFI/BT but only BT functionalities will work.

When I try to execute the second keypress to reactivate them, the wole system will freeze for about 30 seconds (mouse is frozen too)
After this 30/40 secs the system will become again alive, and on the menubar the wifi+bt icons will appear.

wifi can explore and get the net essid but then is unable to handshake with it

I've also noted that after this, if the pc is halted, it will not shut down properly as during its last shuttingdown operations it will display a broken gray windows and will hung freezed there as dead 4ever.

To completelly shut it down I had to force it pressing power button for >4sec.

Note : there is also on my laptop an hard switch. even that is not working in proper way even if seems complitelly different from the above soft switch and I guess is another bug

Please accept my apologises for my terrible english

ciao

[Nicolò Chieffo (yelo3)]

can you please check in a console using this command
sudo tail -f /var/log/acpid

and then press the hotkey since the system goes frozen.
then attach the result here

Does this happen after a suspend/resume? or just a normal boot?

[Silvio (winky)]

Nicolò ciao and ty so much for cool and most welcomed interest on this case.

I did not tried yet after susppend/resume situation
the above is on normal boot.
I attach to this post the konsole log file of what you requested me.

unfortunatelly the line where the log ends up is where i try to reconnect to the desired essid w/o any result.
the system seems working at this stage unless wifi that wont connect. But if I shut the PC down the process starts kool (showing also the newly added ubuntu animated bar)at the very end the system wont shut off. it wil keep screen ON with garbage on the screen (90%dark gray and 10 % light gray spots on various part of the screen - random order)
to really shut off the PC the power button is to be pressed for > than 4 secs.

at pc restart (new boot) wifi is conecting immediatelly to the net w/o any problem.
I hope to have clarified better, I will be back on this by this evening.

ciao

[Nicolò Chieffo (yelo3)]

Tell me if the problem occurs even without using the hotkey, but executing
sudo /etc/acpi/asus-wireless.sh
as may times as they are necessary (as it was your hotkey)

If it does not crash, then for sure the problem is not acpi-support
related. but it's a kernel/driver problem and I cannot help you.

Than you can try 2 things: the first is run the command
ps aux
after the problem has occurred, and attach the result, in particoular
look for a process in [defunc] state.

Another thing you can try is to boot ubuntu without the options "quiet slpash"
to do this, when you are at boot prompt, you have to select ubuntu
with the arrow keys, and then hit the key 'e'. then select the row
that starts with "kernel ..." and hit again 'e'. now you can edit the
line: go to the end, and remove both "quiet" and "splash". hit enter
and then hit 'b'. The boot will start and you will see it verbosly.
Now make the error happen and switch the pc down. Then attach here
what you see on the screen when the progress blocks.

Bye

[Silvio (winky)]

Nicolò, Happy Easter.
sry for long time reply but i'm not at home until next week.

I did the first test
sudo /etc/acpi/asus-wireless.sh and that will shut wireless OFF correctly

then pressing on Fn+F2 will work great and wirless will work perfectly.

I will try all other tests u requested me as soon i get back home.

ciao

[Daniel T Chen (crimsun)]

Is this symptom still reproducible in 8.10 or 9.04?

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!