On 11/01/2010 02:38 PM, Marc Chamberlin wrote:

Of course I also rebooted just to be sure the new kernel was running. But no joy with getting it to actually send/receive anything over the wireless network.

Any guru out there want to guide me into the light and get this thing working? Much appreciate and thanks in advance...

Marc...

Marc, I'm no guru with Encore cards, but common problems with wireless are often associated with encryption methods used (wep, wpa, wpa-2). Post the output of iwconfig so we can look at the connection stats. If you want, you can blank the encryption key info (no that it matters) like this: 16:48 alchemy:~/dev/prg/ccpp/lib/gsl> sudo iwconfig <snip> ath0 IEEE 802.11g ESSID:"skyline" Nickname:"" Mode:Managed Frequency:2.437 GHz Access Point: 00:23:69:5C:FD:B6 Bit Rate:48 Mb/s Tx-Power:16 dBm Sensitivity=1/1 Retry:off RTS thr:off Fragment thr:off Encryption key:****-****-****-****-992A-E954-D3CD-56BC Security mode:restricted Power Management:off Link Quality=46/70 Signal level=-49 dBm Noise level=-95 dBm Rx invalid nwid:976013 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 <snip> Also, have you ever had wireless working on 11.2? We will need to make sure the driver is loaded. (we will know once we see the iwconfig info). Check yast to see when it is being loaded ('on boot', 'on cable connection', 'hotplug', etc..) I don't know whether encore uses wpa_supplicant for encryption or not, but if it does, configuring wpa_supplicant is separate from setting the card up in yast. Somebody here will know what it takes to get the encore card going. -- 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

On 11/02/2010 04:05 PM, Marc Chamberlin wrote:

Thanks David for your reply. OK here is my iwconfig info and just for completeness, my ifconfig info. I have had the wireless working on 11.2 with my laptops built in wireless card, but it failed so I have turned it off and am trying to switch over to using a wireless USB dongle....

First, with 11.3, I had nothing but trouble with the default 2.6.34 kernel and wireless. In fact it would lock my laptop 'tight as a drum'. See: https://bugzilla.novell.com/show_bug.cgi?id=628166 I have configured Yast

to load it 'on boot' and am using WEP 128bit encryption. I double checked the key to make sure it is right, and it is.. In the interim I am using a wired cable for my laptop, but time is running out as my wife is not a happy camper having a cable run across our living room! ;-)

Marc..

Heh.. heh... When I wired my office building, I bought 1000' spool of CAT5E (RJ45 crimper and 200 RJ45 ends) and used about 600' there, the remaining 400' went in the home. There were times with 1 router and 2 switches that the house looked like a spider web. Wife wasn't thrilled either :p <snip>

marcslaptop:/home/marc # ifup wlan2 wlan2 name: 802.11 n WLAN SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext' marcslaptop:/home/marc # iwconfig <snip>

wmaster0 no wireless extensions.

wlan2 IEEE 802.11bgn ESSID:"CHAMBERLIN" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=9 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

OK wmmaster0 is the 'dummy' connection and 'wlan2' is the actual interface. The good news is the interface is created and the driver is loaded. The bad news is the "Access Point: Not-Associated". I presume your access point is configured with ESSID "CHAMBERLIN" -- double check spelling, etc.. the wrong ESSID will kill you. When connected, you should bet the access point MAC back (mine): Access Point: 00:23:69:5C:FD:B6 Check to see what access points you can see from your laptop. Use (as root) 'iwlist wlan2 scan'. My interface is ath0, so I get: 16:51 alchemy:/etc/zypp # iwlist ath0 scan ath0 Scan completed : Cell 01 - Address: 00:23:69:5C:FD:B6 ESSID:"skyline" Mode:Master Frequency:2.437 GHz (Channel 6) Quality=49/70 Signal level=-46 dBm Noise level=-95 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:bcn_int=100 IE: IEEE 802.11i/WPA2 Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (2) : CCMP TKIP Authentication Suites (1) : PSK Cell 02 - Address: 00:16:B6:16:9E:06 ESSID:"linksys_SES_19068" Mode:Master Frequency:2.437 GHz (Channel 6) Quality=2/70 Signal level=-93 dBm Noise level=-95 dBm Encryption key:on Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 18 Mb/s 24 Mb/s; 36 Mb/s; 54 Mb/s; 6 Mb/s; 9 Mb/s 12 Mb/s; 48 Mb/s Extra:bcn_int=100 IE: WPA Version 1 Group Cipher : TKIP Pairwise Ciphers (1) : TKIP Authentication Suites (1) : PSK This will allow you to (1) test that you can see your AP, (2) confirm the ESSID it thinks it has. I don't know if the encore driver makes use of wlanconfig, but you can also use it to scan for AP's. Two steps are required to use wlanconfig: # Insert the scanning module: modprobe wlan_scan_sta # Scan for wireless networks: wlanconfig wlan2 list scan Once you have confirmed the AP ESSID, you can continue to manually connect to the AP: # set the operating mode (Managed or Ad-Hoc) (you can skip this - yours is already managed) iwconfig wlan2 mode Managed # set the frequency or channel (if needed - auto works fine) iwconfig wlan2 channel 3 # set your WEP key iwconfig wlan2 key <yourkey> # check your current keys wlanconfig wlan2 list keys # Connect to the AP iwconfig wlan2 essid "CHAMBERLIN" # (double check spelling, etc.) iwconfig wlan2 key s:password # (for ASCII key entry) iwconfig wlan2 key restricted [3] 0123456789 # (sets mode and uses key index 3) At this point you should be connected to the AP. Confirm with iwconfig that you have something like: Access Point: 00:23:69:5C:FD:B6 Then it is just a matter of getting the IP address if you use dhcp. For suse, I use (as root): /sbin/dhcpcd -D -K -N -t 999999 -h you can also use --debug and --test options to help debug (see man dhcpcd) Going through the process manually will help uncover where the connection is failing. You can check with iwconfig between each step to check progress. When you run into a problem. Post back here. I'm just going through what I did with my atheros card which may not be a 1:1 match for encore, but the process is fairly generic. Post back when you find where the connect doesn't do what it is supposed to. If I can't answer the question, then somebody else on the list probably can.

