FileSystem becomes readonly with nvidia-340 drivers

[vlOd]

So I recently upgraded to Linux Mint 20.1 (Cinnamon) to Linux Mint 20.2 (Cinnamon).

I had the nvidia-340 drivers installed before upgrading but after after upgrading, randomly the filesystem would become readonly.
If i uninstall the nvidia-340 drivers and use the nouveau drivers everything is fine and I can do whatever I would try to.
Does anyone know how to fix this????

inxi -Fxxxrz:

Code: Select all

System:
  Kernel: 5.4.0-77-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 5.0.5 wm: muffin 5.0.1 dm: LightDM 1.30.0 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop Mobo: Gigabyte model: GA-78LMT-S2P v: x.x 
  serial: <filter> BIOS: Award v: FC date: 12/19/2011 
CPU:
  Topology: Triple Core model: AMD Athlon II X3 455 bits: 64 type: MCP 
  arch: K10 rev: 3 L2 cache: 1536 KiB 
  flags: lm nx pae sse sse2 sse3 sse4a svm bogomips: 19932 
  Speed: 2100 MHz min/max: 800/3300 MHz Core speeds (MHz): 1: 2100 
  2: 2600 3: 800 
Graphics:
  Device-1: NVIDIA GT218 [GeForce 210] vendor: ASUSTeK driver: nouveau 
  v: kernel bus ID: 01:00.0 chip ID: 10de:0a65 
  Display: x11 server: X.Org 1.20.9 driver: modesetting 
  unloaded: fbdev,vesa resolution: 1440x900~60Hz 
  OpenGL: renderer: NVA8 v: 3.3 Mesa 20.2.6 direct render: Yes 
Audio:
  Device-1: AMD SBx00 Azalia vendor: Gigabyte driver: snd_hda_intel 
  v: kernel bus ID: 00:14.2 chip ID: 1002:4383 
  Device-2: NVIDIA High Definition Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0be3 
  Device-3: Xiongmai web camera type: USB 
  driver: snd-usb-audio,uvcvideo bus ID: 1-2:3 chip ID: 23c5:1478 
  serial: <filter> 
  Sound Server: ALSA v: k5.4.0-77-generic 
Network:
  Device-1: Qualcomm Atheros AR8151 v2.0 Gigabit Ethernet 
  vendor: Gigabyte driver: atl1c v: 1.0.1.1-NAPI port: df00 
  bus ID: 02:00.0 chip ID: 1969:1083 
  IF: enp2s0 state: up speed: 100 Mbps duplex: full mac: <filter> 
Drives:
  Local Storage: total: 372.62 GiB used: 134.90 GiB (36.2%) 
  ID-1: /dev/sda vendor: Kingston model: SV300S37A240G size: 223.57 GiB 
  speed: <unknown> serial: <filter> rev: BBF2 scheme: MBR 
  ID-2: /dev/sdb vendor: Western Digital model: WD1600AVVS-63L2B0 
  size: 149.05 GiB speed: 3.0 Gb/s serial: <filter> rev: 3A01 
  scheme: MBR 
Partition:
  ID-1: / size: 126.74 GiB used: 33.70 GiB (26.6%) fs: ext4 
  dev: /dev/sda5 
Sensors:
  System Temperatures: cpu: 45.6 C mobo: N/A gpu: nouveau temp: 53 C 
  Fan Speeds (RPM): N/A 
Repos:
  No active apt repos in: /etc/apt/sources.list 
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list 
  1: deb https://dl.winehq.org/wine-builds/ubuntu/ focal main
  2: deb http://ppa.launchpad.net/ubuntu-mozilla-security/ppa/ubuntu focal main
  3: deb https://repos.codelite.org/wx3.1.5/ubuntu/ groovy universe
  4: deb http://repository.spotify.com stable non-free
  Active apt repos in: /etc/apt/sources.list.d/anydesk-stable.list 
  1: deb http://deb.anydesk.com/ all main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list 
  1: deb http://mint.mirrors.telekom.ro/repos uma main upstream import backport
  2: deb http://mirrors.nav.ro/ubuntu focal main restricted universe multiverse
  3: deb http://mirrors.nav.ro/ubuntu focal-updates main restricted universe multiverse
  4: deb http://mirrors.nav.ro/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
  Active apt repos in: /etc/apt/sources.list.d/qbittorrent-team-qbittorrent-stable-focal.list 
  1: deb http://ppa.launchpad.net/qbittorrent-team/qbittorrent-stable/ubuntu focal main
  Active apt repos in: /etc/apt/sources.list.d/skype-stable.list 
  1: deb [arch=amd64] https://repo.skype.com/deb stable main
  Active apt repos in: /etc/apt/sources.list.d/steam.list 
  1: deb [arch=amd64,i386] https://repo.steampowered.com/steam/ stable steam
  2: deb-src [arch=amd64,i386] https://repo.steampowered.com/steam/ stable steam
  Active apt repos in: /etc/apt/sources.list.d/sublime-text.list 
  1: deb https://download.sublimetext.com/ apt/stable/
  Active apt repos in: /etc/apt/sources.list.d/vscode.list 
  1: deb [arch=amd64,arm64,armhf] http://packages.microsoft.com/repos/code stable main
Info:
  Processes: 232 Uptime: 2h 18m Memory: 4.63 GiB used: 1.57 GiB (33.9%) 
  Init: systemd v: 245 runlevel: 5 Compilers: gcc: 9.3.0 alt: 10/9 
  Shell: bash v: 5.0.17 running in: gnome-terminal inxi: 3.0.38 

[Moonstone Man]

Code: Select all

System:
  Desktop: Cinnamon 5.0.5 
  Distro: Linux Mint 20.2 Uma base: Ubuntu 20.04 focal 
CPU:
  Topology: Triple Core model: AMD Athlon II X3

You are attempting to run a leading edge operating system on slow, old equipment so it should come as no surprise that there are issues. The issue may not actually be due to the nVidia drivers specifically, but to an interaction of different drivers. It could also be an interaction due to hardware failure that has only now made its presence known. It's difficult to say, and probably doubly-difficult to troubleshoot. I would recommend trying LM Xfce, using the open source driver only, or a different distribution, eg MX Linux, that is geared toward old hardware.

The reason for that advice is that while Linux has advanced at least 11 years ahead of your machine, the machine itself has not moved since the day it was built. Also, just because it worked ok with 20.1, given the age of the machine, it does not follow that it will also work with 20.2.

None of that implies that 20.2 cannot be made to work with nVidia drivers, only that it probably isn't economical to troubleshoot. Also, you make no mention of how the drivers are being installed, so information is missing. Finally, if the machine's performance is acceptable with the nouveau driver then the best course of action is probably to stay with it.

[vlOd]

None of that implies that 20.2 cannot be made to work with nVidia drivers, only that it probably isn't economical to troubleshoot. Also, you make no mention of how the drivers are being installed, so information is missing. Finally, if the machine's performance is acceptable with the nouveau driver then the best course of action is probably to stay with it.

I was installing them from the driver manager, but I didnt try reinstalling them after the upgrade, so after I purged them and then reinstalled them they are pretty stable now.

[Moonstone Man]

... I didnt try reinstalling them after the upgrade ...

Ah, ok. I'll keep that piece of information for future reference. Thank you.