Posts by ilmich

Hi, sorry for the absence. My life has changed recently (my little star was born <3), so my time has been reduced. But I don't intend to abandon this project, I'll just go slower.

supergigi73 Are you trying to boot from the SD card? If so, how did you prepare it? The error is very strange because it stopped during the storage mount phase, which presupposes that the hardware side has detected everything. Maybe it had a problem when it tried to resize the data partition at the first boot, and consequently, then cannot use it correctly. In any case, if you have a copy of the original firmware (or a link where you can download it, I'll take a look)

leap123 Unfortunately, since I don't have the board, I can't, as I never managed to do in the past, verify what happens. In any case, with libreelec-13, I'll switch to a hybrid bootloader (some proprietary blobs and mainline U-Boot, a bit like Armbian), where that board seems to work fine. You have to be patient.

I included support for this board with the help of deleonkikko, who did the tests. But I just bought it because some things are not yet supported mainline (like the 2k connector)

hi oldie__ thanks for the logs

libreelec 11

Feb 16 18:11:14.664106 LibreELEC kernel: ntfs: volume version 3.1.
Feb 16 18:11:14.664699 LibreELEC kernel: ntfs: (device sda5): load_system_files(): Volume is dirty.  Mounting read-only.  Run chkdsk and mount in Windows.
Feb 16 18:11:14.665111 LibreELEC kernel: ntfs: volume version 3.1.
Feb 16 18:11:14.665411 LibreELEC kernel: ntfs: (device sda1): load_system_files(): Volume is dirty.  Mounting read-only.  Run chkdsk and mount in Windows.

libreelec 12

Feb 27 17:26:20.095723 LibreELEC udevil[580]: mount: /var/media/WD ELEMENTS 2-1: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error.
Feb 27 17:26:20.095723 LibreELEC udevil[580]:        dmesg(1) may have more information after failed mount system call.
Feb 27 17:26:20.098361 LibreELEC kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Feb 27 17:26:20.136565 LibreELEC systemd[1]: Starting udevil-mount@-dev-sdc6.service...
Feb 27 17:26:20.150721 LibreELEC kernel: ntfs3: sdb1: volume is dirty and "force" flag is not set!
Feb 27 17:26:20.151416 LibreELEC udevil[597]: mount: /var/media/WD ELEMENTS 5-1: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error.
Feb 27 17:26:20.151416 LibreELEC udevil[597]:        dmesg(1) may have more information after failed mount system call.
Feb 27 17:26:20.163521 LibreELEC kernel: ntfs3: sda2: volume is dirty and "force" flag is not set!
Feb 27 17:26:20.164094 LibreELEC udevil[591]: mount: /var/media/WD ELEMENTS 2-2: wrong fs type, bad option, bad superblock on /dev/sda2, missing codepage or helper program, or other error.
Feb 27 17:26:20.164094 LibreELEC udevil[591]:        dmesg(1) may have more information after failed mount system call.

you should kindly try running a file system check from windows. Libreelec 11 mounts your volumes in read-only mode, the new libreelec 12 ntfs driver refuses to do this.

Quote from meho

There is only one "small" problem called wifi... Wifi works fine with armbian but shows no signs of life in libreelec (using generic image, I don't think others will work). Wifi adapter is Realtek 8723CS.

meho my mistake, it was included in previous releases. I will reinsert it as soon as possible

Quote from oldie__

My problem is that the Le11 versions do recogniize my USB-HD's but the Le12 version doesn't. My HD's are nothing special but normal WD-Elements connected via a 4x USB3 hub.

oldie__ I have to check but I don't often use 'complex' USB devices because since the libreelec 10 builds, I have always had problems without a separate power supply (the USB ports are not powerful enough). In any case please send a log and your dtb

leap123 can you understand if we are talking more or less about the same board? (You may have to open the device). Unfortunately, I don't have all the boards, but I remember that pocng had solved it. If so, I'll try to do the fix you suggested

ml-1 thank you very much for your contribution which I included in my builds!!
I know that the soc can support higher frequencies, but the current ones are the result of many tests and take into consideration the fact that these boxes often have very poor heat dissipation and therefore you could encounter sudden restarts due to excessively high temperatures.

Hi all,

a new build of libreelec 12 available with:

- updated to latest libreelec source
- added Alfawise A95XR1 thanks to ml-1

Cheers
Michele

Quote from ml-1

First, I just want to say thanks for this port!

I'm happy that my work is useful

Quote from ml-1

It made my old device collecting dust worth using again.

Aside from the fun of developing this port, reusing 'old' hardware is one of the goals.

Quote from ml-1

I have an Alfawise A95XR1 so I needed to make my own dtb in order to get leds working but after that it seems to work very well except for HD audio passthrough, it's just silent, but works it well if I disable passthrough for TrueHD and DTS-HD. Other passthrough works fine.

Make sure you have selected the correct device (default could be spdif output). Send a log anyway if you can.

Quote from ml-1

Any chance of getting a95xr1 included in future builds?

Of course, I don't understand if you can do it independently, in any case I need the stock dtb (or a link to download the original firmware)

Quote from dtech

However, ilmich uses mainline kernel (6.x) in his builds where this module is probably no longer usable.

I can try. The Realtek drivers are very similar, so I should be able to make it work with the new kernels, too.

Quote from ihipop

while balbes150 's unOfficial LE uses kernel 6.12.3 (latest stable) , it can boot successfully, so which means it uses a vendor rockchip bootloader?

I don't know where to find the source of those builds but I imagine yes

Quote from ihipop

LibreELEC 11.0 uses kernel 6.1.x (not mainline), LibreELEC 12.0 uses kernel 6.6.x (not mainline)

Libreelec uses the latest LTS version of the mainline kernel (i.e., the official one, not the RockChip one), which is available when the stable version is released.

The 6.12 kernel will (probably) be used in libreelec 13, which is currently still in development.

Quote from ihipop

Is there any official way to install LE to the internal eMMC ?

Official no, so if you have problems (in reality, it's very unlikely that you have them), you may not have support. But if you want to install it in your internal emmc, just write an image of Libreelec (previously saved on a SD card) with dd after starting it from the SD card.

Rockchip CPUs, if they find a bootloader in the internal memory, start with that and possibly try to launch the operating system from the SD card.

but if I remember correctly your vendor's bootloader (which is the one you have with the Android installation) is not able to launch the mainline bootloader (which is the one used starting from libreelec 11) and vice versa. you can see this from the fact that libreelec 10 works instead (because it has the vendor rockchip bootloader) and also the unofficial builds you mentioned.

more information can be found here

Boot option - Rockchip open source Document

the only options I know of are

- install libreelec in your emmc
- delete your emmc so that the board, finding nothing in the internal memory, boots entirely from the SD card

hi FurmanSK if you can, try this build of libreelec 13

roc-3328-cc

where I've added some optimizations that I will send upstream.
I did some testing and it works very well even in 4k. let me know if you notice anything strange.

the main changes are
- ddr4 at 800mhz
- I improved the infrared receiver support by adding some remote controls that I created over time thanks to the users of my build for rk3228
- I increased the gpu frequency to 500mhz
- I enabled the multigen lru in the kernel

the source is here

GitHub - rockchip-with-unofficial-love/LibreELEC.tv at roc-cc-le13-wip

Just enough OS for KODI. Contribute to rockchip-with-unofficial-love/LibreELEC.tv development by creating an account on GitHub.

github.com

Unfortunately, I also had little time this year.

In any case, and without any definite planning, I'm working on some small improvements (having said that the 4k problem is a known problem of the kernel used in libreelec 12, which should be okay with libreelec 13).

I'll keep this thread updated when I have news.

Hi all,

a new build of libreelec 12 available with:

- added RTL8189ES wifi driver (thanks Lochnair for testing)
- various fixes and improvements
- finished porting from libreelec 11
- reintroduced wpa_supplicant as wifi manager (iwd has problems with bad drivers that I have to use)
- updated to latest libreelec source

Cheers
Michele

Lochnair my apologies, the repository was not updated. try again now.

Thank you

Hi Lochnair , try this test build where I compiled the driver you suggested (and added firmware for usb ethernet)

test

Unfortunately we have to go by trial and error because I don't have your device.

Quote from Lochnair

The stock Android is terrible, but LibreELEC seems to run pretty well on it, so thanks a lot!

I'm happy, the work behind it was long and sometimes complicated.

Quote from Lochnair

Ethernet and Wi-Fi doesn't work,

I saw some errors related to missing firmware. Let's see what I can do.

Quote from Lochnair

Ended up dumping DTB from both image and /proc as I wasn't sure if I did it correctly from the image, both attached should they be useful somehow.

they are useful because I could add support to your box too.

Quote from Habitual6824

My Apple type-c to headphone adapter doesn't show up as an audio device in settings. I did check lsusb and it does show up there so not sure what's up. This also happens in LE11. Currently my workaround is to use a cheap optical/coax to 3.5mm converter, which works with the SPDIF output.

After some research, I read that the device actually activates when you connect a device via 3.5mm jack. Can you please try? In the meantime, I'm trying to understand if some drivers are missing.