dmesg error messages - something to fix?

English Install/Boot/Login
1

Suggestions how to fix these error messages?

**localhost:~ #** dmesg | egrep "error|Error" 
    0.841040] RAS: Correctable **Error**s collector initialized. 
    1.808522] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.808528] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
    1.809083] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT0._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.809089] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT0._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
    1.809306] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.809312] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
    1.812788] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.812794] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
    1.814135] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT4._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.814141] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT4._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
    1.816407] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.816412] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT5._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
    1.818992] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT1._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.818998] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT1._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
    1.820351] ACPI BIOS **Error** (bug): Could not resolve symbol \_SB.PCI0.SAT0.PRT5._GTF.DSSP], AE_NOT_FOUND (20210730/psargs-330) 
    1.820357] ACPI **Error**: Aborting method \_SB.PCI0.SAT0.PRT5._GTF due to previous **error** (AE_NOT_FOUND) (20210730/psparse-531) 
   11.115593] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv106_fuc084 failed with **error** -2 
   11.115603] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv106_fuc084d failed with **error** -2 
   39.968808] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: **error**s=remount-ro. Quota mode: none. 
   40.498913] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv106_fuc084 failed with **error** -2 
   40.498923] nouveau 0000:01:00.0: Direct firmware load for nouveau/nv106_fuc084d failed with **error** -2

My system is as follows:

**localhost:~ #** inxi -Fz 
**System:    Kernel:** 5.14.21-150400.24.21-default x86_64 **bits:** 64 **Console:** pty pts/0 **Distro:** openSUSE Leap 15.4 
**Machine:   Type:** Desktop **System:** MSI **product:** MS-7971 **v:** 1.0 **serial:** N/A 
           **Mobo:** MSI **model:** Z170-A PRO (MS-7971) **v:** 1.0 **serial:** <filter> **UEFI:** American Megatrends **v:** 1.K0 **date:** 07/10/2018 
**CPU:       Info:** Quad Core **model:** Intel Core i7-6700K **bits:** 64 **type:** MT MCP **cache:****L2:** 8 MiB 
           **Speed:** 800 MHz **min/max:** 800/4200 MHz **Core speeds (MHz):****1:** 800 **2:** 800 **3:** 800 **4:** 800 **5:** 800 **6:** 800 **7:** 800 **8:** 800 
**Graphics:  Device-1:** NVIDIA GK208B [GeForce GT 730] **driver:** nouveau **v:** kernel 
           **Device-2:** Microdia Camera **type:** USB **driver:** snd-usb-audio,uvcvideo 
           **Display:****server:** SUSE LINUX 1.20.3 **driver:****loaded:** nouveau **unloaded:** fbdev,modesetting,vesa 
           **resolution:** 2560x1440~60Hz 
           **OpenGL:****renderer:** llvmpipe (LLVM 11.0.1 256 bits) **v:** 4.5 Mesa 21.2.4 
**Audio:     Device-1:** Intel 100 Series/C230 Series Family HD Audio **driver:** snd_hda_intel 
           **Device-2:** NVIDIA GK208 HDMI/DP Audio **driver:** snd_hda_intel 
           **Device-3:** Microdia Camera **type:** USB **driver:** snd-usb-audio,uvcvideo 
           **Sound Server-1:** ALSA **v:** k5.14.21-150400.24.21-default **running:** yes 
           **Sound Server-2:** PulseAudio **v:** 15.0 **running:** yes 
           **Sound Server-3:** PipeWire **v:** 0.3.49 **running:** yes 
**Network:   Device-1:** Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet **driver:** r8169 
           **IF:** eth0 **state:** up **speed:** 1000 Mbps **duplex:** full **mac:** <filter> 
**Drives:    Local Storage:****total:** 5.16 TiB **used:** 2.45 TiB (47.4%) 
           **ID-1:** /dev/nvme0n1 **vendor:** Samsung **model:** MZVPV512HDGL-00000 **size:** 476.94 GiB 
           **ID-2:** /dev/sda **vendor:** Intel **model:** SSDSA2CW160G3 **size:** 149.05 GiB 
           **ID-3:** /dev/sdb **vendor:** Seagate **model:** ST3500418AS **size:** 465.76 GiB 
           **ID-4:** /dev/sdc **vendor:** Seagate **model:** ST3500418AS **size:** 465.76 GiB 
           **ID-5:** /dev/sdd **type:** USB **vendor:** Seagate **model:** Expansion **size:** 3.64 TiB 
