dib0700: infrared and hibernation issues

Bug #1035822 reported by sander
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

There are some severe issues with the dib0700 module. Watching tv is no problem, but hibernation seems to be instable. Also, the wrong protocol is loaded for the remote control and loading the protocol after hibernation wakeup sometimes fails.

This is my hardware:
http://www.terratec.net/en/products/Cinergy_T_USB_XXS_2068.html
Here you can see the remote control:
http://www.terratec.net/en/products/pictures/img/4041785_29db8c0f42.png

Issues:

1) Hibernating the system whilst watching tv fails consistently. One needs to reset the computer in order to proceed.

2) Sometimes loading the default protocol RC-5 after hibernation wakeup fails with this dmesg error:
dib0700: rc submit urb failed

If this happens, it is not possible to load any protocol using ir-keytable. Also, reloading the dib0700 module does not help. The only solution is to manually unplug the USB device and plug it in again. If you do this, the RC-5 protocol will be loaded.

3) The module always loads the RC-5 protocol whilst the remote control that was accompanied with my hardware does not support this protocol. The dib0700 module should know it needs to load the NEC protocol, or else there should be a straightforward way in Ubuntu to set the correct protocol.

4) After hibernation wakeup, the protocol always needs to be changed to nec again. The dib0700 module should know it had been set to the NEC protocol before hibernation and it should automatically load this protocol again. My workaround for this bug is to install the "hibernate" package and edit /etc/hibernate/common.conf:

OnResume 20 /usr/bin/ir-keytable -s `ls /sys/class/rc/` -p nec

5) Enable Wake on USB Activity as described on http://wiki.xbmc.org/index.php?title=HOW-TO:Suspend_and_wake_in_Ubuntu#Enable_Wake_on_USB_Activity does not work. Maybe I did something wrong, but I suspect this is related to the bug that the dib0700 module loads the wrong protocol, RC-5 (instead of NEC).

If any additional information is needed or if I need to run some tests, feel free to ask. I am really eager to get my Ubuntu TV experience as best as possible!

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-29-generic 3.2.0-29.46
ProcVersionSignature: Ubuntu 3.2.0-29.46-generic 3.2.24
Uname: Linux 3.2.0-29-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu12
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: sander 2868 F.... pulseaudio
 /dev/snd/controlC0: sander 2868 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xfe700000 irq 55'
   Mixer name : 'Realtek ALC892'
   Components : 'HDA:10ec0892,14627681,00100302'
   Controls : 44
   Simple ctrls : 21
Card1.Amixer.info:
 Card hw:1 'Generic'/'HD-Audio Generic at 0xfe640000 irq 56'
   Mixer name : 'ATI R6xx HDMI'
   Components : 'HDA:1002aa01,00aa0100,00100200'
   Controls : 6
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined penum
   Playback channels: Mono
   Mono: Playback [on]
Date: Sun Aug 12 10:38:26 2012
HibernationDevice: RESUME=UUID=7e91278a-c36a-4e13-a04f-b7997c624d45
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: MSI MS-7681
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-29-generic root=UUID=e19aaf97-63bd-4e5d-83bf-e79f61103001 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-29-generic N/A
 linux-backports-modules-3.2.0-29-generic N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: Upgraded to precise on 2012-05-26 (77 days ago)
dmi.bios.date: 07/13/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V1.14
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P67A-GD65 (MS-7681)
dmi.board.vendor: MSI
dmi.board.version: 2.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: MSI
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV1.14:bd07/13/2011:svnMSI:pnMS-7681:pvr2.0:rvnMSI:rnP67A-GD65(MS-7681):rvr2.0:cvnMSI:ct3:cvr2.0:
dmi.product.name: MS-7681
dmi.product.version: 2.0
dmi.sys.vendor: MSI

Revision history for this message
sander (s-devrieze) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.5kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. Please only remove that one tag and leave the other tags. 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.

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'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.6-rc1-quantal/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
sander (s-devrieze) wrote :

Unfortunately, the mainline kernel does not includes the dib0700 modules:

/lib/modules/3.2.0-29-generic/kernel/drivers/media/rc/keymaps/rc-dib0700-nec.ko
/lib/modules/3.2.0-29-generic/kernel/drivers/media/rc/keymaps/rc-dib0700-rc5.ko
/lib/modules/3.2.0-29-generic/kernel/drivers/media/dvb/dvb-usb/dvb-usb-dib0700.ko

Hence, dmesg output with the mainline kernel looks as follows:

[ 112.526864] usb 2-1.5: new high-speed USB device number 5 using ehci_hcd
[ 112.619442] usb 2-1.5: New USB device found, idVendor=0ccd, idProduct=00ab
[ 112.619447] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 112.619450] usb 2-1.5: Product: Cinergy T XXS
[ 112.619452] usb 2-1.5: Manufacturer: TerraTec GmbH
[ 112.619454] usb 2-1.5: SerialNumber: 0000000001

Obviosuly, no feature of the hardware works with mainline. Am I supposed to install mainline kernel headers and compile the dib0700 modules myself?

sander (s-devrieze)
tags: added: kernel-unable-to-test-upstream
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
sander (s-devrieze) wrote :

Can I test something else to help these issues to get fixed? I am still using Ubuntu 12.04.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.