[Help] I get Kernel panic error when pc wakes from suspend mode

Anu · 2024-07-12 10:24:32

Help please i am new and i am using gnome desktop and I am using Nvidia Graphic card (GTX1050 TI) and I think this issue is related to that i have tried re-installing drivers, re-installing OS but nothing seems to work it was fine before few updates but now i am facing this problem.

https://imgur.com/WFk3m0J

This is the error i am getting please Help .

Last edited by V1del (2024-07-12 11:19:00)

Anu · 2024-07-12 10:25:52

https://imgur.com/WFk3m0J - this is the image link sorry i don't know how this works this is my first post

V1del · 2024-07-12 11:21:26

Which nvidia driver version are you running? If not 555x from the repos but e.g. 535 from the AUR you need to disable user session freezing on systemd's side: https://bbs.archlinux.org/viewtopic.php … 7#p2181817 and the last post for some more locations to add this file.

Anu · 2024-07-12 13:47:56

and i tried doing the above thing it didn't fix it

V1del · 2024-07-12 14:25:08

The thing I linked should already be present in the repo versions of nvidia-utils.

Generally speaking for suspend to work properly you need to configure restoration of VRAM as documented in: https://wiki.archlinux.org/title/NVIDIA … er_suspend

seth · 2024-07-12 20:04:24

1. can you suspend/resume from the multi-user.target? (2nd link below)
2. if yes, please post the journal covering that

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

3. can you still scroll up in the console output you posted - this is maybe not the first error
4. have you tried the 535xx drivers?

akb825 · 2024-07-13 09:01:30

Same issue here, and setting NVreg_PreserveVideoMemoryAllocations=1 doesn't appear to fix it. The previous driver version (I believe 550) had a small (like 10%) chance to have a blank screen on resume, but the current driver has a very high (like 90-95%) chance to kernel panic.

See also this post on the NVIDIA forums. The stack trace isn't quite the same as my own, but the rest is very similar.

Here is a relevant extract from my own log:

Jul 13 01:37:29 htpc systemd-sleep[1065]: System returned from sleep operation 'suspend'.
Jul 13 01:37:32 htpc kernel: BUG: unable to handle page fault for address: ffff9fd744fdac04
Jul 13 01:37:32 htpc kernel: #PF: supervisor read access in kernel mode
Jul 13 01:37:35 htpc kernel: #PF: error_code(0x0000) - not-present page
Jul 13 01:37:35 htpc kernel: PGD 100000067 P4D 100000067 PUD 100219067 PMD 0 
Jul 13 01:37:35 htpc kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Jul 13 01:37:35 htpc kernel: CPU: 0 PID: 490 Comm: irq/29-nvidia Tainted: P
          IOE      6.9.9-arch1-1 #1 a564e80ab10c5cd5584d6e9a0715907a10e33ca4
Jul 13 01:37:35 htpc kernel: Hardware name: MSI MS-7522/MSI X58 Pro (MS-7522)
      , BIOS V7.3 04/17/2009
