Llevo arrastrando un error en mi configuración de LIRC desde hace mucho tiempo. Sin ponerme a buscar el origen lo achacaba a un fallo del propio núcleo del sistema GNU al mapear los dispositivos input layer.

Leyendo la documentación de LIRC -cosa que debería hacer siempre- he encontrado la parte dedicada a Linux input layer driver. Se dice en él:

Sometimes the input device mapping changes between system reboots. In that case you are also able to specify the correct input device by its name or physical location [...]

Al parecer es un comportamiento normal que en cada reinicio no se asegure siempre que un dispositivo se le asigne el mismo número en /dev/input/event. En mi caso el mando a distancia suele asignarse el número 5 ó 6. A veces, al iniciar de nuevo el sistema, se daba que LIRC bloqueaba el ratón. Cambiar el archivo /etc/lirc/hardware.conf y reiniciar el servicio lirc cada vez que ocurría era, como mínimo, muy molesto.

La solución pasa por indicar el valor Phys de proporciona /proc/bus/input/devices en cada dispositivo. A continuación la salida de cat /proc/bus/input/devices:

I: Bus=0011 Vendor=0002 Product=0004 Version=0000
N: Name=”GenPS/2 Genius Mouse“
P: Phys=isa0060/serio1/input0
S: Sysfs=/devices/platform/i8042/serio1/input/input5
[...]

I: Bus=0001 Vendor=1461 Product=2c05 Version=0001
N: Name=”saa7134 IR (AverTV DVB-T 777)“
P: Phys=pci-0000:03:01.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:1e.0/0000:03:01.0/input/input6
[...]

Como resultado REMOTE_DEVICE de /etc/lirc/hardware.conf queda con el siguiente valor:

REMOTE_DEVICE=phys=’pci*/ir0‘

El asterisco (*) es un comodín.

LIRC-LINUX INFRARED REMOTE CONTROL

LIRC is a package that allows you to decode and send infra-red signals of many (but not all) commonly used remote controls.

The most important part of LIRC is the lircd daemon that will decode IR signals received by the device drivers and provide the information on a socket. It will also accept commands for IR signals to be sent if the hardware supports this. The second daemon program called lircmd will connect to lircd and translate the decoded IR signals to mouse movements.

Sending infrared signals

SOFTWARE: LIRC lirc-0.8.5.tar.bz2, 700 kB

LIRC is a package that supports receiving and sending IR signals of the most common IR remote controls. A list of supported hardware is available on the main page. It contains a daemon that decodes and sends IR signals, a mouse daemon that translates IR signals to mouse movements and a couple of user programs that allow to control your computer with a remote control.
For Irman support download the latest libirman library. If you want to link the LIRC drivers statically to your kernel, have a look at Karsten Scheibler's static LIRC package. 

In our college our department has an expo based on LINUX .In that our team had selected to do LIRC.

You may ask what is LIRC?

To know in detail about lirc refer the site “www.lirc.org”

I searched how to do this project in linux.In that i had seen a website “lnx manoweb.com”.

In that they given how to do an lirc receiver.The components neede are

1. TSOP 1738 Irreceiver

2. C1 – 4.7µF capacitor
3. D1 – 1N4148 diode
4. R1 – 4k7 resistor (4.7 kOhm)
5. IC2 – 78L05, 100mA, voltage regulator (TO-92 casing)
6. 9-pin or 25-pin SUB-D socket

The circuit is connected as in “manoweb.com” and we get the LIRC Receiver.

Connect to the serial port of the system and do the following

1. Download pacakage of lirc(lirc-0.8.5.tar.bz2)

extract it as “tar jxvf lirc-0.8.5.tar.bz2”

After this all the command are done in terminal of linux. We had downloaded lirc package in desktop.

In terminal we do the following

1. cd Desktop

2. cd lirc-0.8.5

3. ./setup.sh

setup.sh written by Karsten Scheibler, 1999-JUN-28

If you have problems or questions please consult the mailing list

<http://lists.sourceforge.net/mailman/listinfo/lirc-list>

Configuration: .setup.config, executable shell script: configure.sh

Starting the generated shell script which will call configure with the right

parameters…

checking for a BSD-compatible install… /usr/bin/install -c

checking whether build environment is sane… yes

checking for gawk… no

checking for mawk… mawk

checking whether make sets $(MAKE)… yes

checking for gcc… gcc

checking for C compiler default output file name… a.out

checking whether the C compiler works… yes

checking whether we are cross compiling… no

checking for suffix of executables…

checking for suffix of object files… o

checking whether we are using the GNU C compiler… yes

checking whether gcc accepts -g… yes

checking for gcc option to accept ISO C89… none needed

checking for style of include used by make… GNU

checking dependency style of gcc… gcc3

checking whether gcc and cc understand -c and -o together… yes

checking for a BSD-compatible install… /usr/bin/install -c

checking whether make sets $(MAKE)… (cached) yes

checking for mknod… /bin/mknod

checking for mkfifo… /usr/bin/mkfifo

checking for depmod… /sbin/depmod

checking for libusb-config… no

checking whether ln -s works… yes

checking build system type… i686-pc-linux-gnu

checking host system type… i686-pc-linux-gnu

checking for a sed that does not truncate output… /bin/sed

checking for grep that handles long lines and -e… /bin/grep

checking for egrep… /bin/grep -E

checking for ld used by gcc… /usr/bin/ld

checking if the linker (/usr/bin/ld) is GNU ld… yes

checking for /usr/bin/ld option to reload object files… -r

