You are not logged in.

#1 2009-08-29 21:53:48

Janarto
Member
From: Paris
Registered: 2008-09-23
Posts: 80

[Solved] Wired connection ok but wireless problem on Intel 5100

Here is how i solved the problem :
1 - get back to the wiki doing everything in order
2 - added dbus in attition to hal in the deamon line in rc.conf
3 - put wicd at the end of the deamon line
4 - then configured wicd for my wireless network at boot : no more dbus error, and connection perfectly ok

Thx very much for the superb wiki, certainly my fault if i messed up but i still have to learn wink


Hi wink

I've got a problem with the wireless connection on my toshiba R10

my wired connection is working flawlessly but i can't use my wifi card. I'm using arch 2009.8 i686

Here is what i've done following the wiki :

1 : installed ifplugd for the RJ45 connection + added the deamon on my rc.conf
2 : installed wireless-tools
3 : installed the driver intel 5100
# pacman -S iwlwifi-5000-ucode

set up my mod_autolog yes

here is my ifconfig -a

[me@arch ~]$ ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:1C:7E:83:EB:B4  
          inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:7eff:fe83:ebb4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:603 errors:0 dropped:0 overruns:0 frame:0
          TX packets:610 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100  
          RX bytes:329491 (321.7 Kb)  TX bytes:84091 (82.1 Kb)
          Memory:ffcc0000-ffce0000  
 
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:66 errors:0 dropped:0 overruns:0 frame:0
          TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0  
          RX bytes:4400 (4.2 Kb)  TX bytes:4400 (4.2 Kb)
 
wlan0     Link encap:Ethernet  HWaddr 00:22:FB:04:1A:72  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000  
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 
wmaster0  Link encap:UNSPEC  HWaddr 00-22-FB-04-1A-72-00-00-00-00-00-00-00-00-00-00  
          UP RUNNING  MTU:0  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000  
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

I have a dbus error : « Could not connect to wicd's D-Bus interface. Check the wicd log for error messages. »
so i modified my configuration file following this topic on the french forum http://forums.archlinux.fr/topic3967.html (same error message)

here is my rc.conf

#
# /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="fr_FR.utf8"
HARDWARECLOCK="localtime"
USEDIRECTISA="no"
TIMEZONE="Europe/Paris"
KEYMAP="fr-pc"
CONSOLEFONT=
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=()
 
# 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="arch"
 
# 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
#
 
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
INTERFACES=(eth0)
 
# 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 network ifplugd netfs slim crond alsa fam)

i tried to start wicd manually but it stay busy infinitely :

74526684.png

here is my /etc/wicd/manager-setting.conf

 GNU nano 2.0.9      Fichier : /etc/wicd/manager-settings.conf                  
 
[Settings]
wireless_interface = wlan0
pref_width = 450
window_width = 530
prefer_wired = False
flush_tool = 0
use_global_dns = False
global_dns_dom = None
always_show_wired_interface = True
sudo_app = 0
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
backend = external
link_detect_tool = 0
dhcp_client = 0
window_height = 529
wired_connect_mode = 1
debug_mode = 0
sudo_app = 0
global_dns_1 = None
global_dns_2 = None
global_dns_3 = None
backend = external
link_detect_tool = 0
dhcp_client = 0
window_height = 529
wired_connect_mode = 1
debug_mode = 0
pref_height = 450
wired_interface = eth0
signal_display_type = 1
global_search_dom = None
auto_reconnect = True
wpa_driver = wext

and what i get ont the graphical interface : no wireless network found
wicd.png

here is my "ps aux | grep dbus"

[root@arch ~]# ps aux | grep dbus
dbus      1373  0.0  0.0   2252   940 ?        Ss   14:27   0:00 /usr/bin/dbus-daemon --system
me        1703  0.0  0.0   3156   696 ?        S    14:27   0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
me        1704  0.0  0.0   2264   972 ?        Ss   14:27   0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
root      2794  0.0  0.0   3892   872 pts/1    S+   15:11   0:00 grep dbus

in the preference settings of wicd, it's correct : eth0 as wired connection and wlan0 as wireless

