Posts by HiassofT

Quote from mglae

Code

2020-04-12 06:47:51.414 T:2320466800  NOTICE: ADDON: service.bluetooth-audio v9.2.0.102 installed

Bluetooth Audio Device Changer is setting the defined default audio device when starting. Change the addon setting.

Well spotted, this is most certainly the culprit.

forget my comment regarding librespot, that addon is probably fine.

so long,

Hias

Your hifiberry card seems to be detected fine.

However you have a lot of pulseaudio errors in your log and seem to be using the librespot addon. Please try with the librespot addon removed, if that fixes audio device in kodi it's best to ask in the librespot thread.

so long,

Hias

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:

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

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

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

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

Probably the user hit the "like" button by accident and later noticed his mistake so hit the button again to remove the like. Or he removed the like by accident. That can happen quite easily esp on a mobile device.

so long,

Hias

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

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

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)

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

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

This is a known issue with 1GB RPi4s, see this thread RPI4 on Libreelec 9.1.502 thumbnail/pictures problems with infos how to work around the issue.

so long,

Hias

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

Here's the default config.txt for RPi4: LibreELEC.tv/config.txt at libreelec-9.2 · LibreELEC/LibreELEC.tv · GitHub

When editing it on a PC make sure you configure the editor to use Unix line endings, not windows line endings.

so long,

Hias

Quote from Da Flex

Sure? Isn't it an MCE remote, which needs LIRC?

No and No.

First of all MCE has become a rather generic term and a lot of remotes that don't use the original MCE remote protocol and scancodes have been marketed under that term.

The original MCE remotes (plus scancodes) are supported out of the box with in-kernel/ir-keytable decoding via the rc6_mce keymap.

The Xbox 360 remote uses the rc6/mce protocol as well but uses different scancodes so it needs a separate keymap (to map scancodes to keycodes) - see LibreELEC.tv/xbox_360 at libreelec-9.2 · LibreELEC/LibreELEC.tv · GitHub

To make things easier for users we use a special multi-keymap by default so that the original Microsoft MCE remote, Xbox 360 and Xbox One keymaps are used instead of only the default rc6_mce keymap - see LibreELEC.tv/options at master · LibreELEC/LibreELEC.tv · GitHub

Lirc is only needed for a few, rather odd, remotes that aren't supported by in-kernel decoding (which will become even fewer in LE10 where we support BPF protocol decoders via ir-keytable).

so long,

Hias

Quote from Da Flex

No, it's essential. You don't need config.txt options to start LIRC. Download your fitting lircd.conf here.

uh, no. No lirct.conf should be needed, the xbox 360 remote should be supported by in-kernel decoding out of the box.

so long,

Hias

Quote from userfame

I'm more confused now after reading the wiki because It talks about a lot's of confusing things but doesn't tells me how I could use my remote which already worked out of the box in the past

The wiki page contains a very detailed step-by-step troubleshooting section Infrared Remotes [LibreELEC.wiki].

Please follow the steps there and post the details what exactly doesn't work. Creating a poll but not providing any info isn't helping much in your case (unless you only want to rant).

so long,

Hias

If you use kernel-level IP configuration you have to pass in all settings (netmask, gateway, DNS/NTP server etc). See the documentation of the ip= setting in linux/nfsroot.txt at rpi-4.19.y · raspberrypi/linux · GitHub

Connman interferes badly with disk/storage on NFS so it is disabled automatically in LE 9.2.1 when kernel ip configuration is used.

so long,

Hias