Author Topic: DVB-T USB device help (Read 3404 times)

Jonesy · « **on:** May 16, 2011, 07:27:49 AM »

I have just acquired another DVB-T USB device. It is a Peak 192133agpk. But I just cant get it to work.
Has anyone any help to offer on this device. Modules, drivers, firmware etc so i can get it to work?.

It's quite old by the look of it so I would have thought it was supported, most are these days.

My old Zarlink ZL10353 is also still listed by Kaffeine but not my new 192133agpk. I'm quite hopeless
when it comes to such devices.

I know the vendor ID is eb1a and the device id is e357. According to a search the driver is the em28xx
which modprobe shows to be loaded. For some reason the device does not appear at all in PCC. Not
even as an unknown device!. It works fine on a window box so I know the device is not fried and
lsusb shows it is there and working!!.

lsusb Bus 001 Device 005: ID eb1a:e357 eMPIA Technology
.

Thanx

Was_Just19 · « **Reply #1 on:** May 16, 2011, 10:38:29 AM »

I think it has an em2870 chip and if so the driver required is em28xx ...... along with a newer kernel ..... anything from 2.6.37.19 and later, so one of our 2.6.38 kernels will do fine.

Plug in the device and in a terminal do

dmesg

and copy and paste the last 20 lines or so into your next post.

That should help identify it.

regards.

EDIT
My own saga trying to get a device working that was not yet supported in the kernel ..... there may be some useful info in there if you can spend the time reading all the nonsense

http://www.pclinuxos.com/forum/index.php/topic,83935.0.html

Jonesy · « **Reply #2 on:** May 16, 2011, 05:50:34 PM »

Here is the output from dmesg for the device as requested...

Code: [Select]

usb 1-1: Product: USB 2870 Device
em28xx: New device USB 2870 Device @ 480 Mbps (eb1a:e357, interface 0, class 0)
em28xx #0: chip ID is em2870
em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 57 e3 c0 12 62 40 6a 22 00 00
em28xx #0: i2c eeprom 10: 00 00 04 57 6a 0d 00 00 60 00 00 00 02 00 00 00
em28xx #0: i2c eeprom 20: 54 00 00 00 f0 10 01 00 00 00 00 00 5b 00 00 00
em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00
em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 22 03 55 00 53 00
em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 37 00 30 00 20 00 44 00
em28xx #0: i2c eeprom 80: 65 00 76 00 69 00 63 00 65 00 00 00 00 00 00 00
em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x32317d02
em28xx #0: EEPROM info:
em28xx #0:      No audio on board.
em28xx #0:      500mA max power
em28xx #0:      Table at 0x04, strings=0x226a, 0x0000, 0x0000
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)

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 video1
usbcore: registered new interface driver em28xx
em28xx driver loaded

Was_Just19 · « **Reply #3 on:** May 17, 2011, 03:44:57 AM »

Some information from you might be useful in trying to determine what you are doing and with what .....

what dvb packages have you installed?
what kernel are you using?
what DE are you using?

did you try any of the commands in the thread I linked to? What output did you get from them?

http://www.mjmwired.net/kernel/Documentation/video4linux/CARDLIST.em28xx

