You are not logged in.
I occasionally get a black screen when I go to wake up my laptop after a minute of inactivity. I'm not sure whats causing this problem exactly. I'm new to Arch and am not fully knowledgeable with the command line.
I am running Arch with KDE Plasma as my desktop.
Last edited by NeonWyvern24 (2024-04-18 18:36:56)
Offline
DPMS?
Plasma on wayland (now the default) or X11 and does it make a difference?
Please post your complete system journal for the boot:
sudo journalctl -b | curl -F 'file=@-' 0x0.stOffline
I've switched to X11 to hopefully perform better with my nVidia graphics
The device also appears to crash occasionally while performing the same actions.
I ran the command and only recieved:
http://0x0.st/Xom1.txt
I'm not sure what to do with this.
Edit: I just realized what that did ![]()
Last edited by NeonWyvern24 (2024-04-18 10:58:17)
Offline
The boot ran only for ~2 minutes, does it cover such incident?
You've a hybrid graphics system (amdgpu+nvidia) and
Apr 18 06:52:20 LOQ-15APH8 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2
Apr 18 06:52:20 LOQ-15APH8 kernel: nvidia-modeset: WARNING: GPU:0: Unable to read EDID for display device DP-2
…
Apr 18 06:52:20 LOQ-15APH8 kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get target temp from SBIOS @ platform_request_handler_ctrl.c:2146
Apr 18 06:52:20 LOQ-15APH8 kernel: NVRM: nvAssertOkFailedNoLog: Assertion failed: Invalid data passed [NV_ERR_INVALID_DATA] (0x00000025) returned from PlatformRequestHandler failed to get platform power mode from SBIOS @ platform_request_handler_ctrl.c:2089
Apr 18 06:52:41 LOQ-15APH8 kernel: NVRM: rmapiAllocWithSecInfo: RMAPI_GPU_LOCK_INTERNAL alloc requested without holding the RMAPI locksome issues w/ the nvidia chip.
Step #1
Enable https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!), stay away from fbdev=1 for now (the results are inconclusive and there was just a thread where this locked the framebuffer…)
Offline
Thanks. However I'm not sure where I find the DRM modeset setting to switch it. Where would I find that at?
Offline
Did you click the link I posted?
Offline
Yeah. It states; "To enable it, set the modeset=1 kernel module parameter for the nvidia_drm module.". Although, I'm not sure where that is.
I hope I'm not being difficult. ![]()
Offline
"kernel module parameter" in that sentence is a link, if you don't understand the sentence on it's own, chances are you need to click that link to get further information on what kernel parameters are and how they can be set.
The method of doing so depends on your bootloader which you've set up during install and that link contains instructions for each of them.
Offline
Okay. so I added the values "nvidia_drm.modeset=1" & "nvidia_drm.fbdev=1" to the file nvidia_drm.conf under /etc/modprobe.d however I run
cat /sys/module/nvidia_drm/parameters/modesetand it still outputs N. I did everything I think it was telling me. Am I missing something?
Offline
NOT a modprobe option and you would have had to rebuild the initramfs and I told you to stay awy from fvdev and also that's the wrong syntax for modprobe
Offline
It says that the loadable kernel modules are set within /etc/modprobe.d/, and that the syntax is parameter=value. And I missed the no fbdev, it was in the wiki so I just followed it. I'm can't tell what I'm doing wrong.
Offline
My problem has been resolved and assistance is no longer needed. I apologize for wasting your time.
Offline
Offline
I switched my server back to wayland and everything's fine
Offline
Without setting nvidia_drm.modeset=1 ? That is a precondition that nvidia wayland anything works in any capacity.
Offline
I'm not sure. Everything works fine now so I don't have a problem and no longer need support.
Offline
Strange... In any case please mark as [SOLVED] by editing the title in your first post.
Offline
It's a dual graphcis system, wayland will run fine on the primary AMD chip and I guess the nvidia one is completely ignored.
@NeonWyvern24
If you want to use the nvidia GPU (esp. on wayland) you'll have to make sure that
cat /sys/module/nvidia_drm/parameters/modeset says "Y"
If it doesn't, you need to understand that
added the values "nvidia_drm.modeset=1" & "nvidia_drm.fbdev=1" to the file nvidia_drm.conf under /etc/modprobe.d
is wrong on multiple levels and will only lead to modprobe complaints about bogus module parameters.
Those are kernel parameters and you're supposed to add "nvidia_drm.modeset=1" to the kernel commandline.
You can fix this now or later - looking the other side won't work and only at *that* point you'd have wasted peoples time because all efforts effectively didn't lead anywhere because you decided to run.
Since I assume that there's probably some language barrier: https://deepl.com
Offline