From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 27455] New: dualhead not working, second display always black
Date: Sun, 4 Apr 2010 21:33:37 -0700 (PDT) [thread overview]
Message-ID: <bug-27455-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=27455
Summary: dualhead not working, second display always black
Product: xorg
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: tcwardrobe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=34667)
--> (https://bugs.freedesktop.org/attachment.cgi?id=34667)
output of dmesg
Regardless of connected before booting or after, second display turns black as
soon as nouveau.ko is loaded (but it switches from standby to on when it
should). xrandr -q recognizes the second display correctly, xrandr --output
VGA-1 --auto == display on but black.
A sidenote, while watching a clip with mplayer and going fullscreen, the second
display switches from on to standby and on again every several seconds (between
10 and 30 seconds).
See dmesg attached.
ii libdrm-nouveau1 2.4.18-4
Userspace interface to nouveau-specific kernel DRM services -- runtime
ii libdrm2 2.4.18-4
Userspace interface to kernel DRM services -- runtime
ii xserver-xorg-video-nouveau 1:0.0.15+git20100329+7858345-1
X.Org X server -- Nouveau display driver (experimental)
Debian sid/experimental, kernel 2.6.32 (backported drm from 2.6.33)
01:00.0 VGA compatible controller [0300]: nVidia Corporation NV34M [GeForce FX
Go5200 32M/64M] [10de:0328] (rev a1)
regards
Michael
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2010-04-05 4:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-05 4:33 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-27455-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-04-05 12:38 ` [Bug 27455] dualhead not working, second display always black bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-05 13:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-05 13:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-05 13:58 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-05 15:50 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2010-04-12 14:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-01-05 11:23 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-07 13:05 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-07 19:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-07 22:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-18 13:55 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-06-18 20:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-08-30 6:56 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-08 22:17 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-08 23:09 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-12-09 15:33 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 16:40 ` 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-27455-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.