SliTaz Forum
You are not logged in.
Installing on an Asus eee 900 notebook. SliTaz 5 installs, updates and works fine for about a day. Then both the wired ethernet and the wireless stop working. All the setting in the network.conf appear correct. Most frustrating is if I open Wi-Fi configuration it detects the signals just fine but after putting in the WPA Password it seems to not allow the connection and wlan0 does not show up under Connection Properties (on the task bar). Just shows eth0 and lo. Similar for the wired connection, if I turn off DHCP the task bar icon lights up like there is a connection but if I open it, it says disconnected. Also no joy if opening a browser.
I have re-installed several times with the same results. Works fine through updates, several shut downs and restarts, then the next day it doesn't work.
Added info, I have a eee 401 4g - Wi-Fi works fine, wired does not.
Offline
Have you updated any packages since it worked fine?
Here's pitfall.
For example, openssl updated about 3 days ago, and you need to update both: libcrypto, libssl, openssl. You'll get the problems with network connection if you upgraded one or two of that three packages.
I think, you don't need to reinstall SliTaz several times to solve problem.
Update system with the latest packages using command
[c]tazpkg up[/c]
Check the installed packages health using command
[c]tazpkg check[/c]
Also, your hard disk may slowly die. After a short time after reinstalling it can slowly ruin your files.
Offline
Good day Aleksej. Thank you for the quick reply. Firefox is the only package that I install after all of the updates run. I first ran into this problem several months ago. At first I thought I might have set up something wrong and would go through re installing. Since then I did not have time to work on the problem. I thought I would give it another go.
After any package install or update this time I would cycle it through with a reboot. This way if it failed I could perhaps spot what was causing it. But it doesn't fail that way. I also don't think it is the hard drive (it has a ssd) because none of the other packages fail. Also it fails in this very specific way.
ran tazpkg check and everything looked good.
Offline
Hi Gary,
Please share your system report made using TazPanel. AFAIK it contains many logs where we can find some useful information.
Also, please tell, do you have dual boot with the Windows? If yes, do you boot Windows before problem appear? Sometimes devices can't (or in turn, can) be properly initialized after they have been used in Windows.
Offline
The same issues occur with me. I have assembled a computer from old computer parts and installed SliTaz 4.0. It all worked fine until I got connected with the internet for the first time via Ethernet.
After a reboot the same problems occur with me as with egginabasket. I have included the log from the panel (I hope it's the right report). The PC has no WiFi capabilities, but I really need that Ethernet to work 
. I have executed the same commands as you mentioned above, but I could not detect an error. I am however, a first-time SliTaz user, so I might have missed have something.
Offline
Aleksej, here is a copy of my report. My need is the opposite of Saltbag, the Wi-Fi is what is important for me. I generated the report just after an attempt to connect. I get a signal just fine, but when putting in the WPA key, it does not connect.
Offline
@egginabasket: the boot log says "wlan0 is not a Wi-Fi interface, changing it." This comes from the network.sh init script, which looks for /sys/class/net/wlan0/wireless. Can you type:
[c]ls /sys/class/net/wlan0[/c]
and report the output?
Also, what if you *do not* update packages after installation? (What iso are you using: RC3 or Weekly?)
Offline
llev,
Here is what I tried;
Here is some of what I tried following on your suggestion.
ls /sys/class/net/wlan0/
came back with a set of switches
so I tried some and they just echo back !?
ls /sys/class/net/wlano/carrier
/sys/class/net/wlan0/carrier
ls /sys/class/net/
dummy0 eth0 lo tunl0 wlan0
cat /sys/class/net/wlan/operstate
down
I am using RC-3. If I don't upgrade the packages, it seems to work just fine. In fact it works fine after the upgrades and thru several reboots. When I start it up the next day that is when it stops connecting. It is frustrating me because one would think that this would be an easy fix.
As I stated in the original post, I have both a EEE pc 900 and EEE pc 401, they are very similar machines with the same chip set for wifi and ethernet. Yet, on one the wifi works and the other it does not. On both the ethernet stopped working. I will upload the report from the 401 machine for comparison when I get the time.
These are Slitaz only, not dual boot. Also, I have not been able to get them to connect upon boot, but I will worry about that when I get this first problem fixed.
Thanks for the suggestions.
Offline
Hi Gary,
so I tried some and they just echo back !?
ls /sys/class/net/wlano/carrier
/sys/class/net/wlan0/carrier
It seems like you're looking for the "cat" command to display content of the pseudo-file in question:
[c]cat /sys/class/net/wlan0/carrier[/c]
Offline
Here is the report from my eeepc 401, as you can see it uses the nearly the same hardware except for the screen and ssd configuration.
Additional info;
The hardware is not broken, I can boot Ubuntu, Mint, and Puppy off a thumb drive and everything works. So should Slitaz (At one point I did have an older version of Slitaz on there and it worked wonderfully.)
Why do I bother? I like the "feel" of Slitaz, it is light weight and fast on these older devices. So is Puppy, but puppy "feels" like something my 4 year old granddaughter would play with. Mint and Ubuntu have too much bloat ware.
Offline
Where I wrote "eeepc 401" it should be eeepc 701. Sometimes my fingers have a mind of their own.
Offline
ls /sys/class/net/wlan0/
came back with a set of switches
Give the output, please.
Offline
@egginabasket
How are you trying to connect? I have to use tazpanel to connect wireless in a Eee pc 1000.
I also have a problem with the connection to the AP being deauthorized if in console mode, connects fine in Lxde with tazpanel.
Offline
Ilev here is what I get;
ls /sys/class/net/wlan0/
addr_assign_type dormant mtu statistics
addr_len duplex netdev_group subsystem
address flags operstate tx_queue_len
broadcast ifalias phy80211 type
carrier ifindex power uevent
dev_id iflink queues wireless
device link_mode speed
roadie - I am not sure what you are saying. Specifically I don't know what AP or Lxde are. (Sorry, I am self taught in most of this.) However, you gave me the idea of playing around with Tazpanel. I found that on the 701 I could log in as root and stop and start the wlan0 AND start and stop the eth0. But starting one stopped the other!? This is what changed on this machine when I did the upgrade. (This is probably basic stuff.) Before the upgrade it seemed both would work depending on which I selected in the "network connection" drop down on the task bar.
Here is where I stand right now on the 900 machine. Trying the above process of logging in as root I can start and stop the eth0 (in tazpanel) so at least I have connectivity. Trying the same with wlan0 it stops the eth0 and starts the wlan0 but at this point it hangs at "scanning wireless interface..."
Now this may be important-when I go to the "network connection" drop down on the task bar it shows only eth0 and lo, it does not show wlan0.
Now if I use "Wi-Fi configuration" under "Preferences" drop down, it will show me the available networks but when I select my network it will ask me for the WPA password
but not connect. (If I select an open network it will also not connect.)
So what am I missing?
And thanks again everyone for all the input so far.
Offline
Does your WPA password have "strange" characters in it, like ampersand, hash, etc.? Or just letters and digits?
But starting one stopped the other!? This is what changed on this machine when I did the upgrade. (This is probably basic stuff.)
The fact that one stops when the other starts is the normal way SliTaz's network script works. I highly doubt the RC3 iso behaves differently.
Before the upgrade it seemed both would work depending on which I selected in the "network connection" drop down on the task bar.
I can't make any sense of this sentence (I'm not a native speaker of English): how can you say "/both/ work /depending on which/..."?
Also, AFAIK, the card selection in this drop down has no effect on actual network configuration, it just selects which device to report about in the task bar.
Offline
llev - Sorry if my statement was confusing. I will restate the problem as clearly as I can.
I now have connectivity through eth0. I still do not have connectivity through wlan0.
The card selection on the drop down does not have wlan0 listed.
No strange characters in the current WPA. And I also try to connect through an open connection I have available.
In Tazpanel trying to connect with wlan0 it stops the eth0 and starts the wlan0 but at this point it hangs at "scanning wireless interface..." and does not display the available networks.
If I try to connect using Wi-Fi configuration in the menu it will display the available networks but not connect.
Offline
Hi,
There was a bug in the "Wi-Fi configuration" tool, it wouldn't try to connect when you clicked "Start Wi-Fi". Please download and install the new version: http://cook.slitaz.org/cooker.cgi?download=slitaz-tools-boxes-962.tazpkg
It will probably not solve your problem but will give us a sound "working base".
Offline
Hi llev,
I tryed that, but no change.
I am including the Tazpanel log from my try incase there is somethig there that will help.
Thank you.
Offline
Thanks for the log. Can you paste the contents of [c]/etc/network.conf[/c] and [c]/etc/wpa/wpa.conf[/c]? (I think you cannot attach this, just paste it into your message; remove/hide your wifi keys before sending your post.)
Offline
llev - thanks again.
/etc/network.conf
# /etc/network.conf: SliTaz system wide networking configuration.
# Config file used by: /etc/init.d/network.sh
#
NETWORK_CONF_VERSION="2"
# Set default interface.
INTERFACE="eth0"
# Dynamic IP address.
# Enable/disable DHCP client at boot time.
DHCP="yes"
#
# Settings only for static IP address.
#
# Enable/disable static IP at boot time.
STATIC="no"
# Set IP address and netmask for a static IP.
IP="192.168.0.8"
NETMASK="255.255.255.0"
# Set broadcast address
BROADCAST="192.168.0.255"
# Set route gateway for a static IP.
GATEWAY="192.168.0.1"
# Set domain name
DOMAIN=""
# Set DNS server for a static IP.
DNS_SERVER="192.168.0.1"
#
# Wi-Fi settings.
#
# Enable/disable wireless connection at boot time.
WIFI="no"
# Set "yes" if you don't want to store networks you're already connected.
WIFI_BLANK_NETWORKS=""
#
# Wi-Fi settings for iwconfig.
#
# Wi-Fi interface. It can auto-search interface if value below is fail.
WIFI_INTERFACE="wlan0"
# WPA driver; default is "wext" (Wireless Extension).
WIFI_WPA_DRIVER="wext"
# Set the operating mode of the device. The mode can be "Ad-Hoc", "Managed",
# "Master", "Repeater", "Secondary", "Monitor" or "Auto".
WIFI_MODE="Managed"
# Set the operating channel in the device. Empty by default.
WIFI_CHANNEL=""
# Force the card to register to the Access Point given by the address, if it's
# possible. Empty by default to automatic mode.
WIFI_AP=""
#
# Wi-Fi settings for wpa_supplicant (for given network).
#
# SSID (network name)
WIFI_ESSID="grd"
# BSSID (optional), use this block to associate with the AP
WIFI_BSSID=""
# Wi-Fi security. Empty ("") for open network; "ANY" for trying many methods;
# "WEP" for WEP; "WPA" for WPA/WPA2-PSK; "EAP" for 802.1x EAP.
WIFI_KEY_TYPE="WPA"
# Password for WEP, WPA, EAP, WAPI, and ANY; both in ASCII or HEX form.
WIFI_KEY="********"
# Method for EAP: "PEAP", "TLS", "TTLS", "PWD".
WIFI_EAP_METHOD=""
# File path to CA certificate file (PEM/DER).
WIFI_CA_CERT=""
# File path to client certificate file (PEM/DER).
WIFI_CLIENT_CERT=""
# Identity string for EAP.
WIFI_IDENTITY=""
# Anonymous identity string for EAP.
WIFI_ANONYMOUS_IDENTITY=""
# Inner authentication parameters: "", "PAP", "MSCHAP", "MSCHAPV2", "GTC".
WIFI_PHASE2=""
/etc/wpa/wpa.conf
network={
ssid="HP-Print-36-LaserJet 200 color"
scan_ssid=1
network={
ssid="xfinitywifi"
scan_ssid=1
network={
ssid=""
scan_ssid=1
key_mgmt=NONE
priority=2
}
network={
ssid="grd"
scan_ssid=1
psk="********"
key_mgmt=WPA-PSK
priority=3
}
Offline
OK, there are missing closing braces in wpa.conf. Remove this file altogether (you have a backup here 
) and retry.
Offline
llev
Thank You! That worked!
Sorry I did not get back to you sooner. I got very busy last week. I am amazed that you spotted the missing brace. It took me a week to find a missing comma back in the old Fortran days.
Thanks again,
egg
Offline
Hi,
You're welcome! Missing braces are easy to spot because they come in pairs :-)
There was a bug in network.sh which is probably the culprit; it affected EAP and has been corrected here. Thanks for having indirectly found it!
So you had a missing comma, and neither your code editor nor the compiler gave you enough hints to figure this out? (I still do Fortran occasionally, so maybe /your/ "old Fortran days" date back to punchcards?)
Offline
Yes, punchcards. I was just learning and the professor though that frustration was a great teaching tool. Keep up the good work.
egg
Offline
[ Generated in 0.022 seconds, 7 queries executed - Memory usage: 1.6 MiB (Peak: 1.77 MiB) ]