Jul 13 01:37:35 htpc kernel: RIP: 0010:_nv012398rm+0xbd/0x130 [nvidia]
Jul 13 01:37:35 htpc kernel: Code: 8b 45 20 41 bf 01 00 00 00 41 89 54 24 20 41 89 44 24 24 4c 89 e6 4c 89 ef e8 ef 78 65 00 49 89 c4 48 85 c0 74 5f 49 8b 0c 24 <8b> 41 04 0f ae e8 41 39 44 24 20 74 dc 8b 41 08 0f b7 d8 25 00 00
Jul 13 01:37:35 htpc kernel: RSP: 0018:ffff9fd74150fcc0 EFLAGS: 00010286
Jul 13 01:37:35 htpc kernel: RAX: ffff928064e5bdd8 RBX: 0000000000000001 RCX: ffff9fd744fdac00
Jul 13 01:37:35 htpc kernel: RDX: fffffffffffffff0 RSI: ffff928045d18008 RDI: ffff928045d188e8
Jul 13 01:37:35 htpc kernel: RBP: ffff92806502abe0 R08: 0000000000000000 R09: 000000000000000020
Jul 13 01:37:35 htpc kernel: R10: ffff92806502ac24 R11: ffffffffc0ff65f0 R12: ffff928064e5bdd8
Jul 13 01:37:35 htpc kernel: R13: ffff928045d188e8 R14: ffff928045d18008 R15: 0000000000000000
Jul 13 01:37:35 htpc kernel: FS:  0000000000000000(0000) GS:ffff9280f9a00000(0000) knlGS:0000000000000000
Jul 13 01:37:35 htpc kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jul 13 01:37:35 htpc kernel: CR2: ffff9fd744fdac04 CR3: 0000000104964000 CR4: 00000000000006f0
Jul 13 01:37:35 htpc kernel: Call Trace:
Jul 13 01:37:35 htpc kernel:  <TASK>
Jul 13 01:37:35 htpc kernel:  ? __die_body.cold+0x19/0x27
Jul 13 01:37:35 htpc kernel:  ? page_fault_oops+0x15a/0x2b0
Jul 13 01:37:35 htpc kernel:  ? search_bpf_extables+0x5f/0x80
Jul 13 01:37:35 htpc kernel:  ? exc_page_fault+0x18a/0x190
Jul 13 01:37:35 htpc kernel:  ? asm_exc_page_fault+0x26/0x30
Jul 13 01:37:35 htpc kernel:  ? _nv012399rm+0x1f0/0x1f0 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  ? _nv012398rm+0xbd/0x130 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  _nv035255rm+0x19e/0x2f0 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  _nv030183rm+0x24/0xc0 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  _nv021801rm+0x295/0x3c4 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  _nv031947rm+0x63/0xc0 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  _nv012544rm+0x27f/0x3f0 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  _nv031957rm+0x167/0x1d0 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  _nv000735rm+0x113/0x150 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  rm_isr_bh+0x20/0x5c [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  nvidia_isr_kthread_bh+0x1f/0x50 [nvidia 41a16fe130ec860eaba96a8a9fe1d23564470a94]
Jul 13 01:37:35 htpc kernel:  irq_thread_fn+0x23/0x60
Jul 13 01:37:35 htpc kernel:  irq_thread+0x18f/0x270
Jul 13 01:37:35 htpc kernel:  ? __pfx_irq_thread_fn+0x10/0x10
Jul 13 01:37:35 htpc kernel:  ? __pfx_irq_thread_dtor+0x10/0x10
Jul 13 01:37:35 htpc kernel:  ? __pfx_irq_thread+0x10/0x10
Jul 13 01:37:35 htpc kernel:  kthread+0xd2/0x100
Jul 13 01:37:35 htpc kernel:  ? __pfx_kthread+0x10/0x10
Jul 13 01:37:35 htpc kernel:  ret_from_fork+0x34/0x50
Jul 13 01:37:35 htpc kernel:  ? __pfx_kthread+0x10/0x10
Jul 13 01:37:35 htpc kernel:  ret_from_fork_asm+0x1a/0x30
Jul 13 01:37:35 htpc kernel:  </TASK>

seth · 2024-07-13 12:27:11

What do the irrelevant parts from before the sleep look like?

seth wrote:

4. have you tried the 535xx drivers?

akb825 · 2024-07-13 17:26:47

seth wrote:

What do the irrelevant parts from before the sleep look like?

Jul 13 01:36:26 htpc ntpd[621]: Listen normally on 4 enp6s0 192.168.0.102:123
Jul 13 01:36:26 htpc ntpd[621]: Listen normally on 5 enp6s0 [2600:8801:e800:28e:7150:5ecd:bf6e:336b]:123
Jul 13 01:36:26 htpc ntpd[621]: Listen normally on 6 enp6s0 [fe80::e31e:1798:972c:5dfd%2]:123
Jul 13 01:36:26 htpc ntpd[621]: 74.6.168.72 local addr <null> -> 192.168.0.102
Jul 13 01:36:26 htpc ntpd[621]: 2600:1700:5a0f:ee00::314:1b local addr <null> -> 2600:8801:e800:28e:7150:5ecd:bf6e:336b
Jul 13 01:36:26 htpc ntpd[621]: 5.78.62.36 local addr <null> -> 192.168.0.102
Jul 13 01:36:26 htpc ntpd[621]: 155.248.196.28 local addr <null> -> 192.168.0.102
Jul 13 01:36:26 htpc ntpd[621]: new interface(s) found: waking up resolver
Jul 13 01:36:30 htpc sudo[1045]: pam_systemd_home(sudo:account): New sd-bus connection (system-bus-pam-systemd-home-1045) opened.
Jul 13 01:36:30 htpc sudo[1045]:  abarany : PWD=/home/abarany ; USER=root ; COMMAND=/usr/bin/systemctl suspend
Jul 13 01:36:30 htpc sudo[1045]: pam_unix(sudo:session): session opened for user root(uid=0) by abarany(uid=1000)
Jul 13 01:36:30 htpc systemd-logind[569]: The system will suspend now!
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3016] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3017] manager: NetworkManager state is now ASLEEP
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3019] device (enp6s0): state change: activated -> deactivating (reason 'sleeping', sys-iface-state:'managed')
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3019] dhcp4 (enp6s0): canceled DHCP transaction
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3020] dhcp4 (enp6s0): activation: beginning transaction (timeout in 45 seconds)
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3020] dhcp4 (enp6s0): state changed no lease
Jul 13 01:36:30 htpc sudo[1045]: pam_unix(sudo:session): session closed for user root
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3022] dhcp6 (enp6s0): canceled DHCP transaction
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3022] dhcp6 (enp6s0): activation: beginning transaction (timeout in 45 seconds)
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3022] dhcp6 (enp6s0): state changed no lease
Jul 13 01:36:30 htpc avahi-daemon[566]: Withdrawing address record for 192.168.0.102 on enp6s0.
Jul 13 01:36:30 htpc avahi-daemon[566]: Leaving mDNS multicast group on interface enp6s0.IPv4 with address 192.168.0.102.
Jul 13 01:36:30 htpc avahi-daemon[566]: Interface enp6s0.IPv4 no longer relevant for mDNS.
Jul 13 01:36:30 htpc systemd[1]: Starting Network Manager Script Dispatcher Service...
Jul 13 01:36:30 htpc systemd[1]: Started Network Manager Script Dispatcher Service.
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.3979] device (enp6s0): state change: deactivating -> disconnected (reason 'sleeping', sys-iface-state: 'managed')
Jul 13 01:36:30 htpc NetworkManager[564]: <info>  [1720859790.4002] device (enp6s0): state change: disconnected -> unmanaged (reason 'unmanaged-sleeping', sys-iface-state: 'managed')
Jul 13 01:36:30 htpc kernel: r8169 0000:06:00.0 enp6s0: Link is Down
Jul 13 01:36:30 htpc systemd[1]: Reached target Sleep.
Jul 13 01:36:30 htpc systemd[1]: Starting NVIDIA system suspend actions...
Jul 13 01:36:30 htpc suspend[1055]: nvidia-suspend.service
Jul 13 01:36:30 htpc logger[1055]: <13>Jul 13 01:36:30 suspend: nvidia-suspend.service
Jul 13 01:36:30 htpc csd-media-keys[693]: Unable to get default sink
Jul 13 01:36:30 htpc csd-media-keys[693]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jul 13 01:36:30 htpc csd-media-keys[693]: gvc_mixer_card_get_index: assertion 'GVC_IS_MIXER_CARD (card)' failed
Jul 13 01:36:30 htpc csd-media-keys[693]: Unable to get default sink
Jul 13 01:36:31 htpc systemd[1]: nvidia-suspend.service: Deactivated successfully.
Jul 13 01:36:31 htpc systemd[1]: Finished NVIDIA system suspend actions.
Jul 13 01:36:31 htpc systemd[1]: Starting System Suspend...
Jul 13 01:36:31 htpc systemd-sleep[1065]: User sessions remain unfrozen on explicit request ($SYSTEMD_SLEEP_FREEZE_USER_SESSIONS=0).
Jul 13 01:36:31 htpc systemd-sleep[1065]: This is not recommended, and might result in unexpected behavior, particularly
Jul 13 01:36:31 htpc systemd-sleep[1065]: in suspend-then-hibernate operations or setups with encrypted home directories.
Jul 13 01:36:31 htpc systemd-sleep[1065]: Performing sleep operation 'suspend'...
Jul 13 01:36:31 htpc kernel: PM: suspend entry (deep)
Jul 13 01:37:29 htpc kernel: Filesystems sync: 0.494 seconds
Jul 13 01:37:29 htpc kernel: Freezing user space processes
Jul 13 01:37:29 htpc kernel: Freezing user space processes completed (elapsed 0.001 seconds)
Jul 13 01:37:29 htpc kernel: OOM killer disabled.
Jul 13 01:37:29 htpc kernel: Freezing remaining freezable tasks
Jul 13 01:37:29 htpc kernel: Freezing remaining freezable tasks completed (elapsed 0.000 seconds)
Jul 13 01:37:29 htpc kernel: printk: Suspending console(s) (use no_console_suspend to debug)
Jul 13 01:37:29 htpc kernel: mceusb 4-2:1.0: suspend
Jul 13 01:37:29 htpc kernel: serial 00:02: disabled
Jul 13 01:37:29 htpc kernel: sd 4:0:0:0: [sda] Synchronizing SCSI cache
Jul 13 01:37:29 htpc kernel: sd 4:0:1:0: [sdb] Synchronizing SCSI cache
Jul 13 01:37:29 htpc kernel: ata5.00: Entering standby power mode
Jul 13 01:37:29 htpc kernel: ata5.01: Entering standby power mode
Jul 13 01:37:29 htpc kernel: ACPI: PM: Preparing to enter system sleep state S3
Jul 13 01:37:29 htpc kernel: ACPI: PM: Saving platform NVS memory
Jul 13 01:37:29 htpc kernel: Disabling non-boot CPUs ...
Jul 13 01:37:29 htpc kernel: smpboot: CPU 1 is now offline
Jul 13 01:37:29 htpc kernel: smpboot: CPU 2 is now offline
Jul 13 01:37:29 htpc kernel: smpboot: CPU 3 is now offline
Jul 13 01:37:29 htpc kernel: smpboot: CPU 4 is now offline
Jul 13 01:37:29 htpc kernel: smpboot: CPU 5 is now offline
Jul 13 01:37:29 htpc kernel: smpboot: CPU 6 is now offline
Jul 13 01:37:29 htpc kernel: smpboot: CPU 7 is now offline
Jul 13 01:37:29 htpc kernel: ACPI: PM: Low-level resume complete
Jul 13 01:37:29 htpc kernel: ACPI: PM: Restoring platform NVS memory
Jul 13 01:37:29 htpc kernel: Force enabled HPET at resume
Jul 13 01:37:29 htpc kernel: Enabling non-boot CPUs ...
Jul 13 01:37:29 htpc kernel: smpboot: Booting Node 0 Processor 1 APIC 0x2
Jul 13 01:37:29 htpc kernel: CPU1 is up
Jul 13 01:37:29 htpc kernel: smpboot: Booting Node 0 Processor 2 APIC 0x4
Jul 13 01:37:29 htpc kernel: CPU2 is up
Jul 13 01:37:29 htpc kernel: smpboot: Booting Node 0 Processor 3 APIC 0x6
Jul 13 01:37:29 htpc kernel: CPU3 is up
Jul 13 01:37:29 htpc kernel: smpboot: Booting Node 0 Processor 4 APIC 0x1
Jul 13 01:37:29 htpc kernel: CPU4 is up
Jul 13 01:37:29 htpc kernel: smpboot: Booting Node 0 Processor 5 APIC 0x3
Jul 13 01:37:29 htpc kernel: CPU5 is up
Jul 13 01:37:29 htpc kernel: smpboot: Booting Node 0 Processor 6 APIC 0x5
Jul 13 01:37:29 htpc kernel: CPU6 is up
Jul 13 01:37:29 htpc kernel: smpboot: Booting Node 0 Processor 7 APIC 0x7
Jul 13 01:37:29 htpc kernel: CPU7 is up
Jul 13 01:37:29 htpc kernel: ACPI: PM: Waking up from system sleep state S3
Jul 13 01:37:29 htpc kernel: usb usb1: root hub lost power or was reset
Jul 13 01:37:29 htpc kernel: usb usb4: root hub lost power or was reset
Jul 13 01:37:29 htpc kernel: usb usb5: root hub lost power or was reset
Jul 13 01:37:29 htpc kernel: usb usb6: root hub lost power or was reset
Jul 13 01:37:29 htpc kernel: usb usb7: root hub lost power or was reset
Jul 13 01:37:29 htpc kernel: usb usb8: root hub lost power or was reset
Jul 13 01:37:29 htpc kernel: serial 00:02: activated
Jul 13 01:37:29 htpc kernel: ata3.00: ACPI cmd ef/03:0c:00:00:00:a0(SET FEATURES) filtered out
Jul 13 01:37:29 htpc kernel: ata3.00: ACPI cmd ef/03:46:00:00:00:a0(SET FEATURES) filtered out
Jul 13 01:37:29 htpc kernel: usb 4-2: reset full-speed USB device number 2 using uhci_hcd
Jul 13 01:37:29 htpc kernel: ata2: SATA link down (SStatus 0 SControl 300)
Jul 13 01:37:29 htpc kernel: ata1: SATA link down (SStatus 0 SControl 300)
Jul 13 01:37:29 htpc kernel: ata7: SATA link down (SStatus 0 SControl 300)
Jul 13 01:37:29 htpc kernel: ata8: SATA link down (SStatus 0 SControl 300)
Jul 13 01:37:29 htpc kernel: usb 5-2: reset low-speed USB device number 3 using uhci_hcd
Jul 13 01:37:29 htpc kernel: usb 6-1: reset low-speed USB device number 2 using uhci_hcd
Jul 13 01:37:29 htpc kernel: mceusb 4-2:1.0: resume
Jul 13 01:37:29 htpc kernel: firewire_core 0000:07:00.0: rediscovered device fw0
Jul 13 01:37:29 htpc kernel: ata6.00: SATA link down (SStatus 0 SControl 300)
Jul 13 01:37:29 htpc kernel: ata6.01: SATA link down (SStatus 0 SControl 300)
Jul 13 01:37:29 htpc kernel: ata5.00: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 13 01:37:29 htpc kernel: ata5.01: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
Jul 13 01:37:29 htpc kernel: ata5.01: ACPI cmd ef/03:45:00:00:00:b0(SET FEATURES) filtered out
Jul 13 01:37:29 htpc kernel: ata5.01: ACPI cmd ef/03:0c:00:00:00:b0(SET FEATURES) filtered out
Jul 13 01:37:29 htpc kernel: ata5.01: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Jul 13 01:37:29 htpc kernel: sd 4:0:0:0: [sda] Starting disk
Jul 13 01:37:29 htpc kernel: ata5.00: ACPI cmd ef/03:45:00:00:00:a0(SET FEATURES) filtered out
Jul 13 01:37:29 htpc kernel: ata5.00: ACPI cmd ef/03:0c:00:00:00:a0(SET FEATURES) filtered out
Jul 13 01:37:29 htpc kernel: ata5.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out
Jul 13 01:37:29 htpc kernel: ata5.00: configured for UDMA/133
Jul 13 01:37:29 htpc kernel: ata5.01: configured for UDMA/133
Jul 13 01:37:29 htpc kernel: sd 4:0:1:0: [sdb] Starting disk
Jul 13 01:37:29 htpc kernel: usb 5-1: reset low-speed USB device number 2 using uhci_hcd
Jul 13 01:37:29 htpc kernel: OOM killer enabled.
Jul 13 01:37:29 htpc kernel: Restarting tasks ... done.
Jul 13 01:37:29 htpc kernel: random: crng reseeded on system resumption
Jul 13 01:37:29 htpc kernel: PM: suspend exit

