How to create a free elec for a game stick 4k lite version 6.0
Not possible. The device has 256MB RAM, but LE needs at least 1GB.
How to create a free elec for a game stick 4k lite version 6.0
Not possible. The device has 256MB RAM, but LE needs at least 1GB.
why is the word: s c i e n t i f i c not allowed in a post XD?
We have a blacklist of buzzwords to block spam posts. We need that protection, and we don't do real science here.
Is there a list of supported GPUs?
No, we don't have a whitelist for PC components (too much work). The best thing you can do is going to the forums main page, and searching for a specific GPU. So you'll get search results from all sub-forums.
No log, no problem.
It switches to a specific frame buffer:
Jan 07 20:45:54.287681 LibreELEC kernel: meson-drm d0100000.vpu: Queued 1 outputs on vpu
Jan 07 20:45:54.287811 LibreELEC kernel: stackdepot: allocating hash table of 131072 entries via kvcalloc
Jan 07 20:45:54.288333 LibreELEC kernel: meson-drm d0100000.vpu: CVBS Output connector not available
Jan 07 20:45:54.289012 LibreELEC kernel: meson-dw-hdmi c883a000.hdmi-tx: Detected HDMI TX controller v2.01a with HDCP (meson_dw_hdmi_phy)
Jan 07 20:45:54.289641 LibreELEC kernel: meson-dw-hdmi c883a000.hdmi-tx: registered DesignWare HDMI I2C bus driver
Jan 07 20:45:54.290201 LibreELEC kernel: meson-drm d0100000.vpu: bound c883a000.hdmi-tx (ops meson_dw_hdmi_ops)
Jan 07 20:45:54.290312 LibreELEC kernel: [drm] Initialized meson 1.0.0 for d0100000.vpu on minor 0
Jan 07 20:45:54.290363 LibreELEC kernel: Console: switching to colour frame buffer device 240x67
Jan 07 20:45:54.290917 LibreELEC kernel: meson-drm d0100000.vpu: [drm] fb0: mesondrmfb frame buffer device
Any chance to test / debug the function of "switching to colour frame buffer device 240x67"? Maybe that's the moment when the screen goes black.
Download the latest img.gz image here:
https://test.libreelec.tv/13.0/Generic/Generic/
Then select that file from USB-SD Creator.
That's a wrong guess (and if you don't know the answer, don't guess).
Hard to resist when logs are filled with so much fake news.
EGL has issues while writing onto canvas (system log):
2025-01-20 15:55:15.543 T:808 debug <general>: EGL Debugging:
Error: EGL_BAD_ALLOC
Command: eglCreateImageKHR
Type: EGL_DEBUG_MSG_CRITICAL_KHR
Message: createImageFromDmaBufs failed
2025-01-20 15:55:15.543 T:808 debug <general>: CEGLImage::CreateImage - attributes:
EGL_WIDTH: 376
EGL_HEIGHT: 464
EGL_LINUX_DRM_FOURCC_EXT: AR24
EGL_DMA_BUF_PLANE0_FD_EXT: 53
EGL_DMA_BUF_PLANE0_OFFSET_EXT: 0
EGL_DMA_BUF_PLANE0_PITCH_EXT: 1504
2025-01-20 15:55:15.543 T:808 error <general>: CEGLImage::CreateImage - failed to import buffer into EGL image: 0x3003
Display More
I think the cause is a GPU driver issue (missing mali regulator, crash log):
Jan 07 20:45:57.901461 LibreELEC kernel: lima d00c0000.gpu: gp - mali450 version major 0 minor 0
Jan 07 20:45:57.921082 LibreELEC kernel: lima d00c0000.gpu: pp0 - mali450 version major 0 minor 0
Jan 07 20:45:57.923010 LibreELEC kernel: lima d00c0000.gpu: pp1 - mali450 version major 0 minor 0
Jan 07 20:45:57.923667 LibreELEC kernel: lima d00c0000.gpu: pp2 - mali450 version major 0 minor 0
Jan 07 20:45:57.924346 LibreELEC kernel: lima d00c0000.gpu: l2_cache0 8K, 4-way, 64byte cache line, 128bit external bus
Jan 07 20:45:57.925304 LibreELEC kernel: lima d00c0000.gpu: l2_cache1 64K, 4-way, 64byte cache line, 128bit external bus
Jan 07 20:45:57.925997 LibreELEC kernel: lima d00c0000.gpu: bus rate = 166666667
Jan 07 20:45:57.926602 LibreELEC kernel: lima d00c0000.gpu: mod rate = 24000000
Jan 07 20:45:57.927225 LibreELEC kernel: lima d00c0000.gpu: error -ENODEV: _opp_set_regulators: no regulator (mali) found
Seems like chewitt is already familiar with that issue:
Re: Missing mali regulator in Amlogic dts - Robin Murphy
Maybe this is helpful:
You have a problem with an add-on. Ask for an update at Kodi forum, where most add-on devs are.
Maybe, depending on your RPi5 hardware revision.
Nope, that doesn't work. For RPi5 you need bleeding edge LE, like a nightly build or the upcoming LE 12.0.2.
Disabling WiFi isn't going to help with the 2.4GHz device when USB 3.0 is the source of issues.
We still don't know that for sure.
Is the idea that there might be interference in the signal, or that it's too far from the remote?
First one. Disable the internal WiFi at config.txt: