Difference between revisions of "Template:Making-it-work:dvb-usb-dib0700"

From LinuxTVWiki
Jump to: navigation, search
m (Remote control)
(Keys repeated twice: Added note stating that changing toggle bit mask prevents key repeats on remote)
 
(46 intermediate revisions by 14 users not shown)
Line 1: Line 1:
== Making it work ==
+
== Making it Work (generic for all dib0700) ==
 +
<noinclude><div style="background:#FF1F1F">
 +
This page is a Template that is included by a couple of dib0700 based devices.
  
 +
On the left in the toolbox there is a link called '''What links here'''. Use it to find the product
 +
pages that include this template.
 +
 +
If you have product specific information, please include it on the product page.
 +
 +
See [[TerraTec Cinergy T USB XXS]] for an example of how to do this.
 +
</div></noinclude>
  
 
{{Firmware:dvb-usb-dib0700}}
 
{{Firmware:dvb-usb-dib0700}}
  
 
=== Drivers ===
 
=== Drivers ===
It requires the dib0700 driver. Just use Mercurial by following the [[How to install DVB device drivers]] instructions.
+
It requires the dib0700 driver. Just use Mercurial by following the [[How to Obtain, Build and Install V4L-DVB Device Drivers]] instructions.
  
{{Note|1=These patches still haven't made it into the tree, and have not received a lot of feedback after the latest official merges. Use at your own risk if you feel that you need them.
+
==== Forcing the activation of LNAs (Low Noise Amplifier) ====
<div {{PreStyle}}>
+
; [http://www.linuxtv.org/pipermail/linux-dvb/2007-August/019493.html Silence unknown keycodes]
+
: When an unknown key code is received (from another remote, like the receiver's or the TV's), it is not eaten and the module keeps yelling about it. This patch stops the yelling.
+
: ''Jonas Anden, Thu Aug 2 00:28:17 CEST 2007''
+
: This patch is not cleanly applicable, but it is an easy one-liner to do by hand.
+
: This patch is regarded as not really being the proper fix; it just limits the effect of bad behaviour.
+
: This patch is not to be used with the following patch.
+
: This patch should be deprecated once the following patch has seen more testing.
+
  
; [http://www.linuxtv.org/pipermail/linux-dvb/2008-February/023844.html Key repeat for dib0700 IR receiver]
+
You may have to force LNA to get this card working:
: Solves remote toggle bit stuff and implements repeated key feature (with repeat delay to avoid unwanted double hits) for rc-5 and nec protocols. It also contains some keymap for the remotes used for testing (a philipps compatible rc5 remote and a teac nec remote). They are far from being complete since I've used them just for testing.
+
: ''Filippo Argiolas, Tue Feb 19 16:17:55 CET 2008''
+
: This patch is not to be used with the previous patch.
+
: '''This patch is prefered over the previous patch.'''
+
</div>
+
Please report [http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb on the list].}}
+
 
+
 
+
'''Note for WinTV Nova-T-500 users:''' the current drivers are close to stable at the moment (2008-01-25).  Occasional USB disconnects may still be experienced. The disconnects were caused by disabling the pull-down resistors or unintentional writes from the dib0700 bridge to the usb bus when accidentally hitting the end of a SOF packet. Why and when this happens can only be debugged by the dibcom firmware guys [http://www.linuxtv.org/pipermail/linux-dvb/2008-January/023123.html] . Other possible reasons for bad behavior could be bad reception (check your aerial, cabling, splitters and low-cost amplifiers) and EIT scanning. Search the [http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb linux-dvb mailing list] for more information and current problems being experienced.
+
 
+
=== On-board amplifier for Nova-T-500 ===
+
 
+
You may want/need to turn on the on-board amplifier:
+
  
 
In <tt>/etc/modprobe.d/options</tt> add:
 
In <tt>/etc/modprobe.d/options</tt> add:
  options dvb-usb-dib0700 force_lna_activation=1
+
  options dvb_usb_dib0700 force_lna_activation=1
 
+
=== Disabling the remote control sensor ===
+
  
 +
==== Disabling the remote control sensor ====
  
 
You may want to disable the remote control sensor if you are using another one and want to avoid error messages in the logs:
 
You may want to disable the remote control sensor if you are using another one and want to avoid error messages in the logs:
Line 43: Line 30:
 
  options dvb_usb disable_rc_polling=1
 
  options dvb_usb disable_rc_polling=1
  
=== All relevant kernel modules options ===
+
==== All relevant kernel modules options ====
 
+
 
+
 
In <tt>/etc/modprobe.d/options</tt> add:
 
In <tt>/etc/modprobe.d/options</tt> add:
 
  options [module name] [option name]=[setting]
 
  options [module name] [option name]=[setting]
Line 53: Line 38:
  
 
The debug values are bit fields, with each bit representing a different category. Add values to turn on multiple debugging categories.
 
The debug values are bit fields, with each bit representing a different category. Add values to turn on multiple debugging categories.
15.
 
 
 
==== dib3000mc ====
 
 
 
debug: turn on debugging (default: 0) (int)
 
 
buggy_sfn_workaround: Enable work-around for buggy SFNs (default: 0) (int)
 
 
==== mt2060 ====
 
 
 
debug:Turn on/off debugging (default:off). (int)
 
 
==== dvb_usb_dib0700 ====
 
 
 
force_lna_activation: force the activation of Low-Noise-Amplifyer(s) (LNA), if applicable for the device (default: 0=automatic/off). (int)
 
 
dvb_usb_dib0700_ir_proto: set ir protocol (0=NEC, 1=RC5 (default), 2=RC6). (int)
 
 
debug:set debugging level (1=info,2=fw,4=fwdata,8=data (or-able)). (debugging is not enabled) (int)
 
 
==== dvb_usb ====
 
 
 
debug: set debugging level (1=info,xfer=2,pll=4,ts=8,err=16,rc=32,fw=64,mem=128,uxfer=256  (or-able)). (int)
 
 
disable_rc_polling: disable remote control polling (default: 0). (int)
 
 
force_pid_filter_usage: force all dvb-usb-devices to use a PID filter, if any (default: 0). (int)
 
 
 
==== dvb_core ====
 
 
 
dvb_net_debug: enable debug messages (int)
 
 
frontend_debug: Turn on/off frontend core debugging (default:off). (int)
 
 
dvb_shutdown_timeout: wait <shutdown_timeout> seconds after close() before suspending hardware (int)
 
 
dvb_force_auto_inversion: 0: normal (default), 1: INVERSION_AUTO forced always (int)
 
 
dvb_override_tune_delay: 0: normal (default), >0 => delay in milliseconds to wait for lock after a tune attempt (int)
 
 
dvb_powerdown_on_sleep: 0: do not power down, 1: turn LNB voltage off on sleep (default) (int)
 
 
cam_debug: enable verbose debug messages (int)
 
 
debug: Turn on/off debugging (default:off). (int)
 
 
dvbdev_debug: Turn on/off device debugging (default:off). (int)
 
 
 
==== dibx000_common ====
 
 
 
debug: turn on debugging (default: 0) (int)
 
 
=== Sample kernel output - winTV Nova-T-500 ===
 
 
 
[  30.965645] dib0700: loaded with support for 5 different device-types
 
[  30.965925] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in cold state, will try to load a firmware
 
[  31.008899] dvb-usb: downloading firmware from file 'dvb-usb-dib0700-03-pre1.fw'
 
[  31.206081] dib0700: firmware started successfully.
 
[  31.711176] dvb-usb: found a 'Hauppauge Nova-T 500 Dual DVB-T' in warm state.
 
[  31.711222] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
 
[  31.711325] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
 
[  31.831535] DVB: registering frontend 0 (DiBcom 3000MC/P)...
 
[  31.854890] MT2060: successfully identified (IF1 = 1220)
 
[  32.388673] dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
 
[  32.388853] DVB: registering new adapter (Hauppauge Nova-T 500 Dual DVB-T)
 
[  32.394293] DVB: registering frontend 1 (DiBcom 3000MC/P)...
 
[  32.398790] MT2060: successfully identified (IF1 = 1220)
 
[  32.959607] input: IR-receiver inside an USB DVB receiver as /class/input/input4
 
[  32.959633] dvb-usb: schedule remote query interval to 150 msecs.
 
[  32.959637] dvb-usb: Hauppauge Nova-T 500 Dual DVB-T successfully initialized and connected.
 
[  32.959657] usbcore: registered new interface driver dvb_usb_dib0700
 
 
=== Sample kernel output - WinTV Nova-T stick ===
 
 
This is for the 70001 version, using the driver in Linux 2.6.22.1.
 
 
usb 1-10: new high speed USB device using ehci_hcd and address 8
 
usb 1-10: configuration #1 chosen from 1 choice
 
dvb-usb: found a 'Hauppauge Nova-T Stick' in cold state, will try to load a firmware
 
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-01.fw'
 
dib0700: firmware started successfully.
 
dvb-usb: found a 'Hauppauge Nova-T Stick' in warm state.
 
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
 
DVB: registering new adapter (Hauppauge Nova-T Stick).
 
DVB: registering frontend 2 (DiBcom 7000MA/MB/PA/PB/MC)...
 
MT2060: successfully identified (IF1 = 1220)
 
dvb-usb: Hauppauge Nova-T Stick successfully initialized and connected.
 
 
This is for the model 294 G, using the driver in Linux 2.6.23.9 with a HG of v4l-dvb from 29th of December 2007.
 
 
usb 3-5: new high speed USB device using ehci_hcd and address 80
 
usb 3-5: configuration #1 chosen from 1 choice
 
dib0700: loaded with support for 5 different device-types
 
dvb-usb: found a 'DiBcom STK7070P reference design' in cold state, will try to load a firmware
 
dvb-usb: downloading firmware from file 'dvb-usb-dib0700-1.10.fw'
 
dib0700: firmware started successfully.
 
dvb-usb: found a 'DiBcom STK7070P reference design' in warm state.
 
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
 
DVB: registering new adapter (DiBcom STK7070P reference design)
 
DVB: registering frontend 0 (DiBcom 7000PC)...
 
DiB0070: successfully identified
 
dvb-usb: DiBcom STK7070P reference design successfully initialized and connected.
 
usbcore: registered new interface driver dvb_usb_dib0700
 
 
 
=== Remote control ===
 
Grey top, black bottom, 45 buttons, snowboard shape.
 
 
Find the IR receiver's device by looking in the 'dmesg' output for a line similar to:
 
  
input: IR-receiver inside an USB DVB receiver as /class/input/'''input4'''
+
===== dib3000mc =====
 +
{{Modparm|debug|Turn on debugging||0 (off)|integer}}
 +
{{Modparm|buggy_sfn_workaround|Enable work-around for buggy SFNs||0 (disabled)|integer}}
  
Additionally, the IR receiver will be listed if you execute the command:
+
===== mt2060 =====
 +
{{Modparm|debug|Turn on debugging||0 (off)|integer}}
  
cat /proc/bus/input/devices
+
===== dvb_usb_dib0700 =====
 +
{{Modparm|force_lna_activation|Force the activation of LNAs (Low Noise Amplifier), if applicable for the device||0 (automatic/off)|integer}}
 +
{{Modparm|dvb_usb_dib0700_ir_proto|Set IR protocol|0&#61;NEC, 1&#61;RC5, 2&#61;RC6|1|integer}}
 +
{{Modparm|debug|Set debugging level|1&#61;info, 2&#61;fw, 4&#61;fwdata, 8&#61;data|0 (none)|integer (bitmap)}}
  
For example:
+
===== dvb_usb =====
 +
{{Modparm|debug|Set debugging level|1&#61;info, 2&#61;xfer, 4&#61;pll, 8&#61;ts, 16&#61;err, 32&#61;rc, 64&#61;fw, 128&#61;mem, 256&#61;uxfer|0 (none)|integer (bitmap)}}
 +
{{Modparm|disable_rc_polling|Disable remote control polling||0 (enabled)|integer}}
 +
{{Modparm|force_pid_filter_usage|Force all DVB USB devices to use a PID filter, if any||0 (disabled)|integer}}
  
I: Bus=0003 Vendor=2040 Product=9950 Version=0100
+
===== dvb_core =====
N: Name="IR-receiver inside an USB DVB receiver"
+
{{Modparm|dvb_net_debug|Enable debug messages||0 (disabled)|integer}}
P: Phys=usb-0000:07:01.2-1/ir0
+
{{Modparm|frontend_debug|Turn on frontend core debugging||0 (off)|integer}}
S: Sysfs=/class/input/'''input4'''
+
{{Modparm|dvb_shutdown_timeout|Wait ''n'' seconds after <tt>close()</tt> before suspending hardware||0|integer}}
U: Uniq=
+
{{Modparm|dvb_force_auto_inversion|Set whether <tt>INVERSION_AUTO</tt> is forced on||0 (off)|integer}}
H: Handlers=kbd '''event4'''  
+
{{Modparm|dvb_override_tune_delay|Wait ''n'' milliseconds for lock after a tuning attempt||0|integer}}
B: EV=3
+
{{Modparm|dvb_powerdown_on_sleep|Turn LNB power off on sleep||1 (enabled)|integer}}
B: KEY=14afc336 284284d00000000 0 480058000 219040000801 9e96c000000000 90020000000ffd
+
{{Modparm|cam_debug|Enable verbose debug messages||0 (off)|integer}}
 +
{{Modparm|debug|Turn on debugging||0|integer}}
 +
{{Modparm|dvbdev_debug|Turn on device debugging||0 (off)|integer}}
  
In this example, the remote control gives output into <tt>/dev/input/event4</tt>.
+
===== dibx000_common =====
 +
{{Modparm|debug|Turn on debugging||0 (off)|integer}}
  
The event number depends on your particular system and can vary.
+
{{RemoteControlSupport}}
  
Eventually this event number can even vary at every reboot.
+
==== Keys repeated twice ====
 +
But there is still the problem of the key repeats for it, so that each keypress will be repeated twice. The patches, as mentioned above, may not work, but a workaround is possilbe. It is described in http://ubuntuforums.org/showthread.php?p=4253678
  
You could create a new udev rule in <tt>/etc/udev/rules.d/65-persistent-hauppauge.rules</tt>.
+
Simply add <tt>config = echo " > /dev/null</tt> before the main config in .mythtv/lircrc or .lircrc
  
KERNEL=="input*", ATTRS{name}=="IR-receiver inside an USB DVB receiver", SYMLINK+="input/dvb-ir"
+
  begin
 +
  prog = mythtv
 +
  button = Mute
 +
  '''config = echo " > /dev/null'''
 +
  config = |
 +
  ...
 +
  end
  
This would make the Hauppauge receiver always always be linked to '''<tt>/dev/input/dvb-ir</tt>'''.
+
So each 2nd keypress will be suppressed. This works in some application but not others (e.g. vlc).
  
But Linux systems runing recent udev will automatically create non-varying names, a nicer and automatic way of providing a stable input event name:
+
Alternatively there is a patch for the kernel driver that solves it, it can be found [http://javierarias.wordpress.com/2008/07/01/hauppauge-wintv-nova-t-stick-y-mando-a-distancia-funcionando-%C2%A1por-fin/comment-page-1/#comment-44 here].
  
$ ls -la /dev/input/by-path/
+
Finally if that doesn't work and you have the silver remote (A415-HPG-WE-A
total 0
+
) then changing the lircd.conf line as follows can prevent the duplicate key presses. This has the side-effect of disabling key repeats for the remote entirely. Change
drwxr-xr-x 2 root root 140 2008-02-07 20:31 .
+
<tt>toggle_bit_mask 0x80000000</tt>
drwxr-xr-x 4 root root 280 2008-02-07 20:31 ..
+
to
lrwxrwxrwx 1 root root  9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.0-event-kbd -> ../event1
+
<tt>toggle_bit_mask 0x00000000</tt>
lrwxrwxrwx 1 root root  9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.1-event-mouse -> ../event2
+
lrwxrwxrwx 1 root root  9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.1-mouse -> ../mouse1
+
lrwxrwxrwx 1 root root  9 2008-02-07 20:31 '''pci-4-1--event-ir -> ../event4'''
+
lrwxrwxrwx 1 root root  9 2008-02-07 20:31 platform-pcspkr-event-spkr -> ../event3
+
  
LIRC will use it without needing a special kernel module. use the dev/input driver and specify the input event device in <tt>/etc/lirc/hardware.conf</tt>:
+
Note: do not try to comment out (using #) any line in this file, or lirc won't work anymore.
  
# /etc/lirc/hardware.conf
+
Do NOT do this:
#
+
# Arguments which will be used when launching lircd
+
LIRCD_ARGS=""
+
+
#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=true
+
+
# Run "lircd --driver=help" for a list of supported drivers.
+
DRIVER="'''dev/input'''"
+
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
+
# automatically used instead
+
DEVICE="'''/dev/input/by-path/pci-4-1--event-ir'''"
+
MODULES=""
+
+
# Default configuration files for your hardware if any
+
LIRCD_CONF="/etc/lirc/lircd.conf"
+
LIRCMD_CONF=""
+
  
Here is a proper <tt>lircd.conf</tt>:
+
  #toggle_bit_mask 0x80000000
 +
  toggle_bit_mask 0x00000000
  
#
+
Replace the original line instead.
# brand:                      Hauppauge
+
# model no. of remote control: 45 buttons Snowboard Shape Silver over Black
+
#
+
+
begin remote
+
+
  name  hauppauge-45-snowboard
+
  bits          16
+
  eps            30
+
  aeps          100
+
+
  one            0    0
+
  zero            0    0
+
  pre_data_bits  16
+
  pre_data      0x1
+
  gap          199999
+
  toggle_bit      0
+
+
+
      begin codes
+
          Go                      0x0162
+
          Power                    0x0074
+
          TV                      0x0179
+
          Videos                  0x0189
+
          Music                    0x0188
+
          Pictures                0x00E2
+
          Guide                    0x016D
+
          Radio                    0x0181
+
          ArrowUp                  0x0067
+
          ArrowLeft                0x0069
+
          OK                      0x0160
+
          ArrowRight              0x006A
+
          ArrowDown                0x006C
+
          BackExit                0x009E
+
          Menu                    0x008B
+
          VolumeUp                0x0073
+
          VolumeDown              0x0072
+
          PrevCh                  0x016B
+
          Mute                    0x0071
+
          ChannelUp                0x0192
+
          ChannelDown              0x0193
+
          Record                  0x00A7
+
          Rewind                  0x00A8
+
          SkipBack                0x0195
+
          Play                    0x00CF
+
          Pause                    0x0077
+
          Stop                    0x0080
+
          Fwdwind                  0x00D0
+
          SkipFwd                  0x0197
+
          1                        0x0002
+
          2                        0x0003
+
          3                        0x0004
+
          4                        0x0005
+
          5                        0x0006
+
          6                        0x0007
+
          7                        0x0008
+
          8                        0x0009
+
          9                        0x000A
+
          *                        0x0037
+
          0                        0x000B
+
          #                        0x0029
+
          Red                      0x018E
+
          Green                    0x018F
+
          Yellow                  0x0190
+
          Blue                    0x0191
+
      end codes
+
+
end remote
+

Latest revision as of 13:24, 8 May 2010

Making it Work (generic for all dib0700)

This page is a Template that is included by a couple of dib0700 based devices.

On the left in the toolbox there is a link called What links here. Use it to find the product pages that include this template.

If you have product specific information, please include it on the product page.

See TerraTec Cinergy T USB XXS for an example of how to do this.

Firmware

August 21, 2008 - New firmware file fixing the last cause for i2c errors and disconnects and providing a new, more modular i2c request formatting.

You will need the dvb-usb-dib0700-1.20.fw firmware file in /lib/firmware or the relevant place for your distribution.

You may need to change the name of the file to dvb-usb-dib0700-1.10.fw or create a link until the driver code reflects that change.

For archival purposes: dvb-usb-dib0700-1.10.fw firmware file

August 29,2008 - Issues with Firmware 1.20. Some issues have been found with the latest version of the firmware. Users may wish to continue to use 1.10 unless they have patched their v4l-dvb code with dib0700_new_i2c_api.patch.

November 15,2008 - Issues with Firmware 1.20.

  • The above mentioned dib0700_new_12c_api.patch is not available discretely but is now rolled into the mercurial drivers
  • dvb-usb-dib0700-1.20.fw firmware file is now stable for reception, but remote control functionality is broken; any key press is repeated until the next key is pressed. The only way to get remote control functionality presently is to roll back to 1.10 firmware and suffer the occasional disconnect.
  • The mercurial drivers have been changed so they now load 1.20 firmware. To revert to 1.10 firmware you need to rename your firmware file to dvb-usb-dib0700-1.20.fw or provide a link of that name.
  • To avoid spurious remote control signals with 1.20 firmware, you need to edit /etc/modprobe.d/options or from Ubuntu onwards /etc/modprobe.d/options.confand add:
options dvb_usb disable-rc-polling=1

November 28,2008 - i2c errors. Changes were made to the remote control drivers on November 16,2008 to correct the repeat key problem. The card is generally stable for dual tuner reception and remote control function with Firmware 1.20.

November 10,2009 - mt2060 I2C write failed. Possible regression of a driver bug raised against Ubuntu running 2.6.27-14 and 2.6.31-2.17 causing mt2060 I2C errors in MythTV useage with firmware 1.20. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/397696 Recommend check the kernel extensions listed here for Low Noise Activation and rc_polling are loaded with correct config file name for your distribution, EIT listings information is turned off until a suitable delay (500ms-1000ms)is added to a single card (not both) and the card has correctly been added to the database as two tuners (no additional NULL entries) in the mythtv recordcard table.

Drivers

It requires the dib0700 driver. Just use Mercurial by following the How to Obtain, Build and Install V4L-DVB Device Drivers instructions.

Forcing the activation of LNAs (Low Noise Amplifier)

You may have to force LNA to get this card working:

In /etc/modprobe.d/options add:

options dvb_usb_dib0700 force_lna_activation=1

Disabling the remote control sensor

You may want to disable the remote control sensor if you are using another one and want to avoid error messages in the logs:

In /etc/modprobe.d/options add:

options dvb_usb disable_rc_polling=1

All relevant kernel modules options

In /etc/modprobe.d/options add:

options [module name] [option name]=[setting]

Get the parameters list using

modinfo [name of kernel module]

The debug values are bit fields, with each bit representing a different category. Add values to turn on multiple debugging categories.

dib3000mc
debug
Turn on debugging
Values: integer
Default: 0 (off)
buggy_sfn_workaround
Enable work-around for buggy SFNs
Values: integer
Default: 0 (disabled)
mt2060
debug
Turn on debugging
Values: integer
Default: 0 (off)
dvb_usb_dib0700
force_lna_activation
Force the activation of LNAs (Low Noise Amplifier), if applicable for the device
Values: integer
Default: 0 (automatic/off)
dvb_usb_dib0700_ir_proto
Set IR protocol
Values: integer 0=NEC, 1=RC5, 2=RC6
Default: 1
debug
Set debugging level
Values: integer (bitmap) 1=info, 2=fw, 4=fwdata, 8=data
Default: 0 (none)
dvb_usb
debug
Set debugging level
Values: integer (bitmap) 1=info, 2=xfer, 4=pll, 8=ts, 16=err, 32=rc, 64=fw, 128=mem, 256=uxfer
Default: 0 (none)
disable_rc_polling
Disable remote control polling
Values: integer
Default: 0 (enabled)
force_pid_filter_usage
Force all DVB USB devices to use a PID filter, if any
Values: integer
Default: 0 (disabled)
dvb_core
dvb_net_debug
Enable debug messages
Values: integer
Default: 0 (disabled)
frontend_debug
Turn on frontend core debugging
Values: integer
Default: 0 (off)
dvb_shutdown_timeout
Wait n seconds after close() before suspending hardware
Values: integer
Default: 0
dvb_force_auto_inversion
Set whether INVERSION_AUTO is forced on
Values: integer
Default: 0 (off)
dvb_override_tune_delay
Wait n milliseconds for lock after a tuning attempt
Values: integer
Default: 0
dvb_powerdown_on_sleep
Turn LNB power off on sleep
Values: integer
Default: 1 (enabled)
cam_debug
Enable verbose debug messages
Values: integer
Default: 0 (off)
debug
Turn on debugging
Values: integer
Default: 0
dvbdev_debug
Turn on device debugging
Values: integer
Default: 0 (off)
dibx000_common
debug
Turn on debugging
Values: integer
Default: 0 (off)

Remote control support

Using evdev

As long as the evdev module is loaded, a remote that is recogniced as hid device will be treated as a usb keyboard and this means that you can avoid using lirc.

However, many of the keys on your remote may generate keycodes which are not mapped to anything, by default.

In X you can use xev to find the keycodes and xmodmap to map them to useful symbols. Unfortunately, some keys may generate keycodes that X doesn't recognize at all and the device does not support keymaps, or this would be easy to fix.

Using LIRC

Usually remote controls in linux are managed by the lirc software collection.

To get lirc up and running you need to configure some things.

  • Settings for the hardware
    • Where does lirc get its input from? aka. the DEVICE. E.g. /dev/input/event3
    • How to handle the input? aka. the DRIVER. E.g. devinput
  • Settings for mapping driver output generated by your remote (a bunch of hex numbers) to key names (something like 0..9, Volume+, Next, Record)
  • Settings for mapping key presses to actions (usually located in your .lircrc)
Mythubuntu case

On mythubuntu 10.10, you just have to add this line in /etc/udev/rules.d/65-persistent-hauppauge.rules

SUBSYSTEM=="input", KERNEL=="event*", ATTRS{idVendor}=="2040", ATTRS{idProduct}=="8400", SYMLINK+="lirc0"
Device/driver settings

Find the IR receiver's device by looking in the dmesg output for a line similar to:

input: IR-receiver inside an USB DVB receiver as /class/input/input4

Additionally, the IR receiver will be listed if you execute the command:

cat /proc/bus/input/devices

For example:

I: Bus=0003 Vendor=2040 Product=9950 Version=0100
N: Name="IR-receiver inside an USB DVB receiver"
P: Phys=usb-0000:07:01.2-1/ir0
S: Sysfs=/class/input/input4
U: Uniq=
H: Handlers=kbd event4 
B: EV=3
B: KEY=14afc336 284284d00000000 0 480058000 219040000801 9e96c000000000 90020000000ffd

In this example, the remote control gives output into /dev/input/event4.

The event number depends on your particular system and can vary.

Eventually this event number can even vary at every reboot.

You could create a new udev rule in /etc/udev/rules.d/65-persistent-hauppauge.rules.

KERNEL=="event*", ATTRS{name}=="IR-receiver inside an USB DVB receiver", SYMLINK+="input/dvb-ir"

This would make IR receivers handled by the usb_dvb framework always always be linked to /dev/input/dvb-ir.

But Linux systems running recent udev will automatically create non-varying names, a nicer and automatic way of providing a stable input event name:

$ ls -la /dev/input/by-path/
total 0
drwxr-xr-x 2 root root 140 2008-02-07 20:31 .
drwxr-xr-x 4 root root 280 2008-02-07 20:31 ..
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.0-event-kbd -> ../event1
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.1-event-mouse -> ../event2
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-0000:00:1a.1-usb-0:2:1.1-mouse -> ../mouse1
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 pci-4-1--event-ir -> ../event4
lrwxrwxrwx 1 root root   9 2008-02-07 20:31 platform-pcspkr-event-spkr -> ../event3

LIRC will use it without needing a special kernel module. use the dev/input (or devinput. Check this with the command "lircd --device=help".) driver and specify the input event device in /etc/lirc/hardware.conf

# /etc/lirc/hardware.conf
#
# Arguments which will be used when launching lircd
LIRCD_ARGS=""

#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=true

# Run "lircd --driver=help" for a list of supported drivers.
DRIVER="dev/input"
# If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0 will be
# automatically used instead
REMOTE_DEVICE="/dev/input/by-path/pci-4-1--event-ir"
MODULES=""

# Default configuration files for your hardware if any
LIRCD_CONF="/etc/lirc/lircd.conf"
LIRCMD_CONF=""

If you have REMOTE and TRANSMITTER sections in your hardware.conf file, they should look like this:

#Chosen Remote Control
REMOTE="Terratec Cinergy DT USB XS Diversity"
REMOTE_MODULES=""
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="/dev/input/by-path/pci-1-5-event-ir"
REMOTE_LIRCD_CONF="/etc/lirc/lircd.conf"
REMOTE_LIRCD_ARGS=""
#Chosen IR Transmitter
TRANSMITTER="None"
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
Remote key setup

See device specific section below or try [1].


Sample .lircrc

A sample .lircrc can be found LircrcExample here.

Keys repeated twice

But there is still the problem of the key repeats for it, so that each keypress will be repeated twice. The patches, as mentioned above, may not work, but a workaround is possilbe. It is described in http://ubuntuforums.org/showthread.php?p=4253678

Simply add config = echo " > /dev/null before the main config in .mythtv/lircrc or .lircrc

 begin
  prog = mythtv
  button = Mute
  config = echo " > /dev/null
  config = |
  ...
 end

So each 2nd keypress will be suppressed. This works in some application but not others (e.g. vlc).

Alternatively there is a patch for the kernel driver that solves it, it can be found here.

Finally if that doesn't work and you have the silver remote (A415-HPG-WE-A ) then changing the lircd.conf line as follows can prevent the duplicate key presses. This has the side-effect of disabling key repeats for the remote entirely. Change toggle_bit_mask 0x80000000 to toggle_bit_mask 0x00000000

Note: do not try to comment out (using #) any line in this file, or lirc won't work anymore.

Do NOT do this:

 #toggle_bit_mask 0x80000000
 toggle_bit_mask 0x00000000

Replace the original line instead.