This is the log starting directly before the sleep. (the previous messages are related to mounting network drives, which is set up to do during boot)

seth wrote:

4. have you tried the 535xx drivers?

Not since they were the latest, I was planning on looking into downgrading with an AUR package to work around the issue.

Edit: looks like that won't work, at least not without some tweaking, based on the most recent post on the AUR package:

DKMS build is currently broken, due to this issue: https://forums.developer.nvidia.com/t/n … -up/279072

One other thing to note is waking up immediately after suspend is significantly less likely to trigger the kernel panic. If I suspend and immediately resume it usually doesn't crash, but if I resume after some hours it almost always does.

Last edited by akb825 (2024-07-13 17:36:27)

seth · 2024-07-13 20:09:25

Edit: looks like that won't work, at least not without some tweaking, based on the most recent post on the AUR package:

That was a thing several months ago, there were serveral posts in the forum, patches slushing around and eventually nvidia fixed this upstream - have you tried?
(The 470 comment in the AUR actually was about that situation)

User session remains unfrozen, so that's not it (but incidentally you might have to provide that manually)

akb825 · 2024-07-13 20:42:18

I didn't try it earlier since the comment was a week and a half ago and there was no package update since then, but I gave it a try now and the DKMS stage went through successfully. Perhaps the commenter had an outdated package.

