Large numbers of Kodi users configure things from the command-line, so it's a consequence of that. If you're concerned you can install an SSH key and then disable password access.
Posts by chewitt
-
-
calmos Are you using 4K60 'certified' cables and a 5V/3A (or better) PSU?. If it can work the config is done correctly on the RPi4, but you need to have an HDMI cable that will support higher bandwidth and a decent PSU.
-
The dbus error is harmless and seen on 100% of LE installs.
-
I got bored in a hotel lobby this morning and pushed a change to LE master to add “tree” to the system-tools addon. If it doesn’t throw any compile issues I’ll backport the change to LE12 too.
-
Random guess .. You are navigating to the files using a video view and trying to open them as video files (and not finding video)
-
-
Use `/storage/.kodi/userdata/addon_data/service.system.docker/config/daemon.json` for the config files.
-
They probably used the Android image from one device (with all their piracy/malware hacks) and swapped the kernel so it boots another. No idea which way around they are though.
-
What is not the right? it also have a fake android 14.
No clue with these frankensystems. You need to open the box and see what's under the heatsink
-
Create a systemd .mount file; see the example in /storage/.config/system.d/
-
You are welcome to Docker pull and use any container that you like for any purpose that you like, but the project will not be adding torrent apps to the LinuxServer add-ons list.
-
I'll ask for a full debug log demonstrating the problem (as bareley readable screenshot snippets aren't useful) but if this is going to reveal that you're using some pirate IPTV source with several thousand channels (normally anything with thousands of channels is that kind of thing); you can skip head to the bit where we tell you there is no support for pirates and mark the issue as resolved.
-
I didn't use drm-tip, I just picked the single fix patch from GitHub and dropped it and the HDMI (alsa) reorder patch in packages/linux/patches and rebuilt the image; along with a general bump to RPi ffmpeg 6.1.1 sources which is in my Amlogic dev branch.
Using actual drm-tip probably isn't too hard, but you'll probably need to pull sources from GitHub or GitLab using a githash instead of using a release number. See how the Amlogic sources are handled for Linux; it'll be similar.
-
I have little experience with playlists, but have you tried the node editor? Nodes are things like "recently added" and are constructed from content in the library using filters. The add-on is in the Kodi repo.
NB: You have PM regarding the Kodi forum account.
-
LE is largely packaged into two large compressed files (KERNEL and SYSTEM). If anything corrupts them, they cannot decompress and LE won't boot, whereas with a more conventionally packaged OS with thousands of files scattered over the disk; if you corrupt a couple of files it will usually manage to boot and you might not notice the things that failed due to the corruption.
Cards with corrupted filesystems can be fixed with 'fsck' from the USB stick install or another distro. If you can fix the filesystem you can boot from the card again, and/or copy data off the card to make a backup. Cards can also fail with dead memory breaking the filesystems. This cannot be fixed with fsck, so if fsck fails to repair the card or hangs .. you lost data (and learned why taking backups is a good idea) and you need to start over with a new card (or remain on the USB stick).
Boot the RPi4 from USB, then connect the SD card. Then SSH into the RPi4 from Windows, unmount the filesystems on the SD card so they are not mounted (in use) and filesystem check (fsck) them:
Codeumount /dev/mmcblk0p1 umount /dev/mmcblk0p2 fsck -y /dev/mmbclk0p1 fsck -y /dev/mmcblk0p2See how that goes.
-
ARM SoC images like RPi5 intentionally have no "installer" function and there's no tooling to create boot media from inside the OS (as there's not really a requirement to do that) but it's possible:
Codecd /storage wget https://releases.libreelec.tv/LibreELEC-RPi5.aarch64-12.0.0.img.gz umount /dev/mmcblk0p1 <= Unmount existing partitions gunzip -c LibreELEC-RPi5.aarch64-12.0.0.img.gz | dd of=/dev/mmcblk0 bs=1M umount /dev/mmcblk0p1 umount /dev/mmcblk0p2 shutdownThis sequence ^ assumes the SD card is pre-formatted with a single partition (which is usually the case). LE auto-mounts the default partition(s) so you must unmount them before writing data to the card.
After running 'shutdown' remove the USB, leave the SD in, and power on again. If all went well it should boot from the card.
-
-
This just tells me the issue reported in the other thread is either PEBKAC or something is weird with your board.
