Hello there, im sorry if this topic exists already but there are so many pages to read, my apologies for that. I have installed open suse 2 months ago, so if i will make some mistakes please correct me. I manage to configure kdetv and it works fine but my only issue is the remote control , when i activate lirc and make a test the remote is detected and almost all the buttons are recognized. When i try to use the remote to work on kdetv nothing happens . Can someone give me some hints or a tutorial in a way that i use the tuners remote to change the channels, not the keyboard as it happens now .
Here is a part of “dmesg”
Linux video capture interface: v2.00
ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) -> IRQ 16
PCI: Setting latency timer of device 0000:00:1b.0 to 64
cx88/0: cx2388x v4l2 driver version 0.0.6 loaded
ACPI: PCI Interrupt 0000:03:02.0[A] -> GSI 18 (level, low) -> IRQ 18
cx88[0]: subsystem: 107d:6611, board: Leadtek Winfast 2000XP Expert [card=5,autodetected]
cx88[0]: TV tuner type 44, Radio tuner type -1
cx88[0]: Test OK
tuner’ 1-0043: chip found @ 0x86 (cx88[0])
tda9887 1-0043: tda988[5/6/7] found
All bytes are equal. It is not a TEA5767
tuner’ 1-0060: chip found @ 0xc0 (cx88[0])
tuner-simple 1-0060: type set to 44 (Philips 4 in 1 (ATI TV Wonder Pro/Conexant))
cx88[0]: Leadtek Winfast 2000XP Expert config: tuner=38, eeprom[0]=0x01
input: cx88 IR (Leadtek Winfast 2000XP as /devices/pci0000:00/0000:00:1e.0/0000:03:02.0/input/input7
cx88[0]/0: found at 0000:03:02.0, rev: 5, irq: 18, latency: 96, mmio: 0xe3000000
cx88[0]/0: registered device video0 [v4l2]
cx88[0]/0: registered device vbi0
cx88[0]/0: registered device radio0
+1 on this appeal for help with Leadtek remotes.
OpenSuse 11.0, on an Athlon XP 2800+, a Leadtek Winfast 2000XP analog tuner + remote; and a Leadtek DTV1000-T Digital TV Tuner. MythTV working OK…
Both the TV cards have remotes, and the remote inputs are set up automagically as /dev/input/event6 and /event7, and both feed /dev/ir. Rather than use LIRC, Suse 11.0 seems to read input at these ports through a module called ‘ir-kbd-i2c’. This module only reads about half the buttons on the remotes for the TV cards: from what I’ve read, it is optimised for Hauppage remotes. I couldn’t rmmod it (but I’m a newbie, so I maybe doing it wrong), and I don’t know how to create a keybindings file for it.
I was able to walk through several the final stages of Daniel Saunders Howto (google) to set up LIRC on top - but even LIRC was not reading the remotes convincingly. The STOP and numeral 2 were read as the same input code.
Specific questions:
-how do I improve/adjust ir-kbd-i2c’s performance with either of my remotes (Y04G0033 and Y04000046)?
-how can I remove/disable ir-kbd-i2c if I can’t improve it?
-what might cause Lirc to confuse inputs?
(PS. My first post - how’d I go?)
Congrats for your first post . Yes it was a good one, im glad im not alone , but i dont use MythTV i use KDETV and after making this post i have searched the web and found this site Index of /remotes/leadtek
It has diffent configuration for winfast remotes maybe it will work for you too. By using one of the config`s i managed to enable the remote, the buttons from 1 to 0 , and the red buton that closes my pc when pressed . I hope this will help you to enable some buttons 
Hi Creatura - good to find your post. I’m glad you are having some satisfaction. I haven’t put much more energy into the problem but I did find this in the middle of a mythtv howto url:
DViCO FusionHDTV DVB-T Dual Digital Installation - MythTV
" Remote Control (Lircd)
This I found to be the most painful as I was using the wrong driver for a long time. But after i switched it became a breeze. Now on my system i have 2 /dev/input/events that work when you press a button. When i do a cat /dev/input/event3 and press the 0 key on the remote this happens:
cat /dev/input/event3
0000
[Control-C to quit]
So it seems that this should be the one to use… Unfortunately Not! Something else is parsing the input from your remote and is producing that. What you really want is something that produces binary gibberish when you press a button:
cat /dev/input/event4
����E�
�����E�
[Control-C to quit]
If your screen is mangled from catting out that then you can type “reset” to reset your terminal. So now that we have determined what device we should use it is time to see if we can record our key presses."
I am getting the results he (or she) describes at first, not the unprocessed input he (or she) thinks you should get… I will do some more work on this problem one day - but not tonight.
Thanks atcrank :), interesting post you have discovered but as i where reading the information from the link in your post i have discovered that the configuration is for a USB tv tuner mine is an internal tuner. To be onest im satified with the current standing of the tuner because i can navigate thru channels via remote :), as i said the only keys that work are thoose from 1 to 0 . Im giving up searching a how-to for kdeTV for my type of tuner. Maybe you can find it for me.