em28xx-based KWorld 310U delivers no signal, 2 drivers tried

Hello,

I had troubles with my saa7134 card (driver got in a phase where it never powered on the device again) so I fetched an em2880-based KWorld DVB-T 310U. I feel awkward bothering you again but this device doesn't want to work properly, 2 different drivers tried, although I researched before my purchase which device would most probably work.

I tried the v4l-dvb-kernel em28xx driver from mcentral linked to at
http://mcentral.de/wiki/index.php5/Em2880 which is where one gets directed to when following the links about supported hardware using video via usb em28xx from the v4l wiki main page.

When using tvtime-scanner it reports I/O error, driver doesn't want to stop streaming, driver doesn't want to start streaming and can't drop frame after a while. When using tvtimes gui scanner it hangs at a random channel after a while. While it has gathered some channels then, it hasn't got all. Sometimes tvtime only output black and white and sometimes in color and it freezes at a frame after some while. dmesg says incorrect setup device. For the rare moments the tv image was fine, dmesg gave analog tv request.

DVB-T scanning went fine with scan from dvb-utils and w_scan only mplayer doesn't have an option for TV in its gui (I reconfigured mplayer and got v4l support reported and recompiled) and I won't bash tune manually everytime, so I never saw a DVB-T image and mplayer is the only option with Gnome as far as I gathered (kaffeine is for KDE, someone wrote xine is for grandfathers and Totem, well I didn't find the directory where to place channels.conf).

Then I switched to the v4l-dvb driver which is the first link in the users section on v4l wikis main page. This driver put out to dmesg:

[    0.000000] Linux video capture interface: v2.00
[    0.000000] em28xx v4l2 driver version 0.1.0 loaded
[    0.000000] em28xx new video device (eb1a:e310): interface 0, class
255
[    0.000000] em28xx Has usb audio class
[    0.000000] em28xx #0: Alternate settings: 8
[    0.000000] em28xx #0: Alternate setting 0, max size= 0
[    0.000000] em28xx #0: Alternate setting 1, max size= 0
[    0.000000] em28xx #0: Alternate setting 2, max size= 1448
[    0.000000] em28xx #0: Alternate setting 3, max size= 2048
[    0.000000] em28xx #0: Alternate setting 4, max size= 2304
[    0.000000] em28xx #0: Alternate setting 5, max size= 2580
[    0.000000] em28xx #0: Alternate setting 6, max size= 2892
[    0.000000] em28xx #0: Alternate setting 7, max size= 3072
[    0.000000] em28xx #0: chip ID is em2882/em2883
[    0.000000] em28xx #0: i2c eeprom 00: 1a eb 67 95 1a eb 10 e3 50 12
5c 03 6a 22 00 00
[    0.000000] em28xx #0: i2c eeprom 10: 00 00 04 57 4e 07 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 01 00 00 00
00 00 5b 1e 00 00
[    0.000000] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00
22 03 55 00 53 00
[    0.000000] em28xx #0: i2c eeprom 70: 42 00 20 00 32 00 38 00 38 00
31 00 20 00 44 00
[    0.000000] em28xx #0: i2c eeprom 80: 65 00 76 00 69 00 63 00 65 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom 90: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom a0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom b0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    0.000000] EEPROM ID= 0x9567eb1a, hash = 0x966a0441
[    0.000000] Vendor/Product ID= eb1a:e310
[    0.000000] AC97 audio (5 sample rates)
[    0.000000] 500mA max power
[    0.000000] Table at 0x04, strings=0x226a, 0x0000, 0x0000
[    0.000000] em28xx #0: 
[    0.000000] 
[    0.000000] em28xx #0: The support for this board weren't valid yet.
[    0.000000] em28xx #0: Please send a report of having this working
[    0.000000] em28xx #0: not to V4L mailing list (and/or to other
addresses)
[    0.000000] 
[    0.000000] tuner' 1-0061: chip found @ 0xc2 (em28xx #0)
[    0.000000] xc2028 1-0061: creating new instance
[    0.000000] xc2028 1-0061: type set to XCeive xc2028/xc3028 tuner
[    0.000000] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
[    0.000000] tvp5150 1-005c: tvp5150am1 detected.
[    0.000000] em28xx #0: V4L2 device registered as /dev/video0
and /dev/vbi0
[    0.000000] em28xx #0: Found MSI DigiVox A/D
[    0.000000] usbcore: registered new interface driver em28xx
[    0.000000] tvp5150 1-005c: tvp5150am1 detected.
[    0.000000] tvp5150 1-005c: tvp5150am1 detected.
[    0.000000] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
[    0.000000] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
[    0.000000] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
[    0.000000] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.
[    0.000000] tvp5150 1-005c: tvp5150am1 detected.
[    0.000000] xc2028 1-0061: Error: firmware xc3028-v27.fw not found.

