I have installed eeebuntu 3.0 on my 701 4G on SD card. Two points:
Wireless can be switched of and on again. But the connection itself not. Only a reboot will fix that.
The brightness buttons work but no feedback on then screen.

On the SSD is Ubuntu 9.04 installed with eee-control. With eee-control I see the response for the brightness buttons on the screen and the wireless becomes available again after a switch off/switch on action.

Is there a fix for this problem?

I have the same problems with the WiFi -- after turning it off and on again, it won't find no networks anymore.
Yesterday i thought i solved it with installing Wicd, because at one time it worked. But today i have the same problem again.

What bugs me more than the missing feedback of brightness changes is this: on battery power, the display goes back to "battery-normal"-brightness when coming from idle, even if i manually have set a higher brightness before it started idling.

Anyway, this 3.0 release is some great work! Thank you so much for your efforts and quick responses!

EDIT: Okay, i think i found the problem with the WiFi: It takes some minutes after turning off/on until it finds networks. I just looked again and suddenly there they were.


Cheers,
jitpleecheep.

Just install Wicd, that works.

Yes it does! Wicd seems much better than default.

No solution for me. When wifi is switched on again I see the blue light again, but no response from widc.Waited for 5 minutes. A refresh did not show anything. In plain ubuntu with eee-control no problem at all.

Run the wifi diagnostic.

Sorry, I am not an expert. Where can I find the wifi diagnostic?

If you're talking about wicd (not widc), there is a option called automatic connection when you set up any wireless connections. You have to check that.

Oh, my mistake, I forgot to post the link.

http://www.statux.org/wiki/index.php?ti ... _Utilities

WIFI Toggle

Issue:

* WIFI Toggle turns WIFI OFF, but not ON.

Impacts:

* Ubuntu Jaunty (9.04)

Solution:

* Add the following code from /boot/grub/menu.lst in the "defopts" section

pciehp.pciehp_force=1 pciehp.pciehp_poll_mode=1

The line should look similar to the following:

# defoptions=quiet splash force-hpet pciehp.pciehp_force=1 pciehp.pciehp_poll_mode=1
* run update-grub ie. sudo update-grub
* Reboot your computer.

Hi

Thanks for Base 3.0... looks good, ....but no consistent success for me with wireless on the 701SD

Fully updated to latest kernel and I have deleted the acpi and event scripts and added the grub edit....my problems

1. The wireless does not seem to be picked up on every boot... and IF the blue light indicator shows with a Fn+F2 press, the wireless does not auto connect...The settings are for auto connect ...I am not even sure how to restart manually.
2. The system hangs when the wireless is stopped with Fn+F2

Also, when the wireless does connect after boot, it requires a password entry to the keyring...something I would like to bypass if possible.

I just booted and the wireless was not active - no blue indicator and nothing on iwconfig. I pressed Fn+F2 and the blue indicator showed but no connection / wireless...so rebooted and it requests a login (I have it set to bypass login)...I login and it next asks for the keyring password...then connects automatically. So i stop the wireless with with Fn+F2 and the system hangs....I will need to hold the button down to stop the computer....It takes a double boot then to get the wireless going

Thanks for any advice

Modify menu.lst was the solution for me. Thanks.

I have solved it editing the "/etc/acpi/eeepc/eeepc-wifi-toggle.sh" script.

I am actually using madwifi drivers for my eeepc-701-non-surf, so I change this:

function radio_on{
/sbin/modprobe $WIFI_DRIVER 2>/dev/null

into this:

function radio_on{
/sbin/modprobe ath_pci 2>/dev/null

And also change it in the "radio_off" function in the same file.
It works without problem for me (at least at the moment I am writing this xD). I you are using the default eeebuntu drivers for wifi you should use ath5k or ath9k instead of ath_pci.
I am not sure, but maybe the variable $WIFI_DRIVER is not working correctly... :S

In the case where you aren't using stock drivers, you need to tell the script which driver to use overriding the autodetection, to do that set the following:

WIFI_DRIVER="ath_pci"

in your /etc/default/eeepc-acpi.local file. There is no need to change the script. Please repair it with apt-get install --reinstall eeepc-acpi-utilities (it will overwrite it with the next update anyway).

See the help for more information: http://www.statux.org/wiki/index.php?ti ... figuration

I have changed it and works. Thanks