Jump to content
Flirc Forums

GMFisher

Members
  • Content Count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About GMFisher

  • Rank
    Curious Flirc-er
  1. Thank you for the response. The only challenge is that it USED to show up on logging in via SSH. And I had/have a script that would then match those keystrokes to MPD commands. That user would autologin on boot and the script would run, catching the keystrokes coming from the remote/Flirc. Will check with the HDMI connected and see if it is showing up in that terminal session. If it is a keyboard, why would it NOT be available in an SSH session as a "keyboard"? And more importantly, why would it not be available after a firmware upgrade? Thanks much for your assistance.
  2. With a fresh linux install on the RPI3, I was able to load Flirc and the flirc_util. The status is ok (now). Prior to the firmware update it had some very "interesting" responses for flirc_util test I can program the keys in Linux, so the flirc_util program is picking up the IR commands sent from the remote. flirc_util keys shows the keys programmed to letters, e.g. play is mapped to w. The problem is, pressing the play key is not generating a w and sending it to bash. So no keystrokes are being translated and sent to the OS. The Flirc driver must be working as the util program can read the commands sent and can tell when a remote button has already been programmed. How do I get the keystrokes to be sent to the device, like a keyboard? (Like it used to...) Thanks for your assistance.
  3. Hi, Have been using your Flirc product for a while now and really enjoy the convenience it offers. Rebuilt my system, which included new versions of Flirc software and answered yes to the "Update Firmware?" question on my WIndows 10 machine. The upgrade appeared successful and tests on the Win 10 machine are successful. Config settings still there! Load a fresh image of Moode 4.4 and the keystrokes no longer register on the Pi 3. I have a Ver 2 (nemo) hardware dongle. Have tried it in all 4 USB ports, rebooting each time. It is definitely a Linux issue. I suspect the driver is not loading properly? But it shows as loaded in 'dmesg' below. The dongle works with Windows 10. The remote works with the dongle in Windows 10. Transfer the dongle to a freshly written Moode 4.4 image and the key strokes are not sent. It WAS working fine before the firmware update. Any help would be greatly appreciated. [ 3.431515] usb 1-1.5: new full-speed USB device number 4 using dwc_otg [ 3.576263] usb 1-1.5: New USB device found, idVendor=20a0, idProduct=0006 [ 3.586162] usb 1-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 3.596423] usb 1-1.5: Product: flirc [ 3.602937] usb 1-1.5: Manufacturer: flirc.tv [ 3.612351] systemd[1]: Listening on RPCbind Server Activation Socket. [ 3.622330] hid-generic 0003:20A0:0006.0001: hiddev96,hidraw0: USB HID v1.11 Device [flirc.tv flirc] on usb-3f980000.usb-1.5/input0 [ 3.643843] systemd[1]: Listening on Syslog Socket. [ 3.652207] input: flirc.tv flirc as /devices/platform/soc/3f980000.usb/usb1/1-1/1-1.5/1-1.5:1.1/0003:20A0:0006.0002/input/input0 [ 3.672769] systemd[1]: Created slice System Slice. [ 3.684549] systemd[1]: Created slice system-serial\x2dgetty.slice. [ 3.699676] systemd[1]: Mounting RPC Pipe File System... [ 3.712408] systemd[1]: Listening on udev Control Socket. [ 3.721772] hid-generic 0003:20A0:0006.0002: input,hidraw1: USB HID v1.01 Keyboard [flirc.tv flirc] on usb-3f980000.usb-1.5/input1 [ 3.742219] systemd[1]: Listening on Journal Socket (/dev/log). [ 4.434171] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 4.522284] systemd-journald[94]: Received request to flush runtime journal from PID 1 [ 5.093578] snd-hifiberry-digi soc:sound: ASoC: CODEC DAI wm8804-spdif not registered - will retry [ 5.494133] wm8804 1-003b: revision E [ 5.499740] snd-hifiberry-digi soc:sound: wm8804-spdif <-> 3f203000.i2s mapping ok [ 6.653813] smsc95xx 1-1.1:1.0 eth0: hardware isn't capable of remote wakeup [ 6.654423] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 8.185191] smsc95xx 1-1.1:1.0 eth0: link up, 100Mbps, full-duplex, lpa 0x4DE1 [ 8.185351] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 19.832816] random: crng init done [ 19.832826] random: 7 urandom warning(s) missed due to ratelimiting [ 434.867577] usb 1-1.2: new high-speed USB device number 5 using dwc_otg [ 434.998642] usb 1-1.2: New USB device found, idVendor=0781, idProduct=5575 [ 434.998649] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 434.998653] usb 1-1.2: Product: Cruzer Glide [ 434.998658] usb 1-1.2: Manufacturer: SanDisk [ 434.998662] usb 1-1.2: SerialNumber: 4C530001021015116432 [ 435.000462] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ 435.001130] scsi host0: usb-storage 1-1.2:1.0 [ 436.068367] scsi 0:0:0:0: Direct-Access SanDisk Cruzer Glide 1.00 PQ: 0 ANSI: 6 [ 436.069265] sd 0:0:0:0: [sda] 61194240 512-byte logical blocks: (31.3 GB/29.2 GiB) [ 436.069893] sd 0:0:0:0: [sda] Write Protect is off [ 436.069900] sd 0:0:0:0: [sda] Mode Sense: 43 00 00 00 [ 436.070254] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ 436.077028] sda: sda1 [ 436.078767] sd 0:0:0:0: [sda] Attached SCSI removable disk [ 436.081553] sd 0:0:0:0: Attached scsi generic sg0 type 0
×
×
  • Create New...