**Partition: ID-1:** / **size:** 39.08 GiB **used:** 9.43 GiB (24.1%) **fs:** ext4 **dev:** /dev/nvme0n1p3 
           **ID-2:** /boot/efi **size:** 155.8 MiB **used:** 6 MiB (3.9%) **fs:** vfat **dev:** /dev/nvme0n1p1 
           **ID-3:** /home **size:** 426.88 GiB **used:** 124.42 GiB (29.1%) **fs:** ext4 **dev:** /dev/nvme0n1p4 
**Swap:      ID-1:** swap-1 **type:** partition **size:** 2.01 GiB **used:** 0 KiB (0.0%) **dev:** /dev/nvme0n1p2 
**Sensors:   System Temperatures:****cpu:** 56.0 C **mobo:** 29.8 C **gpu:** nouveau **temp:** 60.0 C 
           **Fan Speeds (RPM):** N/A 
**Info:      Processes:** 269 **Uptime:** 0h 9m **Memory:** 62.76 GiB **used:** 2.29 GiB (3.6%) **Shell:** Bash **inxi:** 3.3.07
2

Search result:
https://blog.le-vert.net/?p=24

It’s a buggy ACPI implementation in your BIOS.

3

There were also some nouveau and EXT4-fs errors?

The BIOS bugs are obviously not much to do with. Upgraded to (at least then) the latest BIOS Revision 5.12 in 2020:

# dmidecode -t bios
      # dmidecode 3.4
      Getting SMBIOS data from sysfs.
      SMBIOS 3.0 present.
      
      Handle 0x0000, DMI type 0, 24 bytes
      BIOS Information
              Vendor: American Megatrends Inc.
              Version: 1.K0
              Release Date: 07/10/2018
              Address: 0xF0000
              Runtime Size: 64 kB
              ROM Size: 16 MB
              Characteristics:
                      PCI is supported
                      BIOS is upgradeable
                      BIOS shadowing is allowed
                      Boot from CD is supported
                      Selectable boot is supported
                      BIOS ROM is socketed
                      EDD is supported
                      5.25"/1.2 MB floppy services are supported (int       13h)
                      3.5"/720 kB floppy services are supported (int       13h)
                      3.5"/2.88 MB floppy services are supported (int       13h)
                      Print screen service is supported (int 5h)
                      8042 keyboard services are supported (int 9h)
                      Serial services are supported (int 14h)
                      Printer services are supported (int 17h)
                      ACPI is supported
                      USB legacy is supported
                      BIOS boot specification is supported
                      Targeted content distribution is supported
                      UEFI is supported
              BIOS Revision: 5.12
4

Nouveau yes, can’t help with that I’m afraid.

EXT4-fs no, that’s not an error: It’s the option defining the behaviour when an error does occur:

*errors={continue|remount-ro|panic}
*
*
Define the behavior when an error is encountered. (Either ignore errors and just mark the file system erroneous and continue, or remount the file system read-only, or panic and halt the system.) The default is set in the file system superblock, and can be changed using tune2fs

5

Hi
You need to install the firmware… https://build.opensuse.org/package/show/hardware/nvidia-firmware-installer will do the job


zypper in https://download.opensuse.org/repositories/hardware/15.4/noarch/nvidia-firmware-installer-1.1-lp154.1.1.noarch.rpm
6

Thank you, that worked fine. I have not been aware of this hardware repo, but wonder:
Shouldn’t the nvidia-firmware-installer and other needed have been installed during the 15.4 installation after probing the hardware?

7

Thank you for the clarification. I think I let it be as is, because I can’t remember to have changed this myself.

8

Hi
I don’t think it’s ever been submitted to the openSUSE release.

9

As the firmware is extracted from the NVIDIA binary driver openSUSE would possibly run into licensing issues perhaps. Much in the same way as the proprietary (Nvidia) drivers are not directly part of the distribution. But that is just speculation on my part…

10

Well, it is bit confusing. There has always been openSUSE non-oss repository. Nvidiea proprietary graphical drivers is among the community add-on repositories listed by YaST, and selected when users want that. In comparision hplip for my HP ColorJet MFP printer are official, while hp-plugin to use the scanner part is being downloaded and installed during the setup phase. But for the free nouveau driver, there is no message that advice the user to add install the firmware from the hardware repo. And there is unofficial guides to install multimedia codecs using the semi-official Packman repo, or using the OBS Package Installer opi for this and more …

11

Personally I was not aware of “nvidia-firmware-installer” until @malcolmlewis mentioned it.

I also use nvidia cards, and on machines using nouveau, don’t have the proprietary firmware installed. Checking through the journal I also found the same “error” message for direct firmware load failure.

Further investigation led me, eventually, to: https://nouveau.freedesktop.org/VideoAcceleration.html

At installation a message of some sort would probably be beneficial to alert users…