From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 101782] New: GTX1050TI (GP107 / NV137): HDMI output not working
Date: Thu, 13 Jul 2017 13:08:07 +0000 [thread overview]
Message-ID: <bug-101782-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1217 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=101782
Bug ID: 101782
Summary: GTX1050TI (GP107 / NV137): HDMI output not working
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 132664
--> https://bugs.freedesktop.org/attachment.cgi?id=132664&action=edit
log_attaching_detaching
The same hardware as for https://bugs.freedesktop.org/show_bug.cgi?id=101764
When the HDMI cable is connected there is no signal for the external monitor
and the internal panel keeps working as expected.
The journal when the cable is attached and then detached is attached to this
ticket. What's interesting to me is:
gdm-Xorg-:0[551]: (EE) NOUVEAU(G0): failed to set mode: No space left on device
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2810 bytes --]
[-- Attachment #2: Type: text/plain, Size: 154 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2017-07-13 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-13 13:08 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-101782-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-07-13 13:08 ` [Bug 101782] GTX1050TI (GP107 / NV137): HDMI output not working bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-13 13:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-13 13:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-08 17:36 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-08 17:40 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-08-08 20:26 ` 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-101782-8800@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.