[mythtv-users] FC5 and Fusion DVB-T Dual Digital

[Shanon Mulley]

Ummmmm. No. I dont really have any ideas from here. I'm kind of a
linux newbie myself - I just thought I'd help you out as your system
was so damn similar to mine (OS and tv card). But I dont think I can
help you from here.

It seems that our DMESG outputs are identical, except for the one line
that you previously identified:
dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual USB'

But besides that everything seems fine. What are you using to hook it
up (the USB bit) to your machine? I was using internal cables at
first, but I switched to an external cable as I had problems with
internal.

On 7/27/06, Anthony Goddard <anthony at bondimaging.com> wrote:
> Hi There,
> Thanks for the info.
>
> Currently "dmesg | grep dvb-usb" returns the following:
>
> [mythtv at mythtv ~]$ dmesg | grep dvb-usb
> 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'
> 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: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual USB'
> dvb-usb: schedule remote query interval to 150 msecs.
> dvb-usb: DViCO FusionHDTV DVB-T Dual USB successfully initialized and
> connected.
>
>
> So far, all I've done to the box (after installing FC5) is:
>
> 1)yum upgrade (about 700mb of updates)
> 2)yum install kernel-devel, yum install kernel-doc
> 3)ran the firmware script, and placed the .fw file in /lib/firmware
> 4)added the repo's from the wilson guide (atrmps, freshrpms)
> 5)ran yum install mythtv-suite
> 6)ran yum upgrade again which updated things from the mythtv-suite
> install (about 10mb I think)
>
>
>
>
> Any ideas? :-(
>
>
> Cheers!
> Anthony
>
> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org
> [mailto:mythtv-users-bounces at mythtv.org] On Behalf Of Shanon Mulley
> Sent: Thursday, 27 July 2006 7:46 AM
> To: Discussion about mythtv
> Subject: Re: [mythtv-users] FC5 and Fusion DVB-T Dual Digital
>
> Gee, I really dont know if it is the same...
>
> And no - for me that was about it. It started working at that point.
>
> At what point do you get that message? When I run "dmesg | grep dvb-usb"
> I get the following:
> ---DMESG START---
> 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'
> 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.
> ---DMESG END---
>
> How much of that do you get?
>
> On 7/26/06, Anthony Goddard <anthony at bondimaging.com> wrote:
> > Hi, Thanks for the info. I have run what you suggested, and it
> downlaoded the firmware file for me. Is running the firmware install
> like this any different from running wget
> http://linuxtv.org/firmware/dvb-usb-bluebird.fw?
> >
> > The firmware is now in /lib/firmware, and it recognises it on bootup,
> but I still have this in my dmesg:
> >
> > dvb-usb: no frontend was attached by 'DViCO FusionHDTV DVB-T Dual USB'
> >
> > In /dev/dvb/ I have "adaptor0"
> >
> > Is there anything else I need to install to get the frontend attached?
> >
> > Cheers!
> >
> > Anthony
> >
> >
> > -----Original Message-----
> > From: mythtv-users-bounces at mythtv.org on behalf of Shanon Mulley
> > Sent: Wed 7/26/2006 9:28 PM
> > To: Discussion about mythtv
> > Subject: Re: [mythtv-users] FC5 and Fusion DVB-T Dual Digital
> >
> > Well this is embarressing. It seems my notes at home arnt as thorough
> > as I thought they were.
> >
> > I'll try to do it from memory:
> > install kernel-doc (yum install kernel-doc) Now under
> > /usr/share/doc/kernel-doc-2.6.17/Documentation/dvb/, you should have
> > the file get_dvb_firmware. Make this file executable (chmod 777
> > get_dvb_firmware), run it with the bluebird option (./get_dvb_firmware
>
> > bluebird), and follow the instructions given.
> > The firmware file should end up in /lib/firmware/
> >
> > Thats about it really - the bit sticking point for me was working out
> > I needed to install kernel-doc to get the script to get the firmware.
> >
> > I hope this helps.
> >
> > On 7/26/06, Shanon Mulley <shanonmulleyster at gmail.com> wrote:
> > > Kevin,
> > >
> > > from my very limited experience with this, the firmware for the USB
> > > portion of the card is retreived by a script. This script comes
> > > along with kernel-doc (or something). If you dont have kernel-doc
> > > installed, then there is no script. My installation of FC5 did not
> > > install kernel-doc by default.
> > >
> > > On 7/26/06, Kevin Hayes <wondecla at tpg.com.au> wrote:
> > > > On Wed, 26 Jul 2006 14:45:19 +1000 "Anthony Goddard"
> > > > <anthony at bondimaging.com> wrote:
> > > >
> > > > > Hi All,
> > > > > I have put together the following setup:
> > > > >
> > > > > 3Ghz Pentium-D D/core
> > > > > Fedora Core 5 32bit - Kernel 2.6.17-1.2157_FC5smp Nvidia FX6200
> > > > > with TurboCache (using s-video out) Fusion DVB-T Dual Digital
> > > > > tuner (the Australia / Europe one)
> > > > >
> > > > >
> > > > > I can install mythtv-suite through yum, but I run into all sorts
>
> > > > > of problems with building the dvb drivers after that.
> > > > > Basically I install mercurial, in the /root directory I run "hg
> > > > > clone http://linuxtv.org/hg/v4l-dvb"
> > > > > then inside the v4l-dvb folder I run make.
> > > > >
> > > > > I keep running into all sorts of errors when trying to run this.
> > > > >
> > > > > Before I get into too many specifics, I was just wondering if
> > > > > there's anyone out there with a similar setup who knows if I
> > > > > need to do anything different to get it working.
> > > > > I've been working off Jarrad Wilson's guide as well as
> > > > > http://mythtv.org/wiki/index.php/DVICO-Ultraview_Install_in_Aust
> > > > > ralia
> > > > >
> > > > > I have also installed the firmware (.fw file) before, but had
> > > > > errors with frontend not initializing still I have had Myth
> > > > > running fine on the same box running FC4.
> > > > >
> > > > >
> > > > > Because I played around a lot and thought I might have done more
>
> > > > > damage than good, I've formatted and reinstalled FC5 at this
> > > > > stage, so all i have done is a yum upgrade & a yum install
> > > > > Kernel-Devel, and nothing further, and this is my dmesg. (I have
>
> > > > > only pasted the part that look relevant).
> > > > >
> > > > > Hope someone can help!
> > > > >
> > > > > Cheers,
> > > > > anthony
> > > > >
> > > > >
> > > > > hub 3-0:1.0: 2 ports detected
> > > > > usb 1-5: new high speed USB device using ehci_hcd and address 2
> > > > > ACPI: PCI Interrupt 0000:00:1d.2[C] -> GSI 18 (level, low) ->
> > > > > IRQ 177
> > > > > PCI: Setting latency timer of device 0000:00:1d.2 to 64 uhci_hcd
>
> > > > > 0000:00:1d.2: UHCI Host Controller uhci_hcd 0000:00:1d.2: new
> > > > > USB bus registered, assigned bus number 4 uhci_hcd 0000:00:1d.2:
>
> > > > > irq 177, io base 0x0000b400 usb usb4: configuration #1 chosen
> > > > > from 1 choice hub 4-0:1.0: USB hub found hub 4-0:1.0: 2 ports
> > > > > detected cx2388x v4l2 driver version 0.0.5 loaded usb 1-5:
> > > > > configuration #1 chosen from 1 choice cx2388x dvb driver version
>
> > > > > 0.0.5 loaded
> > > > > ACPI: PCI Interrupt 0000:00:1d.3[D] -> GSI 16 (level, low) ->
> > > > > IRQ 169
> > > > > PCI: Setting latency timer of device 0000:00:1d.3 to 64 uhci_hcd
>
> > > > > 0000:00:1d.3: UHCI Host Controller uhci_hcd 0000:00:1d.3: new
> > > > > USB bus registered, assigned bus number 5 uhci_hcd 0000:00:1d.3:
>
> > > > > irq 169, io base 0x0000b800 usb usb5: configuration #1 chosen
> > > > > from 1 choice hub 5-0:1.0: USB hub found hub 5-0:1.0: 2 ports
> > > > > detected
> > > > > ACPI: PCI Interrupt 0000:04:00.0[A] -> GSI 20 (level, low) ->
> > > > > IRQ 233 CORE cx88[0]: subsystem: 18ac:db50, board: DViCO
> > > > > FusionHDTV DVB-T Dual Digital [card=44,autodetected] TV tuner 4
> > > > > at 0x1fe, Radio tuner -1 at 0x1fe
> > > > > dvb-usb: found a 'DViCO FusionHDTV DVB-T Dual USB' in cold
> > > > > state, will try to load a firmware
> > > > > dvb-usb: did not find the firmware file.
> > > > > (dvb-usb-bluebird-01.fw) Please see linux/Documentation/dvb/ for
>
> > > > > more details on firmware-problems. (-2)
> > > > > dvb_usb_cxusb: probe of 1-5:1.0 failed with error -22
> > > > > cx88[0]/0: found at 0000:04:00.0, rev: 5, irq: 233, latency: 32,
> mmio:
> > > > > 0xe5000000
> > > > > cx88[0]/0: registered device video0 [v4l2]
> > > > > cx88[0]/0: registered device vbi0
> > > > > ACPI: PCI Interrupt 0000:04:00.2[A] -> GSI 20 (level, low) ->
> > > > > IRQ 233
> > > > > cx88[0]/2: found at 0000:04:00.2, rev: 5, irq: 233, latency: 32,
> mmio:
> > > > > 0xe6000000
> > > > > cx88[0]/2: cx2388x based dvb card
> > > > > cx88[0]: frontend initialization failed
> > > > > cx88[0]/2: cx8802_stop_dma
> > > > > cx88-dvb: probe of 0000:04:00.2 failed with error -1 cx2388x
> > > > > blackbird driver version 0.0.5 loaded usb 5-1: new full speed
> > > > > USB device using uhci_hcd and address 2 usb 5-1: configuration
> > > > > #1 chosen from 1 choice
> > > > > usbcore: registered new driver dvb_usb_cxusb
> > > > > ACPI: PCI Interrupt 0000:00:1b.0[A] -> GSI 16 (level, low) ->
> > > > > IRQ 169
> > > > > PCI: Setting latency timer of device 0000:00:1b.0 to 64
> > > > > hw_random hardware driver 1.0.0 loaded
> > > > > parport: PnPBIOS parport detected.
> > > > > parport0: PC-style at 0x378, irq 7 [PCSPP,TRISTATE]
> > > > >
> > > > >
> > > > Hi, have been playing around with this card for a few weeks now,
> > > > and have it working successfully on a Win2K partition also on a
> > > > MythDora partition out of the box
> > > >
> > > > I can see from your log that it is not finding the firmware file,
> > > > I'm currently trying to get it detected on a Slackware  10.2
> > > > partition where i got the same message, i googled for it and put
> > > > it in /lib/firmware after that it was detected correctly, and all
> > > > the error messages above disappeared, and it seems to be correctly
>
> > > > detected, except it is not detected in the myth-setup.
> > > >
> > > > That is where i'm now, it works very well for my on the MythDora
> > > > partition,
> > > >
> > > > hth
> > > >
> > > > --
> > > > Kevin Hayes
> > > >
> > > > _______________________________________________
> > > > mythtv-users mailing list
> > > > mythtv-users at mythtv.org
> > > > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> > > >
> > >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
> > _______________________________________________
> > mythtv-users mailing list
> > mythtv-users at mythtv.org
> > http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >
> >
> >
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>