checking for BSD-compatible nm… /usr/bin/nm -B

checking how to recognise dependent libraries… pass_all

.

.

.

.

.

Now enter ‘make’ and ‘make install’ to compile and install the package.

kamban@kamban-desktop:~/Desktop/lirc-0.8.5$

4.sudo make

5.sudo make install

Afer this it is necessary to connect lirc receiver in the system

6.sudo setserial /dev/ttyS0 uart none

7.sudo depmod -a

8.sudo modprobe lirc_serial

9.sudo lircd

After this some time we get the error

lircd: there seems to already be a lircd process with pid 12653

lircd: otherwise delete stale lockfile /var/run/lircd.pid

10.sudo rm/var/run/lircd.pid

then give

sudo lircd

12.sudo mode2

mode2:could not open /dev/lirc

mode2: default_init(): Device or resource busy

to remove this we give this command

13.sudo rm/dev/lirc

then give the command

sudo mode2

after this we get the pulse

pulse 100

space 123

.

.

.

.

.

.

.

.

to quit from this ctrl c

then record it using

14. sudo irrecord /etc/lircd.conf

if any error appears then record it by

15.sudo irrecord -f /etc/lircd.conf

we can record it with our own name to the button by disabling the default button.

16. sudo irrecord /etc/lircd.conf –disable namespace

now record the signal for each button by holding the button.

After this we give restart the lircd then

17.sudo irw

it will test our remote

The connection of our system with remote had been done succesfully if upto this step is done .

If you have doubt inthe above description please refer “lnx.manoweb.com”

In our project we did how to connect an mplayer with the remote and we done it by downloading

Mplayer-mingw.zip

installing it by refer the procedure

In terminal we give

cd which come out from desktop

1. $ mplayer

2.$  mplayer -lircconf saranya.conf

3.$ sudo mplayer -lircconf saranya.conf *.mp3

Hi……. friends….

LIRC is a Linux Infrared Remote Control and the complete details about the documentation, software usage, software downloads all are given in detail in following link.

http://www.lirc.org/arahtml/index.html

See to this link for LIRC components required and for the connections

The most important part of LIRC is the lircd daemon that will decode IR signals received by the device drivers and provide the information on a socket. It will also accept commands for IR signals to be sent if the hardware supports this. The second daemon program called lircmd will connect to lircd and translate the decoded IR signals to mouse movements.

The LIRC package contains the irsend tool for sending infrared signals to e.g. your TV or CD player. For reliable transmission a good config file is even more important than for receiving

SOFTWARE:

LIRC lirc-0.8.5.tar.bz2, 700 kB

LIRC is a package that supports receiving and sending IR signals of the most common IR remote controls. A list of supported hardware is available on the main page. It contains a daemon that decodes and sends IR signals, a mouse daemon that translates IR signals to mouse movements and a couple of user programs that allow to control your computer with a remote control.
For Irman support download the latest libirman library. If you want to link the LIRC drivers statically to your kernel, have a look at Karsten Scheibler’s static LIRC package.

http://www.linuxjournal.com/article/8811

(refer this above website for reference)

http://lnx.manoweb.com/lirc/?partType=section&partName=introduction

(refer above for how to build serial receiver)

Introduzione

In questa terza parte della guida spieghero’ come installare e configurare il telecomando MCE versione 2 che ho trovato insieme alla scheda TV (Hauppauge PVR-500).

Per questa guida ho utilizzato e ‘mixato‘ alcune informazioni trovate su:

• La mia vecchia guida MythTV su Ubuntu – Parte 4

Parte 3: Argomenti trattati

• 3.1: Installazione Lirc
• 3.2: Test telecomando
• 3.3: Copia del ‘Key mapping’ nella cartella home
• 3.4: Fine installazione

3.1: Installazione Lirc

Prima di tutto ho installato Lirc, il programma che permette al PC di ricevere ed inviare i segnali infrarossi di moltissimi telecomandi:

sudo apt-get install lirc lirc-modules-source setserial

Rispetto a due anni fa ora l’installazione del telecomando e’ semplicissima, gia’ in questa fase viene richiesto di scegliere quale telecomando si sta installando. Nel mio caso ho selezionato ‘Windows Media Center Remotes (new version Philips et al.)’:

Successivamente viene richiesto se si vuole configurare anche un trasmettitore IR, che io non utilizzo, ho quindi selezionato la voce ‘None’.

Al termine dell’installazione e configurazione il sistema indica che ha correttamente avviato il demone di Lirc:

3.2: Test telecomando

Con IRW e’ possibile testare se tutti i pulsanti del proprio telecomando sono stati correttamente configurati:

irw

Premendo alcuni tasti sul telecomando vengono visualizzati sullo schermo i relativi codici riconosciuti da Lirc:

3.3: Copia del ‘Key mapping’ nella cartella home

Con questo ulteriore comando viene scaricato il file ‘lircrc’:

wget http://www.farrebyc.com/files/guide/mediacenter-su-ubuntu/9.04/p3/.lircrc cp .lircrc ~/.lircrc

Infine ho creato un link simbolico per permettere a Mythtv di utilizzare il file appena scaricato:

ln -s ~/.lircrc ~/.mythtv/lircrc

Nota: questo e’ il file di configurazione di Lirc che mi ‘porto dietro’ da ormai molto tempo, oltre a quella per MythTV contiene anche le mappature dei tasti per Mplayer, Xine, VLC, Totem ed Elisa.

3.4: Fine installazione

