Date: Tue, 30 Aug 2016 16:14:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 212262] x11/nvidia-driver: after update to 367.35, resume (after suspend-to-RAM) fails to re-initialize display Message-ID: <bug-212262-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212262 Bug ID: 212262 Summary: x11/nvidia-driver: after update to 367.35, resume (after suspend-to-RAM) fails to re-initialize display Product: Ports & Packages Version: Latest Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: danfe@FreeBSD.org Reporter: david@catwhisker.org Assignee: danfe@FreeBSD.org Flags: maintainer-feedback?(danfe@FreeBSD.org) Prior to 367.35, I had (most recently) been running 346.96 -- and resume worked. This was under stable/10, stable/11, and head (all amd64 -- all the same physical hardware; different slices of boot drive). I realize that not everyone needs suspend/resume to work, but the machine in question is my laptop, and I carry it in my backpack as I cycle between home and the shuttle stop (as part of my commute to & from work). Having the la= ptop "on" and cooking itself in the backpack isn't a reasonable option, and powe= ring it off is ... well, a regression, at best. Might it be worthwhile to create an x11/nvidia-driver-346, pending a fix for the newer version of the driver? (I have verbose dmesg.boot for the above 3 versions of the OS available, as well as a fair amount of other info, should that be wanted. And I'm happy = to test.) --=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-212262-13>