From: Nick Bowler <nbowler@elliptictech.com>
To: Ben Skeggs <skeggsb@gmail.com>
Cc: Martin Peres <martin.peres@labri.fr>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel@lists.freedesktop.org
Subject: Re: Linux 3.4-rc4
Date: Fri, 27 Apr 2012 20:39:28 -0400 [thread overview]
Message-ID: <20120428003928.GA16805@elliptictech.com> (raw)
In-Reply-To: <1335504021.5311.0.camel@nisroch>
Hi Ben,
On 2012-04-27 15:20 +1000, Ben Skeggs wrote:
> Does this patch help you at all?
>
> http://cgit.freedesktop.org/nouveau/linux-2.6/commit/?id=a3a285f17867f0018de798b5ee85731ec1268305
Yes. I cherry-picked this patch on top of Linus' master (3.4-rc4+) and
this appears to solve the "black screen on VGA" problem described in the
original report. Thanks!
Unfortunately, that's not the end of my VGA-related regressions. :(
While tracking down the black screen issue, I've been having the monitor
directly connected to the video card the whole time, but now when I'm
connected through my KVM switch (an IOGear GCS1804), it appears that
something's going wrong with reading the EDID, because the available
modes are all screwed up (both console and X decide they want to drive
the display at 1024x768). Here's the output of xrandr on 3.2.15:
% xrandr
Screen 1: minimum 320 x 200, current 1600 x 1200, maximum 4096 x 4096
VGA-1 connected 1600x1200+0+0 (normal left inverted right x axis y axis) 352mm x 264mm
1600x1200 75.0*+ 70.0 65.0 60.0
1280x1024 85.0 + 75.0 60.0
1920x1440 60.0
1856x1392 60.0
1792x1344 60.0
1920x1200 74.9 59.9
1680x1050 84.9 74.9 60.0
1400x1050 85.0 74.9 60.0
1440x900 84.8 75.0 59.9
1280x960 85.0 60.0
1360x768 60.0
1280x800 84.9 74.9 59.8
1152x864 75.0
1280x768 84.8 74.9 59.9
1024x768 85.0 75.1 75.0 70.1 60.0 43.5 43.5
832x624 74.6
800x600 85.1 72.2 75.0 60.3 56.2
848x480 60.0
640x480 85.0 75.0 72.8 72.8 66.7 60.0 59.9
720x400 85.0 87.8 70.1
640x400 85.1
640x350 85.1
320x200 165.1
And on 3.4-rc4+ (with your patch cherry-picked):
% xrandr
Screen 1: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096
VGA-1 connected 1024x768+0+0 (normal left inverted right x axis y axis) 0mm x 0mm
1024x768 60.0*
800x600 60.3 56.2
848x480 60.0
640x480 59.9
320x200 165.1
Running xrandr on 3.4-rc4+ also causes the screen to go black for a
second when it does not on 3.2.15. It also causes several messages of
the form
[drm] nouveau 0000:01:00.0: Load detected on output B
to be logged. Also, looking at /sys/class/drm/card0-VGA-1/edid I see
that it is empty on 3.4-rc4+ and it is correct on 3.2.15. Things seem
to work OK when the KVM is not involved.
This is probably caused by a different commit than the black screen
because I also saw this problem on the 3.3.3+reverts kernel; I just
haven't noticed it until now because, well, the VGA wasn't working at
all until now.
Anyway, I can try to track down what causes this one next week...
Thanks,
--
Nick Bowler, Elliptic Technologies (http://www.elliptictech.com/)
next prev parent reply other threads:[~2012-04-28 0:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-21 22:43 Linux 3.4-rc4 Linus Torvalds
2012-04-22 4:07 ` Nick Bowler
2012-04-22 4:51 ` Linus Torvalds
2012-04-22 7:26 ` Dave Airlie
2012-04-22 16:42 ` Nick Bowler
2012-04-23 3:16 ` Ben Skeggs
2012-04-22 16:40 ` Nick Bowler
2012-04-22 18:20 ` Geert Uytterhoeven
2012-04-23 0:05 ` Nick Bowler
2012-04-23 2:45 ` Konrad Rzeszutek Wilk
2012-04-24 1:03 ` Nick Bowler
2012-04-24 15:11 ` Konrad Rzeszutek Wilk
2012-04-25 1:35 ` Nick Bowler
2012-04-25 2:56 ` Ben Skeggs
2012-04-27 5:20 ` Ben Skeggs
2012-04-28 0:39 ` Nick Bowler [this message]
2012-04-28 6:19 ` Alex Deucher
2012-04-28 15:33 ` Nick Bowler
2012-04-29 22:37 ` Dmitry Torokhov
2012-04-30 9:07 ` Maarten Maathuis
2012-04-30 11:01 ` Luca Tettamanti
2012-05-02 7:54 ` Jean Delvare
2012-05-02 11:31 ` Ben Skeggs
2012-05-04 5:08 ` Ben Skeggs
2012-05-04 14:12 ` Jean Delvare
2012-05-01 13:23 ` Nick Bowler
2012-05-01 15:09 ` Alan Cox
2012-05-01 15:31 ` Nick Bowler
2012-05-01 15:45 ` Alan Cox
2012-05-02 1:20 ` Nick Bowler
2012-05-04 9:20 ` Dave Airlie
2012-05-05 15:39 ` Nick Bowler
2012-04-22 8:38 ` Bjarke Istrup Pedersen
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=20120428003928.GA16805@elliptictech.com \
--to=nbowler@elliptictech.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.peres@labri.fr \
--cc=skeggsb@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).