[SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

bud · 2011-05-21 15:01:45

Hello!

I really want to use arch on this laptop but I always had problem with the wireless part. It sort of works but i get disconnected all the time, it "drops". autoreconnect usually works fine but its extremely annoying to be disconnected 1000000 times a day
The thing is, it works flawless in ubuntu and linux mint, so I have been stuck to those for a while.
I guess I should be able to use ubuntu/linux mints driver/firmware for the ipw2200 in arch, but how do i do it? Im not a noob so i guess it could be done quite easy if someone explained how I do it.
Also, could it be just the firmware that messes it up or is it the driver? If its just the firmware I could just overwrite the old one.

Last edited by bud (2011-07-25 22:45:27)

ewaller · 2011-05-21 17:40:11

Its pretty impressive that you can repetitively reconnect in less than 86mS

What leads you to believe that the drivers from the other distos are different than Arch's ? The drivers are part of the kernel which makes it non-trivial to just copy them over and use them. At the very least, you would have to recompile the kernel driver.

I assume you have installed the ipw2200-fw firmware from core.
Could you post the output of lspci and lspci -n ??
Also, after start up, have you looked though the output of dmesg for information relating to the ipw2200 ?
What does /var/log/messages.log say as to the connecting and disconnecting ?
What router are you using? Is it using WEP, WPA, WPA2, or is it open?

Army · 2011-05-21 20:11:30

What programs do you use in Ubuntu and in Arch to connect to the wireless network? I have the same wireless card and sometimes it depends on the program I use.

bud · 2011-05-21 23:24:41

ewaller wrote:

Its pretty impressive that you can repetitively reconnect in less than 86mS
What leads you to believe that the drivers from the other distos are different than Arch's ? The drivers are part of the kernel which makes it non-trivial to just copy them over and use them. At the very least, you would have to recompile the kernel driver.
I assume you have installed the ipw2200-fw firmware from core.
Could you post the output of lspci and lspci -n ??
Also, after start up, have you looked though the output of dmesg for information relating to the ipw2200 ?
What does /var/log/messages.log say as to the connecting and disconnecting ?
What router are you using? Is it using WEP, WPA, WPA2, or is it open?

hehe, hmm ok, well I just presumed this was a driver-issue since it always works flawless in ubuntu and not in arch. Well right now I can only show output from the linux mint installation.
I have had the same problem on many diffrent routers, wep, wpa wpa2 and even open networks, same thing happens

Army wrote:

What programs do you use in Ubuntu and in Arch to connect to the wireless network? I have the same wireless card and sometimes it depends on the program I use.

In ubuntu/linux mint I have used the default program for handling wireless, dunno what it is called actually. In arch I have always used wicd. Could this be the problem??

Last edited by bud (2011-05-21 23:25:33)

tlmiller · 2011-05-21 23:55:56

While I won't say it's impossible, I doubt it. I don't have anything anymore that has a 2200, but when I did, I used wicd with Arch and it worked flawlessly for me. It in fact was the D610 also.

bud · 2011-05-22 12:03:33

I'll just install Arch again and get some help from there ;-)

astrocrep · 2011-05-26 00:36:43

I have a sony vgn-s460 w/ the ipw2200 and it works perfect for me...
Installed the firmware from core, and use wicd to configure (disabled network daemon)

Just pulled over 500mb w pacman and not a single hick up!

-Rich

bud · 2011-06-01 21:06:56

Ok, im back in Arch, same thing happens, connection drops.
Wicd autoconnects, can take from 1 to XXXX tries before it connects again.

lspci

[bud@stan filearea]$ lspci
00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)
00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
02:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM5751 Gigabit Ethernet PCI Express (rev 01)
03:01.0 CardBus bridge: Texas Instruments PCI6515 Cardbus Controller
03:01.5 Communication controller: Texas Instruments PCI6515 SmartCard Controller
03:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)

lspci -n

[bud@stan filearea]$ lspci -n
00:00.0 0600: 8086:2590 (rev 03)
00:02.0 0300: 8086:2592 (rev 03)
00:02.1 0380: 8086:2792 (rev 03)
00:1c.0 0604: 8086:2660 (rev 03)
00:1d.0 0c03: 8086:2658 (rev 03)
00:1d.1 0c03: 8086:2659 (rev 03)
00:1d.2 0c03: 8086:265a (rev 03)
00:1d.3 0c03: 8086:265b (rev 03)
00:1d.7 0c03: 8086:265c (rev 03)
00:1e.0 0604: 8086:2448 (rev d3)
00:1e.2 0401: 8086:266e (rev 03)
00:1f.0 0601: 8086:2641 (rev 03)
00:1f.2 0101: 8086:2653 (rev 03)
02:00.0 0200: 14e4:1677 (rev 01)
03:01.0 0607: 104c:8036
03:01.5 0780: 104c:8038
03:03.0 0280: 8086:4220 (rev 05)

dmesg

