It's entirely possible that tx6 mini variant has different remote as tx6. Unfortunately, firmware, which manages suspend/resume, doesn't have ability to change IR keys on the fly. If you can manage to figure out IR protocol and scancode of power button, I can provide special build image (for now). Fortunately, it's not that hard. Connect over ssh, execute ir-keytable -t, press power button and copy&paste output here. Note, I don't have any board around me currently, so this command may not be complete.
Posts by jernej
-
-
To all,
there were quite some requests in the past to add option for waking up board via HDMI CEC. Currently I have working code for A64, but there should be no problems porting it to other SoCs.
Are there any volunteers for testing this functionality? If so, please give me exact board name. Note, it can't work on some boards (it must have external 32 kHz crystal).
-
Do you know if other drivers can works with Allwinner
What other drivers? It's Linux policy to have only one driver per peripheral. If you mean vendor driver, which is not upstream, it might work but it's totally useless because it exposes fbdev interface, not drm.
I'll work soon on similar issue on H616, where 2160p@60 doesn't work at all. Maybe I'll discover something that's common to both chips (Allwinner peripheral changes are usually incremental).
-
Images updated to latest libreelec-10.0 branch with addition of following TrueHD MAT fix: https://github.com/xbmc/xbmc/pull/20361
-
This is completely separate issue. Your configuration won't be supported until some developer gets hand on that board and implement support (which may be never).
-
2160p@60 on Allwinner H6 doesn't work with all displays. For example, it works with my monitor but not TV. I haven't discovered why is that so, unfortunately. It should be driver bug, not HW.
-
I plan to add support for all 3 wifi variants eventually. It's possible to utilize front display already, if you add device tree overlay to enable I2C bus and then writing some userspace script to drive it. If you want, I can give you more information how to do that.
-
HW VP9 decoding on H6 is almost useful. ffmpeg support must be reorganized, but for those who would like to try (mostly relevant for YouTube playback), update file is here:
http://jernej.libreelec.tv/test/vp9/LibreELEC-H6.arm-11.0-devel-20211019202307-9f06af3.tar
Sources: https://github.com/jernejsk/LibreELEC.tv/commits/vp9-test
-
-
No, this is the first time I hear it. What kind of restart is it? Only Kodi or whole system? If only Kodi crashed, you should have crash logs.
-
Good question why there is no board specific files. Fortunately, for your test, you can use generic H3 update: https://test.libreelec.tv/LibreELEC-H3.a…012-0cb023d.tar
-
-
Issue confirmed on OrangePi Plus2E with current master. It used to work not so long ago. I'll take a look.
-
H313 is afaik same as H616, with less memory supported (2 GiB vs. 4 GiB). Anyway, neither are supported by upstream Linux, so there is nothing to help with creating DT. Patches exist for H616, but DT parts are subject to change.
-
-
I suspect that problem is not with decoding as it should switch to SW decoding automatically for unsupported formats. Kodi 19 doesn't switch rendering method if resulting format can't be rendered using DRM planes (v20 will most probably support this). Try set EGL rendering method for DRMPRIME (in such case, DRMPRIME decoder/renderer has no benefit) However, as chewitt says, it will be a slideshow.
-
Ok, thanks for confirmation. I also tested latest nightly image on brand new OrangePi 3 board today. I get exactly the same issues with the fresh board, so boards most likely work as they should.
I'll PR fixes to master and LE10 branch as temporary fix. I have yet to figure out what to do exactly for upstream Linux.
-
yes, clue is in first post here: Nightly images for A64, H3, H5, H6 and R40 boards