mythtv continued...

Bruce Labitt bruce.labitt at verizon.net
Mon Apr 16 20:52:26 EDT 2007


Jarod Wilson wrote:
> On Sunday 15 April 2007 20:45:04 Bruce Labitt wrote:
>   
>>> Oh, and what sort of "problem" are you observing at boot time?
>>>       
> Things like that are typically either logged in /var/log/messages, or 
> available in the output of the dmesg command.
>
>   
#dmesg | grep alsa shows nothing.  How can I do this for 
/var/log/messages?  Nevermind, here is the output for

# cat /var/log/messages|grep alsa
# localhost slmodemd: error: alsa setup: cannot open playback device 
'modem1': Invalid argument
>>>> The second is the remote.  I have a streamzap and was able to find the
>>>> lirc.conf file for it.  I don't know how, or where to place the file so
>>>> that lirc can find it.  The lirc pages assume you build it yourself.
>>>> They say it will ask you for these extra files when it is run the first
>>>> time.  When I downloaded lirc from the yum repository and run it it
>>>> doesn't ask for the configuration file.  Any help would be appreciated!
>>>>         
>>> It should be /etc/lircd.conf. Then you'll need a file
>>> /home/<username>/.lircrc (or /home/<username>/.mythtv/lircrc, and/or
>>> symlink the two together) that maps the remote presses to functions
>>> and/or keyboard key presses to send to the apps you're trying to control.
>>>       
>> Can you provide an example of the symlink?  Say I have files
>> /home/myth/.lircrc and /home/myth/.mythtv/lircrc , how are they linked
>> together?  The man page doesn't have an example of usage.  What about
>> permissions?  I would guess that user myth and mythtv would need to be
>> able to read the files.
>>
>> Is the symlink done as $ ln -s .mythtv/lircrc .lircrc  ?  I pulled that
>> from http://www.wilsonet.com/mythtv/tips.php
>>     
>
> Yes, exactly like that, assuming the command was run from within your home 
> directory.
>
>   
>> Right now lirc.conf has -rw-r--r-- and
>>           lircrc    has -rw-rw-r--
>>     
>
> Permissions look fine, but I repeat: the daemon config file needs to be named 
> lircd.conf, not lirc.conf, and placed in /etc/.
>
>   
I heard you this time :) I copied etc/lirc.conf to etc/lircd.conf.  
Restarted the service lircd.  In the status window of service 
configuration it says -

lircmd is stopped
lircd (pid xyz) is running

What is lircmd?

I then started mythfrontend - however the remote is not being connected 
to myth.  I do notice every button press lights up the IR receiver.

I just typed
$ irw
connect:  Connection refused

>> The part that confuses me is (besides everything) is how does lircd even
>> know about these files.  Also how does myth know where to look for these
>> files?  Is there a setup file for either myth or lircd that needs to be
>> run?
>>     
>
> Nope, myth is built to be lirc-aware, and just knows to look in those spots 
> for lirc config files.
>
> One thing that we haven't yet addressed... What lircrc file are you using, and 
> have you made sure the button names mapped within it actually match the 
> button names given in the lircd.conf file you found? That's another big key 
> to getting it working...
>
>   
I found the files in the mythic.tv contributed code area. In their 
Knoppmyth centric world they recommend using lirc.conf ...  anyways the 
link is:

http://mythic.tv/contributed_code.php?osCsid=5084e9ba6b0b843ce2b134f33bff322f

The button names and code definitions in the two files seem to match.  
In addition, they have button definitions for mplayer in the file.
>> Thanks for your help so far!
>>     
>
> No problem, hth.
>
>   
Getting closer...


More information about the gnhlug-discuss mailing list