A questo punto il telecomando è stato installato e configurato correttamente, ed è ora pronto per essere utilizzato.

Guida – Media Center con Ubuntu

Parte 1 — Parte 2 — Parte 3 — Parte 4

In case you’ve been wondering, and I know you are all very concerned about this; CommandIR shipped me a replacement module which has solved my issues. It was simple to plug it in and have it work with Jaunty. They have great install instructions on their site as well. Thanks CommandIR!

Do you collect miscellaneous computer parts? Sometimes they actually come in handy! I found a HP eHome transceiver in my bin and hooked it up to the server and I now have 2 set top boxes firing again. It relieves some of the familial pressure, but I need to get all four set top boxes in rotation. Fortunately most of the recorded programming is OTA high definition, though.

I did receive a response back from CommandIR this morning, and I responded with an invitation to work together over the phone, irc, instant messaging, chat and any other form of real time communication I could think of. Let’s see if they respond favorably.

I need to start documenting more about some of the issues that I have while setting up my MythTV box.  I spend so much time searching for solutions and when I finally find it forget to record it.

I had ben trying to get my IguanaWorks USB IR Blaster working but not having much success.  As it turned out the biggest problem I had was a error in the configuration of my /etc/licr/hardware.conf file.  In the instarctions from Iguanaworks it called for placing:

After several e-mails with support at Iguanawors I finally got the driver installed, and this time with all the other drivers still available.  Big thanks go out to Ben at Iguanaworks for his helping work this one out.  In the end he managed to build a Debian package that prompted you for the selection of the driver.  The interesting thing that I noticed though was that it did not work at first.  That is to say that when I already had the IguanaIR driver installed and then installed the LIRC package.  What I had to do was completely remove LIRC and the IguanaIR driver, reboot (to be safe), install the LIRC package and then the IguanaIR package.  Now everything works.

A couple days ago, (at least 100 years ago) i managed to break the ir receiver’s connector to my Hauppauge PVR-150 leading to Epic FAIL. I had the device and the remote working perfectly with lirc using the hauppauge driver that comes with lirc. Being the lazy person that i am, i’m very irritated in having to get up and walk to the keyboard near the TV to change channels or volume (or anything else) with MythTV.

Just when all seemed lost, i remembered that the pcHDTV card that i have also has an IR receiver. I remembered that when i purchased the card, this feature was unsupported, but i assumed being several years later that developers would be all over that. I was wrong. It seems like it can be done, but it’s certainly not a self-explanatory process. Hopefully my journey will be useful to others:

First off, all i really had to go on was this newsgroup thread from 2006: pcHDTV – Infrared Chip. It looks like very little to no work has been done in this area (which seems typical of the pcHDTV team).

The first thing that must be done is to modify the kernel source slightly:

if you look at the cx88-input.c file in ./linux-2.6.X-whatever/drivers/media/video/cx88 in the kernel sources, you can see two places where there’s a line:

case CX88_BOARD_HAUPPAUGE_HVR1100:

In both places add the following line directly under the previous:
case CX88_BOARD_PCHDTV_HD5500:

now recompile:
make clean
make modules

I’ll let you decide how you want to get the new cx8800.ko and cx88xx.ko files into the tree. (I did it the “bad” way, but technically you should completely regenerate the kernel and module tree.) Whatever you do, don’t forget:

depmod -a

I’m using Gentoo, so my instructions from this point are specific to this distribution. If you’re using a different distro, your mileage may very. Next edit: /etc/make.conf add the line (or change the existing line) to be:

LIRC_DEVICES="devinput"

Now (as root, of course) recompile lirc.
emerge -v lirc

Here’s where it starts to get a little dodgy: You need to edit the keyboard entry in /etc/X11/xorg.conf add the lines:


Option "Dev Phys" "isa0060/serio0/input0"
Option "CoreKeyboard"
Option "Protocol" "evdev"


into Section "InputDevice"

