Not getting 60 fps refresh on Armbian Stretch + Wayland

Post Reply
dqbydt
Posts: 40
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 XU4 VU5 VU7+
Has thanked: 0
Been thanked: 0
Contact:

Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by dqbydt » Sat Feb 23, 2019 8:50 am

What I'm actually looking for is GPU acceleration + vysnc under X. As mentioned in that post, I concluded from forum posts that this was only available out-of-the-box on Armbian + wayland. I built the default image for C2, and tried running weston via weston-launch from a console login. And indeed, the vsync issue appears to be fixed (no tearing seen if I drag windows around).

However, the refresh is definitely not 60 fps. (I am using the Hardkernel VU-7 Plus display). weston-info shows

Code: Select all

mode:
	width: 1024 px, height: 600 px, refresh: 43.066 Hz
Where is the 43.066 coming from? And it doesn't even seem to be that much; there is so much visible judder when I drag the windows that it seems like the refresh rate is half of the 43 indicated.

I tried to create a weston.ini as indicated here with a mode line derived from cvt, but that didn't change anything. How can I get 60 fps refresh with wayland?

User avatar
odroid
Site Admin
Posts: 32358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 146 times
Been thanked: 325 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by odroid » Sat Feb 23, 2019 9:53 am

What happens if you use a generic 1080p HDMI monitor?

dqbydt
Posts: 40
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 XU4 VU5 VU7+
Has thanked: 0
Been thanked: 0
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by dqbydt » Tue Feb 26, 2019 3:24 pm

I don't have a 1080p monitor, but I connected the C2 to a 4K display. The mode displayed by weston-info now is technically correct:

Code: Select all

mode:
	width: 3840 px, height: 2160 px, refresh: 60.000 Hz
	flags: current preferred
But there's just no way it is 60 Hz refresh. This is what it looks like when I drag a terminal window:
https://youtu.be/O0u-kFbLJWc
Note the judder on the edges of the window as I drag it back and forth. At 60 Hz refresh it should've been buttery smooth.

Unless -- the rendering of the window is not accelerated? That is, the display is indeed being refreshed at 60 Hz, but the rendering cannot be completed within 16.67 ms. The startup log on the terminal when I run weston-launch contains:

Code: Select all

Loading module '/usr/lib/aarch64-linux-gnu/libweston-1/drm-backend.so'
. . .
using /dev/dri/card0
Loading module '/usr/lib/aarch64-linux-gnu/libweston-1/gl-renderer.so'
gbm: failed to open any driver
gbm: Last dlopen error: /usr/lib/dri/meson-dri.so: cannot open shared object file: No such file or directory
failed to load driver: meson
. . .
GL renderer: Gallium 0.4 on llvmpipe
Per https://en.wikipedia.org/wiki/Mesa_(com ... e_renderer llvmpipe implies s/w rendering. So is that what's probably happening? Rendering of the wayland desktop is happening on the CPU?

And this still doesn't explain why the refresh rate shown is 43 Hz on the VU-7+. Might lack of EDID on the VU-7+ have something to do with it? (The log shows that the EDID of the 4K display is being read).

User avatar
odroid
Site Admin
Posts: 32358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 146 times
Been thanked: 325 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by odroid » Tue Feb 26, 2019 4:34 pm

As far as I remember, there was a Kernel patch to change the refresh rate to 60Hz from 43Hz for 1024x600 resolution.
We will let you know our github commit link.

Meanwhile, you can try our Ubuntu image to check the refresh rate 60Hz since we don't use Armbian internally.

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Tue Feb 26, 2019 4:51 pm

dqbydt wrote:
Tue Feb 26, 2019 3:24 pm
And this still doesn't explain why the refresh rate shown is 43 Hz on the VU-7+. Might lack of EDID on the VU-7+ have something to do with it? (The log shows that the EDID of the 4K display is being read).
Hi dqbydt,

Do you use display_autodetection mode of ODROID-C2?
If so, could you try a manual mode of 1024x600p60hz?

