Hello Gregor, I remember I also had problems on my Dual Core system, where the bt878 driver load may fail while it is loaded in parallel with the bttv driver. I added this also in my modprobe.conf: install bt878 /sbin/modprobe bttv; /sbin/modprobe --ignore-install bt878; /sbin/modprobe dst; /sbin/modprobe dst_ca; /sbin/modprobe dvb-bt8xx This line forces the loading of all the drivers in the proper order. Hope this helps... Kind Regards, Remy 2008/1/6, Gregor Fuis <gujs.lists@xxxxxxxxx>: > Remy Bohmer wrote: > > Hello Gregor, > > > > Can you please give me the revision numbers? > > These are listed somewhere on the boards. > > As mentioned before, different revisions are different clones from > > other boards en need a different driver configuration. > > Besides, I do not know if all combinations of different revisions of > > the boards work with 1 driver and generic setting. Maybe with the > > latest changes CityK was talking about, it is possible now? > > > > At first, I would suggest to leave the 'green' board out, and just put > > in the cards of the same revision and get that working, when this > > works you can put back in your 'green' card, and try get that working > > also. > > > > To check which firmware version you have, you can enable the logging > > inside the drivers. > > > > It is good to hear that you do not have a yellow card (rev3) in the > > system, which seems to be the most unstable card of the series. > > > > Luckily you do not need a CAM on these boards, because that part is > > very unstable inside the cards itself, which sometimes require a full > > power off of the system (power cable removed for at least 20 seconds), > > to get the boards reset again and to get them working properly... (in > > fact, if the CAM part of some board is getting into an undefined > > state, this will also result in a unbootable system, because the > > firmware is not behaving properly anymore...) > > > > Note: To work around this reset issue partly, it might be worth trying > > to add these flags to your modprobe.conf: 'options dst dst_addons=32' > > I added this dst_addons option set to 32(=DST_TYPE_HAS_CA) to make > > sure the card is reset on load time of the dst-driver. if omitted, the > > dst driver will not be able to communicate to the card during > > dst_probe() on a cold boot and loading the dst (and dst_ca) driver > > fails. (A soft reboot will load the driver after reboot without > > problems.) > > > > > > Kind Regards, > > > > Remy > > > > The blue colored are version 1.0, but on green colored I can't find > version number anywhere on PCB. I will try to remove some labels, if it > is under. > I replaced green one with other blue card because I have total 5 blue > cards. I wold like to get 4 of the to work for my new mythtv setup. And > then to setup another slave mythtv backend for other two. > > I tried your advice with this lines in /etc/modprobe.d/options > options dvb_core dvb_shutdown_timeout=0 > options bttv i2c_hw=1,1,1,1 card=0x71,0x71,0x71,0x71 > options dst dst_addons=32,32,32,32 > > With these lines I can get to work three cards of 4 (all ver 1.0 and > blue), but I can boot my system just 1/3 times. Other 2/3 of boot > procedures system just hangs. > > Regards, > Gregor > > _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
