Any plan for basic mainline linux support?

[RussianNeuroMancer]

What's the kernel version of it, please let me have the output of uname -a.

That the right question - I switched to your Panforst kernel on C4, but forgot to do this so N2+ (running Ubuntu 20.10 image, by the way). After switch to Panfrost kernel on N2+ most of issues I mentioned above (including the one you see on the screenshot) did go away (besides cursor flicker and panfrost gpu sched timeout errors in dmesg that is still possible to reproduce in Gnome Shell overview if Firefox running with layers.acceleration.force-enabled=1 and for example playback video from YouTube). It's good to know that Panfrost is already in good shape on Mali-G52. There is probably some other problems, but at least current state is something that worth time I could spend on testing and reporting issues, when pinky grey issue will be resolved.

However, since pinky grey issue is not resolved I still have to try to get usable system based on Linux 4.9. Currently I trying to get your mali-bifrost-dkms installed on Armbian legacy image, but all available releases fail in different ways.

What exactly you changed in your kernel releases to make mali kernel module build without errors?

[istanbulls]

What's the kernel version of it, please let me have the output of uname -a.

That the right question - I switched to your Panforst kernel on C4, but forgot to do this so N2+ (running Ubuntu 20.10 image, by the way). After switch to Panfrost kernel on N2+ most of issues I mentioned above (including the one you see on the screenshot) did go away (besides cursor flicker and panfrost gpu sched timeout errors in dmesg that is still possible to reproduce in Gnome Shell overview if Firefox running with layers.acceleration.force-enabled=1 and for example playback video from YouTube). It's good to know that Panfrost is already in good shape on Mali-G52. There is probably some other problems, but at least current state is something that worth time I could spend on testing and reporting issues, when pinky grey issue will be resolved.

However, since pinky grey issue is not resolved I still have to try to get usable system based on Linux 4.9. Currently I trying to get your mali-bifrost-dkms installed on Armbian legacy image, but all available releases fail in different ways.

What exactly you changed in your kernel releases to make mali kernel module build without errors?

Have you tried Ubuntu-Wayland 20.04.1LTS 5.10.4? It works stable and fast on both N2+ and C4.
More stable for me than Panfrost and 20.10.

[RussianNeuroMancer]

Have you tried Ubuntu-Wayland 20.04.1LTS 5.10.4? It works stable and fast on both N2+ and C4.
More stable for me than Panfrost and 20.10.

There is pinky grey issue (discussed on the previous page of this topic) on 5.x kernels, so it's not an option for now.

[istanbulls]

@RussianNeuroMancer
I know about the problem. I didn't know you had this problem either. There is no color issue for me. The splash screen is not completely black, it looks like very dark green yes, a color closer to black. but while the system was running I haven't noticed a problem yet.

[tobetter]

What's the kernel version of it, please let me have the output of uname -a.

That the right question - I switched to your Panforst kernel on C4, but forgot to do this so N2+ (running Ubuntu 20.10 image, by the way). After switch to Panfrost kernel on N2+ most of issues I mentioned above (including the one you see on the screenshot) did go away (besides cursor flicker and panfrost gpu sched timeout errors in dmesg that is still possible to reproduce in Gnome Shell overview if Firefox running with layers.acceleration.force-enabled=1 and for example playback video from YouTube). It's good to know that Panfrost is already in good shape on Mali-G52. There is probably some other problems, but at least current state is something that worth time I could spend on testing and reporting issues, when pinky grey issue will be resolved.

However, since pinky grey issue is not resolved I still have to try to get usable system based on Linux 4.9. Currently I trying to get your mali-bifrost-dkms installed on Armbian legacy image, but all available releases fail in different ways.

What exactly you changed in your kernel releases to make mali kernel module build without errors?

For the pinky green issue, are you able to install new kernel package with your N2 with you display device?

Add one line with testing to /etc/apt/sources.list.d/ppa_linuxfactory_or_kr.list and install new kernel package for testing.

Code: Select all