The reason for doing this is because X11 will detect the input device that will be created (/class/input/input5 your input# may be different) as being a keyboard. The arrow keys and the enter key will work, but none of the other keys on the remote. To have lirc working properly, we don’t want X using the remote as a keyboard as well. The above lines explicitly specify the keyboard by bus ID. You can check which device your keyboard is be running:
cat /proc/bus/input/devices

At this point, reboot your machine. This will allow the newly created cx88 and lirc kernel modules to be loaded.

This is where i currently am. I’ll be updating this as i proceed in the debugging process

~~~-edits: 4:08PM CST 1/3/09

Okay 180 degree turn in strategy here. It appears that the kbd driver is somehow being assigned to the ir device. It seems when most other people have this problem it’s the Hardware Abstraction Layer of Linux, but i don’t have HAL installed, so it must be something similar, but not quite the same. Current suspect is udev. It appears that it has all to do with lircd being able to “lock” the input. Clearly this isn’t happening. It seems like all the codes in /etc/lircd.conf may need to change because of the different input interface. Also the way the kernel module works it assigned keycode to most of the bottens on the remote anyway.

It just so happens there’s another very small, simple program called inputlirc It’s very simple, but it interfaces with all the apps that lircd does, but take only one configuration file (since the buttons are already assigned codes, there’s not need for two set of files).

The program can be compiled easily by checking it out of subversion:

svn co http://svn.sliepen.eu.org/inputlirc/trunk/
cd trunk
make


The program created is the entire inputlirc system. Further updates (and the .lircrc file) i end up using once i’m done.

Web pages with useful or related information:

http://www.pchdtv.com/forum/viewtopic.php?t=1529
http://www.mythtv.org/wiki/index.php/LIRC
http://ubuntuforums.org/showthread.php?t=985311
http://parker1.co.uk/mythtv_tips.php
http://ubuntuforums.org/showthread.php?t=678835

Hi there blogosphere, I am sorry I haven’t posted in a while. Things have, as of late, been running really well with SageTV but there’s been quite a few changes.

SageTV is in RC stages of its 6.5 version of the product. The biggest change for this version is the addition of their new HD-200 product support. This device is capable of playing back internet, local network, and SageTV fed content at resolutions of up to 1080p via component or HDMI. The internet and local aspects do not require the use of SageTV’s server component. I’ll go into more detail in a separate post. My home setup now has 6 HD extenders for watching TV. I recently removed my last PC being used for playback.

Aside from firmware issues which plague Windows users as well, my HDPVR has been running well in Linux. This device allows you to capture TV from component outputs up to 1080i on your cable or sat provider set top box. There are a few minor things to tweak when building the drivers. I will go into more detail, you guessed it, in a separate post.

HVR-1600 drivers have never been better! I use 3 of these PCI cards to capture OTA HD signals and standard definition cable box channels. I’ll cover recent changes in a separate post shortly. If you have this card, you’ll want to do a pull from v4l-dvb’s mercurial!

Lastly, in the next few days I will be setting up a method to automatically convert my favorite TV shows to iPod Touch format and mark chapters at commercial break points. The TV shows will be downloaded into iTunes via an RSS feed from a server on my local network. I’ll document the process and provide the scripts make this work.

Thanks for reading!

B

I read on HackADay that u cud make a usb-ir input device, that cud register the input from an ordinary remote, for a tv/hif device.

I then found, a guide to making a an ir receiver, for use via serial pin-9 ( COM ) port. Much simpler and cheaper, not even a micro controller needed

Then i realised, after buing the parts, that i didn’t have a com port on the back of my pc, but that i did have an internal connector ( phew !).

Here is the deal:

Capacitor, resistor, diode, ir modulator, voltage regulator…. ( the diagram is wrong, by the way, for these component, and the capacitor is missing… Had to read allot of data sheets to do it with what components i cud get! ) 

Found this cable, that i never used. Its not the right one for the COMA connector, but tuned it “upside down”, and connected it “to the side” of the pins, and it would do the job

This is my make-shift soldering platform. A piece of wood, with some rubber bands..  :D

Here it is, danling outside my pc case… testing to see if it works at all….

Connected inside….

After installing WinLirc, and seeing the COM1 port was workin’, in tried sending some signals with my trusty samsung remote….

Wuhuu! we get signal!!!!! Ie, its working!!!

Then i found a nice application, “UIce”, that could register the remte, and assign events to the keystrokes all in one. Then i assigned the “up”, “down”, “right”, “left” and “ok” buttons to the corrosponsing mouse events, on the pc…. now i can move around my cursor with my samsung remote…

I will make a nice mount for the reciever one of the next days  

I chose to install Knoppmyth (R5.5) since it’s Debian based and it’s somewhat familiar to me from having messed around with it three years ago.  There’s also a good community forum built around Knoppmyth for support.  Mythbuntu also looks nice and I will probably try it out later when I have more time to see how each distro compares with one another.

Installation on the new system was a breeze but I did run into some minor snags.  The installation was done with the HTPC connected to my Westinghouse 22″ LCD, and subsequent tweaks are being done via VNC on my Window’s box.  Once I feel comfortable with the install, I will reconfigure xorg.conf to play nice with my Sony KDS-55A2000 HDTV @1080p.

A nice feature of the Knoppmyth installer is the remote control script.  During installation, I was prompted to select a remote control to use with Myth, and I choose the Imon-Pad option to match the Moneual’s Imon pad remote.  Without any issues, I was able to use my remote immediately without hassling with recompiling LIRC or config files – nice!

Soundgraph Imon VFD
The VFD wasn’t working out of the box.  A few minutes on the Knoppmyth forum yielded a quick solution.  As root, running this script brought the VFD to life:

/usr/local/bin/vfd_install.sh

When prompted to configure, hit “y”.  A reboot was then required before the VFD would activate.  Note: the large clock mode isn’t compatible with my VFD’s two line display so I had to disable this option under the Appearance > LCD settings within MythTV.

EDIT: The VFD install script has broken the pad function on the Imon remote.  All other buttons function normally, however the pad is no longer responsive.  The “pad” on this remote provides up, down, left and right navigation and is essential for myth menu navigation.  After spending several hours trying to resolve this, I gave up and mapped some other buttons to perform the same function by editing:

/home/mythtv/.lircrc

DVD Playback
DVD’s aren’t working out of the box with my system either.  Xine throws this error at me when trying to play a DVD (both unencrypted and encrypted):

Per Myth’s general settings, the DVD device is set to /dev/dvd which didn’t exist on my system:

Creating a symbolic link fixed the problem allowing me to view a DVD when inserted in the drive:

ln -s /dev/scd0 /dev/dvd

with “scd0″ being my optical drive and “/dev/dvd” the location of the DVD device as defined in Myth’s general settings.  However, when rebooting the machine, the symbolic link is lost every time.  I fixed this by modifying (as root):

/etc/udev/rules.d/z25_persistent-cd.rules

The lines that contained the string “SYMLINK+=”cdrom1″  were changed to “SYMLINK+=”cdrom”, and similiarly for SYMLINK+=”cdrw1″, SYMLINK+=”dvd1″, and SYMLINK+=”dvdrw1″ – the “1″ had to be dropped from each instance.

EDIT: After writing the above, and after a fresh “re-install” (long story), the DVD issue did not manifest itself and the DVD functionality works as expected the second time around.  I have no explanation for the DVD problem on the initial install…

Fix Myth Gallery mount failure messages

When myth starts, I was greeted with the following each time:

“Failed to mount device /dev/sde, showing default myth gallery directory”

This is probably caused by myth trying to mount the empty slots of the USB card reader.  For the meantime, I disabled them by adding the following to the “Ignore Devices” list:

/dev/sdb,/dev/sdc,/dev/sdd,/dev/sde

Make Samba autostart on reboot so I can copy files to the HTPC at anytime from a Window’s box.  From a terminal as root:

update-rc.d samba defaults

Connecting from Window’s, the default username and password are both mythtv 

X11VNC  - get it working correctly with Nvidia and install TightVNC on my Window’s box.  I’m using VNC on my Window’s box to control the Myth frontend while I setup and tweak things.  Remember, I don’t have xorg.conf configured yet to communicate with my HDTV, and I don’t have a spare monitor sitting around to use to connect to the HTPC.  The HTPC at this point is a headless box – meaning it does not have a monitor, keyboard, or other peripherals connected to it at this point.  VNC is not practical for video streaming but well suited to navigate the myth frontend menus. There are issues with nvidia, so first edit:

/home/mythtv/.fluxbox

uncomment and alter the following line (change is in red):

[startup] {/usr/bin/x11vnc -nap -wait 50 -noxdamage -passwd fubar -display :0 -forever -o /var/log/x11vnc.log -bg}

Next, turn off OpenGL flipping by right clicking on the Fluxbox desktop & Apps > Tools > nvidia-settings to bring up the settings panel.  Uncheck “Allow Flipping”:

Results: Remote access to the new headless HTPC from Windows:

different subject same story, there are no exact instructions on how to make the volume knob work with lirc, so i will do a quick howto on that too.

for me there was nothing special about getting the knob to work.
i just installed lirc as described in the post below, after that i played around with irrecord and that’s it.
(fyi: irrecord creates a [remote] section for the lirc config)
if you want to do this yourself use this command:
#irrecord -d=/dev/lirc
follow the instructions.

if you are lazy you could use my config:
begin remote
name ClickWheel
bits 16
eps 30
aeps 100
one 0 0
zero 0 0
post_data_bits 16
post_data 0x0
gap 131995
toggle_bit_mask 0x30000
begin codes
VolUp 0x0001
VolDown 0x0100
end codes
end remote


simple as that.

i did not come around to setup the ir reciever since i bought the wrong remote….
i read that the version2 of the microsoft mce remote should work, so i bought a fake one at amazon.
but unfortunately it is not a microsoft mce remote clone, it acutally is mce compatible but only if you use the receiver shipped with the remote.
it is labeled “ar remote mce” on the back and says “X10 Remote”.
so i figure it will work with the atiusb module if you use the reciever shipped with the remote.
but it won’t work with the imon receiver since the imon uses IR and the X10 uses RF.
that’s not a big problem since i will use the X10 one for my other frontend (see the epia c3 project)

i am searching another remote right now, i have read that the xbox360 universal remote should work, i also found an original microsoft mce remote.
but these are priced at around 30€ so i will do a lil research before spending another 30 for a remote that may not work with imon…

since there are no exact instructions on how to get the vfd to work with LCDd/lirc i will write a quick HowTo.

if you know the thread on codeka.com about how to get it to work it might be helpful, but the instructions there are not all you need to know.

first you need lirc and LCDd.
use these vars in your make.conf:
LCD_DEVICES="imon"
LIRC_DEVICES="imon imon_knob imon_lcd imon_pad"

add this line to your /etc/portage/package.use file
app-misc/lcdproc lirc usb

now just emerge lirc and lcdproc.

let’s see if there is an usb device we can use:
#lsusb
Bus 002 Device 002: ID 15c2:ffdc SoundGraph Inc. iMON PAD Remote Controller
Bus 002 Device 001: ID 1d6b:0001
Bus 001 Device 001: ID 1d6b:0002

if you got the ffdc model, than this instructions are for you, i read that some other models requiere patching, i don’t know what to do exactly because i got the ffdc model shipped with the newer fusion v2 cases.

now let’s see if the modules are already loaded:
#lsmod | grep lirc
lirc_imon 15372 0
lirc_dev 12904 1 lirc_imon
usbcore 148632 4 lirc_imon,ohci_hcd,ehci_hcd


remove the module:
rmmod lirc_imon

and modprobe it withe the important argument is_lcd=0
where 0 is the older vfd display (16×2 characters, negative blue backlight, appears to be off when no text is displayed)
1 is the newer lcd display.
if you do not supply is_lcd=0 it will simply not work.
#modprobe lirc_imon is_lcd=0

start LCDd and see if it succesfully created the device:
#/etc/init.d/LCDd start
#ls /dev/lcd*
/dev/lcd0
#ls /dev/lirc*
/dev/lirc /dev/lirc0 /dev/lircd


you are ready to go! (if there is no lircd device you may have to start lircd as well)
test the LCD:
#echo "TESTME" > /dev/lcd0

if the string appears on the display you got it right!

now what to do to make this permanent?

first add this to /etc/modprode.d/lirc
options lirc_imon is_lcd=0
add the lirc_imon module to /etc/modules.autoload.d/kernel-2.6

that’s it.

just for you to understand (i didn’t know this at first)
LCDd is the Server, it “wakes” the Display and takes connections from clients, these clients are telling LCDd what to do with the Display.
lcdproc is one of these clients for example, it will loop several info screens about the computer state.

And changes channels flawlessly! As I have mentioned earlier I originally had an IguanaIR device which was billed as 4 IR blasting capable ports. I could never get it to work with more than 2 devices and their support was terrible.

I purchased the CommandIR II, and installed it in an available USB header port on the motherboard. A pull from lirc cvs, a quick compile of the driver (make sure to choose CommandIR under USB devices) had me up and running in no time. I am still using a tuning plugin written by a fellow SageTVer, with a script I wrote to perform the channel changes. All is working great. –b

Bueno, acá nuevamente para Contarles Como Instalé Mi Placa Encore TV FM (ENLTV-FM) para ver la Tele en Ubuntu Hardy.

Quizá el Primer paso ha sido un error pues el chip saa7134 ya esta incluido aparentemente en hardy pero ya esta hecho.

En la consola hacer lo siguiente:

1) Instalar mercurial:

