Armbian, image glitch

There are no Armbian images. Which means you are on your own fixing the problems.

@igorp https://dl.radxa.com/zero/images/armbian/

That is not official Armbian.
https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity

They come from: https://www.armbian.com/download/

https://docs.armbian.com/User-Guide_FAQ/

Ok. But this is the firmware from the developer.
So I wrote about the error here.

@FOX the issue is related to the display driver. Anything rather 1920 1080p does produce glitches. @jack

1 Like

Full HD same https://photos.app.goo.gl/n7jQwTVmA5x2HJDQ8

[  353.593055] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x3929f80, tail=0x3929f80
[  353.597367] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7301, status=0x58, head=0x3929f80, tail=0x3929f80, sched_job=00000000259b3ee8
[  353.611825] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x6c80b80, tail=0x6c80b80
[  353.620157] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7300, status=0x58, head=0x6c80b80, tail=0x6c80b80, sched_job=000000000d22c7dd
[  353.668782] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x9eebb80, tail=0x9eebb80
[  353.673516] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7301, status=0x58, head=0x9eebb80, tail=0x9eebb80, sched_job=00000000ed7f3da3
[  353.695429] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x39eab80, tail=0x39eab80
[  353.699737] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7300, status=0x58, head=0x39eab80, tail=0x39eab80, sched_job=000000008afe61d9
[  353.864162] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x48a4380, tail=0x48a4380
[  353.868889] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7300, status=0x58, head=0x48a4380, tail=0x48a4380, sched_job=00000000d7645784
[  353.899062] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x5518380, tail=0x5518380
[  353.903831] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7301, status=0x58, head=0x5518380, tail=0x5518380, sched_job=000000007fd8199f
[  353.941902] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x75b9380, tail=0x75b9380
[  353.946561] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7301, status=0x58, head=0x75b9380, tail=0x75b9380, sched_job=0000000046ff4c79
[  354.039957] panfrost ffe40000.gpu: js fault, js=0, status=UNKNOWN, head=0x690a380, tail=0x690a380
[  354.043350] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7300, status=0x5b, head=0x690a380, tail=0x690a380, sched_job=000000005251cb9c
[  354.070878] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x43ca380, tail=0x43ca380
[  354.075230] panfrost ffe40000.gpu: gpu sched timeout, js=0, config=0x7300, status=0x58, head=0x43ca380, tail=0x43ca380, sched_job=000000005251cb9c
[  354.120595] panfrost ffe40000.gpu: js fault, js=0, status=DATA_INVALID_FAULT, head=0x61e6380, tail=0x61e6380

Ohh, that’s a panfrost issue! What version of the drover are you utilizing?? Try main mesa. I have no problems with main.