Linux Mint 20.2 Performance Issues and DE Locking Up

Alexzee said:
Now his LMDE 6 installation is going through the same performance issues and black screen as the LM 20.2 install.
Click to expand...
Have you reinstalled only DE or whole system?

Your screenshot lacks interface configuration therefore you need to look into /etc/network/interfaces.d and confirm there is file which configures loopback interface as follows:
Bash: 
auto lo
iface lo inet loopback

Please also post output of ip a to confirm loopback NIC is set up.

If this won't work then next step is to replace networking with systemd-networkd but first you want to investigate if loopback is problem.
 


CaffeineAddict said:
Have you reinstalled only DE or whole system?

Your screenshot lacks interface configuration therefore you need to look into /etc/network/interfaces.d and confirm there is file which configures loopback interface as follows:
Bash: 
auto lo
iface lo inet loopback

Please also post output of ip a to confirm loopback NIC is set up.

If this won't work then next step is to replace networking with systemd-networkd but first you want to investigate if loopback is problem.
Click to expand...
No, he hasn't reinstalled a DE nor has he installed a whole system.

He's booted into Sparky Linux now doing work and needs time.

I'll be back in an hour haven't had lunch yet.
 
While booted into Sparky he mounted the LM 20.2 SSD.
Long story short, /etc/network/interfaces.d is 'empty'. There isn't a config file on LM 20.2 nor is there a config file on his LMDE 6 install either that contains:
Code: 
auto lo
iface lo inet loopback

It does not exist.

How, friend do I replace networking with systemd-networkd?
 
Alexzee said:
How, friend do I replace networking with systemd-networkd?
Click to expand...
Follow these steps:

Bash: 
sudo nano /etc/systemd/network/lo.network

if the file already exist make sure it contains the following (otherwise if it exists update it to look the same):
INI: 
[Match]
Name=lo
Type=loopback

[Network]
Description=loopback

[Address]
Address=127.0.0.1/8
Save config with CTRL + O and exist nano with CTRL + X

Next step is to replace networking with systemd-networkd as follows:
Bash: 
# Backup previous config
sudo mv /etc/network/interfaces /etc/network/interfaces.bak

# Stop networking
sudo systemctl stop networking
sudo systemctl disable networking

# Start systemd-networkd
sudo systemctl start systemd-networkd
sudo systemctl enable systemd-networkd

# Restart NetworkManager
sudo systemctl restart NetworkManager

I assume this system does have NetworkManager
Next step is to open NetworkManager UI (how you open it depends on DE), and then manually configure main NIC which is WI-FI interface.
This includes setting IP address and default gateway at least to be able to connect to internet.
 
CaffeineAddict said:
Follow these steps:

Bash: 
sudo nano /etc/systemd/network/lo.network

if the file already exist make sure it contains the following (otherwise if it exists update it to look the same):
INI: 
[Match]
Name=lo
Type=loopback

[Network]
Description=loopback

[Address]
Address=127.0.0.1/8

Next step is to replace networking with systemd-networkd as follows:
Bash: 
# Backup previous config
sudo mv /etc/network/interfaces /etc/network/interfaces.bak

# Stop networking
sudo systemctl stop networking
sudo systemctl disable networking

# Start systemd-networkd
sudo systemctl start systemd-networkd
sudo systemctl enable systemd-networkd

# Restart NetworkManager
sudo systemctl restart NetworkManager

I assume this system does have NetworkManager
Next step is to open NetworkManager UI (how you open it depends on DE), and then manually configure main NIC which is WI-FI interface.
This includes setting IP address and default gateway at least to be able to connect to internet.
Click to expand...
Understood-

I can create /etc/systemd/network/lo.network in nano no problem there.

However, when my buddy log's into LM 20.2 & LMDE 6 all he get's is a black screen. And we can't get a TTY just hard shutdowns to force a reboot.
Maybe I need to use a LIve Debian 12 USB to create these network config's for both systems?

Yeah, all 3 systems are using NetworkManager.

I'm not well versed in manually configuring the nic.
I'm thinking if the WiFi interface is within NetworkManager I should be able to find it.
I've got the IP and default gateway written down already from previous years.
 
Alexzee said:
Maybe I need to use a LIve Debian 12 USB to create these network config's for both systems?
Click to expand...
All that you'll be able to do is make a backup and create a new lo.network (which is not enough) but you won't be able to stop and start services from live system. you could manually but I've never done this.

I suggest you try start system in recovery mode from GRUB to get CLI access to system without desktop and then execute the commands to stop networking and start systemd-networkd from there, and then reboot normally.
 
CaffeineAddict said:
All that you'll be able to do is make a backup and create a new lo.network (which is not enough) but you won't be able to stop and start services from live system. you could manually but I've never done this.

I suggest you try start system in recovery mode from GRUB to get CLI access to system without desktop and then execute the commands to stop networking and start systemd-networkd from there, and then reboot normally.
Click to expand...
Roger that.

I can't risk mistakes on a system that is not mine and I'm sure you'd agree.
I'll have to get proper rest to focus in order to do this.

