Jump to content
Flirc Forums

dborn

Members
  • Content Count

    8
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dborn

  • Rank
    Curious Flirc-er
  1. 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 uhci_hcd [ 2.398139] usb 5-2: New USB device found, idVendor=20a0, idProduct=0006 [ 2.398145] usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 2.398148] usb 5-2: Product: flirc [ 2.398151] usb 5-2: Manufacturer: flirc.tv [ 2.437998] usbcore: registered new interface driver usbhid [ 2.438001] usbhid: USB HID core driver [ 2.448105] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:1d.3-2/input0 [ 2.449274] input: flirc.tv flirc as /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.1/0003:20A0:0006.0002/input/input5 [ 2.508426] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:1d.3-2/input1 Here is what I get from the computer with the upgraded FLIRC when I reboot: > lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub (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 ... [ 7.900173] usb 2-6: device descriptor read/all, error -110 [ 8.088072] usb 2-6: new full-speed USB device number 3 using ohci-pci [ 23.704066] usb 2-6: device descriptor read/64, error -110 [ 39.320058] usb 2-6: device descriptor read/64, error -110 [ 39.428080] usb usb2-port6: attempt power cycle [ 39.932058] usb 2-6: new full-speed USB device number 4 using ohci-pci [ 50.604058] usb 2-6: device not accepting address 4, error -110 [ 50.792058] usb 2-6: new full-speed USB device number 5 using ohci-pci [ 61.612059] usb 2-6: device not accepting address 5, error -110 [ 61.612096] usb usb2-port6: unable to enumerate USB device Now, when I unplug and replug the FLIRC while the computer is powered on: > lsusb Bus 002 Device 006: ID 20a0:0006 Clay Logic > dmesg [ 743.920674] usb 2-6: new full-speed USB device number 6 using ohci-pci [ 744.162676] usb 2-6: New USB device found, idVendor=20a0, idProduct=0006 [ 744.162683] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 744.162687] usb 2-6: Product: flirc [ 744.162690] usb 2-6: Manufacturer: flirc.tv [ 744.348840] hidraw: raw HID events driver (C) Jiri Kosina [ 744.409404] usbcore: registered new interface driver usbhid [ 744.409411] usbhid: USB HID core driver [ 744.508490] hid-generic 0003:20A0:0006.0001: hiddev0,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:04.0-6/input0 [ 744.516430] input: flirc.tv flirc as /devices/pci0000:00/0000:00:04.0/usb2/2-6/2-6:1.1/0003:20A0:0006.0002/input/input7 [ 744.573280] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-0000:00:04.0-6/input1 [ 744.574269] hid-generic 0003:20A0:0006.0003: hiddev1,hidraw2: USB HID v1.11 Device [flirc.tv flirc] on usb-0000:00:04.0-6/input2 I think this should give you a few good hints as to what is happening here. :-) Cheers, Daniel
  2. @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
  3. 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. :) Cheers, Daniel
  4. 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.
  5. Hi Jason, Mine says SKU: FLIRC 2.0 [dori] Firmware is V4.6.3 Thanks, Daniel
  6. 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.
  7. 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. :) Thanks and keep up the good work! Daniel
  8. 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.
×
×
  • Create New...