tcomparri Posted January 1, 2013 Report Share Posted January 1, 2013 Sorry if this has already been covered somewhere, but I'm having trouble getting the flirc software to recognize that the device is actually connected. I used the zadig tool to create the signed driver, and it appears to be working correctly when checking the device manager, but the software to program it says that it's disconnected. I was able to install and get the software to recognize the flirc on an older Windows 7 machine, but not on the one I actually need it to work on (windows 8, ASRock H77M motherboard with USB 3.0 ports). Any help would be appreciated - thanks. 1 Quote Link to comment Share on other sites More sharing options...
Chris! Posted January 2, 2013 Report Share Posted January 2, 2013 Hi tcomparri, Does the mother board you're trying to use it on have any usb2 ports? Quote Link to comment Share on other sites More sharing options...
jason Posted January 2, 2013 Report Share Posted January 2, 2013 This may pertain to you, let us know: "NEC/Renesas USB 3.0 users, please upgrade your drivers to version 2.1.16.0 or later. Older versions of the driver have a bug that prevents libusbx from accessing devices." Quote Link to comment Share on other sites More sharing options...
tcomparri Posted January 25, 2013 Author Report Share Posted January 25, 2013 Thanks for your response. I tried different ports, both usb 2.0 and 3.0, and I upgraded the drivers. Unfortunately, I still can't connect. Quote Link to comment Share on other sites More sharing options...
Chris! Posted January 26, 2013 Report Share Posted January 26, 2013 Can you perhaps try running ubuntu on the system so we can narrow down if it is an operating system issue or a hardware issue Quote Link to comment Share on other sites More sharing options...
tcomparri Posted January 26, 2013 Author Report Share Posted January 26, 2013 Thanks Chris - I did that, and still got the same thing trying to run on ubuntu Quote Link to comment Share on other sites More sharing options...
Chris! Posted January 26, 2013 Report Share Posted January 26, 2013 Hmm, frustrating. Next thing to do would be to check whether the flirc is working. Have you got another computer you could test it on to see if the same thing happens (preferably a different hardware configuration). Sorry you haven't had the best Flirc experience - don't worry though, we won't leave you hanging :) Quote Link to comment Share on other sites More sharing options...
tcomparri Posted January 27, 2013 Author Report Share Posted January 27, 2013 Yes, it seems to be working fine on my old Windows 7 PC. Quote Link to comment Share on other sites More sharing options...
Chris! Posted January 27, 2013 Report Share Posted January 27, 2013 Doh! You mentioned that in your first post - sorry for asking again. Could you try and program it on the windows 7 machine then try and use Flirc (without the set-up software) on the windows 8 machine? (as the settings are stored in Flirc) That way you could use flirc to control the machine but you would have to use another machine to make changes to any buttons and have a mostly working Flirc for now. I'll notify Jason again to see if he has any pearls of wisdom. Quote Link to comment Share on other sites More sharing options...
tcomparri Posted January 27, 2013 Author Report Share Posted January 27, 2013 That worked - Thanks again for all of your help. Quote Link to comment Share on other sites More sharing options...
jason Posted January 27, 2013 Report Share Posted January 27, 2013 Awesome, so glad that helped. What is your motherboard make and manufacturer? I was just replying agreeing with Chris' suggestion. Glad you are up and running. Quote Link to comment Share on other sites More sharing options...
smarvv Posted January 28, 2013 Report Share Posted January 28, 2013 I also have an ASrock H77M motherboard and I am having the same issue. However, I am using USB 2.0 ports. The motherboard has a onboard CIR connection that connects to the front USB 2.0 port. It is my understanding this enables remote to power on the PC. I have disabled CIR in bios and also tried the Flirc on different ports and it still fails to recognize the device. Any ideas? Quote Link to comment Share on other sites More sharing options...
doublet30 Posted February 13, 2014 Report Share Posted February 13, 2014 In order to program Flirc from a debian Linux OS such as Ubuntu, you must do so as a privileged user. try "sudo Flirc" from command line in your terminal and the status should show as connected and there is no need to use a second computer. If you are advanced with Linux configuration, you can configure your user account to have "root" privileges but that decreases system security. TO ADMINISTRATOR: As a fellow Linux developer, I would recommend that the Flirc binary ask for administrator password and run as root automatically to make programming Flirc seamless on ANY Linux OS where sudo is allowed. Have a great day everyone! - Double T - doublet30@hotmail.com Quote Link to comment Share on other sites More sharing options...
doublet30 Posted February 13, 2014 Report Share Posted February 13, 2014 an alternative to changing the Flirc binary is to make two separate deb packages with bash scripts calling the correct graphical sudo program and flirc.deb as a dependency. For example... #flirc-kde #!/bin/bash exec "kdesu Flirc" #flirc-gtk #!/bin/bash exec "gksu Flirc" and install with "sudo apt-get install flirc-gtk" (this is where apt-get will ask for permission to install gksu and flirc.deb as dependencies and yada yada yada) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.