Hi, I'm pulling my hair out trying to debug my flirc devices. I have 3 flirc's for three different systems, all running debian bookworm. all three are intel nuc's, two of the systems keep throwing the same error. it comes back and usable after a day or so. other usb devices seem unaffected. During that time that specific flirc seem to work fine in a different system. other flirc do not work on the system with the error till some time after(when the orig flirc works too). reboots don't fix it, reinstalling the os doesn't fix it. changed remotes (from sony to off brand) doesn't fix it. flirc_util format, nothing. tried using the flirc program, still no luck.

installed by:
curl apt.flirc.tv/install.sh | sudo bash

needed to run/link for flirc_util to work
# ln -s libreadline.so.8 libreadline.so.6

kernel:

$ uname -a

Linux hostname-here 6.1.0-9-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1 (2023-05-08) x86_64 GNU/Linux

flirc firmware running:

Firmware Version: v4.9.3

SKU: Flirc 2.0 [dori]

Git Hash: 0xcb185bde

 

error being shown:

$ flirc_util unit_test

E] lib/libflirc/firmware/fw_4.0.c fl_ver4_set_interrupt(367): timeout
[E] lib/libflirc/firmware/fw_4.2.c _fl_unit_test(132): error recording test0
Flirc Not Okay

after it comes back:
i tend to need to reprogram afterwards, which i do by flirc_util record and not by loadconfig

 

 

so yeah, i don't know what to do .

 

....

help please

lsusb-v.txt flirc-unit-test-debug-true.txt my_flirc_log.txt

Hi,

I've managed to make it work (1st time) on Debian 12, on a VM, I've also used 'curl apt.flirc.tv/install.sh | sudo bash' but that didn't work for me either.

Have you tried downloading http://apt.flirc.tv/arch/x86_64/flirc.latest.x86_64.tar.gz, extracting and copying this to the bin folder?

I also had to create the symlink for the lib

Created ini with: sudo nano /usr/bin/flirc.ini

Added rules with: sudo nano /etc/udev/rules.d/99-flirc.rules

chapas@Debian12:/lib/x86_64-linux-gnu$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 006: ID 20a0:0006 Clay Logic flirc
chapas@Debian12:/lib/x86_64-linux-gnu$ ls -alh libreadlin*
-rw-r--r-- 1 root root 642K Jan  3 20:49 libreadline.a
lrwxrwxrwx 1 root root   38 Jan  3 20:49 libreadline.so -> /lib/x86_64-linux-gnu/libreadline.so.8
lrwxrwxrwx 1 root root   18 Jun 28 17:29 libreadline.so.7 -> libreadline.so.8.2
lrwxrwxrwx 1 root root   18 Jan  3 20:49 libreadline.so.8 -> libreadline.so.8.2
-rw-r--r-- 1 root root 347K Jan  3 20:49 libreadline.so.8.2
chapas@Debian12:/lib/x86_64-linux-gnu$ flirc_util version
3.27.2
FW Version: v4.9.7
   SKU:     Flirc 2.0 [dori]
   Branch:  release
   Config:  release
   Hash:    0x1DE23EB8
chapas@Debian12:/lib/x86_64-linux-gnu$ flirc_util unit_test
Flirc Okay
 

I've used the flirc_util to map some buttons that I couldn't map on the GUI.

 

Regards,

chapas

I've got the exact same issue. It used to work fine for many days until it one day decided not to, and I can't figure out why for the love of me. It won't register any inputs, nothing at all.

Edited September 9, 20242 yr by Atelier Anna

@Atelier Anna is your Flirc plugged directly into the host or via an extension cable?

If you can, try running the following command at a command prompt and see what comes back:

flirc_util device_log

The output of flirc_util settings will also show version information and the status of any mapped keys.

I tried both. It previously worked happy through an extension cable. I also did a bunch of digging:

• The device does not register any IR signals, so I cannot train it. I tried on both Linux and Windows.
• When reflashing firmware and with IR debugging enabled, it reports something like this:

  <3>hashtable_ready(270): RB table CRC Mismatch: 0x32EF6B1C != 0xFFFFFFFF

  <3>iospirit_eep_init(313): hashtable broken, formatting

Best I can tell, hardware might be toast. flirc_util unit_test fails reliably.