Jump to content
Flirc Forums
viperxbr

Flirc not recognized by Win 7 after reboot...

Recommended Posts

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)

This is what I found:

The older firmware FLIRCs (I have 3 out of 5) show this in the dmesg logs (this is from an ACER laptop that accepts the new FLIRC firmware):

[    2.684173] usb 3-1: Product: flirc
[    2.684179] usb 3-1: Manufacturer: flirc.tv
[    3.175146] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.1-1/input0
[    3.178524] input: flirc.tv flirc Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input9
[    3.240745] input: flirc.tv flirc Consumer Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input10
[    3.241127] input: flirc.tv flirc System Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input11
[    3.241493] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1d.1-1/input1

The 2 newer FLIRCs show this:

[    2.657673] usb 3-1: Product: flirc
[    2.657678] usb 3-1: Manufacturer: flirc.tv
[    3.175787] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.1-1/input0
[    3.181080] input: flirc.tv flirc Keyboard as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input9
[    3.240721] input: flirc.tv flirc Consumer Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input10
[    3.241115] input: flirc.tv flirc System Control as /devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.1/0003:20A0:0006.0002/input/input11
[    3.241510] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1d.1-1/input1

[    3.243629] hid-generic 0003:20A0:0006.0003: hiddev1,hidraw2: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.1-1/input2

Notice that extra last line? (hiddev1,hidraw2.../input2) all my other computers are happy with that extra device but not that particular one.

Other computers have varying dmesg output concerning the recognized device, based on the various BIOSes but this last line is the consistent difference between the new firmware and the older one.

Incidentally, the computer with the problem, using an older firmware FLIRC shows this at boot-up:

[    2.910197] usb 2-6: Product: flirc
[    2.910202] usb 2-6: Manufacturer: flirc.tv
[    3.004565] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:04.0-6/input0
[    3.005672] input: flirc.tv flirc as /devices/pci0000:00/0000:00:04.0/usb2/2-6/2-6:1.1/0003:20A0:0006.0002/input/input5
[    3.064504] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:04.0-6/input1

Notice it doesn't identify the "Keyboard", "Consumer Control" nor the "System Control" devices? but it does recognize input,hidraw1 as "USB HID v1.01 Keyboard".

 

Ok, I hope this helps because I think I'm at the end of what I can contribute here ;-)

I guess if no solution is found, I can always swap out an older FLIRC and never upgrade the firmware until this issue is resolved..?

Thanks,

Daniel

P.S. Is it just me but each time I want to log in to this forum, my password isn't recognized and I have to go through the "Forgot password" mechanism. I can then just re-enter the same password again and I am good to go until I log out!?

 

Edited by dborn
Added a link to Jason :)
  • Like 1

Share this post


Link to post
Share on other sites

Here are the specs of the problematic computer:

Acer AR1600/FMCP7A-ION, BIOS P01-A4 11/03/2009

Intel(R) Atom(TM) CPU  230  @ 1.60GHz (family: 0x6, model: 0x1c, stepping: 0x2)

2.5GB RAM

By the way, the Acer laptop used above is actually older (2008) than this AR1600 so it's not just an age thing and also, all my computers (including a very recent top performance model used for UHD video) all use the BIOS (all UEFI turned off for Linux compatibility). This extra new device as seen in my previous post (hiddev1,hidraw2) uses a set of conflicting addresses (0x4D00 - 0x4D04, 0x4E00 - 0x4E3F) which interferes with the normal BIOS operation. Why it seems to work after unplugging/replugging the FLIRC once the computer is operational is beyond me. You guys must play with low-level USB protocols so you should understand what is going on here?

Edited by dborn
Adding more information

Share this post


Link to post
Share on other sites
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.

Share this post


Link to post
Share on other sites

I'm having the exact same issue.  If I start computer and then plug in Flirc, it will work, but if I reboot, it doesn't work.  If I run the Flirc app after reboot, it says the device is disconnected.

FYI, this is the second Flirc device with the same issue.  I bought one a few weeks ago, and returned it thinking it was just a defective unit.  But the replacement I bought does the exact same thing.

I also have another Flirc, that I bought and set up about a year ago (maybe more) that is working just fine.  My comments below describe only my recent experiences, and do not apply to the older, working Flirc device.

I am posting my details (including Ubuntu log entries) in the hopes it will help in finding a solution.

When I installed the Flirc app on my device a few weeks ago, and plugged in the Flirc, the app said there was a firmware update available.  However, IMMEDIATELY after it started the update process, the Flirc device disconnected - and the app became unresponsive.  Then, I rebooted my system, started up the Flirc app again, and this time it immediately jumped into the firmware upgrade and completed it.  NOTE: this happened TWICE - it happened for the device I bought a few ago, and then again when I returned it and bought a new, replacement Flirc.  

Now, as stated above, if I start my computer first, and then plug in Flirc, it will work, but if I reboot with the Flirc device plugged in, it won't work.  If I run the Flirc app after reboot (with the device plugged in), the Flirc app says the device is disconnected.

My system is running a 64-bit version of Ubuntu 18.04.2 LTS, on an AMD Phenom ii x4820, with AMD Cedar graphics card.  Gnome 3.28.2.

The Flirc app states that it is v.3.22.4 with firmware v4.6.3.

After a reboot, the following entries appear in the Ubuntu logs:

10:11:34 kernel: usb usb3-port4: unable to enumerate USB device
10:11:34 kernel: usb usb3-port4: unable to enumerate USB device
10:11:34 kernel: usb 3-4: device not accepting address 5, error -110
10:11:23 kernel: usb 3-4: device not accepting address 4, error -110
10:11:12 kernel: usb 3-4: device descriptor read/64, error -110
10:10:56 kernel: usb 3-4: device descriptor read/64, error -110

