[SOLVED][KDE] Login Window (SDDM) Displays 1080p60; KDE Displays 1080i

General system Newbie
1

Hello! I’ve just installed Endeavour for the first time, after using Manjaro’s ARM XFCE distro quite a bit on my Pis. I’m enjoying it so far. :slight_smile:

I’m using an Intel SBC (Odroid H3+) with a Jasper Lake Pentium Silver N6005 with iGPU. This is a 2021 processor, so it’s modern and apparently very well supported by Intel’s open source drivers. The Intel drivers are installed and running according to inxi. I’m using KDE.

I have the Odroid hooked up to a display that shows the detected resolution and refresh rate when it first turns on, and every time it changes.

At the login screen (which is the default sddm display manager), it identifies a 1080p60 (progressive scan) signal, which is correct for this monitor.

Unfortunately, I’m noticing some color fringing on small text in KDE, which I suspect might actually be from my monitor trying to upscale the 1080i signal to 1080p (which it told me it’s doing).

On login, the screen blanks for a moment and when the desktop appears, it’s a 1080i60 (interlaced) signal.

The Display Settings control panel says it’s configured for 1080, 60 Hz, but clearly something’s off. I wonder if this is a driver issue, maybe?

I figure it must be drivers because this hardware is set up for dual-boot right now. Windows gives a 1080p60 signal as soon as it boots up and stays that way.

xrandr shows there is indeed a 1080i mode and a 1080 60Hz mode that isn’t labeled with an “i” (which I assume to be progressive scan mode?), but giving the command to switch from one to the other didn’t seem to do anything (xrandr -s ). Maybe I need to restart or something else–I’ve not had this problem before so I’m not quite sure how to go about fixing it.

I tried googling, but couldn’t find results with people stuck in interlaced mode at 1080. Since it works fine in Windows, I assume there’s some setting I need to tweak.

I’d appreciate any advice. Please let me know what additional troubleshooting info might be useful.

Thanks!

2

Try xrandr --verbose as per

3

Update: This appears to be a KDE-specific issue (maybe). I grabbed the live ISO, which boots up into XFCE, and it automatically selected 1080p 60Hz.

I’m not really sure what to make of this. I’m not skilled enough yet with Linux to really know how to diagnose what’s happening, and both XFCE and KDE appear to be using the same display drivers (i915, from the kernel, assuming inxi is correct).

@ricklinux , I just saw you reply as I’m typing this. I’ll consult that article and be back. :slight_smile:

1 Like
4

After figuring out how to work with firewalld enough to be able to ssh in to the machine so I can more easily copy text output, I’m back. :slight_smile:

It is indeed using a 1080i output mode:

1920x1080i (0x535) 74.250MHz +HSync +VSync Interlace *current
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.75KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  60.00Hz

So, that explains why that’s happening, at least. I’m less clear on how to fix it: there are a lot of 1080p modes to choose from, and I’ve never had to work with xrandr in verbose mode; I only vaguely understand a lot of that output, and don’t understand at all quite a bit of it. :stuck_out_tongue: I assume I should use the one marked “preferred,” but I’m just guessing there.

1920x1080 (0x47) 148.500MHz +HSync +VSync +preferred
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz

The device appears to be named DP1. That said, I’m not clear on how to select the CTRC. I think it’s currently set to CTRC 0, but there are also 1 and 2? I have no idea what CTRC is, so I’ll be googling it shortly.

All that said, assuming xrandr is actually giving me good advice re: its “preferred” selection, I think this is the command I want? I’m old enough to remember incorrect resolution/refresh rate settings ruining displays that didn’t have the good sense to turn themselves off when asked to do something ridiciulous, so I wanted to check before running it.

xrandr --output DP1 --mode 0x47 --crtc 0 --verbose

Here’s the whole verbose output, for reference:

