Hi friends,
anyone of you know if is possible to use wicd on slitaz 4.0?
..because i obtain many errors, such "unable to autorize the client, unable to run slitaz panel if disable network.sh on /etc/init.d.."
many thanks!
Hi friends,
anyone of you know if is possible to use wicd on slitaz 4.0?
..because i obtain many errors, such "unable to autorize the client, unable to run slitaz panel if disable network.sh on /etc/init.d.."
many thanks!
..bah!
# tazpkg install wicd-1.7.2.4.tazpkg
# /etc/init.d/network.sh stop
# /etc/init.d/wicd start
$ wicd-gtk --no-tray
Wicd Network Manager/click the V indicated by red arrow:
Preferences/External Programs tab/ DHCP Client / udhcpc
Click OK
ah, ok it's necessary to install an update version of wicd, well i try.
Very very thanks for your detailed informations ;-)
ciao!
Well, i've installed the updated wicd version and apply the changes to /etc/rcS.conf and rebooted.
When i run "wicd-gtk --no-tray" obtain:
"Unable to contact the Wicd daemon due to an access denied error from DBus. Please check that your user is in the users group."
The daemon is running:
root@(none):/home/guest# /etc/init.d/wicd start
Wicd already running.
I've seen that left the hostname (none) but on /etc/hostname i've set correctly "cosmogoniAslitaz"
and on /etc/hosts too
if i try to run slitaz panel it doesn't show me the login root window
..hoops! :-9
many thanks again
ok, i've run
hostname -F /etc/hostname
and
/sbin/ifconfig lo 127.0.0.1 up
/sbin/route add 127.0.0.1 lo
so the hostname and the loopback device is ok
..ok, user guest is member of users group.
so, i've reload DBUS: /etc/init.d/dbus restart
run "wicd-gtk --no-tray"
now wicd ask me the root password, i insert it and WICD reply to me:
Error: wrong password!
At this point only one question, the same, the first:
"anyone of you know if is possible to use wicd on slitaz 4.0?"
.. and in any case, on a virgin installation SliTaz, there seems little acceptable this kind of complexity to install a package as wicd?
thanks
@mojo, Quote "Remove network.sh from RUN_SCRIPTS="
This disabled the slitaz panel. Normally when I click on slitaz panel, I get prompted for password, then panel opens to "TazPanel".
With network.sh removed as above, when I click slitaz panel, there is no password prompt, and the panel opens a blank page and stays at 10% forever.
I added network.sh back to rcS.conf, and removed wicd from it also and rebooted. My slitaz panel is back working like it should.
@danjde, I can launch wicd from a root terminal and it seems to be working, but I have no wifi spots showing after a scan. I'm now using the wl driver for my BCM4312.
I may have to modprobe something and blacklist something else. I've got it written down somewhere from a couple years ago with debian and wireless broadcom stuff.
@Jon_J
Sorry, I should have tested that.
The network.sh script sets up the loopback i.p. 127.0.0.1
/etc/hosts => 127.0.0.1 localhost slitaz tazpanel
Address of tazpanel=> http://tazpanel:82/
In addition it sets up the hostname.
Wicd users will have to keep network.sh in RUN_SCRIPTS= and remove wicd from RUN_DAEMONS= of /etc/rcS.conf
After booting up network.sh can be stopped, tazpanel still works and wicd started.
Having both network.sh and wicd running at the same time won't work either.
In Debian based distros, ubuntu, crunchbang, and Debian, one must uninstall network-manager first before installing wicd. That was the same on pdaxrom for Zaurus, it was/is a Debian based distro. WICD is nice, but there is more than one way to connect wireless in linux. Another thing, on my Dell mini 1010, if I input "yes" to WIFI= in network.conf, my ethernet will not work. I've tried this several times while trying to get wireless working. In crunchbang, when connected to my ethernet cable, sometimes my wifi tries to connect, and shows all the local APs in my area. I usually just cancel it.
I probably won't bother with WIFI in slitaz because this netbook is way too slow without a GMA500 video driver. It runs all the gui stuff with the cpu under the graphics driver that is loaded now.
@mojo I am not home and have just my tab with me - can you try this in local.sh
sleep 1
/etc/init.d/network.sh stop
sleep 1
/etc/init.d/wicd start
maybe sleep is not necessary.....
and then in .config/openbox/autostart.sh
# wicd Network Configuration
sleep 2
wicd-gtk --no-tray &
You must log in to post.