Hello,
Ran an update few days ago and lost network connections.
Tried to install last Realtek drivers, but no success.
Any hint welcome to restore connections.
Thank you
Could you give us a few more pointers as the pictures aren't really helpful:
They only show what you've already written there.
Alas I'm not fully in the clear what "peripherique non gere" exactly means but it does look like your realtek is being recognized.
For starters:
- Is your wifi turned on ... are you sure? Check with '
sudo rfkill list' - Is anything being seen at all .... see the output of '
inxi -n' - Check if any firmware is (or isn't) being loaded on boot, with the output of '
dmesg |grep firmware'.
Ultimately, if you've still got the live version of Elive, then run that and see if that works with your wifi i.e check if it is indeed related to the upgrade and not some silly hardware malfunction.
I think that roughly translates to "device not managed" or "device not found" or something.
It most closely translates to "device not managed", but I don't really understand why that would be the case. meaning NM can't manage the device (see @LupusE's answer below for more details)
Which is, in case of exactness Not helpful at all!
But then again, most GUI error messages fall into the category "stupid". 
1 Like
Google translation of 'peripherique non gere' is 'unmanaged device'.
This means the device is availabe, but networkmanager is not allowed to manage it.
- there is another management, for example
/etc/network/interfaces... rename the file f.ex toold_interfaces - The user is not allowed to use networkmanager. -> Add the user to the right group. But I don't know what is the right group. Option 1. is more likely, anyway.
Edit 1: mote -> more
Edit 2: Translation translated
Edit 3: another typo ... But I think now the message is clear.
1 Like
I like dragons. The're be cute.
Problem 1. not in English ... Easy to fix, during online translation
Problem 2. only a few information ... Easy, if you've seen a lot of these messages. In fact, my group-theory was maybe wrong here, because the symptom than is: NM can't be seen in tray. (But to complete this thought: I'd think it is more easy to search, if you know the way.
netdev should be the group in debian/ubuntu/elive, while network maybe it in arch.)
-
I don't think
netplanis a topic in Elive at the moment. -
Sometimes you'll need to create an empty file
touch /etc/NetworkManager/conf.d/10-globally-managed-devices.conf... (see Bug #1638842 ânetwork-manager does not manage ethernet and bluet...â : Bugs : network-manager package : Ubuntu)
That's it. I'm out for today, good luck.
1 Like
Thank you for this quick feed-back.
Sorry that screenshots are in french, this is my native language ...
The issue is that I could connect to network either with Wifi, Ethernet cable and USB converter.
All have been working very fine until last update, since then, all adapters are declared "Not supported".
Booted on SSD ###################################################
~ âŻâŻâŻ cat /etc/network/interfaces
auto lo
iface lo inet loopback
~ âŻâŻâŻ nmcli device status
enp0s31f6: non-géré
"Intel Ethernet"
ethernet (e1000e), F4:39:09:79:2E:8A, hw, mtu 1500
enx00e04c680578: non-géré
"Realtek RTL8153"
ethernet (r8152), 00:E0:4C:68:05:78, hw, mtu 1500
lo: non-géré
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
wlp1s0: non-géré
"Intel 8265 / 8275"
wifi (iwlwifi), 20:16:B9:50:50:00, hw, mtu 1500
~ âŻâŻâŻ nmcli device status
DEVICE TYPE STATE CONNECTION
enp0s31f6 ethernet non-géré --
enx00e04c680578 ethernet non-géré --
lo loopback non-géré --
wlp1s0 wifi non-géré --
~ âŻâŻâŻ nmcli device show
GENERAL.DEVICE: enp0s31f6
GENERAL.TYPE: ethernet
GENERAL.HWADDR: F4:39:09:79:2E:8A
GENERAL.MTU: 1500
GENERAL.STATE: 10 (non-géré)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
WIRED-PROPERTIES.CARRIER: arrĂȘt
IP4.GATEWAY: --
IP6.GATEWAY: --
GENERAL.DEVICE: enx00e04c680578
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 00:E0:4C:68:05:78
GENERAL.MTU: 1500
GENERAL.STATE: 10 (non-géré)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
WIRED-PROPERTIES.CARRIER: arrĂȘt
IP4.GATEWAY: --
IP6.GATEWAY: --
GENERAL.DEVICE: lo
GENERAL.TYPE: loopback
GENERAL.HWADDR: 00:00:00:00:00:00
GENERAL.MTU: 65536
GENERAL.STATE: 10 (non-géré)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.ADDRESS[1]: 127.0.0.1/8
IP4.GATEWAY: --
IP6.ADDRESS[1]: ::1/128
IP6.GATEWAY: --
IP6.ROUTE[1]: dst = ::1/128, nh = ::, mt = 256
GENERAL.DEVICE: wlp1s0
GENERAL.TYPE: wifi
GENERAL.HWADDR: 20:16:B9:50:50:00
GENERAL.MTU: 1500
GENERAL.STATE: 10 (non-géré)
GENERAL.CONNECTION: --
GENERAL.CON-PATH: --
IP4.GATEWAY: --
IP6.GATEWAY: --
Booted on LIVE CD ####################################################
~ âŻâŻâŻ cat /etc/network/interfaces
auto lo
iface lo inet loopback
~ âŻâŻâŻ nmcli
enx00e04c680578: connecté to Wired connection 2
"Realtek RTL8153"
ethernet (r8152), 00:E0:4C:68:05:78, hw, mtu 1500
ip4 default, ip6 default
inet4 192.168.0.25/24
route4 0.0.0.0/0
route4 192.168.0.0/24
inet6 2a01:e0a:1ca:cbc0:88f1:efd7:c4ed:d647/64
inet6 fe80::c7ea:fe7c:240d:dda2/64
route6 fe80::/64
route6 2a01:e0a:1ca:cbc0::/64
route6 ::/0
wlp1s0: connecté to BARTHES
"Intel 8265 / 8275"
wifi (iwlwifi), 20:16:B9:50:50:00, hw, mtu 1500
inet4 192.168.0.23/24
route4 0.0.0.0/0
route4 192.168.0.0/24
inet6 2a01:e0a:1ca:cbc0:7e38:3a51:6017:9aad/64
inet6 fe80::594c:f5e4:982a:3b23/64
route6 fe80::/64
route6 2a01:e0a:1ca:cbc0::/64
route6 ::/0
enp0s31f6: indisponible
"Intel Ethernet"
ethernet (e1000e), F4:39:09:79:2E:8A, hw, mtu 1500
lo: non-géré
"lo"
loopback (unknown), 00:00:00:00:00:00, sw, mtu 65536
DNS configuration:
servers: 192.168.0.200
interface: enx00e04c680578
servers: fd0f:ee:b0::1
interface: enx00e04c680578
servers: fd0f:ee:b0::1
interface: wlp1s0
servers: 192.168.0.200
interface: wlp1s0
~ âŻâŻâŻ nmcli device status
DEVICE TYPE STATE CONNECTION
enx00e04c680578 ethernet connecté Wired connection 2
wlp1s0 wifi connecté BARTHES
enp0s31f6 ethernet indisponible --
lo loopback non-géré --
~ âŻâŻâŻ nmcli device show
GENERAL.DEVICE: enx00e04c680578
GENERAL.TYPE: ethernet
GENERAL.HWADDR: 00:E0:4C:68:05:78
GENERAL.MTU: 1500
GENERAL.STATE: 100 (connecté)
GENERAL.CONNECTION: Wired connection 2
GENERAL.CON-PATH: /org/freedesktop/NetworkManager/ActiveCo
WIRED-PROPERTIES.CARRIER: marche
IP4.ADDRESS[1]: 192.168.0.25/24
IP4.GATEWAY: 192.168.0.200
IP4.ROUTE[1]: dst = 0.0.0.0/0, nh = 192.168.0.200, mt
IP4.ROUTE[2]: dst = 192.168.0.0/24, nh = 0.0.0.0, mt =
IP4.DNS[1]: 192.168.0.200
IP6.ADDRESS[1]: 2a01:e0a:1ca:cbc0:88f1:efd7:c4ed:d647/64
IP6.ADDRESS[2]: fe80::c7ea:fe7c:240d:dda2/64
IP6.GATEWAY: fe80::e69e:12ff:fe02:5b1b
IP6.ROUTE[1]: dst = fe80::/64, nh = ::, mt = 100
IP6.ROUTE[2]: dst = 2a01:e0a:1ca:cbc0::/64, nh = ::, m
IP6.ROUTE[3]: dst = ::/0, nh = fe80::e69e:12ff:fe02:5b
IP6.DNS[1]: fd0f:ee:b0::1
GENERAL.DEVICE: wlp1s0
GENERAL.TYPE: wifi
Could it be possible that a a driver or service got corrupt during last update ?
Cheers
No worry, my point was that I wasn't sure enough to the exact meaning of 'non gere'.
It could be but I doubt it's a driver or service issue ...... I'm not very knowledgeable to the workings of networkmanager as a "go-between" to get network things done ('nmcli' is exactly that). It would be nicer to get info directly from the system IMO. 
Clearly the interfaces are being seen by networkmanager (which is good) but not being managed as they should after the upgrade.
I gather @LupusE has some experience in trouble shooting networkmanager so I'll leave that up to him.
Considering that you're probably using the Buster based Elive version, this link might interest you as a way of troubleshooting your network like a pro:
Thanks a lot for the answers and the compare between live/installed.
I don't think it is a driver-issue. Because the devices are recognized, but not handled. It is either a network-manager configuration issue or a user rights problem.
It would be easier for us to read with LANG=C ... before the command. This will tell the shell to use the default-language for this command.
For example the first output in German, the second in default:
lupus@zoe:~$ nmcli device status
DEVICE TYPE STATE CONNECTION
enp5s0 ethernet verbunden zoe.LupusE.net
lo loopback nicht verwaltet --
lupus@zoe:~$ LANG=C nmcli device status
DEVICE TYPE STATE CONNECTION
enp5s0 ethernet connected zoe.LupusE.net
lo loopback unmanaged --
lupus@zoe:~$
(For completeness: You're able to see your system language with echo $LANG. And instead of C you'll free to use any installed language, see locale -a)
Back to topic:
Per default die nm (NetworkManager) is set to 'info' and will write the output to /var/log/syslog. Please show us the content:
lupus@zoe:~$ sudo grep -i networkmanager /var/log/syslog
The messages will be sorted from oldest to newest. Only the last ones from the last boot (or maximum today) are important. I hope to read something that will give a hint, why the interfaces are not managed.
The Networkmanager ist only the management for the network-connections. You'll should be able to perform all tasks without nm, too.
Start your system and ask your dhcp (service on your router) for a address:
dhclient enp0s31f6 -v, dhclient enx00e04c680578 -v or dhclient wlp1s0 -v, but wlan is a little harder, because of wpa-supplicant. For starters, just try a wired LAN connection.
dhcp will only work, if the system got the LAN cable is connected. Check with cat /sys/class/net/enx00e04c680578/carrier. 1 is good, 0 is bad. (maybe cat /sys/class/net/enp0s31f6/carrier)
Last one: the command LANG=C ip a would be helpful, for an overview.
Add explanation:
There seems to be three Network devices in/at your system.
lo -> loopback, we'll ignore this one, here
enp0s31f6 -> I do think this is a internal card
enx00e04c680578 -> This should be your USB-Ethernet adapter
wlp1s0 -> your WLAN
If it is a user-rights issue, just type id in a terminal. It should be something like:
lupus@zoe:~$ id
uid=1000(lupus) gid=1000(lupus) Gruppen=1000(lupus),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),109(netdev),113(bluetooth),119(scanner)
The numbers can be different on your system, but there should be at least plugdev and netdev.
1 Like
Thank you for the hints, here are the results :
~ âŻâŻâŻ sudo grep -i networkmanager /var/log/syslog
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.7413] NetworkManager (version 1.14.6) is starting... (for the first time)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.7414] Read config: /etc/NetworkManager/NetworkManager.conf (lib: no-mac-addr-change.conf)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.7500] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.7517] manager[0x562bb391a020]: monitoring kernel firmware directory '/lib/firmware'.
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.7522] monitoring ifupdown state file '/run/network/ifstate'.
Mar 6 11:41:15 localhost dbus-daemon[1169]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.9' (uid=0 pid=1188 comm="/usr/sbin/NetworkManager --no-daemon ")
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9139] hostname: hostname: using hostnamed
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9140] hostname: hostname changed from (none) to "Elive-EliteBook540G5"
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9144] dns-mgr[0x562bb3925900]: init: dns=default, rc-manager=resolvconf
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9157] rfkill0: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/ieee80211/phy0/rfkill0) (driver iwlwifi)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9160] manager[0x562bb391a020]: rfkill: WiFi hardware radio set enabled
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9161] manager[0x562bb391a020]: rfkill: WWAN hardware radio set enabled
Mar 6 11:41:15 localhost dbus-daemon[1169]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.9' (uid=0 pid=1188 comm="/usr/sbin/NetworkManager --no-daemon ")
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9628] ifupdown: interface-parser: parsing file /etc/network/interfaces
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9628] ifupdown: interface-parser: finished parsing file /etc/network/interfaces
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9629] ifupdown: management mode: unmanaged
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9629] settings: Loaded settings plugin: SettingsPluginIfupdown ("/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-settings-plugin-ifupdown.so")
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9630] settings: Loaded settings plugin: NMSKeyfilePlugin (internal)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9692] keyfile: new connection /etc/NetworkManager/system-connections/BARTHES.nmconnection (43f4ed0b-3fe8-4c41-90ff-4edb8478ba78,"BARTHES")
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9704] manager: rfkill: WiFi enabled by radio killswitch; enabled by state file
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9705] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9707] manager: Networking is disabled by state file
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9710] dhcp-init: Using DHCP client 'dhclient'
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9802] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-bluetooth.so)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9815] Loaded device plugin: NMWifiFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wifi.so)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9856] Loaded device plugin: NMTeamFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-team.so)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9884] Loaded device plugin: NMWwanFactory (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-wwan.so)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9902] Loaded device plugin: NMAtmManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.14.6/libnm-device-plugin-adsl.so)
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9910] wifi-nl80211: (wlp1s0): using nl80211 for WiFi device control
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9924] device (lo): carrier: link connected
Mar 6 11:41:15 localhost NetworkManager[1188]: [1646563275.9947] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Mar 6 11:41:16 localhost NetworkManager[1188]: [1646563276.0040] manager: (enp0s31f6): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Mar 6 11:41:16 localhost NetworkManager[1188]: [1646563276.0111] device (wlp1s0): driver supports Access Point (AP) mode
Mar 6 11:41:16 localhost NetworkManager[1188]: [1646563276.0134] manager: (wlp1s0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/3)
Mar 6 11:41:16 localhost NetworkManager[1188]: [1646563276.0440] manager: startup complete
Mar 6 11:41:16 localhost NetworkManager[1188]: [1646563276.0694] modem-manager: ModemManager available
Mar 6 11:41:16 localhost NetworkManager[1188]: [1646563276.0722] supplicant: wpa_supplicant running
Mar 6 11:41:21 localhost NetworkManager[1188]: [1646563281.6178] agent-manager: req[0x7f2a4c001d10, :1.48/org.freedesktop.nm-applet/1001]: agent registered
Mar 6 11:41:26 localhost systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Mar 6 11:41:41 localhost NetworkManager[1188]: [1646563301.7060] bluez: use BlueZ version 5
Mar 6 11:41:41 localhost NetworkManager[1188]: [1646563301.7232] bluez5: NAP: added interface 20:16:B9:50:50:04
~ âŻâŻâŻ
~ âŻâŻâŻ dhclient enp0s31f6 -v
zsh: correct dhclient to _dhclient [nyae]? n
Command 'dhclient' is available in the following places
- /sbin/dhclient
- /usr/sbin/dhclient
The command could not be located because '/sbin:/usr/sbin' is not included in the PATH environment variable.
This is most likely caused by the lack of administrative privileges associated with your user account.
~ âŻâŻâŻ
~ âŻâŻâŻ id
uid=1001(Elive) gid=1001(Elive) groupes=1001(Elive),4(adm),7(lp),20(dialout),22(voice),24(cdrom),25(floppy),27(sudo),29(audio),30(dip),44(video),46(plugdev),60(games),105(input),109(netdev),114(bluetooth),117(lpadmin),120(scanner),121(vboxusers),122(saned),123(sambashare),124(pulse)
~ âŻâŻâŻ
Looks like you have raised a hare 
Cheers
This looks like the culprit.
It might be that some 'state' files have been left behind from previous networkmanager instances.
If that is the case they'll be in /var/lib/NetworkManager/ and have a .state ending....actually there shouldn't be any files there so simply remove them with:
'sudo rm /var/lib/NetworkManager/*.state'
and see if this makes a change when you use:
'sudo nmcli n on'
to enable networking.
Just to be sure that all is actually reloaded correctly and no '.state' files re-appear, do a full reboot.
Let's break down to the important lines
At my system it is only got one line lo=lo.
The parser is doing it magic and right behind it says 'unmanaged'. Interesting. As if there is something in the file /etc/network/interfaces.
Yeah, the dhclient issue was a little slumpy from me. dhclient needs root to work, so it will need to be sudo dhclient [interface] -v.
to explain the output: There is something calls 'dhclient', but in /sbin/ and the ordinary user isn't allowed to execute it.
Simple rule: /bin/ is for user executables, /sbin/ is for superuser executables (needs sudo).
/usr/ stands for something like 'unix system resources'. It is nearly the same as / but much more sorted.
But it looks like there is a wireless network connection to me. At the command iwlist, is your SSID (AP/Router Name) behind the ESSID:?
Bingo, this was the trick !
I had a look at NetworkManager.state before deleting :
[main]
NetworkingEnabled=false <- 
WirelessEnabled=true
WWANEnabled=true
then ran 'sudo nmcli n on'
NetworkManager.state came up immediately, removed it, but back again after reboot :
[main]
NetworkingEnabled=true <- 
WirelessEnabled=true
WWANEnabled=true
So, problem solved, network is working again, immediately after 'sudo nmcli n on', even after several reboots, on all adapters.
Thank you very much to all of you, for your support and all hints you shared.
Kind regards
2 Likes
Heh, I would have just suggested to reinstall Elive 
(fast, it will work, and it will save mostly all your environment)
Heh, in another thread you tell to 'educate' so that is what we're doing here. 
2 Likes
Which is good of course and since the moment somebody knows how to solve a "small" problem, no reinstall is needed
Yeah, a re-install is a quick&dirty solution which ...... actually makes me feel dirty and somehow a powerless victim, if I do that.
Whereas if I solve an issue with knowledge at hand, it's a conquest and practically 'makes my day'. 
