I converted from R5E50 to R5F1 a few days ago. Everything looks great and all, but I have a bit of trouble with my serial port IR receiver. I find it takes a several tries to get to navigate menus and such, but only when recording a program. I ran irw, and it only sees maybe one in five keys. Using the keyboard, responses on the frontend are instantaneous.

The system is not overburdened by any means. Mythbackend is using 2-5% to record one program right now from a PVR500. The frontend is using about 12-18% to play a SD stream. I do not have commercial flagging going until later in the night. I did comment out the serial mouse section in xorg.conf, and that didn't seem to bring any improvement.

Once the recordings finish, everything is completely responsive again. I'm just having trouble thinking where to go to debug this further...

I am experiencing the same issue on a serial receiver.

I have been wondering if there is some way to perhaps increase the "priority" of lirc or make it run with root permissions.

Any help is appreciated

I'm having the same issue with lirc. I thought the batteries must have been dying in my remote. I replaced the batteries and it didn't fix anything. Has anyone found a reason for the problem, and/or a solution? We might get a better response if repost this to the "General" forum.

-Jeremy

I think I solved the problem. I was using the lircd.conf and lircrc from my old backup. I ran the script lirc-reconfig.sh and it gave me new lircd.conf and lircrc. after a reboot, it seems to be working correctly now.

The old lircd.conf from my back up was similar but slightly different than the new lircd.conf that the script created. I had customized my lircrc to give me more xine options so I will have to redo that.

Anyway, if it stops working again tomorrow, I'll write back.

-Jeremy

Woke up and tried the remote control this morning and its back to its old shenanigans. The remote works only every 10th press or so. sometimes longer, sometimes shorter. This is really annoying. Anyone have some troubleshooting suggestions?

I've got a haupauge pvr-250 with the remote sensor plugged into the back.
A415-HPG remote control
Using the default lircd.conf and lircrc for this remote
the irw command shows the same consistency (or should I say inconsistency) which means that the button press only registers some of the time.

I have a universal remote that has been programmed to match the A415-HPG and it has the same issue so I'm pretty sure its not a problem with the remote. someone please help.

Jeremy

Jeremy, does yours do this all the time? On my system, it is completely responsive, never misses a key, when the backend is not doing any recording.

Check the hints thread. You may be having the same ir keyboard related problem as people using the Hauppauge receiver...

Renaming that module didn't help my situation any. I checked all the old /var/log/messages, and didn't have that specific error in there.

Back to the drawing board...

tjc: thanks for your help. Your suggestion led me to the right post to get my problem fixed. I followed the advice I found in:
"LIRC conflicts -- Hauppauge remote dead"
(http://mysettopbox.tv/phpBB2/viewtopic.php?t=15219)

and it worked.

cjd1: My problem was intermittent. I tested it during recording and non-recording status and couldn't find a correlation. I was getting the error messages in /var/log/messages which is described in the thread I just linked to.

It sounds like your problem is slightly different than mine, or rather, it sounds like we have the same symptom, but with a different cause. Your problem is clearly linked with the backend recording status. I would try to determine what changes are happening when the backend starts recording. Do any new kernel modules get loaded?

When was the last time you powered down your system and let it sit for a few minutes before starting it back up. I've heard that this will force the firmware of your tuner card to be reloaded.

I hope that helps
-Jeremy

Well, I caught the notice of the next version of ivtv, so I figured, why not?

After installing that, and firing up some recordings, all is well with the remote. Right now I'm recording with both PVR500 tuners and an Air2PC, and threw in some commercial flagging for those, and the remote is working great again.