Joined: Mon Aug 03, 2009 7:47 pm Posts: 15
eeePC model: 4g surf (701
Aurora version: Other
in the wicd manager preferences tab type wlan0 for wireless interface.
curiously, beta 1 and 2 both installs 2 wicd clients that run simultaneously in the system tray. Don't know how to stop it from happening at start up.
worryingly, my wifi problem is still here, even after a full format of the HD and reinstall of new beta 2. mega unhappy about that. I warn users not to perform a 'dist-upgrade'
Joined: Sat Sep 20, 2008 9:10 pm Posts: 52 Location: Riga, Latvia
eeePC model: 901
Aurora version: Standard 3.0
Right, that did it! P.S. Bluetooth also doesn't seem to function properly - it shows "BT turned on" when you push the button, but doesn't really enable anything. If I recall correctly, the same problem was present in Base 3.0 when it was just released...
Edited: oops, I take back the part about wifi working. The second icon did disappear, but typing "wlan0" for "wireless interface" didn't do the trick - it still doesn't scan for networks. P.S. EEE901
Joined: Wed Aug 12, 2009 4:24 pm Posts: 7
eeePC model: 1000HE
Aurora version: Other
Just first impressions from a quick try-out last night:
Wifi not working, no network reported External screen enable not working correctly; resolution not correct, pressing Fn+F says something like "can't enable screen"; I haven't found a place where to fiddle with resolution manually.
Joined: Sat Sep 20, 2008 9:10 pm Posts: 52 Location: Riga, Latvia
eeePC model: 901
Aurora version: Standard 3.0
Another bug: when attempting to shutdown or reboot, sometimes(not always) it just returns you to the login screen. BTW still no wifi, even after following this instruction:
Quote:
Edit /etc/init.d/eeepc-restore.sh Find the line where it ifs eeepc-wifi.sh poweroff || true Comment the line out and save.
It seems that the radio itself works, and the software is to blame.
Joined: Sat Sep 20, 2008 9:10 pm Posts: 52 Location: Riga, Latvia
eeePC model: 901
Aurora version: Standard 3.0
I know that I've written a bit too much already, but I've been able to find the solution to my wifi problem. Just in case if anyone else needs it: 1) type "sudo iwconfig" in the terminal 2) copy the name of the current wireless interface(mine was ra0) into the corresponding line in wicd's preferences. 3) use WPA instead of WEP(in my case with WEP wicd was just writing "connecting..." until timeout, but WPA worked nicely).
Joined: Fri Jun 19, 2009 7:23 am Posts: 13
eeePC model: 901
Aurora version: Standard 3.0
I've got a few issues/requests/niggles to report too. Is someone going to set up a 'LXDE Beta 2 Issues' thread? Save this and the other one for the congratulations?
Joined: Mon Dec 15, 2008 1:55 am Posts: 1969 Location: El Puerto de Santa María, España
eeePC model: 1000HA
Aurora version: Beta 4.0
Toolz wrote:
I've got a few issues/requests/niggles to report too. Is someone going to set up a 'LXDE Beta 2 Issues' thread? Save this and the other one for the congratulations?
There's a whole forum for lxde. Just start a new topic.
_________________ Asus Eee 1000HA - Fuduntu 2012.1 Asus Eee 1000 - Aurora Beta 0.5 (EB4 beta 1 with all updates applied) (left on airplane) Asus G73JHA1 - Fuduntu 2012.1
Joined: Wed May 13, 2009 6:21 am Posts: 11
eeePC model: 900HD
Aurora version: NBR 3.0.1
arif wrote:
in the wicd manager preferences tab type wlan0 for wireless interface.
curiously, beta 1 and 2 both installs 2 wicd clients that run simultaneously in the system tray. Don't know how to stop it from happening at start up.
worryingly, my wifi problem is still here, even after a full format of the HD and reinstall of new beta 2. mega unhappy about that. I warn users not to perform a 'dist-upgrade'
This solved my issue. What a great community. I have a 900A -- if anyone has the same model and struggling to get wifi enabled, please let me know and I can help.
Joined: Wed May 13, 2009 6:21 am Posts: 11
eeePC model: 900HD
Aurora version: NBR 3.0.1
stigmaster wrote:
Right, that did it! P.S. Bluetooth also doesn't seem to function properly - it shows "BT turned on" when you push the button, but doesn't really enable anything. If I recall correctly, the same problem was present in Base 3.0 when it was just released...
Edited: oops, I take back the part about wifi working. The second icon did disappear, but typing "wlan0" for "wireless interface" didn't do the trick - it still doesn't scan for networks. P.S. EEE901
About bluetooth: I used this to install blueman. Added @blueman-applet line to the /etc/xdg/lxsession/LXDE/autostart. Blueman is working fine. I used to use blueman to use "Network Access Point" interface to tether to thru my phone. It was easy in gnome (network-manager)... I am trying to figure out how to do it using wicd. But bluetooth connectivity to all my devices working fine thru blueman.
Joined: Mon Feb 09, 2009 10:58 am Posts: 31
eeePC model: 1000
Aurora version: Other
stigmaster wrote:
I know that I've written a bit too much already, but I've been able to find the solution to my wifi problem. Just in case if anyone else needs it: 1) type "sudo iwconfig" in the terminal 2) copy the name of the current wireless interface(mine was ra0) into the corresponding line in wicd's preferences. 3) use WPA instead of WEP(in my case with WEP wicd was just writing "connecting..." until timeout, but WPA worked nicely).
I think this may be the same as opening Wicd manager, hitting preferences, and entering ra0 in the wireless box there. I had to do that, and then I saw this. Of course at this time I still need to F2 during boot to turn the wifi on, but this step is was necessary also.
Joined: Wed Aug 12, 2009 4:24 pm Posts: 7
eeePC model: 1000HE
Aurora version: Other
Started off with LXDEb2 and started the driver upgrade procedure... let's just say I have abandoned eeebuntu in favour of xubuntu 9.04 with Adam's kernel.
I installed to a USB stick (a full install not the live CD thing) instead of a hard drive because I didn't have a partition available for the exercise. Previous eeebuntu tries were on the HDD.
Some way through the procedure (at about 2nd boot) the display stopped displaying and no amount of ctrl+alt+bksp or ctrl+alt+del or rebooting brought back anything at all. I'm a linux neophyte so decided to go with something that works substantially instead of partially. As reported elsewhere, the external monitor didn't really work, the Fn button that is supposed to control it didn't work, wifi never worked etc etc. Even without Adam's kernel Xubuntu out of the box seems more functional. Based on my experience eeebuntu with LXDE is not 'beta' not even 'alpha'. The final straw was trying out Parted Magic and experiencing how well everything works out of the box. That's what I want in my Linux not the pre-alpha LXDE lame horse. I don't mean to sound harsh here... I guess this stuff is not for noobs...?
I guess that was my last try, I have basically tried all eee flavours by now. Am I missing something or is working Fn keys not worth all this?
Users browsing this forum: No registered users and 2 guests
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot post attachments in this forum