You are not logged in.

#1 2025-02-22 10:56:01

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Trouble with NVIDIA driver

Hi guys, I really need help with a problem I'm having.

so I have installed Arch Linux from the guide https://wiki.archlinux.org/title/Installation_guide

after that I rebooted, and still no problem. then I installed zsh for terminal and configured it after that I rebooted, still no problem. Then after that I downloaded the nvidia driver for my GPU and nvidia-utils with the command "sudo pacman -S nvidia nvidia-utils", what was installed was version 570.xx. after that I tried to reboot again, and the problem was that the reboot took a long time and I tried to wait, after a while, I saw the message on the first line "systemd-shutdown[1]: Waiting for process: 453 ((udev-worker)), 427 (systemd-udev)". Then I forced the shutdown with the power button. I logged back into my account then I uninstalled nvidia and nvidia-utils, after that the reboot process runs normally.

Does anyone know how to fix something like that?

Offline

#2 2025-02-22 13:55:35

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,178

Re: Trouble with NVIDIA driver

What's your actual GPU? And into what do you want to boot? A TTY or a DM?

Offline

#3 2025-02-22 14:27:21

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Re: Trouble with NVIDIA driver

My GPU is GeForce RTX 2050 (mobile). First of all, what is DM?

Offline

#4 2025-02-22 16:25:03

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,443

Re: Trouble with NVIDIA driver

https://wiki.archlinux.org/index.php?title=DM

Please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' 0x0.st

Offline

#5 2025-02-23 09:54:10

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Re: Trouble with NVIDIA driver

Here it is

http://0x0.st/8TVC.txt

By the way Seth, I apologize, I accidentally pressed "report" and I thought I was replying to your message, I didn't mean to report you.?

Offline

#6 2025-02-23 13:55:46

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 25,178

Re: Trouble with NVIDIA driver

A bunch of issues here... First of all disable dhcpcd you don't want that running together with NetworkManager

There are some i915 crashes, likely due to some framebuffer conflict. Try adding, in that order

MODULES=(i915 nvidia nvidia_drm nvidia_modeset nvidia_uvm)

to your /etc/mkinitcpio.conf (and remove the kms hook from the HOOKS line) and adjust your kernel parameters get rid of the unnecessary ibt=off and instead add

nvidia_drm.modeset=1 nvidia_drm.fbdev=0

regenerate your initramfs with

mkinitcpio -P

reboot, do you still have issues with the subsequent reboot?

Don't worry about the report, you're not the first nor the last to accidentally do that, and we can mostly see from context what the intent was.

Last edited by V1del (2025-02-23 13:56:48)

Offline

#7 2025-02-24 09:30:34

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Re: Trouble with NVIDIA driver

I have followed your instructions, but after I reboot it, I can't booting to my system. So I enter USB live then reset the configuration.

I forgot to tell you that I have two GPUs: one is the discrete GPU that I mentioned earlier, and the other is the Intel integrated GPU. can that cause the problem I'm having?

Offline

#8 2025-02-24 09:39:11

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,443

Re: Trouble with NVIDIA driver

Yesno, but we know about the tow GPUs.

Adding the modules to the initramfs is likely not necessary, but (w/ the nvidia driver installed) add

nvidia_drm.modeset=1 nvidia_drm.fbdev=0 systemd.unit=multi-user.target

to the kernel parameters.
If that doesn't work, do NOT reboot by holding the power button. A short press or frenetically pressing ctrl+alt+del is gonna be fine.
Then post the journal for that boot.

If you can boot the multi-user.target, the problem is with your graphical.target (your DM…) resp. its configuration.
Do NOT use nvidia-settings or the likes to generate a static X11 config!

Offline

#9 2025-02-25 05:03:06

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Re: Trouble with NVIDIA driver

Thank you @seth and @V1del, now my system seems work after I set ```nvidia_drm.modeset=0```

I think there is an conflict with my integrated GPU and Discrete GPU.

Offline

#10 2025-02-25 09:06:48

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,443

Re: Trouble with NVIDIA driver

my system seems work after I set ```nvidia_drm.modeset=0```

Means you're likely running on the simpledrm device, that's fixing an itching toe by cutting your leg off.
Post an updated journal.

Your primary concern is