sudo apt-get install mercurial

2) Descargar el fuente del driver:

hg clone http://linuxtv.org/hg/v4l-dvb

3) Instalar el driver:

cd v4l-dvb
sudo make , o sudo make all
sudo make install

4) sudo gedit /etc/modprobe.d/alsa_base

Buscamos

# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 modprobe –ignore-install saa7134 $CMDLINE_OPTS && { modprobe -Qb saa7134-alsa ; : ; }

Le agregamos  la identifiacación de la Encore TV, para que cargue el driver correcto, quedando así:
# Load saa7134-alsa instead of saa7134 (which gets dragged in by it anyway)
install saa7134 modprobe –ignore-install saa7134 $CMDLINE_OPTS && { modprobe -Qb saa7134-alsa -card=3 tuner=69 ; : ; }

Tambien vamos a editar el Archivo Options de módulos:

sudo gedit /etc/modprobe.d/options

# opciones para tarjeta de captura de video con chip phillips
options saa7134 card=3 tuner=69 i2c_scan=1 ir_debug=1

Esto lo que hará es cargar la configuracion de la Encore Tv al iniciar Ubuntu.

Sigan leyendo más Abajo

Visto en Instalar Encore TV FM Tuner Pro (ENLTV) en Ubuntu 7.04 Feisty Fawn

