VDR package feedback

[Andrew Stevens]

Hi VDR packagers,

Recently updated and bumped into a number of further issues.

Configuration:

'testing', 2.6.8 kernel from kernel packages

Hauppage 'Technotrend' DVB board

1.	Module loading

The /usr/sbin/runvdr script appears to try to figure out the required 
front-end modules to load from the lsmod output for the dvb_core.   This 
basically doesn't work as these are *NOT* depend's of dvb_core.  I.e. unless
you've already loaded the right modules it won't load the right modules :-(

The list I use for my Technotrend board is:

MODULES="alps_tdmb7 alps_tdlb7 grundig_29504-401 grundig_29504-491 stv0299 
ves1820 tda1004x mt312 input evdev dvb-ttpci"

The situation is a real pain ... I've never figured out how to get the right 
set of front-ends loaded automatically. I always ended up simply grabbing the 
list from 'insmod' target in the DVB driver sources.

Maybe I've missed something?

2.	Permissions

Moving to running as 'vdr' - excellent. However, there is a small problem with 
the integrated IR remote receiver: to load the right keycode map to the 
driver vdr has to write to /proc/av7110_ir.    The simplest method to make 
this possible would be to simply chown this to vdr:video before starting vdr 
in /usr/sbin/runvdr.

3.	A hint for 2.6.x DVB newbies.

You absolutely need hotplugging active and you need to install the firmware 
in /usr/lib/hotplug/firmware.  Details in <kernel 
sources>/Documentation/dvb/firmware.txt

This one had me tearing my hair for hours as the error message from the driver 
is not in the least useful and the firmware hotplug agent does not seem to 
log useful information into the syslog.  Sigh...


cheers, thanks for work!

	Andrew