<SOLVED> Random freezes in new installation

[blasjuan]

So I'm restoring an old PC whit the idea of using it for my online classes, I bought a new 2GB DDR2 and a 240GB ssd in which I installed Linux Mint cinnamon. It's my first time using Linux, until this week I had only used Windows.
The problem is that the system randomly freezes and the screen makes a glitch like this: https://imgur.com/8R1yaKv (not my image), and the only way to restore the computer is pressing reset button( Alt + Crtl + F1 does nothing).
When it happens? Like I said it's kind of random, the first time happen trying to open firefox but after restarting the pc firefox worked just fine. Usually happens while triying to open a program.
My system info:

Code: Select all

System:    Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: Cinnamon 4.8.6 
           wm: muffin dm: LightDM Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal 
Machine:   Type: Desktop Mobo: ASUSTeK model: M2N68-AM SE2 v: Rev X.0x serial: <filter> 
           BIOS: American Megatrends v: 1101 date: 10/16/2009 
CPU:       Topology: Dual Core model: AMD Athlon 64 X2 5600+ bits: 64 type: MCP arch: K8 rev.F+ 
           rev: 2 L2 cache: 1024 KiB 
           flags: lm nx pae sse sse2 sse3 svm bogomips: 11652 
           Speed: 2913 MHz min/max: N/A Core speeds (MHz): 1: 2913 2: 2913 
Graphics:  Device-1: NVIDIA C61 [GeForce 7025 / nForce 630a] vendor: ASUSTeK driver: nouveau 
           v: kernel bus ID: 00:0d.0 chip ID: 10de:03d6 
           Display: x11 server: X.Org 1.20.9 driver: nouveau unloaded: fbdev,modesetting,vesa 
           resolution: 1360x768~60Hz 
           OpenGL: renderer: NV4C v: 2.1 Mesa 20.2.6 direct render: Yes 
Audio:     Device-1: NVIDIA MCP61 High Definition Audio vendor: ASUSTeK driver: snd_hda_intel 
           v: kernel bus ID: 00:05.0 chip ID: 10de:03f0 
           Sound Server: ALSA v: k5.4.0-72-generic 
Network:   Device-1: NVIDIA MCP61 Ethernet vendor: ASUSTeK M4N68T series type: network bridge 
           driver: forcedeth v: kernel port: d480 bus ID: 00:07.0 chip ID: 10de:03ef 
           IF: enp0s7 state: down mac: <filter> 
           Device-2: Realtek RTL-8185 IEEE 802.11a/b/g Wireless LAN driver: rtl818x_pci v: kernel 
           port: e800 bus ID: 01:06.0 chip ID: 10ec:8185 
           IF: wlp1s6 state: up mac: <filter> 
Drives:    Local Storage: total: 456.46 GiB used: 21.78 GiB (4.8%) 
           ID-1: /dev/sda vendor: A-Data model: SU630 size: 223.57 GiB speed: 3.0 Gb/s 
           serial: <filter> 
           ID-2: /dev/sdb vendor: Samsung model: HD253GJ size: 232.89 GiB speed: 3.0 Gb/s 
           serial: <filter> 
Partition: ID-1: / size: 218.57 GiB used: 21.78 GiB (10.0%) fs: ext4 dev: /dev/sda5 
Sensors:   System Temperatures: cpu: 40.0 C mobo: 32.0 C 
           Fan Speeds (RPM): cpu: 2402 case-1: 0 
Repos:     No active apt repos in: /etc/apt/sources.list 
           Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
           1: deb https: //mirror1.cl.netactuate.com/linuxmint/packages ulyssa main upstream import backport
           2: deb http: //mirrors.eze.sysarmy.com/ubuntu focal main restricted universe multiverse
           3: deb http: //mirrors.eze.sysarmy.com/ubuntu focal-updates main restricted universe multiverse
           4: deb http: //mirrors.eze.sysarmy.com/ubuntu focal-backports main restricted universe multiverse
           5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
           6: deb http: //archive.canonical.com/ubuntu/ focal partner
Info:      Processes: 188 Uptime: 1h 02m Memory: 3.60 GiB used: 1.65 GiB (45.8%) Init: systemd 
           v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client 
           inxi: 3.0.38 

What I tried so far:
1: Reinstall the O.S

2: Format the disk and install L. Mint mate, this only seems to aggravate the problem since the only way to launch the live session was through compatibility mode. When I tried to do a "regular" live session the screen glitches, I tried to install the O.S from the compatibility mode but when I tried to start, the screen glitches again.

3: Disable all effects

4: Check drivers, driver manager says "Your computer does not need any additional drivers."

Other info:

Code: Select all

inxi -G
Graphics:
  Device-1: NVIDIA C61 [GeForce 7025 / nForce 630a] driver: nouveau 
  v: kernel 
  Display: x11 server: X.Org 1.20.9 driver: nouveau 
  unloaded: fbdev,modesetting,vesa resolution: 1360x768~60Hz 
  OpenGL: renderer: NV4C v: 2.1 Mesa 20.2.6 

Code: Select all

~$ dmesg | grep error
[    8.783913] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro

What should I do? Switching to Xfce desktop might be a solution?
I'm really green in all this and English is my second language so please be easy on me!
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
The solution was just to install the Xfce desktop (keeping the same kernel version), things seems to run a little smoother but the system still freezes if I try to open a video editor program or something similar, but for "light" use works just fine. If I get more random crashes I will try switching to an older Kernel version.

