Hello Carla, Carla Sensa <carlase...@sfr.fr> ezt írta (időpont: 2022. jan. 4., K, 17:18): > > Hello Laszlo, > > Sometimes Nvidia drivers and ddcutil just don't play well together... > > The script installs a more recent version of ddcutil than Ubuntu focal > ships with (V1.2.1 vs V0.9.8-2). > > Try uninstalling ddcutil-1.2.1 and see if E starts behaving well > again(reboot your computer).
Thanks for your idea. I've moved the libddcutil* files away from /usr/local/lib, restarted the laptop, and checked the memory maps of E to make sure the .so is not loaded. Then I retried suspending, but unfortunately the nvidia error is still present at resume, and the desktop is still dark and frozen. Regards, Laszlo > > Le 04/01/2022 à 15:20, Carsten Haitzler a écrit : > > On Tue, 4 Jan 2022 11:56:00 +0100 "ezerot...@gmail.com" > > <ezerot...@gmail.com> > > said: > > > >> Carsten Haitzler <ras...@rasterman.com> ezt írta (időpont: 2022. jan. > >> 3., H, 22:49): > >>> > >>> On Mon, 3 Jan 2022 22:28:19 +0100 "ezerot...@gmail.com" > >>> <ezerot...@gmail.com> said: > >>> > >>>> Carsten Haitzler <ras...@rasterman.com> ezt írta (időpont: 2022. jan. > >>>> 3., H, 21:36): > >>>>> > >>>>> On Mon, 3 Jan 2022 19:34:41 +0100 "ezerot...@gmail.com" > >>>>> <ezerot...@gmail.com> said: > >>>>> > >>>>>> Carsten Haitzler <ras...@rasterman.com> ezt írta (időpont: 2022. jan. > >>>>>> 3., H, 19:13): > >>>>>>> > >>>>>>> On Mon, 3 Jan 2022 17:07:43 +0100 "ezerot...@gmail.com" > >>>>>>> <ezerot...@gmail.com> said: > >>>>>>> > >>>>>>>> Hi, > >>>>>>>> > >>>>>>>> I've a brand new amd laptop with an nvidia mobile GPU. It arrived > >>>>>>>> with TuxedoOS (ubuntu 20.04 + budgie wm) preinstalled. That setup > >>>>>>>> works fine out of the box, but I want to replace budgie with > >>>>>>>> enlightenment, because that's what I always use on linux. > >>>>>>>> > >>>>>>>> I've compiled E 0.25 from git (using > >>>>>>>> https://github.com/batden/esteem), and it seemed to work fine. > >>>>>>>> Unfortunately, when I tested suspend+resume, I had a problem. The > >>>>>>>> desktop resumes, but only with minimal brightness, and then it > >>>>>>>> seems to freeze (no keyboard/mouse). I can ssh into the laptop, > >>>>>>>> and killing enlightenment sends me back to the lightdm login > >>>>>>>> prompt. > >>>>>>>> > >>>>>>>> dmesg has this: > >>>>>>>> > >>>>>>>> [11814.110778] PM: suspend exit > >>>>>>>> [11814.630838] NVRM: GPU at PCI:0000:01:00: > >>>>>>>> GPU-589fde69-1161-f26b-1773-e5bcda70d601 > >>>>>>>> [11814.630845] NVRM: Xid (PCI:0000:01:00): 13, pid=5525, Graphics > >>>>>>>> Exception: Shader Program Header 11 Error > >>>>>>>> [11814.630855] NVRM: Xid (PCI:0000:01:00): 13, pid=5525, Graphics > >>>>>>>> Exception: Shader Program Header 18 Error > >>>>>>>> [11814.630865] NVRM: Xid (PCI:0000:01:00): 13, pid=5525, Graphics > >>>>>>>> Exception: ESR 0x405840=0xa2040800 > >>>>>>>> [11814.630877] NVRM: Xid (PCI:0000:01:00): 13, pid=5525, Graphics > >>>>>>>> Exception: ESR 0x405848=0x80000000 > >>>>>>>> > >>>>>>>> The problem happens with both the sw and the opengl compositors. > >>>>>>>> > >>>>>>>> When I suspend from the lightdm prompt or from the budgie desktop, > >>>>>>>> resuming works fine. So it seems something is happening/not > >>>>>>>> happening with the nvidia card when the suspend is started from E. > >>>>>>>> > >>>>>>>> Anyone has any idea, how to debug this? > >>>>>>> i suspect it may have to do with vblank interrupts. the nvidia > >>>>>>> driver doesn't produce them anymore? a quick way to test this: > >>>>>>> > >>>>>>> touch ~/.ecore-no-vsync > >>>>>>> > >>>>>>> restart e then do your suspend/resume > >>>>>> > >>>>>> Thanks for your reply. Unfortunately the problem seems to be somewhere > >>>>>> else, as resuming still fails the same way. > >>>>>> Anything else to try? Could rebuilding E in debugging mode help? > >>>>> > >>>>> probably not - btw - those shader exceptions might have to do with it. > >>>>> evas caches binaries for shaders. rm -rf > >>>>> ~/.cache/evas_gl_common_caches/ - but beyond that the only thing left > >>>>> is your driver. those are its shaders it compiled. > >>>>> > >>>>> google for it: "Graphics Exception: Shader Program Header 11 Error" > >>>>> > >>>>> seems to actually be OS independent and happen on windows too. > >>>>> > >>>>> https://forums.developer.nvidia.com/t/screen-system-is-dead-on-resume-unable-to-resume-with-all-current-drivers/29872/57?page=3 > >>>>> > >>>>> this has been there for a long time... and it seems it doesn't get > >>>>> resolved. > >>>>> > >>>>> https://github.com/Bumblebee-Project/Bumblebee/issues/739 > >>>> > >>>> Yeah, I've tried googling for this too, but found no solutions either. > >>>> > >>>>> it could be that evas uses egl+gles and the nvidia driver > >>>>> implementation for egl+gles is buggy - you can rebuild efl to use full > >>>>> desktop opengl+glx (-Dopengl=full). > >>>> > >>>> I've deleted the evas cache, and set the compositor to SW to make sure > >>>> that it's not an evas egl problem. The exceptions are still there. > >>>> Actually there are 3 exceptions for the kernel thread > >>>> "[irq/92-nvidia]", and 1 for Xorg. When the compositor was set to > >>>> opengl there were more exceptions, and one of them is was for the > >>>> enlightenment process. > >>>> > >>>> So my guess is, that this may not be a problem in E, but maybe a > >>>> missing/extra step during suspend/resume. I'll look into this > >>>> tomorrow. > >>>> > >>>> Thanks for your help, Laszlo > >>> > >>> hmm i wonder why the nvidia driver is complaining - something is using a > >>> shader program of some sot and it's not happy at all. there i something > >>> deeper going on here. but yes - with e using opengl for compositing it'll > >>> be driving the gpu (via opengl) and thus more chance of something going > >>> wrong. > >> > >> I've found another strange thing. In my original configuration I used > >> amdgpu+nvidia X drivers. Now I switched to modesetting+nvidia. > >> Resuming fails again, but there is a different new problem. After > >> starting E from lightdm as usual, I press ctrl+alt+end to restart E, > >> it fades to black as usual, then it switches to something that looks > >> like a console (empty black screen with a cursor line) and stays > >> there. I can not restore the desktop until I kill E. No exceptions > >> from nvidia in the dmesg this time. Any idea for this? > > > > so this is an optimus setup of some sort but now with amd + nvidia... i > > might > > imagine something goes wrong setting up randr maybe? simotek found his > > optimus > > setup required a forced refresh of randr info ... and e has that in it > > (otherwise edid info would not be populated right). check ~/.e-log.log - it > > will tell you what e is doing randr-wise and what it sees, but you should > > end > > up with some kind of screen. perhaps go back away from modesetting to > > amdgpu + > > nvidia? > > > > > > > _______________________________________________ > enlightenment-users mailing list > enlightenment-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-users _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
