[mythtv-users] Linux: Replacement for lirc_zilog driver

Justin Alcorn justin at jalcorn.net
Sat Jul 27 18:11:46 UTC 2019 

And now suddenly my /dev/lirc0 is gone.

root at gossamer:/var/log# sudo systemctl status lircd
● lircd.service - Flexible IR remote input/output application support
   Loaded: loaded (/lib/systemd/system/lircd.service; enabled; vendor
preset: enabled)
   Active: active (running) since Sat 2019-07-27 14:08:25 EDT; 49s ago
     Docs: man:lircd(8)
           http://lirc.org/html/configure.html
 Main PID: 1097 (lircd)
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/lircd.service
           └─1097 /usr/sbin/lircd --nodaemon

Jul 27 14:09:12 gossamer lircd-0.10.0[1097]: Error: could not get file
information for /dev/lirc0
Jul 27 14:09:12 gossamer lircd-0.10.0[1097]: default_init(): No such file
or directory
Jul 27 14:09:13 gossamer lircd[1097]: lircd-0.10.0[1097]: Error: could not
get file information for /dev/lirc0
Jul 27 14:09:13 gossamer lircd[1097]: lircd-0.10.0[1097]: default_init():
No such file or directory
Jul 27 14:09:13 gossamer lircd-0.10.0[1097]: Error: could not get file
information for /dev/lirc0
Jul 27 14:09:13 gossamer lircd-0.10.0[1097]: default_init(): No such file
or directory
Jul 27 14:09:14 gossamer lircd[1097]: lircd-0.10.0[1097]: Error: could not
get file information for /dev/lirc0
Jul 27 14:09:14 gossamer lircd[1097]: lircd-0.10.0[1097]: default_init():
No such file or directory
Jul 27 14:09:14 gossamer lircd-0.10.0[1097]: Error: could not get file
information for /dev/lirc0
Jul 27 14:09:14 gossamer lircd-0.10.0[1097]: default_init(): No such file
or directory

I've checked to be sure that the blaster is fully connected to the HDPVR
and rebooted a couple of times.

help ?


-- 
Justin B. Alcorn
The views expressed are not necessarily my own, much less anyone else's
PGP Fingerprint CCEB F776 C3FD 1050 C8DB  532E B8B9 BED7 7764 406C


On Sat, Jul 27, 2019 at 1:18 PM Justin Alcorn <justin at jalcorn.net> wrote:

> I downloaded a 4.15 kernel and installed and booted on it.  plugged back
> in my HDPVR blaster.   Looks better, but not quite working:
>
> jalcorn at gossamer:~$ lsmod | grep zilog
> lirc_zilog             24576  0
> lirc_dev               16384  2 lirc_zilog
> jalcorn at gossamer:~$ irsend send_once blaster 0_41_KEY_POWER
>
> hardware does not support sending
> Error running command: Input/output error
> jalcorn at gossamer:~$ uname -a
> Linux gossamer 4.15.0-041500-generic #201802011154 SMP Thu Feb 1 11:55:45
> UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
>
> this does. however, seem like a better option at the moment rather than
> trying to get the Iguana IR blaster working...because I'm leaving for
> vacation tomorrow and I'd like my DVR to be working!
> ===========
> I copied my exact /etc/lirc config from my 16.04 setup, rebooted on the
> 4.15 kernel.
>
> root at gossamer:/etc/lirc# systemctl status lircd
> ● lircd.service - Flexible IR remote input/output application support
>    Loaded: loaded (/lib/systemd/system/lircd.service; enabled; vendor
> preset: enabled)
>    Active: active (running) since Sat 2019-07-27 13:14:59 EDT; 4s ago
>      Docs: man:lircd(8)
>            http://lirc.org/html/configure.html
>  Main PID: 5105 (lircd)
>     Tasks: 2 (limit: 4915)
>    CGroup: /system.slice/lircd.service
>            └─5105 /usr/sbin/lircd --nodaemon
>
> Jul 27 13:14:59 gossamer lircd-0.10.0[5105]: Warning: Running as root
> Jul 27 13:14:59 gossamer lircd-0.10.0[5105]: Info: Using remote: blaster.
> Jul 27 13:14:59 gossamer lircd[5105]: lircd-0.10.0[5105]: Info: Using
> remote: Hauppauge.
> Jul 27 13:14:59 gossamer lircd-0.10.0[5105]: Info: Using remote: Hauppauge.
> Jul 27 13:14:59 gossamer lircd[5105]: lircd-0.10.0[5105]: Info: Using
> remote: hauppauge_pvr.
> Jul 27 13:14:59 gossamer lircd[5105]: lircd-0.10.0[5105]: Info: Using
> remote: Hauppauge_350.
> Jul 27 13:14:59 gossamer lircd[5105]: lircd-0.10.0[5105]: Notice:
> lircd(devinput) ready, using /var/run/lirc/lircd
> Jul 27 13:14:59 gossamer lircd-0.10.0[5105]: Info: Using remote:
> hauppauge_pvr.
> Jul 27 13:14:59 gossamer lircd-0.10.0[5105]: Info: Using remote:
> Hauppauge_350.
> Jul 27 13:14:59 gossamer lircd-0.10.0[5105]: Notice: lircd(devinput)
> ready, using /var/run/lirc/lircd
> root at gossamer:/etc/lirc# exit
> logout
> jalcorn at gossamer:~$ irsend send_once blaster 0_41_KEY_POWER
>
> hardware does not support sending
> Error running command: Input/output error
> jalcorn at gossamer:~$ ls -l /dev/lirc*
> crw-rw---- 1 root video 241, 0 Jul 27 13:11 /dev/lirc0
> lrwxrwxrwx 1 root root      15 Jul 27 13:11 /dev/lircd -> /run/lirc/lircd
> jalcorn at gossamer:~$ sudo lsmod | egrep 'hdpvr|lirc'
> lirc_zilog             24576  0
> lirc_dev               16384  2 lirc_zilog
> rc_core                36864  1 lirc_dev
> hdpvr                  32768  0
> v4l2_dv_timings        28672  1 hdpvr
> videodev              176128  1 hdpvr
>
>
>
>
>
>
>
> --
> Justin B. Alcorn
> The views expressed are not necessarily my own, much less anyone else's
> PGP Fingerprint CCEB F776 C3FD 1050 C8DB  532E B8B9 BED7 7764 406C
>
>
> On Thu, Jul 25, 2019 at 11:21 AM Stephen Worthington <
> stephen_agent at jsw.gen.nz> wrote:
>
>> On Thu, 25 Jul 2019 08:30:24 -0400, you wrote:
>>
>> >Update:
>> >
>> >I removed the i2c module:
>> >
>> ># modprobe -r ir-kbd-i2c
>> >
>> >And scheduled a bunch of recordings via the hdpvr... Obviously, knowing
>> >that the channel wouldn't change.
>> >
>> >All the recordings were successful.
>> >
>> >I then reloaded the module.   All recordings fail, sometimes within 5
>> >minutes.   So clearly the driver just doesn't work with the HD-PVR.
>> >
>> >
>> >Has anyone gotten HDPVR IR blasting working on a newer kernel that
>> doesn't
>> >have lirc_zilog?
>> >
>> >Or what other opetions for IR blasting would there be?   I guess I never
>> >thought about the fact that there's no reason it has to be the HDPVR
>> >changing the channel.
>>
>> What kernel are you using?  My Ubuntu 18.04 currently has
>> 4.15.0-55-generic, which still has lirc_zilog.  So if you can revert
>> to a 4.15 kernel, you should be able to use lirc_zilog until the
>> problem with ir-kbd-i2c can be fixed.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://lists.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190727/4f854375/attachment.html>

More information about the mythtv-users mailing list