Posts by chewitt

Creating /storage/.config/samba.conf will not cause a boot failure. That code is relatively unchanged since OE 1.0 days and we would see thousands of forum posts if it were true. The boot message says it cannot find the SYSTEM file in the boot partition (first partition of two used by LE) which is normally because some other process messed with the bootloader config so the partition is wrongly identified or the file is not present or corrupted (cannot uncompress).

I've also tested this out now that I'm not on vacation and (sorry) it doesn't work quite as expected. It's not blocking creation of a directory; samba docs only talk about blocking files so it might be that explicit. Also, blocking a Thumbs.db file that I copy/paste prompts macOS/finder to ask for credentials instead of the copy operation silently failing. It may be easier to let Android do its thing uninterrupted and just run a regular find/delete command via cron instead.

NB: In MacOS you can prevent write of _ and . files: Mac OS X v10.4 and later: How to prevent .DS_Store file creation over network connections - Apple Support so no need to do that with Samba

When you say that BT is no longer working. Was it previously working under an older LE release, or Ubuntu, or ??

Current guess is we're missing the firmware for the BT device. This is easily explained if you came from Ubuntu or an older OE release, but would be an unexplained regression if you were using an earlier LE version.

Looks like we need to update the misc-firmware package to include various newer firmwares. It's an easy fix for LE 8.0.2.

Samba hide Thumbs.db
disable-creation-of-ds_store-files-on-samba-shares

same principle can be used to prevent writing of other folders to the share. To do this in LE rename /storage/.config/samba.conf.sample to samba.conf and modify the shares, then reboot. The modified .conf will be used instead of the embedded (read-only) one if present.

run "dmesg | paste" from the SSH console after a clean boot and share the URL please

I cannot see any evidence of a BT chip in the lspci/lsusb output and dmesg shows nothing about BT devices - the last few lines are standard kernel log spew and don't mean anything. Identifying the chipset inside is the first stage of figuring out what's needed. If you have any output from an OE install that works, it would be useful.

LE is intentionally an embedded/appliance-like OS. If you want apt-get and editable (also means breakable) everything there are several other good distro's to choose from.

Home · Zomboided/service.vpn.manager Wiki · GitHub - Zomboided has a support thread in this forum somewhere

As long as the hdparm command you're wanting to use works from the busybox bash shell (manually test first) that script should be fine. You'll find that Kodi is almost permanently doing something so sending /dev/sda to sleep (assuming it's the boot disk) probably doesn't achieve much.

"dmesg | paste" and share the URL please

Should be fine.

It's time to create a Linux VM on your Windows laptop and learn how to use 'dd' (in Linux) to create disk/partition images. Windows is so completely stupid about multi-partition USB sticks and anything Linux related that this is the easy long-term option.

You can also use the backup function in LE settings which (unless your 16GB card is 95% full) will be several hundred percent quicker than imaging the entire card full of empty space.

Please test LibreELEC-Generic.x86_64-8.0.1.tar and report whether the card works?

Kodi profiles need a major code overhaul and don't really work for this kind of use case. However, in my experience kids watch the same ~5 things over and over and over (and YouTube) so clever Kodi features like central watched status are utterly lost on them. I separate "kids" content at a source level, and manually scrape that one kids source to the new device while other devices use a MySQL config. The kids room has a hardware box that cannot be suspended etc. so I set an overnight cron job to update the library. As long as it gets some artwork kids think the GUI is amazing. They are kids so don't over-think the solution

Try resetting Kodi to defaults. If this does not resolve it, the issue has nothing to do with Kodi. I suspect that's the case anyway because in ~8 years of using Kodi I've never observed what you're describing.

pastebin a Kodi debug log demonstrating the problem please

Estuary does not support changeable backgrounds. You will have to change skin or persuade the Kodi skin developers to add that feature.

Hard reset in the LE settings add-on will fix the problem with this and any other 'build'