EDID of Vu7+ is configured as 1024x600p43Hz. :(
So if your C2 is set as display_autodetection, you must have 43Hz of vsync,
because the final vsync value is a result of [pixel clock / htotal / vtotal] from VU7+ EDID in that case.

Code: Select all

Detailed mode (1) : Clock 32 MHz, 108 mm x 68 mm
               1024 1064 1112 1152 hborder 0
                600  613  616  645 vborder 0
               -hsync -vsync 

Code: Select all

- pixel clock : 32MHz
- Vsync : 43Hz 
With manual 1024x600p60hz, vsync value will be set as a FIXED 60Hz.

Please modify the following parameters in boot.ini.

Code: Select all

### display autodetect to false
# setenv display_autodetect "true"
setenv display_autodetect "false"

setenv m "1024x600p60hz"
I have no idea how Armbian's boot configuration is set.
If this guide is not compatible with Armbian's way (ex: display setting using boot.ini), please let me know.

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

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by memeka » Tue Feb 26, 2019 4:55 pm

There is the assumption here that he’s using the HK 3.16 kernel. He might not, he might me be using armbian with 4.x kernel. I also have a hdmi touchscreen that works on 3.16 but doesn’t on mainline.

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Tue Feb 26, 2019 4:59 pm

odroid wrote:
Tue Feb 26, 2019 4:34 pm
As far as I remember, there was a Kernel patch to change the refresh rate to 60Hz from 43Hz for 1024x600 resolution.
We will let you know our github commit link.

Meanwhile, you can try our Ubuntu image to check the refresh rate 60Hz since we don't use Armbian internally.
@odroid,
For C2, the original refresh rate of hdmi phy setting in case of 1024x600 is 60Hz. (including initial release version from AMLogic)
The history is related to only XU4 case.

Also, I almost forgot the history. :o
That was a very~~ long time ago. haha~

Manual mode, 1024x600 must fix this issue, I think. ;)

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Tue Feb 26, 2019 5:04 pm

memeka wrote:
Tue Feb 26, 2019 4:55 pm
There is the assumption here that he’s using the HK 3.16 kernel. He might not, he might me be using armbian with 4.x kernel. I also have a hdmi touchscreen that works on 3.16 but doesn’t on mainline.
@memeka,
Thanks for the information.

@dqbydt,
Could you share the link of your Armbian kernel that I can check with, if my aforementioned guide doesn't work?

dqbydt
Posts: 40
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 XU4 VU5 VU7+
Has thanked: 0
Been thanked: 0
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by dqbydt » Wed Feb 27, 2019 3:13 am

memeka wrote:
Tue Feb 26, 2019 4:55 pm
There is the assumption here that he’s using the HK 3.16 kernel. He might not, he might me be using armbian with 4.x kernel.
Correct, I am indeed using the mainline kernel with Armbian.

Code: Select all

odroid@odroidc2:~$ uname -a
Linux odroidc2 4.19.24-meson64 #5.76 SMP PREEMPT Wed Feb 20 22:59:52 UTC 2019 aarch64 GNU/Linux
odroid@odroidc2:~$ lsb_release -a
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 9.8 (stretch)
Release:	9.8
Codename:	stretch
joy wrote:
Tue Feb 26, 2019 5:04 pm
I have no idea how Armbian's boot configuration is set.
If this guide is not compatible with Armbian's way (ex: display setting using boot.ini), please let me know.
This is my first time trying Armbian (the only reason I tried it was because of vsync tearing artifacts with HK Ubuntu images) and it looks like their boot config is indeed totally different. Their SD card structure is quite unusual, there is only one partition! No separate boot partition. Kernel image is in /boot within the rootfs. There isn't a boot.ini; instead there are armbianEnv.txt and boot.cmd. The comment at the top of boot.cmd says DO NOT EDIT THIS FILE Please edit /boot/armbianEnv.txt to set supported parameters, so presumably armbianEnv.txt is the equivalent of boot.ini? But there is nothing in it that matches display mode setting. Also I'm not sure whether/how boot.cmd needs to be regenerated from armbianEnv.txt.

I found some modesetting info here: https://docs.armbian.com/User-Guide_Fine-Tuning/ and added disp.screen0_output_mode=1024x600p60 to armbianEnv.txt but that didn't seem to take hold (weston-info after reboot still shows 43 Hz). Then I added that mode line to boot.cmd in spite of the "DO NOT EDIT" warning and regenerated boot.scr. Still no go, 43 Hz after reboot. I have also tried adding a modeline as generated by cvt to ~/.config/weston.ini, as described here: https://linoxide.com/linux-how-to/run-w ... rch-linux/

Code: Select all

