Jump to content

iwl3945 breaks wireless access


Guest Siddhartha Jain
 Share

Recommended Posts

Guest Siddhartha Jain

I have a Lenovo T60p with the Intel 3945ABG ver 02 wireless card built-in. The card worked fine with ipw3945 driver and my WPA AP. Now with the iwl3945 upgrade, it won't connect to any AP, WPA or otherwise. I have Mandriva 2009 32-bit installed.

 

"Linux localhost 2.6.27-desktop586-0.rc8.2mnb #1 SMP Thu Oct 2 05:52:21 EDT 2008 i686 Genuine Intel® CPU T2600 @ 2.16GHz GNU/Linux"

 

Here is the /var/log/messages output when I turn on the "Radio" switch on the laptop:

 

-----snip-----------

Oct 29 21:38:13 L-061012-A kernel: usb 5-1: new full speed USB device using uhci_hcd and address 4

Oct 29 21:38:13 L-061012-A kernel: usb 5-1: configuration #1 chosen from 1 choice

Oct 29 21:38:13 L-061012-A kernel: usb 5-1: New USB device found, idVendor=0a5c, idProduct=2110

Oct 29 21:38:13 L-061012-A kernel: usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0

Oct 29 21:38:13 L-061012-A kernel: usb 5-1: Product: BCM2045B

Oct 29 21:38:13 L-061012-A kernel: usb 5-1: Manufacturer: Broadcom Corp

Oct 29 21:38:13 L-061012-A bluetooth: Starting bluetooth service

Oct 29 21:38:13 L-061012-A kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17

Oct 29 21:38:13 L-061012-A kernel: Registered led device: iwl-phy0:radio

Oct 29 21:38:13 L-061012-A kernel: Registered led device: iwl-phy0:assoc

Oct 29 21:38:13 L-061012-A kernel: Registered led device: iwl-phy0:RX

Oct 29 21:38:13 L-061012-A kernel: Registered led device: iwl-phy0:TX

Oct 29 21:38:13 L-061012-A kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Oct 29 21:38:13 L-061012-A hcid[28184]: Bluetooth HCI daemon

Oct 29 21:38:13 L-061012-A hcid[28184]: Parsing /etc/bluetooth/main.conf failed: No such file or directory

Oct 29 21:38:13 L-061012-A hcid[28184]: Starting SDP server

Oct 29 21:38:13 L-061012-A hcid[28184]: Parsing /etc/bluetooth/input.conf failed: No such file or directory

Oct 29 21:38:13 L-061012-A hcid[28184]: Registered input manager path:/org/bluez/input

Oct 29 21:38:13 L-061012-A hcid[28184]: Failed to listen on control channel

Oct 29 21:38:13 L-061012-A hcid[28184]: Parsing /etc/bluetooth/network.conf failed: No such file or directory

Oct 29 21:38:13 L-061012-A bluetooth: Starting hidd

Oct 29 21:38:14 L-061012-A kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3

Oct 29 21:38:14 L-061012-A kernel: Bluetooth: BNEP filters: protocol multicast

Oct 29 21:38:14 L-061012-A kernel: Bridge firewalling registered

Oct 29 21:38:14 L-061012-A kernel: pan0: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM feature.

Oct 29 21:38:14 L-061012-A hcid[28184]: bridge pan0 created

Oct 29 21:38:14 L-061012-A hcid[28184]: Registered manager path:/org/bluez/network

Oct 29 21:38:14 L-061012-A hcid[28184]: Unix socket created: 14

Oct 29 21:38:14 L-061012-A hcid[28184]: Registered manager path:/org/bluez/audio

Oct 29 21:38:14 L-061012-A hcid[28184]: Registered manager path:/org/bluez/serial

Oct 29 21:38:14 L-061012-A hcid[28184]: HCI dev 0 registered

Oct 29 21:38:14 L-061012-A hcid[28184]: HCI dev 0 up

Oct 29 21:38:14 L-061012-A hcid[28184]: Device hci0 has been added

Oct 29 21:38:14 L-061012-A hcid[28184]: Starting security manager 0

Oct 29 21:38:14 L-061012-A hcid[28184]: Device hci0 has been activated

Oct 29 21:38:16 L-061012-A kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready

Oct 29 21:38:16 L-061012-A ifplugd(wlan0)[2977]: Link beat detected.

Oct 29 21:38:17 L-061012-A ifplugd(wlan0)[2977]: Executing '/etc/ifplugd/ifplugd.action wlan0 up'.

Oct 29 21:38:17 L-061012-A avahi-daemon[4569]: Registering new address record for fe80::219:d2ff:fe17:a474 on wlan0.*.

Oct 29 21:38:17 L-061012-A dhclient: wmaster1: unknown hardware address type 801

