Hi! > > My big box refuses to load the firmware with all kernel config > > files, I tried. Furthermore it looks like the kernel config > > file can crash the box, when "scan -v -c" is started, > > although everything looks good... > > Do you mix up things here? > At least the behaviour was not so good sometimes; then I changed the kernel; then I loaded the modules again; then I tried my test program... At least I can say, that my system does not run as stable as I would like it... > The kernel config file is a totally different thing. > And again: you need an initial config file for scan! > Ok > > My small box crashes with every kernel config file, I > > tried under debian linux. With SuSE 8.1 it worked > > better... But there was no firmware upload, too. What > > should I do (in all cases there was a firmware file > > available (e. g.: > Is that true? > I remember you have a 2.6.11 kernel running. please try the > following: I assume the kernel dvb drivers are installed. > - If you have an old base distribution, > the dvb device ids might be > wrong (/dev/dvb/adapter0/*) They need to be 212 now. > I know. I used the MAKEDEVS script of the DVB drivers CVS version... > - watch the kernel messages (tail -f /var/log/messages) > Yup! > - do a "modprobe firmware-class" > - do a "modprobe budget-av" (you might need to load the tda1004x > module separately) > - do a tzap -c <any valid channels.conf> <station> > in the kenel log, the last message is (what i remember by > heart) > : waiting for firmware upload > tzap should give you a continuous log of the channel > decoder status > Ok. I think I have to wait until 2005-05-23 (then the test signal starts...). I thought already the scan program would cause the firmware upload. -Arne __________________________________ Do you Yahoo!? Yahoo! Mail - Find what you need with new enhanced search. http://info.mail.yahoo.com/mail_250
