Re: intermittent wireless



Bob Tennent <BobT@xxxxxxxxxxxxx> wrote:
On Sun, 07 Jun 2009 18:53:00 GMT, Stefan Patric wrote:
On Sun, 07 Jun 2009 17:30:24 +0000, Bob Tennent wrote:

I have an ASUS SN5000 laptop with an Intel 2100 mini PCI wireless card.
This has been working for some years, but recently only intermittently.
The card is detected:

kernel: ieee80211: Copyright (C) 2004-2005 Intel Corporation kernel:
ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 kernel:
ipw2100: Copyright(c) 2003-2006 Intel Corporation kernel: ACPI: PCI
Interrupt 0000:01:05.0[A] -> GSI 18 (level, low) -> IRQ 169 kernel:
ipw2100: Detected Intel PRO/Wireless 2100 Network Connection kernel:
PCI: Enabling device 0000:00:1f.5 (0005 -> 0007) kernel: ACPI: PCI
Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 201

The modules are loaded:

% lsmod | grep ipw2100
ipw2100 68081 0
ieee80211 34313 1 ipw2100

the scanning function (iwlist eth0 scan) works, but the wireless LED is
off and the interface doesn't associate with the access point. Other
systems with the same configuration and access point work OK.

Would this be a bad card or a bad connector, or is something disabling
the card? The BIOS configuration is set to Wireless LAN enabled.

Bob T.

Since iwlist scan works, I'd say the card is okay. The problem is
elsewhere. What does ifconfig and iwconfig report? Do they show your
card is "up" and associated with your ap? Do you have an IP address?

I'm using a static IP so dhclient isn't involved.

% iwconfig eth0
eth0 unassociated ESSID:"tennent" Nickname:"esprit"
Mode:Managed Channel=0 Access Point: Not-Associated
Bit Rate=0 kb/s Tx-Power:16 dBm
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

% ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:0C:F1:2F:B1:BE
inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
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)
Interrupt:169 Base address:0xa000 Memory:fe8fe000-fe8fefff

Have you tried connecting manually? Have you tried running dhclient
manually?

When the wireless led flashes, connecting isn't a problem. And when the
led comes on, it's during the udev initialization; so I don't think it's
a connection issue: for some reason the wireless is disabled right from
boot-up.

One possibility is that the transmitter is dead; scan would still
work, but of course you couldn't associate with the AP.

Another possibility is rfkill, do you have a kill switch and is
rfkill.ko loaded?

Jerry
.