Fedora 29 Successes and not so much

Post Reply
DaleChatham
Posts: 8
Joined: Fri Feb 22, 2019 9:35 pm
languages_spoken: english
ODROIDs: 2 * Odroid-H2
Has thanked: 0
Been thanked: 0
Contact:

Fedora 29 Successes and not so much

Unread post by DaleChatham » Sun Feb 24, 2019 10:44 am

First the good news. Fedora 29 installs and runs. Virtual manager works and I managed to install Windows 10 in a virtual machine running on Fedora.

Now, the problem. The system boots on a 4K monitor (television, actually) in 4k mode. All goes well until Fedora kicks on X11, then it's stuck at 1080p.

I played around with X configuration a bit, but no joy. What X drivers does it use? Apparently Ubuntu runs at 4k UHD mode?

Any ideas?

I ***REALLY*** do not want to go to Ubuntu.

[dale@odroid-h2-02 libvirt]$ cvt 3840 2160 30
# 3840x2160 29.98 Hz (CVT) hsync: 65.96 kHz; pclk: 338.75 MHz
Modeline "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync

[dale@odroid-h2-02 libvirt]$ xrandr --newmode "3840x2160_30.00" 338.75 3840 4080 4488 5136 2160 2163 2168 2200 -hsync +vsync
X Error of failed request: BadName (named color or font does not exist)
Major opcode of failed request: 139 (RANDR)
Minor opcode of failed request: 16 (RRCreateMode)
Serial number of failed request: 18
Current serial number in output stream: 18

xrandr --addmode XWAYLAND0 3840x2160_30.00

[dale@odroid-h2-02 libvirt]$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
XWAYLAND0 connected (normal left inverted right x axis y axis)
1920x1080 59.96 +
3840x2160_30.00 29.98

[dale@odroid-h2-02 libvirt]$ xrandr --output XWAYLAND0 --mode 3840x2160_30.00
xrandr: Configure crtc 0 failed




Thanks,

Dale

crashoverride
Posts: 4459
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 52 times
Contact:

Re: Fedora 29 Successes and not so much

Unread post by crashoverride » Mon Feb 25, 2019 1:14 am

DaleChatham wrote:
Sun Feb 24, 2019 10:44 am
What X drivers does it use?
Ubuntu uses the "modesetting" X11 driver (xserver-xorg-video-modesetting) by default. An Intel specific X11 driver (xserver-xorg-video-intel) is also available, but it lacks DRI3 (wont work with Vulkan) and is unstable (produces garbage after a period of time) in my testing on J4105.
DaleChatham wrote:
Sun Feb 24, 2019 10:44 am
xrandr --output XWAYLAND0 --mode 3840x2160_30.00
I appears that X11 emulation under Wayland is being used. X11 drivers are not applicable to this.

DaleChatham
Posts: 8
Joined: Fri Feb 22, 2019 9:35 pm
languages_spoken: english
ODROIDs: 2 * Odroid-H2
Has thanked: 0
Been thanked: 0
Contact:

Re: Fedora 29 Successes and not so much

Unread post by DaleChatham » Mon Feb 25, 2019 1:15 am

Is it possible that the reply from the moniter regarding its caoabilities is being mishandled? This OS/monitor combination is working on an Asus AMD motherboard.

User avatar
memeka
Posts: 4313
Joined: Mon May 20, 2013 10:22 am
languages_spoken: english
ODROIDs: XU rev2 + eMMC + UART
U3 + eMMC + IO Shield + UART
Has thanked: 0
Been thanked: 12 times
Contact:

Re: Fedora 29 Successes and not so much

Unread post by memeka » Mon Feb 25, 2019 1:30 am

Fedora uses wayland not X11.
Xrandr is for X11 not wayland so it won’t do anything for you in fedora.
Can you run X11 in fedora?

crashoverride
Posts: 4459
Joined: Tue Dec 30, 2014 8:42 pm
languages_spoken: english
ODROIDs: C1
Has thanked: 0
Been thanked: 52 times
Contact:

Re: Fedora 29 Successes and not so much

Unread post by crashoverride » Mon Feb 25, 2019 1:33 am

I don't use Fedora or Wayland so I am not able to offer much advice. If the monitor works in 4K with Ubuntu, then the same information (EDID) is available to Wayland. Both use the Linux KMS/DRM drivers. Make sure Fedora is not overriding the EDID or disabling KMS in the kernel command line.

DaleChatham
Posts: 8
Joined: Fri Feb 22, 2019 9:35 pm
languages_spoken: english
ODROIDs: 2 * Odroid-H2
Has thanked: 0
Been thanked: 0
Contact:

Re: Fedora 29 Successes and not so much

Unread post by DaleChatham » Mon Feb 25, 2019 7:33 am

I am seeing problems with Fedora 29, centOS 7 and Ubuntu. All work with same install media, same monitor, but Asus motherboard. This probably needs to be moved to problems since it is not OS specific.

DaleChatham
Posts: 8
Joined: Fri Feb 22, 2019 9:35 pm
languages_spoken: english
ODROIDs: 2 * Odroid-H2
Has thanked: 0
Been thanked: 0
Contact:

Re: Fedora 29 Successes and not so much

Unread post by DaleChatham » Mon Feb 25, 2019 7:55 am

The other motherboards have nvidia chipsets, and nvidia supposedly overrides some defaults automatically.



It appears this may be what is going on:

f you run X with -logverbose 6 you can get a lot of details about what is going on. I remember the mode was being rejected because the max pixelclock of HDMI is still only being detected as 165 Mhz by the driver (when it should be like 340Mhz). That modeline your running is 307 Mhz well above the 165. The default 3840x2160 modes (24, 25, 30 Hz) are all around 297 Mhz which again is well over 165 Mhz. The mode validation over-ride stuff is in nvidia's documentation but I have been running 4k monitors since 2005 even using custom modelines (like 2560x1920 on a 22 inch CRT) since like 2000-ish so nothing new to me here.You

You can generate modelines with cvt but in the case of the 31Hz mode I just pulled the 30hz one from EDID and calculated how much more bandwidth would be needed to go from 30 Hz -> 31 Hz.

DaleChatham
Posts: 8
Joined: Fri Feb 22, 2019 9:35 pm
languages_spoken: english
ODROIDs: 2 * Odroid-H2
Has thanked: 0
Been thanked: 0
Contact:

Re: Fedora 29 Successes and not so much

Unread post by DaleChatham » Mon Feb 25, 2019 8:54 am

Solved.

Dot clock > 300MHz is kicked out. I set the res to 3840x2160 at 26Hz. and it is working.

Without the OS, 30Hz works just fine.

Odd....

DaleChatham
Posts: 8
Joined: Fri Feb 22, 2019 9:35 pm
languages_spoken: english
ODROIDs: 2 * Odroid-H2
Has thanked: 0
Been thanked: 0
Contact:

Re: Fedora 29 Successes and not so much

Unread post by DaleChatham » Mon Feb 25, 2019 9:58 pm

This appears not to be an Odroid problem.

When Linux boots, it queries the monitor for its capabilities and creates a list of them It then defaults (apparently) to the highest possible resolution.

The Seiki monitor apparently produces a string the drivers don't know how to parse correctly and it assumes the highest dot clock frequency is something like 150MHz.

This can be overridden with a series of xrandr commands, which will put the display in 4K mode. This command can be run after login and the display resolution will change.

The good news is that I'm planning on using these with Visio monitors, so perhaps this will become a non-problem.

Post Reply

Return to “Other OS”

Who is online

Users browsing this forum: No registered users and 1 guest