Tenemos que hacer Funcionar

• la TV
• La Radio
• En Control Remoto

Para Las Dos primeras nos basta con un:

sudo aptitude install tvtime gnomeradio (o kradio en KDE)

Respecto a Gnomeradio, ya debería funcionar tomando desde /dev/radio0 el otigen.

Con tvtime, elegimos frecuencia personalizada y primero debemos escanear los parametros disponible.

En Argentina la Norma es PAL-Nc, si Tenemos cable elegimos directamente us-cable sino o argentina o personalizada

por ejemplo

tvtime-configure --norm=PAL-Nc --frequencies=us-cable

Luego para que deje de sonar el tvtime cuando se cierra:

sudo gedit ~/.tvtime/tvtime.xml

y agregamos

“option name=”MuteOnExit” value=”1″ “

Nuestro Item pendiente es el Remoto

Veo en  “http://lihuen.info.unlp.edu.ar/index.php/Configuraci%C3%B3n_de_placa_sintonizadora_de_tv_encore_enltv-fm_pci“

Debemos Instalar lirc

#sudo aptitude install lirc

luego

#sudo /etc/init.d/lirc stop

Si necesitamos Bajar y Volver a levantar saa7134 debemos

Ver si esta cargado

lsmod | grep saa

si algun modulo esta cargado entonces

sudo rmmod saa7134

ahora ejecutamos

sudo depmod -ae

volvemos a cargar el modulo

sudo modprobe saa7134 card=3 tuner=69 i2c_scan=1 ir_debug=1

recordar que si necesitamos probar otros valores Comentar lo que pusimos en Options o tomará esos valores al cargarlo

Vemos cual es nuestra Entrada de Control remoto

cat /proc/bus/input/devices

I: Bus=0001 Vendor=1a7f Product=2004 Version=0001
N: Name="saa7134 IR (Encore ENLTV-FM2)"
P: Phys=pci-0000:00:0a.0/ir0
S: Sysfs=/class/input/input2
H: Handlers=kbd event2
B: EV=100003
B: KEY=10a00800 0 0 0 0 0 8000 80 0 21680 0 0 10000ffe

ahora vamos a sacar la información del dispositivo en cuestión

