[SOLVED] ACPI errors and graphics card drivers issues

[Lock3]

Hey, guys,

It's my first post here, so hello everyone.
I've just installed for the first time Linux Mint 64 bits in dual-boot with Windows 10 both in legacy mode.


The dual-boot works fine and so does Mint except that I have these ACPI errors on boot :

Code: Select all

23:31:29 kernel: nouveau 0000:01:00.0: bus: MMIO read of 00000000 FAULT at 611390 [ IBUS ]
23:18:49 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
23:18:49 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
23:18:49 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
23:18:49 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
23:18:49 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
23:18:49 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT4._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
23:18:49 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT4._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
23:18:49 kernel: ACPI Error: Aborting method \_SB.PCI0.SAT0.SPT5._GTF due to previous error (AE_NOT_FOUND) (20190816/psparse-529)
23:18:49 kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PCI0.SAT0.SPT5._GTF.DSSP], AE_NOT_FOUND (20190816/psargs-330)
23:18:49 kernel: nouveau 0000:01:00.0: DRM: failed to create kernel channel, -22

Moreover, it is impossible to install the Nvidia drivers which are recommended in the driver manager. When I try to do it, the system doesn't recognize my graphics card anymore and the image is only managed by the CPU. I specify that I have an RTX 2070.

Secure boot is disabled as well as fast boot on windows 10.

I browsed the forum and tried to modify GRUB without success. Is this a kernel problem?

Any thoughts?

Thank you in advance for your answers

[Pjotr]

Please generate an overview of your system like this:
- Launch a terminal window (this is how to launch a terminal window);
- Make the terminal window full screen, to avoid chopped lines;
- Copy/paste this command into the terminal:

Code: Select all

inxi -Fxz

(if you type: the letter F is a capital letter, and don't omit the space after inxi!)

Press Enter.

Copy/paste the output in your next message.

[Lock3]

Here it is :

Code: Select all

System:
  Kernel: 5.4.0-42-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A serial: <filter> 
  Mobo: ASUSTeK model: MAXIMUS VII RANGER v: Rev 1.xx serial: <filter> 
  BIOS: American Megatrends v: 2012 date: 10/01/2014 
CPU:
  Topology: Quad Core model: Intel Core i7-4790K bits: 64 type: MT MCP 
  arch: Haswell rev: 3 L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 63999 
  Speed: 1401 MHz min/max: 800/4400 MHz Core speeds (MHz): 1: 1400 2: 1400 
  3: 1401 4: 1402 5: 1400 6: 1380 7: 1401 8: 1399 
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2070 Rev. A] vendor: Micro-Star MSI 
  driver: nouveau v: kernel bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.8 driver: modesetting unloaded: fbdev,vesa 
  resolution: 2560x1440~60Hz 
  OpenGL: renderer: llvmpipe (LLVM 10.0.0 256 bits) v: 3.3 Mesa 20.0.8 
  direct render: Yes 
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Device-2: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  Device-3: Logitech [G533 Wireless Headset Dongle] type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-3:3 
  Sound Server: ALSA v: k5.4.0-42-generic 
Network:
  Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e v: 3.2.6-k 
  port: f040 bus ID: 00:19.0 
  IF: eno1 state: down mac: <filter> 
  Device-2: Broadcom and subsidiaries BCM4360 802.11ac Wireless Network 
  Adapter 
  driver: wl v: kernel port: e000 bus ID: 03:00.0 
  IF: wlp3s0 state: up mac: <filter> 
  IF-ID-1: proton0 state: unknown speed: 10 Mbps duplex: full mac: N/A 
Drives:
  Local Storage: total: 3.19 TiB used: 9.88 GiB (0.3%) 
  ID-1: /dev/sda vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB 
  ID-2: /dev/sdb vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB 
  ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
  ID-4: /dev/sdd vendor: Crucial model: CT250MX200SSD1 size: 232.89 GiB 
Partition:
  ID-1: / size: 228.23 GiB used: 9.88 GiB (4.3%) fs: ext4 dev: /dev/sdd1 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A gpu: nouveau temp: 27 C 
  Fan Speeds (RPM): N/A gpu: nouveau fan: 0 
