Mailing List archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[linux-dvb] Re: dvb-bt8xx and dst char major problem ? can't find frontend FOUND WHERE IT COMES FROM !
On Sat, 09 Oct 2004 19:19:47 +0200, Pierre <nunux-dev@wanadoo.fr> wrote:
>
>
> Manu Abraham wrote:
>
> >On Sat October 9 2004 8:09 pm, Pierre wrote:
> >
> >
> >>Pierre wrote:
> >>
> >>
> >>>Ilariu Raducan wrote:
> >>>
> >>>
> >>>>Hi,
> >>>>
> >>>>I have the same problem. I get EXACTLY the same output.
> >>>>If you boot in Windows (with the driver installed) and soft reboot in
> >>>>Linux then it will work.
> >>>>I think the i2c hardware is not properly initialized by the linux
> >>>>driver, while for a soft reboot
> >>>>from windows the i2c remains initialized by windows driver.
> >>>>My card in Twinhan VisionDTV Sat-CI (1030a)
> >>>>
> >>>>Regards,
> >>>>Lale
> >>>>
> >>>>
> >>>>On Thu, 7 Oct 2004 12:29:33 +0400, Manu Abraham <manu@kromtek.com>
> >>>>
> >>>>wrote:
> >>>>
> >>>>
> >>>>>On Wed October 6 2004 9:45 pm, Pierre wrote:
> >>>>>
> >>>>>
> >>>>>>Hi
> >>>>>>
> >>>>>>I'm not sure i'm doing it right. I'm using a 2.6.8-1 kernel and
> >>>>>>linuxtv-dvb-1.1.1 with PCTV SAT CI card.
> >>>>>>
> >>>>>>Here is what i'm loading :
> >>>>>>modprobe videodev
> >>>>>>modprobe bttv card=113 i2c_hw=1
> >>>>>>modprobe dvb-core dvbdev_debug=1 dvb_frontend_debug=1
> >>>>>>modprobe v4l1-compat debug=1
> >>>>>>modprobe dst dst_verbose=1 dst_debug=1
> >>>>>>modprobe dvb-bt8xx debug=1
> >>>>>>
> >>>>>>dmesg is :
> >>>>>>
> >>>>>>Linux video capture interface: v1.00
> >>>>>>i2c_core: Unknown parameter `i2c_debug'
> >>>>>>bttv: driver version 0.9.15 loaded
> >>>>>>bttv: using 8 buffers with 2080k (520 pages) each for capture
> >>>>>>bttv: Bt8xx card found (0).
> >>>>>>ACPI: PCI interrupt 0000:01:06.0[A] -> GSI 18 (level, high) -> IRQ 18
> >>>>>>bttv0: Bt878 (rev 17) at 0000:01:06.0, irq: 18, latency: 32, mmio:
> >>>>>>0xe0000000
> >>>>>>bttv0: detected: Pinnacle PCTV SAT CI [card=113], PCI subsystem ID is
> >>>>>>11bd:0026
> >>>>>>bttv0: using: Twinhan DST + clones [card=113,insmod option]
> >>>>>>bttv0: gpio: en=00000000, out=00000000 in=00f584fd [init]
> >>>>>>bttv0: using tuner=4
> >>>>>>bttv0: add subdevice "dvb0"
> >>>>>>bt878: AUDIO driver version 0.0.0 loaded
> >>>>>>bt878: Bt878 AUDIO function found (0).
> >>>>>>ACPI: PCI interrupt 0000:01:06.1[A] -> GSI 18 (level, high) -> IRQ 18
> >>>>>>bt878(0): Bt878 (rev 17) at 01:06.1, irq: 18, latency: 32, memory:
> >>>>>>0xe0001000
> >>>>>>dst: Unknown parameter `dst_check_ci'
> >>>>>>
> >>>>>>
> >>>>> something wrong here. dst will not read card type from CARD.
> >>>>>maybe a char
> >>>>>major problem ?
> >>>>>
> >>>>>
> >>>>>
> >>>>>>dvb_bt8xx: enumerating available bttv cards...
> >>>>>>dvb_bt8xx: identified card0 as DST DVB-S
> >>>>>>attach: checking "bt878 #0 [hw]"
> >>>>>>find by pci: checking "bt878 #0 [hw]"
> >>>>>>attach: "bt878 #0 [hw]", to card 0
> >>>>>>DVB: registering new adapter (DST).
> >>>>>>dst_attach: check ci
> >>>>>>bt878 find by dvb adap: checking "DST"
> >>>>>>write_dst writing 0x00 0x06 0x00 0x00 0x00 0x00 0x00 0xfa
> >>>>>>write_dst: write_dst error (err == -5, len == 0x08, b0 == 0x00)
> >>>>>>write_dst: write_dst error (err == -5, len == 0x08, b0 == 0x00)
> >>>>>>write_dst: write_dst error (err == -5, len == 0x08, b0 == 0x00)
> >>>>>>write_dst: write_dst error (err == -5, len == 0x08, b0 == 0x00)
> >>>>>>
> >>>>>>
> >>>>> Yes, will not write to card ..
> >>>>>
> >>>>>
> >>>>>
> >>>>>>dst_check_ci: write not successful, maybe no card?
> >>>>>>
> >>>>>>
> >>>>> maybe a char major problem
> >>>>>
> >>>>>
> >>>>>
> >>>>>>DVB: register adapter0/demux0 @ minor: 4 (0x04)
> >>>>>>DVB: register adapter0/dvr0 @ minor: 5 (0x05)
> >>>>>>DVB: register adapter0/net0 @ minor: 7 (0x07)
> >>>>>>
> >>>>>>The ci is not very important. But when i try to launch the scan dvb
> >>>>>>apps
> >>>>>>it says :
> >>>>>>
> >>>>>>scanning /usr/local/addons/dvb-s/Astra-19.2E
> >>>>>>using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> >>>>>>main:1882: FATAL: failed to open '/dev/dvb/adapter0/frontend0': 19 No
> >>>>>>such device
> >>>>>>
> >>>>>>
> >>>>> dst could not find what frontend it is
> >>>>>
> >>>>>
> >>>>>
> >>>>>>The dst module is the frontend isn't it ? It's loaded :
> >>>>>>lsmod :
> >>>>>>Module Size Used by
> >>>>>>dvb_bt8xx 6404 0
> >>>>>>dst 14092 0
> >>>>>>bt878 9536 2 dvb_bt8xx,dst
> >>>>>>v4l1_compat 14084 0
> >>>>>>dvb_core 59156 2 dvb_bt8xx,dst
> >>>>>>tuner 19280 0
> >>>>>>bttv 149100 3 dvb_bt8xx,bt878
> >>>>>>video_buf 18372 1 bttv
> >>>>>>i2c_algo_bit 9352 1 bttv
> >>>>>>v4l2_common 5376 1 bttv
> >>>>>>btcx_risc 4296 1 bttv
> >>>>>>i2c_core 20160 4 dvb_bt8xx,tuner,bttv,i2c_algo_bit
> >>>>>>videodev 8000 1 bttv
> >>>>>>
> >>>>>>Is this a char major pb or am I simply doing it badly ?
> >>>>>>
> >>>>>>
> >>>>> Looks like so .. If not the recent changes in the CVS
> >>>>>might've broken the
> >>>>>driver. The previous versions, before the 2.6.8 stuff work fine though.
> >>>>>
> >>>>>Manu
> >>>>>
> >>>>>
> >>>Hi Ilariu
> >>>Thanks for info, but i'm not using windows at all., but a home made
> >>>linux box. If i even find the solution, i'll keep u informed.
> >>>
> >>>cheers
> >>>
> >>>Pierre
> >>>
> >>>
> >>Does not come from a char major pb !
> >>
> >>Lale, don't you have nforce based motherboard ?
> >>
> >>The PCTV SAT CI works perfectly under a VIA chipset MB. I have 2
> >>machines. I swapped the HD on the VIA MB and used exactly the same setup
> >>
> >>: and it works fine!!! For the NFORCE MB the pb comes from a bad driving
> >>
> >>of the chipset. Next step is to find how to fix the pb on the NFORCE MB.
> >>
> >>
> >
> > Some chipsets have different timings or bad design.. Could be a
> >motherboard/chipset. Therefore the delay setup in the frontend routine
> >initialization and even while running would be upset..
> >
> > One can try fiddling around the delay values and find out ...
> >
> >The same problem can exist on some overclocked Motherboards also.
> >
> >Regarding the recent frontend changes, one can expect broken modules while
> >things are revamped... If it does not work out please do try an earlier
> >version before the 2.6.8.1 episode...
> >
> > There is some problem with my mail going out to linuxtv mailinglist...
> >Somedays back i had sent a mail, but two days later it got bounced back...
> >Now also the same thing is happening
> >
> >Regards,
> >Manu
> >
> >
> >>I'll find out and keep you both informed.
> >>
> >>Regards
> >>
> >>Pierre
> >>
> >>
> >
> >
> >
> Hi Manu
> Thanks for getting back to me.
>
> I've already tried it. patched (v4l and dvb-kerneKernel-2.4-26) - 2.6.7
> Same thing.
>
> ... tricky pb ! The final setup will work under a nforce MB chipset (
> barebone shutlle)
>
> Pierre
>
> --
>
> -------------------------------------------------
> Guess What, THE ..
> -------------------------------------------------
>
> REAL PORTION of Microsoft Windows code:
>
> while (memory_available) {
> eat_major_portion_of_memory (no_real_reason);
> if (feel_like_it)
> make_user_THINK (this_is_an_OS);
> gates_bank_balance++;
> ;
> while (memory_microsofted) {
> system_response;
> cout blow_this_OS_away;
> cout install linux++;
>
> -------------------------------------------------
>
>
This week-end I opened the PC and took a look at the card. It is not
VP1030a, it is a VP1030C blue circuit card.
I still believe there is someting with i2c initialization. The i2c
enable is done using some gpio pin.
Probably on my card that gpio pin differs from some other card versions.
Regards,
Ilariu
Home |
Main Index |
Thread Index