$ cat /etc/apt/sources.list.d/ppa_linuxfactory_or_kr.list
deb http://ppa.linuxfactory.or.kr groovy main
deb http://ppa.linuxfactory.or.kr groovy non-free
deb http://ppa.linuxfactory.or.kr groovy contrib
deb http://ppa.linuxfactory.or.kr groovy testing
$ sudo apt update
$ sudo apt install linux-image-5.10.0-142-odroid-arm64 linux-headers-5.10.0-142-odroid-arm64

I've tested with two display and they gave me better grey with less reddish tone. I've not applied the change to the Panfrost kernel package yet.

EDIT: I've provided the fix to @jgmdev to test on ALARM and he confirms it works. So I guess...the Pinky Grey will be fixed with new kernel package - 5.10.5 - what I am testing.

[amirul]

What's the kernel version of it, please let me have the output of uname -a.

That the right question - I switched to your Panforst kernel on C4, but forgot to do this so N2+ (running Ubuntu 20.10 image, by the way). After switch to Panfrost kernel on N2+ most of issues I mentioned above (including the one you see on the screenshot) did go away (besides cursor flicker and panfrost gpu sched timeout errors in dmesg that is still possible to reproduce in Gnome Shell overview if Firefox running with layers.acceleration.force-enabled=1 and for example playback video from YouTube). It's good to know that Panfrost is already in good shape on Mali-G52. There is probably some other problems, but at least current state is something that worth time I could spend on testing and reporting issues, when pinky grey issue will be resolved.

However, since pinky grey issue is not resolved I still have to try to get usable system based on Linux 4.9. Currently I trying to get your mali-bifrost-dkms installed on Armbian legacy image, but all available releases fail in different ways.

What exactly you changed in your kernel releases to make mali kernel module build without errors?

For the pinky green issue, are you able to install new kernel package with your N2 with you display device?

Add one line with testing to /etc/apt/sources.list.d/ppa_linuxfactory_or_kr.list and install new kernel package for testing.

Code: Select all

$ cat /etc/apt/sources.list.d/ppa_linuxfactory_or_kr.list
deb http://ppa.linuxfactory.or.kr groovy main
deb http://ppa.linuxfactory.or.kr groovy non-free
deb http://ppa.linuxfactory.or.kr groovy contrib
deb http://ppa.linuxfactory.or.kr groovy testing
$ sudo apt update
$ sudo apt install linux-image-5.10.0-142-odroid linux-headers-5.10.0-142-odroid

I've tested with two display and they gave me better grey with less reddish tone. I've not applied the change to the Panfrost kernel package yet.

EDIT: I've provided the fix to @jgmdev to test on ALARM and he confirms it works. So I guess...the Pinky Grey will be fixed with new kernel package - 5.10.5 - what I am testing.

amirul@n2plus:~$ cat /etc/apt/sources.list.d/ppa-linuxfactory-or-kr.list
deb http://ppa.linuxfactory.or.kr groovy main non-free
deb-src http://ppa.linuxfactory.or.kr groovy main non-free
deb http://ppa.linuxfactory.or.kr groovy contrib
deb http://ppa.linuxfactory.or.kr groovy testing
amirul@n2plus:~$ sudo apt update
amirul@n2plus:~$ sudo apt install linux-image-5.10.0-142-odroid linux-headers-5.10.0-142-odroid
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-image-5.10.0-142-odroid
E: Couldn't find any package by glob 'linux-image-5.10.0-142-odroid'
E: Unable to locate package linux-headers-5.10.0-142-odroid
E: Couldn't find any package by glob 'linux-headers-5.10.0-142-odroid'

Help??

[tobetter]

