Bugzilla – Bug 633493
Networkmanager does not work
Last modified: 2012-11-16 05:57:16 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; sv-SE; rv:1.9.2.8) Gecko/20100723 SUSE/3.6.8-0.1.1 Firefox/3.6.8 When changing from traditional network management (ifup) to network management in Yast I get the message 'No network running' when closing the 'network settings' module. The Knetworkmanager does not recognize my network devices (lan, wlan and mobile broadband modem) and the following output is produced from networkmanager if started manually: larsg@vetulusitpc1wl:~> sudo /usr/sbin/NetworkManager --no-daemon NetworkManager: <info> starting... NetworkManager: <info> modem-manager is now available NetworkManager: Loaded plugin ifcfg-suse: (C) 2008 Novell, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager: <info> Found wlan radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1e.0/0000:02:02.0/ieee80211/phy0/rfkill0) (driver <unknown>) NetworkManager: <info> WiFi enabled by radio killswitch; enabled by state file NetworkManager: <info> WWAN enabled by radio killswitch; disabled by state file NetworkManager: <info> Networking is disabled by state file NetworkManager: <info> (eth0): carrier is OFF NetworkManager: <info> (eth0): new Ethernet device (driver: 'tg3') NetworkManager: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 NetworkManager: <info> (eth1): driver does not support SSID scans (scan_capa 0x00). NetworkManager: <info> (eth1): new 802.11 WiFi device (driver: 'ipw2100') NetworkManager: <info> (eth1): exported as /org/freedesktop/NetworkManager/Devices/1 -- Error received: File exists -- Original message: type=0x14 length=56 flags=<REQUEST,ACK,ATOMIC> sequence-nr=1282485955 pid=4214979 NetworkManager: <info> (ttyUSB0): new GSM device (driver: 'option1') NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/NetworkManager/Devices/2 NetworkManager: <WARN> default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files Reproducible: Always Steps to Reproduce: 1.set network management to traditional method (ifup) 2.reset it to managed by network manager 3. Actual Results: no devices to control in knetworkmanager Expected Results: I should have found one wired, one wireless and on mobile connection
Hello, in bug https://bugzilla.novell.com/show_bug.cgi?id=633605 which I reported recently NetworkManager have similar symptoms. In my case NetworkManager was working fine, but stopped working after I upgraded to KDE 4.5 (via One-Click Install from http://kde.org/info/4.5.0.php) and executed zypper to bring all updates. Switching back to "Traditional ifup" networking method allows to connect to network again. Back to Network Manager - network not available. BTW: Problem is not related to KNetworkManager. I also tried LXDE/NetworkManager, network was also not available. So, while in my case problem was initiated by KDE upgrade, I think problem is in Network Manager or some YAST settings/handling of network.
There is continuous (repeatable) problem on my notebook with OpenSUSE 11.3: Ethernet (wired) connection is disabled in NetworkManager. * Wired Network - Disconnected (gray color) Wireless connection is available, and I can connect without any problem. To make sure that problem is not elated to KDE (KNetworkManager) or GNOME, now login to LXDE. But this doesn't solve problem with Ethernet connection. from command line: # nm-tool NetworkManager Tool State: connected - Device: eth1 ----------------------------------------------------------------- Type: Wired Driver: r8169 State: unavailable Default: no HW Address: 00:16:17:51:9A:1D Capabilities: Carrier Detect: yes Speed: 100 Mb/s Wired Properties Carrier: off - Device: wlan1 [Auto dd-wrt] ------------------------------------------------- Type: 802.11 WiFi Driver: rt2500pci State: connected Default: yes HW Address: 00:13:D3:84:FE:9D Capabilities: Speed: 18 Mb/s Wireless Properties WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Access Points (* = current AP) *dd-wrt: Infra, 00:1B:FC:91:83:4C, Freq 2412 MHz, Rate 54 Mb/s, Strength 100 WPA2 hpsetup: Ad-Hoc, 06:5D:57:D0:41:7D, Freq 2437 MHz, Rate 11 Mb/s, Strength 47 pantherx: Infra, 00:1C:C5:D8:34:8C, Freq 2462 MHz, Rate 54 Mb/s, Strength 45 WEP dlink: Infra, 00:26:5A:32:B7:39, Freq 2437 MHz, Rate 54 Mb/s, Strength 45 WPA IPv4 Settings: Address: 192.168.1.51 Prefix: 24 (255.255.255.0) Gateway: 192.168.1.2 DNS: 192.168.1.2
Created attachment 393223 [details] dmesg output from OpenSUSE 11.3 - kernel 2.6.34.7-0 according to dmesg, r8169 module Gigabit Ethernet driver is loaded [ 7.769438] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 7.769468] r8169 0000:04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 7.769526] r8169 0000:04:00.0: setting latency timer to 64 [ 7.769552] r8169 0000:04:00.0: no MSI. Back to INTx. [ 7.770153] r8169 0000:04:00.0: eth0: RTL8168b/8111b at 0xde082000, 00:16:17:51:9a:1d, XID 18000000 IRQ 19 Question is why this module / Ethernet network is not visible in NetworkManager?
(In reply to comment #4) > Created an attachment (id=393223) [details] > dmesg output from OpenSUSE 11.3 - kernel 2.6.34.7-0 > > > according to dmesg, r8169 module Gigabit Ethernet driver is loaded > > [ 7.769438] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded > [ 7.769468] r8169 0000:04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 > [ 7.769526] r8169 0000:04:00.0: setting latency timer to 64 > [ 7.769552] r8169 0000:04:00.0: no MSI. Back to INTx. > [ 7.770153] r8169 0000:04:00.0: eth0: RTL8168b/8111b at 0xde082000, > 00:16:17:51:9a:1d, XID 18000000 IRQ 19 > > Question is why this module / Ethernet network is not visible in > NetworkManager? few lines below - very interesting: [ 7.957259] msi-laptop: Identified laptop model 'MSI S271'. [ 7.958035] eth0 renamed to eth1 by udevd [549] [ 7.969619] udev: renamed network interface eth0 to eth1 what is 'udev' and why it renaming network interface eth0 to eth1? Anyway - according to ifconfig there ar eno interfaces eth0 or eth1. # 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:100 errors:0 dropped:0 overruns:0 frame:0 TX packets:100 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:8028 (7.8 Kb) TX bytes:8028 (7.8 Kb) wlan1 Link encap:Ethernet HWaddr 00:13:D3:84:FE:9D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1721 errors:0 dropped:0 overruns:0 frame:0 TX packets:1426 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1142352 (1.0 Mb) TX bytes:241993 (236.3 Kb)
Created attachment 393224 [details] dmesg from MSI U90 netbook. kernel 2.6.34.7 Another test computer I have - MSI U90 netbook. This system also uses Realtek r8169 Gigabit Ethernet driver [ 11.004606] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 11.004656] r8169 0000:01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [ 11.004723] r8169 0000:01:00.0: setting latency timer to 64 [ 11.004780] alloc irq_desc for 24 on node -1 [ 11.004786] alloc kstat_irqs on node -1 [ 11.004808] r8169 0000:01:00.0: irq 24 for MSI/MSI-X [ 11.006086] r8169 0000:01:00.0: eth0: RTL8102e at 0xf83e8000, 00:21:85:4d:1e:71, XID 14a00000 IRQ 24 But NetworkManager works fine on it, I can disable and re-enable Ethernet network. And Wired connection working! dmesg also has following lines related to r8169 (eth0): [ 40.177553] r8169 0000:01:00.0: eth0: link down [ 40.178176] ADDRCONF(NETDEV_UP): eth0: link is not ready ... [ 91.739476] r8169 0000:01:00.0: eth0: link up [ 91.740136] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 91.766053] r8169 0000:01:00.0: eth0: link down [ 101.848051] eth0: no IPv6 routers present [ 114.934274] r8169 0000:01:00.0: eth0: link up There was nothing like this in previous dmesg file (for MSI S271 notebook) I can only add that both notebooks are connected to the same switch :-)
NetworkManager (nm-tool) output on MSI U90 netbook, with r8169 Ethernet driver. Wired connection running fine. P.S. This system stilluses KDE 4.4.x, I was not adding Factory repository with KDE 4.5.x to tnis computer. Don't know if this is relevant or not. ~> nm-tool NetworkManager Tool State: connected - Device: eth0 [Auto eth0] ---------------------------------------------------- Type: Wired Driver: r8169 State: connected Default: yes HW Address: 00:21:85:4D:1E:71 Capabilities: Carrier Detect: yes Speed: 100 Mb/s Wired Properties Carrier: on IPv4 Settings: Address: 192.168.1.40 Prefix: 24 (255.255.255.0) Gateway: 192.168.1.2 DNS: 192.168.1.2 - Device: wlan0 ---------------------------------------------------------------- Type: 802.11 WiFi Driver: r8180 State: disconnected Default: no HW Address: 00:1D:92:CC:FC:8C Capabilities: Wireless Properties WEP Encryption: yes WPA Encryption: yes WPA2 Encryption: yes Wireless Access Points ZXDSL531BII-66852E: Infra, 00:16:E3:66:85:2E, Freq 2462 MHz, Rate 54 Mb/s, Strength 43 pantherx: Infra, 00:1C:C5:D8:34:8C, Freq 2462 MHz, Rate 54 Mb/s, Strength 61 WEP TRENDnet: Infra, 00:14:D1:57:F8:11, Freq 2412 MHz, Rate 54 Mb/s, Strength 47 WPA Thom_D005807: Infra, 00:24:D1:C8:69:07, Freq 2462 MHz, Rate 54 Mb/s, Strength 50 WPA WPA2 dd-wrt: Infra, 00:1B:FC:91:83:4C, Freq 2412 MHz, Rate 54 Mb/s, Strength 90 WPA2 hpsetup: Ad-Hoc, 06:5D:57:D0:41:7D, Freq 2437 MHz, Rate 11 Mb/s, Strength 62 dlink: Infra, 00:26:5A:32:B7:39, Freq 2437 MHz, Rate 54 Mb/s, Strength 61 WPA ifconfig ------------------- # ifconfig eth0 Link encap:Ethernet HWaddr 00:21:85:4D:1E:71 inet addr:192.168.1.40 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::221:85ff:fe4d:1e71/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:8132 errors:0 dropped:0 overruns:0 frame:0 TX packets:6276 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:4883545 (4.6 Mb) TX bytes:1085049 (1.0 Mb) Interrupt:24 Base address:0x8000 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:176 errors:0 dropped:0 overruns:0 frame:0 TX packets:176 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:12608 (12.3 Kb) TX bytes:12608 (12.3 Kb) wlan0 Link encap:Ethernet HWaddr 00:1D:92:CC:FC:8C UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:50 overruns:0 frame:0 TX packets:2156 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 b) TX bytes:159416 (155.6 Kb) Interrupt:17 Memory:f8670000-f8670100
Created attachment 393236 [details] dmesg from MSI S271, with networking configured as "traditional ifup" dmesg from MSI S271, with networking configured as "traditional ifup" Ethernet connection is now active, and working - this is also visible from dmesg log. [ 11.468637] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [ 11.468674] r8169 0000:04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 [ 11.468735] r8169 0000:04:00.0: setting latency timer to 64 [ 11.468761] r8169 0000:04:00.0: no MSI. Back to INTx. [ 11.472721] r8169 0000:04:00.0: eth0: RTL8168b/8111b at 0xde052000, 00:16:17:51:9a:1d, XID 18000000 IRQ 19 ... [ 11.714290] eth0 renamed to eth1 by udevd [575] [ 11.722495] sdhci: Secure Digital Host Controller Interface driver [ 11.722500] sdhci: Copyright(c) Pierre Ossman [ 11.726437] udev: renamed network interface eth0 to eth1 ... [ 28.032662] r8169 0000:04:00.0: eth1: link up [ 28.032700] r8169 0000:04:00.0: eth1: link up So, networking problem (with NetworkManager) is not related to hardware. ifconfig also confirms that wired (and wireless) adapters are properly configured and received IP address(es) from DHCP server. # ifconfig eth1 Link encap:Ethernet HWaddr 00:16:17:51:9A:1D inet addr:192.168.1.50 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:212821 errors:0 dropped:0 overruns:0 frame:0 TX packets:138002 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:312129915 (297.6 Mb) TX bytes:9510399 (9.0 Mb) Interrupt:19 Base address:0x2000 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:8 errors:0 dropped:0 overruns:0 frame:0 TX packets:8 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:400 (400.0 b) TX bytes:400 (400.0 b) wlan1 Link encap:Ethernet HWaddr 00:13:D3:84:FE:9D inet addr:192.168.1.51 Bcast:192.168.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:786 errors:0 dropped:0 overruns:0 frame:0 TX packets:21 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:106098 (103.6 Kb) TX bytes:5605 (5.4 Kb)
We need a NetworkManager maintainer.
Hi,Bili! This bug seems to occur in both knm and nm . Please have a look at it! Thanks!
No activity for more that 1 1/2y and 11.3 is dead. I will close... please open a new bug if it happens against 12.2 (current stable)