udevinfo -a -p `udevinfo -q path -n /dev/input/event2`

  looking at device '/class/input/input2/event2':
    KERNEL=="event2"
    SUBSYSTEM=="input"
    DRIVER==""
    ATTR{dev}=="13:66"

  looking at parent device '/class/input/input2':
    KERNELS=="input2"
    SUBSYSTEMS=="input"
    DRIVERS==""
    ATTRS{modalias}=="input:b0001v1A7Fp2004e0001-e0,1,14,k71,A7,CF,18B,195,197,19C,ramlsfw"
    ATTRS{uniq}==""
    ATTRS{phys}=="pci-0000:00:0a.0/ir0"
    ATTRS{name}=="saa7134 IR _Encore ENLTV-FM2_" 

  looking at parent device '/devices/pci0000:00/0000:00:0a.0':
    KERNELS=="0000:00:0a.0"
    SUBSYSTEMS=="pci"
    DRIVERS=="saa7134"
    ATTRS{broken_parity_status}=="0"
    ATTRS{enable}=="1"
    ATTRS{modalias}=="pci:v00001131d00007130sv00001A7Fsd00002004bc04sc80i00"
    ATTRS{local_cpus}=="ff"
    ATTRS{irq}=="193"
    ATTRS{class}=="0x048000"
    ATTRS{subsystem_device}=="0x2004"
    ATTRS{subsystem_vendor}=="0x1a7f"
    ATTRS{device}=="0x7130"
    ATTRS{vendor}=="0x1131"

  looking at parent device '/devices/pci0000:00':
    KERNELS=="pci0000:00"
    SUBSYSTEMS==""
    DRIVERS==""

Probamos nuestro Control

tail -f /var/log/syslog

y apreten los botones del control remoto si aparecen secuencias distintas como:

Jul 26 21:53:27 localhost kernel: saa7130[0]/ir: build_key gpio=0x191149 mask=0x7f data=73
Jul 26 21:53:27 localhost kernel: saa7130[0]/ir: build_key gpio=0x511ff mask=0x7f data=127
Jul 26 21:53:29 localhost kernel: saa7130[0]/ir: build_key gpio=0x19114c mask=0x7f data=76

esta de maravillas, si no

Jul 26 21:53:27 localhost kernel: saa7130[0]/ir: build_key gpio=0x191149 mask=0x7f data=0
Jul 26 21:53:27 localhost kernel: saa7130[0]/ir: build_key gpio=0x511ff mask=0x7f data=0
Jul 26 21:53:29 localhost kernel: saa7130[0]/ir: build_key gpio=0x19114c mask=0x7f data=0

tienen un error, mi caso.

si no tienen el error continuamos

$irrecord -H dev/input -d /dev/input/event2 /tmp/lircd.conf

aparecera algo como esto

Please enter the name for the next button (press to finish recording)
nombreDelBoton
Now hold down button “nombreDelBoton”.
Please enter the name for the next button (press to finish recording)

bueno ahi aprentan los botones y listo.

una vez configurados los botones pasamos a copiar el archivo /tmp/lircd.conf al directorio correcto

cp /tmp/lircd.conf /etc/lirc/lircd.conf

bueno ahora configuramos el resto de los archivos

# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS="-d /dev/input/event2" 

#Don't start lircmd even if there seems to be a good config file
#START_LIRCMD=false

#Try to load appropriate kernel modules
LOAD_MODULES=true 

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="dev/input"
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
DEVICE="/dev/lirc"
MODULES="UNCONFIGURED"

# Default configuration files for your hardware if any
LIRCD_CONF="/etc/lirc/lircd.conf"
LIRCMD_CONF="UNCONFIGURED"

el remoto deberia quedar algo como esto

# Please make this file available to others
# by sending it to <lirc@bartelmus.de>
#
# this config file was automatically generated
# using lirc-0.8.0(userspace) on Sat Jul 26 20:18:40 2008
#
# contributed by
#
# brand:                       /tmp/lircd.conf
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote 

  name  /tmp/lircd.conf
  bits           32
  eps            30
  aeps          100

  one             0     0
  zero            0     0
  gap          147849
  toggle_bit      0 

      begin codes
          1                        0x80010002
          2                        0x80010003
          3                        0x80010004
          4                        0x80010005
          5                        0x80010006
          6                        0x80010007
          7                        0x80010008
          8                        0x80010009
          9                        0x8001000A
          0                        0x8001000B
      end codes 

end remote

bueno si quieren pueden poner mas botones aquí solo se agregan los números como ejemplo.

ahora si quieren pueden usar tvtime para ver la tv y gradio o kradio etc para la radio.

en el directorio home del usuario puede crear o se creara con las aplicaciones un archivo

.lircrc

pueden editarlo de la siguiente manera

begin
        remote = encore
        button = POWER
        prog   = irexec
        repeat = 0
        config = tvtime&
    end
begin
    prog   = tvtime
    button = 1
    config = keypad 1
end
begin
    prog   = tvtime
    button = 2
    config = keypad 2
end
begin
    prog   = tvtime
    button = 3
    config = keypad 3
end
begin
    prog   = tvtime
    button = 4
    config = keypad 4
end
begin
    prog   = tvtime
    button = 5
    config = keypad 5
end
begin
    prog   = tvtime
    button = 6
    config = keypad 6
end
begin
    prog   = tvtime
    button = 7
    config = keypad 7
end
begin
    prog   = tvtime
    button = 8
    config = keypad 8
end
begin
    prog   = tvtime
    button = 9
    config = keypad 9
end
begin
    prog   = tvtime
    button = 0
    config = keypad 0
end
begin
	prog   = kradio
	config = eventmap
    repeat = 1
 end

saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0

saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x0 mask=0x0 data=0
saa7133[0]/ir: build_key gpio=0x40 mask=0x0 data=0

Any help to resolve this will be aprecciated.

He avanzado bastante pero aún falta con este tema

After becoming very frustrated with the lack of support from IguanaWorks, I have decided to replace their device with the internal unit from CommandIR.

The Iguana device had been working great when I was running 2 tuners. After adding the 3rd tuner/DCT700 cable box to the mix, I could not get it to work. I opened a ticket with Iguana and I get the impression my issue is not high enough on their priority list to address. As a result I would NOT recommend this company to anyone to do business with.

