From: Dan Espen <dan1espen-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: nouveau <nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: 640x480 does not fill screen
Date: Sat, 16 Feb 2019 12:48:56 -0500 [thread overview]
Message-ID: <icbm3btyif.fsf@home.home> (raw)
In-Reply-To: <ic8sys5x67.fsf-ZbdcMXxcd5KzQB+pC5nmwQ@public.gmane.org> (Dan Espen's message of "Wed, 06 Feb 2019 18:12:16 -0500")
Dan Espen <dan1espen@gmail.com> writes:
> Ilia Mirkin <imirkin@alum.mit.edu> writes:
>
>> On Wed, Feb 6, 2019 at 3:28 PM Dan Espen <dan1espen@gmail.com> wrote:
>>>
>>> Ilia Mirkin <imirkin@alum.mit.edu> writes:
>>>
>>> > It would be useful to know how the screen is connected. Also please
>>> > grab the monitor's EDID from /sys/class/drm/cardN-connector/edid and
>>> > attach it here. It would also be interesting to get a boot with
>>> > "drm.debug=0x1e nouveau.debug=disp=trace" which has the modeswitch in
>>> > question.
>>>
>>> The screen is connected using the MDP port.
>>> I don't find any cardN-connector directory,
>>> the closest match is:
>>>
>>> /sys/class/drm/card0-DP-1/edid
>>
>> N = 0
>> connector = DP-1
>>
>> so looks like you found it.
>>
>> I was actually looking for dmesg with those boot parameters, not the Xorg log.
>>
>> Something to randomly try -- xrandr -s 640x480 -r 75 -- perhaps it'll
>> like that mode better.
>
> Using "-r 75" fixes the problem.
>
>> Also does 720x480 work better?
>
> Yes, 720x480 works without the -r parameter.
>
>> Looking at your EDID, you have:
>>
>> Established timings supported:
>> 720x400@70Hz 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz
>> 640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
>> 640x480@75Hz 4:3 HorFreq: 37500 Hz Clock: 31.500 MHz
>> 800x600@60Hz 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz
>> 800x600@75Hz 4:3 HorFreq: 46900 Hz Clock: 49.500 MHz
>> 1024x768@60Hz 4:3 HorFreq: 48400 Hz Clock: 65.000 MHz
>> 1024x768@75Hz 4:3 HorFreq: 60000 Hz Clock: 78.750 MHz
>> 1280x1024@75Hz 5:4 HorFreq: 80000 Hz Clock: 135.000 MHz
>> Standard timings supported:
>> 1920x1080@60Hz 16:9
>> 1600x1200@60Hz 4:3 HorFreq: 75000 Hz Clock: 162.000 MHz
>> 1280x1024@60Hz 5:4 HorFreq: 64000 Hz Clock: 108.000 MHz
>> 1280x800@60Hz 16:10
>> 1152x864@75Hz 4:3 HorFreq: 67500 Hz Clock: 108.000 MHz
>>
>> CTA extension block
>> Extension version: 3
>> 25 bytes of CTA data
>> Video data block
>> ...
>> VIC 3 720x480@60Hz 16:9 HorFreq: 31469 Hz Clock: 27.000 MHz
>> VIC 2 720x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 27.000 MHz
>> VIC 1 640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
>
> Okay, if I read all that right the EDID supports 640x480 at 60 and 75hz.
> The monitor acts strangely at 60hz but is okay at 75hz.
> Is this something I should configure or can nouveau figure out the best mode?
Okay, looks like I'm moving back to the Nvidia proprietary drivers until
at least this issue is fixed.
So, I'd like to file a bug report but I tried here:
https://bugs.freedesktop.org/enter_bug.cgi
and my mailing list userid/password don't work there.
So, could someone give me guidance on filing the bug report or file one
on my behalf?
It looks like the issue is, when switching modes, if there are multiple
matches on the resolution, Nouveau should pick the mode with the
highest frequency.
--
Dan Espen
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau
next prev parent reply other threads:[~2019-02-16 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 16:31 640x480 does not fill screen Dan Espen
[not found] ` <icmun8j2to.fsf-ZbdcMXxcd5KzQB+pC5nmwQ@public.gmane.org>
2019-02-06 17:02 ` Ilia Mirkin
2019-02-06 20:28 ` Dan Espen
[not found] ` <ico97o64rq.fsf-ZbdcMXxcd5KzQB+pC5nmwQ@public.gmane.org>
2019-02-06 22:23 ` Ilia Mirkin
2019-02-06 23:12 ` Dan Espen
[not found] ` <ic8sys5x67.fsf-ZbdcMXxcd5KzQB+pC5nmwQ@public.gmane.org>
2019-02-16 17:48 ` Dan Espen [this message]
[not found] ` <icbm3btyif.fsf-ZbdcMXxcd5KzQB+pC5nmwQ@public.gmane.org>
2019-02-16 18:18 ` Ilia Mirkin
[not found] ` <CAKb7UvjSoyNctS=jWQ2FJbV=_B6umZjCNt2UsnUG_A=dcXYTgQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-02-16 19:20 ` Dan Espen
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=icbm3btyif.fsf@home.home \
--to=dan1espen-re5jqeeqqe8avxtiumwx3w@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.