Posts by HiassofT

  • RPI4 - Problems with USB3 HDD - Crash after a few hours

    Thanks for dmesg, couldn't spot anything unusual except for the warnings you posted.

    Can you check if the VIA USB firmware is up to date (in LibreELEC Settings->Update)?

    It could be that your drive is acting up or dying, hard to tell though - haven't seen your specific issues yet and 2 WD drives (3.5" MyBook and 2.5" MyPassport) are working fine here on RPi4/USB3.

    so long,

    Hias

  • RPI4 - System switches off in the evening

    The service.tvh.manager addon is the culprit:

    Code
    2020-04-16 22:03:48.401 T:2700940144 NOTICE: [service.tvh.manager] Service was running w/o user activity
 2020-04-16 22:03:54.453 T:2700940144 NOTICE: [service.tvh.manager] Instruct the system to shut down using Application

    Check the addon settings or just uninstall it, not exactly sure what this addon is useful for.

    so long,

    Hias

  • Slow USB3 ntfs/smb write Speeds

    Check if ntfs-3g's big_writes option is set - you should see it via "ps ax | grep ntfs".

    This option is known to speed up writes a lot and it's enabled by default in LibreELEC.

    Code
    xbmc:~ # ps ax | grep ntfs
684 root 0:00 mount.ntfs /dev/sdc1 /media/Sat-Hias -o big_writes,fmask=0133,uid=0,gid=0,utf8

    so long,

    Hias

  • Remote woes after updating to 9.2.1

    Thanks for reporting back, glad it's working now! The bugfix will be in future LE releases, we already added it to our repository.

    KEY_SLEEP and KEY_WAKEUP are remapped via eventlircd, changing that is a bit tricky.

    Since you got lircd working it might be best to just disable all input from the device and let lircd handle everything - then you can also easily change button mapping.

    Add the following lines to your 99-zotac udev rule file, that will prevent eventlircd from picking up the input from the remote:

    Code
    ACTION=="add", SUBSYSTEM=="input", KERNEL=="event*", \
