14f1:8804 cx88 remote control does not work

[Daniel Banck]

I'm using a Hauppauge WinTV-HVR400 with remote control for some of years now.
It worked fine with every ubuntu version below natty. Now it does not work at all.

The IR is detected correctly.
[ 7.616816] input: cx88 IR (Hauppauge WinTV-HVR400 as /devices/pci0000:00/0000:00:1e.0/0000:07:02.0/rc/rc0/input6

I: Bus=0001 Vendor=0070 Product=6906 Version=0001
N: Name="cx88 IR (Hauppauge WinTV-HVR400"
P: Phys=pci-0000:07:02.0/ir0
S: Sysfs=/devices/pci0000:00/0000:00:1e.0/0000:07:02.0/rc/rc0/input6
U: Uniq=
H: Handlers=kbd event6
B: PROP=0
B: EV=100013
B: KEY=100fc312 214a80200000000 0 18000 41a800004801 9e168000000000 10000ffc
B: MSC=10

And it should be accessible on /dev/input/event6, but with and without lirc the remote control does not work at all.

evtest or irw won't produce any output on keypress.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: linux-image-2.6.38-8-generic 2.6.38-8.42
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: daniel 1251 F.... pulseaudio
 /dev/snd/controlC2: daniel 1251 F.... pulseaudio
 /dev/snd/controlC1: daniel 1251 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf1ff8000 irq 46'
   Mixer name : 'VIA VT1828S'
   Components : 'HDA:11064441,104383d0,00100100'
   Controls : 36
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'CX8801'/'Conexant CX8801 at 0xf8000000'
   Mixer name : 'CX88'
   Components : ''
   Controls : 3
   Simple ctrls : 2
Card2.Amixer.info:
 Card hw:2 'Headset'/'Logitech Logitech Wireless Headset at usb-0000:00:1d.0-1.2, full speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0a12'
   Controls : 4
   Simple ctrls : 2
Date: Sun May 15 19:06:10 2011
HibernationDevice: RESUME=UUID=f28dc350-ddc8-46f2-8be9-69538ce298e7
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=7cb04515-59e6-400e-aa93-e3b0a0f19c85 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-2.6.38-8-generic N/A
 linux-backports-modules-2.6.38-8-generic N/A
 linux-firmware 1.52
RfKill:

SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:

dmi.bios.date: 12/07/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1207
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P7P55D
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1207:bd12/07/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP7P55D:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Lars Fehr (lars-fehr)]

My WinTV Go2 is also effected by this bug.

The IR-Control worked fine since I updated to natty.
It worked out-of-the-box and was registered like a keyboard-device.
I didn't install lirc to get it to work.

$ dmesg | grep cx88
[ 49.404571] cx88/0: cx2388x v4l2 driver version 0.0.8 loaded
[ 49.404597] cx8800 0000:05:05.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 49.405867] cx88[0]: subsystem: 0070:3401, board: Hauppauge WinTV 34xxx models [card=1,autodetected], frontend(s): 0
[ 49.405868] cx88[0]: TV tuner type -1, Radio tuner type -1
[ 49.551459] tuner 0-0061: chip found @ 0xc2 (cx88[0])
[ 49.589556] cx88[0]: warning: unknown hauppauge model #34704
[ 49.589557] cx88[0]: hauppauge eeprom: model=34704
[ 49.628122] input: cx88 IR (Hauppauge WinTV 34xxx as /devices/pci0000:00/0000:00:1e.0/0000:05:05.0/rc/rc0/input5
[ 49.628165] rc0: cx88 IR (Hauppauge WinTV 34xxx as /devices/pci0000:00/0000:00:1e.0/0000:05:05.0/rc/rc0
[ 49.629252] rc rc0: lirc_dev: driver ir-lirc-codec (cx88xx) registered at minor = 0
[ 49.629258] cx88[0]/0: found at 0000:05:05.0, rev: 5, irq: 21, latency: 64, mmio: 0xfd000000
[ 49.629294] cx88[0]/0: registered device video1 [v4l2]
[ 49.629313] cx88[0]/0: registered device vbi1
[ 49.629332] cx88[0]/0: registered device radio1
[ 49.894771] cx2388x alsa driver version 0.0.8 loaded
[ 49.894799] cx88_audio 0000:05:05.1: PCI INT A -> GSI 21 (level, low) -> IRQ 21
[ 49.894818] cx88[0]/1: CX88x/0: ALSA support for cx2388x boards

I am using a 32-bit kernel:
$ uname -a
Linux machine 2.6.38-8-generic-pae #42-Ubuntu SMP Mon Apr 11 05:17:09 UTC 2011 i686 i686 i386 GNU/Linux

[alpianon (alberto-pianon)]

I have the same problem with the HVR-4000 remote.
The only "output" I can get is from /dev/lirc0 but it is irregular and uncomprehensible

I tried to apply this patch to cx88 kernel modules:
https://patchwork.kernel.org/patch/758262/
however it still does not work

[alpianon (alberto-pianon)]

SOLVED!
There were two patches to apply for 32-bit kernel, not only one

http://<email address hidden>/msg30942.html

However, only one patch as been accepted in the stable 2.6.38 tree, the other one has been inserted in the devel tree, as far as I can understand from here (and from next messages in thread):

http://<email address hidden>/msg30982.html

[alpianon (alberto-pianon)]

however there are two other issues:

1) in order to make it work, one has to remove the ir-lirc-codec module AFTER it has been loaded
if one prevents it to load from the beginning (with something like "alias ir-lirc-codec /dev/null") the remote does not work
One has to let it load and THEN remove it, then trying with evtest or ir-keytable the remote seems to work fine

2) I did not manage to make the remote work with lirc yet, but only with inputlirc (while it worked perfectly with lirc with my previous installation of Ubuntu 9.04)