Info:
  Processes: 265 Uptime: 3m Memory: 15.58 GiB used: 1.30 GiB (8.3%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38

Thx

[Pjotr]

Check the support section of the ASUS website for a BIOS update. When available, apply it and test.

[Lock3]

Done.

I chose a 2015 firmware version because the version of 2018 was still in beta status.

It still doesn't work.

When I installed Mint I chose "Something Else" in the installer option and I have created a partition in ext4 an / for mount. Do I have to create a swap partition like older version of ubuntu ? Or this is irrelevant for this subject ?

[Pjotr]

Done.

I chose a 2015 firmware version because the version of 2018 was still in beta status.

Sensible choice.

Do I have to create a swap partition like older version of ubuntu ? Or this is irrelevant for this subject ?

That's indeed irrelevant.

You might try a kernel update from the Canonical Kernel Team PPA:
https://easylinuxtipsproject.blogspot.c ... t.html#ID8
(item 8 )

That should give you the latest kernel from the 5.4 series, which hopefully contains improvements that are relevant for your problem.

[Lock3]

I did as you said and switched to the 5.4.0-44 and unfortunately it doesn't change anything.

I experience some weird crashes too : I tried to open Rhythmbox or the firewall and it's stop the current session and send me back to the login screen. (It happens before the kernel update)

Really weird.

[Lock3]

Ok

So I tried the tip with

Code: Select all

nomodeset

on grub then i tried to reinstall with

Code: Select all

nvidia-driver-450

I still have the ACPI errors and the graphic card still doesn't work.

when i try

Code: Select all

sudo nvidia-settings

i have this error :

Code: Select all

ERROR: Unable to load info from any available system


(nvidia-settings:2118): GLib-GObject-CRITICAL **: 18:34:21.705: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
** Message: 18:34:21.708: PRIME: No offloading required. Abort
** Message: 18:34:21.708: PRIME: is it supported? no

And this my sytem after installing this driver :

Code: Select all

System:
  Kernel: 5.4.0-44-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 
  Desktop: Cinnamon 4.6.7 Distro: Linux Mint 20 Ulyana 
  base: Ubuntu 20.04 focal 
Machine:
  Type: Desktop System: ASUS product: All Series v: N/A serial: <filter> 
  Mobo: ASUSTeK model: MAXIMUS VII RANGER v: Rev 1.xx serial: <filter> 
  UEFI [Legacy]: American Megatrends v: 3003 date: 10/28/2015 
CPU:
  Topology: Quad Core model: Intel Core i7-4790K bits: 64 type: MT MCP 
  arch: Haswell rev: 3 L2 cache: 8192 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
  bogomips: 63999 
  Speed: 1701 MHz min/max: 800/4400 MHz Core speeds (MHz): 1: 1700 2: 1701 
  3: 1700 4: 1701 5: 1703 6: 1701 7: 1703 8: 1703 
Graphics:
  Device-1: NVIDIA TU106 [GeForce RTX 2070 Rev. A] vendor: Micro-Star MSI 
  driver: nvidia v: 450.57 bus ID: 01:00.0 
  Display: x11 server: X.Org 1.20.8 driver: fbdev,modesetting,nouveau 
  unloaded: vesa resolution: 640x480~73Hz 
  OpenGL: renderer: llvmpipe (LLVM 10.0.0 256 bits) v: 3.3 Mesa 20.0.8 
  direct render: Yes 
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: ASUSTeK 
  driver: snd_hda_intel v: kernel bus ID: 00:1b.0 
  Device-2: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI 
  driver: snd_hda_intel v: kernel bus ID: 01:00.1 
  Device-3: Logitech [G533 Wireless Headset Dongle] type: USB 
  driver: hid-generic,snd-usb-audio,usbhid bus ID: 3-3:3 
  Sound Server: ALSA v: k5.4.0-44-generic 
Network:
  Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e 
  v: 3.2.6-k port: f040 bus ID: 00:19.0 
  IF: eno1 state: down mac: <filter> 
  Device-2: Broadcom and subsidiaries BCM4360 802.11ac Wireless Network 
  Adapter 
  driver: wl v: kernel port: e000 bus ID: 03:00.0 
  IF: wlp3s0 state: up mac: <filter> 
Drives:
  Local Storage: total: 3.19 TiB used: 11.23 GiB (0.3%) 
  ID-1: /dev/sda vendor: Crucial model: CT256MX100SSD1 size: 238.47 GiB 
  ID-2: /dev/sdb vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB 
  ID-3: /dev/sdc vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB 
  ID-4: /dev/sdd vendor: Crucial model: CT250MX200SSD1 size: 232.89 GiB 
Partition:
  ID-1: / size: 228.23 GiB used: 11.23 GiB (4.9%) fs: ext4 dev: /dev/sdd1 
Sensors:
  System Temperatures: cpu: 29.8 C mobo: 27.8 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 257 Uptime: N/A Memory: 15.58 GiB used: 759.3 MiB (4.8%) 
  Init: systemd runlevel: 5 Compilers: gcc: 9.3.0 Shell: bash v: 5.0.17 
  inxi: 3.0.38 

I think the issue is between the boot and the driver but i don't understand how.

[Pjotr]

Well, you might still try the bèta BIOS from 2018... After all, if it would make your computer unusable, one would suppose that ASUS would have pulled it long ago. So it doesn't look like a big risk.

[Lock3]

So,

This beta bios was made only for spectre vulnerability on CPU wich I am already protected.

Many users had issues with this Bios and I will not take my chance with it I think.


It's a shame beacause Mint works flawlessly on my laptop and it seems to have many issues with a dual boot on legacy mode. Perhaps should I try to convert all the os on EFI mode ? Is it possible anyway without reinstalling the two OS ?

[SMG]

When the Nvidia driver loads properly, you will see nvidia in both the device driver and the display driver.

Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2070 Rev. A] vendor: Micro-Star MSI
driver: nvidia v: 450.57 bus ID: 01:00.0

