From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 91333] New: Connecting second of two monitors to a Lenovo W520 causes displays to go crazy
Date: Tue, 14 Jul 2015 01:46:55 +0000 [thread overview]
Message-ID: <bug-91333-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2096 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=91333
Bug ID: 91333
Summary: Connecting second of two monitors to a Lenovo W520
causes displays to go crazy
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Reporter: cjashfor-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created attachment 117104
--> https://bugs.freedesktop.org/attachment.cgi?id=117104&action=edit
dmesg output from start to connecting the two monitors, then disconnecting the
VGA monitor
I am using a Lenovo W520 on Fedora 22. What I'd like to be able to do is close
the laptop's display and use two external monitors.
I know that Optimus is troublesome in Linux, so I have disabled it, and am
using discrete graphics only (Nvidia Quadro 1000M, 108GLM).
When I plug in the first of the two external monitors via the Displayport
(converted to HDMI), everything works fine; I am able to use the laptop's
internal display and the external monitor.
When I plug in a second display via the VGA port, all of the screens go blank
for a time, and then only the Displayport-connected monitor comes up. It is
usable for about 10 seconds, and then the internal display shows some boot up
messages, and the displayport-connected monitor shows the desktop, but I cannot
type anything. About every three seconds, all screens blank out, and then the
process repeats.
My next step is to then disconnect the VGA monitor, and after about 10 seconds,
it puts me back at the Gnome desktop login. From there I was able to log back
in and get the dmesg output (attached).
Looking at the dmesg output, there is a segfault in libmutter. Perhaps this is
what is causing the problem. I don't know.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3594 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2015-07-14 1:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 1:46 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-91333-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2015-07-14 1:52 ` [Bug 91333] Connecting second of two monitors to a Lenovo W520 causes displays to go crazy bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 3:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 3:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 3:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 4:02 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 4:04 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 4:16 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 8:12 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 17:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-14 17:03 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15 0:44 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15 2:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15 2:00 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15 6:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-15 8:11 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-07-18 8:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 9:01 ` 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-91333-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.