Hello,
I am in the process of trying to get the same card running under gentoo x86.
Things I have tried/noted so far.
If you have a 'newer' version of the card it will have a "Zarlink
ZL10353 DVB-T" Frontend.
This is not supported by Kernel 2.6.17, you will need to get the
v4l-dvb src from http://linuxtv.org/hg/v4l-dvb and complile that.
I have compiled them by only enabling DVB in the kenel config no
drivers. Then compiling the SRC noted above.
I also had the same USB error you are showing. I got rid of it by not
using the internal USB cable provided and using the external. The card
now wakes up. See below.
mythbox Linux video capture interface: v2.00
mythbox cx2388x dvb driver version 0.0.6 loaded
mythbox CORE cx88[0]: subsystem: 18ac:db50, board: DViCO FusionHDTV
DVB-T Dual Digital [card=44,autodetected]
mythbox TV tuner 4 at 0x1fe, Radio tuner -1 at 0x1fe
mythbox ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 5
mythbox PCI: setting IRQ 5 as level-triggered
mythbox ACPI: PCI Interrupt 0000:02:07.2[A] -> Link [LNKD] -> GSI 5
(level, low) -> IRQ 5
mythbox cx88[0]/2: found at 0000:02:07.2, rev: 5, irq: 5, latency: 64,
mmio: 0xfd000000
mythbox cx88[0]/2: cx2388x based dvb card
mythbox DVB: registering new adapter (cx88[0]).
mythbox DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)...
mythbox ACPI: PCI Interrupt 0000:00:13.2[A] -> Link [LNKD] -> GSI 5
(level, low) -> IRQ 5
mythbox ehci_hcd 0000:00:13.2: EHCI Host Controller
mythbox ehci_hcd 0000:00:13.2: new USB bus registered, assigned bus number 1
mythbox ehci_hcd 0000:00:13.2: irq 5, io mem 0xfea00000
mythbox ehci_hcd 0000:00:13.2: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
mythbox usb usb1: configuration #1 chosen from 1 choice
mythbox hub 1-0:1.0: USB hub found
mythbox hub 1-0:1.0: 6 ports detected
mythbox usb 1-2: new high speed USB device using ehci_hcd and address 2
mythbox usb 1-2: configuration #1 chosen from 1 choice
mythbox dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in cold
state, will try to load a firmware
mythbox dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw'
mythbox usbcore: registered new driver dvb_usb_cxusb
mythbox usb 1-2: USB disconnect, address 2
mythbox dvb-usb: generic DVB-USB module successfully deinitialized and
disconnected.
mythbox usb 1-2: new high speed USB device using ehci_hcd and address 3
mythbox usb 1-2: configuration #1 chosen from 1 choice
mythbox dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in warm state.
mythbox dvb-usb: will pass the complete MPEG2 transport stream to the
software demuxer.
mythbox DVB: registering new adapter (DViCO FusionHDTV DVB-T Dual USB).
mythbox DVB: registering frontend 1 (Zarlink ZL10353 DVB-T)...
mythbox input: IR-receiver inside an USB DVB receiver as /class/input/input2
mythbox dvb-usb: schedule remote query interval to 150 msecs.
mythbox dvb-usb: DViCO FusionHDTV DVB-T Dual USB successfully
initialized and connected.
My problem is that I am unable to tune either card. They both show up
proper in /dev/dvb/adapter0 /dev/dvb/adapter1 but when I try to tune I
get the following on the PCI tuner:
mythbox ~ # dvbscan -a0 /usr/share/dvb/scan/dvb-t/au-sydney_north_shore
scanning /usr/share/dvb/scan/dvb-t/au-sydney_north_shore
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 226500000 1 3 9 3 1 1 0
initial transponder 177500000 1 2 9 3 1 2 0
initial transponder 191625000 1 3 9 3 1 1 0
initial transponder 219500000 1 3 9 3 1 1 0
initial transponder 571500000 1 2 9 3 1 2 0
initial transponder 578500000 1 2 9 3 1 2 0
tune to:
226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
tune to:
226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning
failed)
WARNING: >>> tuning failed!!!
and on the USB:
mythbox ~ # dvbscan -a1 /usr/share/dvb/scan/dvb-t/au-sydney_north_shore
scanning /usr/share/dvb/scan/dvb-t/au-sydney_north_shore
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder 226500000 1 3 9 3 1 1 0
initial transponder 177500000 1 2 9 3 1 2 0
initial transponder 191625000 1 3 9 3 1 1 0
initial transponder 219500000 1 3 9 3 1 1 0
initial transponder 571500000 1 2 9 3 1 2 0
initial transponder 578500000 1 2 9 3 1 2 0
tune to:
226500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
tune to:
177500000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_2_3:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
WARNING: filter timeout pid 0x0011
WARNING: filter timeout pid 0x0000
WARNING: filter timeout pid 0x0010
tune to:
191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
tune to:
191625000:INVERSION_AUTO:BANDWIDTH_7_MHZ:FEC_3_4:FEC_AUTO:QAM_64:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_16:HIERARCHY_NONE (tuning
failed)
WARNING: >>> tuning failed!!!
Any help would be appreciated.
Thanks and good luck Daniel.
Mark
Quoting Daniel Deptford <linuxtv@xxxxxxxxxxxxxxxxxx>:
Hi again - sorry I should have searched and seen chris pascoe's post about
more data. I've replied to him seperately.
So in the meantime I decided to do some tinkering, and install gentoo AMD64
on my machine. Using linux-2.6.17.6 vanilla again, I get this crash logged
in my dmesg:
http://www.rafb.net/paste/results/fRWff882.html
I'm not sure why it can't find the frontend (I've configured it to build all
available frontends), but the callstack of the driver crash is
interesting(!)
Cheers
Daniel
On 23/07/06, Daniel Deptford <linuxtv@xxxxxxxxxxxxxxxxxx> wrote:
Hi there,
I have the aforementioned board installed on a gentoo system, using the
vanilla 2.6.17.6 sources. In case you don't know, its a PCI+USB combo
board and it is connected to my motherboard via an internal USB connector.
I've managed to finally get all the drivers recognisning my board, but
dvbscan moans at me (using both -a0 and -a1) with:
MediaPC dvb-t # dvbscan uk-CrystalPalace
scanning uk-CrystalPalace
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 505833333 0 3 9 1 0 0 0
>>> tune to:
505833333:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to:
505833333:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
(tuning failed)
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
I thought it might have been a range thing, so i found a definition of a
transmitter about 2 miles away:
MediaPC dvb-t # cat uk-Guildford
# Carlton / LWT Region Guildford
# T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy
T 833000000 8MHz 3/4 NONE QAM16 2k 1/32 NONE
Still no dice:
MediaPC dvb-t # dvbscan uk-Guildford
scanning uk-Guildford
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 833000000 0 3 9 1 0 0 0
>>> tune to:
833000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TR
ANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE
WARNING: >>> tuning failed!!!
>>> tune to:
833000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_3_4:FEC_AUTO:QAM_16:TR
ANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE (tuning failed)
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
dmesg log:
MediaPC firmware # dmesg |grep "dvb"
cx2388x dvb driver version 0.0.5 loaded
cx88[0]/2: cx2388x based dvb card
dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in cold state, will try
to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-bluebird-01.fw'
usbcore: registered new driver dvb_usb_cxusb
dvb-usb: generic DVB-USB module successfully deinitialized and
disconnected.
dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software
demuxer.
dvb-usb: schedule remote query interval to 150 msecs.
dvb-usb: DViCO FusionHDTV DVB-T Dual USB successfully initialized and
connected.
checking the devices are present:
MediaPC firmware # ls /dev/dvb
adapter0 adapter1
MediaPC firmware # ls /dev/dvb/adapter0/
demux0 dvr0 frontend0 net0
MediaPC firmware #
I'm completely at a loss. Before trying the board out under linux, I used
the vista beta media center and that did find the channels alright (but I
plan on using MythTV).
I would really appreciate any help you could give me!
Thanks
Daniel
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
_______________________________________________
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
