All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neil Mayhew <neil_mayhew-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
To: amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: 21:9 monitor resolution incorrect since 4.14 kernel
Date: Tue, 29 Oct 2019 16:01:29 -0600	[thread overview]
Message-ID: <32e595a2-fdc1-7b13-2e33-c2b8752c60f2@users.sourceforge.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2933 bytes --]

I have a 21:9 ultrawide monitor connected to an RX 570 with the amdgpu
driver. I'm still using the 4.14 kernel since with later kernels I can't
get the driver to allow use of the full resolution of 2560x1080 and I'm
limited to regular HD, ie 1920x1080. The latest kernel I've tried is
5.4-rc2. My distro is NixOS unstable-small. I have two other monitors
(16:9 and 16:10) connected to the same graphics card.

Is there anything I can do to work around this or try to fix it? I had a
look at the driver sources but couldn't find where the mode is set. I'm
happy to try things if someone can point me in the right direction, even
if it's just to gather better info for a bug report. Using such an old
kernel is becoming really inconvenient.

Some additional info about the situation on 4.14 that may or may not help:

1. The resolution is limited with Wayland but not with X11

2. When the system boots up the resolution is square and the image is
squished horizontally with many columns dropped, both during the boot
process and at the gdm login screen. It's not until after I log with X11
that the resolution is set correctly.

3. The output of xrandr --props is below.

TIA for any help.

--Neil

Screen 0: minimum 320 x 200, current 6160 x 1080, maximum 16384 x 16384
DP-1 connected primary 2560x1080+1920+0 (normal left inverted right x
axis y axis) 798mm x 334mm
    _MUTTER_PRESENTATION_OUTPUT: 0
    EDID:
        00ffffffffffff001e6df9765de80500
        091c010380502278eaca95a6554ea126
        0f5054256b807140818081c0a9c0b300
        d1c08100d1cfcd4600a0a0381f403020
        3a001e4e3100001a003a801871382d40
        582c4500132a2100001e000000fd0038
        4b1e5a18000a202020202020000000fc
        004c4720554c545241574944450a01b5
        02031af12309070747100403011f1312
        8301000065030c0010008c0ad08a20e0
        2d10103e96001e4e31000018295900a0
        a038274030203a001e4e3100001a0000
        00000000000000000000000000000000
        00000000000000000000000000000000
        0000000000ff003830394e544b464244
        3136350a0000000000000000000000a4
    dither: off
        supported: off, on
    audio: auto
        supported: off, on, auto
    scaling mode: None
        supported: None, Full, Center, Full aspect
    underscan vborder: 0
        range: (0, 128)
    underscan hborder: 0
        range: (0, 128)
    underscan: off
        supported: off, on, auto
    coherent: 1
        range: (0, 1)
    link-status: Good
        supported: Good, Bad
    CONNECTOR_ID: 48
        supported: 48
    non-desktop: 0
        supported: 0, 1
   2560x1080     59.98 +  74.99*
   1920x1080     74.99    59.96    50.00    59.99    59.94    59.93 
   1680x1050     59.95    59.88 

[etc.]

[-- Attachment #1.2: Type: text/html, Size: 3840 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Neil Mayhew <neil_mayhew@users.sourceforge.net>
To: amd-gfx@lists.freedesktop.org
Subject: 21:9 monitor resolution incorrect since 4.14 kernel
Date: Tue, 29 Oct 2019 16:01:29 -0600	[thread overview]
Message-ID: <32e595a2-fdc1-7b13-2e33-c2b8752c60f2@users.sourceforge.net> (raw)
Message-ID: <20191029220129.qt-ZKfJOEwV9GL9uhe5AYK2QT0nT3L3JYh-h0IG9pYs@z> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2933 bytes --]

I have a 21:9 ultrawide monitor connected to an RX 570 with the amdgpu
driver. I'm still using the 4.14 kernel since with later kernels I can't
get the driver to allow use of the full resolution of 2560x1080 and I'm
limited to regular HD, ie 1920x1080. The latest kernel I've tried is
5.4-rc2. My distro is NixOS unstable-small. I have two other monitors
(16:9 and 16:10) connected to the same graphics card.

Is there anything I can do to work around this or try to fix it? I had a
look at the driver sources but couldn't find where the mode is set. I'm
happy to try things if someone can point me in the right direction, even
if it's just to gather better info for a bug report. Using such an old
kernel is becoming really inconvenient.

Some additional info about the situation on 4.14 that may or may not help:

1. The resolution is limited with Wayland but not with X11

2. When the system boots up the resolution is square and the image is
squished horizontally with many columns dropped, both during the boot
process and at the gdm login screen. It's not until after I log with X11
that the resolution is set correctly.

3. The output of xrandr --props is below.

TIA for any help.

--Neil

Screen 0: minimum 320 x 200, current 6160 x 1080, maximum 16384 x 16384
DP-1 connected primary 2560x1080+1920+0 (normal left inverted right x
axis y axis) 798mm x 334mm
    _MUTTER_PRESENTATION_OUTPUT: 0
    EDID:
        00ffffffffffff001e6df9765de80500
        091c010380502278eaca95a6554ea126
        0f5054256b807140818081c0a9c0b300
        d1c08100d1cfcd4600a0a0381f403020
        3a001e4e3100001a003a801871382d40
        582c4500132a2100001e000000fd0038
        4b1e5a18000a202020202020000000fc
        004c4720554c545241574944450a01b5
        02031af12309070747100403011f1312
        8301000065030c0010008c0ad08a20e0
        2d10103e96001e4e31000018295900a0
        a038274030203a001e4e3100001a0000
        00000000000000000000000000000000
        00000000000000000000000000000000
        0000000000ff003830394e544b464244
        3136350a0000000000000000000000a4
    dither: off
        supported: off, on
    audio: auto
        supported: off, on, auto
    scaling mode: None
        supported: None, Full, Center, Full aspect
    underscan vborder: 0
        range: (0, 128)
    underscan hborder: 0
        range: (0, 128)
    underscan: off
        supported: off, on, auto
    coherent: 1
        range: (0, 1)
    link-status: Good
        supported: Good, Bad
    CONNECTOR_ID: 48
        supported: 48
    non-desktop: 0
        supported: 0, 1
   2560x1080     59.98 +  74.99*
   1920x1080     74.99    59.96    50.00    59.99    59.94    59.93 
   1680x1050     59.95    59.88 

[etc.]

[-- Attachment #1.2: Type: text/html, Size: 3840 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx

             reply	other threads:[~2019-10-29 22:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-29 22:01 Neil Mayhew [this message]
2019-10-29 22:01 ` 21:9 monitor resolution incorrect since 4.14 kernel Neil Mayhew
     [not found] ` <32e595a2-fdc1-7b13-2e33-c2b8752c60f2-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
2019-10-30 18:07   ` Neil Mayhew

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=32e595a2-fdc1-7b13-2e33-c2b8752c60f2@users.sourceforge.net \
    --to=neil_mayhew-rn4veauk+akrv+lv9mx5uipxlwaovq5f@public.gmane.org \
    --cc=amd-gfx-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.