You are not logged in.
Pages: 1
hey folks,
a couple weeks ago i installed slitaz rolling on a friends laptop. all worked well, apart from connecting to his wifi network. i dont use wifi at home that much, but when i tried it recently i got the same error as my friend did (message below).
i usually connect via
/etc/init.d/network.sh restart /path/to/configFile
upon trying it now (i usually update packages when there are updates) i get the following:
root@slitaz:/home/tux # /etc/init.d/network.sh restart /home/tux/.network/WiFiKenny
Loading network settings from /home/tux/.network/WiFiKenny
Stopping all interfaces
Killing all daemons
Shutting down Wi-Fi card
Stopping all interfaces
Killing all daemons
killall: udhcpc: no process killed
Shutting down Wi-Fi card
Configuring Wi-Fi interface wlan0... [ Done ]
Change network settings in /etc/wpa/wpa.conf
Starting wpa_supplicant for any key type...
Successfully initialized wpa_supplicant
Line 58: unknown network field 'network'.
Line 67: failed to parse network block.
Failed to read or parse configuration '/etc/wpa/wpa.conf'.
Starting udhcpc client on: wlan0...
udhcpc (v1.23.2) started
Sending discover...
Sending discover...
Sending discover...
No lease, forking to background
Connecting to H16H6R4D3...
.....Failed to connect to non-global ctrl_ifname: (null) error: No such file or directory
[ Failed ]
can anyone help me on this one? i dont know where the problem came from..
thanks!
Offline
There have been many changes to /etc/init.d/network.sh and /etc/network.conf
http://hg.slitaz.org/slitaz-boot-scripts/rev/6c2d6362887d
http://hg.slitaz.org/slitaz-boot-scripts/rev/f3e7c1cc6aef
http://hg.slitaz.org/slitaz-boot-scripts/rev/28a9c8b64212
http://hg.slitaz.org/slitaz-boot-scripts/file/a8aa6b77a7ed/usr/share/slitaz/network.conf_migration
The last one adds a script that renames your existing /etc/network.conf and creates a new version of network.conf in a different format.
There is a bug report about wifi problems: http://bugs.slitaz.org/?id=147
I run custom boot scripts and have slitaz-boot-scripts blocked for over 3 months to prevent overwrite on updates.
You can try rolling back the update of slitaz-boot-scripts that owns /etc/init.d/network.sh and /etc/network.conf
Rename /etc/network.conf to /etc/network.conf.old before the rollback.
Reconfigure /etc/network.conf installed after the rollback.
On your system check /var/log/tazpkg.log to see if you updated slitaz-boot-scripts prior to the last update to find the version that worked.
If you never updated then boot your install iso:
[c]tazpkg search slitaz-boot-scripts[/c]
Outputs slitaz-boot-scripts version you started with.
Attached is every version of slitaz-boot-scripts going back to 5.6.1 that was in slitaz-5.0-rc2
[c]tazpkg install slitaz-boot-scripts-<version>.tazpkg --forced[/c]
After you find the version that works.
[c]tazpkg block slitaz-boot-scripts[/c]
Offline
@mojo: thanks a lot for the workaround! now im mobile again 
5.7 didnt work, but 5.6.7 did..
Offline
as said, it works for me.
my friend gets the follwing output:
stopping all interfaces
Killing all daemons
Shutting down wifi card
Configuring wlan0... [ Done ]
Creating: /etc/wpa/wpa.conf
Starting wpa_supplicant for WPA-PSK...
Successfully initialized wpa_supplicant
rfkill: WLAN hard blocked
Could not set interface wlan0 flags (UP): Operation not possible due to RF-kill
Starting udhcpc client on: wlan0...
Selected interface 'wlan0'
any hints? thanks!
Offline
Hi K3nn3th,
rfkill: WLAN hard blocked
Quick answer: very possible, this error means WLAN card was switched off manually by your friend.
It may be slider without fixation (as for my netbook) of Fn + F3 keys combination (as for my son's notebook), or something similar. Switch WLAN card on, wait few seconds and try to start Wi-Fi connection again.
Long answer: hardware switch may not help. Some WLAN cards supporting software Rfkill. You can install package (I can't recall the name) and manage Rfkill in the command line. Please, search forum for "rfkill" — mojo answered few times.
Offline
Pages: 1
[ Generated in 0.015 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]