I dared to update KDE on my openSUSE Tumbleweed system to the version 4.9.4 in the previous week. I noticed after a computer restart that my internet browser could not resolve domain names as usual. The network settings icon did not appear in the corresponding notification area.
If I start the program “KNetworkManager” manually, I do not see the expected wired network connection any more in the configuration dialogue. How can I get it back working easily?
Hello. I am not sure but since no one else replied yet to start things off it probably makes sense to verify that the ethernet controller/device is still being found.
From a terminal as root try ‘lspci’ or ‘lspci -v’ (that is the letter L in lowercase, not the number one)
The display from the command “lspci” contains the entry “NVIDIA Corporation MCP77 Ethernet”. A YaST module shows also more information for the device “eth0”.
The network hardware is still working in my Microsoft Windows environment.
The network works also as expected in a session by Knoppix 7.0.5. Which commands should I try to restart the detection for the wired network connection in my “updated” openSUSE system?
KDE already is part of Tumbleweed. What you should do is make a vendor change to Tumbleweed first, then reapply the vendor change to Packman for Tumbleweed. Chances are that you now have package from the mentioned repo mixed with those in Tumbleweed, which IMHO is the case.
You should be able to establish wired ethernet connectivity by disabling the network manager for the moment:
YaST>>Network Devices>>Network Settings, under ‘Global Options’ choose ‘Traditional Method with ifup’. (Proceed with making sure that the ethernet connection is using DHCP.)
Is it possible to determine why the network manager does not like to reactivate the wired connection in my openSUSE system?
YaST>>Network Devices>>Network Settings, under ‘Global Options’ choose ‘Traditional Method with ifup’.
It seems that this tool does not let me adjust the corresponding properties if the top level domain was left empty (without a setting like “.site” or “.local”) in my network configuration.
The first step is getting a working ethernet connection (via ifup). Then you can proceed to determining the integrity of your KDE desktop as Knurpht has advised. It is likely that you have some inconsistent packages as part of your ‘partial’ transition to tumbleweed. Post the output requested by Knurpht.
Another experiment worth trying is to create a new user account, and see if you can establish NM wired ethernet connectvity via that account. If that works, it will just be a NM config issue (perhaps a stale or corrupted file in /etc/NetworkManager/ or similar).
> It seems that this tool does not let me adjust the corresponding
> properties if the top level domain was left empty (without a setting
> like “.site” or “.local”) in my network configuration.
Just a note, although you may not need it: do not use .local domains if
you need to interact with Windows domains (AD), you will not be able to
join.
–
Cheers / Saludos,
Carlos E. R.
(from 11.4, with Evergreen, x86_64 “Celadon” (Minas Tirith))
I dared to update KDE on my openSUSE Tumbleweed system to the version 4.9.5 a moment ago. I could reactivate the network setup method “User Controlled with NetworkManager” by YaST2 after a computer restart.