can't activate wifi

Hi,

I also am a 'victim' of this bug, but it is not the fault of eee-control.
It somehow has to do with how the wireless gets enabled and disabled.
*If your system booted with wifi on, the wifi is recognized, then you
disable it, it will just disable the radio of the wifi.
*If your system boots without wifi the Eeepc disables the wifi also in the
BIOS. The wifi is not recognized. If you later try to turn it on, it is
still not recognized. You have to reboot to get it recognized.

This is something that is the 'fault' of the Linux kernel or how the Eepc is
disabling the wifi (in the BIOS). So you should file a bug in launchpad
against the 'linux' package, and/or at the linux kernel bugzilla.

greetings,

On Sun, May 30, 2010 at 10:56 AM, yamo <email address hidden> wrote:

>
> ** Attachment added: "/var/crash/_usr_bin_eee-control-tray.1000.crash"
>
> http://launchpadlibrarian.net/49348340/_usr_bin_eee-control-tray.1000.crash
>
> --
> can't activate wifi
> https://bugs.launchpad.net/bugs/587443
> You received this bug notification because you are the registrant for
> eee-control.
>

--
met vriendelijke groet/kind regards,

Maarten Fonville

I'm not sure to really understand your message.
Could you create a new bug like you said, I will mark this bug as duplicate of your kernel bug?

Thanks in advance,

Sorry for a late response this time, have been busy :)
The bug is not within eee-control.
You should file a new bug to the 'linux' package on launchpad, describing this bug.

The real bug is in short:
'If I disable the wireless device on my machine with a 'soft' switch it is turned of properly. But when I reboot (and try to enable my wireless) the device is not even recognized anymore. It isn't even listed in lspci.

I already did change the package to 'linux' now for this bug, but am not sure whether it will be picked up by the people who can do anything about this.

Thanks for your replies since this bug report I didn't had it.

yamo,
   Since you haven't seen this for a bit, are you satisfied that this can be closed and then reopened should you encounter it again?

Thanks!

~JFo

Well, I still have this problem myself.
I just don't know in how 'easy' it is to fix. Since the main problem seems to be that when the Wi-Fi is switched off, at the next boot it is also automaticall considered 'switched off' in the BIOS (there is a setting there) and if you then switch it on with the fn+F key, the light for the Wi-Fi is turned on the laptop, but the device doesn't appear in lspci and the kernel doesn't see anything happening...

I tried today I had to witch on switch off and switch on (I don't have count but I made it more that one time) and the second test I switch on and it works...

But apport said that eee-control-tray crashed again

 Hi,

Maarten Fonville a tapoté, le 21/06/2010 22:39:
> Well, I still have this problem myself.
> I just don't know in how 'easy' it is to fix. Since the main problem seems to be that when the Wi-Fi is switched off, at the next boot it is also automaticall considered 'switched off' in the BIOS (there is a setting there) and if you then switch it on with the fn+F key, the light for the Wi-Fi is turned on the laptop, but the device doesn't appear in lspci and the kernel doesn't see anything happening...

In my eeepc wifi is on Fn F2 and I can switch off wifi with this Fn F2
but not witch on!

With eee-control-tray 0.9.6 I can switch on but, I have to click on
wifi more than one time to make wiki working.

--
Stéphane Grégoire
<email address hidden>
http://pasdenom.info

Another crash today.

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]