odroid@odroidc2:~$ cat ~/.config/weston.ini 
[output] name=HDMI1
# 1024x600 59.69 Hz (CVT) hsync: 36.95 kHz; pclk: 43.75 MHz
mode=43.75  1024 1072 1104 1184  600 603 613 619 +hsync -vsync
transform=normal
None of these methods work, unfortunately.
joy wrote:
Tue Feb 26, 2019 5:04 pm
Could you share the link of your Armbian kernel that I can check with, if my aforementioned guide doesn't work?
I built it from source with all the defaults for odroid-c2, following the guide here: https://docs.armbian.com/Developer-Guid ... eparation/
I think the only thing I deliberately selected was mainline kernel instead of HK.

dqbydt
Posts: 40
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 XU4 VU5 VU7+
Has thanked: 0
Been thanked: 0
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by dqbydt » Wed Feb 27, 2019 3:55 am

I realized another option might be to force EDID. They have a /lib/firmware/edid/1024x600.bin, which contains:

Code: Select all

$ edid-decode /lib/firmware/edid/1024x600.bin
...
Standard timings supported:
  1024x576@60Hz
Detailed mode: Clock 50.400 MHz, 355 mm x 208 mm
               1024 1048 1184 1344 hborder 0
                600  601  604  625 vborder 0
               -hsync +vsync 
...               
I'm not sure why it says 1024x576 but I tried it anyway, with drm_kms_helper.edid_firmware=edid/1024x600.bin in both armbianEnv.txt as well as boot.cmd. But after I reboot, I don't see that parameter in /proc/cmdline. So I'm missing some mechanics of passing kernel params. If anybody can confirm that this is a reasonable approach to follow, I can ask on the armbian forums regarding the correct technique for doing this.

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

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by memeka » Wed Feb 27, 2019 5:00 am

C2 drivers in mainline have limited clocks for hdmi, so vu5/7 might not work.

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Wed Feb 27, 2019 8:27 am

dqbydt wrote:
Wed Feb 27, 2019 3:13 am
I built it from source with all the defaults for odroid-c2, following the guide here: https://docs.armbian.com/Developer-Guid ... eparation/
I think the only thing I deliberately selected was mainline kernel instead of HK.
Thank you for sharing the information.
My aforementioned guide must be useless.

If you're using 4.19.x mainline kernel and meson display driver supports a common drm interface, your edid must work as 1024x600p60hz,
because the drm driver of the kernel will select the detailed timing information that is higher priority.

I haven't tried it with 4.19 mainline kernel, just confirmed 4.14.y kernel with XU4 and drm/kms helper interface, which is same way.
https://wiki.odroid.com/odroid-xu4/appl ... ibfirmware
And my edid.bin is same as yours.
It works as 1024x600p60hz.

Code: Select all

$ cat 1024x600.bin | edid-decode 
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   21 6c 00 00 00 00 00 00 0c 1b
version:         01 03
basic params:    80 23 14 78 ea
chroma info:     5e c0 a4 59 4a 98 25 20 50 54
established:     00 00 00
standard:        61 c0 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    b0 13 00 40 41 58 19 20 18 88 13 00 63 d0 10 00 00 1c
descriptor 2:    00 00 00 ff 00 4c 69 6e 75 78 20 23 30 0a 20 20 20 20
descriptor 3:    00 00 00 fd 00 3b 3d 24 26 06 00 0a 20 20 20 20 20 20
descriptor 4:    00 00 00 fc 00 31 30 32 34 78 36 30 30 0a 20 20 20 20
extensions:      00
checksum:        43

Manufacturer: HKL Model 0 Serial Number 0
Made week 12 of 2017
EDID version: 1.3
Digital display
Maximum image size: 35 cm x 20 cm
Gamma: 2.20
DPMS levels: Standby Suspend Off
Supported color formats: RGB 4:4:4, YCrCb 4:2:2
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
  1024x576@60Hz
Detailed mode: Clock 50.400 MHz, 355 mm x 208 mm
               1024 1048 1184 1344 hborder 0
                600  601  604  625 vborder 0
               -hsync +vsync 
Serial number: Linux
Monitor ranges (GTF): 59-61Hz V, 36-38kHz H, max dotclock 60MHz
Monitor name: 1024x600
Checksum: 0x43 (valid)
EDID block does NOT conform to EDID 1.3!
	Detailed block string not properly terminated
