On 11/03/2010 04:22 PM, kanenas@hawaii.rr.com 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 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. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org