amirul@n2plus:~$ cat /etc/apt/sources.list.d/ppa-linuxfactory-or-kr.list
deb http://ppa.linuxfactory.or.kr groovy main non-free
deb-src http://ppa.linuxfactory.or.kr groovy main non-free
deb http://ppa.linuxfactory.or.kr groovy contrib
deb http://ppa.linuxfactory.or.kr groovy testing
amirul@n2plus:~$ sudo apt update
amirul@n2plus:~$ sudo apt install linux-image-5.10.0-142-odroid linux-headers-5.10.0-142-odroid
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package linux-image-5.10.0-142-odroid
E: Couldn't find any package by glob 'linux-image-5.10.0-142-odroid'
E: Unable to locate package linux-headers-5.10.0-142-odroid
E: Couldn't find any package by glob 'linux-headers-5.10.0-142-odroid'

Help??

Sorry, I gave you wrong command so please use this.

Code: Select all

$ sudo apt install linux-image-5.10.0-142-odroid-arm64 linux-headers-5.10.0-142-odroid-arm64

Also, run another command if the kernel version is not switched to 5.10.0-142 after rebooting.

Code: Select all

$ sudo flash-kernel --force 5.10.0-142-odroid-arm64

[amirul]

Sorry, I gave you wrong command so please use this.

Code: Select all

$ sudo apt install linux-image-5.10.0-142-odroid-arm64 linux-headers-5.10.0-142-odroid-arm64

Also, run another command if the kernel version is not switched to 5.10.0-142 after rebooting.

Code: Select all

$ sudo flash-kernel --force 5.10.0-142-odroid-arm64

amirul@n2plus:~$ sudo apt install linux-image-5.10.0-142-odroid-arm64 linux-headers-5.10.0-142-odroid-arm64
amirul@n2plus:~$ sudo flash-kernel --force 5.10.0-142-odroid-arm64

Sorry, ubuntu wayland failed to start.

[tobetter]

Sorry, I gave you wrong command so please use this.

Code: Select all

$ sudo apt install linux-image-5.10.0-142-odroid-arm64 linux-headers-5.10.0-142-odroid-arm64

Also, run another command if the kernel version is not switched to 5.10.0-142 after rebooting.

Code: Select all

$ sudo flash-kernel --force 5.10.0-142-odroid-arm64

amirul@n2plus:~$ sudo apt install linux-image-5.10.0-142-odroid-arm64 linux-headers-5.10.0-142-odroid-arm64
amirul@n2plus:~$ sudo flash-kernel --force 5.10.0-142-odroid-arm64

Sorry, ubuntu wayland failed to start.

Hmmm...maybe Bifrost driver building is failed. Will you run this script?
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

[amirul]

Hmmm...maybe Bifrost driver building is failed. Will you run this script?
http://ppa.linuxfactory.or.kr/band-aid/ ... st_dkms.sh

amirul@n2plus:~$ sudo ./rebuild_bifrost_dkms.sh
E: failed to download Linux header packages - :5.10.5-202101080343~groovy

[amirul]

On the other hand xfce4 runs in accelerated X out of the box
amirul@groovy-server:~$ uname -a
Linux groovy-server 5.10.0-odroid-panfrost-arm64 #1 SMP PREEMPT Ubuntu 5.10.4-202101051132~groovy (2021-01-05) aarch64 aarch64 aarch64 GNU/Linux
amirul@groovy-server:~$ grep Panfrost /var/log/Xorg.0.log
[ 1128.373] (II) modeset(0): glamor X acceleration enabled on Mali G52 (Panfrost)
amirul@groovy-server:~$ glxinfo |grep OpenGL
OpenGL vendor string: Panfrost
OpenGL renderer string: Mali G52 (Panfrost)
OpenGL version string: 2.1 Mesa 21.0.0-devel (git-a6bdbd5c0f)
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 21.0.0-devel (git-a6bdbd5c0f)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:

Only cons: pinky-grey & flashing mouse cursor

[tobetter]

