Manu Abraham wrote: > Andreas Vinsander wrote: >> Hi! >> >> I recently subscribed to this maillist and have since done some reading >> up on the posts. And found this from the "Mantis >> VP-1027/VP-1033/VP-1034/VP-2033/VP-3033"-thread: >> > > > Sorry for the late reply .. > >> -------------- >> Subject: Re: Mantis VP-1027/VP-1033/VP-1034/VP-2033/VP-3033 >> From: Manu Abraham >> Date: Sat, 07 Oct 2006 05:11:49 -0700 >> >> Lauri Tischler wrote: >>> Does this apply also to these cards >>> - Twinhan DTV TER-CI 3030 Mantis DVB-T >>> - Twinhan DTV TER-CI 3040 DVB-T PCI >>> - Twinhan DTV SAT-CI 1030 DVB-S PCI >> No. The dst module supports these cards. > > > Apologies, a mistake from my side. The 3030 Mantis DVB-T is a Mantis > based card. Sorry for that stupid mistake. > > >> Manu >> ---------------- >> >> I have one of those Twinhan DTV TER-CI 3030 Mantis DVB-T pci cards, but >> the dst module (from gentoo package v4l-dvb-hg-0.1-r2, which seems to >> pull the source via hg from the dvb repository) doesn't seem to >> recognize the card. dmesg and logfiles shows that the modules are loaded >> but they don't find a bt8x8 chip and thus no /dev/dvb/ entries are >> created (udev-103). I have tried the modules supplied by the kernel >> gentoo-sources-2.6.18-r2 (do I need to try vanilla 2.6.19-rc5?) as well, >> with the same results. >> >> I am running 64bit Linux on an Athlon64 X2 3800+ stuffed into an ASUS >> M2NPV-VM motherboard. Both PCI slots are used, one for the Twinhan card >> and the other for an atheros based WiFi card (which works alright btw). >> >> I provide some lspci & pcimodules output down below, what else can I do >> to find out what goes wrong here? Is it possible that Manu missed >> something when he stated that this card was supported by the dst module? >> >> >> # lspci -vv >> ... >> 04:08.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI >> Bridge Controller [Ver 1.0] (rev 01) >> Subsystem: Twinhan Technology Co. Ltd Unknown device 0024 >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- >> ParErr- Stepping- SERR- FastB2B- >> Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- >> <TAbort- <MAbort- >SERR- <PERR- >> Latency: 32 (2000ns min, 63750ns max) >> Interrupt: pin A routed to IRQ 5 >> Region 0: Memory at fdaff000 (32-bit, prefetchable) [size=4K] > > > This is a Mantis based card supported by the Mantis driver and not the dst. > >> ... >> >> # lspci -nv >> 04:08.0 0480: 1822:4e35 (rev 01) >> Subsystem: 1822:0024 >> Flags: bus master, medium devsel, latency 32, IRQ 5 >> Memory at fdaff000 (32-bit, prefetchable) [size=4K] >> >> # pcimodules >> nvidia >> i2c-nforce2 >> snd-hda-intel >> ath_pci >> >> No sign of any DVB drivers compliant with the card at 04:08.0 >> > > > This card VP-3030 would use the MT352 driver rather than the ZL10353 > driver as compared to the VP-3033 > Argh, stupid mistake (confusing model numbers) VP-30300 has a ZL10353, not a MT352 (the older version has a MT352, another model number) So it just boils down as to find why the ZL10353 responds differently in this case. Regards, Manu _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
