HD-PVR IR Driver Patch for .32 available?
Submitted by Balloondoggies on May 25, 2010 - 9:29am
Due to issues with my serial blaster with an HDPVR I want to change to using the HDPVR IR Blaster, however I see that Jarod said the driver for the blaster was left out of the .32 kernel. (http://www.gossamer-threads.com/lists/mythtv/users/435408)
I am currently running kernel 2.6.32.12.115.fc12.
What would be the best way to patch the driver into this kernel?
This is something I have never done before so I am not exactly sure where to look for it.
FWIW, I'm using serial
FWIW, I'm using serial blaster and HDPVR at the same time with no issues. If you'd like some help with that, I'd be happy to try -- one thing I needed to do after install was add 'setserial /dev/ttyS0 uart none'
to my /etc/rc.local file before it calls the mythdora script.
I think you're probably best waiting for the experts to fix the HDPVR IR issues.
Thanks for the info, the
Thanks for the info, the reason I am looking at the HDPVR blaster is because of this issue:
http://www.mythdora.com/?q=node/5392
I posted to the Mythtv user group and Patrick's replied saying he had the same/similar issue so he went to the HDPVR Blaster, so I figured it was worth a shot.
http://www.gossamer-threads.com/lists/mythtv/users/437697
I would LOVE to keep my serial blaster, but right now I can only record on 1 input, recording on 2 causes crashes and such (as explained in the mythdora.com link I provided). It appears to revolve around LIRC for some reason.
Per a suggestion for troubleshooting on the mythlist, I tried "/bin/true" as the channel change script *by passing LIRC* and the system is stable as ever. I am not 100% sure what is going on.
I see that Jarod's post is from January and I have seen reports of it working since then. However some of the links on Jarod's page is broken anyway, so I really can't use that.
Hmm... so it seems like the
Hmm... so it seems like the serial blaster doesn't work when the HD Homerun is recording?
Have you tried changing the serial port?
Have you tried removing the HDPVR to see if it has any impact on situation? Try just unplugging it, starting a HD Homerun recording, then run the changechannel.sh script and see what happens.
Actually LIRC hangs the
Actually LIRC hangs the entire machine when ANY other tuner is recording.
"Have you tried removing the HDPVR to see if it has any impact on situation? Try just unplugging it, starting a HD Homerun recording, then run the changechannel.sh script and see what happens."
Yep, same results, entire system hangs.
So for giggles I decided to a clean install, here is what I did:
1) Install from DVD using the default setup selecting to use the Mythdora Update Repo as well
2) Test LIRC by running the channelchange.sh script to confirm it is working,it was and blasted without issue
3) Added my HD Homerun to the mythtvsetup
4) Scanned for channels
5) Setup a manual recording for 5 mins on the HDHR
6) While it was recording I ran the changechannel.sh script and BOOM entire system hangs.
7) I reset the machine and remove the HD Homerun. I add my pcHDTV PC-3000.
8) Scan for channels
9) Test LIRC by running the channelchange.sh script to confirm it is working,it was and blasted without issue.
10) Setup a manual recording for 5 mins on the PC-3000
11) While it was recording I ran the changechannel.sh script and BOOM entire system hangs.
So even with a clean install it is happening.
In the script you posted in
In the script you posted in the other thread:
#!/bin/bash
PATH=/bin:/usr/bin:/usr/sbin
REMOTE=dish
irsend --device=/dev/lircd1 SEND_START $REMOTE SELECT
sleep 4.0
for digit in `echo $1 | sed 's/\(.\)/\1 \n/g'` ; do
irsend --device=/dev/lircd1 SEND_START $REMOTE $digit
sleep 0.2
done
irsend --device=/dev/lircd1 SEND_START $REMOTE SELECT
sleep 0.2
irsend --device=/dev/lircd1 SEND_START $REMOTE CANCEL
sleep 3.0
You're calling irsend SEND_START - I've never used that but according to the docs, http://www.lirc.org/html/irsend.html that sends a repeating code which doesn't stop until you irsend SEND_STOP. I think you should be using SEND_ONCE.
Yes, I changed that because
Yes, I changed that because of some reliability issues with blasting and solve a different issue.
But that is really a moot point since I am using the default blasting script on the clean install which uses SEND_ONCE and it still happens...:(
damn, thought was it...
damn, thought was it... :(
Can you change your serial IO port / IRQ in the BIOS? Or if it's an add-in serial card, can you move it to a different PCI slot?
If not, I'm fresh out of ideas, sorry.
I am almost 100% that this
I am almost 100% that this problem is hardware based now. I returned my dedicated backend to the way it has been for months and was in working condition for a long time. I had been using this serial port and blaster for a few months before this problem came up. After returning the system to how it had been (without the HDPVR hooked up) I again reinstalled to experience the same issue. That takes the HDPVR out of the picture as the problem.
The serial port I am using was just pin outs on the MOBO, which is common since most MOBOs don't actually have the serial ports on them anymore. So I am using an add on which is a cable that plugs into the pins and gives me a port on the back of the CPU. I changed the IRQ of the serial connection, same issue
I even have a different serial blaster from irblaster.info that I tried, same issue.
Perhaps the serial port/cable/pin out on the mobo has an issue.
I am going to have the wife get a PCI card that I pop in the machine to see if that resolves the problem.
so while I was waiting for
so while I was waiting for the wife to come home, I grabbed another PC and installed/setup a backend just like I configure my real backend.
I used the same serial blaster, install media, and test recorded from the same HD Homerun.
Get this...it worked just fine. I blasted like crazy as it was recording from the HDHR, and nothing failed.
This other box is a P4 3.0 so it might work as a backend only. But it is only single core, I would much rather use the dual core AMD in the box that ISN'T working. All of encoders are hardware encoders so it might work.
Oh well, wife should be home soon with some new parts.
ok, so after spending hours
ok, so after spending hours on this last night with NO positive results.
Today I changed out EVERYTHING. New Mobo (with a serial port on the back panel, not just pins on the MOBO), Processor, Ram, power supply, serial blaster.
Guess what? SAME RESULT, I can cause it to hang anytime.
The ONLY thing I can think of is that both MOBOs I tried are ASUS. My original Mobo and my test Mobo are MSI.
I wonder if it is a chipset that something doesn't like.
The new MOBO I got today is the ASUS M4A77D.
http://www.asus.com/product.aspx?P_ID=gVPip6NkD93nzINC&templete=2
I literally am at my wits end...
So the fix was moving to a
So the fix was moving to a USB blaster.
A buddy runs Media Center so he ran a USB blaster by. Just with a few changes, it is up and running without issue.
New hardware didn't do it, I guess it is software.
I guess it has something to do with lirc_serial.
Time to restore by DB and copy back over the data.