~]$ cat xrandr.output 
Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767
DP1 connected primary 1920x1080+0+0 (0x535) normal (normal left inverted right x axis y axis) 360mm x 290mm
        Identifier: 0x42
        Timestamp:  24327
        Subpixel:   unknown
        Gamma:      1.0:1.0:1.0
        Brightness: 1.0
        Clones:     HDMI1
        CRTC:       0
        CRTCs:      0 1 2
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter: 
        EDID: 
                00ffffffffffff00068c0d1024000000
                1a14010388241d8cea9c209c544f8f26
                2152563fcf008180814090409500a940
                455961598199023a801871382d40582c
                4500c48e0000001ebc1b00a050201730
                3020360020200000001a7c2e90a0601a
                1e403020360020200000001a283c80a0
                70b023403020360020200000001a010e
                020325f24d901f041305140211061522
                2120e305030023090707830100006603
                0c00100038483f403062b02e4040c013
                0020200000001e023a80d072382d4010
                2c4580c48e0000001e011d007251d01e
                206e285500c48e0000001e011d00bc52
                d01e20b8285540c48e0000001e000000
                0000000000000000000000000000005c
        HDCP Content Type: HDCP Type0 
                supported: HDCP Type0, HDCP Type1
        Content Protection: Undesired 
                supported: Undesired, Desired, Enabled
        vrr_capable: 0 
                range: (0, 1)
        Colorspace: Default 
                supported: Default, RGB_Wide_Gamut_Fixed_Point, RGB_Wide_Gamut_Floating_Point, opRGB, DCI-P3_RGB_D65, BT2020_RGB, BT601_YCC, BT709_YCC, XVYCC_601, XVYCC_709, SYCC_601, opYCC_601, BT2020_CYCC, BT2020_YCC
        max bpc: 12 
                range: (6, 12)
        Broadcast RGB: Automatic 
                supported: Automatic, Full, Limited 16:235
        audio: auto 
                supported: force-dvi, off, auto, on
        subconnector: HDMI 
                supported: Unknown, VGA, DVI-D, HDMI, DP, Wireless, Native
        link-status: Good 
                supported: Good, Bad
        non-desktop: 0 
                range: (0, 1)
  1920x1080 (0x47) 148.500MHz +HSync +VSync +preferred
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.50KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  60.00Hz
  1920x1200 (0x532) 154.000MHz +HSync -VSync
        h: width  1920 start 1968 end 2000 total 2080 skew    0 clock  74.04KHz
        v: height 1200 start 1203 end 1209 total 1235           clock  59.95Hz
  1920x1080 (0x533) 148.500MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  56.25KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  50.00Hz
  1920x1080 (0x534) 148.352MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  67.43KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  59.94Hz
  1920x1080i (0x535) 74.250MHz +HSync +VSync Interlace *current
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.75KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  60.00Hz
  1920x1080i (0x536) 74.250MHz +HSync +VSync Interlace
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  28.12KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  50.00Hz
  1920x1080 (0x537) 74.250MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.75KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  30.00Hz
  1920x1080 (0x538) 74.250MHz +HSync +VSync
        h: width  1920 start 2448 end 2492 total 2640 skew    0 clock  28.12KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  25.00Hz
  1920x1080 (0x539) 74.250MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  27.00KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  24.00Hz
  1920x1080i (0x53a) 74.176MHz +HSync +VSync Interlace
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.72KHz
        v: height 1080 start 1084 end 1094 total 1125           clock  59.94Hz
  1920x1080 (0x53b) 74.176MHz +HSync +VSync
        h: width  1920 start 2008 end 2052 total 2200 skew    0 clock  33.72KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  29.97Hz
  1920x1080 (0x53c) 74.176MHz +HSync +VSync
        h: width  1920 start 2558 end 2602 total 2750 skew    0 clock  26.97KHz
        v: height 1080 start 1084 end 1089 total 1125           clock  23.98Hz
5

It’s hard to look at here scrolling. I think your command matches what they used. Are you going to try that?

6

I was waiting to see if you’d tell me the monitor would explode first, but, yes. :wink:

If this works, what’s the preferred way to make it permanent? I know I need to execute the command when the session starts, but I’m new enough to this that I’m always confused about which config file to muck with, especially as it seems to change with Linux flavor and/or DE.

I think .xprofile would be fine?

EDIT: That command worked. :slight_smile:

EDIT 2: It’s .xprofile, not .xsession. And putting it there did nothing. :frowning:

7

I’m not that experienced with xrandr. I would read the man pages for it and or the Arch wiki.

https://wiki.archlinux.org/title/xrandr#Adding_undetected_resolutions

Edit: Section 4.3 maybe?

8

I hate to say it, but I think that you’re right. I really, really hate messing with Xorg conf files, but I think I’m going to have to.

While it’s entirely possible and almost certain that I don’t know what I’m doing, putting the command in KDE’s autostart thing did nothing at all. Clearly I need to read the docs some more. Or just cave and mess with the Xorg config. :stuck_out_tongue:

Thanks for all your help. This was maddening.

9

Remember in settings startup and shutdown background services that kscreen is running It might overwrite the settings? (Kscreen2 screen management) :man_shrugging:

Edit: Did you get it working then?

10

Running the command manually fixes it. I’m going to try editing the Xorg conf. I’ve made sure I have ssh access so I can fix that when it inevitably breaks and locks me out of the GUI.

#SoConfident
#GoodAtXorg

:stuck_out_tongue:

I’d never even heard of Kscreen2 until you mentioned it (I’ve not used KDE in 10+ years), so I suppose I should look at that before screwing around with Xorg conf files. It wouldn’t surprise me if that’s the root of the issue, since this doesn’t happen in the live environment (XFCE).

11

@ricklinux honestly, at this point, I’m ready to blast out the entire KDE install and start over.

I’ve now spent hours messing around with the display settings to get progressive scan mode to work, when it worked automatically in XFCE. It’s also overriding automatic startup scripts and forcing me to do scary things in the Xorg config. :stuck_out_tongue: I also had to download additional drivers to get my trackpad to work right, which I didn’t have to do in the live environment.

The only reason I went with KDE was because I wanted to try the add-on that lets you switch in and out of a tiling window manager mode, but I’m getting too frustrated with something I haven’t even started using yet.

EDIT: If I’m going to be this confused about how the GUI works, I might as well just install i3 or Qtile and actually learn how to use it. :wink:

12

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.