|
From: cipher <ci...@me...> - 2009-01-15 18:05:09
|
Hi all, Thanks in advance for your time and for putting some effort regarding this matter. I have a Pinnacle PCTV Hybrid Pro PCI. Works ok with MPlayer to tune channels and watch tv. MPlayer claims the device is a 310i chip from Pinnacle. Installed lirc 0.8.4a with options: ./configure --with-driver=devinput && make && sudo make install. Start lircd this way: /usr/sbin/lircd -H dev/input -d /dev/input/event5 Start irexec and the /dev/input/event5 device is initialized. I can't get the remote to work. It is a RC-42D. According to kernel documentation the saa7134 driver is built in with the remote code which should make him work right out of the box. I followed the instructions in http://linux.bytesex.org/v4l2/faq.html, where is very clear how to have the remote working: ****************************** Quoting http://linux.bytesex.org/v4l2/faq.html: Q: But I want use lircd for IR input. No problem, you can do that too: 1. Get a recent lircd version with linux input layer support. The 0.6.6 release is too old, a cvs snapshot or a 0.7 pre-release should do. You only need to build the lircd daemon + tools, no lirc kernel drivers needed. Take care that the dev/input driver is included when building lircd (either ./configure --with-driver=any to simply include all drivers or --with-driver=devinput). 2. Load the evdev module (which is part of the linux input layer). Check /proc/bus/input/devices to see which eventn device the IR input device has. 3. Fetch the lircd.conf file for the linux input layer. 4. Start the daemon this way: /usr/sbin/lircd -H dev/input -d /dev/input/eventn. Q: How can I use the infrared remote shipped with the tv card ? In the 2.6 kernels the remote simply is registered as keyboard input device within the linux input layer. When using the saa7134 driver it "just works", with bttv you'll have to load either ir-kbd-gpio or ir-kbd-i2c depending on your TV card. If in doubt just try both. Have a look at the /proc/bus/input/devices file to see whenever the device is present or not. End quoting http://linux.bytesex.org/v4l2/faq.html ****************************** I use the input-layer-tools to check if events are arriving and nothing comes... :) Udev loads saa7134 module, the device in /dev/input/event5 is created and it has a physical address i2c-1/1-0047/ir0,which you can find below. It is also seen as a keyboard which is part of the deal -> "H: Handlers=kbd event5". Check this out: xifre@venus:~$ dmesg | grep saa saa7130/34: v4l2 driver version 0.2.14 loaded saa7133[0]: found at 0000:03:05.0, rev: 209, irq: 20, latency: 64, mmio: 0xfdeff000 saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i [card=101,autodetected] saa7133[0]: board init: gpio is 600c000 ir-kbd-i2c: Pinnacle PCTV detected at i2c-1/1-0047/ir0 [saa7133[0]] saa7133[0]: i2c eeprom 00: bd 11 2f 00 54 20 1c 00 43 43 a9 1c 55 d2 b2 92 saa7133[0]: i2c eeprom 10: ff e0 60 06 ff 20 ff ff 00 30 8d 2f dd 75 ff ff saa7133[0]: i2c eeprom 20: 01 2c 01 23 23 01 04 30 98 ff 00 e7 ff 21 00 c2 saa7133[0]: i2c eeprom 30: 96 10 03 32 15 20 ff 15 0e 6c a3 eb 04 4f 4c 3f saa7133[0]: i2c eeprom 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff saa7133[0]: i2c eeprom f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff tuner' 1-004b: chip found @ 0x96 (saa7133[0]) saa7133[0]: registered device video0 [v4l2] saa7133[0]: registered device vbi0 saa7133[0]: registered device radio0 DVB: registering new adapter (saa7133[0]) xifre@venus:~$ cipher@aleera:~$ dmesg | grep v4l2 saa7130/34: v4l2 driver version 0.2.14 loaded saa7133[0]: registered device video0 [v4l2] cipher@aleera:~$ xifre@venus:~$ dmesg | grep Pinnacle saa7133[0]: subsystem: 11bd:002f, board: Pinnacle PCTV 310i [card=101,autodetected] input: Pinnacle PCTV as /class/input/input5 ir-kbd-i2c: Pinnacle PCTV detected at i2c-1/1-0047/ir0 [saa7133[0]] Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=1 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=0 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=1 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=0 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=1 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=0 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=1 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=0 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=1 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=0 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=1 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=0 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=1 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=0 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=1 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=0 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=1 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=0 (...) xifre@venus:~$ xifre@venus:~$ lsmod Module Size Used by btcx_risc 8584 0 radeon 117764 2 snd_seq_dummy 7684 0 snd_seq_oss 32412 0 snd_seq_midi_event 10880 1 snd_seq_oss snd_seq 49444 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event snd_seq_device 11532 3 snd_seq_dummy,snd_seq_oss,snd_seq snd_pcm_oss 41376 0 snd_mixer_oss 18816 1 snd_pcm_oss nfsd 202780 25 exportfs 8704 1 nfsd tda1004x 17668 1 saa7134_dvb 18828 0 videobuf_dvb 10628 1 saa7134_dvb dvb_core 74728 1 videobuf_dvb tuner 35020 0 tea5767 10116 1 tuner tda8290 16260 1 tuner tda18271 32264 1 tda8290 tda827x 13572 2 tda8290 tuner_xc2028 21136 1 tuner xc5000 13572 1 tuner tda9887 12676 1 tuner tuner_simple 11784 1 tuner mt20xx 14856 1 tuner tea5761 8708 1 tuner saa7134 132820 1 saa7134_dvb videodev 33792 2 tuner,saa7134 v4l1_compat 16132 1 videodev compat_ioctl32 5376 1 saa7134 snd_hda_intel 195704 0 v4l2_common 14720 2 tuner,saa7134 videobuf_dma_sg 16900 3 saa7134_dvb,videobuf_dvb,saa7134 rtc_cmos 13856 0 videobuf_core 21252 3 videobuf_dvb,saa7134,videobuf_dma_sg snd_pcm 71044 2 snd_pcm_oss,snd_hda_intel parport_pc 39996 0 snd_timer 24968 2 snd_seq,snd_pcm rtc_core 21148 1 rtc_cmos ir_kbd_i2c 13072 1 saa7134 parport 37588 1 parport_pc rtc_lib 6912 1 rtc_core snd_page_alloc 13832 2 snd_hda_intel,snd_pcm snd_hwdep 12548 1 snd_hda_intel ir_common 40964 2 saa7134,ir_kbd_i2c k8temp 9216 0 tveeprom 18448 1 saa7134 snd 52280 9 snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep i2c_piix4 12428 0 r8169 31492 0 hwmon 7068 1 k8temp xifre@venus:~$ xifre@venus:~$ cat /proc/bus/input/devices I: Bus=0018 Vendor=0000 Product=0000 Version=0000 N: Name="Pinnacle PCTV" P: Phys=i2c-1/1-0047/ir0 S: Sysfs=/class/input/input5 U: Uniq= H: Handlers=kbd event5 B: EV=100003 B: KEY=108fc010 2100802 0 0 0 0 48000 2180 c0000801 9e1680 0 0 4ffc xifre@venus:~$ ls -la /dev/input/ total 0 drwxr-xr-x 3 root root 220 2009-01-13 19:42 ./ drwxr-xr-x 21 root root 14580 2009-01-13 20:17 ../ drwxr-xr-x 2 root root 120 2009-01-13 19:42 by-path/ crw-r----- 1 root root 13, 64 2009-01-13 19:42 event0 crw-r----- 1 root root 13, 65 2009-01-13 19:42 event1 crw-r----- 1 root root 13, 66 2009-01-13 19:42 event2 crw-r----- 1 root root 13, 67 2009-01-13 19:42 event3 crw-r----- 1 root root 13, 68 2009-01-13 19:42 event4 crw-r----- 1 root root 13, 69 2009-01-13 19:42 event5 crw-r----- 1 root root 13, 63 2009-01-13 19:42 mice crw-r----- 1 root root 13, 32 2009-01-13 19:42 mouse0 xifre@venus:~$ xifre@venus:~$ file /dev/input/* /dev/input/by-path: directory /dev/input/event0: character special (13/64) /dev/input/event1: character special (13/65) /dev/input/event2: character special (13/66) /dev/input/event3: character special (13/67) /dev/input/event4: character special (13/68) /dev/input/event5: character special (13/69) /dev/input/mice: character special (13/63) /dev/input/mouse0: character special (13/32) xifre@venus:~$ xifre@venus:~$ uname -a Linux venus 2.6.25.10 #4 SMP Sat Jan 10 20:12:39 WET 2009 i686 AMD Athlon(tm) 64 X2 Dual Core Processor 5200+ AuthenticAMD GNU/Linux xifre@venus:~$ sudo /usr/local/sbin/lircd -n -H dev/input -d /dev/input/event5 lircd: WARNING: you should specify a valid gap value lircd: lircd(devinput) ready cipher@aleera:~/share/input$ input-events usage: input-events [ -g ] [ -t <sec> ] devnr cipher@aleera:~/share/input$ xifre@venus:~/share/input$ sudo input-events 5 -t 60 /dev/input/event5 bustype : BUS_I2C vendor : 0x0 product : 0x0 version : 0 name : "Pinnacle PCTV" phys : "i2c-1/1-0047/ir0" bits ev : EV_SYN EV_KEY EV_REP waiting for events (NONE...!!!) My thoughts: saa7133[0]: board init: gpio is 600c000 -> is there a chance that for any reason udev is not loading the proper module and i have to use the bttv and ir-kbd-gpio module? i think it's not present in the kernel code these days. Not sure. ir-kbd-i2c: Pinnacle PCTV detected at i2c-1/1-0047/ir0 [saa7133[0]] -> the IR device, although it's saa7133, the saa7134 module is loaded. Not sure if we got something wrong here. The remote is supported and has a configuration file. Should i use the lircd configuration for the linux-input-layer or the RC-42D configuration in remotes/pinnacle_systems/RC-42D? ir-kbd-i2c: Pinnacle PCTV detected at i2c-1/1-0047/ir0 [saa7133[0]] Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=1 Pinnacle PCTV: unknown key: key=0x10 raw=0x10 down=0 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=1 Pinnacle PCTV: unknown key: key=0x35 raw=0x35 down=0 -> Something abnormal here i supose... not sure... Anyway... I also configured lircd with the Pinnacle PCTV Pro (pinsys) driver and tried to use it as a serial device but got no luck. Remote has batteries, new ones. I have two of these cards in diferent computers with the same configuration and none of them works. The supplied IR cable is connected at the back of the pci card, of course. Could you please point me in the right direction to get the remote working and enlighten me on what i am doing wrong? Feel free to ask for output you may think necessary to unravel the mistery. Kind regards, Igor --- |