Grigor Gatchev wrote:
Package: network-manager-kde Version: 1:0.2.2-1 Severity: normal(I'm not sure whether this bug is in network-manager-kde: could be in wpasupplicant, or elsewhere.)When started, KNetworkManager finds the wired device, but not the wireless device. (KWifiManager and command line find it and work OK with it - currently I use them; that's why I suspect wpasupplicant could be guilty, too - V0.6.3-2.)Situation:Newly reinstalled (from scratch) laptop ASUS X51R-AP140. Before the reinstall KNetworkManager worked OK. (I remember it needed some tinkering when I installed it first, but could not recall the details.)Reinstall started with a network CD for Etch, standard system only, then dist-upgraded to Lenny/Sid, and added the rest. Installed MadWiFi for my Atheros-based card (m-a a-i madwifi).Added my user to the netdev group. Read network-manager/README.Debian. Tried installing and removing the recommended packages. My /etc/network/inerfaces: --- # The loopback network interface auto lo iface lo inet loopback address 127.0.0.1 netmask 255.0.0.0 auto eth0 iface eth0 inet dhcp auto ath0 iface ath0 inet dhcp ---
Very likely a NM problem.Could you please send me the output of "nm-tool", "lshal" and "NetworkManager --no-daemon" (you have stop the running NM fist with "/etc/init.d/network-manager stop"
Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