After suspending and resuming a few times it does seem to have avoided the kernel panic, though since it was less likely to happen when resuming very shortly after suspending it isn't fully conclusive. I'll report back later for whether I see any further crashes once I've had some longer periods of being suspended where it was almost guaranteed to crash before.

Anu · 2024-07-15 06:03:26

waking up immediately after suspend is significantly less likely to trigger the kernel panic. If I suspend and immediately resume it usually doesn't crash, but if I resume after some hours it almost always does. This is what's happening for me. idk what to do i tried the steps provided by @v1del but that didn't fix the issue.

seth · 2024-07-15 06:27:32

seth wrote:

4. have you tried the 535xx drivers?

akb825 · 2024-07-15 19:59:22

At this point I think I can fairly confidently say that the 535 drivers are stable.

@Anu in case you aren't sure what @seth is referring to, try installing the nvidia-535xx-dkms package on AUR. Any other nvidia packages you have installed should be replaced by an equivalent 535xx package on AUR. (note that nvidia-utils will be already be covered by nvidia-535xx-dkms) See Arch User Repository for more info on how to install AUR packages.

Anu · 2024-07-16 05:46:33

i am trying to install that driver, but it is saying that it breaks some dependency of "nvidia-utils" and if i try to uninstall that it breaks the dependency of "lib32-nvidia", so it is not even letting me install all the packages of nvidia-535xx-dkms package so i don't know if that affects something or not.

