<br><br><div class="gmail_quote">On Wed, Apr 21, 2010 at 1:13 PM, Ron Garrison <span dir="ltr"><<a href="mailto:ron.garrison@gmail.com">ron.garrison@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class="h5">On Wed, Apr 21, 2010 at 10:12 AM, Greg Woods <<a href="mailto:greg@gregandeva.net">greg@gregandeva.net</a>> wrote:<br>
> On Sun, 2010-04-18 at 20:26 -0700, Yeechang Lee wrote:<br>
>> On Sun, Apr 18, 2010 at 10:10 AM, Greg Woods <<a href="mailto:greg@gregandeva.net">greg@gregandeva.net</a>> wrote:<br>
>> > I do know one way: rent another "real" STB from Comcast and get<br>
>> > another HD-PVR (then I get the deal with the fun of trying to keep<br>
>> > multiple firewire devices straight for channel changing).<br>
>><br>
>> Despite the up-front and monthly cost this is indeed your best<br>
>> bet:<br>
><br>
> I have thought about this and decided that a second HD-PVR is the way to<br>
> go, freeing me from the need for an IR blaster and giving me a second<br>
> tuner for all of my HD channels, not just the former-analog ones that I<br>
> have recently lost Myth access to. I already have a second STB which is<br>
> a Comcast DVR box, so I'll hook that up to the new HD-PVR. No additional<br>
> monthly cost, but I will have to be careful not to schedule more than<br>
> one recording at a time on the Comcast DVR, and be careful when I use it<br>
> for playback, so that there is always one tuner free when Myth wants to<br>
> use it. The potential for this kind of screw up leading to failed<br>
> recordings is the major down side to going this route (along with the<br>
> $200 for another HD-PVR, but at least there is some added benefit as<br>
> well). At some point I may decide this is just too much trouble and turn<br>
> in the DVR box for a regular STB. But having the Comcast DVR as a backup<br>
> when my Myth box went south for whatever reason has been a life saver<br>
> more than once, along with the extra two tuners it provides during<br>
> football season :-)<br>
><br>
>><br>
>> * It is 100% future-proof, no matter what cable or satellite provider<br>
>> you switch to in the future<br>
><br>
> Not entirely of course. The MPAA and their cable company stooges are<br>
> still wanting to close "the analog hole". The conversion of analog to<br>
> encrypted digital is only the first step, I do not expect them to give<br>
> up working on the component output. Right now I can't think of a way<br>
> they can close this off without also rendering some customer TV's<br>
> incapable of HD, but that doesn't mean they won't still come up with<br>
> something or that they won't eventually get their puppets the FCC to<br>
> approve letting them close it off anyway. Nothing is ever 100% future<br>
> proof.<br>
><br>
>> * You're already familiar with the HD-PVR<br>
><br>
> True, another point in favor of this.<br>
><br>
>> * FireWire channel switching is 100% reliable unlike IR blasters, and<br>
>> uses GUID so the two boxes would always be distinct<br>
><br>
> What's a GUID? Is this documented somewhere I can go read about? I'm<br>
> going to have to deal with it soon.<br>
><br>
>> * Writing a udev rule to give the two HD-PVRs distinct /dev node<br>
>> labels is easy (took me about 15 seconds to figure out how to do so<br>
>> for the first time)<br>
><br>
> I'm sure I can manage that part, but if you want to let me see the ones<br>
> you have, it would help :-)<br>
><br>
>> * You get HD-quality access to every channel you pay for already<br>
><br>
> ...and I can free up a PCI slot also by removing the PVR-500 brick, er,<br>
> card. May be useful in the future.<br>
><br>
> Comcast sucks.<br>
><br>
> --Greg<br>
<br>
</div></div>And with the second HDPVR, you will have two irblasters (one per<br>
hdpvr) that you can use to to control your DTAs and unbrick your<br>
PVR-500 :-)<br>
<br>
Not sure if the hdpvr blasters are fully working yet though. I<br>
thought I read somewhere that they weren't. I haven't tried myself.<br>
<font color="#888888"><br>
Ron<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users" target="_blank">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></div></div></blockquote><div><br>This is a very old thread, but the info was relevant to me getting my mceusb GP-IR02BK IR blaster working so I thought I would add something to try and help the next guy. I had the exact same problem with lirc accepting input for my blaster and not giving any errors. I set the ehome remote drivers in the kernel, added the firmware to /lib/firmware, and I was seeing the IR device in dmesg, but it would not work. I finally found that even though I had usb working in the kernel, I needed to enable the relevant USB kernel device driver options for my motherboard. I did that and boom, it worked.<br>
<br>below are some reference info that would have been helpful for me to know when something is loading right<br><br>lsusb<br>Bus 002 Device 003: ID 1784:0008 TopSeed Technology Corp. eHome Infrared Transceiver<br><br>one init.d # dmesg | grep IR | grep -v IRQ<br>
USB Serial support registered for IR Dongle<br>ir_usb: v0.5:USB IR Dongle driver<br>lirc_dev: IR Remote Control driver registered, major 253<br>IR RC5(x) protocol handler initialized<br>IR RC6 protocol handler initialized<br>
IR MCE Keyboard/mouse protocol handler initialized<br>IR LIRC bridge handler initialized<br>Registered IR keymap rc-rc6-mce<br>input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input3<br>tveeprom 0-0000: has radio, has IR receiver, has no IR transmitter<br>
<br>one init.d # dmesg | grep mce<br>mce: CPU supports 7 MCE banks<br>usbcore: registered new interface driver mceusb<br>Registered IR keymap rc-rc6-mce<br>input: MCE IR Keyboard/Mouse (mceusb) as /devices/virtual/input/input3<br>
rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0<br>mceusb 2-1.1:1.0: Registered Topseed Technology Corp. eHome Infrared Transceiver with mce emulator interface version 1<br>mceusb 2-1.1:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x1 active)<br>
<br>
# relevant lines or /etc/init.d/lircd<br>
start-stop-daemon --start --quiet --pidfile /var/run/lirc/lircd_recv.pid --exec /usr/sbin/lircd -- \<br>
-P /var/run/lirc/lircd_recv.pid --output=/var/run/lirc/lircd_recv --driver=devinput --device=/dev/input/event2<br>
start-stop-daemon --start --quiet --pidfile /var/run/lirc/lircd_send.pid --exec /usr/sbin/lircd -- \<br>
-P /var/run/lirc/lircd_send.pid --output=/var/run/lirc/lircd_send --driver=default --device=/dev/lirc0<br><br># for testing<br>
irsend --device=/var/run/lirc/lircd_send SEND_ONCE dish 1<br><br></div></div><br>