Feb 23 16:46:58 arxh kernel: ------------[ cut here ]------------
Feb 23 16:46:58 arxh kernel: i915 0000:00:02.0: [drm] Port B asks to use VBT vswing/preemph tables
Feb 23 16:46:58 arxh kernel: WARNING: CPU: 0 PID: 477 at drivers/gpu/drm/i915/display/intel_bios.c:2692 intel_bios_init+0x1352/0x17f0 [i915]
Feb 23 16:46:58 arxh kernel: Modules linked in: intel_powerclamp soundwire_bus coretemp snd_soc_sdca snd_soc_avs kvm_intel snd_soc_hda_codec snd_hda_ext_core snd_soc_core kvm snd_compress ac97_bus snd_pcm_dmaengine vfat snd_hda_codec_hdmi fat iwlmvm(+) crct10dif_pclmul crc32_pclmul polyval_clmulni joydev polyval_generic i915(+) mousedev snd_hda_intel ghash_clmulni_intel snd_intel_dspcfg sha512_ssse3 sha256_ssse3 mac80211 snd_intel_sdw_acpi sha1_ssse3 uvcvideo aesni_intel snd_hda_codec processor_thermal_device_pci videobuf2_vmalloc gf128mul processor_thermal_device uvc drm_buddy crypto_simd hid_multitouch iTCO_wdt btusb processor_thermal_wt_hint videobuf2_memops snd_hda_core libarc4 processor_thermal_rfim hid_generic videobuf2_v4l2 i2c_algo_bit btrtl intel_pmc_bxt cryptd snd_hwdep processor_thermal_rapl ptp nvidia_drm(POE+) pps_core intel_rapl_msr nvidia_uvm(POE) nvidia_modeset(POE) iwlwifi snd_pcm intel_rapl_common drm_display_helper btintel videobuf2_common r8169 iTCO_vendor_support rapl ee1004 btbcm mei_pxp mei_hdcp
Feb 23 16:46:58 arxh kernel:  processor_thermal_wt_req spi_nor videodev intel_lpss_pci snd_timer i2c_i801 btmtk realtek intel_cstate bluetooth mxm_wmi cfg80211 processor_thermal_power_floor intel_pmc_core mdio_devres mc cec drm_ttm_helper mei_me psmouse snd intel_lpss intel_uncore mtd pcspkr i2c_smbus libphy ttm intel_gtt processor_thermal_mbox int3403_thermal mei idma64 rfkill i2c_mux soundcore intel_vsec video i2c_hid_acpi int340x_thermal_zone int3400_thermal pmt_telemetry i2c_hid intel_hid wmi acpi_thermal_rel sparse_keymap pinctrl_tigerlake pmt_class acpi_pad mac_hid nvidia(POE) dm_mod loop nfnetlink ip_tables x_tables ext4 crc32c_generic crc16 mbcache jbd2 sdhci_pci sdhci_uhs2 serio_raw atkbd sdhci nvme libps2 vivaldi_fmap cqhci nvme_core crc32c_intel spi_intel_pci mmc_core i8042 spi_intel nvme_auth serio
Feb 23 16:46:58 arxh kernel: CPU: 0 UID: 0 PID: 477 Comm: (udev-worker) Tainted: P           OE      6.13.3-arch1-1 #1 0e057b3ba87c8453f3120f28a0cea5eaa8068906
Feb 23 16:46:58 arxh kernel: Tainted: [P]=PROPRIETARY_MODULE, [O]=OOT_MODULE, [E]=UNSIGNED_MODULE
Feb 23 16:46:58 arxh kernel: Hardware name: Axioo Pongo 725/Pongo 725, BIOS 1.07.01TAX 09/21/2023
Feb 23 16:46:58 arxh kernel: RIP: 0010:intel_bios_init+0x1352/0x17f0 [i915]
Feb 23 16:46:58 arxh kernel: Code: 48 8b 78 08 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 63 db a0 f0 44 89 f1 48 89 da 48 c7 c7 60 82 8d c7 48 89 c6 e8 ae f1 0f f0 <0f> 0b e9 bb fd ff ff 0f b7 83 60 04 00 00 83 e8 03 66 83 f8 04 76
Feb 23 16:46:58 arxh kernel: RSP: 0018:ffffa0fb80d3b7a0 EFLAGS: 00010282
Feb 23 16:46:58 arxh kernel: RAX: 0000000000000000 RBX: ffff953602ae31e0 RCX: 0000000000000027
Feb 23 16:46:58 arxh kernel: RDX: ffff95399f0218c8 RSI: 0000000000000001 RDI: ffff95399f0218c0
Feb 23 16:46:58 arxh kernel: RBP: ffff953622e64618 R08: 0000000000000000 R09: ffffa0fb80d3b620
Feb 23 16:46:58 arxh kernel: R10: ffffffffb98b5408 R11: 0000000000000003 R12: 0000000000000001
Feb 23 16:46:58 arxh kernel: R13: 0000000000000000 R14: 0000000000000042 R15: ffff95362445a2a0
Feb 23 16:46:58 arxh kernel: FS:  0000742aea0df880(0000) GS:ffff95399f000000(0000) knlGS:0000000000000000
Feb 23 16:46:58 arxh kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 23 16:46:58 arxh kernel: CR2: 0000782c2e85f000 CR3: 000000010e802006 CR4: 0000000000f72ef0
Feb 23 16:46:58 arxh kernel: PKRU: 55555554
Feb 23 16:46:58 arxh kernel: Call Trace:
Feb 23 16:46:58 arxh kernel:  <TASK>
Feb 23 16:46:58 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 e1382054a189ce529d4b4b7d8f5b5a2c50ce8d26]
Feb 23 16:46:58 arxh kernel:  ? __warn.cold+0x93/0xf6
Feb 23 16:46:58 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 e1382054a189ce529d4b4b7d8f5b5a2c50ce8d26]
Feb 23 16:46:58 arxh kernel:  ? report_bug+0xff/0x140
Feb 23 16:46:58 arxh kernel:  ? handle_bug+0x58/0x90
Feb 23 16:46:58 arxh kernel:  ? exc_invalid_op+0x17/0x70
Feb 23 16:46:58 arxh kernel:  ? asm_exc_invalid_op+0x1a/0x20
Feb 23 16:46:58 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 e1382054a189ce529d4b4b7d8f5b5a2c50ce8d26]
Feb 23 16:46:58 arxh kernel:  intel_display_driver_probe_noirq+0x42/0x240 [i915 e1382054a189ce529d4b4b7d8f5b5a2c50ce8d26]
Feb 23 16:46:58 arxh kernel:  i915_driver_probe+0x3ba/0xb20 [i915 e1382054a189ce529d4b4b7d8f5b5a2c50ce8d26]
Feb 23 16:46:58 arxh kernel:  ? drm_privacy_screen_get+0x198/0x1c0
Feb 23 16:46:58 arxh kernel:  local_pci_probe+0x42/0x90
Feb 23 16:46:58 arxh kernel:  pci_device_probe+0xdd/0x270
Feb 23 16:46:58 arxh kernel:  really_probe+0xdb/0x340
Feb 23 16:46:58 arxh kernel:  ? pm_runtime_barrier+0x54/0x90
Feb 23 16:46:58 arxh kernel:  ? __pfx___driver_attach+0x10/0x10
Feb 23 16:46:58 arxh kernel:  __driver_probe_device+0x78/0x110
Feb 23 16:46:58 arxh kernel:  driver_probe_device+0x1f/0xa0
Feb 23 16:46:58 arxh kernel:  __driver_attach+0xba/0x1c0
Feb 23 16:46:58 arxh kernel:  bus_for_each_dev+0x8c/0xe0
Feb 23 16:46:58 arxh kernel:  bus_add_driver+0x112/0x1f0
Feb 23 16:46:58 arxh kernel:  driver_register+0x72/0xd0
Feb 23 16:46:58 arxh kernel:  i915_init+0x23/0x90 [i915 e1382054a189ce529d4b4b7d8f5b5a2c50ce8d26]
Feb 23 16:46:58 arxh kernel:  ? __pfx_i915_init+0x10/0x10 [i915 e1382054a189ce529d4b4b7d8f5b5a2c50ce8d26]
Feb 23 16:46:58 arxh kernel:  do_one_initcall+0x58/0x310
Feb 23 16:46:58 arxh kernel:  do_init_module+0x60/0x230
Feb 23 16:46:58 arxh kernel:  init_module_from_file+0x89/0xe0
Feb 23 16:46:58 arxh kernel:  idempotent_init_module+0x115/0x310
Feb 23 16:46:58 arxh kernel:  __x64_sys_finit_module+0x65/0xc0
Feb 23 16:46:58 arxh kernel:  do_syscall_64+0x82/0x190
Feb 23 16:46:58 arxh kernel:  ? do_sys_openat2+0x9c/0xe0
Feb 23 16:46:58 arxh kernel:  ? switch_fpu_return+0x4e/0xd0
Feb 23 16:46:58 arxh kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90
Feb 23 16:46:58 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 23 16:46:58 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 23 16:46:58 arxh kernel:  ? vfs_fstatat+0x75/0xa0
Feb 23 16:46:58 arxh kernel:  ? __do_sys_newfstatat+0x3c/0x80
Feb 23 16:46:58 arxh kernel:  ? __seccomp_filter+0x303/0x520
Feb 23 16:46:58 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 23 16:46:58 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 23 16:46:58 arxh kernel:  ? switch_fpu_return+0x4e/0xd0
Feb 23 16:46:58 arxh kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90
Feb 23 16:46:58 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 23 16:46:58 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 23 16:46:58 arxh kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 23 16:46:58 arxh kernel: RIP: 0033:0x742ae9b2588d
Feb 23 16:46:58 arxh kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 04 0d 00 f7 d8 64 89 01 48
Feb 23 16:46:58 arxh kernel: RSP: 002b:00007ffefee856e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Feb 23 16:46:58 arxh kernel: RAX: ffffffffffffffda RBX: 0000596ead63d960 RCX: 0000742ae9b2588d
Feb 23 16:46:58 arxh kernel: RDX: 0000000000000004 RSI: 0000742aea0c705d RDI: 0000000000000042
Feb 23 16:46:58 arxh kernel: RBP: 00007ffefee857a0 R08: 0000000000000000 R09: 00007ffefee85750
Feb 23 16:46:58 arxh kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000742aea0c705d
Feb 23 16:46:58 arxh kernel: R13: 0000000000020000 R14: 0000596ead64c3a0 R15: 0000596ead631710
Feb 23 16:46:58 arxh kernel:  </TASK>
Feb 23 16:46:58 arxh kernel: ---[ end trace 0000000000000000 ]---