here is my "iwlist wlan0"

[root@arch ~]# iwlist wlan0 scanning
wlan0     No scan results

i've tried a lspci -vv :

[me@arch ~]$ lspci -vv
00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07)
 Subsystem: Toshiba America Info Systems Device 0001
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>
 Kernel driver in use: agpgart-intel
 Kernel modules: intel-agp
 

00:03.0 Communication controller: Intel Corporation Mobile 4 Series Chipset MEI Controller (rev 07)
 Subsystem: Toshiba America Info Systems Device 0001
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at ffcff000 (64-bit, non-prefetchable) [size=16]
 Capabilities: <access denied>
 Kernel driver in use: heci
 Kernel modules: heci
 

00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
 Subsystem: Toshiba America Info Systems Device 0001
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 28
 Region 0: Memory at ffcc0000 (32-bit, non-prefetchable) [size=128K]
 Region 1: Memory at ffcfe000 (32-bit, non-prefetchable) [size=4K]
 Region 2: I/O ports at cf80 [size=32]
 Capabilities: <access denied>
 Kernel driver in use: e1000e
 Kernel modules: e1000e
 

00:1f.0 ISA bridge: Intel Corporation ICH9M-E LPC Interface Controller (rev 03)
 Subsystem: Toshiba America Info Systems Device 0001
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Capabilities: <access denied>
 Kernel modules: iTCO_wdt
 


01:00.0 Network controller: Intel Corporation Wireless WiFi Link 5100
 Subsystem: Intel Corporation Device 1301
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 32 bytes
 Interrupt: pin A routed to IRQ 29
 Region 0: Memory at ff900000 (64-bit, non-prefetchable) [size=8K]
 Capabilities: <access denied>
 Kernel driver in use: iwlagn
 Kernel modules: iwlagn

I suspect that something is wrong between iwlagn and iwlwifi-5000 which can cause this problem.
I have to say that I'm quite lost here, i hope someone will have an idea wink

thank you very much

Last edited by Janarto (2009-08-30 02:46:18)

Offline

#2 2009-08-30 02:09:31

djszapi
Member
From: Cambridge, United Kingdom
Registered: 2009-06-14
Posts: 1,439
Website

Re: [Solved] Wired connection ok but wireless problem on Intel 5100

Hello connexion2000!

Did you try with other applications, like autowifi or networkmanager or maybe from command line ? Can it work so ?

Offline

#3 2009-08-30 02:43:06

Janarto
Member
From: Paris
Registered: 2008-09-23
Posts: 80

Re: [Solved] Wired connection ok but wireless problem on Intel 5100

i've solved it by redoing everything, i guess the main problem was the fact that i had to add dbus after hal in the deamons

thx very much

Offline

#4 2009-08-30 02:48:54

Profjim
Member
From: NYC
Registered: 2008-03-24
Posts: 658

Re: [Solved] Wired connection ok but wireless problem on Intel 5100

Stab in the dark...the hal daemon should start dbus, but sometimes I've been encouraged to add the dbus DAEMON explicitly (before hal).

I don't really understand dbus too intimately, but I've come across situations where although dbus is running, I can't talk to it because the DBUS_SESSION_BUS_{ADDRESS,PID,WINDOWID} variables weren't visible in the environment I was working in. For instance, if dbus is started by xinitrc, and then some system-level daemon tries to talk to dbus, usually it fails for me, and I have to use some workaround.

Now I would expect wicd to be set up so that the ordinary user doesn't encounter any problems of this sort. On the other hand, the error you're getting does say that it's dbus communication which is failing. Perhaps you could try shutting down hald and dbus, open a terminal, su -, /etc/rc.d/dbus start, and then try from that command line to tell wicd to connect?

Offline

#5 2009-08-30 12:02:28

Janarto
Member
From: Paris
Registered: 2008-09-23
Posts: 80

Re: [Solved] Wired connection ok but wireless problem on Intel 5100

i've removed dbus and now it's working perfectly, i don't really get everything here, but anyway, if it ain't broke don't fix it big_smile

Offline

Board footer

Powered by FluxBB