+- PINE64 (https://forum.pine64.org)
+-- Forum: Quartz64 (https://forum.pine64.org/forumdisplay.php?fid=166)
+--- Forum: Linux on Quartz64 (https://forum.pine64.org/forumdisplay.php?fid=168)
+--- Thread: Armbian and LibreELEC and AltLinux for Quartz64 (/showthread.php?tid=16312)
RE: Armbian for Quartz64 - igorp - 03-23-2022
Daily test builds: https://imola.armbian.com/dl/quartz64a/nightly/
RE: Armbian for Quartz64 - balbes150 - 04-01-2022
New versions 20220331 with kernel 5.16.18 and 5.17.1
RE: Armbian and LibreELEC for Quartz64 - balbes150 - 04-04-2022
Test version of Libreelec for Quartz64.
https://disk.yandex.ru/d/nLZ6UCxUpWMMUQ
Please note, there is no bootloader in the image, the launch works only when using new versions of u-boot from Armbian. If you have the Armbian version installed in eMMC, you can use any media (SD card or USB media) to run LE. Or use a bundle of SD card with Armbian + USB media with LE. At the moment there is a problem with HW decoding, so you need to disable hardware DRM in the player settings. The capabilities of the rk3566 processor are quite enough for software decoding up to 1440p, I checked different videos, they work without brakes. I hope to solve this problem soon, because HW is already working on Station P2\M2, I need to find what is missing in DTB for Qurtz64a.
RE: Armbian and LibreELEC for Quartz64 - shaggy013 - 04-04-2022
Great if i found my clock back
i try a attempt
perhaps
&vpu {
status = "okay";
};
&vdpu_mmu{
status = "okay";
};
is see that you patch that in k356x.dtsi but not okay or disabled in the device dts .
but that dont explain why p2/m2 works and quartz not
RE: Armbian and LibreELEC for Quartz64 - balbes150 - 04-04-2022
(04-04-2022, 06:51 AM)shaggy013 Wrote: Great if i found my clock back
i try a attempt
perhaps
&vpu {
status = "okay";
};
&vdpu_mmu{
status = "okay";
};
is see that you patch that in k356x.dtsi but not okay or disabled in the device dts .
but that dont explain why p2/m2 works and quartz not
Adding parameters does not change anything (they are already included). I think the reason is rk809 != rk817 and you need to look at the code. After playing with the DTB parameters, I get "static noise" in cases where HW decoding should work.
Updated the LE version. The HW decoder works, but you need to switch the DPM plan mode to EGL in the media player settings.
RE: Armbian and LibreELEC for Quartz64 - balbes150 - 04-05-2022
I checked running the latest versions of AltLinux on Quartz64.
The system starts up and works normally. The startup principle is similar to the Libreelec startup mechanism described above.
For those who have Armbian installed on eMMC with support for launching any systems from USB \ SD, the launch is very simple. Download the image, unpack and burn the image to a USB\SD device, connect to Quartz64 and turn on the power. The system starts automatically.
Please note, this is initial support, the initial launch before the image appears on the screen can take up to 30-60 seconds.
https://disk.yandex.ru/d/7efAT4uD6VEpxw
RE: Armbian and LibreELEC for Quartz64 - shaggy013 - 04-05-2022
well there are some diffrence between a rk809 and a rk817 boost, a switch etc
and some board dont even have one of them
and why the strange uboot construction future spi thoughts ?
nice more distro's
with a box-demo dts and the ir and vfd in the overlay you can get a lot of tvboxes happy
https://github.com/warpme/minimyth2/commit/76fcc06d8f0f668e8ddd115282dcecfcea8938c9#diff-9230cfcfe16424c9af1d66e198477fcfe9073a19b17930218e9081cd0af867cd
if i can reanimate my board i will check them
RE: Armbian and LibreELEC for Quartz64 - balbes150 - 04-05-2022
Conducted glmark2 tests using the AltLinux system and the regular-workstation-arm image.
When using the default 5.16 kernel, the result is modest, only 25.
But after simply replacing only the 5.17 kernel with files from the latest version of Armbian, the result is 225, very good for the initial launch without optimization.
Code:
=======================================================
glmark2 2021.02
=======================================================
OpenGL Information
GL_VENDOR: Panfrost
GL_RENDERER: Mali-G52 r1 (Panfrost)
GL_VERSION: 3.1 Mesa 22.0.1
=======================================================
[build] use-vbo=false: FPS: 211 FrameTime: 4.739 ms
[build] use-vbo=true: FPS: 234 FrameTime: 4.274 ms
[texture] texture-filter=nearest: FPS: 371 FrameTime: 2.695 ms
[texture] texture-filter=linear: FPS: 374 FrameTime: 2.674 ms
[texture] texture-filter=mipmap: FPS: 371 FrameTime: 2.695 ms
[shading] shading=gouraud: FPS: 189 FrameTime: 5.291 ms
[shading] shading=blinn-phong-inf: FPS: 190 FrameTime: 5.263 ms
[shading] shading=phong: FPS: 184 FrameTime: 5.435 ms
[shading] shading=cel: FPS: 185 FrameTime: 5.405 ms
[bump] bump-render=high-poly: FPS: 78 FrameTime: 12.821 ms
[bump] bump-render=normals: FPS: 396 FrameTime: 2.525 ms
[bump] bump-render=height: FPS: 378 FrameTime: 2.646 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 291 FrameTime: 3.436 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 159 FrameTime: 6.289 ms
[pulsar] light=false:quads=5:texture=false: FPS: 348 FrameTime: 2.874 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 143 FrameTime: 6.993 ms
[desktop] effect=shadow:windows=4: FPS: 223 FrameTime: 4.484 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 75 FrameTime: 13.333 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 75 FrameTime: 13.333 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 74 FrameTime: 13.514 ms
[ideas] speed=duration: FPS: 157 FrameTime: 6.369 ms
[jellyfish] <default>: FPS: 203 FrameTime: 4.926 ms
[terrain] <default>: FPS: 23 FrameTime: 43.478 ms
[shadow] <default>: FPS: 146 FrameTime: 6.849 ms
[refract] <default>: FPS: 26 FrameTime: 38.462 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 292 FrameTime: 3.425 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 292 FrameTime: 3.425 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 294 FrameTime: 3.401 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 297 FrameTime: 3.367 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 292 FrameTime: 3.425 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 295 FrameTime: 3.390 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 293 FrameTime: 3.413 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 290 FrameTime: 3.448 ms
=======================================================
glmark2 Score: 225
=======================================================RE: Armbian and LibreELEC for Quartz64 - balbes150 - 04-06-2022
(04-05-2022, 06:30 AM)shaggy013 Wrote: well there are some diffrence between a rk809 and a rk817 boost, a switch etc
and some board dont even have one of them
and why the strange uboot construction future spi thoughts ?
nice more distro's
with a box-demo dts and the ir and vfd in the overlay you can get a lot of tvboxes happy
https://github.com/warpme/minimyth2/commit/76fcc06d8f0f668e8ddd115282dcecfcea8938c9#diff-9230cfcfe16424c9af1d66e198477fcfe9073a19b17930218e9081cd0af867cd
if i can reanimate my board i will check them
>and why the strange uboot construction future spi thoughts ?
I use a machine translator and did not understand what the essence of the question is.
>with a box-demo dts and the ir and vfd in the overlay you can get a lot of tvboxes happy
it won't work, TV boxes are full of shit (I've worked a lot with different ones and I know well what it is). they die after a few months of intensive work. I no longer waste time on this empty work, there is no practical use in it, after a few weeks you realize that you have wasted money and are already buying normal devices with normal support.
I discovered a funny phenomenon. I compared the glmark2 Armbian tests (Ubuntu Jammy and Debian Sid) and Altlinux (I use the same kernel on both systems). Armbian's results are 100, and AltLinux's are 225-370 . I haven't figured out why there is such a difference yet. I have only one instance of Quartz64 with 4GB of RAM, it would be interesting to compare the behavior on models with 8GB of RAM.
Code:
=======================================================
glmark2 2021.02
=======================================================
OpenGL Information
GL_VENDOR: Panfrost
GL_RENDERER: Mali-G52 r1 (Panfrost)
GL_VERSION: 3.1 Mesa 22.0.1
=======================================================
[build] use-vbo=false: FPS: 366 FrameTime: 2.732 ms
[build] use-vbo=true: FPS: 373 FrameTime: 2.681 ms
[texture] texture-filter=nearest: FPS: 637 FrameTime: 1.570 ms
[texture] texture-filter=linear: FPS: 637 FrameTime: 1.570 ms
[texture] texture-filter=mipmap: FPS: 646 FrameTime: 1.548 ms
[shading] shading=gouraud: FPS: 268 FrameTime: 3.731 ms
[shading] shading=blinn-phong-inf: FPS: 270 FrameTime: 3.704 ms
[shading] shading=phong: FPS: 262 FrameTime: 3.817 ms
[shading] shading=cel: FPS: 266 FrameTime: 3.759 ms
[bump] bump-render=high-poly: FPS: 108 FrameTime: 9.259 ms
[bump] bump-render=normals: FPS: 716 FrameTime: 1.397 ms
[bump] bump-render=height: FPS: 682 FrameTime: 1.466 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 473 FrameTime: 2.114 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 201 FrameTime: 4.975 ms
[pulsar] light=false:quads=5:texture=false: FPS: 637 FrameTime: 1.570 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 185 FrameTime: 5.405 ms
[desktop] effect=shadow:windows=4: FPS: 561 FrameTime: 1.783 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 82 FrameTime: 12.195 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 82 FrameTime: 12.195 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 75 FrameTime: 13.333 ms
[ideas] speed=duration: FPS: 255 FrameTime: 3.922 ms
[jellyfish] <default>: FPS: 305 FrameTime: 3.279 ms
[terrain] <default>: FPS: 23 FrameTime: 43.478 ms
[shadow] <default>: FPS: 175 FrameTime: 5.714 ms
[refract] <default>: FPS: 26 FrameTime: 38.462 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 499 FrameTime: 2.004 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 495 FrameTime: 2.020 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 500 FrameTime: 2.000 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 501 FrameTime: 1.996 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 490 FrameTime: 2.041 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 496 FrameTime: 2.016 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 498 FrameTime: 2.008 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 491 FrameTime: 2.037 ms
=======================================================
glmark2 Score: 372
=======================================================RE: Armbian and LibreELEC and AltLinux for Quartz64 - shaggy013 - 04-06-2022
Ow i mean with booting from usb etc with the armbian uboot on a sd or emmc for le , what is the use of that ? , to force armbian with le on a device
and the only thing i could think of is a special uboot for on a spi
yeah tv-boxes world is lot of bad products , it was just a thought
they had 1 or 2 months ago a discussion about glmark and from what i get from that is to use the same version on both distros wayland,xorg
https://repology.org/project/glmark2/packages
lot of glmark2 2021.02 versions
and sadly i cant say i have 4Gb
DDR Version V1.11 20211103
ln
unknown device
error
ERR
once i figured that issue out power or memory
, i would glad to check it for you