Add the parameters from #8 and add i915, but none of the nvidia modules to the initramfs.
Then post a journal for that boot.

Offline

#11 2025-02-26 04:31:56

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Re: Trouble with NVIDIA driver

Here it is the updated journal

http://0x0.st/8A6D.txt

Offline

#12 2025-02-26 09:30:09

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,443

Re: Trouble with NVIDIA driver

Lose those: "quiet splash" they will make it hard to track what's going on.
i915 still warns

Feb 26 11:23:24 arxh kernel: ------------[ cut here ]------------
Feb 26 11:23:24 arxh kernel: i915 0000:00:02.0: [drm] Port B asks to use VBT vswing/preemph tables
Feb 26 11:23:24 arxh kernel: WARNING: CPU: 7 PID: 207 at drivers/gpu/drm/i915/display/intel_bios.c:2692 intel_bios_init+0x1352/0x17f0 [i915]
Feb 26 11:23:24 arxh kernel: Modules linked in: i915(+) i2c_algo_bit drm_buddy video wmi ttm intel_gtt drm_display_helper cec
Feb 26 11:23:24 arxh kernel: CPU: 7 UID: 0 PID: 207 Comm: modprobe Not tainted 6.13.4-arch1-1 #1 07f0136ec6257c7900889d08fabc01499f07b8cb
Feb 26 11:23:24 arxh kernel: Hardware name: Axioo Pongo 725/Pongo 725, BIOS 1.07.01TAX 09/21/2023
Feb 26 11:23:24 arxh kernel: RIP: 0010:intel_bios_init+0x1352/0x17f0 [i915]
Feb 26 11:23:24 arxh kernel: Code: 48 8b 78 08 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 e3 c0 da cf 44 89 f1 48 89 da 48 c7 c7 60 a2 93 c0 48 89 c6 e8 0e d2 49 cf <0f> 0b e9 bb fd ff ff 0f b7 83 60 04 00 00 83 e8 03 66 83 f8 04 76
Feb 26 11:23:24 arxh kernel: RSP: 0018:ffffa772407ef690 EFLAGS: 00010282
Feb 26 11:23:24 arxh kernel: RAX: 0000000000000000 RBX: ffff8f2c82ae65e0 RCX: 0000000000000003
Feb 26 11:23:24 arxh kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000001
Feb 26 11:23:24 arxh kernel: RBP: ffff8f2c86d60618 R08: 0000000000000000 R09: ffffa772407ef510
Feb 26 11:23:24 arxh kernel: R10: ffffffff91cb5408 R11: 0000000000000003 R12: 0000000000000001
Feb 26 11:23:24 arxh kernel: R13: 0000000000000000 R14: 0000000000000042 R15: ffff8f2c87875840
Feb 26 11:23:24 arxh kernel: FS:  000076e80192b740(0000) GS:ffff8f301f380000(0000) knlGS:0000000000000000
Feb 26 11:23:24 arxh kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 26 11:23:24 arxh kernel: CR2: 0000613d61427020 CR3: 0000000106570002 CR4: 0000000000f70ef0
Feb 26 11:23:24 arxh kernel: PKRU: 55555554
Feb 26 11:23:24 arxh kernel: Call Trace:
Feb 26 11:23:24 arxh kernel:  <TASK>
Feb 26 11:23:24 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 11:23:24 arxh kernel:  ? __warn.cold+0x93/0xf6
Feb 26 11:23:24 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 11:23:24 arxh kernel:  ? report_bug+0xff/0x140
Feb 26 11:23:24 arxh kernel:  ? handle_bug+0x58/0x90
Feb 26 11:23:24 arxh kernel:  ? exc_invalid_op+0x17/0x70
Feb 26 11:23:24 arxh kernel:  ? asm_exc_invalid_op+0x1a/0x20
Feb 26 11:23:24 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 11:23:24 arxh kernel:  intel_display_driver_probe_noirq+0x42/0x240 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 11:23:24 arxh kernel:  i915_driver_probe+0x3ba/0xb20 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 11:23:24 arxh kernel:  ? drm_privacy_screen_get+0x198/0x1c0
Feb 26 11:23:24 arxh kernel:  local_pci_probe+0x42/0x90
Feb 26 11:23:24 arxh kernel:  pci_device_probe+0xdd/0x270
Feb 26 11:23:24 arxh kernel:  really_probe+0xdb/0x340
Feb 26 11:23:24 arxh kernel:  ? pm_runtime_barrier+0x54/0x90
Feb 26 11:23:24 arxh kernel:  ? __pfx___driver_attach+0x10/0x10
Feb 26 11:23:24 arxh kernel:  __driver_probe_device+0x78/0x110
Feb 26 11:23:24 arxh kernel:  driver_probe_device+0x1f/0xa0
Feb 26 11:23:24 arxh kernel:  __driver_attach+0xba/0x1c0
Feb 26 11:23:24 arxh kernel:  bus_for_each_dev+0x8c/0xe0
Feb 26 11:23:24 arxh kernel:  bus_add_driver+0x112/0x1f0
Feb 26 11:23:24 arxh kernel:  driver_register+0x72/0xd0
Feb 26 11:23:24 arxh kernel:  i915_init+0x23/0x90 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 11:23:24 arxh kernel:  ? __pfx_i915_init+0x10/0x10 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 11:23:24 arxh kernel:  do_one_initcall+0x58/0x310
Feb 26 11:23:24 arxh kernel:  do_init_module+0x60/0x230
Feb 26 11:23:24 arxh kernel:  init_module_from_file+0x89/0xe0
Feb 26 11:23:24 arxh kernel:  idempotent_init_module+0x115/0x310
Feb 26 11:23:24 arxh kernel:  __x64_sys_finit_module+0x65/0xc0
Feb 26 11:23:24 arxh kernel:  do_syscall_64+0x82/0x190
Feb 26 11:23:24 arxh kernel:  ? __x64_sys_pread64+0x9f/0xc0
Feb 26 11:23:24 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:23:24 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:23:24 arxh kernel:  ? do_sys_openat2+0x9c/0xe0
Feb 26 11:23:24 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:23:24 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:23:24 arxh kernel:  ? do_sys_openat2+0x9c/0xe0
Feb 26 11:23:24 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:23:24 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:23:24 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:23:24 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:23:24 arxh kernel:  ? do_user_addr_fault+0x36c/0x620
Feb 26 11:23:24 arxh kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 26 11:23:24 arxh kernel: RIP: 0033:0x76e801a4788d
Feb 26 11:23:24 arxh kernel: Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 53 04 0d 00 f7 d8 64 89 01 48
Feb 26 11:23:24 arxh kernel: RSP: 002b:00007fffe40cb018 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Feb 26 11:23:24 arxh kernel: RAX: ffffffffffffffda RBX: 0000613d61424cc0 RCX: 000076e801a4788d
Feb 26 11:23:24 arxh kernel: RDX: 0000000000000004 RSI: 0000613d526eca19 RDI: 000000000000000b
Feb 26 11:23:24 arxh kernel: RBP: 00007fffe40cb0b0 R08: 0000000000000000 R09: 0000613d61426d20
Feb 26 11:23:24 arxh kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 0000613d526eca19
Feb 26 11:23:24 arxh kernel: R13: 0000000000060000 R14: 0000613d61424de0 R15: 0000613d61425ac0
Feb 26 11:23:24 arxh kernel:  </TASK>
Feb 26 11:23:24 arxh kernel: ---[ end trace 0000000000000000 ]---