Stay tuned for CommandIR feedback. I selected their new internal version and am looking forward to the install. I need to have all my tuners operational before the kickoff of the new TV season!

B

Hace un par de meses compré una Hauppauge WinTV-NOTA-T-Stick y me funciona a la perfección tras haber seguido las instrucciones de instalación de LinuxTV. Lo que nunca logré hacer funcionar fue el mando a distancia: miles de pruebas que nunca funcionaron acabaron por desquiciarme, san Google no me ayudó y acabé por pasar del mando… hasta ayer por la tarde. Volví a entrar en las instrucciones de LinuxTV y vi que habían añadido una sección para el mando a distancia, pero esas instrucciones no funcionaban pues explican la instalación para dos modelos de mando diferentes al que viene con mi stick, cuyo número de modelo es DSR-0112 (lo podéis ver en la parte trasera), de 35 teclas, gris por la parte delantera y negro por la trasera; lo podéis ver en la foto de la izquierda (clic en ella para verla a tamaño completo). Total, que pongo a funcionar LIRC, intento capturar las teclas de mi mando usando irrecord para generar mi lircd.conf y me da los siguientes errores siempre:

$ irrecord -H devinput -d /dev/input/by-path/pci-5-6–event-ir /tmp/lircd.conf
[...]
irrecord: gap not found, can't continue
irrecord: closing '/dev/input/by-path/pci-5-6–event-ir'


Estos errores son debidos a que las pulsaciones en el mando a distancia no son detectadas por LIRC pese a que el sistema sí reconoce un receptor de infrarrojos incrustado en el receptor TDT/DVB. Para hacer que el LIRC reconozca las pulsaciones desde el mando se debe aplicar un parche al driver de la Hauppauge; explicaré el procedimiento que seguí en mi Mandriva 2008.0 (para otras distribuciones el proceso será el mismo con algún comando cambiado, como por ejemplo urpmi). Así, abrimos una consola de root y seguimos estas instrucciones:

$ urpmi mercurial
$ hg clone http://linuxtv.org/hg/v4l-dvb
$ cd v4l-dvb/linux/drivers/media/dvb/dvb-usb/
$ wget http://cache.gmane.org/gmane/linux/drivers/dvb/42458-001.bin -O dib0700_devices_ir_DSR-0112.diff
$ patch –verbose –dry-run < dib0700_devices_ir_DSR-0112.diff
$ cd ../../../../..

Y luego ya seguimos con el procedimiento explicado en LinuxTV:

$ make && make install


Una vez hecho esto ya tenemos nuestro driver para la Hauppauge listo para funcionar y para reconocer las teclas pulsadas en el mando a distancia. Ahora reiniciamos el sistema (extrañamente hacer un reload de los módulos no me funcionó ) y lo que nos queda es configurar el mando a distancia; esto consiste en asignar al código enviado por cada tecla del mando un “nombre”. Esto se hace en el fichero lircd.conf y para configurarlo podemos hacerlo a mano (usando irrecord) o podemos usar un lircd.conf ya preparado para este mando. Para hacerlo de esta última manera abrimos otra consola como root y ejecutamos los siguientes comandos:

$ cd /etc/
$ wget http://cache.gmane.org//gmane/linux/drivers/dvb/42458-002.bin -O lircd.conf

Arrancamos el servicio LIRC:

$ service lircd restart
Deteniendo demonio de control remoto infrarrojo de Linux: [FALLÓ ]
Deteniendo demonio de Control Remoto Infrarrojo de Linux: [FALLÓ ]
Iniciando demonio de Control Remoto Infrarrojo de Linux: [ OK ]
Iniciando demonio del ratón para Control Remoto Infrarrojo de Li[ OK ]

Si todo va bien ahora deberían funcionar tanto el dispositivo de TDT como el mando a distancia. El primero lo podemos comprobar con el Kaffeine o mplayer por ejemplo y para probar el segundo ejecutamos el programa irw en una consola y pulsamos algunas teclas en el mando:

$ irw
0000000000010073 00 vol+ hauppauge
0000000000010073 00 vol+ hauppauge
000000000001008b 00 menu hauppauge
000000000001008b 00 menu hauppauge
000000000001009e 00 back hauppauge
000000000001009e 00 back hauppauge
00000000000100cf 00 play hauppauge
00000000000100cf 00 play hauppauge
0000000000010077 00 pause hauppauge
0000000000010077 00 pause hauppauge

Si os sale algo parecido a esto enhorabuena, ya podéis usar el mando a distancia de la Hauppauge WinTV-NOVA-T-Stick en vuestras aplicaciones favoritas. Únicamente tengo el problema de que el sistema reconoce cada pulsación como doble, de manera que si doy a la tecla bajar volumen me bajará “dos veces” de volumen, y si pulso la tecla 4 para ir al canal número 4 en realidad intenta ir al canal 44. Actualización: en los comentarios han pegado un parche que soluciona el problema de la doble pulsación.

Si usáis KDE os recomendaría echar un vistazo a IRKick (que básicamente es una manera de hacer más fácil la configuración de LIRC bajo KDE), que forma parte del paquete kdeutils-common. Quizás algún día escriba un post sobre IRKick, que éste ya es demasiado largo.

Fuentes:

• LinuxTV.org: instrucciones para instalar Hauppauge WinTV-NOVA-T-Stick
• LinuxTV.org: cómo instalar drivers de dispositivos DVB en Linux
• Lista de correo de linux-dvb