Posts by oldie__

chewitt thanks, it is working wow

Set the dirty bit at one external HD (under Win7) by "fsutil dirty set r:" and (as expected) the volume wasn't mounted by LE12.
However, after installing the NTFS-3G driver add-on the volume is mounted correctly and all Kodi file manager functions (move, copy, delete, etc.) are working.

Funny is, that if I set the dirty bit on a normal USBstick, the stick is mounted corectly by LE12 without NTFS-3G driver add-on.
In my opinion that means the new in-kernel-driver doesn't behave consistently and it may still needs some work...

hi ilmich many thanks for the hint!
I did run the system check as suggested and all volumes are now mounted by LE12. Flashed to internal memory, and all is OK

However, I consider that mounting dirty volumes as read-only is more logical and definittely much more user friendly. Alternativelly there should be at least some notification not just silently ignore/drop those volumes. Hope this is just a matter of driver settings...

In my case, the dirty bit was set because we did have several times power outage during playback with Kodi on my Android box (MiBox), but Android seems to ignore this bit. Fortunattely it seems that unplugging the power supply from this LE box during playback doesn't cause this kind of problem.

And one last unrelated question: I noticed that even when the TVbox is powered of from remote control, the external drives continue to run, and stop running only after I unplug the power supply from the TVbox. Is this normal?

ilmich thank you for the fast reply, pls find further down following documents:
1. log from LE12
2. log from LE11
3. DTB's from multitool image extracted with extract-dtb (2 parts)
4. DTB's from rkDumper images extracted with extract-dtb (1 part)
Remarks:
a. On the "tvbox-backup" image created by multitool the last extracted "09_dtbdump.dtb" was ~ 7.5GB in size and triggered an error on my computer, and on the "kernel.img" created by rkDumper the last extracted "04_dtbdump.dtb" was ~ 6.8MB in size and triggered an error on my computer - hence I discarded both of them. All other dtb's are in attached files.
b. Each of my external WD-Elements Desktop HD's does have her own separate power supply.
c. I personally dont't think it is a dtb problem, coz I replaced the dtb's from LE12 with those from LE11 and USB still did not work.

thx
oldie__

respect to the team and the comunity which contributed to these LibreELEC RK222x builds.

Long story short:
I purchased recently (by mistake) a cheap TVbox labeled "MX10 MX Box S - 4K Ultra HD set-top-box". The scope for which I'm using it is mainly to playback videos from external HD's connected via USB.
Because on the original OS (fake Android 13, actually Android 7) Kodi was not able to playback smoothly 1080p videos, I searched for alternatives and landed at LibreELEC.
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.
What I did up to now:
1. Tested LibreELEC [unofficial] Le12 on SD card and it didn't recognize the USB-disks. However, with the latest revision dated 2025-02-18 the WLAN is working, but not the USB.
2. Tested LibreELEC [unofficial] Le11 on SD card and it worked: have LAN, have USB, playback is perfect. Don't have WLAN and file manager functions in Kodi don't work.
3. Backed up the original firmware with rkDumper (under Win10) and MultiTool (from SD card). Tried to extract the DTB's from the img files with extract-dtb v1.2.3 (python/Win10), but I'm not sure if i did it correctly.
4. Flashed LibreELEC [unofficial] Le11 to the internal memory, and it worked same as from SD card, but much snappier.

Remark: If you think it is helpful, let me know and I upload the extracted DTB's or, alternativelly, the IMG's which do contain DTB's.

Strongly hope that you can fix the USB problem, enabling me to upgrade to latest Kodi

And here is the picture of the upper side of the board.

Thanx