OK, those are all quick things to mention based upon the inxi.
Can I ask if this is a new install … as in you are finding freshly installed system to act this way?
Or is it a longstanding system that is suddenly acting this way ?
Now I enabled swap but still the same.
I use a backup Disk from my previous PC. Now I want to migrate to this new PC.
sudo mhwd -li
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-nvidia 2023.03.23 false PCI
Warning: No installed USB configs!
I tried to use nvidia-470 driver, no this issue, but can’t adjust lightness
I have updated BIOS to latest. issue is not fixed.
Tried to create a new user but the new user has the same issue.
Tried to install amd-ucode but still the same.
I also have almost this exact problem, running Manjaro multi-boot on a '12 Mac Pro with Nvidia GTX780 card. In my case it’s the machine spins up after waking from suspend, but display remains black . . . no cursor.
It happened in the 5.15.146-1-MANJARO kernel, but in grub “advanced options” there are two kernel options, the lower one provided 5.4.266-1-MANJARO . . . and we are back in business as we were last week, display revives from suspend properly.
This problem has been affecting my Leap 15.6 “/” and there, moving the kernel forward to the newest kernels available has not fixed the problem . . . I think that is their 6.7 xxx lp xxxx kernels, been going on for a couple of months. Today was the first time in many moons that there has been a problem with manjaro’s basic functioning . . . .
I have a Tumbleweed, two debian, a mint LMDE, and a Lubuntu Noble installs that are working fine; now only Leap and Manjaro are failing to revive from suspend . . . seems possibly “kernel” related. Nothing to do in Manjaro, except for upgrading Firefox and some "majaro “dummy package” . . . . Non-revival from suspend does interfere with basic daily driving . . . now I know I need to “advance option” to roll back the kernel???
Seems like from the bug report handler on the Bugzilla site, it is a “difficult problem to figure out,” AND it is a problem that does interfere with normal usage of an OS . . . . In the case of Leap the affliction has continued for several months . . . .
I’ll have to monitor Manjaro to see if and when a new kernel comes down the pike, does it perpetuate the problem or fix it??
Hmm . . . some problems just hang around because the problem is difficult to figure out, or it effects only a few people . . . low motivation, etc.
I posted another thread on the >kernel subforum to find out if adding kernels to Manjaro would remove the one that is now working in my system, and the good news is, kernels stay installed until manually removed. But the commenter indicated that “packages get installed with the kernel” . . . meaning that possibly it’s something other than the kernel itself that are brought in, and perhaps those packages are 'the problem"??? And, so, the latest system iso’s are going to have those packages, thus perpetuating the problem???
I don’t know what percentage of users have nvidia cards in them, but, having had this same problem through a number of OSs over the years I have found that if it is “upstream” with something from Nvidia, they also have “low motivation” to try to fix a linux problem . . . because what is “in it for them $$$$???” to fix open source system problems . . . ???
Best to be patient, my “ultimate solution” in linux is to have multi-boot system, that way as one system hits a run of problems I have other systems that are working properly, etc.
I got the same problem with XFCE sometimes, with Kernel 6.6 i got a blackscreen after suspend,
with 6.1 i get a blackscreen with a mousepointer.
So far i fixed it a bit by setting at powermanagement - system from sleep, hibernate to suspend,
shown here. https://docs.xfce.org/xfce/xfce4-power-manager/preferences
Maybe it helps until the patch comes along and we can see, how it will goes.
It’s not clear from your post what exactly you set your settings to to try to get some revival from suspend??? I just looked at it and there doesn’t seem to be any, “when reviving from suspend” data included??
But, seems like from what you are saying it provides modest assistance and the real “answer” will be if and when a patch gets applied to dbus??
When you scroll down at the page above, there is the tab ‘system’, where it shows the settings if you are using XFCE.
You can find that at your your desktop at applications - settings - power management.
Since i dont want suspend with pressing a button, i did choose the main rule for suspend mode there.
Sleep mode does not work anyway.
I also turned off my display power management, but not sure, if that makes a difference.
That makes sense.
I only now realized you have dual-gfx.
It didnt appear in the inxi at first glance … I suppose because of the forced nvidia driver install.
But looking at the CPU it identifies itself as having graphical capabilities.
With the correct profile installed…
(Note: you should have no other mhwd profiles except video-linux and video-hybrid-amd-nvidia-prime)
X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 152 (GLX)
Minor opcode of failed request: 24 (X_GLXCreateNewContext)
Value in failed request: 0x0
Serial number of failed request: 50
Current serial number in output stream: 51
but now I find it has no sound but only when I plug in earphone.
Generally I have learned over the years in linux using Nvidia cards that going “nouveau” or “default” rather than with proprietary nvidia drivers, usually provides more consistent function . . . but clearly not always. Nvidia doesn’t seem to give spot on upgrades with each new linux release.
I started another thread asking about kernels in the forum, and there one of the posters said this problem possibly relates to problems with “Dbus” and that they are waiting for a patch for it . . . ETA unknown at this point??
If you have to do something, then maybe check into what that patch for Dbus might entail and test it out and then let us tired olden folke know how it went?? : - ))))))