[mythtv-users] lirc almost solved

Nick Morrott knowledgejunkie at gmail.com
Mon Mar 26 04:56:19 UTC 2007

On 26/03/07, Claude Gélinas agr. <claude at phyto.qc.ca> wrote:

> Now it work. I've done two things.
> reverse the ~/.mythtv/lircrc and ~/.lircrc as the symlink was done the
> wrong way. Now the link is .lircrc -> .mythtv/lircrc

Shouldn't make any difference

> I also find that the lirc_i2c module was not loaded and lircd no started
> before the mythfrontend was started. So I kill the mythfrontend then
> /sbin/modprobe lirc_i2c
> /sbin/service lircd start
> mythfrontend
> and bingo I get the remote.

This would be the cause of the problem.

> I don't know why lirc do not start automatically as I have it setup in
> my /etc/modprobe.conf as this:
> lias eth0 forcedeth
> alias scsi_hostadapter sata_nv
> alias char-major-61 lirc_i2c
> ...
> alias char-major-81 videodev
> alias char-major-81-0 ivtv
> alias char-major-81-1 ivtv
> alias char-major-81-2 ivtv
> install ivtv /sbin/modprobe saa7127; /sbin/modprobe --ignore-install
> ivtv; /sbin/modprobe ivtv-fb
> options ivtv-fb osd_compat=1
> install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe --ignore-install
> lirc_i2c
> I'm not sure if lircd is starting automatically. should I chamge
> something in the /etc/modprobe.conf ??

On Fedora I just put a simple modprobe script in
/etc/sysconfig/modules/ and it gets loaded early on in the boot

MythTV Official wiki:
MythTV users list archive:

"An investment in knowledge always pays the best interest." - Benjamin Franklin

More information about the mythtv-users mailing list