Hi again, On Tue, 23 Mar 2004 18:34:32 +0000 Andrew de Quincey wrote: > > Firstly, I have managed to find a short-term solution to the problem. When > > I add the following line to my modules.conf, the frontend becomes rather > > stable upon a cold boot: > > > > above budget-core grundig_29504-401 > > > > If I replace that line with something else appropriate, the DVB stuff fails > > instantly on my box upon VDR initialisation, requiring a reboot. > > Ah great thanks, I'll have a look. > > What happens if you (without the modules.conf line) try: > modprobe grundig_29504-401 > wait for a minute > then run VDR... does that have the same problem? If so, it has to be a timing > issue. Okay I deleted all the lines from modules.conf except: probeall /dev/dvb budget alias /dev/dvb/* /dev/dvb After a brief amount of power-off (60 secs), I rebooted to find these modules loaded (presumably due to alias, probeall and devfs): budget 4544 0 budget_core 5572 1 budget dvb_core 57300 2 budget,budget_core crc32 3840 1 dvb_core saa7146 15460 2 budget,budget_core ttpci_eeprom 2304 1 budget_core I then modprobe'd grundig_29504_401, then issued 'sleep 60' to make sure I paused long enough. VDR then starts up OK after those steps. Should I try something else (remove "alias" and "probeall" lines?) or leave the PC off for a longer period to try and invoke the "crash"? Cheers, John
Attachment:
pgp00004.pgp
Description: PGP signature