On 09 Aug 2005 "Christoph Hermanns" Christoph.Hermanns@web.de wrote:
Am Sun, 7 Aug 2005 20:08:17 +0000 (UTC) schrieb Stefan Huelswitt s.huelswitt@gmx.de:
On 07 Aug 2005 "Christoph Hermanns" Christoph.Hermanns@web.de wrote:
How can i speed up the starting of the dvb driver and vdr ?
If you're using a FF dvb card, loading the firmware takes some time.
You can speed up this (or actually hide some time) if you don't let runvdr load the driver but rather create an own startup script to load the driver and run this one very first after boot i.e. S01. You have to background (&) the make insmod call.
Is this correct:
- Comment out the start of dvb driver in runvdr:
# Load driver if it hasn't been loaded already: #if [ $LSMOD -eq 0 ] ; then # (cd $DVBDIR; make insmod) # fi
- Create new dvb-start.sh script (is the & at the right place ?):
# Load driver if it hasn't been loaded already: if [ $LSMOD -eq 0 ] ; then (cd $DVBDIR; &make insmod) fi
No, won't work that way. One problems is, that if you background the make insmod, the boot process continues while the firmware is loaded. If the rest of the boot script is fast, you may end with the situation that vdr starts up before the make insmod is finished.
So I do to load the driver (may be a own script. I do it in boot directly) (you have to adjust the dvb driver path):
( touch /tmp/dvb-insmod; \ cd /usr/local/source/dvb; make insmod; rm /tmp/dvb-insmod ) &
In runvdr I check for the existance of the trigger file:
while [ -a /tmp/dvb-insmod ]; do sleep1 done
This way the vdr startup is delayd until the insmod is finished. (may be there are mor sofisticated method to do this, but it works).
Question: If the dvb-driver hangs, will the restart be unaffected from this change ? (I think so, but i'll ask to be sure ;-)
No, the restart won't be affected.
Regards.
Am Tue, 9 Aug 2005 19:17:04 +0000 (UTC) schrieb Stefan Huelswitt s.huelswitt@gmx.de:
On 09 Aug 2005 "Christoph Hermanns" Christoph.Hermanns@web.de wrote:
Am Sun, 7 Aug 2005 20:08:17 +0000 (UTC) schrieb Stefan Huelswitt s.huelswitt@gmx.de:
On 07 Aug 2005 "Christoph Hermanns" Christoph.Hermanns@web.de wrote:
How can i speed up the starting of the dvb driver and vdr ?
If you're using a FF dvb card, loading the firmware takes some time.
You can speed up this (or actually hide some time) if you don't let runvdr load the driver but rather create an own startup script to load the driver and run this one very first after boot i.e. S01. You have to background (&) the make insmod call.
Is this correct:
- Comment out the start of dvb driver in runvdr:
# Load driver if it hasn't been loaded already: #if [ $LSMOD -eq 0 ] ; then # (cd $DVBDIR; make insmod) # fi
- Create new dvb-start.sh script (is the & at the right place ?):
# Load driver if it hasn't been loaded already: if [ $LSMOD -eq 0 ] ; then (cd $DVBDIR; &make insmod) fi
No, won't work that way. One problems is, that if you background the make insmod, the boot process continues while the firmware is loaded. If the rest of the boot script is fast, you may end with the situation that vdr starts up before the make insmod is finished.
So I do to load the driver (may be a own script. I do it in boot directly) (you have to adjust the dvb driver path):
( touch /tmp/dvb-insmod; \ cd /usr/local/source/dvb; make insmod; rm /tmp/dvb-insmod ) &
In runvdr I check for the existance of the trigger file:
while [ -a /tmp/dvb-insmod ]; do sleep1 done
This way the vdr startup is delayd until the insmod is finished. (may be there are mor sofisticated method to do this, but it works).
I've tried this and it works with the trigger file, but it's about 10 seconds slower than without checking the existing of the trigger file. Strange...don't know....
Greetings, Christoph
On Tuesday 16 August 2005 19:13, Christoph Hermanns wrote:
Am Tue, 9 Aug 2005 19:17:04 +0000 (UTC) schrieb Stefan Huelswitt
[...]
In runvdr I check for the existance of the trigger file:
while [ -a /tmp/dvb-insmod ]; do sleep1 done
This way the vdr startup is delayd until the insmod is finished. (may be there are mor sofisticated method to do this, but it works).
I've tried this and it works with the trigger file, but it's about 10 seconds slower than without checking the existing of the trigger file. Strange...don't know....
Because you (probably) only need modules that are loaded at the beginning of the list.
IMO it is worth to play around with the insmod.sh script (the one that is used when calling "make insmod"). Remove the modules that are not required in the "start" case. Start from botton, e.g. by removing half of all modules.
Kind regards, Stefan
Stefan Huelswitt wrote:
[...] One problems is, that if you background the make insmod, the boot process continues while the firmware is loaded. If the rest of the boot script is fast, you may end with the situation that vdr starts up before the make insmod is finished.
Ideally vdr would start up anyways and detect new/removed devices at runtime. I don't know how useful vdr currently is in conjunction with USB adaptors for example.
cu Ludwig
-
Christoph Hermanns -
Ludwig Nussel -
s.huelswitt＠gmx.de -
Stefan Taferner