SliTaz Forum

Guest

Guest

Wifi Cannot Work on Boot - eeepc 1000H netbook

I'd tried the en:guides:wifi-easy and wifi-hard. Somehow it won't work.

I'm using slitaz stable whereby the wifi is NOT wlan0... it's ra0.

I'd changed the network.conf file to the below.

=== START /etc/network.conf ===

INTERFACE="ra0"

# Dynamic IP address.

# Enable/disable DHCP client at boot time.

DHCP="yes"

# Static IP address.

# Enable/disable static IP at boot time.

STATIC="yes"

# Set IP address and netmask for a static IP.

IP="192.168.1.112"

NETMASK="255.255.255.0"

# Set route gateway for a static IP.

GATEWAY="192.168.1.1"

# Set DNS server for a static IP.

DNS_SERVER="192.168.1.1"

# Wifi connection.

# Enable/disable wireless connection at boot time.

WIFI="yes"

# Wifi interface (iwconfig) and ESSID.

WIFI_INTERFACE="ra0"

WIFI_ESSID="theessidname"

WIFI_MODE="managed"

WIFI_KEY="s:thepassword"

WIFI_KEY_TYPE="wep"

WPA_DRIVER=""

WIFI_CHANNEL=""

WIFI_IWCONFIG_ARGS=""

=== END /etc/network.conf ===

It won't work. The module rt2860sta is initialized on boot.

However, if I do the following as root in the terminal, the wifi will work...

iwconfig ra0 key open

iwconfig ra0 key s:thepassword

iwconfig ra0 essid theessidname

udhcpc -i ra0

Please let me know what should I do to make the wifi work from boot.

Thank you!

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: Wifi Cannot Work on Boot - eeepc 1000H netbook

1. Install ralink firmware:

http://distro.ibiblio.org/pub/linux/distributions/slitaz/packages/cooking/firmware-rt2x00-20110227.tazpkg

2. /etc/network.conf :

DHCP="yes" STATIC="no"   or    DHCP="no" Static="yes"

Don't say "yes" or "no" to both.

3. TazUSB : #tazusb writefs gz

Reboot if you fail to connect with wep change WIFI_KEY_TYPE="any"

Guest

Guest

Re: Wifi Cannot Work on Boot - eeepc 1000H netbook

May I know how do I 'install' the ralink firmware? I tried by entering in the terminal

./firmware-rt2x00-20110227.tazpkg

It showed many lines of error ending 'not found'.

Kindly advise.

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: Wifi Cannot Work on Boot - eeepc 1000H netbook

Open xterm become root:

su

password: root

Go to same directory as firmware-rt2x00-20110227.tazpkg

tazpkg install firmware-rt2x00-20110227.tazpkg

Guest

Guest

Re: Wifi Cannot Work on Boot - eeepc 1000H netbook

It's installed. But now it cannot detect ra0. There's only 'lo' listed in the Network Connections.

Do I have to load any modules? I'd taken out the rt2860sta from initialization.

mojo

Administrator

Registered: 2011-03-29

Posts: 2,174

Re: Wifi Cannot Work on Boot - eeepc 1000H netbook

#modprobe -r rt2860sta

#modprobe rt2860sta

#/etc/init.d/network.sh restart

If you can't connect:

Look for errors in dmesg

Turn off wep

lsmod =>look for modules rtxxxx than may be autoloading causing conflict

Post lspci -nn

Guest

Guest

Re: Wifi Cannot Work on Boot - eeepc 1000H netbook

Hi mojo,

After thinking thru, I suspect it's the 'key open' line that is missing.

So, I'd opened up /etc/init.d/network.sh and added a line as per below

==== network.sh snippet - START ====

        # encrypted network

        [ -n "$WIFI_KEY" ] && case "$WIFI_KEY_TYPE" in

            wep|WEP)

                iwconfig $WIFI_INTERFACE key open # this line added by me

                 IWCONFIG_ARGS="$IWCONFIG_ARGS key $WIFI_KEY"

                 iwconfig $WIFI_INTERFACE essid "$WIFI_ESSID" $IWCONFIG_ARGS

==== network.sh snippet - END ====

After adding the line - iwconfig $WIFI_INTERFACE key open - the wifi works on boot. Even then, I still have to click on the 'Network Status Monitor' icon on the systray and change to...

General tab > Connection > Name > ra0 (from 'Unknown')

In fact, I'd reinstalled slitaz-stable (without the slitaz-cooking's firmware-rt2x00-20110227.tazpkg). Slitaz detected and loaded the rt2860sta module. But it's not defaulted in the Network Status Monitor.

Hope this helps someone! Cheers!

Guest

Guest

Re: Wifi Cannot Work on Boot - eeepc 1000H netbook

One thing I'd noticed is that under the Network Status Monitor's General Tab, there's always Activity: Receiving...

Wonder why's tat?