[linux-dvb] Re: Twinhan Vision Plus & WinFast DTV1000-T

Sigmund Augdal Helberg sigmund at snap.tv
Mon Mar 6 10:15:27 CET 2006


On Mon, 2006-03-06 at 18:58 +1000, Matt Pratt wrote:
> On 2/27/06, Matt Pratt <mattpratt.au at gmail.com> wrote:
>         
>         Non-working case:
>         
>         bttv0: Bt878 (rev 17) at 0000:02:0c.0, irq: 169, latency: 132,
>         mmio: 0xf9000000
>         bttv0: using:  *** UNKNOWN/GENERIC ***  [card=0,autodetected] 
>         bttv0: gpio: en=00000000, out=00000000 in=00fffffe [init]
>         
>         
>         Which seems to indicate that the pci_read_config_word() of
>         PCI_SUBSYSTEM_ID and PCI_SUBSYSTEM_VENDOR_ID is failing.
>         
>         Does this indicate larger PCI problems, like a conflict
>         between the boards?
>         
>         Can some ACPI fiddling help here?
> 
> 
> So even lspci -x was showing that the Subsystem Id and Subsustem
> Vendor Id were being cleared to zeros in the PCI config space of this
> card. But only when the two cards were in the machine. No amount of
> slot swapping seemed to make a difference. Upgrade of motherboard
> firmware made no difference. noacpi, lacpi, pci=routeirq, pci=noacpi
> made no difference. Went to the effort of putting the cards into
> another machine. They just worked. Eventually tried acpi=off (which I
> thought noacpi would have done the same thing) and they both worked! 
These cards often does not initialize correctly at bootup, this is
usually fixed by forcing the driver to treat these cards as twinhan
cards (by using modprobe bttv card=0x71,0x71 (repeate for the number of
cards you have)), then make sure the rdc8820_reset function of dst.c is
called. This may happen by default or not depending on which driver
tree/revition you are using. If it is not happening loading the driver
twice usually works.
summary:
modprobe bttv card=0x71,0x71
modprobe dvb_bt8xx
rmmod dvb_bt8xx
modprobe dvb_bt8xx

note that when the cards are initialized once they will work over
several reboots even without this magic being done.

Can you check that acpi=off really makes a difference, and that it
wasn't just a matter of the reset being triggered and the next boot
being a warm reboot? Do this by cold booting the trublesome computer and
then use acpi=off when booting. I do not belive any kernel booting
parameter has any influence on this, as it seems to happen long before
the kernel gets started (this can be confirmed by looking at the led on
the card (if your card has a led on it)).

Regards

Sigmund
> 
> Thanks for your help Manu.
> 
> Matt
> 
> 
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb




More information about the linux-dvb mailing list