[54152.486299] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54152.501003] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54154.986863] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[54165.984600] eth1: no IPv6 routers present
[54169.267959] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54169.300310] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54174.019592] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54174.480844] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54174.574664] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54174.607114] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54174.626259] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54177.160048] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[54188.157971] eth1: no IPv6 routers present
[54208.184105] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54208.284634] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54208.317565] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54221.049963] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54223.457561] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54223.548065] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54223.581218] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54223.601808] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54226.099001] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[54236.464599] eth1: no IPv6 routers present
[54258.461428] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54258.496106] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54258.517136] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54259.524874] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54259.621437] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54259.656659] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54261.437289] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[54271.811400] eth1: no IPv6 routers present
[54485.267923] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54485.300666] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54490.021180] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54490.347277] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54490.441399] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
[54490.473078] ADDRCONF(NETDEV_UP): eth0: link is not ready
[54490.487493] ADDRCONF(NETDEV_UP): eth1: link is not ready
[54493.001515] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[54503.064570] eth1: no IPv6 routers present

/var/log/messages.log

Jun  1 22:57:49 localhost dhcpcd[1512]: sending signal 1 to pid 1345
Jun  1 22:57:49 localhost dhcpcd[1345]: received SIGHUP, releasing
Jun  1 22:57:49 localhost dhcpcd[1345]: eth1: removing interface
Jun  1 22:57:49 localhost dhcpcd[1512]: waiting for pid 1345 to exit
Jun  1 22:57:49 localhost kernel: [54485.267923] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
Jun  1 22:57:49 localhost kernel: [54485.300666] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun  1 22:57:54 localhost kernel: [54490.021180] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun  1 22:57:54 localhost kernel: [54490.347277] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun  1 22:57:54 localhost kernel: [54490.441399] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
Jun  1 22:57:54 localhost kernel: [54490.473078] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun  1 22:57:54 localhost kernel: [54490.487493] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun  1 22:57:57 localhost kernel: [54493.001515] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jun  1 22:57:57 localhost dhcpcd[1577]: version 5.2.12 starting
Jun  1 22:57:57 localhost dhcpcd[1577]: eth1: rebinding lease of 192.168.1.66
Jun  1 22:57:57 localhost dhcpcd[1577]: eth1: acknowledged 192.168.1.66 from 192.168.1.254
Jun  1 22:57:57 localhost dhcpcd[1577]: eth1: checking for 192.168.1.66
Jun  1 22:58:03 localhost dhcpcd[1577]: eth1: leased 192.168.1.66 for 3600 seconds
Jun  1 22:58:03 localhost dhcpcd[1577]: forked to background, child pid 1601
Jun  1 23:04:41 localhost dhcpcd[1601]: eth1: carrier lost
Jun  1 23:04:42 localhost dhcpcd[1601]: eth1: carrier acquired
Jun  1 23:04:42 localhost dhcpcd[1601]: eth1: rebinding lease of 192.168.1.66
Jun  1 23:04:45 localhost dhcpcd[1601]: eth1: acknowledged 192.168.1.66 from 192.168.1.254
Jun  1 23:04:45 localhost dhcpcd[1601]: eth1: checking for 192.168.1.66
Jun  1 23:04:46 localhost dhcpcd[1911]: sending signal 1 to pid 1601
Jun  1 23:04:46 localhost dhcpcd[1601]: received SIGHUP, releasing
Jun  1 23:04:46 localhost dhcpcd[1601]: eth1: removing interface
Jun  1 23:04:46 localhost dhcpcd[1911]: waiting for pid 1601 to exit
Jun  1 23:04:46 localhost kernel: [54902.274560] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
Jun  1 23:04:46 localhost kernel: [54902.306488] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun  1 23:04:51 localhost kernel: [54907.021659] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun  1 23:04:51 localhost kernel: [54907.350476] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun  1 23:04:51 localhost kernel: [54907.444687] tg3 0000:02:00.0: BAR 0: set to [mem 0xdfdf0000-0xdfdfffff 64bit] (PCI address [0xdfdf0000-0xdfdfffff])
Jun  1 23:04:51 localhost kernel: [54907.481686] ADDRCONF(NETDEV_UP): eth0: link is not ready
Jun  1 23:04:51 localhost kernel: [54907.501074] ADDRCONF(NETDEV_UP): eth1: link is not ready
Jun  1 23:04:54 localhost kernel: [54910.074175] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jun  1 23:04:54 localhost dhcpcd[1961]: version 5.2.12 starting
Jun  1 23:04:54 localhost dhcpcd[1961]: eth1: broadcasting for a lease
Jun  1 23:04:54 localhost dhcpcd[1961]: eth1: offered 192.168.1.66 from 192.168.1.254
Jun  1 23:04:54 localhost dhcpcd[1961]: eth1: acknowledged 192.168.1.66 from 192.168.1.254
Jun  1 23:04:54 localhost dhcpcd[1961]: eth1: checking for 192.168.1.66
Jun  1 23:04:59 localhost dhcpcd[1961]: eth1: leased 192.168.1.66 for 3600 seconds
Jun  1 23:04:59 localhost dhcpcd[1961]: forked to background, child pid 1987

help?

eincello · 2011-06-19 18:22:32

