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.
You can further speed up things, if you don't use seperate startup scripts but rather one single boot script.
Scanning IDE bus e.g. for DVD-ROM blocks my machine for several seconds. So I compiled IDE driver as a module (doing network boot, so no boot drive). I call modprobe ide-detect very late in the boot process.
Regards.
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:
1. 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
2. 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
Question: If the dvb-driver hangs, will the restart be unaffected from this change ? (I think so, but i'll ask to be sure ;-)
Regards, Christoph
On Tuesday 09 August 2005 19:00, Christoph Hermanns wrote:
Am Sun, 7 Aug 2005 20:08:17 +0000 (UTC) schrieb Stefan Huelswitt
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
You only moved the loading, but still load everything. What has to be done is to only load those drivers that are really required. Have a look at the insmod.sh script that comes in $DVBDIR, and remove all unneeded drivers from the "start" stage in the script.
Other methods like using the kernel module loader sound technically superior to me, but it might be not that easy for you, and the outcome (and boot time) is probably the same.
--Stefan
Am Wed, 10 Aug 2005 07:31:36 +0200 schrieb Stefan Taferner taferner@kde.org:
[...]
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
You only moved the loading, but still load everything. What has to be done is to only load those drivers that are really required. Have a look at the insmod.sh script that comes in $DVBDIR, and remove all unneeded drivers from the "start" stage in the script.
Yes, i had the same idea some time ago. But i have no insmod.sh script in $DVBDIR ?!?! I've been running Klaus' 2.4'er reference dvb-driver from 26.12.2004 . I have only a nexus 2.1 dvb card in my vdr pc. I think there is an alps bsrv2 frontend on my dvb card, but im not sure. When i delete all the other frontends, i also see the random stripes when the driver starts and then a black screen, but when vdr starts i've only seen this error on the console:
no primary device found - using first device! invalid primary device number:1
Have i delete too much ? And how can i figure out which frontend resists on my nexus ?
Regards, Christoph
-
Christoph Hermanns -
s.huelswitt＠gmx.de -
Stefan Taferner