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