seth · 2024-07-16 05:50:38

Do not try to uninstall anything. Install the 535xx packages, they'll trigger a conflict warning and ask you whether you want to replace the nvidia packages.
https://wiki.archlinux.org/title/Pacman … de/removal - maybe read around that page anyway.

akb825 · 2024-07-16 06:04:11

If the lib32 packages are installed, it will complain when you attempt to replace the base nvidia packages with nvidia-535xx because of the lib32 package dependencies. To work around it, it should be safe to uninstall the lib32-nvidia packages, then replace them with the lib32-nvidia-535xx packages once the base nvidia-535xx-dkms package is in place. However, as seth says you should avoid manually removing the nvidia and nvidia-utils packages, and let nvidia-535xx-dkms replace them as part of its installation.

I had to go through the same process with my install.

Edit: I used an AUR package manager to install them, which builds the packages one at a time. If you manually run makepkg on all of the nvidia-535xx packages (including the lib32 ones), you may be able to install all of them at the same time through a single pacman command to avoid having to uninstall the lib32 packages first.

Last edited by akb825 (2024-07-16 06:07:47)

Arch Linux

#1 2024-07-12 10:24:32

[Help] I get Kernel panic error when pc wakes from suspend mode

#2 2024-07-12 10:25:52

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#3 2024-07-12 11:21:26

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#4 2024-07-12 13:47:56

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#5 2024-07-12 14:25:08

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#6 2024-07-12 20:04:24

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#7 2024-07-13 09:01:30

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#8 2024-07-13 12:27:11

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#9 2024-07-13 17:26:47

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#10 2024-07-13 20:09:25

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#11 2024-07-13 20:42:18

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#12 2024-07-15 06:03:26

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#13 2024-07-15 06:27:32

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#14 2024-07-15 19:59:22

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#15 2024-07-16 05:46:33

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#16 2024-07-16 05:50:38

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

#17 2024-07-16 06:04:11

Re: [Help] I get Kernel panic error when pc wakes from suspend mode

Board footer