jim wrote: > > I just upgraded my box from 10.0 to 10.2, and this apparently broke the > wireless network connection, which had been fine. Some points about the > problem: > > This is software, not hardware, the card is known-good and works > fine in Win, also worked fine in Linux until the upgrade. There is no > driver issue, it is a linksys with RT2500 chipset. > > The setup process for the wireless connection goes OK until you try > and set the connection's mode to Managed using the command line iw* > utitlities. This gets you an error message: "SET failed on device ra0 ; > Device or resource busy." Also there is a line in /var/log/messages, > "ra0: cannot create symlink to default key." when this happens. I then > tried iwconfig to show status and got this: > > MASTERBEAST:/var/log # iwconfig > lo no wireless extensions. > > eth0 no wireless extensions. > > sit0 no wireless extensions. > > wmaster0 IEEE 802.11g Frequency:2.412 GHz > RTS thr:off Fragment thr=2346 B > > ra0 IEEE 802.11g ESSID:"ParadiseNett2005" > Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated > RTS thr:off Fragment thr=2346 B > Encryption key:off > > MASTERBEAST:/var/log # > > I don't know where wmaster0 comes from, ra0 is the one I tried to > configure. This didn't happen with 10.0. Also the encryption isn't on > (should be, iwconfig did not complain when I set it). > > Trying to do the same thing using Yast2 and Netwokr manager appears > to work fine but actually doesn't. Here's the output in > /var/log/messages. > > Jan 15 18:44:17 MASTERBEAST NetworkManager: <info> ra0: Device is > fully-supported using driver 'rt2500pci'. > Jan 15 18:44:17 MASTERBEAST NetworkManager: <WARN> > nm_device_802_11_wireless_set_mode(): error setting card ra0 to Inf > rastructure mode: Device or resource busy > Jan 15 18:44:17 MASTERBEAST NetworkManager: <info> nm_device_init(): > waiting for device's worker thread to start > Jan 15 18:44:17 MASTERBEAST kernel: ra0: starting scan > Jan 15 18:44:17 MASTERBEAST NetworkManager: <info> nm_device_init(): > device's worker thread started, continuing. > Jan 15 18:44:17 MASTERBEAST NetworkManager: <info> Now managing > wireless (802.11) device 'ra0'. > Jan 15 18:44:17 MASTERBEAST NetworkManager: <info> Deactivating > device ra0. > Jan 15 18:44:17 MASTERBEAST kernel: ra0: cannot create symlink to > default key > Jan 15 18:44:17 MASTERBEAST NetworkManager: <WARN> > nm_device_802_11_wireless_set_mode(): error setting card ra0 to Inf > rastructure mode: Device or resource busy > > At this point I can't ping my wireless router successfully. > > This one has me stumped, I'll admit. Anyone seen this? My guess is > that there is some option somewhere that has to be set a certain way for > this to work, but it is not obvious, to say the least. I remember this > being a 15-minute process in 10.0. Possibly Network Mgr is tripping up > somewhere & creating the wmaster0 connection which has a lock on some > resource. I would appreciate a pointer to the docs where this might be > discussed... > > Jim > >
I have the same problem with my IBM T20 laptop it worked great in 10.0, 10.1 but the wireless broke in 10.2. I could get it to work if I unplugged the wireless card and plugged it into my other PCMICA slot and set it up again using YAST to set it up. But the next time I rebooted the computer it would be broken again and the I could make it work is deleting the old setup and plugging it into the other slot. I tried setting things up using ifconfig and that didn't help either. I got the feeling that it is a pcmica problem and not a wlan problem. I ended giving up and re-installing 10.1 which works fine after installing all the patches again. -- Robert Cunningham Sr. Physics Laboratory Coordinator /RSO -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
