Jump to content
Flirc Forums

Search the Community

Showing results for tags 'ubuntu'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Flirc forums
    • Getting Started with Flirc
    • General Questions
    • How To
    • Show Off
    • Remote Controls
    • Ideas and Suggestions
    • Bugs

Found 13 results

  1. I'm attempting to install FLIRC on ubuntu 17.04 by following the instructions at: https://support.flirc.tv/hc/en-us/articles/203633465-Installing-Flirc-GUI-on-Linux-Debian- I'm getting a few errors such as: Err:1 http://apt.flirc.tv/arch/x64 binary/ flirc 2.6.4-1 404 Not Found E: Failed to fetch http://apt.flirc.tv/arch/x64/./flirc_2.6.4-1_amd64.deb 404 Not Found E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? I'm a novice Linux user, so sorry if I'm missing something obvious. Neil
  2. FLIRC USB Firmware v4.1.1. Remote is an Acoustic Research ARRS05G. Using the Kodi profile. OS is Ubuntu LTS 16.04: matt@host:~$ cat /etc/os-release NAME="Ubuntu" VERSION="16.04.2 LTS (Xenial Xerus)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 16.04.2 LTS" VERSION_ID="16.04" HOME_URL="http://www.ubuntu.com/" SUPPORT_URL="http://help.ubuntu.com/" BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/" VERSION_CODENAME=xenial UBUNTU_CODENAME=xenial matt@host:~$ cat /etc/debian_version stretch/sid Whenever I press a button on the remote, I'd say there's maybe a 20% chance it is recognized. In other words, it seems most button presses are ignored. This is with the FLIRC USB device plugged into the front of the PC, and me standing right in front of it, with the remote only a few inches away. Using a (wired) USB keyboard, all button presses work immediately as expected. I'm using Flirc v2.5.1, from Deb package flirc_2.5.1-1_amd64.deb (md5sum: 4ac86479eae26df57a676e9674bb699e). Simply running Flirc and then exiting prints this out to the console: matt@host:~$ Flirc Can't load 'test.ini' 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ 00: ff ff ff ff ff ff ff ff ff ff ff ff ............ Object::connect: No such signal QCheckBox::currentIndexChanged(int) [D] lib/libflirc/flirc_driver.c fl_major_version(387): something bad happened That "something bad happened" doesn't inspire much confidence.
  3. hi, i just updated to the 2.3.9 package and noticed an extra generic man page being included in /usr/share/doc/flirc/Flirc.1. please see attached image of the formatted/rendered man page. seems a generic bit unintentionally included in the package. thanks, -matt
  4. There are a number of situations where you may want to configure/control flirc from the command line rather than the GUI. For example, XBMCbuntu is made to boot directly to XBMC without ever displaying a desktop environment. You may also like to be able to modify your flirc configuration via ssh without interrupting an XBMC session. In this tutorial I'll cover some basic steps for getting started with flirc from a command line. INSTALLATION First, we'll install the flirc software. To do this, you need to add flirc to your apt-get sources. You can do this with any text editor. Easiest is probably nano: sudo nano /etc/apt/sources.list Scroll all the way to the bottom of the file (Ctrl+V is page down) and add these lines: # flirc deb http://apt.flirc.tv/arch/i386 binary/ Save your changes (Ctrl+X exits nano, prompting you to save. Hit Y for yes, and enter to save without changing the file name). Then update apt-get to include your new source: sudo apt-get update Now you can install the flirc software: sudo apt-get install flirc Now it's possible to run all flirc commands from the command line, including programming the device, backing up your configuration, firmare installs, etc. For a list of flirc commands, you can just type 'flirc' and press enter, or 'flirc help'. For help with a specific flirc command, use 'flirc help <command>'. FIRMWARE You'll want a place for storing flirc firmware and config files. Here's how I do it: Go to your home directory if you aren't there already (in Linux, the tilde (~) represents your home directory, so if you're using XBMCbuntu and logged in as the xbmc user, 'cd ~' will take you to your home directory). If you're using another computer to do all of this via ssh, your ssh sessions will start in your home directory anyway by default. Make a folder called .flirc: mkdir .flirc Go to your new folder: cd .flirc To pull down firmware 1.0: wget http://downloads.flirc.tv/fw/fw_1.0.bin (Optional) Linux tip: If you use 'ls' you will see that there's now a file called fw_1.0.bin in your ~/.flirc/ folder. I use 'ls -al' (or just 'll' on most Linux builds), as that will also show hidden files and folders (like the ones with dots (.) in front of them) and the list is formatted nicer and provides much more info than ls alone. To install the firmware, make sure your flirc is connected and run: flirc upgrade fw_1.0.bin I don't know direct addresses for beta firmware. I'm not sure if Jason wants those to be public anyway. If he does he can add them to this thread. Either way, I'll add a post about copying files to and from an XBMCbuntu box soon. Also, since the flirc software is now installed, you can get to the GUI if you really need to as well, by exiting XBMC and logging into xbmcbuntu from the log in window, using the same account/password as your xbmc account. Flirc will most likely be one of very few apps installed so it's not hard to find, and it looks the same on Linux as is does on Windows or Mac, but I really like using flirc from the command line honestly. It's really easy to use 'flirc delete' and 'flirc record <key>' to change buttons on the fly without interrupting your xbmc sessions.
  5. Hi. I've currently got FLIRC firmware 3.6 and a Harmony 650. I notice that since updating the firmware on my FLIRC and my Harmony that sometimes I'll get buttons pressing twice when navigating in KODI. I've followed the suggestions here and here and it's improved but it still occurs sometimes. I'm wondering if there's a way I can increase the Inter-Key Delay setting beyond 6. I'm on Ubuntu 14.
  6. Xubuntu 14.04 Gui problem

    Hello, i have just bouth twice Flirc. So i have followed the information to install it on xubuntu 14.04 64 bit. And so i have got the version 1.2.9 . As i always put the last stable firmware, i have made an upgrade. The stick was on 2.1, and after the update it goes to 3.1 I have tested to asign key, and it works. After that i stop the application and do overthing. I wanted to add some keyboard key to the stick. I could not launch the application from the user, it says:
  7. A few moths ago, I purchased Flirc and programmed it on my windows machine using the Panasonic TV profile as posted at Plugged the Flicr dongle into my XBMCBUNTU machine and everything worked great. Best gadget I have ever purchased. I have since had to reinstall XBMC on that machine and instead of using XBMCBUNTU like I originally did, I installed Ubuntu and added the xbmc packages. I was expecting to just plug the Flicr dongle in and it would work just like before since the programming is contained on the dongle, but it now does nothing. The remote is sending the command(based on the feedback indicator on the remote), but I get no response on the XBMC machine. I did the obvious things: 1. Add 'deb http://apt.flirc.tv/arch/i386 binary/' to /etc/apt/sources.list 2. apt-get update 3. apt-get install flirc Enabled the 'remote sends keyboard commands' option within the XBMC configuration. Was there some other step that I had forgotten or overlooked that was part of the XBMCBuntu install that would be missing by installing the full OS? I have ran out of ideas of what to check, where to look, etc Any suggestions?
  8. Hello flirc community. I'm having some trouble with my flirc, and I'm posting here in desperation. I purchased this IR repeater some time ago, and have been using it with great success with flirc on a windows vista machine running xbmc. I recently upgraded my htpc, and switched to linux in the process. I programmed the flirc first without the repeater, and it worked fine. I then moved the htpc into my media closet, cleared the configuraiton and programmed it again through the IR repeater. Flirc records the buttons, but refuses to repeat them. The repeater does still work on my 5.1 receiver. I'm running Ubuntu 14.04, flirc firmware 1.2.6, and the latest flirc packages from the repository. If it matters flirc is plugged into the motherboard usb ports, not the front ones (I ran into that problem when I was running it on vista). Please someone help me salvage this awesome device!
  9. Hi everyone, just got my flirc yesterday, and i am having some troubles with it. Hardware: Custom built i3 Asrock h77m-itx 4gb ram BIOS 1.90 Harmony 900 remote Dinovo Mini Blue tooth Keyboard FLIRC XBMC Gotham 13.1 It took me awhile to get it working but flirc is working fine, i have programed the activity to use flirc on the harmony 900 it will power on my tv and zvox but not my htpc, i have to use my dinovo mini to power it on. For the life of me i can not figure out why the flirc does not power on my htpc, i have checked all the bios settings updated to the latest asrock bios 1.90, i even used my wireless logitech keyboard and it powers the machine one with no issues. If someone could help me that would be so good. Could it be that i am putting it to a shutdown state rather than sleep mode state ? that is why it is not wkring if so then why would my other devices be able to power it on. thanks w
  10. Ubuntu New install, can't connect to device

    I just received my Flirc on my 64-bit Ubuntu 13.10 machine. Since the repositories are down, I did a manual download. I can run the GUI but it gives the disconnected sign. lsusb Bus 004 Device 005: ID 20a0:0001 Clay Logic I suspect I need to add a line to my udev rules but have no idea what I should add or how to do it. Any help would be appreciated
  11. Ubuntu Minimal XBMC

    Edit: Just noticed I posted under wrong topic. Can this be moved? In the past I ran XBMC on a full Ubuntu desktop 10.04 environment, installed Flirc, used the GUI setup, and all was well. I just reinstalled XBMC on top of Ubuntu Minimal (used this script http://forum.xbmc.org/showthread.php?tid=141369) and now my remote will not work at all. I tried the command line with; $ flirc record and mapped all of my keys, saved the config with; $ flirc saveconfig $ flirc normal but still no luck. I've searched the forum but cannot find this topic. Anyone familiar with my issue? Thanks for any help. Flirc Version 1.0.2 Firmware Version: 1 10-02-2011 Remote: Universal Remote Control URC-R50 Ubuntu minimal: 13.04 XBMC: Think Eden
  12. These are instructions that worked for my ubuntu 12.04-based XBMC HTPC. None of the other howtos I could find actually worked for me. Recent ubuntus (e.g. 12.04 or later) use udev and automatically query the "wakeup" capability of USB devices, and allow setting the "wakeup" property of the device only if it supports it. The "stable" FLIRC firmware does not expose the "wakeup" capability to the kernel. Only later "fw_wakeup" betas do (starting in v2 I think). Anyhow - here is the procedure that did the trick for me - YMMV but at least this will give you some hopefully useful pointers :) For wake-up to work with newer ubuntu’s with udev, the “Wake Up Firmware v6” is required. This method works in recent ubuntus (e.g. 12.04 or later) Connect FLIRC to the HTPC - then do: ..... Bus 005 Device 003: ID 20a0:0001 Clay Logic Note: Bus 5, Device 2. Note also: Vendor ID: 20a0; Device ID: 0001 lsusb -t …. /: Bus 05.Port 1: Dev 1, Class=root_hub, Driver=ohci_hcd/5p, 12M |__ Port 4: Dev 3, If 0, Class=HID, Driver=usbhid, 1.5M |__ Port 4: Dev 3, If 1, Class=vend., Driver=, 1.5M Note: Bus 05, Port 4 Now if flashed with a “recent wake up” firmware, FLIRC will advertise via USB that it can wake up the machine, and this can be verified by querying the “power” capabilities of “Bus 05, Port 4”: ls /sys/bus/usb/devices/5-4/power active_duration control runtime_enabled wakeup_active wakeup_max_time_ms async level runtime_status wakeup_active_count wakeup_total_time_ms autosuspend persist runtime_suspended_time wakeup_count autosuspend_delay_ms runtime_active_kids runtime_usage wakeup_hit_count connected_duration runtime_active_time wakeup wakeup_last_time_ms If “wakeup” shows up in the listing, all is good. With the original “non-wakeup” firmware, no wakeup capability was showing up. Note: the old (pre udev) way of activating wakeup (sh -c 'echo "USB4" > /proc/acpi/wakeup') no longer works in ubuntu 12.04+ Now we can manually test if wakeup works by doing (note the use of the "bus" and the "port" addresses): echo enabled > /sys/bus/usb/devices/5-4/power/wakeup Suspend / resume should now work. This could be added to rc.local - the problem with this approach is that if the FLIRC is moved to a different USB port, wakeup won’t work. The best approach is to create a new udev rule: cd /etc/udev/rules.d/ vi 90-flircwakeup.rules SUBSYSTEM=="usb", ATTRS{idVendor}=="20a0", ATTRS{idProduct}=="0001" RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup'" This will allow wake for the FLIRC no matter where it is connected. Note that for wake up to work, the “wake up” key has to be recorded using the “flirc” utility.
  13. using the `xev` program on both my media center machine (laptop running mythbuntu 11.04) and my ordinary machine (desktop running vanilla ubuntu 11.10), I can see that: On the laptop only, sometimes pressing a button normally will cause repeated events to be sent until the next button is pressed (after which *that* button may be stuck on indefinitely). At other times it's fine, but it often seems to get stuck in this mode - i.e once a keypress starts repeating, future key presses probably will too. With the same flirc, remote & config, running on my desktop, I have not been able to get this to happen. So I'm presuming it's something in the linux even stack somewhere? I'm not too sure where to look to figure out where the problem is. Is there some way to get flirc to dump logs of what events it thinks it's generating, to see if the bug is with flirc or linux? I noticed a mention here ( http://blog.flirc.tv/?page_id=46 ) of "inter-key delay time to help fix when rapidly pressing causes `stuck key`". "Stuck key" seems to be my problem, but it's unrelated to how fast I press keys (a single press can trigger it). I also couldn't see how to configure or find out more about this delay setting - is it exposed from the command line tool? If it's useful, my laptop is: $ uname -a Linux tjcee 2.6.38-12-generic #51-Ubuntu SMP Wed Sep 28 14:25:20 UTC 2011 i686 i686 i386 GNU/Linux And my desktop: $ uname -a Linux meep 3.0.0-13-generic #22-Ubuntu SMP Wed Nov 2 13:27:26 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
×