Willing to try that, since that problem is very annoying…
Any safe guides to install the proprietary driver? Haven’t done this before.
Sure, here’s one Configure NVIDIA (non-free) settings and load them on Startup, and here’s another Configure Graphics Cards.
Cheers.
2 Likes
The automatic process installed the “video-hybrid-amd-nvidia-prime” driver. The problem with the cable persisted.
I removed this one, and installed manually the “video-nvidia” driver. Problem persists.
However, journal has below entries now:
Oct 26 16:36:41 am5manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP7._PRW], AE_ALREADY_EXISTS (20220331/dswload2-326)
Oct 26 16:36:41 am5manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Oct 26 16:36:41 am5manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20220331/dswload2-326)
Oct 26 16:36:41 am5manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Oct 26 16:36:41 am5manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20220331/dswload2-326)
Oct 26 16:36:41 am5manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20220331/psobject-220)
Oct 26 16:36:41 am5manjaro kernel: hub 10-0:1.0: config failed, hub doesn't have any ports! (err -19)
Oct 26 16:36:41 am5manjaro kernel:
Oct 26 16:36:42 am5manjaro bluetoothd[947]: Failed to set mode: Failed (0x03)
Oct 26 16:36:51 am5manjaro sddm[1213]: Failed to read display number from pipe
Oct 26 16:36:53 am5manjaro sddm[1213]: Failed to read display number from pipe
Oct 26 16:36:56 am5manjaro sddm[1213]: Failed to read display number from pipe
Oct 26 16:36:56 am5manjaro sddm[1213]: Could not start Display server on vt 2
Should I worry about “sddm[1213]” ?
I noticed your BIOS is version F12: There are two BIOS releases available for your mainboard, since F12. It’s possible one of those might improve things.
Yes, couple of times, since when I reboot with the cable on, I end up in a black screen
Not sure what do I need to check there…
True, but these are 13a and 13d. These are release candidates and I had problems with them. I am waiting for the 13 to get published.
I think you mean ACHI mode, not ACPI… It is ACHI mode, the other option is RAID.
Related to ACPI are these under “Advanced CPU Settings”:
PSS Support
Enables or disables the generation of ACPI_PPC, _PSS, and _PCT objects.
Indeed, yes. I was distracted; and possibly dyslexic.
AHCI, IDE, and RAID are the most common choices, depending on the mainboard; and this has nothing to do with the ACPI errors.
But, for now, I’m in great need of sleep. Goodnight.
Tried to update to Kernel 6.5 and see how it goes. Pretty much shame errors, but looks ok.
However, below journal entries are from when I have the cable connected to my dGPU where I end up in a black screen.
Any feedback what is wrong?
Oct 29 17:53:32 am5manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP7._PRW], AE_ALREADY_EXISTS (20230331/dswload2-326)
Oct 29 17:53:32 am5manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230331/psobject-220)
Oct 29 17:53:32 am5manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.GPP2._PRW], AE_ALREADY_EXISTS (20230331/dswload2-326)
Oct 29 17:53:32 am5manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230331/psobject-220)
Oct 29 17:53:32 am5manjaro kernel: ACPI BIOS Error (bug): Failure creating named object [\_GPE._L08], AE_ALREADY_EXISTS (20230331/dswload2-326)
Oct 29 17:53:32 am5manjaro kernel: ACPI Error: AE_ALREADY_EXISTS, During name lookup/catalog (20230331/psobject-220)
Oct 29 17:53:32 am5manjaro kernel: hub 10-0:1.0: config failed, hub doesn't have any ports! (err -19)
Oct 29 17:53:32 am5manjaro kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Oct 29 17:53:32 am5manjaro kernel: iwlwifi 0000:0e:00.0: WRT: Invalid buffer destination
Oct 29 17:53:33 am5manjaro kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Oct 29 17:53:33 am5manjaro systemd-modules-load[490]: Failed to insert module 'nvidia_drm': Device or resource busy
Oct 29 17:53:34 am5manjaro kernel: NVRM: The NVIDIA probe routine was not called for 1 device(s).
Oct 29 17:53:34 am5manjaro systemd[1]: Failed to start Load Kernel Modules.
░░ Subject: A start job for unit systemd-modules-load.service has failed
░░ Defined-By: systemd
░░ Support: https://forum.manjaro.org/c/support
░░
░░ A start job for unit systemd-modules-load.service has finished with a failure.
░░
░░ The job identifier is 38 and the job result is failed.
Oct 29 17:53:34 am5manjaro bluetoothd[854]: src/adapter.c:reset_adv_monitors_complete() Failed to reset Adv Monitors: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to clear UUIDs: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to add UUID: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to add UUID: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to add UUID: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to set mode: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to add UUID: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to add UUID: Failed (0x03)
Oct 29 17:53:34 am5manjaro bluetoothd[854]: Failed to add UUID: Failed (0x03)
Oct 29 17:53:42 am5manjaro sddm[1081]: Failed to read display number from pipe
Oct 29 17:53:44 am5manjaro sddm[1081]: Failed to read display number from pipe
Oct 29 17:53:47 am5manjaro sddm[1081]: Failed to read display number from pipe
Oct 29 17:53:47 am5manjaro sddm[1081]: Could not start Display server on vt 2
Oct 29 17:56:46 am5manjaro kernel: watchdog: watchdog0: watchdog did not stop!
I found this, relating to that error, however it’s a few years old:
In your case, considering that sddm isn’t freezing, this probably isn’t relevant.
I can’t help any further with those errors, except to try attaching the cable to another port; most likely you have already tried that.
I had it attached on another VGA, an AMD 6900XT, so I thing that suffices for “another port” 
Thank you, anyway!
I bit different info from dmesg:
[ 11.841013] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[ 11.841929] NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[ 11.841930] NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
[ 11.841930] NVRM: No NVIDIA devices probed.
[ 18.582048] CIFS: No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3.1.1), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3.1.1 (or even SMB3 or SMB2.1) specify vers=1.0 on mount.
[ 19.468419] qemu-system-x86[1135]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
[ 20.305167] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[ 20.306061] NVRM: This can occur when a driver such as:
NVRM: nouveau, rivafb, nvidiafb or rivatv
NVRM: was loaded and obtained ownership of the NVIDIA device(s).
[ 20.306061] NVRM: Try unloading the conflicting kernel module (and/or
NVRM: reconfigure your kernel without the conflicting
NVRM: driver(s)), then try loading the NVIDIA kernel module
NVRM: again.
[ 20.306062] NVRM: No NVIDIA devices probed.
This is after I installed Nvidia driver, and not the default open source