[alpianon (alberto-pianon)]

the command I am using is
inputlircd -g -n cx88* -m 0 -d /var/run/lirc/lircd

[tafkaz (zucca-web)]

Have the same problem after updating to natty.
Unfortunately this is all a little to new to me. i don't get it. Is there a solution for this issue yet?
Or do i simply have to wait till some new kernel-version is being released?
Maybe there's a kernel repo around with allready all the fixes and patches included?

Thanks for your help, I presume it's all easy to you, but i am just a mythtv-user with no experience in kernel patching and so on!

[tafkaz (zucca-web)]

i noticed some kernel updates in the repos today and "apt-get upgrade" ran flawlessly.
After reboot i noticed the remote will work when lircd is not running. at least i get some input on the cli if i press the remote buttons.
If i restart /etc/init.d/lirc though (and it seems it starts perfectly, no errors), this effect vanishes immediately.
This is all very strange

[Steve Blamey (fedorus-deactivatedaccount)]

Following the kernel update to 2.6.38-10, I have been able to get the remote working for my Hauppauge WinTV Nova-T cards (Single Tuner) in Mythbuntu.

[tafkaz (zucca-web)]

Great to hear Steve!
could you please post your hardware.conf and lircd.conf?
Or what else did you do?

Thanks Sascha

[Steve Blamey (fedorus-deactivatedaccount)]

@tafkaz I've never had any success getting the WinTV Nova-T remote to work when using Mythbuntu's configuration center or using dpkg-reconfigure so I configure it manually (see my files below, this lircd.conf will only work with the WinTV Nova-T remote).

Then:

sudo service lirc restart

test with:

irw

press some remote buttons and you should see output similar to:

000000008001001c 00 OK hauppauge_nova_t_uk
0000000080010080 00 Stop hauppauge_nova_t_uk
00000000800100a7 00 Record hauppauge_nova_t_uk
0000000080010002 00 1 hauppauge_nova_t_uk
0000000080010003 00 2 hauppauge_nova_t_uk
0000000080010004 00 3 hauppauge_nova_t_uk

If you are using MythTV you would then need to edit ~/.lirc/mythtv to map the remote buttons (OK, Stop, Record, etc.) to keypresses.

hardware.conf, replace the /dev/event device with the appropriate device on your system:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
#REMOTE="Hauppauge DVB-T card (ver. 2.1)"
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="/dev/input/event6"
REMOTE_SOCKET=""
REMOTE_LIRCD_ARGS=""

#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""

#Enable lircd
START_LIRCD="true"

#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="false"

# Default configuration files for your hardware if any
LIRCMD_CONF=""

lircd.conf:

# Please make this file available to others
# by sending it to <email address hidden>
#
# this config file was automatically generated
# using lirc-0.7.1pre2(any) on Sat Sep 17 01:00:56 2005
#
# contributed by
#
# brand: lircd.conf.kernel-2.6.13.1.conf
# model no. of remote control:
# devices being controlled by this remote:
#

begin remote

  name hauppauge_nova_t_uk
  bits 16
  eps 30
  aeps 100

  one 0 0
  zero 0 0
  pre_data_bits 16
  pre_data 0x8001
  gap 135803
  toggle_bit 0

      begin codes
          Power 0x0074
          Go 0x0161
          TV 0x0179
          Videos 0x0189
          Music 0x0188
          Pictures 0x016F
          Guide 0x016D
          Radio 0x0181
          Up 0x0067
          Left 0x0069
          Right 0x006A
          Down 0x006C
          OK 0x001C
          Back 0x00AE
          Menu 0x008B
          VolumeUp 0x0073
          VolumeDown 0x0072
          PreviousChannel 0x019C
          Mute 0x0071
          ChannelUp 0x0192
          ChannelDown 0x0193
          Record 0x00A7
          Stop 0x0080
          Replay 0x00A8
          Play 0x00CF
          Skip ...

[tafkaz (zucca-web)]

OOOOH STeve!
You're so much the man!
This has resolved the issue...the remote is working again!

Thank you very much
Sascha

[tafkaz (zucca-web)]

edit: had to change some of the entries in my .lircrc for mythtv to match the new mappings...
But works great now!

[Steve Blamey (fedorus-deactivatedaccount)]

Glad I could help, tafkaz.

[penalvch (penalvch)]

Daniel Banck, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please do not test the kernel in the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. As well, please comment on which kernel version specifically you tested.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream', and comment as to why specifically you were unable to test it.

Please let us know your results. Thanks in advance.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#Bug_Reporting_Etiquette
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

[Daniel Banck (dbanck)]

Everything is working fine with 12.04.

[penalvch (penalvch)]

Daniel Banck, ok. Do you desire a backport for a prior release, or may this report be closed as Status Invalid?

[Daniel Banck (dbanck)]

I don't need a backport personally. Furthermore I think the source of the issue would be hard to find.
You may close this bug report. Thanks! (:

[penalvch (penalvch)]

Daniel Banck, this bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.