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

[Tom Dexter]

On Wed, Aug 23, 2017 at 10:46 AM, Tom Dexter <digitalaudiorock at gmail.com> wrote:

>
> 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

OK...the trace1 level seems to work:
lircd --nodaemon --loglevel=trace1 --logfile=/root/lirc.log
--device=/dev/lirc0 --driver=default /etc/lirc/lircd.conf

Which the attached log. The irw attempts are towards the end.

Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lirc.log
Type: text/x-log
Size: 17004 bytes
Desc: not available
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20170823/7bc6dc39/attachment.bin>