DVB-T USB device help

[Jonesy]

As you have the unit open, you might also check the numbers of the other chips on board.

This post seems to imply that certain combinations of chips definitely work ....

They all definitely have an EM2870 and a QT1010. Since the e357 and e359
are known to work, e357 and e359 must also have a ZL10353. I think it
likely that e358 must also have a ZL10353.

http://osdir.com/ml/linux.drivers.em28xx/2007-05/msg00003.html

Interestingly that would make for the exact same specs as my Zarlink devicem which works so thats not viable really.
The print on the other chip is proving next to impossible to read so it could be anything, I'll keep trying on that though.

Here are the last lines of output from dmesg again:

Code: [Select]

em28xx #0: Identified as Kworld 355 U DVB-T (card=42)
em28xx #0:

em28xx #0: The support for this board weren't valid yet.
em28xx #0: Please send a report of having this working
em28xx #0: not to V4L mailing list (and/or to other addresses)

i2c-core: driver [tuner] using legacy suspend method
i2c-core: driver [tuner] using legacy resume method
tuner 1-0062: chip found @ 0xc4 (em28xx #0)
tuner 1-0062: tuner type not set
em28xx #0: v4l2 driver version 0.1.2
tuner 1-0062: tuner type not set
em28xx #0: V4L2 video device registered as video0
usbcore: registered new interface driver em28xx
em28xx driver loaded


[Was_Just19]

I dunno .....  it is weird .......  the device is seen as a video device ..... not a DVB device .....

It is not being correctly recognised, yet indications are that you have the correct drivers loaded .......  unless you can find a different chip number in that thing ....

I am stumped 

[Jonesy]

Ok we have a development on this. I managed to remove the test label and borrow a very powerful magnifying glass.

The other chip appears to be an Intel WJCE6353 described in the data sheet as a Nordig Unified DVB-T COFDM Terrestrial demodulator for PC-TV and hand-held Digital TV

http://download.intel.com/design/celect/datashts/D55752.pdf

So now we know the type of chips on the device...

QT1010
CE6353

I have found a linux driver dvb-usb-dtv5100 for a device with the exact same chipset here: http://royale.zerezo.com/dtv5100/

Then I found it is installed already and so modprobed it, but still the same problem. Not recognized properly and no worky

[Was_Just19]

At this time I would be inclined to edit the modprobe-preload file and comment out all driver entries relating to this and previous devices. Include in that list the em28xx  driver which is apparently being picked up by the device ....   but is this not a driver for v4l devices not dtt devices?  I am getting a bit confused as I have both types of devices here ....  DTT & Video Grabber

Then start again, introducing the different drivers, starting of course with the 5100.

[Jonesy]

At this time I would be inclined to edit the modprobe-preload file and comment out all driver entries relating to this and previous devices. Include in that list the em28xx  driver which is apparently being picked up by the device ....   but is this not a driver for v4l devices not dtt devices?  I am getting a bit confused as I have both types of devices here ....  DTT & Video Grabber

Then start again, introducing the different drivers, starting of course with the 5100.

Ok I commented out all possible entries in modprobe.preload but still the same. I then blacklisted the em28xx to stop it being picked up and the device just wasn't detected. No output in dmesg, nothing. I reinserted the modules starting with the dtv5100 but still no luck. Untill I re-enabled the em28xx module, then the device was picked up again and appeared in dmesg as before with the same error as a v4l device.

I now know the chipset and all the drivers are present so the device would seem to be supported, but no luck. I may give up. I have a sneaking feeling this is either a firmware issue (highly unlikely since this is supposed to be a 'warm' device) or a broken driver package. In which case it's an issue for the Dev's.

[Was_Just19]

At this time I would be inclined to edit the modprobe-preload file and comment out all driver entries relating to this and previous devices. Include in that list the em28xx  driver which is apparently being picked up by the device ....   but is this not a driver for v4l devices not dtt devices?  I am getting a bit confused as I have both types of devices here ....  DTT & Video Grabber

Then start again, introducing the different drivers, starting of course with the 5100.

Ok I commented out all possible entries in modprobe.preload but still the same. I then blacklisted the em28xx to stop it being picked up and the device just wasn't detected. No output in dmesg, nothing. I reinserted the modules starting with the dtv5100 but still no luck. Untill I re-enabled the em28xx module, then the device was picked up again and appeared in dmesg as before with the same error as a v4l device.

I now know the chipset and all the drivers are present so the device would seem to be supported, but no luck. I may give up. I have a sneaking feeling this is either a firmware issue (highly unlikely since this is supposed to be a 'warm' device) or a broken driver package. In which case it's an issue for the Dev's.

Bummer .......  maybe an update at some time will change the situation.

My DTT DVB device does not use the em28xx driver apparently

Code: [Select]

usb 1-2.4.4: new high speed USB device using ehci_hcd and address 9
usb 1-2.4.4: New USB device found, idVendor=15a4, idProduct=9016
usb 1-2.4.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-2.4.4: Product: DVB-T 2
usb 1-2.4.4: Manufacturer: Afatech
usb 1-2.4.4: SerialNumber: 010101010600001
dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in cold state, will try to load a firmware
dvb-usb: downloading firmware from file 'dvb-usb-af9015.fw'
dvb-usb: found a 'Afatech AF9015 DVB-T USB2.0 stick' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (Afatech AF9015 DVB-T USB2.0 stick)
af9013: firmware version:4.95.0.0
DVB: registering adapter 0 frontend 0 (Afatech AF9013 DVB-T)...
tda18218: NXP TDA18218HN successfully identified.
Registered IR keymap rc-empty
input: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2.4/1-2.4.4/rc/rc2/input10
rc2: IR-receiver inside an USB DVB receiver as /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2.4/1-2.4.4/rc/rc2
dvb-usb: schedule remote query interval to 500 msecs.
dvb-usb: Afatech AF9015 DVB-T USB2.0 stick successfully initialized and connected.
Afatech DVB-T 2: Fixing fullspeed to highspeed interval: 10 -> 7
input: Afatech DVB-T 2 as /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2.4/1-2.4.4/1-2.4.4:1.1/input/input11
generic-usb 0003:15A4:9016.0006: input,hidraw3: USB HID v1.01 Keyboard [Afatech DVB-T 2] on usb-0000:00:1d.7-2.4.4/input1

[Jonesy]

Yeah bummer indeed. Seems there are three (four if you count the Peak 203244AGPK device which uses the Afatech AF9015 chip) two of which work out of the box. I chose the third one that doesn't  

Woulda been nice to make it go..

Meanwhile I got the old (but not good) Zarlink device to fall back on.

Thanks for your help mate.

[Was_Just19]

Yeah bummer indeed. Seems there are three (four if you count the Peak 203244AGPK device which uses the Afatech AF9015 chip) two of which work out of the box. I chose the third one that doesn't  

Woulda been nice to make it go..

Meanwhile I got the old (but not good) Zarlink device to fall back on.

Thanks for your help mate.

As you saw above I have a device that identifies itself as an Afatech .......  but it has only been recently supported (kernel 2.6.37) due to its tuner not being supported.

You have the tuner driver for your device, but the device somehow is not properly recognised.

It is strange that the unit is identified as "Kworld 355 U DVB-T (card=42)" and yet is not apparently supported as a DVB-T device.

I can only guess that the device as identified does not have an entry for support.

Unless something along these lines might be possible ......

http://www.spinics.net/lists/linux-media/msg27466.html

Over my head though .....

regards.

[Jonesy]

I've peeled open the windows driver packages and the *.inf references are definitely to em28xx drivers.

Code: [Select]

emBDA.inf -- This file contains installation information for
;                eMPIA USB 2.0 Video Devices EM28xx.
;
;   This installation is for Windows XP and 32-bit Vista.
;
;   Copyright (C) eMPIA Technology, Inc.  2002-2007

So the device is correctly identified and the correct em28xx driver being selected. For some reason the QT1010 driver for the tuner is not being asigned to the device even though the system is detecting the presence of a QT1010 and it knows the QT1010 drivers are available. This must be a driver packaging issue. Do you think it is worth posting a note  in the broken packages thread?.

[Just17]

I've peeled open the windows driver packages and the *.inf references are definitely to em28xx drivers.

Code: [Select]

emBDA.inf -- This file contains installation information for
;                eMPIA USB 2.0 Video Devices EM28xx.
;
;   This installation is for Windows XP and 32-bit Vista.
;
;   Copyright (C) eMPIA Technology, Inc.  2002-2007

So the device is correctly identified and the correct em28xx driver being selected. For some reason the QT1010 driver for the tuner is not being asigned to the device even though the system is detecting the presence of a QT1010 and it knows the QT1010 drivers are available. This must be a driver packaging issue. Do you think it is worth posting a note  in the broken packages thread?.

Did you not say that the QT1010 is used successfully by another device?

If so then it is hardly the fault of the package .......  unless the driver needs that specific device to be enumerated somewhere and it isn't.

Is there any sign of an update to the driver?

[Jonesy]

Ooppss my bad. What I meant to say was package request   

Yes the QT1010 tuner works perfectly on my MSI Mega Sky 55801 (Zarlink) device. Not seen an update unless there is one in the pipeline. Fingers crossed.

[Just17]

Ooppss my bad. What I meant to say was package request   

Yes the QT1010 tuner works perfectly on my MSI Mega Sky 55801 (Zarlink) device. Not seen an update unless there is one in the pipeline. Fingers crossed.

I guess it might be either of the packages, or maybe the kernel, that would require something to be in there to support the device.

Is there anything you found that shows this device working in Linux?

[Jonesy]

I have found references to working devices but no one is saying how they got them working.
I give up on it for now.

Anyway, to make things more interesting, if your still up for the challenge. I have just acquired
another device!.

The device is identified in dmesg as:

Code: [Select]

usb 1-1: new high speed USB device using ehci_hcd and address 4
usb 1-1: New USB device found, idVendor=1b80, idProduct=d395
usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 1-1: Product: usbtv
usb 1-1: Manufacturer: realtek


The chipset is RTL2832U and FC0012 after cracking open the case.


lsusb says its  Bus 001 Device 005: ID 1b80:d395 Afatech

This one is deader than the previous one. It doesn't even get warm, but it works in w1nd0w$
so I know it's not a brick.

But I have a real bad feeling about this one. A quick look suggests there is no rtl2832 kernel module.

[Just17]

      I am beginning to wonder if you are searching for devices that won't work in Linux    

The 1b80:e395  is supported by the Afatech 9013/5/6 packages.

The d395 appears to be different

This seems to hold some hope ......

http://aur.archlinux.org/packages.php?ID=36746&comments=all

PKGBUILD

http://aur.archlinux.org/packages/dvb-usb-rtl2832u-arch/PKGBUILD


https://build.opensuse.org/package/show?package=dvb-usb-rtl2832u&project=home%3Ajvroosmalen%3Abranches%3Ahome%3Apolyconvex

Maybe just a matter of getting the driver packaged?

You should get the output for that device from

lsusb -v   (whould give the verbose output with more details)

It does appear that you will need the Realtek driver mentioned above ..... but at this stage I would be be sure of anything   

regards

[Jonesy]

I've put in a package request to see if it can be added. There is a link to a pre-compiled module that supports the FC0012 tuner with an install shell script which I tested on a caddy drive install I use just for testing and it failed at the last minute due to a missing autoconfig.h file.

Should be a snip for one of the devs to modify.

As for the previous device it seems that there is just  missing support for the QT1010 driver that needs to be
added to the package for that device ID. Don't know who you would contact about that, as you say it's not a broken package, just a weakness in it.