Oct 29 21:38:17 L-061012-A dhclient: wmaster0: unknown hardware address type 801

Oct 29 21:38:18 L-061012-A dhclient: wmaster1: unknown hardware address type 801

Oct 29 21:38:18 L-061012-A dhclient: wmaster0: unknown hardware address type 801

Oct 29 21:38:19 L-061012-A dhclient: DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6

Oct 29 21:38:20 L-061012-A dhclient: DHCPOFFER from 192.168.1.1

Oct 29 21:38:20 L-061012-A dhclient: DHCPREQUEST on wlan0 to 255.255.255.255 port 67

Oct 29 21:38:22 L-061012-A dhclient: DHCPACK from 192.168.1.1

Oct 29 21:38:22 L-061012-A kernel: iwl3945 0000:03:00.0: PCI INT A disabled

Oct 29 21:38:22 L-061012-A avahi-daemon[4569]: Withdrawing address record for fe80::219:d2ff:fe17:a474 on wlan0.

Oct 29 21:38:22 L-061012-A kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17

Oct 29 21:38:22 L-061012-A kernel: Registered led device: iwl-phy0:radio

Oct 29 21:38:22 L-061012-A kernel: Registered led device: iwl-phy0:assoc

Oct 29 21:38:22 L-061012-A kernel: Registered led device: iwl-phy0:RX

Oct 29 21:38:22 L-061012-A kernel: Registered led device: iwl-phy0:TX

Oct 29 21:38:22 L-061012-A avahi-daemon[4569]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.7.

Oct 29 21:38:22 L-061012-A kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready

Oct 29 21:38:22 L-061012-A avahi-daemon[4569]: New relevant interface wlan0.IPv4 for mDNS.

Oct 29 21:38:22 L-061012-A avahi-daemon[4569]: Registering new address record for 192.168.1.7 on wlan0.IPv4.

Oct 29 21:38:22 L-061012-A NET[28958]: /sbin/dhclient-script : updated /etc/resolv.conf

Oct 29 21:38:22 L-061012-A dhclient: bound to 192.168.1.7 -- renewal in 38871 seconds.

Oct 29 21:38:22 L-061012-A dhclient: receive_packet failed on wlan0: Network is down

Oct 29 21:38:22 L-061012-A ifplugd(wlan0)[2977]: client: Determining IP information for wlan0... done.

Oct 29 21:38:23 L-061012-A ifplugd(wlan0)[2977]: Program executed successfully.

Oct 29 21:38:23 L-061012-A ifplugd(wlan0)[2977]: Link beat lost.

Oct 29 21:38:29 L-061012-A ifplugd(wlan0)[2977]: Executing '/etc/ifplugd/ifplugd.action wlan0 down'.

Oct 29 21:38:29 L-061012-A avahi-daemon[4569]: Withdrawing address record for 192.168.1.7 on wlan0.

Oct 29 21:38:29 L-061012-A avahi-daemon[4569]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.7.

Oct 29 21:38:29 L-061012-A avahi-daemon[4569]: Interface wlan0.IPv4 no longer relevant for mDNS.

Oct 29 21:38:29 L-061012-A kernel: iwl3945 0000:03:00.0: PCI INT A disabled

Oct 29 21:38:29 L-061012-A ifplugd(wlan0)[2977]: Program executed successfully.

Oct 29 21:38:29 L-061012-A kernel: iwl3945 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17

Oct 29 21:38:29 L-061012-A kernel: Registered led device: iwl-phy0:radio

Oct 29 21:38:29 L-061012-A kernel: Registered led device: iwl-phy0:assoc

Oct 29 21:38:29 L-061012-A kernel: Registered led device: iwl-phy0:RX

Oct 29 21:38:29 L-061012-A kernel: Registered led device: iwl-phy0:TX

Oct 29 21:38:29 L-061012-A kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready

------------snip-----------------------------------

 

 

lspci

 

------------snip-----------------------------------

03:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)

------------snip-----------------------------------

 

 

Can someone please help me fix the card configuration?

 

There is another odd thing with the wireless config. I am using a Alfa wireless card (RTL8187):

"Bus 001 Device 005: ID 0bda:8187 Realtek Semiconductor Corp. "

 

The RTL8187 card does work but the signal strength is very low and the LED on the card does not blink while in operation. The RTL card has an external antenna and works pretty well when I boot into Windows including the green LED on the card.

 

Any pointers?

 

Thanks!!

Link to comment
Share on other sites

Guest Siddhartha Jain

Never mind. It is working now. I have no idea how it fixed itself because I have been trying to troubleshoot it for the last 2-3 days but it simply would not work. Today, I flipped the switch on and off a few times and it just worked.

 

The RTL interface issue still remains.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...