Hmm.<br><br>Well, I do have some interesting results. First, from dmesg:<br><br>lirc_dev: IR Remote Control driver registered, major 61<br>lirc_i2c: chip 0x10020 found @ 0x18 (Hauppauge IR)<br>lirc_dev: lirc_register_plugin: sample_rate: 10<br>
lirc_serial: auto-detected active high receiver<br>lirc_dev: lirc_register_plugin: sample_rate: 0<br><br><br>It does say that lirc_serial (which is what's supposed to be connected to my blaster) has detected a receiver, when it's actually a transmitter. I don't know if that makes a difference.<br>
<br>Far more interestingly, when I manually do "modprobe lirc_serial", that is EXACTLY when the LED lights up (and then stays on forever until I turn the box off). So...maybe some sort of misconfiguration of lirc_serial? I installed lirc from yum and so didn't ever run ./configure....what kind of configuration can I be doing before I do the modprobe?<br>
<br>My receiver doesn't have firewire, StarChoice is very strict about not allowing outside things touch their receivers, heh.<br><br>Thanks again to all who have commented so far,<br>--Trevor<br><br><br><div><span class="gmail_quote">On 22/03/2008, <b class="gmail_sendername">Steve Wilson</b> <<a href="mailto:mythtv_arizona@yahoo.com">mythtv_arizona@yahoo.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br> --- Trevor Hill <<a href="mailto:trevor.hill@gmail.com">trevor.hill@gmail.com</a>> wrote:<br> <br> > I haven't posted here in a while. I had a MythTV<br> > box that ran flawlessly<br> > for about three years with only minor updates until<br>
> it gave up the ghost a<br> > few weeks ago. I broke down and bought almost a<br> > whole new set of parts<br> > (motherboard, processor, hard driver, etc.) rather<br> > than trying to figure out<br> > which of the parts on my old machine had failed.<br>
> Everything is going well!<br> > Except for the IR blaster. I have a motorola<br> > receiver (for StarChoice) and<br> > a plain old RS232 IR blaster I got from<br> > <a href="http://irblaster.info">irblaster.info</a>.<br>
><br> > The configuration looks okay -- I've followed the<br> > directions at<br> > <a href="http://www.htpcug.com/blaster.htm">http://www.htpcug.com/blaster.htm</a>. When I try to<br> > run the change channel<br>
> script, I don't get any errors or weird log entries,<br> > but nothing happens.<br> > The doubly strange thing: the LED on the blaster<br> > that is supposed to blink<br> > when a signal is sent is on constantly from some<br>
> point during the startup<br> > process (I'm not exactly sure where) until I turn<br> > the machine off. This is<br> > obviously not normal. :)<br> ><br> > I had it running on COM1 (IRQ4) at first. After<br>
> that didn't go very well, I<br> > tried switching it to COM2. When I'd changed the<br> > IRQ of the single serial<br> > port in the BIOS but hadn't reconfigured the<br> > modprobe.conf yet, the LED on<br>
> the blaster obviously didn't come on for that<br> > reboot. However, when I fixed<br> > up modprobe.conf and rebooted again, we were back to<br> > the old situation: LED<br> > on all the time, no signals being sent, no error<br>
> messages.<br> ><br> > Any ideas? I've mostly ruled out lircd.conf and<br> > such being a problem as<br> > that wouldn't cause the IR blaster to not send any<br> > signals at all, just send<br>
> the wrong ones.<br> ><br> > My current modprobe.conf:<br> ><br> > [snip]<br> > alias char-major-61-0 lirc_i2c<br> > alias char-major-61-1 lirc_serial<br> > options lirc_serial irq=3 io=0x2f8<br>
> ####IR setup####<br> > install lirc_i2c /sbin/modprobe ivtv; /sbin/modprobe<br> > --ignore-install<br> > lirc_i2c<br> > install lirc_serial setserial /dev/ttyS1 uart none;<br> > /sbin/modprobe<br> > --ignore-install lirc_serial<br>
> [/snip]<br> ><br> > rc.local:<br> ><br> > /sbin/modprobe lirc_i2c<br> > /sbin/modprobe lirc_serial<br> > /usr/sbin/lircd --device=/dev/lirc0<br> > --output=/dev/lircd<br> > /usr/sbin/lircd --driver=default --device=/dev/lirc1<br>
> --output=/dev/lircd1<br> > --pidfile=/var/run/lircd1.pid<br> ><br> ><br> > # ls -al /dev/lirc*<br> > lrwxrwxrwx 1 root root 5 2008-03-21 20:23<br> > /dev/lirc -> lirc0<br> > crwxrwxrwx 1 root lirc 61, 0 2008-03-21 20:23<br>
> /dev/lirc0<br> > crwxrwxrwx 1 root lirc 61, 1 2008-03-21 20:23<br> > /dev/lirc1<br> > srwxrwxrwx 1 root root 0 2008-03-21 20:23<br> > /dev/lircd<br> > srwxrwxrwx 1 root root 0 2008-03-21 20:23<br>
> /dev/lircd1<br> ><br> ><br> > --Trevpr<br> <br>> > _______________________________________________<br> > mythtv-users mailing list<br> > <a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
><br> <a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br> ><br> <br> I assume you've done the setup in the link since you<br> have a remote control as well. Does the remote work?<br>
<br> Also, I'd try to manually start lirc to see if any<br> errors popup so I'd comment out the lines in rc.local<br> and then I'd do each modprobe then start lirc. I'd<br> also add the --logfile switch to lirc. I'd then do a<br>
dmesg | grep lirc to see if it says anything doesn't<br> look right. After that, I'd manually try sending one<br> code at a time in a terminal to see if it gives you<br> any errors.<br> <br> #irsend --device=/dev/lircd1 SEND_ONCE<br>
"REMOTE_NAME_in_lircd" 1<br> <br><br> <br> ____________________________________________________________________________________<br> Looking for last minute shopping deals?<br> Find them fast with Yahoo! Search. <a href="http://tools.search.yahoo.com/newsearch/category.php?category=shopping">http://tools.search.yahoo.com/newsearch/category.php?category=shopping</a><br>
<br> </blockquote></div><br>