All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 81363] [NV84] Black screen after UDEV is intialized
Date: Sat, 19 Dec 2015 00:58:37 +0000	[thread overview]
Message-ID: <bug-81363-8800-xcuqGNoLD2@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-81363-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


[-- Attachment #1.1: Type: text/plain, Size: 772 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=81363

--- Comment #11 from Jeff <jrsx13-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
This is still not working on Kernel 4.2. But during this test I had the laptop
connected to a DVI output. And the DVI output worked great. So it seems this is
not working for the LVDS only, which has the black light on but remains
blank/black.

I noticed on a Google search that there had been blank screen issues on
pre-nv50 drivers: http://patchwork.ozlabs.org/patch/215168/

I wonder if this is something that exists on my card as well. I was glad to see
the display working on the DVI output, but I am hoping to have this working on
LVDS at some point.

Thanks

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

[-- Attachment #1.2: Type: text/html, Size: 1543 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2015-12-19  0:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-14 22:42 [Bug 81363] New: Black screen after UDEV is intialized bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-81363-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-07-14 22:43   ` [Bug 81363] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-14 22:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-14 22:51   ` [Bug 81363] [NV84] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15  0:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-15 23:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-07-16  0:00   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-01-02  2:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-19  0:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2015-12-19 18:49   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-12-20  3:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-81363-8800-xcuqGNoLD2@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.