You are not logged in.
Pages: 1
Hi, for the client i get
$ wicd-client
(process:8315): Gtk-WARNING **: Locale not supported by C library.
Using the fallback 'C' locale.
Importing pynotify failed, notifications disabled.
Has notifications support False
Loading...
Connecting to daemon...
Can't connect to the daemon, trying to start it automatically...
Then a gui ask's for root, after hitting it in I get this:
Could not connect to wicd's D-Bus interface. Check the wicd log for error messages.
Before that I did this:
bash-3.2# /etc/rc.d/network stop
:: Stopping Network [DONE]
bash-3.2# nano /etc/rc.conf
bash-3.2# /etc/rc.d/dbus restart
:: Stopping D-BUS system messagebus [DONE]
:: Starting D-BUS system messagebus [DONE]
bash-3.2# /etc/rc.d/wicd restart
:: Stopping wicd Daemon [DONE]
:: Starting wicd Daemon [DONE]
bash-3.2#
Last edited by jerik (2009-06-27 20:55:08)
Offline
Hmm, I installed wicd-bzr (which I thought was just more bleeding edge?), and rebooted... now it works.
What is wicd-bzr?
Offline
No, the only problem left is that it doesn't activate wlan0
[jerik@myhost ~]$ iwlist wlan0 scan
wlan0 Failed to read scan data : Network is down
I wonder if my last problem was caused by starting both dbus and hal, and solved by reducing to only hal...
Last edited by jerik (2009-06-25 23:34:31)
Offline
...which is weird, as HAL starts DBUS automatically, it can't function without it.
On your other issue, wicd keeps all interfaces down as long as you don't order it to refresh or connect to a network. ifconfig wlan0 up would bring it up manually.
Why are you trying to scan manually, doesn't the client display APs? You could also check if "wlan0" is set as the wireless adapter in the preferences menu.
Last edited by Malstrond (2009-06-26 00:30:40)
Offline
Hi! Yes, what I meant is that in my rc.conf I had both dbus and hal, so removing dbus and letting hal deal with starting dbus seemed to make a difference. My wicd client says: No wireless networks found, thought there are many around. So after i hit iwlist wlan0 scan, I saw that wlan0 was down. Yes, wlan0 is set as the adapter in my client... maby this is the problem: after hitting ifcinfig wlan0 up I got:
EDIT: Sorry, pasted wrong output
$ ifconfig wlan0 up
SIOCSIFFLAGS: Permission denied
Last edited by jerik (2009-06-26 11:40:10)
Offline
Did you disable the interfaces in rc.conf as the wiki says?
http://wiki.archlinux.org/index.php/Wicd#Initial_Setup
Offline
Yes
#
eth0="dhcp"
INTERFACES=(!eth0 !wlan0)
should wlan0 also be set to dhcp?
Offline
An exclamation mark before the interface disables it
never trust a toad...
::Grateful ArchDonor::
::Grateful Wikipedia Donor::
Offline
But, the wiki says:
Disable (!) any devices in the INTERFACES array that you wish to manage with Wicd
Offline
Did you up the device as root?
sudo iwconfig wlan0 up
Also try checking for the name of the device with ifconfig -a, maybe it's mapped differently?
Offline
I tried with and without root... same result. What am I suposed to look for using ifconfig -a, I get something I've never seen before about "wmaster0"
Offline
I don't know what you have done wrong actually. I have never had any problems whatsoever with wicd.
I'd recommend to start over, reinstall it and check and double check the wicd wiki entry. Then reboot and try again. That's how I normally solve my problems:
1. reinstall
2. read the arch wiki
3. enter correct stuff in rc.conf etc
4. reboot
5. success
Offline
I'd recommend to start over, reinstall it and check and double check the wicd wiki entry.
I hope you mean reinstall wicd not Arch .
Removing all traces of wicd (including configurations) then reinstalling wicd and following the wiki closely is a good advice .
English is not my native language .
Offline
Yeah, wicd not arch.
Offline
Ok, I'll do that. But when one uninstall doesn't that also rename the configfiles with a .packsave-ending so that they are not used upon a reinstallation?
Offline
Edit: I messed up
Last edited by jerik (2009-06-26 18:20:19)
Offline
Ok, the wiki tells me to rename root to network here, but that makes the client not able to start. Though it start just fine as it was.
<policy user="root">
<allow own="org.wicd.daemon"/>
<allow send_destination="org.wicd.daemon"/>
<allow send_interface="org.wicd.daemon"/>
<allow send_destination="org.wicd.daemon.wireless"/>
<allow send_interface="org.wicd.daemon.wireless"/>
<allow send_destination="org.wicd.daemon.wired"/>
<allow send_interface="org.wicd.daemon.wired"/>
<allow send_destination="org.wicd.daemon.config"/>
<allow send_interface="org.wicd.daemon.config"/>
</policy>
Is it unwise to install wicd-testing from AUR?
Last edited by jerik (2009-06-26 18:41:53)
Offline
This is my rc.conf file:
#
# /etc/rc.conf - Main Configuration for Arch Linux
#
# -----------------------------------------------------------------------
# LOCALIZATION
# -----------------------------------------------------------------------
#
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime"
# USEDIRECTISA: use direct I/O requests instead of /dev/rtc for hwclock
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
#
LOCALE="nb_NO.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="Europe/Oslo"
KEYMAP="no-latin1"
CONSOLEFONT="lat1-12"
CONSOLEMAP=
USECOLOR="yes"
# -----------------------------------------------------------------------
# HARDWARE
# -----------------------------------------------------------------------
#
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
#
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
#
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=(!soundcore)
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# -----------------------------------------------------------------------
# NETWORKING
# -----------------------------------------------------------------------
#
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
#
HOSTNAME="myhost"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
#
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
#
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#
eth0="dhcp"
INTERFACES=(!eth0 !wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
#
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
#
# Network profiles are found in /etc/network.d
#
# This now requires the netcfg package
#
#NETWORKS=(main)
# -----------------------------------------------------------------------
# DAEMONS
# -----------------------------------------------------------------------
#
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
#
DAEMONS=(syslog-ng hal netfs crond wicd oss)
Offline
And, if it's of help, this is info about my wireless card
$ iwconfig wlan0
wlan0 IEEE 802.11abg ESSID:""
Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated
Tx-Power=0 dBm
Retry min limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality:0 Signal level:0 Noise level:0
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
Offline
Wooh, I made it! I think the reason was that the wifi-driver didn't support European channels (above 11)
Offline
Pages: 1