| LinHES Forums http://forum.linhes.org/ |
|
| R5E50 IRBlaster issue http://forum.linhes.org/viewtopic.php?f=6&t=13795 |
Page 1 of 1 |
| Author: | lonerzzz [ Tue Jan 23, 2007 10:33 pm ] |
| Post subject: | R5E50 IRBlaster issue |
I have upgraded from R5B7 to R5E50 including hardware with minimal issues. I am quite impressed with all the work that has gone on towards stabilization. Thanks to the contributors. The one sticky problem that remains is trying to get both lirc and the irblaster running. I have a USB based remote which upgraded and ran without issue. The remote is tied to the lircd instance and lirc0 device. My homemade serial port irblaster which works on the old hardware does not work on the upgraded platform. I get the ever useless lirc messages after many attempts to change various configuration files and numerous reboots: As user root: > irsend --device=/dev/irblaster SEND_ONCE SAE8000 select irsend: could not connect to socket irsend: Connection refused Here is what I know so far: 1) I ran irblaster.sh and the installation went well. 2) lircd and irblasterd are running with the following output from 'ps' root 3212 1 0 23:06 ? 00:00:00 /usr/sbin/irblasterd --driver=default --device=/dev/irblaster --pidfile=/var/run/irblasterd.pid --output=/dev/ir root 2960 1 0 23:05 ? 00:00:00 /usr/sbin/lircd --driver=default --device=/dev/lirc0 3) The device files look like: crw-r--r-- 1 root root 61, 1 Jan 23 23:06 /dev/irblaster srw-rw-rw- 1 root root 0 Jan 23 23:06 /dev/irblasterd crw-rw---- 1 root video 61, 0 Jan 23 23:05 /dev/lirc0 crw-rw---- 1 root video 61, 1 Jan 23 23:06 /dev/lirc1 srw-rw-rw- 1 root root 0 Jan 23 23:05 /dev/lircd crw-rw---- 1 root dialout 4, 64 Jan 23 23:05 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 Jan 23 23:05 /dev/ttyS1 4) The /etc/lirc/hardware.conf file looks like: # /etc/lirc/hardware.conf # # Arguments which will be used when launching lircd LIRCD_ARGS="" #Don't start lircmd even if there seems to be a good config file START_LIRCMD=false #Try to load appropriate kernel modules LOAD_MODULES=true # Run "lircd --driver=help" for a list of supported drivers. DRIVER="default" # If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be # automatically used instead DEVICE="/dev/lirc0" MODULES="lirc_dev lirc_atiusb" 5) The /etc/irblaster/hardward.conf file looks like: # /etc/irblaster/hardware.conf # # Author: Greg Frost # The COM Port used by the IRBlaster. Set it to COM1 COM2 or "". IRBLASTER_SERIAL_PORT=COM1 6) The lsmod results for lirc show the lirc_serial module loaded lirc_serial 16128 0 lirc_atiusb 19104 1 lirc_dev 16628 2 lirc_serial,lirc_atiusb usbcore 111364 4 lirc_atiusb,ehci_hcd,ohci_hcd 7) The UNIX sockets from netstat look like: unix 2 [ ACC ] STREAM LISTENING 9482 /dev/lircd unix 3 [ ] STREAM CONNECTED 13273 /dev/lircd unix 3 [ ] STREAM CONNECTED 13131 /dev/lircd unix 2 [ ACC ] STREAM LISTENING 9969 /dev/irblasterd Any suggestions would be appreciated because the complete lack of information from the irsend executable is making this a painful task. If I get the information, I will offer up any script changes to encapsulate this knowledge. Thanks for the ongoing efforts, Jason |
|
| Author: | Greg Frost [ Tue Jan 23, 2007 11:32 pm ] |
| Post subject: | Re: R5E50 IRBlaster issue |
lonerzzz wrote: I get the ever useless lirc messages after many attempts to change various configuration files and numerous reboots: Thats the wrong command. Try:As user root: > irsend --device=/dev/irblaster SEND_ONCE SAE8000 select irsend: could not connect to socket irsend: Connection refused Code: irsend --device=/dev/irblasterd SEND_ONCE SAE8000 select Note the /dev/irblasterd
|
|
| Author: | tjc [ Tue Jan 23, 2007 11:58 pm ] |
| Post subject: | |
Also see the Upgrade Hints posting and make sure you've taken care of all the issues listed there, in your case I suspect that you need to add the mythtv user to the dialout group. (Known Change #8 ) Even if you don't read the whole thing, searching that posting and the replies for "lirc" should find most of the issues of concern. |
|
| Author: | lonerzzz [ Tue Jan 23, 2007 11:58 pm ] |
| Post subject: | Re: R5E50 IRBlaster issue |
Thanks for the very quick response to the very uninformed question on my part. Just for understanding, is this the same way that one would interact to write to lirc if it were being used, ie writing to /dev/lircd? From the command line, the --output=/dev/irblasterd seemed to me to be where the irblasterd would write its output. Thus from what you are saying, does it mean that /dev/irblasterd is the input side of the socket and /dev/irblaster would be the output if there were any? Thanks again, Jason |
|
| Author: | Greg Frost [ Wed Jan 24, 2007 12:08 am ] |
| Post subject: | |
/dev/irblaster is the equivalent of /dev/lirc0. It is the interface to the lirc driver which is loaded as part of the kernel. /dev/irblasterd or /dev/lircd is a socket that is created by the daemon for the purpose of communicating with other applications (such as irw, irxevent, irexec, irsend etc). Some of the lirc tools interface directly with the device driver (such as mode2). Others as described above are designed only to communicate with the daemon. |
|
| Page 1 of 1 | All times are UTC - 6 hours |
| Powered by phpBB® Forum Software © phpBB Group http://www.phpbb.com/ |
|