[Bug 212262] x11/nvidia-driver: after update to 367.35, resume (after suspend-to-RAM) fails to re-initialize display
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Aug 30 16:14:56 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212262
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 at FreeBSD.org
Reporter: david at catwhisker.org
Assignee: danfe at FreeBSD.org
Flags: maintainer-feedback?(danfe at 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 laptop
"on" and cooking itself in the backpack isn't a reasonable option, and powering
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.)
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list