Date: Mon, 04 Dec 2017 22:54:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 224069] (Fix included) Use of uninitalized register value in vesa.ko, causing X, text console and suspend/resume to fail Message-ID: <bug-224069-8-H5F4GJ3g3L@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-224069-8@https.bugs.freebsd.org/bugzilla/> References: <bug-224069-8@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D224069 --- Comment #10 from Stefan B. <sblachmann@gmail.com> --- (In reply to Jung-uk Kim from comment #9) > We can add few knobs in the driver to work around these issues=20 > and turn them on by default if NVIDIA controller is found. That would be the right thing to do then. Would save a lot of bad UX. And the supporting guys on the forums would be happy if these constantly recurring nvidia problems would be mitigated (at least to a degree). It's not nice to see people going back to Linux just because the text conso= le is unusable etc. > The root cause is NVIDIA does not really support VESA BIOS re-POST=20 > and save/restore state calls. It just checks few bits and returns=20 > immediately if they are set/clear. Aww. Didn't know that. You did obviously a lot of research. Kudos! This is a very bad thing to learn, as this could make STD with Nvidia cards virtually impossible without involving X. (Btw, do you know whether ATI cards behave better in this regard, supporting state saving/restoring?) --=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-224069-8-H5F4GJ3g3L>