Recommended Posts

I purchased the Flirc Jan 11/19 and it was working great. I have a dedicated Win 7/KODI HTPC that I use it in. I've setup batch files so that I can start Flirc then Kodi on bootup. Since the latest round of Firmware/Software updates, this Flirc device comes up as unrecognizable USB device by the OS when ever I do a restart of the PC.

I now have to unplug then replug the Flirc back into the PC in order for it to be recognize every time I boot up.

Any ideas how I can fix this or revert back to the Firmware prior to this one? I guess in hindsight, I should of left it alone. Why fix something that ain't broke...

Share this post

Link to post

Share on other sites

I have 5 FLIRCs on mythtv linux computers and I've upgraded one FLIRC when I made some changes to the key mappings s and now when I boot the computer (or take it out of sleep), the FLIRC is not seen at all (nothing comes up in lsusb or dmesg) and the only way I've found is also to unplug and replug it back in while the computer is on.

Please let me know if I can do anything to help.

Thanks,

Daniel

P.S. I program all my FLIRCs on a separate Win7 laptop where I also program my Harmony remotes used with the FLIRCs.

Share this post

Link to post

Share on other sites

In reading through the forum, I've seen @jason answer many of those posts in a quick and pleasant manner :)

Right now, I don't dare make any more changes to my FLIRCs and wind up with more problematic units. I also hope they become aware of this problem rapidly.

Like I said earlier, as I have 5 FLIRCs all being used on different computer architectures so once a fix is out, I could cover testing from many potential types of users all by myself!

Anyway, I'm sure this will get addressed quickly. The FLIRC has revolutionized the use of infrared remotes with computers (or any device that can take a USB keyboard) that I can't believe they will ignore this problem once they are made aware. :)

Share this post

Link to post

Share on other sites

In this state, does the GUI detect flirc and no buttons work? Or the GUI doesn't recognize it?

In my case, I program the FLIRC from a Win7 laptop so I plug it in while the PC is already up and running so that works fine.

Once I plug it in my linux PC, when I power it up while the FLIRC is already plugged in (such as after a reboot), it is not seen at all, as evidenced by the total absence of the device in the dmesg log and even after, when using the lsusb command, it's exactly like the FLIRC was not plugged in. If I pull it out then and plug it back in, then it is recognized normally and works just fine.

When I suspend the computer (which I do most of the time), it recovers nicely from that state.

I could try powering up the laptop with the FLIRC already plugged in to see what happens, I haven't tried that yet.

Thanks,

Daniel,

**Update: ok, I tried plugging into Win7 laptop first and then powering up and going into GUI. It was recognized.

I also tried plugging the FLIRC back into the linux computer while it was in sleep, and it was not recognized after waking up the computer. That test may not be relevant but I still tried it out of curiosity.

Share this post

Link to post

Share on other sites

The problem seems to be the OS does not recognize the USB device on boot up. It sees something but unable to recognize it. As I mentioned above, I have to un-pulg and re-plug it back in for the OS to recognize it. This happened after the latest round of software/firmware updates. Worked fine before then.

Share this post

Link to post

Share on other sites

Thanks for the extra info. I haven't been able to reproduce this yet with multiple flircs and pc's and usb ports. I must be missing something. Not to worry, I can always give you guys the old firmware, but let me continue looking, I'm sure I'll find it shortly. Today wasn't the best from a time perspective, I was split amongst a few things, but this is considered red hot urgent.

Share this post

Link to post

Share on other sites

Jason, if there's anything I can do to help (run special firmware version with debugging code, sending you logs from my computer, etc.) please let me know.

I'd have several computers to try it on with either linux or Win7 or Win10.

Yes, as a last resort, going back to a previous firmware would be a way out but it would mean we couldn't upgrade firmwares ever again? It might be a good idea to have on your side a repository of previous firmware versions with a tool to specifically reflash a FLIRC to any previous version. It would certainly help take the pressure off of you guys when a problem arises due to a new firmware release. :)

Share this post

Link to post

Share on other sites

I would like to ask for the previous firmware so that I can recover that failing FLIRC until you guys figure it out. It's been over a month since this issue was first identified. Having to unplug and replug the FLIRC every time the computer is booted or rebooted is getting tiresome.

Share this post

Link to post

Share on other sites

I'm positive it's a firmware issue, but I can't for the life of me reproduce this.

Can you guys post your OS version, your hardware version, whether it's USB 2.0 or 3.0 ports? Any other information. A picture of device manager when it boots into this 'bad state'. Etc.

Here is the latest firmware, upload the correct sku for your hardware. Once I see the problem, I'll have a fix pushed in seconds, but there is no reason for you guys to keep waiting anymore. I'm really sorry.

(nothing connected to any USB port, and there is nothing else than the FLIRC connected)

> dmesg

[ 2.664308] usb 2-6: new full-speed USB device number 2 using ohci-pci
[ 2.745144] ACPI Warning: SystemIO range 0x0000000000004D00-0x0000000000004D3F conflicts with OpRegion 0x0000000000004D00-0x0000000000004D04 (\IP2) (20170831/utaddress-247)
[ 2.745168] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
[ 2.745177] ACPI Warning: SystemIO range 0x0000000000004E00-0x0000000000004E3F conflicts with OpRegion 0x0000000000004E00-0x0000000000004E3F (\_SB.PCI0.SM00) (20170831/utaddress-247)
[ 2.745194] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

Share this post

Link to post

Share on other sites

I think I have the same problem on Win 10. At boot it says "A USB device has malfunctioned".

It doesn't respond to keypresses and when I try to run the GUI shows 'disconnected' in the titlebar. Unplugging and replugging fixes the issue, then it will continue working through sleep and resume, but break again next reboot.

Hardware is an old but stable AMD motherboard/CPU with USB 2.0.

SKU Flirc 2.0 [dori]

GIT HASH 0x93a109d3

Is there anything else that will help you debug? Anything from system event log for example?

Share this post

Link to post

Share on other sites

I'm positive it's a firmware issue, but I can't for the life of me reproduce this.

Can you guys post your OS version, your hardware version, whether it's USB 2.0 or 3.0 ports? Any other information. A picture of device manager when it boots into this 'bad state'. Etc.

Here is the latest firmware, upload the correct sku for your hardware. Once I see the problem, I'll have a fix pushed in seconds, but there is no reason for you guys to keep waiting anymore. I'm really sorry.

@jason Hi buddy, I'm still struggling with this, are the attached firmwares older ones which don't have the issue? Can we flash these without losing our configuration or will we need to reassign buttons etc?