Hope that helps.

Let me know if you need any additional info.

Hoping for a quick resolution.

 

 

Share this post


Link to post
Share on other sites

@San Diego MRVCan you check in your logs  (dmesg) if you get anything about "ACPI Warning: System range xxx conflict"?

I believe this is the root cause of the problem.

Daniel

Share this post


Link to post
Share on other sites

@dborn, I checked dmesg logs, and there is no mention of a conflict.

For reference, I too am using an older machine, a small desktop from around 2011. It also uses BIOS rather than EFI.

I did some reading, and the -110 error listed in the Ubuntu logs supposedly means the device is not receiving enough power. But i have an adequate power supply, and, like everyone else, I have no problem if I start PC first and then plug in the Flirc. Similarly, even if it was plugged in at startup, it will work if I take it out and plug it into a different USB port.

All the USB ports on my PC are 2.0 - no 3.0 ports.

I’m at my wit’s end. Would be nice to hear from the forum administrator.

Share this post


Link to post
Share on other sites

Hmm, that's interesting...

I guess your only option right now is to reflash your flirc with the previous firmware (v4.4.2 afaik). For my part,  since I still had some flircs with previous firmwares on hand,  I just swapped two of them and now I'm fine. It seems it's not really a priority for the administrators after all.

I'll keep an eye out for an eventual resolution but I'm not holding my breath.

Good luck,

Daniel

Share this post


Link to post
Share on other sites

I haven't actually done it myself but if you go up this thread,  you will see that Jason has posted two different copies of previous firmwares,  be sure to use the right one and then I believe there is an option in the flirc gui app to upload the file to the flirc.

Good luck!

Daniel

Share this post


Link to post
Share on other sites
36 minutes ago, dborn said:

I haven't actually done it myself but if you go up this thread,  you will see that Jason has posted two different copies of previous firmwares,  be sure to use the right one and then I believe there is an option in the flirc gui app to upload the file to the flirc.

Good luck!

Daniel

That’s correct, go to file->upgrade firmware

Not to worry, if it’s the wrong one, it wont upload. You can’t brick it.

Share this post


Link to post
Share on other sites

The older firmware works like a charm.

I have already started and restarted my system several times, with no problems at all. 

Flirc appears to be working correctly - no detectable problems.

Share this post


Link to post
Share on other sites

@jason  Sorry it's been a while since I've checked this thread.  Seems that I'm not the only one with this issue.

I've since removed the FLIRC and switched back to my old Hauppauge TV IR device so I could get some stability back.

I guess in the meantime, my OS is Win 7 Ultimate and here are some snips of my hardware specs.

Thanks,

Todd.

Capture.JPG

Capture1.JPG

Edited by viperxbr

Share this post


Link to post
Share on other sites
On 6/7/2019 at 10:53 PM, jason said:

That’s correct, go to file->upgrade firmware

Not to worry, if it’s the wrong one, it wont upload. You can’t brick it.

well i just downgrade flirc firmware to version 4.4.2 and it works after reboot, but i lost the option record toogle implement on version 4.6 and this is a no no for me, i need to have both worlds, flirc always conected, and option record toogle

 

@jason how can we fix this problem? 

 

thanks.

Edited by putefabio

Share this post


Link to post
Share on other sites
On 6/7/2019 at 8:13 PM, San Diego MRV said:

@dborn, I checked dmesg logs, and there is no mention of a conflict.

For reference, I too am using an older machine, a small desktop from around 2011. It also uses BIOS rather than EFI.

I did some reading, and the -110 error listed in the Ubuntu logs supposedly means the device is not receiving enough power. But i have an adequate power supply, and, like everyone else, I have no problem if I start PC first and then plug in the Flirc. Similarly, even if it was plugged in at startup, it will work if I take it out and plug it into a different USB port.

All the USB ports on my PC are 2.0 - no 3.0 ports.

I’m at my wit’s end. Would be nice to hear from the forum administrator.

I’ll need a volunteer to help pin this down. Not much time, but a good amount of interaction on trying various firmware images. Let me know who’s up for it. I’ll compensate with a refund and some additional products, some which will be released within the next few days and weeks.

 

Share this post


Link to post
Share on other sites

Hi, I would like to buy a USB FLIRC to obtain the IR code of a remote control. My goal is just to know the code to transmit it with another device. Is it possible to do this with the FLIRC software?

 

Share this post


Link to post
Share on other sites
On 7/10/2019 at 8:11 AM, Controlli said:

Hi, I would like to buy a USB FLIRC to obtain the IR code of a remote control. My goal is just to know the code to transmit it with another device. Is it possible to do this with the FLIRC software?

 

Yes

Share this post


Link to post
Share on other sites
On 6/28/2019 at 11:56 AM, putefabio said:

im down for it, what i need to do?

 

if its easier contact me via email putefabio@sapo.pt 

Yes, shoot me a PM, let's connect over skype or gchat or whats app and lets get this worked out.

Share this post


Link to post
Share on other sites
On 7/15/2019 at 8:41 PM, jason said:

Yes, shoot me a PM, let's connect over skype or gchat or whats app and lets get this worked out.

Sent you pm days ago, you dont awnser, i want to help but its hard this way..

Share this post


Link to post
Share on other sites

I'm trying to solve this as quickly as possible now. I have a big release soon, and it's critical that this firmware is 100% stable, so I will need to issue a fix in the next 2 weeks.

I'm looking to buy a system that this is happening on so I can reproduce locally.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...