Summary: | x11/nvidia-driver: after update to 367.35, resume (after suspend-to-RAM) fails to re-initialize display | ||
---|---|---|---|
Product: | Ports & Packages | Reporter: | david |
Component: | Individual Port(s) | Assignee: | Alexey Dokuchaev <danfe> |
Status: | Closed FIXED | ||
Severity: | Affects Only Me | CC: | blachste, ekurzinger, w.schwarzenfeld |
Priority: | --- | Flags: | bugzilla:
maintainer-feedback?
(danfe) |
Version: | Latest | ||
Hardware: | amd64 | ||
OS: | Any |
Description
david
2016-08-30 16:14:55 UTC
I just tried downgrading to x11/nvidia-driver-340; that seems to work (including suspend/resume), at least under stable/11. Just FYI, removing driver "device VESA" (included in GENERIC) from the kernel config, switching to sc console and building + installing the new kernel solved the problem for me. A few weeks ago -- when I started running stable/11 for more than merely smoke-testing, and I thus needed to be able to suspend & resume -- I appended the line: kern.vty="sc" to /boot/loader.conf, and that got suspend/resume working for me (both for stable/11 and head; stable/10 didn't need it). This was while running x11/nvidia-driver-346.96. I have (of course) left that specification in while I attempted to use x11/nvidia-driver-367.35. So while it's good to note that switching from vt to sc while running nvidia-driver-367.35 works for some, it does not work for all... even in configurations where nvidia-driver-346.96 worked (and -340.96 works). Maintainer feedback? (Resp. is this still relevant?), I think https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237050 should resolve this, if anyone wants to double check. Thank you; I was able to go back to x11/nvidia-driver (nvidia-driver-390.87_3, as of this writing) yesterday, and suspend/resume works fine (in stable/11, stable/12, and head). I did need to (also) load nvidia-modeset.ko (as expected). I believe that this bug report may be closed. |