[mythtv-users] lirc_serial move to serial_ir nightmare in kernel 4.12

[Tom Dexter]

On Wed, Aug 23, 2017 at 10:24 AM, Alec Leamas <leamas.alec at gmail.com> wrote:
>
>
> On 23/08/17 16:13, Tom Dexter wrote:
>>
>> On Wed, Aug 23, 2017 at 9:48 AM, Alec Leamas <leamas.alec at gmail.com>
>> wrote:
>>>
>>>
>>> On 23/08/17 14:37, Tom Dexter wrote:
>>>
>>>
>>>> Alec: Regarding your request on the other thread to
>>>> increase the log level and start lircd, and try irw, I made sure my
>>>> lirc_options.conf had:
>>>>
>>>> loglevel       = 7
>>>> logfile = /root/lirc.log
>>>>
>>>> I use sysklogd and I'd have to figure out how to reoconfigure that to
>>>> show debug level output. With the above, I do get logging to that
>>>> file, but it doesn't appear any different than what I was getting:
>>>>
>>>> Aug 23 08:32:45.279510 mythfront lircd: Info: lircd:  Opening log,
>>>> level:
>>>> Info
>>>>
>>>
>>> Something is very broken here. It seems that for some reason your lircd
>>> does
>>> not pickup the setting from lirc_options.conf. I have no idea why.  The
>>> recommended value in this case is 'debug', not '7', though.
>>>
>>> You could test to add the --loglevel command line option in the startup
>>> script.
>>>
>>> Also, a link to the lircd.conf you are using would make sense.
>>>
>>> --a
>>>
>> Why does the example show "loglevel = 6"?:
>>
>> https://sourceforge.net/p/lirc/git/ci/master/tree/lirc_options.conf
>>
>> It took be forever to set up everything for that test. I can do it
>> over again if that was incorrect. Seems really odd though.
>>
> The loglevel option is documented in the lircd(8) manpage - the options file
> keys corresponds exactly to the command line options. The example is just,
> well, an example.
>
> If you still don't get the expected behaviour, just stop all services and
> run lircd from the commandline. You probably then need the --nodaemon option
> together with --loglevel, --logfile, --device and --driver.
>
> Cheers!
>
> --alec

No clue what's up. Here's what I just did without the service running:

lircd --nodaemon --loglevel=debug --logfile=/root/lirc.log
--device=/dev/lirc0 --driver=default /etc/lirc/lircd.conf

That actually started and did in fact log to /root/lirc.log, but
*exactly* as I was getting before:

Aug 23 10:41:25.177433 mythfront lircd: Info: lircd:  Opening log, level: Info
Aug 23 10:41:25.184102 mythfront lircd: Info: Initial device: /dev/lirc0
Aug 23 10:41:25.184353 mythfront lircd: Info: [lirc] protocol is enabled
Aug 23 10:41:25.184495 mythfront lircd: Info: Initial device: /dev/lirc0
Aug 23 10:41:25.184696 mythfront lircd: Info: [lirc] protocol is enabled
Aug 23 10:41:25.184835 mythfront lircd: Debug: lircd:  Opening log, level: Debug
Aug 23 10:41:25.185144 mythfront lircd: Warning: Running as root
Aug 23 10:41:25.185392 mythfront lircd: Info: Using remote: TIVO34.
Aug 23 10:41:25.186012 mythfront lircd: Notice: lircd(default) ready,
using /var/run/lirc/lircd
Aug 23 10:41:51.972637 mythfront lircd: Notice: accepted new client on
/var/run/lirc/lircd
Aug 23 10:41:51.972785 mythfront lircd: Info: [lirc] protocol is enabled
Aug 23 10:42:15.926433 mythfront lircd: Info: removed client

Don't know what to say about that, as it rules out everything except
lircd itself(?).

Tom