Thank You!
I installed the FLIRC software on my Windows 10 PC from https://flirc.tv/products/flirc-usb-receiver
I then choose "Kodi" from the "Controllers" menu and added each of my keys to config.
Moved the USB dongle to my LibreELEC box and IT WORKS!!!!
Thanks
Greetings-
I am running LE12 on a RPi4. I have recently purchased a FLIRC USB dongle but am unable to connect to the device once it has been installed. I have tried following the wiki entry Infra-Red Remotes but am stopped by the first step.
Each time I try to run the ir-keytable command I receive a "No devices found" error regardless of the flags I use.
# ir-keytable
No devices foundI assumed this indicated that the system has not found the device yet, but it seems to have.
# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 003: ID 20a0:0006 Clay Logic flirc
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub# lsusb -v -d 20a0:0006
Bus 001 Device 003: ID 20a0:0006 Clay Logic flirc
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 [unknown]
bDeviceSubClass 0 [unknown]
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x20a0 Clay Logic
idProduct 0x0006 flirc
bcdDevice 2.00
iManufacturer 1 flirc.tv
iProduct 2 flirc
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x0062
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
(Bus Powered)
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 63
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.01
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 148
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x84 EP 4 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0008 1x 8 bytes
bInterval 50
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 3 Human Interface Device
bInterfaceSubClass 0 [unknown]
bInterfaceProtocol 1 Keyboard
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.11
bCountryCode 0 Not supported
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 55
Report Descriptors:
** UNAVAILABLE **
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Device Status: 0x0000
(Bus Powered)I have tried adding different version of dtoverlay=gpio-ir to /flash/config.txt (with reboots in between) but still no luck, or device found.
I feel that I am missing a step.
Any direction will be helpful
-Thanks
Awake It sounds like that is just the name of the drive. You can rename the drive in Linux (and LibreELEC) with e2label.
Assuming you wish to change drive sdb1 run the following command.
e2label /dev/sdb1 new-label-name-hereIf you don't know what the device to use, you can see them via the df -h command.
You may also rename the drive via Windows by right mouse clicking on the drive and choosing to format it (but reformatting will delete all data on the drive) and entering a new Volume Name.
@arhodiewithsoul, I think your best bet, assuming you have the hardware, is to setup a media server, using Ubuntu or Windows, for the storage of you content then connect to it with LibreELEC via SMB (samba).
This will also allow you to expand your setup in the future easier (ie. a second TV).
As far as the drives spontaneously having this issue, either the system was writing data to the drives during a power outage (most likely) or other event that caused the write to not correctly finish, or the drives may just be getting old.
Piscenois, if you haven't already, please post this issue on the kodi.tv forum; this is a problem with Kodi, not LibreELEC.
Katha-Kombe please provide logs so others may help you trouble shoot your issue.
Have you ran getedid create via ssh?
See the EDID for more information.
If that dose not help, please provide logs so others may help you trouble shoot this issue.
Hi arhodiewithsoul,
It looks like your hard drives are formatted as NTFS and are being marked as "dirty" by the system (meaning the system has decided they are having issues and flipped a flag to have them checked).
NTFS is a Windows format and LibreELEC dose not have the needed utilities to check and repair any problems on these drives.
From your Logs:
Jun 18 18:48:19.535178 MaximusPi systemd[1]: Starting [email protected]...
Jun 18 18:48:19.567347 MaximusPi kernel: ext3: Unknown parameter 'fmask'
Jun 18 18:48:19.567525 MaximusPi kernel: ext2: Unknown parameter 'fmask'
Jun 18 18:48:19.567613 MaximusPi kernel: ext4: Unknown parameter 'fmask'
Jun 18 18:48:19.567675 MaximusPi kernel: squashfs: Unknown parameter 'fmask'
Jun 18 18:48:19.567733 MaximusPi kernel: hfsplus: unable to parse mount options
Jun 18 18:48:19.567797 MaximusPi kernel: hfs: unable to parse mount options
Jun 18 18:48:19.567854 MaximusPi kernel: UDF-fs: bad mount option "fmask=0133" or missing value
Jun 18 18:48:19.570678 MaximusPi kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0xc0856600)
Jun 18 18:48:19.570812 MaximusPi kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 1th superblock
Jun 18 18:48:19.570873 MaximusPi kernel: F2FS-fs (sda1): Magic Mismatch, valid(0xf2f52010) - read(0x0)
Jun 18 18:48:19.570928 MaximusPi kernel: F2FS-fs (sda1): Can't find valid F2FS filesystem in 2th superblock
Jun 18 18:48:19.570982 MaximusPi kernel: fuseblk: Unknown parameter 'fmask'
Jun 18 18:48:19.620671 MaximusPi kernel: ntfs3: sda1: volume is dirty and "force" flag is not set!
Jun 18 18:48:19.620906 MaximusPi udevil[7193]: mount: mounting /dev/sda1 on /media/Persephone failed: Invalid argument
Jun 18 18:48:19.621825 MaximusPi udevil[7189]: mount: mounting /dev/sda1 on /media/Persephone failed: No such device
Jun 18 18:48:19.692860 MaximusPi systemd[1]: Finished [email protected].When you run the check/repair on the drives in windows, it flips the flag on the drive saying all is well now.
Unfortunately this problem may continue to happen with your current setup.
Reformatting the drive will delete ALL DATA on the drive, so you must back it up first (I understand that is not always do-able). You may have to look at serving the data from a different system (windows or a linux distribution that handles NTFS).
What format is the drive in? NTFS does not seem to work well after a while on LibreELEC.
I had a similar problem with a WD Elements drive, I was forced to reformat it to ext4 from NTFS and it has worked perfect since.
Reformatting the drive will delete ALL DATA on the drive, so you must back it up first (I understand that is not always do-able).
On LibreELEC you may run the following once that data has been moved off:
umount /dev/sda1
mkfs.ext4 /dev/sda –L Data1Note the name is used as the mount point, so you may want to keep your old drives name when reformatting it.
This should work fine (running Kodi + TVHeadend client & server on a RPi4).
What problems did you have when you tried to move to a RPi4 last time?
You could also keep the TVHeadend server running on your RPi3 and move to the RPi4 form Kodi & TVHeadend client.
I am using the "Geekworm Raspberry Pi 4 Heavy-duty Aluminum Passive Cooling Metal Case" linked above. It works great, but WiFi does not work well due to the antenna being surrounded by metal.
But I love it because it keeps the RPi4 cool (currently 42.2c) without a fan and it looks nice on the desk.
Yes, this was added in pull request 7412.