On the other hand xfce4 runs in accelerated X out of the box
amirul@groovy-server:~$ uname -a
Linux groovy-server 5.10.0-odroid-panfrost-arm64 #1 SMP PREEMPT Ubuntu 5.10.4-202101051132~groovy (2021-01-05) aarch64 aarch64 aarch64 GNU/Linux
amirul@groovy-server:~$ grep Panfrost /var/log/Xorg.0.log
[ 1128.373] (II) modeset(0): glamor X acceleration enabled on Mali G52 (Panfrost)
amirul@groovy-server:~$ glxinfo |grep OpenGL
OpenGL vendor string: Panfrost
OpenGL renderer string: Mali G52 (Panfrost)
OpenGL version string: 2.1 Mesa 21.0.0-devel (git-a6bdbd5c0f)
OpenGL shading language version string: 1.20
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 2.0 Mesa 21.0.0-devel (git-a6bdbd5c0f)
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 1.0.16
OpenGL ES profile extensions:

Only cons: pinky-grey & flashing mouse cursor

The Pinky-Grey issue will be resolved with new kernel package update and still I am testing the changes before uploading which will be happen in 12 hours hopefully.

[amirul]

The Pinky-Grey issue will be resolved with new kernel package update and still I am testing the changes before uploading which will be happen in 12 hours hopefully.

That's awesome news. Thank you for your effort

[mad_ady]

Regarding mouse cursor flicker - I think it was present on xu4 too and needed HW cursor to be disabled in xorg.conf...

[jgmdev]

I have upgraded the archlinux linux-amlogic-panfrost-510 package to include tobetter fix for pinky grays, so far is working perfectly in all the displays I have !

[amirul]

amirul@n2plus:~$ uname -a
Linux n2plus 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.5-202101082057~groovy (2021-01-08) aarch64 aarch64 aarch64 GNU/Linux
amirul@n2plus:~$ dkms status
mali-bifrost, 24.0+202101081746~groovy, 5.10.0-odroid-arm64, aarch64: installed

Pinky-grey is gone, great job tobetter

[tobetter]

amirul@n2plus:~$ uname -a
Linux n2plus 5.10.0-odroid-arm64 #1 SMP PREEMPT Ubuntu 5.10.5-202101082057~groovy (2021-01-08) aarch64 aarch64 aarch64 GNU/Linux
amirul@n2plus:~$ dkms status
mali-bifrost, 24.0+202101081746~groovy, 5.10.0-odroid-arm64, aarch64: installed

Pinky-grey is gone, great job tobetter

Thank you to know it works...and glad to know Mali Bifrost driver is successfully updated with 5.10.5 kernel.

[amirul]

Panfrost wayland was working great too after the update, no pinky-grey & mouse cursor flicker. Then I got tired of the keyring unlock dialog, deleted all my keys, now having trouble getting to the desktop
Guess I'll stick with bifrost for now.

EDIT: It's all good, the desktop is at Alt-F8 not F7
amirul@groovy-server:~$ uname -a
Linux groovy-server 5.10.0-odroid-panfrost-arm64 #1 SMP PREEMPT Ubuntu 5.10.5-202101090637~groovy (2021-01-08) aarch64 aarch64 aarch64 GNU/Linux

[RussianNeuroMancer]

For the pinky green issue, are you able to install new kernel package with your N2 with you display device?

With 5.10.5 pinky grey issue indeed go away, thanks!

I tried to apply same fix on Armbian, but this isn't succeed so far.

[tobetter]

For the pinky green issue, are you able to install new kernel package with your N2 with you display device?

With 5.10.5 pinky grey issue indeed go away, thanks!

I tried to apply same fix on Armbian, but this isn't succeed so far.

Thank you for confirmation...it's more pinky, likely red...

[Sav]

I have upgraded the archlinux linux-amlogic-panfrost-510 package to include tobetter fix for pinky grays, so far is working perfectly in all the displays I have !

I can confirm the same.

[RussianNeuroMancer]

it's more pinky, likely red...

I tried to remove all own Armbian patches and this didn't help. Now I trying to build their kernel with your config, so result should be identical to your branch (assuming all changed between upstream and your build is listed at the top of the list). But if this won't help, maybe you have an idea what could cause such as difference between behavior of your kernel on your image and behaviour of Armbian kernel on Armbian build? Maybe it have something to do with uboot version? I just not sure what else could cause this.

