Mailinglist Archive: opensuse (2835 mails)

< Previous Next >
[opensuse] wireless stops working
  • From: Ken Schneider <suse-list3@xxxxxxxxxxxxx>
  • Date: Wed, 24 Dec 2008 16:58:54 -0500
  • Message-id: <4952B09E.6020109@xxxxxxxxxxxxx>
Relevant entries in messages file:

****************************************************************************
Dec 24 16:42:05 hp9925 kernel: usb 1-1: new high speed USB device using
ehci_hcd and address 5
Dec 24 16:42:05 hp9925 kernel: usb 1-1: configuration #1 chosen from 1 choice
Dec 24 16:42:05 hp9925 kernel: phy2: Selected rate control algorithm 'pid'
Dec 24 16:42:05 hp9925 kernel: Registered led device: rt73usb-phy2:radio
Dec 24 16:42:05 hp9925 kernel: Registered led device: rt73usb-phy2:assoc
Dec 24 16:42:05 hp9925 kernel: Registered led device: rt73usb-phy2:quality
Dec 24 16:42:05 hp9925 kernel: usb 1-1: New USB device found,
idVendor=07d1, idProduct=3c04
Dec 24 16:42:05 hp9925 kernel: usb 1-1: New USB device strings: Mfr=1,
Product=2, SerialNumber=0
Dec 24 16:42:05 hp9925 kernel: usb 1-1: Product: 802.11 bg WLAN
Dec 24 16:42:05 hp9925 kernel: usb 1-1: Manufacturer: Ralink
Dec 24 16:42:05 hp9925 kernel: usb 1-1: Product: 802.11 bg WLAN
Dec 24 16:42:05 hp9925 kernel: usb 1-1: Manufacturer: Ralink
Dec 24 16:42:05 hp9925 ifup: interface 'wmaster0' is a wlan helper
interface. Exiting.
Dec 24 16:42:06 hp9925 ifup: wlan0
Dec 24 16:42:06 hp9925 ifup-wireless: command 'iwconfig wlan0 nick hp9925'
returned
Dec 24 16:42:06 hp9925 ifup-wireless: Error for wireless request "Set
Nickname" (8B1C) :
Dec 24 16:42:06 hp9925 ifup-wireless: SET failed on device wlan0 ;
Operation not supported.
Dec 24 16:42:06 hp9925 kernel: firmware: requesting rt73.bin
Dec 24 16:42:06 hp9925 ifup-dhcp: Starting DHCP4 client on wlan0
Dec 24 16:42:06 hp9925 dhcpcd[23753]: wlan0: dhcpcd 3.2.3 starting
Dec 24 16:42:06 hp9925 dhcpcd[23753]: wlan0: hardware address =
00:1e:58:b4:04:a7
Dec 24 16:42:06 hp9925 dhcpcd[23753]: wlan0: broadcasting for a lease
Dec 24 16:42:07 hp9925 kernel: wlan0: authenticate with AP 00:12:17:38:ed:08
Dec 24 16:42:07 hp9925 kernel: wlan0: authenticated
Dec 24 16:42:07 hp9925 kernel: wlan0: associate with AP 00:12:17:38:ed:08
Dec 24 16:42:07 hp9925 kernel: wlan0: RX AssocResp from 00:12:17:38:ed:08
(capab=0x431 status=0 aid=1)
Dec 24 16:42:07 hp9925 kernel: wlan0: associated
Dec 24 16:42:07 hp9925 ifup-dhcp: .
Dec 24 16:42:09 hp9925 dhcpcd[23753]: wlan0: offered 192.168.1.102 from
192.168.1.1
Dec 24 16:42:09 hp9925 dhcpcd[23753]: wlan0: checking 192.168.1.102 is
available on attached networks
Dec 24 16:42:10 hp9925 ifup-dhcp: .
Dec 24 16:42:10 hp9925 dhcpcd[23753]: wlan0: leased 192.168.1.102 for
86400 seconds
Dec 24 16:42:10 hp9925 dhcpcd[23753]: wlan0: adding IP address
192.168.1.102/24
Dec 24 16:42:10 hp9925 avahi-daemon[3586]: Joining mDNS multicast group on
interface wlan0.IPv4 with address 192.168.1.102.
Dec 24 16:42:10 hp9925 avahi-daemon[3586]: New relevant interface
wlan0.IPv4 for mDNS.
Dec 24 16:42:10 hp9925 avahi-daemon[3586]: Registering new address record
for 192.168.1.102 on wlan0.IPv4.
Dec 24 16:42:10 hp9925 dhcpcd[23753]: wlan0: adding default route via
192.168.1.1 metric 0
Dec 24 16:42:11 hp9925 ifup-dhcp:
Dec 24 16:42:11 hp9925 ifup-dhcp: wlan0 IP address:
192.168.1.102/24 (hp9925)
Dec 24 16:42:11 hp9925 syslog-ng[2325]: Configuration reload request
received, reloading configuration;
Dec 24 16:42:11 hp9925 syslog-ng[2325]: New configuration initialized;
Dec 24 16:42:11 hp9925 ifdown: wlan0
Dec 24 16:42:12 hp9925 ifup: wlan0
Dec 24 16:42:12 hp9925 SuSEfirewall2: SuSEfirewall2 not active
Dec 24 16:42:12 hp9925 dhcpcd[23753]: wlan0: exiting
***************************************************************************

At this point all is well, I can surf the web until the following rears
it's ugly head...

***************************************************************************
Dec 24 16:43:47 hp9925 kernel: wlan0: No ProbeResp from current AP
00:12:17:38:ed:08 - assume out of range
Dec 24 16:43:47 hp9925 kernel: klogd 1.4.1, ---------- state change ----------
***************************************************************************

At which time all surfing comes to a halt. What the hell is ProbeResp and
_WHY_ assume out of range? I'm sitting 3 feet from the AP when this
happens. This card worked great in 11.0.

If I unplug the card and plug it back in it works for about 1.5 minutes
and stops again when ProbeResp rears it's ugly head again.

--
Ken Schneider
SuSe since Version 5.2, June 1998
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups