Date: Fri, 15 Sep 2023 05:26:01 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 273812] x11/nvidia-driver: screen off after wake up from suspend to RAM Message-ID: <bug-273812-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D273812 Bug ID: 273812 Summary: x11/nvidia-driver: screen off after wake up from suspend to RAM Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: danfe@FreeBSD.org Reporter: fuz@FreeBSD.org Flags: maintainer-feedback?(danfe@FreeBSD.org) Assignee: danfe@FreeBSD.org I have recently upgraded my laptop from an old Kepler-class card that requi= red nvidia-driver-340 to function to a slightly less old nvidia Quadro M2200 us= ing x11/nvidia-driver and x11/nvidia-drm-kmod. I have current packages from 20= 23Q3 installed. Unfortunately I now have the issue that when I suspend the system and wake = it back up, the screen stays black. If I load nvidia-drm late in the boot pro= cess (after nvidia-modeset), the system console shows garbage and switching cons= oles back and forth makes the X server visible again (though some windows are fi= lled with garbage). If I load nvidia-drm in loader.conf, the screen simply stays black. The only way to fix this is to blindly open a console and then to s= tart another X server. Then, this new X server works, but switching to the old X server or the system console turns the screen off again. Any idea what the problem might be? My description of the various symptoms= may be slightly imprecise. I recall there was one configuration in which the screen seemingly turned back on on its own after a while, but I wasn't able= to get back to it. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-273812-7788>