|
Bugzilla – Full Text Bug Listing |
| Summary: | Wireless nic doesn't connect with ath5k module | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 11.1 | Reporter: | kevin vandeventer <pilotgi> |
| Component: | Network | Assignee: | Tambet Ingo <tambet> |
| Status: | RESOLVED INVALID | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | pilotgi, suprlady |
| Version: | Alpha 2 | ||
| Target Milestone: | --- | ||
| Hardware: | i686 | ||
| OS: | SUSE Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Attachments: | wpa_supplicant debug logs | ||
|
Description
kevin vandeventer
2008-08-29 19:29:13 UTC
Any error message ? Try to connect to wireless network and if it fails. Send output of "dmesg" and /var/log/NetworkManager Thanks /var/log/NetworkManager: Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> starting... Sep 17 17:02:09 linux-uqc5 NetworkManager: <WARN> nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add(): Sucess Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> eth0: Device is fully-supported using driver 'forcedeth'. Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> Found new Ethernet device 'eth0'. Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> (eth0): exported as /org/freedesktop/Hal/devices/net_00_17_31_6f_3c_02 Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> wlan0: Device is fully-supported using driver 'ath5k_pci'. Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> wlan0: driver supports SSID scans (scan_capa 0x01). Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> Found new wireless (802.11) device 'wlan0'. Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> (wlan0): exported as /org/freedesktop/Hal/devices/net_00_15_e9_b7_fd_8b Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> Trying to start the supplicant... Sep 17 17:02:09 linux-uqc5 NetworkManager: <info> Trying to start the system settings daemon... Sep 17 17:02:10 linux-uqc5 NetworkManager: <info> (wlan0): supplicant manager is now in state 1 (from 0). Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): device state change:1 -> 2 Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): bringing up device. Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): preparing device. Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): deactivating device. Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (wlan0): device state change: 1 -> 2 Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (wlan0): bringing up device. Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (wlan0): preparing device. Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (wlan0): deactivating device. Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): carrier now ON (device state 2) Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): device state change:2 -> 3 Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): carrier now OFF (device state 3) Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): device state change:3 -> 2 Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (eth0): deactivating device. Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (wlan0): device state change: 2 -> 3 Sep 17 17:02:13 linux-uqc5 NetworkManager: <info> (wlan0): supplicant interface state change: 1 -> 2. Parts of dmesg relevant to ath5k: ath5k_pci 0000:04:09.0: registered as 'phy0' phy0: Selected rate control algorithm 'pid' ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) Adding 2104472k swap on /dev/sda1. Priority:-1 extents:1 across:2104472k ieee1394: The root node is not cycle master capable; selecting a new root node and resetting... ieee1394: Host added: ID:BUS[0-01:1023] GUID[0011d80000df1ec0] device-mapper: uevent: version 1.0.3 device-mapper: ioctl: 4.13.0-ioctl (2007-10-18) initialised: dm-devel@redhat.com loop: module loaded fuse init (API version 7.9) type=1505 audit(1221688919.287:2): operation="profile_load" name="/bin/ping" name2="default" pid=1757 type=1505 audit(1221688919.322:3): operation="profile_load" name="/sbin/klogd" name2="default" pid=1759 type=1505 audit(1221688919.371:4): operation="profile_load" name="/sbin/syslog-ng" name2="default" pid=1760 type=1505 audit(1221688919.407:5): operation="profile_load" name="/sbin/syslogd" name2="default" pid=1769 type=1505 audit(1221688919.458:6): operation="profile_load" name="/usr/sbin/avahi-daemon" name2="default" pid=1774 type=1505 audit(1221688919.579:7): operation="profile_load" name="/usr/sbin/identd" name2="default" pid=1785 type=1505 audit(1221688919.614:8): operation="profile_load" name="/usr/sbin/mdnsd" name2="default" pid=1786 type=1505 audit(1221688919.650:9): operation="profile_load" name="/usr/sbin/nscd" name2="default" pid=1787 type=1505 audit(1221688919.698:10): operation="profile_load" name="/usr/sbin/ntpd" name2="default" pid=1788 type=1505 audit(1221688919.734:11): operation="profile_load" name="/usr/sbin/traceroute" name2="default" pid=1789 NET: Registered protocol family 10 lo: Disabled Privacy Extensions ip6_tables: (C) 2000-2006 Netfilter Core Team ip_tables: (C) 2000-2006 Netfilter Core Team nf_conntrack version 0.5.0 (16384 buckets, 65536 max) powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4200+ processors (2 cpu cores) (version 2.20.00) powernow-k8: ACPI Processor support is required for SMP systems but is absent. Please load the ACPI Processor module before starting this driver. powernow-k8: ACPI Processor support is required for SMP systems but is absent. Please load the ACPI Processor module before starting this driver. powernow: This module only works with AMD K7 CPUs mtrr: base(0xe0000000) is not aligned on a size(0xff00000) boundary eth0: no link during initialization. ADDRCONF(NETDEV_UP): eth0: link is not ready ADDRCONF(NETDEV_UP): wlan0: link is not ready NET: Registered protocol family 17 wlan0: Initial auth_alg=0 wlan0: authenticate with AP 00:14:6c:94:50:68 wlan0: RX authentication from 00:14:6c:94:50:68 (alg=0 transaction=2 status=0) wlan0: authenticated wlan0: associate with AP 00:14:6c:94:50:68 wlan0: RX AssocResp from 00:14:6c:94:50:68 (capab=0x421 status=0 aid=1) wlan0: associated wlan0: CTS protection enabled (BSSID=00:14:6c:94:50:68) wlan0: switched to short barker preamble (BSSID=00:14:6c:94:50:68) ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready wlan0: disassociate(reason=3) bootsplash: status on console 0 changed to on wlan0: no IPv6 routers present Network manager sees my wireless connection and shows signal strength. It just doesn't connect. Ethernet cable not connected when I did this dmesg. Interesting. After installing openSUSE 11.1 Beta 1, I had no internet connection, wired or wireless. See bug 428135. I switched from NetworkManager to ifup and was able to connect with eth0. Then I configured my wireless with YaST, which was now listed as ath0 instead of wlan0 with the ath5k module. Now I am connected with wireless also. Here is the result of ip r: 192.168.1.0/24 dev ath0 proto kernel scope link src 192.168.1.129 192.168.1.0/24 dev eth0 proto kernel scope link src 192.168.1.132 169.254.0.0/16 dev ath0 scope link 127.0.0.0/8 dev lo scope link default via 192.168.1.1 dev ath0 The version of NetworkManager is 0.7.0.r4060-3.4. *** Bug 407464 has been marked as a duplicate of this bug. *** Sorry, confused, what's the problem here -- seems like it works? Now the problem is probably the title of this bug ;). The problem isn't with ath5k, it's with NetworkManager. The problem I'm having seems to be related etc/resolv.conf not being modified with dns addresses when NetworkManager is used as in bug 429722. This bug is about ppp but the same thing happens with dhcp. If ifup is used, /etc/resolve.conf is modified correctly. Also see bug 429132, comment 23, 24, 25. Reassigning to the gnome people, according to the database, they take care of NM. Please fix PDB up, there is some old maintainers address which BNC won't accept. It looks like your AP does not use any authentication, is that correct? ct 3 21:50:42 linux-m741 NetworkManager: <info> Activation (wlan0/wireless): connection 'kevinmacbook' requires no security. No secrets needed. Oct 3 21:50:42 linux-m741 NetworkManager: <info> Config: added 'ssid' value 'kevinmacbook' Oct 3 21:50:42 linux-m741 NetworkManager: <info> Config: added 'scan_ssid' value '1' Oct 3 21:50:42 linux-m741 NetworkManager: <info> Config: added 'key_mgmt' value 'NONE' Oct 3 21:50:42 linux-m741 NetworkManager: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete. Oct 3 21:50:42 linux-m741 NetworkManager: <info> Config: set interface ap_scan to 1 Oct 3 21:50:42 linux-m741 NetworkManager: <info> (wlan0): supplicant connection state change: 1 -> 2 Oct 3 21:51:07 linux-m741 NetworkManager: <info> Activation (wlan0/wireless): association took too long, failing activation. Please have a look at http://en.opensuse.org/Tracking_down_wireless_problems , enable wpa_supplicant debugging and attach wpa_supplicant log file here. Thanks. Created attachment 253187 [details]
wpa_supplicant debug logs
Yes I'm using wpa2 encryption with a password. I changed from ifup to NetworkManager so I could generate the wpa_supplicant logs with debugging. When I restarted the network I was unable to connect. I checked YaST2 network settings again and the wireless entry was greyed out and I got this error message: "This configuration is not compatible with NetworkManager. Use nm-settings applet or switch to traditional method with ifup." The log file in #10 doesn't have any association attempts, so there's nothing useful in there. I'm confused about your last comment: "I changed from ifup to NetworkManager so I could generate the wpa_supplicant logs with debugging." So you're not using NetworkManager at all? About the message you received, it means you either use traditional method which is configured from yast, or you use NetworkManager, configured from it's own tools (connection editor in gnome, accessible from applet's right-click menu and control center). I didn't notice your comment #7 when I asked for the wpa_supplicant logs. If that's the case, there's no need of wpa_supplicant log files. The /etc/resolv.conf bugs you mention there are all fixed by now, does it not fix your problem? No, I'm not using NetworkManager at all. I can only connect with ifup. If I start NetworkManager, my wireless AP is recognized but I can't connect. When I start NetworkManager, the applet in the panel is gray. Can NetworkManager even run when I'm using ifup? If I do rcnetwork stop and then start NM, the applet in the panel is gray but my wireless AP is listed. NM says wlan0 is disconnected. Clicking on connect does nothing. If I do rcnetwork start, it says " 'NetworkManager' is active but configuration says 'NetControl'. Call rcnetwork restart instead. failed" When I do rcnetwork restart, it starts the network with ifup again. I'm using KDE 4.1.3 NetworkManager-0.7.0.r4274-2.1 NetworkManager-glib-0.7.0.r4274-2.1 NetworkManager-kde4-0.7-5.2 NetworkManager-kde-0.7r848570-20.1 NetworkManager-kde4-lang-11.1-3.3 You need to choose is yast whether you want to use NetworkManager or you want to use traditional ifup. Two programs can not control same hardware at the same time. I still have no idea what doesn't work for you. I get no network connection when I use NetworkManager. I have no idea why NM won't connect. It's what I always used through openSUSE 11.0 but it won't work for me in 11.1. Ifup works fine. What exactly doesn't work? Have you configured your system to use NetworkManager instead of traditional method? Can you see your network cards in NetworkManager? Can you see your access point in NM? Do you use any kind of authentication with it? Which? Does it succeed (as I read from comment #7)? Does it set your IP address and netmask correctly? Does it set the default route correctly? Does it update /etc/resolv.conf correctly? Please have a look at http://en.opensuse.org/Tracking_down_wireless_problems again, enable wpa_supplicant debugging, *try to activate your device", and attach /var/log/NetworkManager and /var/log/wpa_supplicant.log files here. I think at this point you should just close this bug. The title is misleading because I originally thought the problem was related to the ath5k module, but since I can connect with ifup, that obviously isn't the problem. The problem is with NetworkManager and there's plenty of other bug reports of people having the same problems as me. I feel like I've already answered all the questions from comment #16 in my earlier posts anyway. I'll try more trouble shooting when RC 1 comes out. Closing. |