dqbydt wrote:
Wed Feb 27, 2019 3:13 am
I'm not sure why it says 1024x576 but I tried it anyway, with drm_kms_helper.edid_firmware=edid/1024x600.bin in both armbianEnv.txt as well as boot.cmd. But after I reboot, I don't see that parameter in /proc/cmdline. So I'm missing some mechanics of passing kernel params. If anybody can confirm that this is a reasonable approach to follow, I can ask on the armbian forums regarding the correct technique for doing this.
But to use the approach, bootargs must contain this information, drm_kms_helper.edid_firmware=edid/1024x600.bin.
I think you'd better ask this cmdline issue on Armbian forum, too.

And one more thing is needed.
Meson hdmi driver of the mainline kernel should support 50.4MHz pixel clock.
If not so, you may not have display.

Let me check the driver.

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Wed Feb 27, 2019 11:03 am

dqbydt wrote:
Wed Feb 27, 2019 3:55 am
I'm not sure why it says 1024x576 but I tried it anyway, with drm_kms_helper.edid_firmware=edid/1024x600.bin in both armbianEnv.txt as well as boot.cmd. But after I reboot, I don't see that parameter in /proc/cmdline. So I'm missing some mechanics of passing kernel params. If anybody can confirm that this is a reasonable approach to follow, I can ask on the armbian forums regarding the correct technique for doing this.
You need to build boot.scr again as following.

Code: Select all

root@odroidc2:~# cd /boot/
(modify boot.cmd, then....)
root@odroidc2:/boot# mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n 'Execute uImage.bin' -d boot.cmd boot.scr
(then, reboot)

User avatar
odroid
Site Admin
Posts: 32358
Joined: Fri Feb 22, 2013 11:14 pm
languages_spoken: English
ODROIDs: ODROID
Has thanked: 146 times
Been thanked: 325 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by odroid » Wed Feb 27, 2019 11:11 am

joy wrote:
Tue Feb 26, 2019 4:59 pm
@odroid,
For C2, the original refresh rate of hdmi phy setting in case of 1024x600 is 60Hz. (including initial release version from AMLogic)
The history is related to only XU4 case.
You are right! :oops:
I'm getting old quickly. hahaha :o

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Wed Feb 27, 2019 12:01 pm

joy wrote:
Wed Feb 27, 2019 11:03 am
dqbydt wrote:
Wed Feb 27, 2019 3:55 am
I'm not sure why it says 1024x576 but I tried it anyway, with drm_kms_helper.edid_firmware=edid/1024x600.bin in both armbianEnv.txt as well as boot.cmd. But after I reboot, I don't see that parameter in /proc/cmdline. So I'm missing some mechanics of passing kernel params. If anybody can confirm that this is a reasonable approach to follow, I can ask on the armbian forums regarding the correct technique for doing this.
You need to build boot.scr again as following.

Code: Select all

root@odroidc2:~# cd /boot/
(modify boot.cmd, then....)
root@odroidc2:/boot# mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n 'Execute uImage.bin' -d boot.cmd boot.scr
(then, reboot)
Hi dqbydt,
As I checked the 4.19.y meson drm driver and related patches, it looks 1024x600p60hz with pixel clock 50.4MHz can work with drm/kms helper.

To make sure, I'm checking forced edid on Armbian image.
I updated kernel to 4.19.25-meson64 and boot.scr.
Now I got the correct cmdline, but it doesn't work yet.

Code: Select all

root@odroidc2:~# uname -a
Linux odroidc2 4.19.25-meson64 #5.76 SMP PREEMPT Wed Feb 27 10:00:21 KST 2019 aarch64 GNU/Linux

Code: Select all

root@odroidc2:~# cat /proc/cmdline 
root=UUID=24e14127-60f7-4057-9dc1-310e21f86ff1 rootwait rootfstype=ext4 panic=10 console=ttyAML0,115200 console=tty1 consoleblank=0 loglevel=1 ubootpart=fc280000-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u   drm_kms_helper.edid_firmware=1024x600.bin cgroup_enable=memory swapaccount=1

Code: Select all

root@odroidc2:~# cat /sys/class/drm/card0-HDMI-A-1/edid | edid-decode
.....
Established timings supported:
Standard timings supported:
Detailed mode: Clock 32.000 MHz, 108 mm x 68 mm
               1024 1064 1112 1152 hborder 0
                600  613  616  645 vborder 0
               -hsync -vsync 
