Posts by chewitt

Filenames contains "Nova" and "NOVA" and in a Linux case-sensitive filesystem this means two different files. What file is served/returned/downloaded when you click on a file?

Correct, I think the filesystems are marked dirty so you need to fsck them and remount. You can dry-run the fsck if needed, it will check for issues and report, but not make changes.

Please share Pictures, Debug Logs from TVH (or whatever makes the recording) and filesystem output (all to pastebin) to prove that two files of the same name exist in the same filesystem at the same time. That should be impossible, so we need to explain or eliminate that before pointing fingers at Samba server behaving badly in that scenario.

Assuming you are booted from the SSD, i.e. the 2G/4G HDD are not the boot device: umount the mounted drives, fsck the partitions on them, then use e2label to change the disk labels; reboot and the drives will mount with new names visible. My guess is the drives haven't been cleanly ejected/shutdown in Windows so the filesystems are marked as dirty. Linux considers dirty filesystems to be corrupted so auto-mounts them read-only to prevent damage. The fsck will clear the dirty flags and allow things to remount in read-write mode. NB: If you are only going to use the drives in LE you'd be better off with EXT4 partitions; I'd guess Windows drives are NTFS which (until Linux 5.15 appears in LE releases) will be rather slow (fast enough for local playback, but not best performance).

LE version is?

LE 7.0 was built using Ubuntu 14.04/16.04 so OE 5.0 is probably 14.04 material.

Okay, well, if you get stuck with OE things .. ask Q's. Otherwise we'll leave you to it

If folks like bumerc have failed to understand or figure out how Armbian booted in the various CE forum threads I don't stand much chance of a eureka moment (as I know far less then them) .. so I'll pass on the opportunity for a fruitless and frustrating investigation. I'd prefer to spend my limited time for Amlogic fiddling on other dev things. Sorry.

Selling the laptop (eBay or local equivalent of..) and putting the earned funds towards a Raspberry Pi will avoid the forced learning excercise on compiling distro images (fun that it can be). An RPi3B+ or even a much older RPi2 will greatly outperform any 16-year old laptop and can still run current software.

[    3.682808] mmc0: tuning execution failed: -5
[    3.682820] mmc0: ddr50 tuning failed
[    3.682838] mmc0: new ultra high speed DDR50 SDHC card at address 0001
[    3.684028] mmcblk0: mmc0:0001 SD32G 29.1 GiB
[    6.330769] mmc0: tuning execution failed: -5
[    6.330793] mmc0: ddr50 tuning failed
[    6.332062] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    6.332124] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[    6.335152] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    6.335165] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[    6.335197] ldm_validate_partition_table(): Disk read failed.
[    6.337727] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    6.337738] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[    6.340279] blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    6.340290] Buffer I/O error on dev mmcblk0, logical block 0, async page read
[    6.340321]  mmcblk0: unable to read partition table
[    6.344660] blk_update_request: I/O error, dev mmcblk0, sector 61069184 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[    6.347382] blk_update_request: I/O error, dev mmcblk0, sector 61069184 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[    6.347397] Buffer I/O error on dev mmcblk0, logical block 7633648, async page read

^ To me it looks like a bad SD card, or perhaps a power issue making the board unstable, but that's unlikely if the older CE image runs fine.

The codebase of our master branch (tagged as LE11) is likely to be forked into an LE 10.2 release at some point .. depending on how long the wait for Kodi 20.0 is.

The version of Kodi in OE 5.0 (Helix?) is now too old to be useful for anything but playing local media; anything online is not going to run with the ancient packages in the image, and updating "a few" packages will cascade into compile dependencies; getting Kodi to run in the image is a choreographed dance that involves a lot of packages. For that reason lrusak comment is valid; it will be much easier to rework our current codebase (where all the packages have working sources that match the buildsystem) than resurrect OE 5.0.

Commits · chewitt/LibreELEC.tv · GitHub

^ This is a branch based on LE 7.0 which reverts the removal of i386 support in order to run LE 7.0 on a mk1 AppleTV. By now this branch will also be full of packages that are outdated with broken source URLs, but it at least gives you a clue on what was needed back in ~2017 (when I last built that branch). You want a subset of the changes; there are things for AppleTV (which has an old nVidia GPU) that you don't need.

NB: IIRC there's a thread in these forums from a user that created an i386 build for an Intel GPU with Kodi v17 .. and in the threat he links to GitHub sources. I'm being lazy to look .. but I did find it on GitHub in the past.

Quote from ChrisChris23

It seems this new version is not available in auto update

LE (and OE before) have *never* supported auto-update between Kodi major versions. It's available as a manual update, although if you are running LE 9.x please note that we strongly advise a clean install due to the Python2 > Python3 add-on changes in Kodi.

I'm not sure we bothered to create one, because it needs changes which I never got around to submitting before the release was cut. I'm not sure I will have time to do much in the next couple of weeks, but I will see if I can remeber to dig my Cubox-i out and test again.

NB: Right now there's not a huge difference between LE 10 and LE 11 nightlies (apart from the number) .. go see what happens.

C2 has issues with USB generally (even in the old vendor kernels) so YMMV with USB booting.

What GPU is in the laptop? .. this will be the main factor that limits your options with newer images (depending on what's inside)

Add "TimeoutSec=30" to the [mount] section and see if that works? .. i'm not sure what the defaults are.

If that doesn't work, the alternative would be to create a bash script with a working sequence of mount commands, then execute the script from a systemd .service file with right before/after dependencies for Kodi use.

Quote from blackride

Can I fix the dtb file?

In the old forum thread you found the user has a generic S912 image where you must configure the correct dtb file for the box to boot. In the LE10 C2 image I shared everything is correctly preconfigured so the dtb does not need "fixing" to work.

See if "boot=/dev/mmcblk0p1 disk=/dev/mmcblk0p2" work (edit the exlinux.conf). If not, I have no idea what the problem is.