Thanks CaffeineAddict!
bb later
 
Headed to friends system now.
It's been a long time since I've entered into Advanced Options from Grub and Entered into rescue mode.
Be back after I follow your instructions in post # 24 and #26.
 
Alexzee said:
It's been a long time since I've entered into Advanced Options from Grub and Entered into rescue mode.
Click to expand...
Every GRUB menu has "Recovery mode" in addition to other regular boot entries to boot the kernel.
If there are multiple kernels make sure to boot into one that you normally boot into.

There is really not much that you could screw, I have recovered my system several times by using this method.

No permanent changes to GRUB are made by default, you only need to take care not to modify GRUB itself but rather get into text mode without desktop which is what recovery mode is used for, to get text mode access to run terminal commands without UI.
You will need to know Username/Password combo to be able to login to system upon boot.
 
Entered Rescue Mode and created the /etc/systemd/network/lo.network file in nano.
Did the back up of the network interfaces file and stopped networking.
Started and enabled systemd-networkd then restarted NetworkManager.

Rebooted and checked on Network Manger. All good.
After 3-5 minutes the DE flashed and turned to an all gray screen and was unresponsive.
Approx: 30 seconds later, the screen flashed and Firefox was open however; the DE, FF and mouse was locked up, frozen and was completely unresponsive.
 
Alexzee said:
Entered Rescue Mode and created the /etc/systemd/network/lo.network file in nano.
Did the back up of the network interfaces file and stopped networking.
Started and enabled systemd-networkd then restarted NetworkManager.

Rebooted and checked on Network Manger. All good.
After 3-5 minutes the DE flashed and turned to an all gray screen and was unresponsive.
Approx: 30 seconds later, the screen flashed and Firefox was open however; the DE, FF and mouse was locked up, frozen and was completely unresponsive.
Click to expand...
Please run ip a in normal boot (not recovery), if you see lo device listed and set to address as configured in lo.network then we can conclude that loopback is not an issue but something else.

In which case regarding possible loopback problem our investigation is done and additional investigations should be focused elsewhere.
 
CaffeineAddict said:
Please run ip a in normal boot (not recovery), if you see lo device listed and set to address as configured in lo.network then we can conclude that loopback is not an issue but something else.

In which case regarding possible loopback problem our investigation is done and additional investigations should be focused elsewhere.
Click to expand...
Ok be back in a few.
I'll post the output of ip a when I return, thanks!
 
CaffeineAddict said:
Please run ip a in normal boot (not recovery), if you see lo device listed and set to address as configured in lo.network then we can conclude that loopback is not an issue but something else.

In which case regarding possible loopback problem our investigation is done and additional investigations should be focused elsewhere.
Click to expand...
The lo device is set to the address as configured in lo.network, unless I'm mistaken--

Code: 
 ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d4:3d:7e:d6:eb:39 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 08:10:76:c5:4b:2c brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.15/24 brd 192.168.0.255 scope global dynamic noprefixroute wlp3s0
       valid_lft 86311sec preferred_lft 86311sec
    inet6 2601:155:2:7860::1/128 scope global dynamic noprefixroute
       valid_lft 185966sec preferred_lft 185966sec
    inet6 2601:155:2:7860:394f:534e:9ca2:8575/64 scope global temporary dynamic
       valid_lft 345512sec preferred_lft 85990sec
    inet6 2601:155:2:7860:60e4:ff38:12a0:ed5a/64 scope global dynamic mngtmpaddr noprefixroute
       valid_lft 345512sec preferred_lft 345512sec
    inet6 fe80::8937:2074:3e3a:c1af/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

FWIW, all 3 distro's: LMDE 6, Sparky Linux and & LM 20.2 are all having this same performance issue.
 
@Alexzee
I'm not sure how to continue troubleshooting this, but what I would do is either start hardware tests (ex. memory test, CPU test etc) or otherwise run a live distro USB to see if problem persist.
 
CaffeineAddict said:
@Alexzee
I'm not sure how to continue troubleshooting this, but what I would do is either start hardware tests (ex. memory test, CPU test etc) or otherwise run a live distro USB to see if problem persist.
Click to expand...
Ok. Thanks for your honesty, much appreciated.
I've got Debian 12 Live on a USB so I can boot into that and trouble shoot with hardware tests.

Memtest should be in the Grub and if not I can burn it to a DVD for his CDROM to read and run.
I hope it's not a memory leak--

And, while I'm at it maybe roll back to an older kernel as well and see if that changes anything.
 
from post#2

Has freedesktop been a part of the install for very long ?
 
The owner should know ?

Disable it if possible.....for no other reason other than to rule it out
 
I have zero experience of freedesktop....This is just a guess on my part
 
Condobloke said:
The owner should know ?

Disable it if possible.....for no other reason other than to rule it out
Click to expand...
He's thinks freedesktop showed when pkg gir1 was installed sometime last week. Maybe the week before:-
Any ideas brother on how to disable it?
 
You must log in or register to reply here.

Members online

Total: 574 (members: 3, guests: 571)

Latest posts

Top