[Bug 201461] switching back to sc(4) or vt(4) console fails with nvidia.ko

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Wed Sep 30 00:02:19 UTC 2015


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201461

--- Comment #11 from Andy Ritger <aritger at nvidia.com> ---
Hi Tony.

Restoring the text console can be fragile.  This is often sensitive to:

* The NVIDIA driver version.
* The particular graphics board you are using.
* How the monitor is connected to the graphics board (DVI, 15-pin VGA,
DisplayPort, etc).

Please be sure you have the latest version of the NVIDIA FreeBSD driver.
I think the latest right now is 355.11:

    http://www.nvidia.com/Download/driverResults.aspx/90397/en-us

If you can experiment with either different graphics boards or different
connectors between the monitor and the graphics board to attempt to
isolate which parameters repro or don't repro this bug, that would help.

A few other things:

* Does the monitor still have sync?  Most monitors have an LED (e.g., green
when active, amber when sync is lost, blank when powered off)  Distinguishing
between those will help to understand if restoring the text console is driving
modetimings that the monitor can't handle (monitor lost sync), or if something
about redrawing the console got broken (image on monitor is black, but monitor
is active and did not lose sync)
* The NVIDIA FreeBSD driver provides a script, nvidia-bug-report.sh, that will
gather various information about your GPU and system.  It would be helpful to
attach that to this bug.
* The NVIDIA FreeBSD driver includes a utility, nvidia-debugdump, which can
capture various GPU hw state.  Could you run `nvidia-debugdump -D` and attach
the file it produces?

Thanks.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-bugs mailing list