What uboot version you use for your images? Is it upstream or there is some specific patches?

In case of Armbian it's a uboot 2020.10 and a few patches that shouldn't affect anything related to HDMI, as I understand.

[tobetter]

it's more pinky, likely red...

I tried to remove all own Armbian patches and this didn't help. Now I trying to build their kernel with your config, so result should be identical to your branch (assuming all changed between upstream and your build is listed at the top of the list). But if this won't help, maybe you have an idea what could cause such as difference between behavior of your kernel on your image and behaviour of Armbian kernel on Armbian build? Maybe it have something to do with uboot version? I just not sure what else could cause this.

What uboot version you use for your images? Is it upstream or there is some specific patches?

In case of Armbian it's a uboot 2020.10 and a few patches that shouldn't affect anything related to HDMI, as I understand.

I use Hardkernel stock LEGACY U-boot only, never tried to boot with the update version yet. What I can tell you based on Amlogic magic code experience, even it could behave differently when you show the logo or not from U-boot. And kernel config would not be the matter since the fix I made is not dependent to any other module except HDMI driver.

[RussianNeuroMancer]

I use Hardkernel stock LEGACY U-boot only, never tried to boot with the update version yet.

odroidg12-v2015.01 branch, or some other?

What I can tell you based on Amlogic magic code experience, even it could behave differently when you show the logo or not from U-boot. And kernel config would not be the matter since the fix I made is not dependent to any other module except HDMI driver.

I see. If .config didn't workout I will try to put some variables from this file into this one, and maybe make some changes here.

By the way, did you contacted Neil about this pinky-grey issue and your workaround?

[chewitt]

Amlogic/vendor u-boot sets a lot of DRM properties that are not currently supported or are partially supported in Linux which leads to corner cases where weird colours can show up. One of the reasons to consider using mainline u-boot with mainline kernel images is eliminating these differences. As mainline u-boot doesn't support any DRM capabilities the mainline kernel cannot handle, you don't see the colour problems. It's more of a workaround than a fix, but it works.

FWIW, I use mainline u-boot (currently 2021.01-rc4) with all the Odroid boards I use for testing (N2/N2+/C4/C2/XU4)

branch: https://github.com/chewitt/u-boot/commi ... ic-2021.01

[RussianNeuroMancer]

Amlogic/vendor u-boot sets a lot of DRM properties that are not currently supported or are partially supported in Linux which leads to corner cases where weird colours can show up. One of the reasons to consider using mainline u-boot with mainline kernel images is eliminating these differences. As mainline u-boot doesn't support any DRM capabilities the mainline kernel cannot handle, you don't see the colour problems. It's more of a workaround than a fix, but it works.

I see, but I not quite understand how exactly it's related to observed issue (besides the fact that I obviously should try some other uboot branch - either legacy or yours) since:
1. Pinky grey issue reproducible with vendor uboot on tobetter image and with mainline uboot on Armbian, so it's not causes by difference described in your message, I suppose?
2. Weird colors on the photos is what I getting with mainline uboot (right now in Armbian there is no convenient way to use legacy uboot on ODROID-C4). So it's looks like tobetter workaround somehow rely on legacy uboot behavior?

FWIW, I use mainline u-boot (currently 2021.01-rc4) with all the Odroid boards I use for testing (N2/N2+/C4/C2/XU4)

branch: https://github.com/chewitt/u-boot/commi ... ic-2021.01

Is tobetter workaround works for you on your 2021.01 branch?

[alpe]

I use Ubuntu Minimal 20.04.
Is there any kernel 5+ considered stable?
If so, how to install it?

I want to have btrfs features that aren't available on 4.9.

[alpe]

@alpe,
Try @tobetter's Debian/Ubuntu Netboot Installer which supports Kernel 5.10.
viewtopic.php?f=182&t=37109

[RussianNeuroMancer]

@odroid I wonder if you was able to reproduce any issues mentioned in this topic?

[tobetter]

