VDR package feedback

[Thomas Schmidt]

--h31gzZEtNLTqOjlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hi

Sorry that it took so long for a response, but i was very busy with my
exams in the last weeks.

* Andrew Stevens schrieb am 06.02.05, um 19:40 Uhr:
> 1.	Module loading
>=20
> The /usr/sbin/runvdr script appears to try to figure out the required=20
> front-end modules to load from the lsmod output for the dvb_core.   This=
=20
> basically doesn't work as these are *NOT* depend's of dvb_core.  I.e. unl=
ess
> you've already loaded the right modules it won't load the right modules :=
-(

Well, runvdr does not try to figure out which modules should be loaded
for a working dvb-configuration, it would be very difficult to do such
a thing. (Normally hotplug should manage this, i guess the best
solution would be to improbe hotplug to handle dvb-drivers correct.)=20

Runvdr just checks which dvb-modules are loaded and in the case vdr=20
exits abnormal runvdr just tries to reload all these modules. (It is=20
not uncommon that the dvb-drivers hang sometimes, so this practice is
needed from time to time.) In the case that there are not any loaded
dvb-modules runvdr just ries to load the module "dvb", which may be an
alias for the right modules.

> The situation is a real pain ... I've never figured out how to get the ri=
ght=20
> set of front-ends loaded automatically. I always ended up simply grabbing=
 the=20
> list from 'insmod' target in the DVB driver sources.
>=20
> Maybe I've missed something?

You should just configure the module-init-tools, in my setup
TechnoTrend FF Rev. 1.5) stv0299 is the right frontend-module and i=20
created the file /etc/modprobe.d/dvb with the following content:

alias dvb dvb-ttpci
install dvb-ttpci /sbin/modprobe stv0299; /sbin/modprobe --ignore-install d=
vb-ttpci

This means that the module stv0299 is loaded together with dvb-ttpci.

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

The best location for this command would be /etc/default/vdr, this
file is marked as configfile and will not be overwritten when you
upgrade the vdr-package.

> 3.	A hint for 2.6.x DVB newbies.
>=20
> You absolutely need hotplugging active and you need to install the firmwa=
re=20
> 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 d=
river=20
> is not in the least useful and the firmware hotplug agent does not seem t=
o=20
> log useful information into the syslog.  Sigh...

Ok, you are right in this point, it is a little bit difficult to find
this out for newbies, i guess we should add a note to the documentation=20
of the vdr-package.


Regards,
Thomas

--=20
Thomas Schmidt
thomas.schmidt@in.stud.tu-ilmenau.de

--h31gzZEtNLTqOjlF
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCGJvDc9+NqwoydlIRAq2NAKDU4PFG8JulDIpAG9RgulHM8BgKSACfRwWZ
SLGGGVf6uiZds5185nB9BUc=
=CYAh
-----END PGP SIGNATURE-----

--h31gzZEtNLTqOjlF--