[mythtv-users] LIRC problem: hardware does not support sending

Alec Leamas leamas.alec at gmail.com
Mon Jan 23 20:45:33 UTC 2017



On 23/01/17 20:52, Warren Sturm wrote:
> On Mon, 2017-01-23 at 11:43 -0800, Paul Stillwell wrote:
>> Hi,
>>
>> I recently update from Fedora 23 to Fedora 24. In Fedora 23, LIRC was
>> working perfectly, but under Fedora 24 when I try to run my channel
>> changing script I get the error:
>>
>> hardware does not support sending
>> Error running command: Input/output error
>>
>> I have tried everything I can think of to fix this issue. I confirmed
>> that /dev/lirc0 exists, I have made sure that lurched.service and
>> lidcmd.service are both enabled and running, and I have checked that
>> the /dev/lirc0 has the proper permission (they are set to 660).
>>
>> Googling around for this results in nothing anywhere close to recent.
>>
>> Any ideas on what could be going wrong?
>>
>> Paul

IIRC the default driver changed from 'default' (silly name!) in 0.9.3 to 
devinput in 0.9.4.  So, it you didn't actually define what driver you 
are using, this could give these symptoms (the devinput driver certainly 
does not allow sending)

> Check your /usr/lib/systemd/system/lircd.service.  It may have been
> over-written by the update.

Indeed, this is how systemd is designed.

>  Make a copy in /etc/systemd/system and
> modify the copy.  Mine now looks like this:

Unless you have *very* specific needs this is not required. Since 0.9.2 
lirc supports the lirc_options-conf file. This is used to define all the
configuration described below, including the  modprobe stuff if it's 
required. (The vast majority of the kernel driver used  by LIRC are 
autoloaded by the kernel).

Also note that the service to enable is lircd.socket, not lircd.service. 
This is to work-around some otherwise hard to debug race conditions 
during startup.

Bottom line:  Check that the /lib/systemd/*lirc* files are as shipped, 
remove any local service definitions in /etc/systemd/system and update 
lirc_options.conf, primarely with driver =... and device =... In most 
cases that should be enough.



Cheers!

--alec


More information about the mythtv-users mailing list