Hello, I don't really understand what you want us to do now. Our problem is (or was) that our cards first were present with 13d0:2102 and then "magically" changed their IDs to (the correct) 13d0:2103. When the card identifies itself as 2102 the kernel module don't find the hardware. (And even if I added the 2102 it wasn't working as seen in my very first message: http://www.linuxtv.org/pipermail/linux-dvb/2006-November/014564.html) We are only wondering why Technisat have done this ID-switch. Our two cards (Michaels and mine) are now working for us but for a new user this is not self-explanatory. This I think applies only for the revision 2.3. I have not seen this 2102 thing again with my card. (Probably a message which is displayed if a 13d0:2102 is detected should be displayed to a user that he should try reinserting the card (at least reboot) or "wait until it gets the 2103" and should consider to get help on this mailing list.) Merry Christmas Bernhard Am Samstag, 23. Dezember 2006 21:30 schrieb Yvan Gosset: > Hello. > > As I remember for my little study of the existing linux code directory about > b2c2 driver, PC-IDs of a PCI card are not used at this time for drivers for > FlexCop: all frontend is tried when loading modules drivers. > (you can understand this info: modules for hardware can be loaded succefully > even hardware is not present, but it's not a problem at all for the present > hardware) > > PCI-IDs is not the most important information: > you need to know the version of the Flexcop chip, the demodulator chips (and > less?: the tuner=pll). > You can use debug parameter with insmod or modprobe > to see more details. > > For example: > "make unload > sync > /sbin/modprobe i2c-core > /sbin/insmod ./dvb-core.ko #frontend_debug=1 > /sbin/insmod ./dvb-pll.ko > /sbin/insmod ./mt312.ko > /sbin/insmod ./mt352.ko > /sbin/insmod ./bcm3510.ko > /sbin/insmod ./nxt200x.ko > /sbin/insmod ./lgdt330x.ko > /sbin/insmod ./stv0299.ko > /sbin/insmod ./compat_ioctl32.ko > /sbin/insmod ./v4l1-compat.ko > /sbin/insmod ./v4l2-common.ko > /sbin/insmod ./videodev.ko > /sbin/insmod ./video-buf.ko > /sbin/insmod ./stv0297_cs2.ko debug=1 > ##debug:set debugging level (1=info,2=i2c,4=calc (|-able)). (int) > /sbin/insmod ./b2c2-flexcop.ko debug=3 > ##debug:set debug level (1=info,2=tuner,4=i2c,8=ts,16=sram,32=reg...) > /sbin/insmod ./b2c2-flexcop-pci.ko > ##debug:set debug level (1=info,2=regs,4=TS,8=irqdma (|-able)). (int) > " > > " > /sbin/insmod ./b2c2-flexcop.ko debug=3 > " > debug info and i2c messages.. (see sources) > 1=info,2=i2c, 3=1+2 > > > At soon, Yvan. > > Le Saturday 23 December 2006 11:55, Bernhard Huafbauer a écrit : > > For the records: I have also shut down my system removed a > > AVM Fritzcard, inserted this Skystar2 and booted. > > > > (If this occurs only in this combination a solution could be to > > remove the old card, boot und shutdown one times and then > > insert the Skystar2?) > > > > Regards > > Bernhard > > > > Am Samstag, 23. Dezember 2006 09:51 schrieb Michael Joswig: > .... > > _______________________________________________ > linux-dvb mailing list > linux-dvb@xxxxxxxxxxx > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