ATTRS{idVendor}=="0471", ATTRS{idProduct}=="20cc", \
ENV{eventlircd_enable}="false", ENV{LIBINPUT_IGNORE_DEVICE}="1"

    You'll then also need to prevent xorg from picking up the input, you can do that by creating a /storage/.config/xorg.conf file, that will then be used instead of the default xorg.conf files in /etc/X11. Pick the one matching your graphics card and add the inputclass block from the linked kodi thread there.

    so long,

    Hias

  • Cross compile addon

    Basically yes. If in doubt better also run "scripts/clean" with both packages after changing PKG_VERSION or if you want to rebuild both. Otherwise game.libretro.uae might not pick up a libretro-uae change.

    so long,

    Hias

  • Cross compile addon

    After you ran "scripts/screate_addong game.libretro.uae" you should have the zip in target/addons/... (you need to get down a few directory levels there).

    scripts/build only builds the binary but not the addon zip (that's what create_addon is for).

    BTW: If you rebuild the addon after some changes you either need to remove the target/addons/... folder(s) or set ADDON_OVERWRITE="yes" in ~/.libreelec/options - otherwise it won't re-create a zip with the same version number

    so long,

    Hias

  • Cross compile addon

    The kodi addon is called game.libretro.uae and you have to use that in the create_addon call.

    The game.libretro.uae addon package depends on the libretro-uae package which will be built automatically if you compile the addon.

    To manually compile libretro-uae you have to use scripts/build

    so long,

    Hias

  • Remote woes after updating to 9.2.1

    You can drop the xorg.conf change (not needed as the input device will be grabbed by eventlircd anyways) and the RUN+= you added to the udev rule (that was only needed by fernetmenta's ancient upstart setup - it's not relevant to LE).

    The zotac_repeat error seems to be the real issue here. It's a bug in lirc LIRC / Tickets / #327 plugin zotac broken

    lirc is pretty much unmaintained these days but the bug (and fix) was quite obvious. Could you test with this build?

    LibreELEC-Generic.x86_64-9.2-devel-20200408115852-106a54a.tar

    BTW: if you restart lircd via systemctl you also have to restart lircd-uinput. Better not do that but just reboot, that's safer :)

    so long,

    Hias

  • How to config udevil to auto-mount usb drive and create a Samba share for it?

    If you have a power issue then you need to fix that.

    Self-powered hard drives have always been problematic, especially on RPi1. Either use a powered USB hub or a drive with it's own power supply.

    Keep in mind that if you don't fix the power issue the data on the drive could get corrupted - so interpret these mount issues as a strong warning sign that you have an urgent problem to fix and that you have been quite lucky so far that the data on your drive survived without damage.

    so long,

    Hias

  • Remote woes after updating to 9.2.1

    Thanks for the detailed test info!

    The patch you linked never made it upstream and as it was constantly breaking with kernel updates we had to drop it.

    The "topseed" HID driver seems to be rather similar to the old one (using the same 0xffbc vendor page and almost identical keycodes) so you could try binding this driver to your IR receiver. mceusb is a completely different thing and won't work at all.

    An alternative would be to use the zotac driver in lirc, see this older thread for more info [xbmcbuntu] [SOLVED] some buttons not working PHILIPS MCE USB IR Receiver-Spinel plus

    The lirc zotac driver is already shipped with LibreELEC so you can skip all the compilation stuff in that thread. But there are a couple of things to be aware of:

    You may need to add "usbhid.quirks=0x0471:0x20CC:0x10" to the end of kernel command line (in /flash/syslinux.cfg or /flash/extlinux.conf on X86) to get the /dev/usb/hiddevX device).

    As mentioned in the thread the udev rule has to be modified for newer kernels, in LibreELEC creating a /storage/.config/udev.rules.d/99-zotac.rules file with the following content should work (this will give you a /dev/remote symlink as the hiddevX number may change)

    Code
    SUBSYSTEM=="usbmisc" , ACTION=="add", ATTRS{idVendor}=="0471", ATTRS{idProduct}=="20cc", SYMLINK+="remote"

    Then, to use the zotac lirc driver you have top copy /etc/lirc/lirc_options.conf to /storage/.config/lirc_options.conf, edid it and change driver from "default" to "zotac" and device from "/dev/lirc0" to "/dev/remote"

    Finally copy the lircd.conf file from that thread to /storage/.config/lircd.conf and reboot.

    If you get double buttonpresses from the previous working buttons just comment out these button/keycode lines in the lircd.conf file and only leave those with 0xFFBC... codes in there.

    so long,

    Hias

  • How to config udevil to auto-mount usb drive and create a Samba share for it?

    See the configs and scripts in our repository.

    Basically we have a udev rule LibreELEC.tv/95-udevil-mount.rules at master · LibreELEC/LibreELEC.tv · GitHub that determines which devices should be auto-mounted and then starts the udevil-mount@ systemd service LibreELEC.tv/[email protected] at master · LibreELEC/LibreELEC.tv · GitHub

    This service calls the samba-autoshare wrapper script LibreELEC.tv/samba-autoshare at master · LibreELEC/LibreELEC.tv · GitHub which in turn calls the samba-config script LibreELEC.tv/smbd-config at master · LibreELEC/LibreELEC.tv · GitHub to (re-)generate the samba config file and then sends a HUP signal to smbd so samba re-reads the config file.

    The share name is identical to the mount-directory in /media which is handled by udevil (using the filesystem label, if present).

    so long,

    Hias

  • The pain with the ir remote

    It might be best to check with a fresh install on a spare SD card. Could well be that you carried over some outdated config/scripts (autostart.sh, .config/udev.rules.d, .config/lircd.conf etc) that's now interfering.

    The only thing you need to change on a fresh install is adding the "dtoverlay=gpio-ir" line to config.txt - then Microsoft MCE (and Xbox 360) remotes should just work.

    If you're not getting pulse/space from ir-ctl -r then either some script/config/addon/... is messing with GPIO configs or it's the hardware.

    Be especially wary of addons that uses the hacky pi-gpio library or config.txt settings/overlays that enable pwm (which uses the same GPIO as your IR input).

    so long,

    Hias