| LinHES Forums http://forum.linhes.org/ |
|
| LIRC on R5D1 http://forum.linhes.org/viewtopic.php?f=2&t=11642 |
Page 1 of 1 |
| Author: | orionthunter [ Fri Sep 15, 2006 12:54 pm ] |
| Post subject: | LIRC on R5D1 |
I am using R5D1 and I am trying to get LIRC to work with a home-brew serial ir reciever. I tried following the instructions in the wiki, but they are rather confusing, which lots of edits for various versions. Anyway, I got to the part about making the .conf and when I run irrecord I get this: root@mythtv:/usr/src/lirc-0.8.0# irrecord myremote.conf irrecord - application for recording IR-codes for usage with lirc Copyright (C) 1998,1999 Christoph Bartelmus(lirc@bartelmus.de) irrecord: could not get hardware features irrecord: this device driver does not support the new LIRC interface irrecord: major number of /dev/lirc is 4 irrecord: LIRC major number is 61 irrecord: check if /dev/lirc is a LIRC device irrecord: could not init hardware (lircd running ? --> close it, check permissions) What should I do? Thanks, Zack |
|
| Author: | jzigmyth [ Wed Sep 20, 2006 9:56 am ] |
| Post subject: | |
See the second post in this thread: http://mysettopbox.tv/phpBB2/viewtopic.php?t=10653 It contains "from scratch" instructions for R5C7 updated for R5D1. If you are talking about the LIRCHowTo in the knoppmyth wiki you can ignore everything in it. It was written for older versions of knoppmyth. Everything is already done for you in R5C7 and R5D1. You still need to have a proper /etc/lircd.conf for your remote and a proper /home/mythtv/.mythtv/lircrc that has button names that match your lircd.conf. There are also several lines that need to be added to /etc/init.d/bootmisc.sh You should be able to find a correct lircd.conf for your remote from http://lirc.sourceforge.net/remotes/ and copy it over /etc/lircd.conf. If your remote isn't listed there, see if some other remote in your house is listed there and try that just to see if you can get things working. You can always mess around with irrecord later. If you did follow the wiki Lirchowto completely, its also possible that you mucked something up in R5D1 and you may need to start over. Good luck! |
|
| Author: | orionthunter [ Wed Sep 20, 2006 12:44 pm ] |
| Post subject: | |
I think I did mess somthing up following those instructions, is there anything I can do aside from re-installing knoppmyth? thanks |
|
| Author: | jzigmyth [ Wed Sep 20, 2006 2:02 pm ] |
| Post subject: | |
I'm afraid I can't help you there. I'm a noob myself and my first line of defense is always a virgin re-install! Perhaps someone else can help you back out of it. Did you try adding those lines to bootmisc.sh and then rebooting and then trying irrecord again? |
|
| Author: | derek1234 [ Wed Sep 20, 2006 7:43 pm ] |
| Post subject: | |
When I received this message, this is what got irw working: Code: fuser /dev/lircd (it will say something like "/dev/lircd 909") Code: kill 909
chmod 666 /dev/lircd /usr/sbin/lircd Now try irw again and see if it works. If it does not try re-booting after adding the lines to /etc/init.d/bootmisc.sh as jzigmyth suggests above. |
|
| Author: | jzigmyth [ Thu Sep 21, 2006 7:29 am ] |
| Post subject: | |
Hi derek1234, In your code you put Code: chmod 666 /dev/lircd but wouldn't something like this be better? Code: chmod 775 /dev/lircd
I think 666 has all the execute permissions turned off. It seems like lircd should be set as executable, right? |
|
| Author: | tjc [ Thu Sep 21, 2006 7:42 am ] |
| Post subject: | |
No. That's a device not an executable... Directories have the execute bit turned on because it's overloaded to mean something else there, and links because they're just supposed to be pass through aliases, but you really don't want it on a device or for that matter anything other than an executable program or script. |
|
| Author: | jzigmyth [ Thu Sep 21, 2006 12:48 pm ] |
| Post subject: | |
Sorry I steered someone in the wrong direction. ':oops:' I got confused between /dev/lircd and /usr/sbin/lircd, in fact I'm still confused. Are these the same thing or is one an executable and one a device? Does one start the other? Could they just as easily have different names or do they have the same name by definition? |
|
| Author: | tjc [ Thu Sep 21, 2006 6:37 pm ] |
| Post subject: | |
Different paths, different objects (modulo aliasing). Why not do an ls -li on both of them and you'll see: Code: root@black2:~# ls -li /usr/sbin/lircd /dev/lircd
858160 srw-rw-rw- 1 root root 0 Sep 20 20:56 /dev/lircd 669014 -rwxr-xr-x 1 root root 373288 Aug 3 20:47 /usr/sbin/lircd This makes it pretty clear that they're as different a Boy George and Curious George. 
|
|
| Author: | magicmycote [ Sat Sep 23, 2006 4:08 pm ] |
| Post subject: | |
I have a pvr-250, which has an ir blaster port on it...but I lost the irblaster cable, so I have a serial irblaster in its place. But when I hooked it up and started up, it picks up no signal. I think myth/lirc is looking for a signal on my pvr 250, how can I disable that and make it look in com1/2? some portions of my dmesg that may help: ACPI: Processor [CPU0] (supports 2 throttling states) Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A serial8250: ttyS1 at I/O 0x2f8 (irq = 3) is a 16550A ....... lirc_dev: IR Remote Control driver registered, at major 61 ...... lirc_serial: auto-detected active high receiver lirc_dev: lirc_register_plugin: sample_rate: 0 ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.7.0 (tagged release) loading .............. ivtv: ==================== END INIT IVTV ==================== cx2388x v4l2 driver version 0.0.5 loaded lirc_i2c: chip found @ 0x18 (Hauppauge IR) lirc_dev: lirc_register_plugin: sample_rate: 10 ........ |
|
| Author: | magicmycote [ Sat Sep 23, 2006 4:09 pm ] |
| Post subject: | |
or alternatively, how can i test out each com port with mode2? |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|