Version: (using KDE KDE 3.5.4) Installed from: Ubuntu Packages OS: Linux hey mates, since today my knetworkmanager worked, and everything was fine. Most stable networktool I have ever seen and the most important advantage, it supported wpa. But suddenly after I added the loopback device in interface it stopped working. I tried everything.. but couldn't get it fixed. Even to delete the stuff I added couldn't solve the problem, though it was basically all I did... I read knetworkmanager works with HAL to get information about the network devices. But I don't believe that. lshal tells me that everythning is fine with my wireless pci card but knetworkmanager keeps on telling me that there are no network devices at all. What a bullshit! Please help me!!!! Why can't get knetworkmanager the required inforamtion from hal to see my wlan card????????? Thanks
knetworkmanager only uses the informations provided by networkmanager daemon, which isn't maintained by KDE
I'm having the same problem, however, I didn't add anything to interface. When I click the KNetworkManager in the task bar, it only shows the "Wired Devices" section, and the "Wireless Devices" section doesn't show at all. Funny thing is when I move my mouse pointer over to the options menu item, a sub-menu appears with commands to disable or enable my wireless device.
What does 'nm-tool' say? Is your card listed there? I also hear Ubuntu patched NetworkManager daemon to ignore any interfaces listed in /etc/network/interfaces, maybe this is the reason - but I know very little about xbuntu.
I can also see my wireless card (Buffalo WLI-CB-G54A) using lshal but get "no network device found" plus option to Disable Wireless using KNetworkManager. I tried removing all interfaces except lo from /etc/network/interfaces and restarting the network but still the same.
Output from lshal as above: nick@nick-laptop:~$ lshal --show pci_14e4_4320 -l udi = '/org/freedesktop/Hal/devices/pci_14e4_4320' info.udi = '/org/freedesktop/Hal/devices/pci_14e4_4320' (string) linux.subsystem = 'pci' (string) linux.hotplug_type = 1 (0x1) (int) pci.subsys_product = 'Unknown (0x0324)' (string) pci.subsys_vendor = 'Melco Inc' (string) info.product = 'BCM4306 802.11b/g Wireless LAN Controller' (string) pci.product = 'BCM4306 802.11b/g Wireless LAN Controller' (string) info.vendor = 'Broadcom Corporation' (string) pci.vendor = 'Broadcom Corporation' (string) pci.device_protocol = 0 (0x0) (int) pci.device_subclass = 128 (0x80) (int) pci.device_class = 2 (0x2) (int) pci.subsys_vendor_id = 4436 (0x1154) (int) pci.subsys_product_id = 804 (0x324) (int) pci.vendor_id = 5348 (0x14e4) (int) pci.product_id = 17184 (0x4320) (int) info.linux.driver = 'ndiswrapper' (string) pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.0/0000:02:00.0' (string) info.parent = '/org/freedesktop/Hal/devices/pci_104c_ac1b_0' (string) info.bus = 'pci' (string) linux.sysfs_path_device = '/sys/devices/pci0000:00/0000:00:02.0/0000:02:00.0' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:02.0/0000:02:00.0' (string)
i have the same problem...it was resolved in previous versions but now reappeard after the last update
Same problem as #2 above. Using Kubuntu.
Hi, with me all worked fine until upgrading to Gutsy. Now I'm having the same problems as #2 above.
I wanted to file a new Bug report while this report got listed in the check for duplicates. The bug is: No GUI way to fall back to Knetworkmanager interface management mode after using manual configuration GUI for the interface. No notification about the cause of lack of management. Now i see this is explained by the #3 comment - since NetworkManager ignores all interfaces listed in /etc/network/interfaces, and that's what the knetworkmanager's manual configuration updates. To fix the issue one needs to remove the corresponding entries trom the file, just as directed in http://ubuntuforums.org/showthread.php?t=528421 , where I found out that I wasn't the only confused user. More specifically, manual configuration is not in the knetworkmanager component but it is a configuration panel from KDE that can be shown by issuing "kcmshell kcm_knetworkconfmodule". Nevertheless IMHO either knetworkmanager should not rely on NetworkManager or the "feature" of ignoring manualy configured interfaces that NM introduced should be marked as a regression bug. Let me know if repairing the interfaces file is not a remedy for this bug so I can submit a new bug report.
Another solution would be to add an onption to "Manage Interface With Knetwork" which would cause the corresponding entries to be removed from /etc/network/interfaces. Right now the interfaces are missign from the popup menu which totally confuses the user to think his network cards are not properly installed.
Kubuntu problem according to comment #9, they added the patch to hide manually configure devices from NM. Please take it to K|Ubuntu.