On 11/3/2010 2:41 PM, David C. Rankin wrote:
don't know if 11.2 is ok w.it, but earlier suse versions had occasional issues with network device numbers incremented almost arbitrarily in /etc/udev/rules.d/(some number)persistent-network.rules or persistent-net.rules. The fact that your wlandevice is called wlan2 might confuse a script looking for a wlan0 / wlan1. you might want to manually edit the .rules script by commenting out the line assigning wlan2 to your wireless card and see where an "rcnetwork restart" (as root) or reboot (don't remember well, tried this a while back) takes you. d. You know, I saw that in the 10.x days, but usually with ethX interfaces. Now
On 11/03/2010 04:22 PM, kanenas@hawaii.rr.com wrote: that you mention it, wlan2 does sound like that may be a problem. (it's usually wlan0) IIRC Marc, has the built in wireless + another one. That would account for wlan0 and wlan1 -- but why wlan2?
Marc,
I should have suggested this earlier, but (1) open yast and delete ALL of your wireless connections, (2) go open the udev rules file (on 11.0 it's:)
16:36 alchemy:/etc/udev/rules.d> cat 70-persistent-net.rules # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it,as long as you keep each rule on a single line. # PCI device 0x10ec:0x8136 (r8169) # This file was automatically generated by the /lib/udev/write_net_rules # program run by the persistent-net-generator.rules rules file. # # You can modify it,as long as you keep each rule on a single line. # PCI device 0x10ec:0x8136 (r8169) # PCI device 0x168c:0x001c (ath_pci) # PCI device 0x168c:0x001c (ath_pci) # PCI device 0x168c:0x001c (ath_pci) # PCI device 0x168c:0x001c (ath5k) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:9e:7c:f6:e7", ATTR{type}=="1", KERNEL=="wlan*", NAME="wlan0" SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:38:af:36:b8", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x168c:0x001c (ath_pci) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:1b:9e:7c:f6:e7", ATTR{type}=="1", KERNEL=="ath*", NAME="ath0"
(3) make a backup of the file (always a good idea)
(4) delete all the wireless entries
(5) go back to yast and re-add your wireless card
(6) rcnetwork restart (or I'd just reboot to make sure any lingering code from prior drivers doesn't remain resident in memory)
(7) then go back to working on the connection, scan test, etc..
Thanks d.
Thanks again Kanenas, David for your suggestions... I have followed your advice and removed all my wireless entries from Yast, and from 70-persistent-net.rules. Then starting from ground zero reinstalled the wireless USB dongle with YaST. That got me to where wlan0 is now considered my wireless network interface. Restarted the network, and rebooted, but still no joy getting it to actually communicate... I checked the AP, it is a Linksys WAP54G and the SSID broadcast is enabled. (I presume this is the setting you were referring to, and as I mentioned previously my laptop sees the ESSID when running under Windoz) I also noted that my Linksys AP was configured to use channel 6, and the iwconfig was reporting that the Encore wireless adapter was using the freq for channel 1. So I manually set the 'WIRELESS_CHANNEL' to '6' in my ifcfg-wlan0 file in the /etc/sysconfig/network dir. (Couldn't figure out how to do that via YaST) But still no joy! So now iwconfig gives this report - marcslaptop:/etc/sysconfig/network # iwconfig lo no wireless extensions. eth0 no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11bgn ESSID:"CHAMBERLIN" Mode:Managed Frequency:2.437 GHz Access Point: Not-Associated Tx-Power=11 dBm Retry long limit:7 RTS thr:off Fragment thr:off Encryption key:1234-1234-1234-1234-1234-1234-12 Power Management:on 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 David, you also mentioned the Broadcom driver and asked me to search for it with Google. I don't understand why Broadcom? Under the Hardware tab, Yast reports that it is using the rt2800USB module, and it gives me an alternative choice of rt2870sta module. (I tried both in fooling around with this, still no joy however) Marc... -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org