Posts by chewitt

The box is probably booting and you can login over SSH to get logs which will explain the issue. Logs will also show what the hardware is and what LE version is installed .. else we can only blind guess at your issue, and generally we suck at that.

crazyturk Are you using a full-size SD card or a micro-SD in an adapter? - I have problems with adapters; most of the ones I have do not work with the box, but one "works enough" for the box to read mainline u-boot in the first 1MB from the SD card, and this will then search and find extlinux.conf on a USB stick to boot the box. Once I was able to boot into LE I could download the image to /storage and write it to eMMC with "emmctool".. and from that point I no longer need the USB stick and SD card arrangement. It helps to watch the boot process; the DB9 port on the rear is wired for UART.

The dedicated Hub image is for my experiements with mainline u-boot (on SD card) which requires the emmc storage to be erased. It works well for WP2 but not Hub for some reason - to be investigated sometime when I have time. If you have vendor u-boot installed still the 'box' image is the one to use.

PCM audio still has some issues with channel mapping but Pass-Through HDMI audio should work fine.

LE uses /flash/config.txt .. use "mount -o remount,rw /flash" to make it editable from SSH.

Boot the RPi4 and check the MAC address for the wlan0 interface, then reboot, and check the MAC again. Does the MAC remain the same, or does it change with every boot?

Being German doesn't grant you a right to consume German Netflix, even if you do pay for the service - it's geo circumvention and this is clearly against their T&Cs.

I'm not seeing anythng in the issue report that says it is an older Atom/ION machine? - but if iit was, ION = nVidia and there is no support for nVidia GPUs in LE11 'Generic' images so you'd need to self-compile the 'Generic_Legacy' version (while this is still possible).

Quote from Niceguy

You're absolutely not interested in other people who want to help.

That's wrong. We love it when users help. We love it even more when they fact-check help instead of making guesses and incorrect statements that cause confusion.

The LE 10.80.0 (Nexus) images in my team share https://chewitt.libreelec.tv/testing/ contain an experimental fix from Martin B for "the noise" that can be experienced with GXBB, GXL and GXM devices using the AIU audio driver. If you have an S905, S905X/D/W/Y or S912 device; please reduce volume on your TV or AVR, update the image, then spend a few minutes navigating around and fiddling with switches and options in the Kodi audio settings page (normally an easy way to provoke that audio problem). Please post back with success or reports of 'the noise' or crackling or other audio oddities you experience?

NB: These images have partially workiing hardware decode again, using the same ffmpeg patch-set as Raspnerry Pi. This is progress, but it means playback is worse in real-terms since ~50% of things now fail, whereas recent images had software-only decode (completely broken hardware decode) where 100% of 1080p media plays within CPU limits. TL/DR; If you're trying to run these images for daily use, you probably want to disable hardware decoding.

It's not a typo, and please stop hijacking threads with advice if you don't actually know the answer.

Kodi has a user interface that's been designed (it didn't just happen that way) to fit onto a TV screen. If you hack the default fonts to be bigger that throws a whole heap of things out of visual alignment and the defaul GUI (skin) will start looking rubbish. Kodi does support other skins, and some of them may allow the font size to be configured, and/or some of them simply use different sized fonts. Experiment .. because that can be done from a remote without needing to override Font files from the SSH console. Plan B .. get a bigger TV. Plan C .. sit closer to the TV screen. NB: If you think our dumbed-down OS is too complicated for you, please feel free to use something else.

It's not impossible to add an NFS server, but it does require some developer skills and buliding a custom image. Have a look at the commits in escalade RetroELEC GitHub repo for more details.

https://github.com/melmorabity/pl…mment-981832577 ?

Quote from dwhacks

I am using the Argon One V2 case. Any ideas?

We're all getting a bit fed up of random problems with Argon One case users. So before we go any further .. remove the board from the case and start with a clean image (or remove all boot configuration you attempted) and see if the issues all magically solve themselves.

i.e. the same place it was in Kodi 18 / 17 / 16 / 15 / etc.

You clearly didn't follow the thread. eSpeak is not an issue. The size discussion was about picotts; If this is 80MB it will not be added to our images (which are often ~125MB total size) and it will need to go into an add-on.

The type of connectors and components used and layout style of the PCB looks older to me, so I'd put my money on it being an Amlogic S812 device. All the Amlogic S912 boards I've seen use PCBs with more layers and much more dense population of smaller components. Another clue / hint on age will be MMYY or YYMM date codes on components, e.g. RAM chips. There's a 1502 printed on the PCB which would be Feb 2015 which would also align with S812 as S912 devices started to show up in 2016. If it genuinely has a Mali T830 chip; it's a HiSilicon Kirin board, but I think documentation typos (or even the wrong documentation in the box) are more likely.

Sure. In a corporate development enviroment a product manager would task the Engineering team to create it and it would get done. In an open-source environment like Kodi where all the developers are working in their spare time as a hobby that style of development doesn't work or happen. Everyone is typically fiddling with a small area of code aligned to a personal interest, and very few people have the time or skilsets to take on large cross-functional refactorings and integrations. There have been some serious attempts at a browser, but it's proving to be a non-trivial task requiring a large effort, and for a varied mix of "real life" reasons, previous attempts have fizzled out.