lima driver (used for mali450) doesn't support devfreq yet, but it's worked upon. Currently it's expected that reasonable defaults will be set either by bootloader or DT (if possible).
Posts by jernej
-
-
Is there current problems with video decoding on the OPI3?
No. Press "o" during playback and check which codec it is and if it is HW or SW decoded. Chances are that you're using unsupported codec and it's decoded in software. That can happen with YouTube plugin now that more and more video streams are VP9 coded. While H6 technically supports HW decoding VP9, it will take a while before it becomes implemented.
-
Maybe I can install the image you propose on my board?
no, it won't work. You have right image already. Part above quote was target to OrangePi PC2 owners in general. I guess I should make two separate posts, sorry for the confusion. YT addon is pain to set up currently, I spend few hours yesterday. Just try python3 6.7.0 beta1 from here: Release 6.7.0-dev · jdf76/plugin.video.youtube · GitHub
-
Please test latest OrangePi PC2 (H5) image:
LibreELEC-H5.arm-9.80-devel-20200308081621-cfb1324-orangepi-pc2.img.gz
If it is good enough, it will be merged into official LibreELEC git repository and nightly images will become available soon thereafter.
I'm having trouble with logging in to the YouTube add-on:
LoginExcepiton: [401] deleted_client ...
The OAuth client was deleted
What can I do to fix it?
Only current solution for YT plugin is to create your own keys. Just follow Personal API Keys · jdf76/plugin.video.youtube Wiki · GitHub I think default keys were revoked by Google. Note: If you did that already some time ago, it's possible that you have to re-create them. My 2017 keys didn't work. Additionally, I had to update to 6.7.0-beta1 due to sign in issues.
-
Not that I know of. We don't store nightly images. Maybe someone has it and can upload it. But just FYI, it won't have all the improvements, especially around video decoding.
-
For example, where do the patches happen? Rendering path? decoding?
There are several patches responsible mostly for video decoding and hdmi audio, but also a few others. Check all patches in projects/Allwinner and in ffmpeg package for v4l2-request api. There is also Kodi patch which makes sure that highest GUI size is 1080p. You really don't need better GUI resolution, which would just slow down everything. Videos are still rendered at 4K.
Do I have to check out libreELEC build system to learn about these details?
Not sure how else you will get those patches and needed build switches to activate them.
Strangely, both Kodi's system information telling that it's all panfrost rendering.
GPU != VPU and no, videos are not rendered by GPU in LibreELEC.
-
Will removing "quiet" from extlinux.conf make it more verbose?
yes
-
Deinterlacing (Sky Football) doesn´t. But this will hopefully implemented?
Yes, I have proof of concept prepared, but there are some issues to be fixed before it becomes useable
-
I thought someone might ask for that
This is "go to" debugging tool, especially for boot issues.
-
natumbri can you provide log from serial console?
-
-
foxyc partial logs don't count. Note that it should be debug log. You can enable it by hand by creating /storage/.kodi/userdata/advancedsettings.xml with following content:
<advancedsettings>
<loglevel hide="false">1</loglevel>
</advancedsettings>
full dmesg output would be also useful.
-
I really don't know what might be wrong. You said RPi worked ok in such case? Debugging drivers is not easy - I'm using separate sd card with ALARM rootfs (arch linux for arm) and modified U-Boot to boot kernel over network. Then I can modify kernel, build it, boot it over tftpd and test it.
-
aelray dmesg shows that HDMI is always in disconnected state. Then it's no wonder why you don't get any picture. Just to be clear, is HDMI cable actually connected to the board and only TV is off? That case should work as I often boot it in such way. However, if you plug HDMI cable later, when board is already booted, then I imagine there would be problems, but I don't plan to work on that anytime soon.
-
This is a single-core system, I believe.
Oh, I mixed up few SoCs. That's strange then. You can always press "o" during playback to check if video is HW decoded or not.
However I did get to dmesg output through ssh1, and there is more
Nothing strange here. But it kernel actually crashed, you shouldn't be able to get ssh connection. Is there any file with "kodi_crashlog" in same folder than normal kodi log?
-
That is odd then, because the OSD reports CPU significantly below 100% when stuttering like that, typically 40-60%
Maybe ffmpeg decode mpeg4 only on one core.
dmesg: It seems that after Kodi starts up, the output on UART stops. Is that intended (where should I get it, then)?
That strongly suggest that Linux crashes. Can you add "
ignore_loglevel" to kernel command line in extlinux.conf, along with previous modifications we talked about? -
FPS are reported only for UI at the moment, so this is surely lower for menus (not much is going on) and it doesn't match video playback. mpeg4 is slow because there is no HW acceleration and it's decoded by CPU. I have no idea what's going on with H264. For that, I would need at least Kodi debug log and dmesg output.
-
It's always only happening when unplugged. So if started without hdmi plugged I can't just plug it in, but have to restart.
Yeah, I imagine this could be a problem, but I'm sorry to say that this is not really a priority to fix.