marcslaptop:/home/marc # ifconfig <snip>

ifconfig looks fine Give it a go and report back. You can do the same with the built in wireless. It *should* work. Also Bob Williams just posted a great howto on upgrading the kernel on 11.3 which I *recommend* you do -- I had nothing but problems with the 2.6.34 kernel. I've included Bob's post on kernel updates below: Problem: The default kernel that ships with openSUSE 11.3 conflicts with the latest Nvidia graphics drivers, leading to frequent freezing of the system for several seconds at a time. My keyboard buffer was also affected, often sending a jumble of the characters I'd typed each time the system caught up with me. Solution: Upgrade the kernel. 1. Add this repository, either in YaST or with zypper ar: http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.3/ 2. In YaST software management, upgrade all your kernel packages to the newer kernel - in my case that's 2.6.36-90-desktop. The packages I had to upgrade were kernel-desktop, kernel-desktop-devel and kernel-devel. Install kernel- sources, if it's not already installed, otherwise upgrade it as well. The easiest way to do this upgrade is to select the Kernel:/HEAD repository and click on 'Switch system packages to the versions in this repository'. 3. Build and install the Nvidia drivers. On the Nvidia website - http://www.nvidia.co.uk/page/home.html - click on 'Download Drivers', enter the details of your graphics card, and download the driver. This will be in the form a shell script, such as NVIDIA-Linux- x86_64-260.19.12.run. (The name will differ if you've selected the 32 bit driver). Save it wherever you like, then make it executable (chmod +x <filename>). Reboot the computer, selecting the new 2.6.36 kernel. Graphics mode will fail, and you will be left at a console login prompt. Login as root, then cd to the directory containing the Nvidia script. Type: ./NVIDIA-Linux-x86_64-260.19.12.run or whatever your file was called. Agree to the licence, then accept all the options offered. The final stage is to ask if you want the script to run nvidia-xconfig for you. The default is No, but I would recommend answering yes here, as you will only have to do this later anyway. Reboot again (:~ # shutdown -r now), and you should be back into a graphical environment. -- 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

David C. Rankin said the following on 11/02/2010 06:13 PM:

[very big snip]

Thank you David. I'm sure that would be of help if I could get my wifi turned on :-) I don't use it much, maybe once a month or less in the local library. back in 11.0 I couldn't turn it off. Now I can't turn it on. HP Compaq presario, lspci reports 0b:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) I have loaded # lsmod | grep b43 b43 185887 0 ssb 55734 1 b43 mac80211 243704 1 b43 cfg80211 155503 2 b43,mac80211 pcmcia 58165 2 b43,ssb mmc_core 72120 3 b43,ssb,sdhci -- The nice part about being a pessimist is that you are constantly being either proven right or pleasantly surprised. -- George F. Will -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Wednesday 03 November 2010 16:38:31 Peter Nikolic wrote:

On Wednesday 03 Nov 2010 12:07:07 Anton Aylward wrote:

...

David C. Rankin said the following on 11/02/2010 06:13 PM:

...

[very big snip]

Thank you David. I'm sure that would be of help if I could get my wifi turned on :-)

I don't use it much, maybe once a month or less in the local library. back in 11.0 I couldn't turn it off. Now I can't turn it on.

HP Compaq presario, lspci reports

0b:03.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03)

I have loaded

# lsmod | grep b43 b43 185887 0 ssb 55734 1 b43 mac80211 243704 1 b43 cfg80211 155503 2 b43,mac80211 pcmcia 58165 2 b43,ssb mmc_core 72120 3 b43,ssb,sdhci

Hi .

I have had to take 11.3 of my laptop a Compaq Presario here as well because i could not get wirless working with a broadcom card i have gone back to 11.2 that works fine this is x86_64 .

I had that with the Broadcom card that came with my Dell Vostro laptop. I got to the point where I replaced it with an Intel 5300agn card that I bought off eBay, which worked out of the box. It wasn't expensive, and for the amount of aggravation it saved, I figure I came out ahead. -- Stan Goodman Qiryat Tiv'on Israel -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Marc Chamberlin said the following on 11/03/2010 12:06 PM:

Anton, Peter, Stan - Please don't hijack this thread, it makes it harder to follow and diverts the focus away. It you want help, please start a separate thread.

And how is my request for help getting wireless adapter to work any different from the the OP asking for help getting the wireless adapter to work? Are you saying we need a different thread for each *type* of adaptor? -- The whole notion of passwords is based on an oxymoron. The idea is to have a random string that is easy to remember. Unfortunately, if it's easy to remember, it's something nonrandom like 'Susan.' And if it's random, like 'r7U2*Qnp,' then it's not easy to remember. -- Bruce Schneier -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Tuesday 02 November 2010 11:05:25 am Marc Chamberlin wrote:

On 11/1/2010 3:38 PM, David C. Rankin wrote:

...

On 11/01/2010 02:38 PM, Marc Chamberlin wrote:

...

Of course I also rebooted just to be sure the new kernel was running. But no joy with getting it to actually send/receive anything over the wireless network.

Any guru out there want to guide me into the light and get this thing working? Much appreciate and thanks in advance...

Marc...

Marc,

I'm no guru with Encore cards, but common problems with wireless are often associated with encryption methods used (wep, wpa, wpa-2). Post the output of iwconfig so we can look at the connection stats. If you want, you can blank the encryption key info (no that it matters) like this:

16:48 alchemy:~/dev/prg/ccpp/lib/gsl> sudo iwconfig <snip>

ath0 IEEE 802.11g ESSID:"skyline" Nickname:"" Mode:Managed Frequency:2.437 GHz Access Point: 00:23:69:5C:FD:B6 Bit Rate:48 Mb/s Tx-Power:16 dBm Sensitivity=1/1 Retry:off RTS thr:off Fragment thr:off Encryption key:****-****-****-****-992A-E954-D3CD-56BC Security mode:restricted Power Management:off Link Quality=46/70 Signal level=-49 dBm Noise level=-95 dBm Rx invalid nwid:976013 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

<snip>

Also, have you ever had wireless working on 11.2? We will need to make sure the driver is loaded. (we will know once we see the iwconfig info). Check yast to see when it is being loaded ('on boot', 'on cable connection', 'hotplug', etc..) I don't know whether encore uses wpa_supplicant for encryption or not, but if it does, configuring wpa_supplicant is separate from setting the card up in yast.

Somebody here will know what it takes to get the encore card going.

Thanks David for your reply. OK here is my iwconfig info and just for completeness, my ifconfig info. I have had the wireless working on 11.2 with my laptops built in wireless card, but it failed so I have turned it off and am trying to switch over to using a wireless USB dongle.... I have configured Yast to load it 'on boot' and am using WEP 128bit encryption. I double checked the key to make sure it is right, and it is.. In the interim I am using a wired cable for my laptop, but time is running out as my wife is not a happy camper having a cable run across our living room! ;-)

Marc..

marcslaptop:/home/marc # ifdown eth0 eth0 device: nVidia Corporation MCP51 Ethernet Controller (rev a3) marcslaptop:/home/marc # ifup wlan2 wlan2 name: 802.11 n WLAN SuSEfirewall2: Warning: no default firewall zone defined, assuming 'ext' marcslaptop:/home/marc # iwconfig lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan2 IEEE 802.11bgn ESSID:"CHAMBERLIN" Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=9 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

marcslaptop:/home/marc # ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:174 errors:0 dropped:0 overruns:0 frame:0 TX packets:174 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:10770 (10.5 Kb) TX bytes:10770 (10.5 Kb)

wlan2 Link encap:Ethernet HWaddr 00:02:6F:5F:98:45 inet addr:192.168.2.10 Bcast:192.168.2.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

wmaster0 Link encap:UNSPEC HWaddr 00-02-6F-5F-98-45-00-00-00-00-00-00-00-00-00-00 UP RUNNING MTU:0 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

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. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

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

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

On 11/03/2010 07:16 PM, Marc Chamberlin wrote:

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...

There is something rotten in Denmark...

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)

Yep, that's the one. I missed the windows part. Linksys Wireless have been great for me (still running older WRT54Gs), so the setup there is simple and just works (as it does for you from windows) Why not use ndiswrapper and use your windows drivers in Linux? http://www.bauer-power.net/2007/09/using-windows-drivers-in-linux.html 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?

It must have been late and I must have been thinking about another wireless issue. Just disregard :-) It is always worth filing a bug report concerning the wireless issue. As mentioned, I have found kernel module alias mismatches with other wireless chipsets. If yast is selecting the module for you, then it should select one that works. If not, then the smart folks need to figure out why it doesn't. You have the best clean config you can have now. persistent-net.rules is now fixed and wlan0 is what you want to work with. (although in theory it doesn't matter) If I had a usb wireless chip giving me that much trouble, I'd 3 pt. it right into file 13 and start over. See what the other recommendations are and post back when you are ready to configure it. We have pretty much exhausted my bag of wireless tricks... -- 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