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

[bugzilla-noreply at freebsd.org]

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

--- Comment #12 from Tony Narlock <tony at git-pull.com> ---
(In reply to Andy Ritger from comment #11)

VP2770-LED monitor, via Displayport

NVIDIA-FreeBSD-x86_64-355.11 is what I'm using. Note I did have to go in
manually and edit nv-freebsd.h to support this:

./nv-freebsd.h:25:2: error: This driver does not support FreeBSD 11.x/-CURRENT!

$ freebsd-version -ku; uname -apKU
11.0-CURRENT
11.0-CURRENT
FreeBSD z600 11.0-CURRENT FreeBSD 11.0-CURRENT #24: Mon Sep 28 15:30:02 CDT
2015     root at z600:/usr/obj/usr/src/sys/MYKERNEL  amd64 amd64 1100079 1100079

> * 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)

No signal sign.  Amber light on power button.

Then blue when I switch back to X.

Attaching dumps after this post.

Probably unrelated, bug #203456: packaging requesting to overwrite manually
installed nvidia-driver with packaged version (nvidia-driver-340).  I'm
confident 350.11 is installed, but actively trying to rule out and off chance
libraries left over from an uninstalled nvidia-driver could be interfering.

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