After I got the firmware following the instructions on the wiki, tvtimes takes approximately 10 seconds to load (it seems to load 80 different firmwares) in contrast to instant load before but tvtime says no signal and while it can scan the screen remains blue.

I tried the zapping application but it delivers 3 error messages before it segfaults: /dev/vbi0 is no vbi device, -- that's it at another try, it was sth like driver doesn't support video_overlay and sth long string before.

What are the best working options to get my KWorld DVB-T 310U usable in analog TV mode at least? Which driver to I have to take, what would I have to do? (I removed my previous saa7134 driver installation completely, so probably no old modules lying around). I'm on Ubuntu 8.04 but I have a vanilla kernel 2.6.27-rc5 source at hand (yes which I configured, compiled and have working with Ubuntu in another grub entry :-)), which v4l drivers would I have to enable there to use that kernels drivers?

Thanks fro any help!

Kind and Best Regards

Lars

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Hello Lars,

Could you sniff your device using usbsnoop tool? After that, please send the log file back to the list. With log file we can try to figure out the issue.

Here some info about usbsnoop:
http://www.linuxtv.org/v4lwiki/index.php/Usbsnoop

At video4linux mailist we're working only in mainline source.

Cheers,
Douglas

--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

Hi,

Am Mittwoch, den 03.09.2008, 01:39 +0200 schrieb Markus Rechberger:

What's the state of each of your 3 trees v4l-dvb-kernel, v4l-dvb-experimental and em28xx-new? I noticed that the last entry to your v4l trees is around 4 months old in both cases and that they both received updates at around the same times. Is there a difference in the experimental tree from the kernel tree? Is every file affected or were only some added/changed? I gathered from gnames archive of your em28xx mailing list that you have an em28xx-new tree. Unfortunately I found only 5 posts regarding the 310U, yet many regarding the 300. Will your new tree support the chips that come with the em2883 like the XCeive 3028? Your kernel driver gave the 310U the status of a DVB-T device and w_scan worked, unfortunately the analog part was unstable as mentioned in my first e-mail and I have no DVB-T viewing application under Gnome (or they don't work (Totem misses the channels.conf and I don't know where to put it and mplayers gui has no TV controls and I haven't figured out its command line spec and I don't know whether I want to)). The v4l-dvb driver from the v4l wikis main-page (so not yours) didn't give the 310U the status of a DVB-T device so it would just work for analog.
The v4l wiki has many different pages which tell similar things but they are not linked with each other and sometimes one leads there while the other leads elsewhere and the information obtained then is different. For example regarding the em28xx it is said that only analog works but the xc3028 which may come with an em28xx (as in my case) is said to have support for DVB-T yet the v4l-dvb driver didn't make the device a DVB-T one. Is that the em28xx drivers "fault"?
Also there is a seperate wiki for dvb-t which I think is unneccessary. They are pointing to the same repository (v4l-dvb) and the same people are working on the driver, isn't this the case? It would be sufficient if the linuxTV wiki split the technical section only into one for dvb-info and one for analog info. And where would the hybrid people go?

Lars
--
video4linux-list mailing list
Unsubscribe mailto:[email protected]?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list