[linux-dvb] Re: dvb-bt8xx and dst char major problem ? can't find frontend

[Ilariu Raducan <ilariu@gmail.com>]

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
> 
>