This happens to me, too, doesn't matter if I'm using wicd or wpa_supplicant and dhcpcd by themselves.

From dhcpcd:

dhcpcd[4772]: version 5.2.12 starting
[...]
dhcpcd[4772]: eth1: leased 172.16.237.100 for 43200 seconds
dhcpcd[4772]: eth1: carrier lost
dhcpcd[4772]: eth1: carrier acquired
dhcpcd[4772]: eth1: rebinding lease of 172.16.237.100
[...]

From wpa_supplicant:

Associated with 00:12:3a:4b:5c:6d
WPA: Key negotiation completed with 00:12:3a:4b:5c:6d [PTK=CCMP GTK=CCMP]
CTRL-EVENT-CONNECTED - Connection to 00:12:3a:4b:5c:6d completed (auth) [id=0 id_str=]
CTRL-EVENT-DISCONNECTED bssid=00:12:3a:4b:5c:6d reason=0
Trying to associate with 00:12:3a:4b:5c:6d (SSID='homeap' freq=2447 MHz)
Associated with 00:12:3a:4b:5c:6d

Nothing else interesting in the logs. It only seems to happen after the computer has been up a while, at least 20-30 minutes or so.

EDIT: I'm using an Inspiron 6000.

lspci:

00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation Mobile 915GM/PM Express PCI Express Root Port (rev 03)
00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 03)
00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 03)
00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 (rev 03)
00:1d.3 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 (rev 03)
00:1d.7 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller (rev 03)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev d3)
00:1e.2 Multimedia audio controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Audio Controller (rev 03)
00:1e.3 Modem: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) AC'97 Modem Controller (rev 03)
00:1f.0 ISA bridge: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge (rev 03)
00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03)
01:00.0 VGA compatible controller: ATI Technologies Inc M22 [Mobility Radeon X300]
03:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX (rev 02)
03:01.0 CardBus bridge: Ricoh Co Ltd RL5c476 II (rev b3)
03:01.1 FireWire (IEEE 1394): Ricoh Co Ltd R5C552 IEEE 1394 Controller (rev 08)
03:01.2 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 17)
03:03.0 Network controller: Intel Corporation PRO/Wireless 2200BG [Calexico2] Network Connection (rev 05)

lspci -n

00:00.0 0600: 8086:2590 (rev 03)
00:01.0 0604: 8086:2591 (rev 03)
00:1d.0 0c03: 8086:2658 (rev 03)
00:1d.1 0c03: 8086:2659 (rev 03)
00:1d.2 0c03: 8086:265a (rev 03)
00:1d.3 0c03: 8086:265b (rev 03)
00:1d.7 0c03: 8086:265c (rev 03)
00:1e.0 0604: 8086:2448 (rev d3)
00:1e.2 0401: 8086:266e (rev 03)
00:1e.3 0703: 8086:266d (rev 03)
00:1f.0 0601: 8086:2641 (rev 03)
00:1f.2 0101: 8086:2653 (rev 03)
01:00.0 0300: 1002:5460
03:00.0 0200: 14e4:170c (rev 02)
03:01.0 0607: 1180:0476 (rev b3)
03:01.1 0c00: 1180:0552 (rev 08)
03:01.2 0805: 1180:0822 (rev 17)
03:03.0 0280: 8086:4220 (rev 05)

Last edited by eincello (2011-06-19 18:41:11)

bud · 2011-07-01 13:26:11

So, any 1337 arch user that could help us?

universalpoe · 2011-07-08 08:42:58

From the boot process, I note that it persistently reports "eth1: no IPv6 routers present", so may be you can disable the ipv6 module to load in the modprobe.conf to try it out. And by the way, don't use wicd, try link the wireless using wpa_supplicant+dhcpcd, because it's wicd may have drop issues with certain drivers. Good luck.

MoonSwan · 2011-07-08 21:22:14

Can we presume you've loaded the necessary firmware files from the setup DVD? I know many Intel wifi cards do not work with out it.

bud · 2011-07-14 22:32:51

Yes the firmware is loaded, it wont work at all without it

bud · 2011-07-25 22:44:38

SOLVED!!

I threw wicd in the trash and used networkmanager instead, has been working flawless except for one time when the connection died. According to dmesg it was a "firmware error".
I downloaded the latest firmware from intels homepage and replaced it (same size and date) but since then I havent been able to get the error again

Arch Linux

#1 2011-05-21 15:01:45

[SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#2 2011-05-21 17:40:11

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#3 2011-05-21 20:11:30

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#4 2011-05-21 23:24:41

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#5 2011-05-21 23:55:56

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#6 2011-05-22 12:03:33

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#7 2011-05-26 00:36:43

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#8 2011-06-01 21:06:56

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#9 2011-06-19 18:22:32

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#10 2011-07-01 13:26:11

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#11 2011-07-08 08:42:58

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#12 2011-07-08 21:22:14

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#13 2011-07-14 22:32:51

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

#14 2011-07-25 22:44:38

Re: [SOLVED] Wireless issue - ipw2200 - Dell Latitude D610

Board footer