Hi Soeren, Am Mittwoch, den 08.08.2007, 11:42 +0200 schrieb Soeren Sonnenburg: > On Tue, 2007-08-07 at 23:40 +0200, hermann pitton wrote: > > Hi, > > Hi Hermann, > > > Am Dienstag, den 07.08.2007, 09:03 +0200 schrieb Soeren Sonnenburg: > > > On Mon, 2007-08-06 at 00:21 +0200, hermann pitton wrote: > > > > Hi Paolo, > > > > > > > > Am Sonntag, den 05.08.2007, 09:56 +0200 schrieb Paolo Dell'Aquila: > > > > > Hallo, I'm writing here becuase I need some informations about the > > > > > Asus P7131 Hybrid (1043:4876, board: ASUSTeK P7131 Hybrid > > > > > [card=112,autodetected]). > > > > > > > > > > 1. > > > > > Which is the newest firmware for this board? I downloaded the > > > > > "revision 29" from lifeview, is this the right one? > > > > > > > > latest available for download, as far as I know. > > > > > > how does one find out which firmware revision one is using? I am asking > > > as I have severe stability issues (the card works for a couple of hours > > > then at some point cold freezes the system). Note that with the other > > > budget card this setup works fine (uptime months...). > > > > see your dmesg. The tda1004x reports revision 20. Try to get 29. > > At least I'm not aware of other such reports yet. Especially not for > > DVB-T usage. > > strange, I could not convince tda1004x to load the lifeview firmware > (obtained via the get_dvb_firmware script > Documentation/dvb/get_dvb_firmware ) although placed > in /lib/firmware/dvb-fe-tda10046.fw . > > Looking at tda10046_fwupload() in > linux/drivers/media/dvb/frontends/tda1004x.c I found a couple of > > if (tda1004x_check_upload_ok(state) == 0) > return 0; > > checks, which occur before firmware load (and were always triggered). > That is why I got stuck at firmware 20. It now correctly says: > > tda1004x: found firmware revision 29 -- ok sorry, I forgot to tell, that you need a _cold_ boot. If ever possible a firmware reload is avoided, because firmware runs independent from kernel. Could be even a complete OS without having licensing issues this way. [snip] > > > You should not need any saa7134 options, but you might try with saa7134 > > driver latency=32 or 64, maybe also in the BIOS I guess, since you have > > 16MHz PCI speed currently. > > Latency is already 64, but I don't understand why I should have only > 16Mhz PCI speed? Look at your dmesg, PCI latency 16 was reported. Good Luck, Hermann _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