That link would seem to indicate the device is supported in the 2.6.38 kernels (#42), if as yet unproved.

Was_Just19 · « **Reply #4 on:** May 17, 2011, 03:56:57 AM »

OK, found the info I think ......

ftp://ftp.eu.kernel.org/pub/scm/linux/kernel/git/jejb/storage-tree/drivers/media/video/em28xx/em28xx-cards.c

According to what I read in that the tuner in your device is

Quote

[EM2870_BOARD_KWORLD_350U] = {
      .name = "Kworld 350 U DVB-T",
      .valid = EM28XX_BOARD_NOT_VALIDATED,
      .tuner_type = TUNER_XC2028,
      .tuner_gpio = default_tuner_gpio,

Code: [Select]

locate xc2028
/lib/modules/2.6.38.2-pclos1.bfs/kernel/drivers/media/common/tuners/tuner-xc2028.ko.gz
/lib/modules/2.6.38.4-pclos1.bfs/kernel/drivers/media/common/tuners/tuner-xc2028.ko.gz

Do as root

modprobe tuner-xc2028

Then check the device again.

regards.

Jonesy · « **Reply #5 on:** May 17, 2011, 06:22:02 AM »

Hi, thanks for your patience with this

Some specs, KDE4 fully updated.
Kernel 2.6.38.2 (updated this morning from 2.6.37.x)

DVB packages:-
dvb-apps
dvbtune
dvb-usb-af9015
libdvbpsi5
libv4l
libdvb

Primary DVB app is Kaffeine.

We have a slight improvement, the card is now identified in dmesg output but not the tuner despite doing modprobe tuner-xc2028. It seems the tuner is an issue and the device is still NOT shown in hardware in PCC at all.

I'm still trawling through all the stuff at the link but frankly it just baffles me even more.

Code: [Select]

em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0x32317d02
em28xx #0: EEPROM info:
em28xx #0:      No audio on board.
em28xx #0:      500mA max power
em28xx #0:      Table at 0x04, strings=0x226a, 0x0000, 0x0000
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)

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

I added tuner-xc2028 to etc/modprobe.preload and rebooted, now I have this output, but still not worky.

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 · « **Reply #6 on:** May 17, 2011, 06:46:19 AM »

When I had tuner trouble the only reliable means of determining the chip used was to open the case and read the numbers from all the likely chips.

Doing that allowed me to be certain of the tuner and to focus on exactly what I needed.

If you can do that it would take any doubt out of it.

Also booting with the unit inserted is not ideal.
I would suggest you reboot without it, run dmesg, plug it in, and run dmesg again.

Post back the additional lines at the end of the dmesg output.
Something *may* be different

regards.

Jonesy · « **Reply #7 on:** May 17, 2011, 07:54:31 AM »

The dmesg output after pluging the device in is the same as my last entry.

Code: [Select]

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

The tuner chip is a Quantec QT 1010....

This one in fact.. http://www.quantek-inc.com/qt1010.html

More here: http://www.linuxtv.org/wiki/index.php/KWorld_DVB-T_355U

The decoder chip must be being correctly identified and the driver loaded. Just the Tuner is a problem
like you seem to have had with yours.

The Quantec QT1010 tuner is the same as in my old Zarlink DVB-T device, so why it doesn't work is a mystery.

Was_Just19 · « **Reply #8 on:** May 17, 2011, 10:11:04 AM »

What does the following command return?

I get nothing

Code: [Select]

[user@Dell ~]$ lsmod | grep qt
[user@Dell ~]$

If yours is the same then you need to load the driver for the tuner - as root -

Code: [Select]

[root@Dell user]# modprobe qt1010
[root@Dell user]# lsmod | grep qt
qt1010                  4685  0
i2c_core               16500  11 qt1010,tda18218,af9013,i2c_i801,nvidia,dvb_usb_af9015,dvb_usb,em28xx,v4l2_common,videodev,tveeprom

After that plug in the device.

You need to be using a newer kernel it seems .....

Code: [Select]

[user@Dell ~]$ locate qt1010
/lib/modules/2.6.38.4-pclos1.bfs/kernel/drivers/media/common/tuners/qt1010.ko.gz

regards.

Was_Just19 · « **Reply #9 on:** May 17, 2011, 10:17:22 AM »

The difficulty with most of these devices is trying to determine what tuner chip the manufacturer used at any time in production.
They change tuners quite often it seems but do not change the device name or ID, which makes it almost impossible to know from the ID what tuner module is needed.

regards.

Jonesy · « **Reply #10 on:** May 17, 2011, 12:25:50 PM »

I pryed open the device and it is a QT1010 tuner chip.

locate qt1010 returns:

Code: [Select]

/lib/modules/2.6.38.6-pclos1/kernel/drivers/media/common/tuners/qt1010.ko.gz

So after doing modprobe qt1010 as Root

lsmod | grep qt returns this:

Code: [Select]

qt1010                  4685  1
i2c_core               16372 11 nvidia,qt1010,tda18218,af9013,i2c_i801,nvidia,dvb_usb_af9015,dvb_usb,em28xx,v4l2_common,videodev,tveeprom,videodev

So the module is present. But I knew that since it is the same module as used by my old DVB-T stick yet pluging the new device in still returns the Tuner not set message.

SpOoOooky

!!

Was_Just19 · « **Reply #11 on:** May 17, 2011, 01:41:06 PM »

Was the module active before you modprobed it?

Have you entered the module in modprobe.preload?

Jonesy · « **Reply #12 on:** May 17, 2011, 04:39:55 PM »

Quote from: Just19 on May 17, 2011, 01:41:06 PM

Was the module active before you modprobed it?

Have you entered the module in modprobe.preload?

Yes it was active, it was used by my previous Zarlink device as you can see from this output from dmesg for it..
It is in modprobe.preload.

Code: [Select]

dvb-usb: found a 'MSI Mega Sky 55801 DVB-T USB2.0' in warm state.
dvb-usb: will pass the complete MPEG2 transport stream to the software demuxer.
DVB: registering new adapter (MSI Mega Sky 55801 DVB-T USB2.0)
DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)...
Quantek QT1010 successfully identified.
dvb-usb: MSI Mega Sky 55801 DVB-T USB2.0 successfully initialized and connected.
usbcore: registered new interface driver dvb_usb_gl861

Why the QT1010 is identified in this old device and not the new one is a mystery. But the new one most
definitely has a QT1010 tuner. I have it in pieces again in front of me.

Was_Just19 · « **Reply #13 on:** May 17, 2011, 04:46:14 PM »

Maybe there is a firmware file required for it?

Will you post the dmesg output again for the new device with the qt1010 in place .....

Was_Just19 · « **Reply #14 on:** May 17, 2011, 04:57:28 PM »

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

Quote

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

PCLinuxOS-Forums

News:

Author Topic: DVB-T USB device help (Read 3404 times)

Jonesy

DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Jonesy

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Jonesy

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Jonesy

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Jonesy

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Jonesy

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help

Was_Just19

Re: DVB-T USB device help