@odroid I wonder if you was able to reproduce any issues mentioned in this topic?

Can you clarify the issues?

[alpe]

@alpe,
Try @tobetter's Debian/Ubuntu Netboot Installer which supports Kernel 5.10.
viewtopic.php?f=182&t=37109

Can't I install 5.10 on my current official Ubuntu 20.04?
It would take me many hours to start clean and configure everything.
Update to tobetter's version using dist-upgrade would be fine too.

[RussianNeuroMancer]

@odroid I wonder if you was able to reproduce any issues mentioned in this topic?

Can you clarify the issues?

I am sorry, forgot to paste the link:

viewtopic.php?f=181&t=41136

[tobetter]

@odroid I wonder if you was able to reproduce any issues mentioned in this topic?

Can you clarify the issues?

I am sorry, forgot to paste the link:

viewtopic.php?f=181&t=41136

Thanks, so...Pinky-Grey issue resolved...and...I am a bit lost about Black Flickering issue, have you tried with the latest Panfrost update on Ubuntu 20.10 or ArchLinux from @jgmdev?

[odroidn2user]

Is anyone working on solving the display driver support on mainline N2, the bug causing the image compression / image processing alike artifacts around bright colors?

[RussianNeuroMancer]

Thanks, so...Pinky-Grey issue resolved...

In upstream?
If this issue is not fixed in upstream yet, could you please answer to my question about Neil in this message, if possible?

and...I am a bit lost about Black Flickering issue, have you tried with the latest Panfrost update on Ubuntu 20.10

