Hi all,

Firstly, like so many other people I must point out that yes, I am fairly new to Linux.

Now that that's out the way, my first Linux project has been mythtv driven, and so far I feel I have done fairly well.

I have installed knoppmyth as my backend server, and am using xebian on my xbox for the frontend. I live in the UK and subscribe to Sky, and as such have an Amstrad DRX100 Sky digibox. I am now at the point where everything is working apart from LIRC (even though I did struggle with my TV card for some time). I have been trying to change the channel via IR, and have been following the instructions in the guide found here http://losdos.dyndns.org:8080/public/my ... _LIRC.html.

I noticed this forum is linked to in this guide, and that the author posts here and thought this would be the best place to post my question.

I have worked throughout the guide, and after a few tangents and minor tweaks, am now sending signals to my digibox. During the set up I chose to use the remote configuration file for the Sky navigator (asuming that this would effectively be an all-in-one type Sky remote).

The problem is that although my digibox is receiving commands, it is consistently only receiving every other command. for example if I send 123 the TV will display only 1 and 3, then if I send 123 again (even if i wait 10 min) it will receive only 2.

I have adjusted the timing in the change_chan.sh script gradually up to 2 seconds, with the same results, and I have also tried a stronger resistor in the ir blaster, this time same results with less range.

Is there anything I am missing that could explain this? I am also confident that my backend server is doing little else at the time.

Thank you for your time and help, and thank you to all the talented people who have contributed to myth tv and its associated bits and pieces, the guides, and everything that has made it possible for me to get this far.

You may have been bitten by the nasty lirc_serial SMP bug that's giving lots of us grief. Lirc is crashing constantly when sending serial commands because of it. Check dmesg or tail -f /var/log/messages and each time your box fails to send all the digits, watch what's happening. If the log is filling up with lirc_serial smp bug messages...well...there's nothing you can do but recompile the kernel without smp support. If not, don't know what your problem is.

I'll let you know in a few days if rebuilding the kernel without SMP support is a viable solution and I'll post a writeup.

Well, for some odd reason, despite the error messages, I can change channels just fine. I replaced my old crap DCT2244 box today with a shiny new DCT2524 and what a big difference it made.

My mythbox is still puking up errors in the syslog but it's still changing the channels like it should through my ir blaster. Who knew? I'm starting to wonder if the error is a problem at all..if folks just don't have their ir blasters configured properly.