Persistent ACPI/_DSM, GPU Power, and Freezing Issues

KeYunLong

KeYunLong

Member
Joined
Jul 22, 2022
Messages
30
Reaction score
12
Credits
692
Hi everyone,

I’ve been experiencing intermittent freezes and a host of ACPI-related errors on my Fedora installation—even though my BIOS is fully updated (version 3601, released 10/12/2024 by American Megatrends). What’s really puzzling is that the exact same hardware runs flawlessly under Windows.
Below I’ve provided the details of my system along with the commands I used to verify them and a summary of the issues I’m encountering.
Fedora Version: 41
Kernel Version: 6.12.11-200.fc41.x86_64
CPU Details:
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
CPU(s): 12
Vendor ID: GenuineIntel
Model name: 12th Gen Intel(R) Core(TM) i5-12400F
Core(s) per socket: 6
Thread(s) per core: 2
GPU Details:
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GA104 [GeForce RTX 3060 Ti Lite Hash Rate] [10de:2489] (rev a1)
Subsystem: ASUSTeK Computer Inc. Device [1043:883c]
Kernel driver in use: nvidia
Kernel modules: nouveau, nvidia_drm, nvidia

Issues and Observations:
ACPI _DSM Failures:
My logs show repeated failures when evaluating certain ACPI Device-Specific Methods (_DSM). An example from the log:

ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:2 (0x1001)
ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:1 (0x1001)
...
ACPI: \: failed to evaluate _DSM bf0212f2-788f-c64d-a5b3-1f738e285ade rev:0 func:12 (0x1001)

These errors are tied to the PEG1 slot (likely affecting my NVIDIA GPU) and suggest that the firmware struggles with creating or parsing device-specific objects.
GPU Power Management Issues:
I also see the following message in my logs:
/usr/bin/nvidia-powerd[1026]: Found unsupported configuration. Exiting...
This implies that the NVIDIA power management daemon isn’t happy with the current configuration—possibly a fallout from the aforementioned ACPI issues.
Additional Driver & Peripheral Messages:
intel-lpss 0000:00:15.0: probe with driver intel-lpss failed with error -22
i801_smbus 0000:00:1f.4: SMBus base address uninitialized, upgrade BIOS
(Even though my BIOS is already updated.)
Other minor errors include an EVIOCSKEYCODE failure from udev, occasional Bluetooth mode setting errors, and some issues from gdm-password regarding user directory updates.
Kernel Parameter Tweaks:
I’m currently booting with these GRUB parameters:
rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.max_cstate=1 idle=nomwait
I’ve also experimented with variations like using acpi=strict or acpi_osi=Linux, acpi=off and nomodeset but none of these adjustments have fully prevented the spontaneous freezes—both when idle and during active use.
Summary & Questions:

In summary, despite having a fully updated BIOS and the fact that my hardware runs perfectly under Windows, my Fedora system continues to suffer from:
  • Persistent ACPI _DSM evaluation failures (likely affecting the PEG1 slot/GPU)
  • GPU power management issues with nvidia-powerd reporting unsupported configurations
  • Additional warnings and errors related to Intel-LPSS and SMBus initialization
  • Intermittent system freezes during both idle periods and active use
Has anyone encountered similar issues on a Fedora system with these specifications? Are there further kernel parameter tweaks, driver adjustments, or other solutions that might help resolve these ACPI and GPU power management conflicts on Linux?Thanks in advance for any help or insights!
 

Attachments



Question, do you have this problem on X11 or Wayland? which do you use? does it not work on both?

Please provide output of all of the 4 commands:

Bash: 
sudo dmesg | grep nvidia
# AND
inxi -Gx
# AND
sudo cat /sys/module/nvidia_drm/parameters/modeset
# AND
cat /etc/modprobe.d/*
 
Last edited:
Hi CaffeineAddict,I’m running my session on wayland, and here are the outputs you requested:
echo $XDG_SESSION_TYPE
wayland

I haven't tested X11. I'll do this and give you a feedback.

sudo dmesg | grep nvidia
[ 5.133627] nvidia: loading out-of-tree module taints kernel.
[ 5.133634] nvidia: module license 'NVIDIA' taints kernel.
[ 5.133636] nvidia: module verification failed: signature and/or required key missing - tainting kernel
[ 5.133637] nvidia: module license taints kernel.
[ 5.283474] nvidia-nvlink: Nvlink Core is being initialized, major device number 511
[ 5.284887] nvidia 0000:01:00.0: PCI->APIC IRQ transform: INT A -> IRQ 16
[ 5.284902] nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
[ 5.391482] nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
[ 5.466376] nvidia-uvm: Loaded the UVM driver, major device number 509.
[ 5.496061] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 565.77 Wed Nov 27 22:53:48 UTC 2024
[ 5.499762] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 7.053249] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
[ 7.077682] nvidia 0000:01:00.0: vgaarb: deactivate vga console
[ 7.154598] fbcon: nvidia-drmdrmfb (fb0) is primary device
[ 7.154603] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device

inxi -Gx
Graphics:
Device-1: NVIDIA GA104 [GeForce RTX 3060 Ti Lite Hash Rate] vendor: ASUSTeK
driver: nvidia v: 565.77 arch: Ampere bus-ID: 01:00.0
Device-2: KYE Systems (Mouse Systems) Genius WideCam F100
driver: snd-usb-audio,uvcvideo type: USB bus-ID: 1-2.1.3:10
Display: wayland server: X.Org v: 24.1.4 with: Xwayland v: 24.1.4
compositor: gnome-shell v: 47.3 driver: gpu: nvidia,nvidia-nvswitch
resolution: 1: 2560x1440~165Hz 2: 1920x1080~60Hz
API: OpenGL v: 4.6.0 vendor: nvidia v: 565.77 glx-v: 1.4
direct-render: yes renderer: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Info: Tools: api: glxinfo gpu: nvidia-settings x11: xdriinfo, xdpyinfo,
xprop, xrandr

sudo cat /sys/module/nvidia_drm/parameters/modeset
Y

sudo cat /etc/modprobe.d/*
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist appletalk
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist ax25
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist batman-adv
install nf_conntrack /sbin/modprobe --ignore-install nf_conntrack $CMDLINE_OPTS && /sbin/sysctl --quiet --pattern 'net[.]netfilter[.]nf_conntrack.*' --system
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist floppy
# Setting modprobe kvm_intel/kvm_amd nested = 1
# only enables Nested Virtualization until the next reboot or
# module reload. Uncomment the option applicable
# to your system below to enable the feature permanently.
#
# User changes in this file are preserved across upgrades.
#
# For Intel
#options kvm_intel nested=1
#
# For AMD
#options kvm_amd nested=1
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist l2tp_eth
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist l2tp_netlink
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist l2tp_ppp
#
# Set the NFS lock manager grace period. n is measured in seconds.
#options lockd nlm_grace_period=90
#
# Set the TCP port that the NFS lock manager should use.
# port must be a valid TCP port value (1-65535).
#options lockd nlm_tcpport
#
# Set the UDP port that the NFS lock manager should use.
# port must be a valid UDP port value (1-65535).
#options lockd nlm_udpport
#
# Set the maximum number of outstanding connections
#options lockd nlm_max_connections=1024
#
# Set the default time value for the NFS lock manager
# in seconds. Default is 10 secs (min 3 max 20)
#options lockd nlm_timeout=10
#
# Choose whether to record the caller_name or IP address
# this peer in the local rpc.statd's database.
#options lockd nsm_use_hostnames=0

# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist netrom
install libnvdimm /usr/bin/ndctl load-keys ; /sbin/modprobe --ignore-install libnvdimm $CMDLINE_OPTS
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist rds
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist rose
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_choke
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_drr
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_etf
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_gred
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_mqprio
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_multiq
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_netem
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_qfq
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_red
# This kernel module can be automatically loaded by non-root users. To
# enhance system security, the module is blacklisted by default to ensure
# system administrators make the module available for use as needed.
# See https://access.redhat.com/articles/3760101 for more details.
#
# Remove the blacklist by adding a comment # at the start of the line.
blacklist sch_sfb
# Increase default vhost memory map limit to match
# KVM's memory slot limit
options vhost max_mem_regions=509
 
@KeYunLong
Everything looks as it should be for wayland.

Try switch to X11 session and let us know if the problem persists there.
If it doesn't then maybe disabling modset in wayland could do the trick.
 
CaffeineAddict said:
@KeYunLong
Everything looks as it should be for wayland.

Try switch to X11 session and let us know if the problem persists there.
If it doesn't then maybe disabling modset in wayland could do the trick.
Click to expand...
Hi everyone,

I wanted to provide an update on my recent attempts to switch from Wayland to X11..

What I Did:
Disabling Wayland in GDM.

I edited /etc/gdm/custom.conf and uncommented the line: WaylandEnable=false

Generating an Xorg Configuration:
I ran: sudo nvidia-xconfig
which produced a full /etc/X11/xorg.conf with several sections (including InputDevice, Module, Device, and Screen).

Unfortunately, booting with this configuration resulted in a black screen instead of my user menu.

Simplifying Xorg Configuration:
I backed up the generated file and created a minimal /etc/X11/xorg.conf with just one section:

Section "Device"
Identifier "NVIDIA Card"
Driver "nvidia"EndSection

Same result, booting with this configuration resulted in a black screen instead of my user menu.

In other instances, when forced into X11 (and seeing a black screen), I had to revert by commenting out the WaylandEnable=false line and restarting to regain access.

Has anyone encountered similar behavior when trying to force X11 on Fedora with NVIDIA hardware (I'm using an NVIDIA GeForce RTX 3060 Ti?

Are there additional tweaks—perhaps involving GRUB kernel parameters (such as nvidia-drm.modeset) or further GDM configuration adjustments—that might allow a successful switch to an X11 session?

Could this behavior suggest an issue with the NVIDIA driver or a deeper compatibility problem between Fedora’s handling of Wayland/X11 transitions and the GPU?

I appreciate everyone’s input so far and look forward to any advice. Especially for my main problem which is the freezing Issues, I can totally live without X11.

Cheers!
 
Last edited:
dos2unix said:
Which version of fedora? Which desktop environment.

Some desktop environments in Fedora 41, are Wayland ONLY!!

news.itsfoss.com

Fedora 41 Workstation With GNOME To Be Wayland Only!

Fedora's flagship ISO will only feature Wayland, ditching X11.
news.itsfoss.com news.itsfoss.com
No X11 drivers exist for them at all.
Click to expand...
Hi dos2unix,Thanks for your reply. To clarify:

I’m running Fedora 41 with GNOME. I’m aware that recent Fedora editions push Wayland by default, and that some environments on Fedora 41 are structured for Wayland-only operation. However, I’ve been trying to force an X11 session in hopes that it may help resolve some of the persistent issues I've been encountering (ACPI/_DSM messages, GPU power anomalies, and occasional freezing).

I was hoping that forcing X11 might resolve some of these issues or at least help isolate the cause.

Any suggestions for further debugging or configuration changes would be highly appreciated. As I said X11 was just a way of troubleshoooting Thanks again for your input!

I have now added a line nvidia-drm.modeset=1 to "GRUB_CMDLINE_LINUX=" to see if it changes anything - I can say for sure that I booted my system without any problem. I will have to wait and see if my system freezes or not.
 
Last edited:
It failed again after changing to rhgb quiet nvidia-drm.modeset=1. The latest logs:

journalctl -b | grep -i nvidia
lut 08 10:54:00 rabbit-hole kernel: Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.11-200.fc41.x86_64 root=UUID=13b396eb-b359-43c7-a5f8-16e983b36fc9 ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.max_cstate=1 idle=nomwait nvidia-drm.modeset=1
lut 08 10:54:00 rabbit-hole kernel: Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.11-200.fc41.x86_64 root=UUID=13b396eb-b359-43c7-a5f8-16e983b36fc9 ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.max_cstate=1 idle=nomwait nvidia-drm.modeset=1
lut 08 10:54:03 rabbit-hole dracut-cmdline[389]: Using kernel command line parameters: rd.driver.pre=btrfs BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.11-200.fc41.x86_64 root=UUID=13b396eb-b359-43c7-a5f8-16e983b36fc9 ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.max_cstate=1 idle=nomwait nvidia-drm.modeset=1
lut 08 10:54:12 rabbit-hole kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14
lut 08 10:54:12 rabbit-hole kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15
lut 08 10:54:12 rabbit-hole kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16
lut 08 10:54:12 rabbit-hole kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17
lut 08 10:54:12 rabbit-hole kernel: nvidia: loading out-of-tree module taints kernel.
lut 08 10:54:12 rabbit-hole kernel: nvidia: module license 'NVIDIA' taints kernel.
lut 08 10:54:12 rabbit-hole kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernel
lut 08 10:54:12 rabbit-hole kernel: nvidia: module license taints kernel.
lut 08 10:54:12 rabbit-hole kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511
lut 08 10:54:12 rabbit-hole kernel: nvidia 0000:01:00.0: PCI->APIC IRQ transform: INT A -> IRQ 16
lut 08 10:54:12 rabbit-hole kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+mem
lut 08 10:54:12 rabbit-hole kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 565.77 Wed Nov 27 23:33:08 UTC 2024
lut 08 10:54:12 rabbit-hole kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.
lut 08 10:54:12 rabbit-hole kernel: nvidia-uvm: Loaded the UVM driver, major device number 509.
lut 08 10:54:12 rabbit-hole kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 565.77 Wed Nov 27 22:53:48 UTC 2024
lut 08 10:54:12 rabbit-hole kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
lut 08 10:54:12 rabbit-hole kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
lut 08 10:54:12 rabbit-hole kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga console
lut 08 10:54:12 rabbit-hole kernel: fbcon: nvidia-drmdrmfb (fb0) is primary device
lut 08 10:54:12 rabbit-hole kernel: nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device
lut 08 10:54:05 rabbit-hole audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 08 10:54:07 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
lut 08 10:54:05 rabbit-hole /usr/bin/nvidia-powerd[1020]: nvidia-powerd version:1.0(build 1)
lut 08 10:54:07 rabbit-hole /usr/bin/nvidia-powerd[1020]: Found unsupported configuration. Exiting...
lut 08 10:54:05 rabbit-hole systemd[1]: Started nvidia-powerd.service - nvidia-powerd service.
lut 08 10:54:07 rabbit-hole systemd[1]: nvidia-powerd.service: Deactivated successfully.
lut 08 10:54:07 rabbit-hole systemd[1]: nvidia-fallback.service - Fallback to nouveau as nvidia did not load was skipped because of an unmet condition check (ConditionPathExists=!/sys/module/nvidia).
lut 08 10:54:07 rabbit-hole systemd[1]: nvidia-fallback.service - Fallback to nouveau as nvidia did not load was skipped because of an unmet condition check (ConditionPathExists=!/sys/module/nvidia).
lut 08 10:54:15 rabbit-hole gnome-shell[1463]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
lut 08 10:54:22 rabbit-hole gnome-shell[2253]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.
lut 08 10:54:22 rabbit-hole systemd[2089]: Started app-gnome-nvidia\x2dsettings\x2duser-2484.scope - Application launched by gnome-session-binary.

journalctl -b -e
lut 08 10:54:34 rabbit-hole systemd[1423]: Stopped dbus-broker.service - D-Bus User Message Bus.
lut 08 10:54:34 rabbit-hole systemd[1423]: Removed slice session.slice - User Core Session Slice.
lut 08 10:54:34 rabbit-hole systemd[1423]: Closed dbus.socket - D-Bus User Message Bus Socket.
lut 08 10:54:34 rabbit-hole systemd[1423]: Removed slice app.slice - User Application Slice.
lut 08 10:54:34 rabbit-hole systemd[1423]: Reached target shutdown.target - Shutdown.
lut 08 10:54:34 rabbit-hole systemd[1423]: Finished systemd-exit.service - Exit the Session.
lut 08 10:54:34 rabbit-hole systemd[1423]: Reached target exit.target - Exit the Session.
lut 08 10:54:34 rabbit-hole systemd[1]: [email protected]: Deactivated successfully.
lut 08 10:54:34 rabbit-hole systemd[1]: Stopped [email protected] - User Manager for UID 42.
lut 08 10:54:34 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:54:34 rabbit-hole systemd[1]: Stopping [email protected] - User Runtime Directory /run/user/42...
lut 08 10:54:34 rabbit-hole systemd[1]: run-user-42.mount: Deactivated successfully.
lut 08 10:54:34 rabbit-hole systemd[1]: [email protected]: Deactivated successfully.
lut 08 10:54:34 rabbit-hole systemd[1]: Stopped [email protected] - User Runtime Directory /run/user/42.
lut 08 10:54:34 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:54:34 rabbit-hole systemd[1]: Removed slice user-42.slice - User Slice of UID 42.
lut 08 10:54:34 rabbit-hole systemd[1]: user-42.slice: Consumed 4.633s CPU time, 630.2M memory peak.
lut 08 10:54:34 rabbit-hole systemd-logind[1036]: Removed session 1.
lut 08 10:54:46 rabbit-hole systemd[1]: fprintd.service: Deactivated successfully.
lut 08 10:54:46 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:54:46 rabbit-hole audit: BPF prog-id=76 op=UNLOAD
lut 08 10:54:53 rabbit-hole systemd[1]: systemd-hostnamed.service: Deactivated successfully.
lut 08 10:54:53 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:54:53 rabbit-hole audit: BPF prog-id=69 op=UNLOAD
lut 08 10:54:59 rabbit-hole systemd[1]: systemd-localed.service: Deactivated successfully.
lut 08 10:54:59 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:54:59 rabbit-hole audit: BPF prog-id=75 op=UNLOAD
lut 08 10:54:59 rabbit-hole audit: BPF prog-id=74 op=UNLOAD
lut 08 10:54:59 rabbit-hole audit: BPF prog-id=73 op=UNLOAD
lut 08 10:55:08 rabbit-hole systemd[2089]: Started app-gnome-org.mozilla.firefox-3242.scope - Application launched by gnome-shell.
lut 08 10:55:08 rabbit-hole audit: BPF prog-id=78 op=LOAD
lut 08 10:55:08 rabbit-hole audit: BPF prog-id=79 op=LOAD
lut 08 10:55:08 rabbit-hole audit: BPF prog-id=80 op=LOAD
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-0-rescue.conf:6: Unknown li>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-0-rescue.conf:7: Unknown li>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-0-rescue.conf:8: Unknown li>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.10-200.fc41.x86_64.con>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.10-200.fc41.x86_64.con>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.10-200.fc41.x86_64.con>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.9-200.fc41.x86_64.conf>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.9-200.fc41.x86_64.conf>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.9-200.fc41.x86_64.conf>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.11-200.fc41.x86_64.con>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.11-200.fc41.x86_64.con>
lut 08 10:55:08 rabbit-hole systemd-logind[1036]: /boot/loader/entries/73968366d3a74c55b95c564e360c79e8-6.12.11-200.fc41.x86_64.con>
lut 08 10:55:08 rabbit-hole systemd[1]: Starting systemd-timedated.service - Time & Date Service...
lut 08 10:55:08 rabbit-hole systemd[1]: Started systemd-timedated.service - Time & Date Service.
lut 08 10:55:08 rabbit-hole audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg>
lut 08 10:55:08 rabbit-hole rtkit-daemon[1024]: Successfully made thread 3393 of process 3242 (/usr/lib64/firefox/firefox) owned by>
lut 08 10:55:17 rabbit-hole realmd[1860]: quitting realmd service after timeout
lut 08 10:55:17 rabbit-hole realmd[1860]: stopping service
lut 08 10:55:17 rabbit-hole systemd[1]: realmd.service: Deactivated successfully.
lut 08 10:55:17 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:55:31 rabbit-hole rtkit-daemon[1024]: Successfully made thread 3750 of process 3552 (/usr/lib64/firefox/firefox) owned by>
lut 08 10:55:38 rabbit-hole systemd[1]: systemd-timedated.service: Deactivated successfully.
lut 08 10:55:38 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:55:38 rabbit-hole audit: BPF prog-id=80 op=UNLOAD
lut 08 10:55:38 rabbit-hole audit: BPF prog-id=79 op=UNLOAD
lut 08 10:55:38 rabbit-hole audit: BPF prog-id=78 op=UNLOAD
lut 08 10:56:14 rabbit-hole systemd[1]: virtqemud.service: Deactivated successfully.
lut 08 10:56:14 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg=>
lut 08 10:56:26 rabbit-hole systemd[2089]: Starting grub-boot-success.service - Mark boot as successful...
lut 08 10:56:26 rabbit-hole systemd[2089]: Finished grub-boot-success.service - Mark boot as successful.
lut 08 10:56:35 rabbit-hole geoclue[1822]: Failed to query location: Query location SOUP error: Not Found
lut 08 10:57:06 rabbit-hole geoclue[1822]: Failed to query location: Query location SOUP error: Not Found
lut 08 10:57:52 rabbit-hole systemd[2089]: Started app-gnome-ptyxis-3985.scope - Application launched by gsd-media-keys.
lut 08 10:57:53 rabbit-hole kernel: evm: overlay not supported
lut 08 10:57:53 rabbit-hole podman[4015]: 2025-02-08 10:57:53.128156681 +0100 CET m=+0.045272262 system refresh
lut 08 10:57:53 rabbit-hole systemd[2089]: Created slice user.slice - Slice /user.
lut 08 10:57:53 rabbit-hole systemd[2089]: Started podman-pause-846dffbc.scope.
lut 08 10:57:53 rabbit-hole systemd[2089]: Started run-r4019bbec62944ea694389295256b2bb9.scope - /usr/bin/bash.
lut 08 10:57:53 rabbit-hole gnome-shell[2253]: Invalid sequence for VSYNC frame info
lut 08 10:58:40 rabbit-hole geoclue[1822]: Failed to query location: Query location SOUP error: Not Found


sudo dmesg | grep -i drm
[ 0.000000] Command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.11-200.fc41.x86_64 root=UUID=13b396eb-b359-43c7-a5f8-16e983b36fc9 ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.max_cstate=1 idle=nomwait nvidia-drm.modeset=1
[ 0.031943] Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.12.11-200.fc41.x86_64 root=UUID=13b396eb-b359-43c7-a5f8-16e983b36fc9 ro rootflags=subvol=root rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.max_cstate=1 idle=nomwait nvidia-drm.modeset=1
[ 0.368473] ACPI: bus type drm_connector registered
[ 0.393874] simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic
[ 0.393875] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0
[ 0.394401] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
[ 3.873444] systemd[1]: Starting [email protected] - Load Kernel Module drm...
[ 3.897189] systemd[1]: [email protected]: Deactivated successfully.
[ 3.897437] systemd[1]: Finished [email protected] - Load Kernel Module drm.
[ 5.464236] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
[ 7.111466] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1
[ 7.173778] fbcon: nvidia-drmdrmfb (fb0) is primary device
[ 7.173782] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device

I'm going now to test: nvidia-drm.modeset=0

Edited:

The value 0 made my system ugly, and the resolution doesn't work properly on my screen. There is no way for me to agree for such set up. I'll remove modeset value.

Latest update: I changed thg power settings from "balanced" to "high performance". Saving options are disabled.

1739009769678.png
 
Last edited:
t took almost week since the last freezing I was thinking that the GUI power settings fixed the issue, but unfortunately not. It got freezing.

:~$ journalctl -b | grep -i nvidialut
kernel: input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input14lut 13 14:01:06 rabbit-hole kernel: input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input15lut 13 14:01:06 rabbit-hole kernel: input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input16lut 13 14:01:06 rabbit-hole kernel: input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input17lut 13 14:01:06 rabbit-hole kernel: nvidia: loading out-of-tree module taints kernel.lut 13 14:01:06 rabbit-hole kernel: nvidia: module license 'NVIDIA' taints kernel.lut 13 14:01:06 rabbit-hole kernel: nvidia: module verification failed: signature and/or required key missing - tainting kernellut 13 14:01:06 rabbit-hole kernel: nvidia: module license taints kernel.lut 13 14:01:06 rabbit-hole kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 511lut 13 14:01:06 rabbit-hole kernel: nvidia 0000:01:00.0: PCI->APIC IRQ transform: INT A -> IRQ 16lut 13 14:01:06 rabbit-hole kernel: nvidia 0000:01:00.0: vgaarb: VGA decodes changed: olddecodes=io+mem,decodes=none:owns=io+memlut 13 14:01:06 rabbit-hole kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 565.77 Wed Nov 27 23:33:08 UTC 2024lut 13 14:01:06 rabbit-hole kernel: nvidia_uvm: module uses symbols nvUvmInterfaceDisableAccessCntr from proprietary module nvidia, inheriting taint.lut 13 14:01:06 rabbit-hole kernel: nvidia-uvm: Loaded the UVM driver, major device number 509.lut 13 14:01:06 rabbit-hole kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 565.77 Wed Nov 27 22:53:48 UTC 2024lut 13 14:01:06 rabbit-hole kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driverlut 13 14:01:06 rabbit-hole kernel: [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1lut 13 14:01:06 rabbit-hole kernel: nvidia 0000:01:00.0: vgaarb: deactivate vga consolelut 13 14:01:06 rabbit-hole kernel: fbcon: nvidia-drmdrmfb (fb0) is primary devicelut 13 14:01:06 rabbit-hole kernel: nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer devicelut 13 14:01:06 rabbit-hole systemd[1]: Started nvidia-powerd.service - nvidia-powerd service.lut 13 14:01:06 rabbit-hole audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'lut 13 14:01:06 rabbit-hole /usr/bin/nvidia-powerd[1072]: nvidia-powerd version:1.0(build 1)lut 13 14:01:06 rabbit-hole /usr/bin/nvidia-powerd[1072]: Found unsupported configuration. Exiting...lut 13 14:01:06 rabbit-hole systemd[1]: nvidia-powerd.service: Deactivated successfully.lut 13 14:01:06 rabbit-hole audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=nvidia-powerd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'lut 13 14:01:08 rabbit-hole systemd[1]: nvidia-fallback.service - Fallback to nouveau as nvidia did not load was skipped because of an unmet condition check (ConditionPathExists=!/sys/module/nvidia).lut 13 14:01:15 rabbit-hole gnome-shell[1471]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.lut 13 14:01:36 rabbit-hole gnome-shell[2266]: Added device '/dev/dri/card1' (nvidia-drm) using atomic mode setting.lut 13 14:01:37 rabbit-hole systemd[2119]: Started app-gnome-nvidia\x2dsettings\x2duser-2526.scope - Application launched by gnome-session-binary.

:~$ sudo dmesg | grep -i drm
[ 0.369467] ACPI: bus type drm_connector registered[ 0.394186] simple-framebuffer simple-framebuffer.0: [drm] Registered 1 planes with drm panic[ 0.394188] [drm] Initialized simpledrm 1.0.0 for simple-framebuffer.0 on minor 0[ 0.395216] simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device[ 3.848187] systemd[1]: Starting [email protected] - Load Kernel Module drm...[ 3.862696] systemd[1]: [email protected]: Deactivated successfully.[ 3.862843] systemd[1]: Finished [email protected] - Load Kernel Module drm.[ 5.371967] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver[ 6.864137] [drm] Initialized nvidia-drm 0.0.0 for 0000:01:00.0 on minor 1[ 6.927389] fbcon: nvidia-drmdrmfb (fb0) is primary device[ 6.927392] nvidia 0000:01:00.0: [drm] fb0: nvidia-drmdrmfb frame buffer device

My GRUB was:

GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.m>
GRUB_DISABLE_RECOVERY="true"
GRUB_ENABLE_BLSCFG=true

so I decided to experiment a bit and changed it to:

GRUB_CMDLINE_LINUX="rhgb quiet rd.driver.blacklist=nouveau modprobe.blacklist=nouveau usbcore.autosuspend=-1 pci=noacpi processor.max_cstate=1 idle=nomwait nvidia-drm.modeset=1 nvidia.NVreg_RegistryDwords='PowerMizerEnable=0x1;PowerMizerDefaultAC=0x1'"

Unfortunately after restart:

I've got a GUI notification "Program GNOME Software nieoczekiwanie zakończył działanie." (eng. "GNOME Software unexpectedly terminated the program.")

This crash report (from /var/spool/abrt/...) points to GNOME Software but might hint at broader issues with the current configuration. The logs show that while the NVIDIA modules (including DRM) load without fatal errors, there’s a message from nvidia-powerd stating an unsupported configuration before it exits.

Why I’m Not Switching to nvidia-drm.modeset=0​

I’ve tried using nvidia-drm.modeset=0 in the past, but that degrades the display quality and resolution significantly—something I cannot accept. I’d like to maintain the “proper” visual experience while resolving the freezes.

Questions:

  • Are there additional tweaks or registry options (or perhaps a driver update) that might help improve stability without downgrading visual quality?
  • Could the GNOME Software crash be related to the NVIDIA power management conflicts indicated by nvidia-powerd? Is there a workaround for that?
Any guidance or suggestions would be greatly appreciated!
I think I'll ask the same question on the Fedora forum. I can sacrifice a lot for using the Linux OS, but the OS freezing is something I won't accept - even with Windows I had 0 freezes on my current hardware.
 
You must log in or register to reply here.

Similar threads

J
My system is freezing
Replies
8
Views
2K
dos2unix
dos2unix
Tokishu
Power and USB issues across multiple Linux distributions (sleep, device disconnects)
Replies
3
Views
224
KGIII
K
J
Dual boot linux mint and arch
Replies
9
Views
657
KGIII
K
G
Linux not* booting after BIOS flash on a dual-boot machine with Windows 11 [I can't use Arch btw]
Replies
6
Views
2K
osprey
osprey
B
Brother Printer issues
2
Replies
27
Views
3K
Baddc053
B


Members online

Total: 1,125 (members: 3, guests: 1,122)

Latest posts

Top