<div dir="ltr"><div dir="auto">Update:<div dir="auto"><br></div><div dir="auto">I removed the i2c module:</div><div dir="auto"><br></div><div dir="auto"># modprobe -r ir-kbd-i2c</div><div dir="auto"><br></div><div dir="auto">And scheduled a bunch of recordings via the hdpvr... Obviously, knowing that the channel wouldn't change.</div><div dir="auto"><br></div><div dir="auto">All the recordings were successful.</div><div dir="auto"><br></div><div dir="auto">I then reloaded the module. All recordings fail, sometimes within 5 minutes. So clearly the driver just doesn't work with the HD-PVR.</div><div dir="auto"><br></div><div dir="auto"><br></div><div>Has anyone gotten HDPVR IR blasting working on a newer kernel that doesn't have lirc_zilog?</div><div><br></div><div>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.</div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 23, 2019, 11:38 PM Justin Alcorn <<a href="mailto:justin@jalcorn.net" rel="noreferrer" target="_blank">justin@jalcorn.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 22, 2019 at 5:43 AM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" rel="noreferrer noreferrer" target="_blank">stephen_agent@jsw.gen.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sun, 21 Jul 2019 22:34:20 -0400, you wrote:<br>
<br>
>So with the upgrade to 18.04, it isn't just that LIRC was broken - They<br>
>took the entire lirc_zilog driver way.<br>
><br>
>They replaced it with ir-kbd-ic2, the notice is here:<br>
><a href="https://www.mess.org/2017/12/18/What-s-coming-in-v4-16-for-rc-core/" rel="noreferrer noreferrer noreferrer" target="_blank">https://www.mess.org/2017/12/18/What-s-coming-in-v4-16-for-rc-core/</a><br>
><br>
>So now it doesn't use the lirc.conf I was using to send IR blaster<br>
>information from the HDPVR to my STB. I did see in the dmesg the notice<br>
>"add enable_hdpvr parameter", so I created /etc/modprobe.d/ir-kbd-ic2.conf<br>
>with the line<br>
><br>
>options ir-kbd-ic2 enable_hdpvr<br>
><br>
>I now use my script that I used before and it lights up the HDPVR and no<br>
>errors are generated - but also, no information is sent to the STB.<br>
><br>
>Has anyone found documentation on how to use this driver to send blaster<br>
>information via the HDPVR ?<br>
<br>
My Ubuntu 18.04 is running kernel 4.15 (4.15.0-54-generic), so the<br>
changes on the above page are supposedly still in the future when 4.16<br>
arrives. Maybe Ubuntu has backported the changes to their version of<br>
the 4.15 kernel?<br>
<br>
In any case, it looks like the new driver is available and you are<br>
getting it to do something. So the problem is likely in your lirc<br>
configuration, which has all changed in the new lirc version. So what<br>
do you have in the main lirc config file<br>
(/etc/lirc/lirc_options.conf)? What driver file do you have loaded in<br>
/etc/lirc/lircd.conf.d? Do you have an IR remote input as well as the<br>
blaster on the HDPVR?<br><br></blockquote><div><br></div><div>Configuration is exactly the same on the 18.04 and on the old 16.04. which, it seems would be wrong.</div><div><br></div><div>Also note: There's still a comment on the HDPVR page on the wiki </div><div><br></div><div><a href="https://www.mythtv.org/wiki/Hauppauge_HD-PVR" rel="noreferrer noreferrer" target="_blank">https://www.mythtv.org/wiki/Hauppauge_HD-PVR</a><br></div><div><br></div><div>"<span style="color:rgb(37,37,37);font-family:sans-serif;font-size:14px">f you have the ir_kbd_i2c module loaded, this can cause the HD-PVR to hang after a short amount of recording (60-120 seconds). Remove this module via 'rmmod ir_kbd_i2c' and try again if this is affecting you."</span></div><div><span style="color:rgb(37,37,37);font-family:sans-serif;font-size:14px"><br></span></div><div><span style="color:rgb(37,37,37);font-family:sans-serif;font-size:14px">Every recording I've tried has hung after between 11 and 18 minutes with the i2c driver loaded, so I'm quite concerned :-(</span></div><div><br></div><div>lircd.conf.d has the devinput conf file. I've now renamed it to .dist. I'm not sure what to put in there for the HDPVR blaster.</div><div><br></div><div>etc/lirc/lirc_options.conf:<br></div><div># These are the default options to lircd, if installed as<br># /etc/lirc/lirc_options.conf. See the lircd(8) and lircmd(8)<br># manpages for info on the different options.<br>#<br># Some tools including mode2 and irw uses values such as<br># driver, device, plugindir and loglevel as fallback values<br># in not defined elsewhere.<br><br>[lircd]<br>nodaemon = False<br>driver = devinput<br>device = auto<br>output = /var/run/lirc/lircd<br>pidfile = /var/run/lirc/lircd.pid<br>plugindir = /usr/lib/x86_64-linux-gnu/lirc/plugins<br>permission = 666<br>allow-simulate = No<br>repeat-max = 600<br>#effective-user =<br>#listen = [address:]port<br>#connect = host[:port]<br>#loglevel = 6<br>#release = true<br>#release_suffix = _EVUP<br>#logfile = ...<br>#driver-options = ...<br><br>[lircmd]<br>uinput = False<br>nodaemon = False<br><br># [modinit]<br># code = /usr/sbin/modprobe lirc_serial<br># code1 = /usr/bin/setfacl -m g:lirc:rw /dev/uinput<br># code2 = ...<br><br><br># [lircd-uinput]<br># add-release-events = False<br># release-timeout = 200<br># release-suffix = _EVUP<br></div><div><br></div><div>I'll bet this is a problem...it still refers to zilog in hardware.conf. Again, not sure what to change....</div><div><br></div><div># /etc/lirc/hardware.conf<br>#<br>#Disable kernel support.<br>#Typically, lirc will disable in-kernel support for ir devices in order to<br>#handle them internally. Set to false to prevent lirc from disabling this<br>#in-kernel support. <br>#DISABLE_KERNEL_SUPPORT="true"<br><br>#Enable lircd<br>START_LIRCD="true"<br><br>#Don't start lircmd even if there seems to be a good config file<br>#START_LIRCMD="false"<br><br>#Try to load appropriate kernel modules<br>LOAD_MODULES="true"<br><br># Default configuration files for your hardware if any<br>LIRCMD_CONF=""<br><br>#Forcing noninteractive reconfiguration<br>#If lirc is to be reconfigured by an external application<br>#that doesn't have a debconf frontend available, the noninteractive<br>#frontend can be invoked and set to parse REMOTE and TRANSMITTER<br>#It will then populate all other variables without any user input<br>#If you would like to configure lirc via standard methods, be sure<br>#to leave this set to "false"<br>FORCE_NONINTERACTIVE_RECONFIGURATION="false"<br>START_LIRCMD=""<br><br>#Chosen IR transmitter<br>TRANSMITTER="HD-PVR"<br>TRANSMITTER_MODULES="lirc_dev lirc_zilog"<br>TRANSMITTER_DRIVER=""<br>TRANSMITTER_DEVICE="/dev/lirc0"<br>TRANSMITTER_SOCKET=""<br>TRANSMITTER_LIRCD_CONF=""<br>TRANSMITTER_LIRCD_ARGS=""</div><div><br></div><div><br></div><div>lircd.conf begins with this:</div><div><br></div><div>#<br># contributed by Jens Leuschner <<a href="mailto:leuschner@gmx.net" rel="noreferrer noreferrer" target="_blank">leuschner@gmx.net</a>><br>#<br># brand: Hauppauge<br># model: <br># supported devices: WinTV primo; WinTV pci; WinTV radio<br>#<br># This config file will work with both homebrew receivers and <br># original Hauppauge TV cards !!!<br>#<br><br>begin remote<br><br> name blaster<br> bits 32<br> flags RAW_CODES<br> eps 0<br> aeps 0<br> plead 0<br> gap 333333<br> repeat_bit 0<br> begin raw_codes<br> name 0_1_KEY_0<br> 65536<br><div><div dir="ltr" class="gmail-m_4247115509697207457m_1388233766415639783m_683395234417817208gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><br></div><div><br></div><div>lircmd.conf has just comments.</div><div><br></div></div></div></div></div></div></div><div> </div></div></div>
</blockquote></div>