Unfortunately, since I wasn't able to get pinky grey workaround working in combination with upstream uboot and upstream kernel on Armbian running on ODROID-C4 I postoponed all tasks related to ODROID-C4 and N2, so honestly I don't remember details right now (in particular - I don't remember if it was reproducible on Groovy-based images; I not tested Arch-based images).

[tobetter]

Thanks, so...Pinky-Grey issue resolved...

In upstream?
If this issue is not fixed in upstream yet, could you please answer to my question about Neil in this message, if possible?

I use odroidg12-v2015.01 branch only for U-boot, I've mailed Neil once about the issue and he had not seen this yet. The code I remove for the Pinky grey issue was copied from 4.9 branch, according to him, I've not submit the patch yet since the issue could be happen to mainline U-boot which I don't work with and had no chance to try it so far. So the fix is in my kernel repository only, and I believe ArchLinux fro @jgmdev use it and no idea who else use the fix.

and...I am a bit lost about Black Flickering issue, have you tried with the latest Panfrost update on Ubuntu 20.10

Unfortunately, since I wasn't able to get pinky grey workaround working in combination with upstream uboot and upstream kernel on Armbian running on ODROID-C4 I postoponed all tasks related to ODROID-C4 and N2, so honestly I don't remember details right now (in particular - I don't remember if it was reproducible on Groovy-based images; I not tested Arch-based images).

As I said I don't work with mainline U-boot which is not my intention to use so don't know if the Pinky-Grey issue or what ever colour issue happens with mainline U-boot. Probably @chewitt would know better than me since his LibeElec use the mainline U-boot.

[wrist]

Just to be clear. I have a complete OS images (armbian and nixos) with u-boot 2019.

When I dd the image to the SD, it boots. When I dd the same image to the eMMC, it fails to boot. I cannot work out why. Should the eMMC be treated differently?

did you (or anyone here) have any luck using recent NixOS releases on the N2+ (either through the SD card or the eMMC)? if yes, what modifications were needed to achieve that?

[odroidn2user]

Can anyone report any news about the monitor bug in the mainline support?

I keep having the ugly bright coloring, with grainy radiating artifacts around bright colors on my monitor.
This doesn't happen on Hardkernel 4.9 kernel, but it does happen on mainline Linux kernels.
Which means the N2 mainline kernels can't actually be used for anything that requires a monitor.
It is not a new bug, it's been around since the first 5.x mainline I tried, which is well over a year now.
Tried tobetters ubuntu, manjaro arm kernel and the arch linux arm from jgmdev here. They all got it.
And it doesn't show up on screenshots, with and without panfrost, so it seems to me that it must be the monitor driver.

Any insights? I'd love to use the N2's for actual stuff, but the monitor driver bug makes this impossible.
I use a very standard (and new) Dell monitor. I also have an older LG monitor. Both suffer with the bug on the N2.
And it is not just me that experiences this problem. And I don't have this problem with other devices or the hardkernel kernel.

Anyone? Please?
Any plans for fixing the mainline linux support?
I don't have a lot of money, but I can make a small bug bounty donation if that helps. I am willing to donate.

[cdu13a]

Can anyone report any news about the monitor bug in the mainline support?

I keep having the ugly bright coloring, with grainy radiating artifacts around bright colors on my monitor.
This doesn't happen on Hardkernel 4.9 kernel, but it does happen on mainline Linux kernels.
Which means the N2 mainline kernels can't actually be used for anything that requires a monitor.
It is not a new bug, it's been around since the first 5.x mainline I tried, which is well over a year now.
Tried tobetters ubuntu, manjaro arm kernel and the arch linux arm from jgmdev here. They all got it.
And it doesn't show up on screenshots, with and without panfrost, so it seems to me that it must be the monitor driver.

Any insights? I'd love to use the N2's for actual stuff, but the monitor driver bug makes this impossible.
I use a very standard (and new) Dell monitor. I also have an older LG monitor. Both suffer with the bug on the N2.
And it is not just me that experiences this problem. And I don't have this problem with other devices or the hardkernel kernel.

Anyone? Please?
Any plans for fixing the mainline linux support?
I don't have a lot of money, but I can make a small bug bounty donation if that helps. I am willing to donate.

Do you happen to have an example image that this happens very clearly with?

Also what resolution are you using? (Or any other info about display settings that you are using)

[odroidn2user]

Do you happen to have an example image that this happens very clearly with?
Also what resolution are you using? (Or any other info about display settings that you are using)

Well, I use 1080p on both monitors I have, that is 1080p 60hz. Standard normal monitor, hdmi. LG monitor is a 1080p TV. Dell monitor is a P2319H.
It is not a faulty device, I have multiple N2. Also on C4. Also, not the HDMI cable, got multiple of those. Happens with mainline kernel, not the Hardkernel 4.9 kernel.

You notice it on the Firefox icon, for example. The bright orange on the right side looks blocky.
But also on the red links here on the forum, like text on the "post reply" button. It radiates a light red shine.
Or the mouse-over on links, they are red. It looks disrupted. Also the wiggly lines below misspelled words, they have a bright red accent on a normal red wiggly line.
Also, the blue line around the edit box, it has a somewhat darker blue line you would expect, and a bright blue line right next to it to the right. The blue line radiates a bright blue outline.
The buttons at the top of the edit field light up blue when you mouse-over them, they too have a light blue glow to them.

But the artefacts really are everywhere. It is mostly noticable on bright colors, but it really is everywhere. The image looks a little off.
And around the bright colors, it catches the eye. It is not pleasant computing. It looks like some image compression processing or something. Not sure what it is.

[chewitt]

Please take some pics on a smartphone and share them so we can *see* what you mean. Also which window manager/desktop are you using, and what version of panfrost?

[odroidn2user]

Please take some pics on a smartphone and share them so we can *see* what you mean. Also which window manager/desktop are you using, and what version of panfrost?

I've added a screenshot, showing the red text on the forum.
Notice how the red changes within the text van dark to bright red.
Look at the f in for. Notice the bright red line on the right of the f. And the dark red line to the left.
That should not be there.

Same on the P, look at the standing leg of the P in Plan. There is a bright red line to the right-side of the standing leg of the P.
And on the inside of the round bit of the P, there is a bright red accent.
And the right leg of the n of Plan, both dark and light accents.
The dark bits on the 'b' of 'basic', both on the left and right. The bright red accent on the right of the a of 'basic'.
There are exaggerated color contrasts that shouldn't be there.
Those colors are not the result of a bad camera or bad image, they are visible on screen.



Compare and contrast with a normal view, same monitor, same camera:


Blue accents, notice the light-blue halo effect on the left of the main leg of the T.
And notice the light blue halo effect on the vertical blue line.



And it not just broken anti-aliassing on fonts (although that might also be the case, who knows).
See the zoom in on the blue line, picture taken from the blue line on the right of the comment field here on the forum.
Notice the light blue halo next to the line, on the right, but also slightly on the left of the line.



Pictures were taken from JGMdev's Gnome on Arch Linux ARM, seems to be both on Gnome 38 and the recent update of Gnome 40.
Same however goes on the KDE desktop.

[chewitt]

The red(s) look uniform to me, and exactly the same as I what see on a MacBook Pro if I highlight the link. I'm not seeing any glitches.

[odroidn2user]

Well, if those colors in the photo's look right to you... then I'm afraid I can't really explain it any better.
I've added some more photo's and explained what you can see.

Perhaps someone else wants to help explain the issue?
In the mean time, I can't and won't use the N2, because the end result just isn't right.

[cdu13a]

@odroidn2user

Maybe load an image such as https://www.iconspng.com/uploads/circle ... or-mix.png and then take a photo of how it gets displayed, that way maybe it can be clearer to see what differences there are.

[odroidn2user]

@odroidn2user

Maybe load an image such as https://www.iconspng.com/uploads/circle ... or-mix.png and then take a photo of how it gets displayed, that way maybe it can be clearer to see what differences there are.

Well, there is a jpeg-like compression effect to the image on screen, that is difficult to describe right.
I think the most eye catching is the jagged-like effect (almost a saw-tooth thing) you see on the red.



And the left side of the red curve:
With accents / the N2 on the left, without accents on my Intel NUC (Manjaro Linux, KDE Plasma) on the right:

Same camera, same monitor.

[odroidn2user]

I've detailed some more of the issues on the first set of pictures.
If anyone else that experiences this and wants to help explain, please do.

[cdu13a]

So solid red images look like they have been poorly scaled with jagged edges, but edges of the other colors look more or less normal.

I've actually seen this before with my test builds. I thought I had just used the wrong resolution splash and icon files, and that being a minor cosmetic thing for a test build just dismissed it.

[odroidn2user]

I've added an extra screenshot in the first set of pictures, how it should look.

Top N2 with the coloring issues. Bottom another computer without. Same monitor, same camera, same font, same webpage, same browser (both firefox).



Can't make it any clearer than this, I'm afraid. Look at the 'for bas' coloring, big difference.
- it is not a font rendering issue, see the dark red left edge starts of the underline in the upper image.
- it is not just on reds. As explained earlier, the blue lines around the text edit box on this forum also have a weird bright / light blue halo.
- it is not Firefox. Get the same issues when opening the circles-rgb image in Gimp, for example.
- the top picture is actually how it looks, it is no discoloration due to the camera or picture processing afterwards. You clearly see the weird reds with the naked eye on the monitor.

The effect is most pronounced on red though, which makes me suspect some kind of image compression / processing issue.
But that could well be a wrong assessment. Perhaps it is some kind of color contrast setting which is turned up way too high, or some resizing / upscaling thing.
Someone else described it as the image looking grainy, seems like a fitting description as well.

I took a screenshot of the website with Printscreen, on the N2, in Gnome, when it is showing the coloring issues. And then magnified the screenshot (4x without interpolation).

There are no coloring artifacts visible on the screenshot.
So the software rendering is OK, so it seems to me like it is the output to the monitor where it goes wrong.
I'm thinking the hdmi/monitor driver or somewhere thereabouts.

And moderators, please feel free to remove the images / posts when discussed, seeing as they are LARGE.

[chewitt]

I'd be interested to see a comparison using the same windowing system and desktop environment, but switching between panfrost and libmali, because GL/GLES is what's responsible for blending the different visual layers for rendering/output.