Checksum: 0x9f (valid)
As I checked, the following kernel defconfig should be activated.

Code: Select all

CONFIG_DRM_LOAD_EDID_FIRMWARE
I will try to rebuild kernel, then share the result here again.

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Wed Feb 27, 2019 4:58 pm

@dqbydt,

Here is my instruction.
I've confirmed VU7+ is working with forced EDID 1024x600p60hz (50.4MHz) on Armbian and updated 4.19.25-meson64 kernel.

I included edid binary in kernel side.
I think this approach is not best one so I will check the reason more tomorrow
, why /lib/firmware/myedid.bin is not available without kernel side firmware under kernel/firmware/edid/1024x600.bin.
(As I do forced edid on XU4, it should work. Hmm.... Anyway....)

1. Update defconfig
I attached [ linux-meson64-next.config ] file.
Replace original one with this file.
Path : build/config/kernel/linux-meson64-next.config

2. Copy 1024x600.bin
Also please find 1024x600.bin binary file attachment.
Copy it into the following path.
Path : build/cache/sources/linux-mainline/linux-4.19.y/firmware/edid/1024x600.bin

3. Build kernel again as Armbian's guide using compile.sh and install kernel-related debs

4. update boot.scr
Since kernel 4.15.y, related kernel command line has been changed.

Code: Select all

### drm_kms_helper.edid_firmware -> drm.edid_firmware
drm.edid_firmware=edid/1024x600.bin
Add it in bootargs of /boot/boot.cmd,
then build boot.scr again.

Code: Select all

root@odroidc2:/boot# mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n 'Execute uImage.bin' -d boot.cmd boot.scr
5. Then, reboot.

I confirmed it works.

Code: Select all

root@odroidc2:~# cat /proc/cmdline 
root=UUID=24e14127-60f7-4057-9dc1-310e21f86ff1 rootwait rootfstype=ext4 panic=10 console=ttyAML0,115200 console=tty1 consoleblank=0 loglevel=1 ubootpart=fc280000-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u  drm.edid_firmware=edid/1024x600.bin cgroup_enable=memory swapaccount=1

Code: Select all

root@odroidc2:~# apt-get install edid-decode

root@odroidc2:~# cat /sys/class/drm/card0-HDMI-A-1/edid | edid-decode
Extracted contents:
header:          00 ff ff ff ff ff ff 00
serial number:   21 6c 00 00 00 00 00 00 0c 1b
version:         01 03
basic params:    80 23 14 78 ea
chroma info:     5e c0 a4 59 4a 98 25 20 50 54
established:     00 00 00
standard:        61 c0 01 01 01 01 01 01 01 01 01 01 01 01 01 01
descriptor 1:    b0 13 00 40 41 58 19 20 18 88 13 00 63 d0 10 00 00 1c
descriptor 2:    00 00 00 ff 00 4c 69 6e 75 78 20 23 30 0a 20 20 20 20
descriptor 3:    00 00 00 fd 00 3b 3d 24 26 06 00 0a 20 20 20 20 20 20
descriptor 4:    00 00 00 fc 00 31 30 32 34 78 36 30 30 0a 20 20 20 20
extensions:      00
checksum:        43

Manufacturer: HKL Model 0 Serial Number 0
Made week 12 of 2017
EDID version: 1.3
Digital display
Maximum image size: 35 cm x 20 cm
Gamma: 2.20
DPMS levels: Standby Suspend Off
Supported color formats: RGB 4:4:4, YCrCb 4:4:4
First detailed timing is preferred timing
Established timings supported:
Standard timings supported:
  1024x576@60Hz
Detailed mode: Clock 50.400 MHz, 355 mm x 208 mm
               1024 1048 1184 1344 hborder 0
                600  601  604  625 vborder 0
               -hsync +vsync 
Serial number: Linux
Monitor ranges (GTF): 59-61Hz V, 36-38kHz H, max dotclock 60MHz
Monitor name: 1024x600
Checksum: 0x43 (valid)
EDID block does NOT conform to EDID 1.3!
        Detailed block string not properly terminated

Code: Select all

root@odroidc2:~# cat /sys/module/drm_kms_helper/parameters/edid_firmware 
edid/1024x600.bin

Code: Select all

