[Flirc not recognized by Win 7 after reboot...]

On 9/9/2019 at 9:52 AM, jason said:

I got this mother fucking bug. That was rough. I’ll post an update for you guys tomorrow. 

Thanks to @dborn and @putefabio for the excellent help in letting me use their resources. 

Nothing more satisfying than nailing a bug like that! Thanks to all involved.

[Flirc not recognized by Win 7 after reboot...]

On 5/31/2019 at 5:48 PM, dborn said:

Ok @jason, I think I figured out what is causing this... I decided to take advantage of my 5 FLIRCs and several computers to swap around different FLIRCs on different computers.

It looks like it's an incompatibility between an (older?) BIOS and the newer FLIRC firmwares. The problematic FLIRC actually works fine IN ALL MY OTHER COMPUTERS. I even have another computer that happily uses the newer firmware! (most recently acquired FLIRC)

@dborn nice find. My machine with the fault is also an older box which uses BIOS rather than EFI.

[Flirc not recognized by Win 7 after reboot...]

On 5/16/2019 at 6:14 PM, jason said:

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. 

 

nemo.release.bin 53.19 kB · 2 downloads dori.release.bin 53.06 kB · 2 downloads

@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?

Many thanks

[Flirc not recognized by Win 7 after reboot...]

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?

 

Thanks