Jump to content
Flirc Forums

dborn

Members
  • Content Count

    17
  • Joined

  • Last visited

  • Days Won

    1

dborn last won the day on June 3 2019

dborn had the most liked content!

Community Reputation

1 Neutral

About dborn

  • Rank
    Junior Flirc-er

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am using a usb extender on one of my flircs setup of about 25' long though a conduit with other wires inside such as HDMI and there is no issue with it but this is not the flirc that got the latest firmware upgrade and running on the computer with the issue that needed to be addressed, so it may not be fully relevant here. The flirc that got the firmware upgrade is running fine, directly connected to the computer. However, it is running about 1-2 hours a day and is suspended the rest of the time, hardly ever rebooted or turned off. Hope this helps,
  2. Jason, Sorry I didn't have time to try it out before now. All works fine now, no issues. dmesg output is clean. Cheers, Daniel
  3. That's awesome news! Can you confirm the version? V4.4.2 or newer? Daniel
  4. 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
  5. 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
  6. @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
  7. It's a good thing that "this is considered red hot urgent" ;)
  8. 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, 0x4E
  9. 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
  10. I'm also convinced it's a firmware issue as I use the FLIRCs with linux computers without any particular drivers. You're probably referring to Windows computers but I will give you my OS version just in case :) It's xubuntu 18.04 with kernel 4.15.0-48-generic in all cases. These are all USB2 ports (black). Here is what I get from another computer with a FLIRC that was not firmware upgraded, when I reboot (relevant to the FLIRC): > lsusb Bus 005 Device 002: ID 20a0:0006 Clay Logic > dmesg [ 2.192076] usb 5-2: new full-speed USB device number 2 using u
  11. @jason, 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. Thanks, Daniel Born
  12. 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
  13. 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 ni
  14. Hi Jason, Mine says SKU: FLIRC 2.0 [dori] Firmware is V4.6.3 Thanks, Daniel
  15. Just a quick update on the situation: it seems it can recover from sleep mode pretty consistently. Booting the computer from off still seems to be problematic.
×
×
  • Create New...