You are not logged in.
hello to you users of the freedom linux!
After installing Cinnamon as an office environment you risk having a hiccup with the network manager who indicates that the Wired on / off switch is unmanaged.
Nothing simpler, it happens by commenting on arguments in the conf interfaces file.
We open a terminal window as root then insert the lines below:
nano /etc/network/interfaces
Then comment on these 2 lines as follows:
#allow-hotplug ****
#iface **** inet dhcp
Adapt the asterisks according to the name of your network interface, if you do not know the name of this one:
ip link show
Choice 2 will tell you
And finally restart the service:
/etc/init.d/network-manager restart
And here is the incident resolved
Last edited by wingcommander1999 (2020-05-20 22:40:11)
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
hello to you users of the freedom linux!
[snip]
And finally restart the service:
systemctl restart network-manager
Not on Devuan! systemctl is a systemd abomination invention.
Try:
sudo service network-manager restart
I've also found this problem with Cinnamon on a fresh install of Beowulf using the Desktop iso on an Intel NUC.
Cinnamon installs Network-Manager, which attempts to takeover network management, rewrites /etc/resolve.conf but doesn't get rid of the conflicting code in /etc/network/interfaces.
The result was that I couldn't access my network either over ethernet or wifi
Currently I still can't get it to work with a fixed IP over wifi, which is what I was trying to use, however DHCP works.
Offline
Why would you want to use NetworkManager instead of ifupdown? NM is pure bloat for a simple ethernet connection.
Simpler solution:
# apt purge network-manager{,-gnome}
EDIT: also remove network-manager-gnome to get rid of nm-applet.
Last edited by Head_on_a_Stick (2020-04-14 09:52:23)
Brianna Ghey — Rest In Power
Offline
Why would you want to use NetworkManager instead of ifupdown? NM is pure bloat for a simple ethernet connection.
Simpler solution:
# apt purge network-manager{,-gnome}
EDIT: also remove network-manager-gnome to get rid of nm-applet.
NM is installed by default on cinnamon, which I find biehn integrated into the environment, and then my hardware is powerful enough to make this nonsense (for a purist) run .
Nice to see a Londoner who quotes a French writer;)
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
Network Manager might be overkill for some users and use cases, however I do rather like to have the applet on my panel to show me the status of my WiFi and to allow me easily to re-configure it if I need too. For someone using a laptop away from base perhaps even more so.
Even when I'm ssh-ing into another machine nm-connection-editor gives me a straightforward graphical interface to change my remote machine's network settings without having to know the syntax and edit the config files directly
To me the problem is the way the Cinnamon Desktop installation packages suite, which includes Network Manager, doesn't play nicely with other setups of interfaces, which might be the way they are configured by default or they may be your personalisations.
What (I think) Network Manager should do when installed is replace the existing /etc/network/interfaces with the simplified version that hands off management to network-manager and back up the original. If Network Manager is then de-installed then it ideally it should return the /etc/network/interfaces file to its previous, hopefullly working, state.
Offline
wingcommander1999 wrote:hello to you users of the freedom linux!
[snip]
And finally restart the service:
systemctl restart network-manager
Not on Devuan! systemctl is a systemd
abominationinvention.Try:
sudo service network-manager restart
I've also found this problem with Cinnamon on a fresh install of Beowulf using the Desktop iso on an Intel NUC.
Cinnamon installs Network-Manager, which attempts to takeover network management, rewrites /etc/resolve.conf but doesn't get rid of the conflicting code in /etc/network/interfaces.
The result was that I couldn't access my network either over ethernet or wifiCurrently I still can't get it to work with a fixed IP over wifi, which is what I was trying to use, however DHCP works.
I'm confused, I forgot to adapt my tutorial based on devuan.
Everything is in order
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
Then comment on these 2 lines as follows:
#allow-hotplug **** #iface **** inet dhcp
Where did you get those two lines? My interfaces file only has the entry for the loopback device. Did you set up the network manually during the install?
Offline
Then comment on these 2 lines as follows:
#allow-hotplug **** #iface **** inet dhcp
Where did you get those two lines? My interfaces file only has the entry for the loopback device. Did you set up the network manually during the install?
Nope I did not do anything, it was thus by default before having commented on the 2 lines described, here a screenshot:
Last edited by wingcommander1999 (2020-04-15 15:27:09)
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
OK, thanks. That's odd. I did two cinnamon installs yesterday from the desktop iso - one with a mirror and one without a mirror. I didn't get those lines in either case.
Offline
Apologies in that I'm a bit off topic since I was trying to set up fixed IP WiFI not an Ethernet connection at the time I hit the same issue.
My fresh install of Beowulf-Beta (with Cinnamon) looked like this (now suiitably anonymised):
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
allow-hotplug wlan0
iface wlan0 inet static
address 192.168.1.21/24
gateway 192.168.1.254
# wireless-* options are implemented by the wireless-tools package
wireless-mode managed
wireless-essid *******
wireless-key1 *************
# dns-* options are implemented by the resolvconf package, if installed
dns-nameservers 192.168.1.254
dns-search mydomain.mytld
I started with a WiFi connection and no Ethernet, I had to configure the WiFi iinterface during the install.
As I recall something then broke (probably the issue we are discussing) and I lost my connections. I had to run off-network until I'd found that i needed to comment out all but the loopback network interface, when it started working again. And I could then only run it with DHCP, not fixed IP as I was attempting to do.
It's now running nicely over Ethernet.
Last edited by Marjorie (2020-04-15 19:50:56)
Offline
Why would you want to use NetworkManager instead of ifupdown? NM is pure bloat for a simple ethernet connection.
Simpler solution:
# apt purge network-manager{,-gnome}
EDIT: also remove network-manager-gnome to get rid of nm-applet.
@Head_on_a_Stick
after testing your line I have this as a result:
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
cinnamon-common cjs crda dns-root-data dnsmasq-base gir1.2-appindicator3-0.1
gir1.2-caribou-1.0 gir1.2-clutter-1.0 gir1.2-cmenu-3.0 gir1.2-cogl-1.0
gir1.2-coglpango-1.0 gir1.2-gdesktopenums-3.0 gir1.2-gnomedesktop-3.0
gir1.2-gtkclutter-1.0 gir1.2-json-1.0 gir1.2-keybinder-3.0
gir1.2-meta-muffin-0.0 gir1.2-nm-1.0 gir1.2-nma-1.0 gir1.2-upowerglib-1.0
gnome-backgrounds gvfs-bin iw libcaribou-common libcaribou0 libcjs0
libimagequant0 libkeybinder-3.0-0 libmozjs-52-0 libndp0 libteamdctl0
metacity-common mobile-broadband-provider-info python3-olefile python3-pampy
python3-pexpect python3-pil python3-ptyprocess python3-pyinotify sgml-base
wireless-regdb
Veuillez utiliser « apt autoremove » pour les supprimer.
Les paquets suivants seront ENLEVÉS :
blueman* cinnamon* network-manager* network-manager-gnome*
0 mis à jour, 0 nouvellement installés, 4 à enlever et 2 non mis à jour.
Après cette opération, 24,3 Mo d'espace disque seront libérés.
Souhaitez-vous continuer ? [O/n]
At the end you can read that Cinnamon get fully purged, isn't especially what i search.
We can DL wicd then stop and disable NM without removing it.
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
Note that you can make the command speak English by using
# LC_ALL=C apt purge network-manager{,-gnome}
At the end you can read that Cinnamon get fully purged, isn't especially what i search.
Well that's just stupid, even the GNOME desktop doesn't list network-manager-gnome as a dependency...
We can DL wicd then stop and disable NM without removing it.
Why use wicd? An ethernet connection just needs two lines in /etc/network/interfaces (or four if you don't want to use DHCP).
Anyway, disable NM with
# update-rc.d network-manager disable
Brianna Ghey — Rest In Power
Offline