[Bug 231513] New: Hauppauge grey remote not working with lirc 0.8.0-41 supplied with OpenSuse 10.2
https://bugzilla.novell.com/show_bug.cgi?id=231513 Summary: Hauppauge grey remote not working with lirc 0.8.0-41 supplied with OpenSuse 10.2 Product: openSUSE 10.2 Version: RC 5 Platform: i686 OS/Version: SuSE Other Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: gchris@bellsouth.net QAContact: qa@suse.de The new style Hauppauge (4 colored buttons at the bottom) remote shipped with PVR-150/250/350 TV cards is not being detected properly by the version of LIRC shipped with OpenSuse 10.2 (GM). Lirc creates a /dev/eventx and a /dev/ir linked to eventx. The ir-kbd-i2c module is loaded and detects the Hauppauge card after ivtv runs: (two pcHDTV 3000 cards are also present) Mediacenter:~ # dmesg | egrep 'ivtv|tvee' ivtv: ==================== START INIT IVTV ==================== ivtv: version 0.8.0 (tagged release) loading ivtv: Linux version: 2.6.18.2-34-default SMP mod_unload 586 REGPARM gcc-4.1 ivtv: In case of problems please include the debug info between ivtv: the START INIT IVTV and END INIT IVTV lines, along with ivtv: any module options, when mailing the ivtv-users mailinglist. ivtv0: Autodetected Hauppauge WinTV PVR-350 card (cx23415 based) ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes) tveeprom 3-0050: Hauppauge model 48132, rev K268, serial# 7614695 tveeprom 3-0050: tuner model is LG TAPE H001F MK3 (idx 68, type 47) tveeprom 3-0050: TV standards NTSC(M) (eeprom 0x08) tveeprom 3-0050: audio processor is MSP4448 (idx 27) tveeprom 3-0050: decoder processor is SAA7115 (idx 19) tveeprom 3-0050: has radio, has IR remote tuner 3-0043: chip found @ 0x86 (ivtv i2c driver #0) tuner 3-0061: chip found @ 0xc2 (ivtv i2c driver #0) saa7115 3-0021: saa7115 found @ 0x42 (ivtv i2c driver #0) saa7127 3-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) msp3400 3-0040: MSP4448G-A2 found @ 0x80 (ivtv i2c driver #0) ivtv0: Encoder revision: 0x02050032 ivtv0: Decoder revision: 0x02020023 ivtv0: Registered device video0 for encoder MPEG ivtv0: Registered device video32 for encoder YUV ivtv0: Registered device vbi0 for encoder VBI ivtv0: Registered device video24 for encoder PCM audio ivtv0: Registered device radio0 for encoder radio ivtv0: Registered device video16 for decoder MPEG ivtv0: Registered device vbi8 for decoder VBI ivtv0: Registered device vbi16 for decoder VOUT ivtv0: Registered device video48 for decoder YUV ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes) ivtv0: Initialized Hauppauge WinTV PVR-350, card #0 ivtv: ==================== END INIT IVTV ==================== ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-3/3-0018/ir0 [ivtv i2c driver #0] Mediacenter:~ # The tv card works: chris@Mediacenter:~> ivtv-tune --freqtable=us-bcast --channel=5 /dev/video0: 77.250 MHz (Signal Detected) chris@Mediacenter:~> cat /dev/video0 > my.mpg gives me a file containing good video and sound. But pressing a key on the remote returns an error in dmesg, for example: Pressing the 'TV' key on the remote, Dmesg shows: i2c IR (Hauppauge): unknown key: key=0x1c raw=0x3f9c down=1 i2c IR (Hauppauge): unknown key: key=0x1c raw=0x3f9c down=0 or sometimes: i2c IR (Hauppauge): unknown key: key=0x1c raw=0x379c down=1 i2c IR (Hauppauge): unknown key: key=0x1c raw=0x379c down=0 But lircd.conf shows correct key mapping for this key to be: 'TV' 0x000000000000179C # TV and all other keys show the same corruption of the high order characters with the low order characters recognized correctly. The irw command does not provide any output. The irrecord command does not recognize any function keys, only the number keys from 0-9 are recognized. A recording using the 1 & 2 keys looks like this: begin remote name /home/mythtv/Desktop/irrecord.txt.conf bits 8 eps 30 aeps 100 one 0 0 zero 0 0 pre_data_bits 24 pre_data 0x800100 gap 135993 toggle_bit 0 begin codes One 0x02 Two 0x03 end codes end remote When lirc.conf says it should look like this: (Note even the number of bits differs!) begin remote name Hauppauge_350 bits 13 flags RC5|CONST_LENGTH eps 30 aeps 100 one 969 811 zero 969 811 plead 1097 gap 114605 toggle_bit 2 begin codes '1' 0x0000000000001781 # 1 '2' 0x0000000000001782 # 2 end codes end remote I see from the Suse forums that I'm not the only user experiencing this problem so I hope you can help me get a handle on it. http://www.suseforums.net/lofiversion/index.php/t28671.html Thank you! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231513 gchris@bellsouth.net changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gchris@bellsouth.net ------- Comment #1 from gchris@bellsouth.net 2007-01-03 14:13 MST ------- Ooops! Lirc creates its objects in /dev/input, not /dev. Also, this hardware was tested and works correctly under Windows/Hauppauge software. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231513 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |lnussel@novell.com |screening@forge.provo.novell| |.com | -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231513 ------- Comment #2 from gchris@bellsouth.net 2007-01-04 06:29 MST ------- Another user - same problem! http://forums.suselinuxsupport.de/index.php?showtopic=48629 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231513 ------- Comment #3 from d.r.newman@qub.ac.uk 2007-01-07 11:01 MST ------- I've got lirc + ivtv + mythtv working under SUSE 10.2. But you may not need to do everything that I did - namely downloading the source for LIRC 0.8.1 (now on Sourceforge), compiling and installing it. But you may get away by just making sure your copy of SUSE 10.2 uses lirc_i2c instead of ir-kbd-i2c. The installation created the following entries in /dev : lrwxrwxrwx 1 root root 5 2007-01-07 17:06 /dev/lirc -> lirc0 crw-rw---- 1 root root 61, 0 2007-01-07 17:06 /dev/lirc0 srw-rw-rw- 1 root video 0 2007-01-07 17:06 /dev/lircd Then I needed to put a couple of lines in /etc/sysconfig/lirc to tell SuSE where to look and which module to load: LIRCD_DEVICE="/dev/lirc0" LIRC_MODULE="lirc_i2c" That may be all you need. But if not ... I also moved ir-kdb-i2c out of /lib/modules/2.6.18.2-34-default/kernel/drivers/media/video and did a depmod -ae, so that SUSE 10.2 would NOT load that driver. And if that is not enough, you may need to download and compile a new LIRC (after removing the SUSE one, rpm -e lirc-kmp-default). In my case, when I rebooted everything was working, including remote control of MythTV and IRKick under KDE responding the the remote. Quite unlike the situation produced by the TV Card configuration tool in YAST. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231513 ------- Comment #4 from gchris@bellsouth.net 2007-01-07 14:54 MST ------- Thanks for the suggestion David. I had tried reverting back to lirc_i2c without success but I hadn't gone to the lengths you did to kill ir-kbd-i2c so that may explain why. I'm also investigating how to upload a new lookup table to make ir-kbd-i2c do the job but that requires learning much more about the software than any user should be expected to and my irritation at Suse is growing by the minute. This problem apparently originated with the 2.6 kernel and Suse has simply perpetuated it for the last 2 years. They claim to support the PVR-x50 TV cards but Yast can't set them up, there is no firmware in the distro to run them, they ship no desktop apps that are compatible with them, and you need a degree in programing to get the remotes to work! Great job Suse! If you really care about interoperability how about starting with the packages you're already shipping! Thus this bug report... BTW David, there is also a homegrown replacement for ir-kbd-i2c called (I think) lirc_pvr150 which is reported to work for that card with Suse 10.2 but I don't know if it's applicable to the PVR-350. Also BTW I noted that Jarod Wilson went the lirc_i2c route with Fedora Core 6 so I suspect you've got the best solution. I'm just a little too stubborn when it comes to walking away from a challenge. Best regards! -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231513 lnussel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |WONTFIX ------- Comment #5 from lnussel@novell.com 2007-01-11 02:27 MST ------- I don't have the hardware so I can't do anything about this problem unless someone sends me a patch for the lirc package. Anyways, sounds like ir-kdb-i2c creates an input device. If that is the case just point lirc at that one. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=231513 ------- Comment #6 from gchris@bellsouth.net 2007-01-11 11:14 MST ------- Use of Opensuse's LIRC default driver ir-kbd-i2c with Hauppauge PVR-350 remotes is possible but ill-advised for applications like Mythtv for several reasons. Probably the most compelling is that ir-kbd-i2c is primarily concerned with input devices (i.e. IR remotes) but does not address IR Blasters which are needed for most Mythtv installations. LIRC already does that so using lirc_i2c for remote control input as well makes more sense. Other considerations are that there is little information in the distro to acquaint users with the architectural differences between the older lirc_i2c driver and ir-kbd-i2c. That begins with the misleading and incomplete /usr/share/doc/packages/lirc/README.SUSE which implies that only DVB cards use /dev/input/eventx, does not reveal that all the old lircd.conf and lircc files are obsoleted by the new driver, does not explain that a custom keycode table is needed or how to create it, does not supply the input-20051128-143821.tar.gz software utility which must be downloaded and installed to view the default keycode table and load the new user-created keycode table and does not provide a sample script to load the new table or explain how to integrate the script into init.d. In short, using ir-kbd-i2c might make a wiki article, but it is not for the faint-hearted and switching to lirc_i2c probably makes more sense for most users. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
participants (1)
-
bugzilla_noreply＠novell.com