Display: x11 server: X.Org 1.20.8 driver: fbdev,modesetting,nouveau
unloaded: vesa resolution: 640x480~73Hz

I don't see it loaded or unloaded in the display drivers, so I'm going to suggest the driver did not install properly. I don't what method you used to install it, but Pjotr's website has a section on NVIDIA: how to install the latest video card drivers and roblm has tips for installing on LM20 in this post (scroll to the section in big blue letters - Mint 20 Nvidia Driver Installation Update).

Hopefully information in one of those two places (or both) can help you.

[Lock3]

I tried the first step already without success unfortunately.

I will try the second one with driver directly downloaded from nvidia website.

Thanks for answering guys.

[Lock3]

The second one was better than the others

Driver nvidia-450 has worked flawlessly with the roblm installation technique (with the driver downloaded on nvidia website) after

Code: Select all

sudo service lightdm start

, every program on Mint worked fine, no crashes.... UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don't recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don't know

[SMG]

Driver nvidia-450 has worked flawlessly with the roblm installation technique (with the driver downloaded on nvidia website) after

Code: Select all

sudo service lightdm start

, every program on Mint worked fine, no crashes....

Great!

UNTIL I have rebooted the system and now the driver is gone, with the GPU. Mint is on hardware only with 640*480 resolution.

ACPI errors still there but it seems to be not the real problem here.

The boot sequence don't recognize the nvidia driver I think.

Boot issue ? kernel issue ? I don't know

Earlier you indicated:

So I tried the tip with

Code: Select all

nomodeset

on grub

The Release Notes for Cinnamon indicate you no longer need "nomodeset" after installing the driver. Do you still have "nomodeset" in grub?

[Lock3]

Yes I removed the nomodeset.

I tried a fresh install again this morning, but again it's like Mint can't find the GPU nivdia-driver after or during the boot sequence.

[Lock3]

OK I've got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn't launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don't know what.

[SMG]

OK I've got something new here.

As I said, I did a fresh install and installed the recommanded nvidia-driver-440 an rebooted. Nothing new for this part, the driver didn't launch.

But I have just disconnected (close session) and login again (without reboot) and then everything works fine.

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don't know what.

That sounds similar to what was happening to several people in this thread. Maybe reading through the thread will help. As I understand it, it is not that something is preventing the driver from starting, but rather something is not telling the driver to start at the correct time in the start-up sequence. I know there is a way to fix this (since several people in the thread were able to do it), but I don't currently have the knowledge level to be able to guide something through the correct steps for doing it.

Perhaps someone with more knowledge than I currently have will be able to help

[Lock3]

I tried to put these lines as it's said in the thread

Code: Select all

Section "Files"
    ModulePath      "/usr/lib/x86_64-linux-gnu/nvidia/xorg"
    ModulePath      "/usr/lib/xorg/modules"
EndSection

in the xorg.conf file in /etc/X11 and in /usr/share/X11 (I tried the first, the second and both) and nothing works. Still need to disconnect and login again to start the driver.

[Pjotr]

So the issue seems to be in the boot process of Mint 20. Something is preventing the driver from starting but I don't know what.

Just a shot in the dark, but you might try this:
https://easylinuxtipsproject.blogspot.c ... .html#ID26
(item 26)

If it doesn't help for your problem, no harm done: it's good for your system anyway....

[Lock3]

Done !

Thanks you for the tip but the issue is still here.

Should I just wait for system updates ?