and nvidia hangs

Feb 26 11:27:29 arxh kernel: INFO: task kworker/10:1:165 blocked for more than 122 seconds.
Feb 26 11:27:29 arxh kernel:       Tainted: P        W  OE      6.13.4-arch1-1 #1
Feb 26 11:27:29 arxh kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 26 11:27:29 arxh kernel: task:kworker/10:1    state:D stack:0     pid:165   tgid:165   ppid:2      flags:0x00004000
Feb 26 11:27:29 arxh kernel: Workqueue: kacpi_notify acpi_os_execute_deferred
Feb 26 11:27:29 arxh kernel: Call Trace:
Feb 26 11:27:29 arxh kernel:  <TASK>
Feb 26 11:27:29 arxh kernel:  __schedule+0x425/0x12b0
Feb 26 11:27:29 arxh kernel:  ? acpi_ut_allocate_object_desc_dbg+0x8e/0x110
Feb 26 11:27:29 arxh kernel:  schedule+0x27/0xf0
Feb 26 11:27:29 arxh kernel:  schedule_preempt_disabled+0x15/0x30
Feb 26 11:27:29 arxh kernel:  rwsem_down_write_slowpath+0x1d3/0x660
Feb 26 11:27:29 arxh kernel:  ? __slab_free+0xdf/0x2f0
Feb 26 11:27:29 arxh kernel:  down_write+0x5a/0x60
Feb 26 11:27:29 arxh kernel:  os_acquire_rwlock_write+0x2b/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv049738rm+0x10/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv051176rm+0x284/0x360 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  rm_acpi_nvpcf_notify+0x35/0xf0 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  acpi_ev_notify_dispatch+0x4b/0x70
Feb 26 11:27:29 arxh kernel:  acpi_os_execute_deferred+0x17/0x30
Feb 26 11:27:29 arxh kernel:  process_one_work+0x17b/0x330
Feb 26 11:27:29 arxh kernel:  worker_thread+0x2ce/0x3f0
Feb 26 11:27:29 arxh kernel:  ? __pfx_worker_thread+0x10/0x10
Feb 26 11:27:29 arxh kernel:  kthread+0xcf/0x100
Feb 26 11:27:29 arxh kernel:  ? __pfx_kthread+0x10/0x10
Feb 26 11:27:29 arxh kernel:  ret_from_fork+0x31/0x50
Feb 26 11:27:29 arxh kernel:  ? __pfx_kthread+0x10/0x10
Feb 26 11:27:29 arxh kernel:  ret_from_fork_asm+0x1a/0x30
Feb 26 11:27:29 arxh kernel:  </TASK>
Feb 26 11:27:29 arxh kernel: INFO: task (udev-worker):475 blocked for more than 122 seconds.
Feb 26 11:27:29 arxh kernel:       Tainted: P        W  OE      6.13.4-arch1-1 #1
Feb 26 11:27:29 arxh kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 26 11:27:29 arxh kernel: task:(udev-worker)   state:D stack:0     pid:475   tgid:475   ppid:431    flags:0x00004006
Feb 26 11:27:29 arxh kernel: Call Trace:
Feb 26 11:27:29 arxh kernel:  <TASK>
Feb 26 11:27:29 arxh kernel:  __schedule+0x425/0x12b0
Feb 26 11:27:29 arxh kernel:  schedule+0x27/0xf0
Feb 26 11:27:29 arxh kernel:  schedule_preempt_disabled+0x15/0x30
Feb 26 11:27:29 arxh kernel:  rwsem_down_write_slowpath+0x1d3/0x660
Feb 26 11:27:29 arxh kernel:  down_write+0x5a/0x60
Feb 26 11:27:29 arxh kernel:  os_acquire_rwlock_write+0x2b/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv049738rm+0x10/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv051176rm+0x284/0x360 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv039061rm+0xc4e/0x1560 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv000768rm+0x132b/0x2100 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  rm_init_adapter+0xcd/0xf0 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  ? __x2apic_send_IPI_dest+0x32/0x40
Feb 26 11:27:29 arxh kernel:  nv_open_device+0x35a/0xa30 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  nvidia_dev_get+0x77/0xd0 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  nvkms_open_gpu+0x4b/0x90 [nvidia_modeset ce1e4029f53ced61c4c9e154c2a73cb8b4e3313e]
Feb 26 11:27:29 arxh kernel:  _nv000013kms+0x4d/0x700 [nvidia_modeset ce1e4029f53ced61c4c9e154c2a73cb8b4e3313e]
Feb 26 11:27:29 arxh kernel:  ? _printk+0x6c/0x90
Feb 26 11:27:29 arxh kernel:  nv_drm_load+0xb5/0x81c [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:27:29 arxh kernel:  ? __remove_hrtimer+0x39/0x90
Feb 26 11:27:29 arxh kernel:  ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:27:29 arxh kernel:  ? hrtimer_try_to_cancel.part.0+0x50/0xe0
Feb 26 11:27:29 arxh kernel:  ? sched_balance_newidle+0x2c8/0x460
Feb 26 11:27:29 arxh kernel:  ? sched_clock+0x10/0x30
Feb 26 11:27:29 arxh kernel:  ? sched_clock_cpu+0xf/0x1d0
Feb 26 11:27:29 arxh kernel:  ? psi_group_change+0x13b/0x310
Feb 26 11:27:29 arxh kernel:  drm_dev_register+0x122/0x250
Feb 26 11:27:29 arxh kernel:  nv_drm_register_drm_device+0xa2/0x180 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:27:29 arxh kernel:  nv_drm_probe_devices+0x99/0xd0 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:27:29 arxh kernel:  ? __pfx_nv_linux_drm_init+0x10/0x10 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:27:29 arxh kernel:  do_one_initcall+0x58/0x310
Feb 26 11:27:29 arxh kernel:  do_init_module+0x60/0x230
Feb 26 11:27:29 arxh kernel:  init_module_from_file+0x89/0xe0
Feb 26 11:27:29 arxh kernel:  idempotent_init_module+0x115/0x310
Feb 26 11:27:29 arxh kernel:  __x64_sys_finit_module+0x65/0xc0
Feb 26 11:27:29 arxh kernel:  do_syscall_64+0x82/0x190
Feb 26 11:27:29 arxh kernel:  ? switch_fpu_return+0x4e/0xd0
Feb 26 11:27:29 arxh kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90
Feb 26 11:27:29 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:27:29 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:27:29 arxh kernel:  ? do_sys_openat2+0x9c/0xe0
Feb 26 11:27:29 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:27:29 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:27:29 arxh kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 26 11:27:29 arxh kernel: RIP: 0033:0x7ba4b332588d
Feb 26 11:27:29 arxh kernel: RSP: 002b:00007fff48be03b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Feb 26 11:27:29 arxh kernel: RAX: ffffffffffffffda RBX: 000064cf964ac5d0 RCX: 00007ba4b332588d
Feb 26 11:27:29 arxh kernel: RDX: 0000000000000004 RSI: 000064cf964a2f90 RDI: 000000000000003a
Feb 26 11:27:29 arxh kernel: RBP: 00007fff48be0450 R08: 0000000000000000 R09: 000064cf964ae0a0
Feb 26 11:27:29 arxh kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000064cf964a2f90
Feb 26 11:27:29 arxh kernel: R13: 0000000000020000 R14: 000064cf964a81f0 R15: 000064cf964ac5d0
Feb 26 11:27:29 arxh kernel:  </TASK>
Feb 26 11:29:32 arxh kernel: INFO: task kworker/10:1:165 blocked for more than 245 seconds.
Feb 26 11:29:32 arxh kernel:       Tainted: P        W  OE      6.13.4-arch1-1 #1
Feb 26 11:29:32 arxh kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 26 11:29:32 arxh kernel: task:kworker/10:1    state:D stack:0     pid:165   tgid:165   ppid:2      flags:0x00004000
Feb 26 11:29:32 arxh kernel: Workqueue: kacpi_notify acpi_os_execute_deferred
Feb 26 11:29:32 arxh kernel: Call Trace:
Feb 26 11:29:32 arxh kernel:  <TASK>
Feb 26 11:29:32 arxh kernel:  __schedule+0x425/0x12b0
Feb 26 11:29:32 arxh kernel:  ? acpi_ut_allocate_object_desc_dbg+0x8e/0x110
Feb 26 11:29:32 arxh kernel:  schedule+0x27/0xf0
Feb 26 11:29:32 arxh kernel:  schedule_preempt_disabled+0x15/0x30
Feb 26 11:29:32 arxh kernel:  rwsem_down_write_slowpath+0x1d3/0x660
Feb 26 11:29:32 arxh kernel:  ? __slab_free+0xdf/0x2f0
Feb 26 11:29:32 arxh kernel:  down_write+0x5a/0x60
Feb 26 11:29:32 arxh kernel:  os_acquire_rwlock_write+0x2b/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  _nv049738rm+0x10/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  _nv051176rm+0x284/0x360 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  rm_acpi_nvpcf_notify+0x35/0xf0 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  acpi_ev_notify_dispatch+0x4b/0x70
Feb 26 11:29:32 arxh kernel:  acpi_os_execute_deferred+0x17/0x30
Feb 26 11:29:32 arxh kernel:  process_one_work+0x17b/0x330
Feb 26 11:29:32 arxh kernel:  worker_thread+0x2ce/0x3f0
Feb 26 11:29:32 arxh kernel:  ? __pfx_worker_thread+0x10/0x10
Feb 26 11:29:32 arxh kernel:  kthread+0xcf/0x100
Feb 26 11:29:32 arxh kernel:  ? __pfx_kthread+0x10/0x10
Feb 26 11:29:32 arxh kernel:  ret_from_fork+0x31/0x50
Feb 26 11:29:32 arxh kernel:  ? __pfx_kthread+0x10/0x10
Feb 26 11:29:32 arxh kernel:  ret_from_fork_asm+0x1a/0x30
Feb 26 11:29:32 arxh kernel:  </TASK>
Feb 26 11:29:32 arxh kernel: INFO: task (udev-worker):475 blocked for more than 245 seconds.
Feb 26 11:29:32 arxh kernel:       Tainted: P        W  OE      6.13.4-arch1-1 #1
Feb 26 11:29:32 arxh kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 26 11:29:32 arxh kernel: task:(udev-worker)   state:D stack:0     pid:475   tgid:475   ppid:431    flags:0x00004006
Feb 26 11:29:32 arxh kernel: Call Trace:
Feb 26 11:29:32 arxh kernel:  <TASK>
Feb 26 11:29:32 arxh kernel:  __schedule+0x425/0x12b0
Feb 26 11:29:32 arxh kernel:  schedule+0x27/0xf0
Feb 26 11:29:32 arxh kernel:  schedule_preempt_disabled+0x15/0x30
Feb 26 11:29:32 arxh kernel:  rwsem_down_write_slowpath+0x1d3/0x660
Feb 26 11:29:32 arxh kernel:  down_write+0x5a/0x60
Feb 26 11:29:32 arxh kernel:  os_acquire_rwlock_write+0x2b/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  _nv049738rm+0x10/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  _nv051176rm+0x284/0x360 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  _nv039061rm+0xc4e/0x1560 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  _nv000768rm+0x132b/0x2100 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  rm_init_adapter+0xcd/0xf0 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  ? __x2apic_send_IPI_dest+0x32/0x40
Feb 26 11:29:32 arxh kernel:  nv_open_device+0x35a/0xa30 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  nvidia_dev_get+0x77/0xd0 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:29:32 arxh kernel:  nvkms_open_gpu+0x4b/0x90 [nvidia_modeset ce1e4029f53ced61c4c9e154c2a73cb8b4e3313e]
Feb 26 11:29:32 arxh kernel:  _nv000013kms+0x4d/0x700 [nvidia_modeset ce1e4029f53ced61c4c9e154c2a73cb8b4e3313e]
Feb 26 11:29:32 arxh kernel:  ? _printk+0x6c/0x90
Feb 26 11:29:32 arxh kernel:  nv_drm_load+0xb5/0x81c [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:29:32 arxh kernel:  ? __remove_hrtimer+0x39/0x90
Feb 26 11:29:32 arxh kernel:  ? __pfx_nv_drm_event_callback+0x10/0x10 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:29:32 arxh kernel:  ? hrtimer_try_to_cancel.part.0+0x50/0xe0
Feb 26 11:29:32 arxh kernel:  ? sched_balance_newidle+0x2c8/0x460
Feb 26 11:29:32 arxh kernel:  ? sched_clock+0x10/0x30
Feb 26 11:29:32 arxh kernel:  ? sched_clock_cpu+0xf/0x1d0
Feb 26 11:29:32 arxh kernel:  ? psi_group_change+0x13b/0x310
Feb 26 11:29:32 arxh kernel:  drm_dev_register+0x122/0x250
Feb 26 11:29:32 arxh kernel:  nv_drm_register_drm_device+0xa2/0x180 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:29:32 arxh kernel:  nv_drm_probe_devices+0x99/0xd0 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:29:32 arxh kernel:  ? __pfx_nv_linux_drm_init+0x10/0x10 [nvidia_drm f8d8ed81ce072514a5c59ba9c55b93e284c89bc9]
Feb 26 11:29:32 arxh kernel:  do_one_initcall+0x58/0x310
Feb 26 11:29:32 arxh kernel:  do_init_module+0x60/0x230
Feb 26 11:29:32 arxh kernel:  init_module_from_file+0x89/0xe0
Feb 26 11:29:32 arxh kernel:  idempotent_init_module+0x115/0x310
Feb 26 11:29:32 arxh kernel:  __x64_sys_finit_module+0x65/0xc0
Feb 26 11:29:32 arxh kernel:  do_syscall_64+0x82/0x190
Feb 26 11:29:32 arxh kernel:  ? switch_fpu_return+0x4e/0xd0
Feb 26 11:29:32 arxh kernel:  ? arch_exit_to_user_mode_prepare.isra.0+0x79/0x90
Feb 26 11:29:32 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:29:32 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:29:32 arxh kernel:  ? do_sys_openat2+0x9c/0xe0
Feb 26 11:29:32 arxh kernel:  ? syscall_exit_to_user_mode+0x37/0x1c0
Feb 26 11:29:32 arxh kernel:  ? do_syscall_64+0x8e/0x190
Feb 26 11:29:32 arxh kernel:  entry_SYSCALL_64_after_hwframe+0x76/0x7e
Feb 26 11:29:32 arxh kernel: RIP: 0033:0x7ba4b332588d
Feb 26 11:29:32 arxh kernel: RSP: 002b:00007fff48be03b8 EFLAGS: 00000246 ORIG_RAX: 0000000000000139
Feb 26 11:29:32 arxh kernel: RAX: ffffffffffffffda RBX: 000064cf964ac5d0 RCX: 00007ba4b332588d
Feb 26 11:29:32 arxh kernel: RDX: 0000000000000004 RSI: 000064cf964a2f90 RDI: 000000000000003a
Feb 26 11:29:32 arxh kernel: RBP: 00007fff48be0450 R08: 0000000000000000 R09: 000064cf964ae0a0
Feb 26 11:29:32 arxh kernel: R10: 0000000000000000 R11: 0000000000000246 R12: 000064cf964a2f90
Feb 26 11:29:32 arxh kernel: R13: 0000000000020000 R14: 000064cf964a81f0 R15: 000064cf964ac5d0
Feb 26 11:29:32 arxh kernel:  </TASK>

WTF. It seems the HW doesn't initialize at all.

Feb 26 11:23:24 arxh kernel: DMI: Axioo Pongo 725/Pongo 725, BIOS 1.07.01TAX 09/21/2023

There're no traces of that, but do you run a parallel windows installation?
Can you disable either chip in the UEFI settings?
Is this on battery or external power (or doesn't matter)?

Please post a journal from a boot w/ nouveau to illustrate what's actually working when it does (and I suspect it's the simpledrm device…)

Offline

#13 2025-02-26 11:59:31

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Re: Trouble with NVIDIA driver

seth wrote:

but do you run a parallel windows installation?

No, I don't. I was checked with "lsblk -f", there's no partition that refers to windows.

seth wrote:

Can you disable either chip in the UEFI settings?

I can't disable the chip via UEFI, there is no option to disable the chip.

seth wrote:

Please post a journal from a boot w/ nouveau to illustrate what's actually working when it does (and I suspect it's the simpledrm device…)

Does it mean, I have to uninstall nvidia driver and un-blacklist nouveau?
If yes, here it is
http://0x0.st/8AUh.txt

Offline

#14 2025-02-26 13:42:42

seth
Member
From: Won't reply 2 private help req
Registered: 2012-09-03
Posts: 75,443

Re: Trouble with NVIDIA driver

I can't disable the chip via UEFI, there is no option to disable the chip.

No choice between "discrete" and "integrated" graphics?

Despite

Feb 26 18:45:33 arxh kernel: i915 0000:00:02.0: [drm] Found alderlake_p (device ID 46a3) display version 13.00 stepping D0
Feb 26 18:45:33 arxh kernel: Console: switching to colour dummy device 80x25
Feb 26 18:45:33 arxh kernel: i915 0000:00:02.0: vgaarb: deactivate vga console
Feb 26 18:45:33 arxh kernel: i915 0000:00:02.0: [drm] Using Transparent Hugepages
Feb 26 18:45:33 arxh kernel: ------------[ cut here ]------------
Feb 26 18:45:33 arxh kernel: i915 0000:00:02.0: [drm] Port B asks to use VBT vswing/preemph tables
Feb 26 18:45:33 arxh kernel: WARNING: CPU: 6 PID: 208 at drivers/gpu/drm/i915/display/intel_bios.c:2692 intel_bios_init+0x1352/0x17f0 [i915]
Feb 26 18:45:33 arxh kernel: Modules linked in: i915(+) i2c_algo_bit drm_buddy video mxm_wmi wmi ttm intel_gtt drm_display_helper cec
Feb 26 18:45:33 arxh kernel: CPU: 6 UID: 0 PID: 208 Comm: modprobe Not tainted 6.13.4-arch1-1 #1 07f0136ec6257c7900889d08fabc01499f07b8cb
Feb 26 18:45:33 arxh kernel: Hardware name: Axioo Pongo 725/Pongo 725, BIOS 1.07.01TAX 09/21/2023
Feb 26 18:45:33 arxh kernel: RIP: 0010:intel_bios_init+0x1352/0x17f0 [i915]
Feb 26 18:45:33 arxh kernel: Code: 48 8b 78 08 48 8b 5f 50 48 85 db 75 03 48 8b 1f e8 e3 80 53 e9 44 89 f1 48 89 da 48 c7 c7 60 e2 7a c0 48 89 c6 e8 0e 92 c2 e8 <0f> 0b e9 bb fd ff ff 0f b7 83 60 04 00 00 83 e8 03 66 83 f8 04 76
Feb 26 18:45:33 arxh kernel: RSP: 0018:ffffb929808bf9c0 EFLAGS: 00010286
Feb 26 18:45:33 arxh kernel: RAX: 0000000000000000 RBX: ffff9b22c2970010 RCX: 0000000000000003
Feb 26 18:45:33 arxh kernel: RDX: 0000000000000000 RSI: 0000000000000003 RDI: 0000000000000001
Feb 26 18:45:33 arxh kernel: RBP: ffff9b22ca1b4618 R08: 0000000000000000 R09: ffffb929808bf840
Feb 26 18:45:33 arxh kernel: R10: ffffffffab2b5408 R11: 0000000000000003 R12: 0000000000000001
Feb 26 18:45:33 arxh kernel: R13: 0000000000000000 R14: 0000000000000042 R15: ffff9b22cae7e9c0
Feb 26 18:45:33 arxh kernel: FS:  0000795b30648740(0000) GS:ffff9b265f300000(0000) knlGS:0000000000000000
Feb 26 18:45:33 arxh kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Feb 26 18:45:33 arxh kernel: CR2: 00007ffe1a875fc8 CR3: 00000001016e8004 CR4: 0000000000f70ef0
Feb 26 18:45:33 arxh kernel: PKRU: 55555554
Feb 26 18:45:33 arxh kernel: Call Trace:
Feb 26 18:45:33 arxh kernel:  <TASK>
Feb 26 18:45:33 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 18:45:33 arxh kernel:  ? __warn.cold+0x93/0xf6
Feb 26 18:45:33 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 18:45:33 arxh kernel:  ? report_bug+0xff/0x140
Feb 26 18:45:33 arxh kernel:  ? handle_bug+0x58/0x90
Feb 26 18:45:33 arxh kernel:  ? exc_invalid_op+0x17/0x70
Feb 26 18:45:33 arxh kernel:  ? asm_exc_invalid_op+0x1a/0x20
Feb 26 18:45:33 arxh kernel:  ? intel_bios_init+0x1352/0x17f0 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 18:45:33 arxh kernel:  intel_display_driver_probe_noirq+0x42/0x240 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 18:45:33 arxh kernel:  i915_driver_probe+0x3ba/0xb20 [i915 aeb9b9d2410f30b1d4be194b289226a70d4dcdef]
Feb 26 18:45:33 arxh kernel:  ? drm_privacy_screen_get+0x198/0x1c0
Feb 26 18:45:33 arxh kernel:  local_pci_probe+0x42/0x90
Feb 26 18:45:33 arxh kernel:  pci_device_probe+0xdd/0x270
Feb 26 18:45:33 arxh kernel:  really_probe+0xdb/0x340
Feb 26 18:45:33 arxh kernel:  ? pm_runtime_barrier+0x54/0x90
…

i915 still warning, it takes over from the simpledrm device:

Feb 26 18:45:33 arxh kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Feb 26 18:45:33 arxh kernel: fbcon: i915drmfb (fb0) is primary device
Feb 26 18:45:33 arxh kernel: i915 0000:00:02.0: [drm] fb0: i915drmfb frame buffer device

Afterwards nouveau shows up, there're not outputs attached it the GPU:

Feb 26 18:45:33 arxh kernel: [drm] Initialized nouveau 1.4.0 for 0000:01:00.0 on minor 0
Feb 26 18:45:33 arxh kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes
Feb 26 18:45:33 arxh kernel: nouveau 0000:01:00.0: [drm] Cannot find any crtc or sizes

So the i915 warning is likely just noise.

On the "trouble", the boot in #11 actually succeeded and you logged in on the console before the nvidia module seems to have caused a timeout in udev

…
Feb 26 11:24:24 arxh systemd[1]: Started User Manager for UID 1000.
Feb 26 11:24:24 arxh systemd[1]: Started Session 1 of User thopmann.
Feb 26 11:24:24 arxh login[645]: LOGIN ON tty1 BY thopmann
Feb 26 11:24:25 arxh systemd-udevd[431]: 0000:01:00.0: Worker [475] processing SEQNUM=3710 is taking a long time
Feb 26 11:26:35 arxh systemd-udevd[431]: 0000:01:00.0: Worker [475] processing SEQNUM=3710 killed
Feb 26 11:27:29 arxh kernel: INFO: task kworker/10:1:165 blocked for more than 122 seconds.
Feb 26 11:27:29 arxh kernel:       Tainted: P        W  OE      6.13.4-arch1-1 #1
Feb 26 11:27:29 arxh kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Feb 26 11:27:29 arxh kernel: task:kworker/10:1    state:D stack:0     pid:165   tgid:165   ppid:2      flags:0x00004000
Feb 26 11:27:29 arxh kernel: Workqueue: kacpi_notify acpi_os_execute_deferred
Feb 26 11:27:29 arxh kernel: Call Trace:
Feb 26 11:27:29 arxh kernel:  <TASK>
Feb 26 11:27:29 arxh kernel:  __schedule+0x425/0x12b0
Feb 26 11:27:29 arxh kernel:  ? acpi_ut_allocate_object_desc_dbg+0x8e/0x110
Feb 26 11:27:29 arxh kernel:  schedule+0x27/0xf0
Feb 26 11:27:29 arxh kernel:  schedule_preempt_disabled+0x15/0x30
Feb 26 11:27:29 arxh kernel:  rwsem_down_write_slowpath+0x1d3/0x660
Feb 26 11:27:29 arxh kernel:  ? __slab_free+0xdf/0x2f0
Feb 26 11:27:29 arxh kernel:  down_write+0x5a/0x60
Feb 26 11:27:29 arxh kernel:  os_acquire_rwlock_write+0x2b/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv049738rm+0x10/0x40 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  _nv051176rm+0x284/0x360 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  rm_acpi_nvpcf_notify+0x35/0xf0 [nvidia 6941c45aedd99fc08be5fdd0866a43ea486eb233]
Feb 26 11:27:29 arxh kernel:  acpi_ev_notify_dispatch+0x4b/0x70
Feb 26 11:27:29 arxh kernel:  acpi_os_execute_deferred+0x17/0x30
Feb 26 11:27:29 arxh kernel:  process_one_work+0x17b/0x330
Feb 26 11:27:29 arxh kernel:  worker_thread+0x2ce/0x3f0
…

Did you add any custom udev rules? Attempts at RTD3 or so?
The nvidia driver (nvidia-utils) blacklists nouveau anyway.
What else did you do itr?

Don't overcomplicate this, don't try to do anything special - just installing the nvidia and nvidia-utils packages should™ do.
Speaking of which, have you tried the behavior of linux-lts and nvidia-lts instead?

Offline

#15 2025-02-26 15:00:50

chazzy_whazzy
Member
Registered: 2025-02-22
Posts: 8

Re: Trouble with NVIDIA driver

seth wrote:

Did you add any custom udev rules? Attempts at RTD3 or so?

No, I haven't added any custom udev rules. I was reading about udev to understand it better, but i haven't made any changes to its configuration.


seth wrote:

Speaking of which, have you tried the behavior of linux-lts and nvidia-lts instead?

Ah, I haven't, I will try it tomorrow.

By the way, thank you for today @seth, it really helps me, have a nice day seth.

Offline

Board footer

Powered by FluxBB