Thank you everybody!!

[spamegg]

Yes, Try XCFE first.

How much RAM do you have? If it's 2GB as you said, then maybe you are running out of RAM. You can add -m to the inxi parameters to show Memory info: inxi -Fxmprz

Your PC is quite old (dual core Athlon, DDR2 RAM, BIOS is from 2009) so you're not gonna have a good time running a modern OS. Maybe try Mint 19 (which is supported until 2023) because you can use the 4.15 kernel which works better on older hardware. After that consider retiring that machine to light offline use and maybe get better hardware.

The "remount" error is a file system issue. You can boot into the Live Install USB/DVD and run fsck /dev/sdxx to fix file system errors (replace sdxx with your boot drive, it will be something like sda2 or sdb1, you can see it with lsblk).

If none of these work, there might be a hardware issue.

[kc1di]

Hi and Welcome to Linux,

With the Nvidia graphics card you'll have to do some work to get it going properly.
see the release note here. https://www.linuxmint.com/rel_ulyssa_cinnamon.php
Scroll down to the section on

Code: Select all

Solving freezes during the boot sequence

I know that the freezes don't always happen during boot. but the cure is the same. Follow the instructions there.

the advise to use the XFCE version is good advise also. Good luck.

[SMG]

The problem is that the system randomly freezes and the screen makes a glitch like this: https://imgur.com/8R1yaKv (not my image), and the only way to restore the computer is pressing reset button( Alt + Crtl + F1 does nothing).

Give LM19.2 Xfce a try. It's possible the older kernel as well as the lighter desktop will be a better match for your older hardware. LM19 is supported for another two years.

The advice about freezes given by kc1di does not apply in this situation because your graphics card is too old to be able to use an Nvidia driver. The nouveau driver, which has already installed, is your only option. There are no other drivers you can use.

2: Format the disk and install L. Mint mate, this only seems to aggravate the problem since the only way to launch the live session was through compatibility mode. When I tried to do a "regular" live session the screen glitches, I tried to install the O.S from the compatibility mode but when I tried to start, the screen glitches again.

It is possible there may be a physical issue with the graphics card, but it is also possible the older 4.15 kernel may be a better match for it.

Code: Select all

~$ dmesg | grep error
[    8.783913] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro

This is not an error. It is a normal part of the boot cycle and you can ignore this. It happens in every boot cycle and happens on everyone's Mint install.

When the system boots, it normally boots in read-write mode so all the drivers and everything else can be set up properly. Once that is done, the root is then remounted in read-only (ro) mode so you can use the system without anything being accidentally overwritten. The word "errors" in that line is just saying to give you messages if there is a problem while in read-only mode.

[kc1di]

The advice about freezes given by kc1di does not apply in this situation because your graphics card is too old to be able to use an Nvidia driver. The nouveau driver, which has already installed, is your only option. There are no other drivers you can use.

Though that is true, you still need the nomodeset parameter for the nouveau driver to work properly.

[SMG]

The advice about freezes given by kc1di does not apply in this situation because your graphics card is too old to be able to use an Nvidia driver. The nouveau driver, which has already installed, is your only option. There are no other drivers you can use.

Though that is true, you still need the nomodeset parameter for the nouveau driver to work properly.

How exactly would that work given nomodeset disables graphics drivers? The reason nomodeset is used in the link you provided is to be able to use software rendering mode (no graphics drivers) so one can get a screen until the Nvidia driver is loaded.

The nomodeset kernel parameter is only to be temporary solution until drivers can be installed and the OP of this thread already has the nouveau driver installed.
___________________________________________

Edited to add: I found this very old thread How to set NOMODESET and other kernel boot options in grub2 which indicates "Adding the nomodeset parameter instructs the kernel to not load video drivers and use BIOS modes instead until X is loaded."

That seems to indicate to me it would not have an effect while the system (and X) is running, but maybe there is something you know about this which indicates otherwise.

[kc1di]

The nomodeset kernel parameter is only to be temporary solution until drivers can be installed and the OP of this thread already has the nouveau driver installed.

The problem is that the Nouveau Driver requires KMS (kernel-modesetting) Which older Nvidia cards do not support well if at all. So it must be disabled in order for the card to work with the Nouveau driver. This is not the case with newer cards which have KMS support and can use the propitiatory divers well. The whole thing is a mess in a sense because Nvidia refuses to release open source drivers and nourveau is forced to use reverse engineering to try to accomplish useful open source drivers for nvidia cards. nomodeset turns of the Kernel mode setting function of the kernel. this may cause limited ability of the card to give good graphics but at least the card will work where it freezes when KMS is requested by the kernel. So yes as you have said it's primarily used for boot, but still useful for regular operation of the card after x has started. It's my understanding that it will not work with a Wayland system however.
from the Wipedia old but still ture:

Nvidia did not release all the needed documentation for its graphics chip, development proceeded under the nouveau project, which uses reverse engineering to build a working open-source driver for Nvidia cards. Nouveau was accepted in version 2.6.33 of the kernel, released on December 10, 2009. Kernel-based mode setting is not only supported by the nouveau driver, it is required

In any event sounds that the OP has found a solution for the time being and hope it works out well for him.