[drm] Got external EDID base block and 0 extensions from "edid/1024x600.bin" for connector "HDMI-A-1"
[drm:dw_hdmi_mode_valid] Modeline 0:"1024x600" 60 50400 1024 1048 1184 1344 600 601 604 625 0x48 0x6
[drm:meson_hdmi_pll_find_params] PLL params for 504000kHz: m=a8 frac=0 od=16
[drm:meson_hdmi_pll_find_params] PLL params for 504000kHz: m=54 frac=0 od=8
Could you try it?
I hope it fixes this issue, so you can get 60 fps with VU7+ and go to the next step for your project.

Once I have an update, I will share it here again.
Attachments
c2_armbian_forced_edid_vu7plus.zip
(212 Bytes) Downloaded 20 times

dqbydt
Posts: 40
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 XU4 VU5 VU7+
Has thanked: 0
Been thanked: 0
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by dqbydt » Thu Feb 28, 2019 3:25 pm

Hello @joy
joy wrote:
Wed Feb 27, 2019 4:58 pm
I attached [ linux-meson64-next.config ] file.

Also please find 1024x600.bin binary file attachment.
Were both of these intended to be in the c2_armbian_forced_edid_vu7plus.zip? But that zip is empty, there are no files in it.

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Thu Feb 28, 2019 6:15 pm

dqbydt wrote:
Thu Feb 28, 2019 3:25 pm
Hello @joy
joy wrote:
Wed Feb 27, 2019 4:58 pm
I attached [ linux-meson64-next.config ] file.

Also please find 1024x600.bin binary file attachment.
Were both of these intended to be in the c2_armbian_forced_edid_vu7plus.zip? But that zip is empty, there are no files in it.
@dqbydt,
I made a mistake. Sorry.
I attached another zip file again.
Could you check it again?
Attachments
c2_armbian_forced_edid_vu7plus_2.zip
(35.97 KiB) Downloaded 22 times

dqbydt
Posts: 40
Joined: Wed Mar 01, 2017 7:52 am
languages_spoken: English
ODROIDs: C1+ C2 XU4 VU5 VU7+
Has thanked: 0
Been thanked: 0
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by dqbydt » Fri Mar 01, 2019 11:40 am

@joy, I tried your steps and it works!

I see this as the output of weston-info:

Code: Select all

interface: 'wl_output', version: 3, name: 10
        x: 0, y: 0, scale: 1,
        physical_width: 350 mm, physical_height: 200 mm,
        make: 'HKL', model: '1024x600',
        subpixel_orientation: unknown, output_transform: normal,
        mode:
                width: 1024 px, height: 600 px, refresh: 60.000 Hz,
                flags: current preferred
        mode:
                width: 1024 px, height: 576 px, refresh: 59.967 Hz,
                flags:
        mode:
                width: 1024 px, height: 768 px, refresh: 60.004 Hz,
                flags:
So it is indeed running at 60 Hz refresh. Thank you for your help!

joy
Posts: 890
Joined: Fri Oct 02, 2015 1:44 pm
languages_spoken: english
ODROIDs: ODROID-C1+, XU4, X
Has thanked: 13 times
Been thanked: 49 times
Contact:

Re: Not getting 60 fps refresh on Armbian Stretch + Wayland

Unread post by joy » Mon Mar 04, 2019 8:41 am

dqbydt wrote:
Fri Mar 01, 2019 11:40 am
@joy, I tried your steps and it works!

I see this as the output of weston-info:

Code: Select all

interface: 'wl_output', version: 3, name: 10
        x: 0, y: 0, scale: 1,
        physical_width: 350 mm, physical_height: 200 mm,
        make: 'HKL', model: '1024x600',
        subpixel_orientation: unknown, output_transform: normal,
        mode:
                width: 1024 px, height: 600 px, refresh: 60.000 Hz,
                flags: current preferred
        mode:
                width: 1024 px, height: 576 px, refresh: 59.967 Hz,
                flags:
        mode:
                width: 1024 px, height: 768 px, refresh: 60.004 Hz,
                flags:
So it is indeed running at 60 Hz refresh. Thank you for your help!
@dqbydt,
Thank you for sharing your status.
Glad to hear it works! :D

Also for me, this is a good chance to look into the meson drm driver of mainline kernel.
( Even though still I'm trying to figure out why userspace support under /lib/firmware doesn't work, but don't have any update so far. I hope I can fix it so, share a better solution with you soon. )

Post Reply

Return to “Other OS”

Who is online

Users browsing this forum: No registered users and 3 guests