this worked great for me. PVR-150 R5A16.

BUT, i can't get it to control my digital cable box? anyone have the IRblaster part of this working???
thanks!
steve

Thanks for this, I used this to try to advance my problems
with the iMon remote and step 9 was the next thing I was
missing woohoo!

9.) Add the following line to the end of /etc/modules
Code: lirc_i2c
I modified mine as was indicated from my remote to:
lirc_imon

My question is, should I do somthing similar in steps
11 and 12? That is should I use, but modify those commands
in the same way?


11.) Make sure the following line appears in /etc/mythtv/modules/ivtv
Code:
alias char-major-61 lirc_i2c would becom\e
alias char-major-61 lirc_imon

12.) To test:
Code:
# rmmod lirc_i2c
# modprobe lirc_i2c
# lircd
# irw

Or put another way, I get the modules line. What does the 'alias' line do?
and the 'modprobe" line do?
Thanks in advance, videog

Thanks robert.pdx! Your tutorial worked perfect for the remote that came with my PVR-250. I am beyond happy!

Modprobe is a utility that loads a module into the kernel at runtime (instead have having to compile any necessary modules directly into the kernel).

The alias directive allows the kernel to address the module by a generic name. A lookup table of sorts, providing a uniform interface for the kernel. Char stands for character device. A character device (like a serial port) can talk using messages of variable size, where a block device (like a hard drive) talks in chunks of a fixed size. Your PVR card and associated IR receiver are character devices.

Every device in the system is going to have a number. If you look in /usr/src/linux/Documentation/devices.txt you can infer some information.

Notice that 81 is video4linux (aliased to ivtv if you're using a PVR 150/250/350 card). Notice too that device 61 which is tied into that IR receiver on your PVR card (char-major-61) falls in the "experimental use" category. Now you can tell your friends that you're both unstable AND experimental.

I don't know anything about the imon remote, so I can't help there.

HeyHey~

I'm also having issue getting lircd to work after a reboot.



If I ps -ae |grep lirc, I only get 'lirc_dev'.

Once I type /etc/init.d/lirc start - then I see lircd and lircmd. restart mythfrontend and the remote works great! (until the next time I boot)
Anyone get past this?TIA

I am currently trying to get the silver remote to work, but when I looked around there was a script called something like lirc-reconfgure.sh that autmatically unpacked sources and compiled and installed modules (and of course created devices) with a nice dialog interface.

Does that script do things wrong? Or am I just not the linux hardcore guy as all others?:-)

Anyway, my problem is that even if I kill lircd things happend when i press keys on the remote (the OK-button gives Enter, but for most other I get some Unknown key error). But I just read the tips to use the fuser command and I realised I probably have to edit the file under /home/mythtv too (I'll look at that when I get home from work).

A follow up on this (I'm at work now so I can't verify it). It seems as for the Nova-T the remote is handled by the evdev event handler, so when running lirc-reconfigure.sh I shall NOT chose the TV-card route but the Event-route. I'll try that when I get home!

(Because lircd won't start because it can not initialise the device. But that makes sense if evdev already uses the remote interface on the Nova-T)

Thanks for posting this how to... I have the remote up and running just fine now!

Does this howto work with R5A26 and Hauppauge WinTV PVR-350 silver remote?

If then, thanks for a great howto!

For R5A22 it was not necessary to follow this howto. All I did was choose the Hauppauge grey remote (yes, even though I have the new 350/silver remote) during installation and irw worked straight away after installation. The installed lircd.conf appears to have the codes for all three Hauppauge remotes in it. I DID have to edit the lircrc file for the key mappings though (I cut and pasted one from the forum here). Next step is to optimise the lircrc.conf so that all the buttons work. So I guess the same might apply to R5A26 as well.

BTW, quick gripe on the nomenclature - grey remote is 34 buttons (I think) and silver remote is 40+ buttons (as per pic at start of thread). Some people are confused about that

_________________
HP VL400 (PIII 866), Skystar2 2.6D, PVR350, Nvidia FX5200, 384MB, 200GB, KnoppMyth R5.5

Thanks nickread! Now it works with some buttons.

I have downloaded a spesific lircrc file for the pvr-350 remote, but only som buttons work in mythtv. What exactly do I have to do for mapping the buttons, or do you already have some lircrc and lircd.conf files you can share with me?

Many thanks!

As far as I know (and subject to correction by wiser folk) there are three places to configure a working remote:

lircd.conf
This maps the codes generated by the remote to lables reflecting the different keys. If you run irw from the command line, it will return the label for each key as you press it (exit with Ctrl-C). If you get a reasonably correct label (one or more times) each time you press a key, for every key then thats AOK and you don't need to mess with lircd.conf

Key mappings
This can be adjusted under the mythfrontend/setup or via mythweb. Basically this determines the KEYBOARD keys corresponding to the actions you want taken.

lircrc
This marries the key lables from lircd.conf with the keyboard key mappings from the mythtv setup. Each entry identifies a lirc aware application, a label from lircd.conf, and usually a keyboard key to map to (although you can do other stuff as well). This is the best place to optimise I think.

Having said all this I haven't got around to doing any changes yet, as my config works for the basic stuff. And if you do make changes, backup the original as its easy enough to mess it up

_________________
HP VL400 (PIII 866), Skystar2 2.6D, PVR350, Nvidia FX5200, 384MB, 200GB, KnoppMyth R5.5

I just upgraded from R5A16 to R5A26. I seem to have everything working except the remote. I have the Haupauge silver remote. I have been able to get it working in two previous installations without any problem. (Thanks, Knoppmyth.) Most recently, I used the directions at the top of this thread and got it installed under R5A16.

When I upgraded to R5A26, during the installation process, it asked me what remote and I think I selected hauppauge silver. It said it couldn't help me install it. So I again tried the instructions at the top of this thread. I cannot get any output from the remote. I tried the installation three times and I made sure that the receiver was plugged in. (the remote worked yesterday in R5A16.)

Here is where it seems to go off the track:

root@mythtv:/usr/src# rmmod lirc_i2c
ERROR: Module lirc_i2c does not exist in /proc/modules
root@mythtv:/usr/src# modprobe lirc_i2c
WARNING: Error inserting lirc_dev (/lib/modules/2.6.13.2-chw-3/misc/lirc_dev.ko): Unknown symbol in module, or unknown parameter (see dmesg)
FATAL: Error inserting lirc_i2c (/lib/modules/2.6.13.2-chw-3/misc/lirc_i2c.ko): Unknown symbol in module, or unknown parameter (see dmesg)
root@mythtv:/usr/src# lircd
root@mythtv:/usr/src# irw
root@mythtv:/usr/src#

Any ideas how to get me back on track??

Fixed it:

Reinstalled R5A26 fresh.
Selected "grey" instead of "silver" during install. (like nickread suggested above)
Edited lircd.conf (per nickread's suggestion above).
Copied an lircrc file for the silver remote that I found in the forum.
Restarted.

It works.

I tried that. The install gray, but it did not work for me. irw gives me no out put at all. I posted over in hardware but no luck yet.

_________________
R5F1 : AMD 64 2800 : Nvidia 5200 : 2x PVR- 150