On Thu, Jul 7, 2011 at 11:11 PM, Tom Bongiorno <span dir="ltr"><<a href="mailto:two.bits.11@gmail.com">two.bits.11@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div></div><div class="h5"><div>On Thu, Jul 7, 2011 at 1:08 PM, Michael Lynch <span dir="ltr"><<a href="mailto:lynchmv@gmail.com" target="_blank">lynchmv@gmail.com</a>></span> wrote:</div><div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Tom, I *just* got it working. I must admit, I followed the wiki<br>
instructions and kept failing. I came across an irc log where Bierdo<br>
was helping echosysp with a similar issue with the hdpvr module. I<br>
read along with that and noticed that the wiki makes it seem like you<br>
can select just the pvr related modules in the v4l/.conf file to<br>
compile, but that apparently isn't true. I had to compile all of the<br>
modules from the media_build tree and then install them and *then*<br>
make sure that there weren't any duplicate modules after the install.<br>
There were some and I had to clean those up, though I must admit, I<br>
only cleaned up the hdvpr, lirc_zilog, lirc_dev and v4l_compat<br>
modules. After that, I got:<br>
<br>
v4l2_compat_ioctl32: Unknown symbol put_compat_timespec (err 0)<br>
<br>
in dmesg after trying to insert the hdpvr module, so I copied over my<br>
original v4l2-compat-ioctl32.ko from my kernel tree to the module<br>
location, ran depmod -a and then had success. Then I modprob'd<br>
lirc_zilog and got my /dev/lirc0 device. Success!<br>
<div><div></div><div><br>
<br>
<br>
On Thu, Jul 7, 2011 at 10:01 AM, Tom Bongiorno <<a href="mailto:two.bits.11@gmail.com" target="_blank">two.bits.11@gmail.com</a>> wrote:<br>
> On Thu, Jul 7, 2011 at 8:59 AM, Michael Lynch <<a href="mailto:lynchmv@gmail.com" target="_blank">lynchmv@gmail.com</a>> wrote:<br>
>><br>
>> I'm in the process of moving my backend to a new machine and am having<br>
>> issues getting the HDPVR blaster to work. I've followed the wiki page<br>
>> for enabling the transmitter and am not having any luck when inserting<br>
>> the lirc_zilog module. The module loads fine but does not create the<br>
>> /dev/lirc* device. Any suggestions on where to go from here? Here is<br>
>> my relevant system info, if more is needed, please let me know.<br>
>><br>
>> root@mythtv:~# uname -a<br>
>> Linux mythtv 2.6.37.6 #3 SMP Sat Apr 9 22:49:32 CDT 2011 x86_64<br>
>> Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz GenuineIntel GNU/Linux<br>
>><br>
>> root@mythtv:~# cat /etc/slackware-version<br>
>> Slackware 13.37.0<br>
>><br>
>> root@mythtv:~# lircd -n<br>
>> lircd: lircd(default) ready, using /var/run/lirc/lircd<br>
>> lircd: accepted new client on /var/run/lirc/lircd<br>
>> lircd: could not get file information for /dev/lirc<br>
>> lircd: default_init(): No such file or directory<br>
>> lircd: WARNING: Failed to initialize hardware<br>
>> lircd: error processing command: SEND_ONCE blaster select<br>
>> lircd: hardware does not support sending<br>
>> lircd: removed client<br>
>><br>
>> root@mythtv:~# modinfo lirc_zilog<br>
>> filename:<br>
>><br>
>> /lib/modules/<a href="http://2.6.37.6/kernel/drivers/linux/drivers/staging/lirc/lirc_zilog.ko" target="_blank">2.6.37.6/kernel/drivers/linux/drivers/staging/lirc/lirc_zilog.ko</a><br>
>> alias: lirc_pvr150<br>
>> license: GPL<br>
>> author: Gerd Knorr, Michal Kochanowicz, Christoph Bartelmus,<br>
>> Ulrich Mueller, Stefan Jahn, Jerome Brock, Mark Weaver, Andy Walls<br>
>> description: Zilog/Hauppauge infrared transmitter driver (i2c stack)<br>
>> depends: i2c-core,lirc_dev<br>
>> vermagic: 2.6.37.6 SMP mod_unload<br>
>> parm: minor:Preferred minor device number (int)<br>
>> parm: debug:Enable debugging messages (bool)<br>
>> parm: tx_only:Only handle the IR transmit function (bool)<br>
>><br>
>><br>
>> dmesg output after 'modprobe lirc_zilog debug=1 ':<br>
>> [34628.832421] lirc_zilog: Zilog/Hauppauge IR driver initializing<br>
>> [34628.833411] lirc_zilog: initialization complete<br>
>><br>
>> /var/log/message output after 'modprobe lirc_zilog debug=1' :<br>
>> Jul 7 07:55:11 mythtv udevd[1216]: seq 1709 queued, 'add' 'module'<br>
>> Jul 7 07:55:11 mythtv udevd[1216]: passed 118 bytes to netlink<br>
>> monitor 0x61f1f0<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: seq 1709 running<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: device 0x633970 has devpath<br>
>> '/module/lirc_zilog'<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: no db file to read<br>
>> /dev/.udev/db/+module:lirc_zilog: No such file or directory<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: RUN<br>
>> 'socket:@/org/freedesktop/hal/udev_event'<br>
>> /lib/udev/rules.d/90-hal.rules:2<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: passed 101 bytes to socket<br>
>> monitor 0x633970<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: passed -1 bytes to netlink<br>
>> monitor 0x633620<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: seq 1709 processed with 0<br>
>> Jul 7 07:55:11 mythtv udevd[1216]: seq 1709 done with 0<br>
>> Jul 7 07:55:11 mythtv kernel: [28846.771131] lirc_zilog:<br>
>> Zilog/Hauppauge IR driver initializing<br>
>> Jul 7 07:55:11 mythtv udevd[1216]: seq 1710 queued, 'add' 'drivers'<br>
>> Jul 7 07:55:11 mythtv udevd[1216]: passed 140 bytes to netlink<br>
>> monitor 0x61f1f0<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: seq 1710 running<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: device 0x621220 has devpath<br>
>> '/bus/i2c/drivers/Zilog!Hauppauge i2c IR'<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: no db file to read<br>
>> /dev/.udev/db/+drivers:Zilog!Hauppauge i2c IR: No such file or<br>
>> directory<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: device 0x633730 has devpath<br>
>> '/bus/i2c/drivers'<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: device 0x633ab0 has devpath<br>
>> '/bus/i2c'<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: RUN<br>
>> 'socket:@/org/freedesktop/hal/udev_event'<br>
>> /lib/udev/rules.d/90-hal.rules:2<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: passed 144 bytes to socket<br>
>> monitor 0x621220<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: passed -1 bytes to netlink<br>
>> monitor 0x633620<br>
>> Jul 7 07:55:11 mythtv udevd-work[2069]: seq 1710 processed with 0<br>
>> Jul 7 07:55:11 mythtv udevd[1216]: seq 1710 done with 0<br>
>> Jul 7 07:55:11 mythtv kernel: [28846.772349] lirc_zilog:<br>
>> initialization complete<br>
>> _______________________________________________<br>
>> mythtv-users mailing list<br>
>> <a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
>> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
><br>
> Michael,<br>
><br>
> Nice timing! I am having the same exact issue as we speak. I am using<br>
> Mythbuntu 11.04.<br>
><br>
> Ubuntu 11.04 (GNU/Linux 2.6.38-8-generic i686)<br>
><br>
> Comcast completely broke Firewire control with a recent guide overhaul and I<br>
> need this to change channels.<br>
><br>
> -Tom<br>
><br>
> _______________________________________________<br>
> mythtv-users mailing list<br>
> <a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
> <a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
><br>
><br>
_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
</div></div></blockquote></div><br></div></div><div>Michael, Thanks for the info. I will have to re-read the instructions, but I was under the impression that there was little I had to do from the wiki.</div><br>"Ubuntu/MythBuntu 11.04 currently has built-in support for the HD-PVR's IR Blaster. Follow the steps below to enable the IR transmitter."<div>
<br></div><div>I thought I followed the 10 or so steps. I hope to try again this weekend. I know I screwed something up tinkering.</div><div><br></div><font color="#888888"><div>-Tom</div>
</font></blockquote></div><br>Doh!!!!!<br><br>I am an idiot! Of the few steps that I have to do to get this working, I skipped one. I don't know how, but I did. I forgot to copy the firmware into the /lib/firmware directory. This fixed my no /dev/lirc0 problem.<br>
<br>My new problem is that I cannot get it to blast anything. After an hour or two, I realized that the Hauppauge IR Blaster cable if proprietary and my generic IR Blaster cable and 3.5 to 2.5mm adapter were not going to work. I ordered it from Hauppauge for under $10 shipped. For completeness, I will report if I get it working when I receive the cable.<br>
<br>BTW, since I am running Mythbuntu 11.04, there is no compilation necessary. I just have to follow "Steps to Enable IR Transmitter" from the "IR Transmitter Support" section. I think! :)<br><br>-Tom<br>