em28xx driver - xc3028 tuner - readreg error

em28xx driver - xc3028 tuner - readreg error

[Valerio Bontempi]

Hi all,

today, after I have just installed an update for v4l-lib and
v4l-lib-devel opensuse 11.2 packages, my v4l-dvb driver (compiled from
sources) does not work anymore
Just looking to dmesg output I find

[  806.721162] em28xx: New device TerraTec Electronic GmbH Cinergy T
USB XS @ 480 Mbps (0ccd:0043, interface 0, class 0)
[  806.721353] em28xx #0: chip ID is em2870
[  806.833068] em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 43 00 c0 12
5c 00 9e 24 6a 34
[  806.833096] em28xx #0: i2c eeprom 10: 00 00 06 57 02 0c 00 00 00 00
00 00 00 00 00 00
[  806.833117] em28xx #0: i2c eeprom 20: 44 00 00 00 f0 10 01 00 00 00
00 00 5b 00 00 00
[  806.833138] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01
00 00 00 00 00 00
[  806.833158] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[  806.833178] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[  806.833198] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00
34 03 54 00 65 00
[  806.833218] em28xx #0: i2c eeprom 70: 72 00 72 00 61 00 54 00 65 00
63 00 20 00 45 00
[  806.833238] em28xx #0: i2c eeprom 80: 6c 00 65 00 63 00 74 00 72 00
6f 00 6e 00 69 00
[  806.833258] em28xx #0: i2c eeprom 90: 63 00 20 00 47 00 6d 00 62 00
48 00 00 00 24 03
[  806.833279] em28xx #0: i2c eeprom a0: 43 00 69 00 6e 00 65 00 72 00
67 00 79 00 20 00
[  806.833299] em28xx #0: i2c eeprom b0: 54 00 20 00 55 00 53 00 42 00
20 00 58 00 53 00
[  806.833319] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[  806.833339] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[  806.833359] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[  806.833379] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[  806.833401] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0xbfdf1b96
[  806.833409] em28xx #0: EEPROM info:
[  806.833414] em28xx #0:       No audio on board.
[  806.833419] em28xx #0:       500mA max power
[  806.833425] em28xx #0:       Table at 0x06, strings=0x249e, 0x346a, 0x0000
[  806.834138] em28xx #0: Identified as Terratec Cinergy T XS (card=43)
[  806.834289] em28xx #0:
[  806.834290]
[  806.834297] em28xx #0: The support for this board weren't valid yet.
[  806.834305] em28xx #0: Please send a report of having this working
[  806.834312] em28xx #0: not to V4L mailing list (and/or to other addresses)
[  806.834314]
[  806.842097] tuner 2-0061: chip found @ 0xc2 (em28xx #0)
[  806.842263] xc2028 2-0061: creating new instance
[  806.842271] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
[  806.842288] usb 1-4: firmware: requesting xc3028-v27.fw
[  806.853287] xc2028 2-0061: Loading 80 firmware images from
xc3028-v27.fw, type: xc2028 firmware, ver 2.7
[  806.886020] xc2028 2-0061: Loading firmware for type=BASE (1), id
0000000000000000.
[  808.284017] xc2028 2-0061: Loading firmware for type=(0), id
000000000000b700.
[  808.310009] SCODE (20000000), id 000000000000b700:
[  808.310020] xc2028 2-0061: Loading SCODE for type=MONO SCODE
HAS_IF_4320 (60008000), id 0000000000008000.
[  808.433021] em28xx #0: v4l2 driver version 0.1.2
[  808.437908] em28xx #0: V4L2 video device registered as /dev/video1
[  808.441137] usbcore: registered new interface driver em28xx
[  808.441154] em28xx driver loaded
[  808.562319] zl10353_read_register: readreg error (reg=127, ret==-19)
[  808.562937] mt352_read_register: readreg error (reg=127, ret==-19)
[  808.563050] em28xx #0: /2: dvb frontend not attached. Can't attach xc3028
[  808.563061] Em28xx: Initialized (Em28xx dvb Extension) extension


Before the update, v4l-dvb driver worked fine, and now it doesn't work
even if I remove the updated packages.
Checking for kernel modules conflict, I found only the modules
installed by v4l-dvb sources.
#find /lib/modules/`uname -r` -name 'em28xx*' | xargs -i ls -l {}
totale 236
-rw-r--r-- 1 root root 21464 22 dic 16:03
/lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-alsa.ko
-rw-r--r-- 1 root root 26176 22 dic 16:03
/lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-dvb.ko
-rw-r--r-- 1 root root 184936 22 dic 16:03
/lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx.ko

Which could be the reason of readreg error?


Thanks and regars

Valerio

Re: em28xx driver - xc3028 tuner - readreg error

[Devin Heitmueller]

On Tue, Dec 22, 2009 at 10:11 AM, Valerio Bontempi
<valerio.bontempi@gmail.com> wrote:
> Before the update, v4l-dvb driver worked fine, and now it doesn't work
> even if I remove the updated packages.
> Checking for kernel modules conflict, I found only the modules
> installed by v4l-dvb sources.
> #find /lib/modules/`uname -r` -name 'em28xx*' | xargs -i ls -l {}
> totale 236
> -rw-r--r-- 1 root root 21464 22 dic 16:03
> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-alsa.ko
> -rw-r--r-- 1 root root 26176 22 dic 16:03
> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-dvb.ko
> -rw-r--r-- 1 root root 184936 22 dic 16:03
> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx.ko

My guess is that these files were provided by your distro through a
kernel update (and in 2.6.31 this board is known to have problems
which have been fixed in the latest v4l-dvb tree).

I would suggest the following going into your v4l-dvb tree and doing
the following:

make distclean && make && make install && reboot

And see if the problem clears up.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: em28xx driver - xc3028 tuner - readreg error

[Valerio Bontempi]

2009/12/22 Devin Heitmueller <dheitmueller@kernellabs.com>:
> On Tue, Dec 22, 2009 at 10:11 AM, Valerio Bontempi
> <valerio.bontempi@gmail.com> wrote:
>> Before the update, v4l-dvb driver worked fine, and now it doesn't work
>> even if I remove the updated packages.
>> Checking for kernel modules conflict, I found only the modules
>> installed by v4l-dvb sources.
>> #find /lib/modules/`uname -r` -name 'em28xx*' | xargs -i ls -l {}
>> totale 236
>> -rw-r--r-- 1 root root 21464 22 dic 16:03
>> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-alsa.ko
>> -rw-r--r-- 1 root root 26176 22 dic 16:03
>> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-dvb.ko
>> -rw-r--r-- 1 root root 184936 22 dic 16:03
>> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx.ko
>
> My guess is that these files were provided by your distro through a
> kernel update (and in 2.6.31 this board is known to have problems
> which have been fixed in the latest v4l-dvb tree).
>
> I would suggest the following going into your v4l-dvb tree and doing
> the following:
>
> make distclean && make && make install && reboot
>
> And see if the problem clears up.
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
>

This is just I have done after removing the update packages (all
related to v4l libs and tools, none related to opensuse kernel), but
with no luck

However I have just tried what you suggested, but the problem hasn't
been cleared up

[    7.276755] em28xx: New device TerraTec Electronic GmbH Cinergy T
USB XS @ 480 Mbps (0ccd:0043, interface 0, class 0)
[    7.276993] em28xx #0: chip ID is em2870
[    7.310070] vc032x: Sensor ID 7673 (16)
[    7.310075] vc032x: Find Sensor OV7670
[    7.310187] gspca: /dev/video0 created
[    7.310224] usbcore: registered new interface driver vc032x
[    7.310228] vc032x: registered
[    7.394941] em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 43 00 c0 12
5c 00 9e 24 6a 34
[    7.394956] em28xx #0: i2c eeprom 10: 00 00 06 57 02 0c 00 00 00 00
00 00 00 00 00 00
[    7.394967] em28xx #0: i2c eeprom 20: 44 00 00 00 f0 10 01 00 00 00
00 00 5b 00 00 00
[    7.394977] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01
00 00 00 00 00 00
[    7.394988] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    7.394998] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    7.395008] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00
34 03 54 00 65 00
[    7.395021] em28xx #0: i2c eeprom 70: 72 00 72 00 61 00 54 00 65 00
63 00 20 00 45 00
[    7.395032] em28xx #0: i2c eeprom 80: 6c 00 65 00 63 00 74 00 72 00
6f 00 6e 00 69 00
[    7.395042] em28xx #0: i2c eeprom 90: 63 00 20 00 47 00 6d 00 62 00
48 00 00 00 24 03
[    7.395052] em28xx #0: i2c eeprom a0: 43 00 69 00 6e 00 65 00 72 00
67 00 79 00 20 00
[    7.395063] em28xx #0: i2c eeprom b0: 54 00 20 00 55 00 53 00 42 00
20 00 58 00 53 00
[    7.395074] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    7.395084] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    7.395094] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    7.395104] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00
[    7.395116] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0xbfdf1b96
[    7.395119] em28xx #0: EEPROM info:
[    7.395120] em28xx #0:       No audio on board.
[    7.395122] em28xx #0:       500mA max power
[    7.395125] em28xx #0:       Table at 0x06, strings=0x249e, 0x346a, 0x0000
[    7.395813] em28xx #0: Identified as Terratec Cinergy T XS (card=43)
[    7.395816] em28xx #0:
[    7.395816]
[    7.395830] em28xx #0: The support for this board weren't valid yet.
[    7.395838] em28xx #0: Please send a report of having this working
[    7.395845] em28xx #0: not to V4L mailing list (and/or to other addresses)
[    7.395846]
[    7.412090] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x1374 @
0, addr 00:1a:92:34:d4:d7
[    7.412096] forcedeth 0000:00:0a.0: highdma csum gbit lnktim desc-v3
[    7.412275] k8temp 0000:00:18.3: Temperature readouts might be
wrong - check erratum #141
[    7.414043] EDAC amd64: This node reports that Memory ECC is
currently disabled.
[    7.414048] EDAC amd64: bit 0x400000 in register F3x44 of the
MISC_CONTROL device (0000:00:18.3) should be enabled
[    7.414051] EDAC amd64: WARNING: ECC is NOT currently enabled by
the BIOS. Module will NOT be loaded.
[    7.414053]     Either Enable ECC in the BIOS, or use the
'ecc_enable_override' parameter.
[    7.414055]     Might be a BIOS bug, if BIOS says ECC is enabled
[    7.414056]     Use of the override can cause unknown side effects.
[    7.414073] amd64_edac: probe of 0000:00:18.2 failed with error -22
[    7.501404] usbcore: registered new interface driver snd-usb-audio
[    7.843367] tuner 2-0061: chip found @ 0xc2 (em28xx #0)
[    8.123514] xc2028 2-0061: creating new instance
[    8.123519] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
[    8.123530] usb 1-4: firmware: requesting xc3028-v27.fw
[    8.134197] xc2028 2-0061: Loading 80 firmware images from
xc3028-v27.fw, type: xc2028 firmware, ver 2.7
[    8.167270] xc2028 2-0061: Loading firmware for type=BASE (1), id
0000000000000000.
[    8.310475] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0011d80000f828c2]
[    8.440483] ieee1394: Host added: ID:BUS[1-00:1023]  GUID[00023c01510ec213]
[    9.574269] xc2028 2-0061: Loading firmware for type=(0), id
000000000000b700.
[    9.600262] SCODE (20000000), id 000000000000b700:
[    9.600267] xc2028 2-0061: Loading SCODE for type=MONO SCODE
HAS_IF_4320 (60008000), id 0000000000008000.
[    9.723270] em28xx #0: v4l2 driver version 0.1.2
[    9.728271] em28xx #0: V4L2 video device registered as /dev/video1
[    9.729313] usbcore: registered new interface driver em28xx
[    9.729317] em28xx driver loaded
[    9.811316] zl10353_read_register: readreg error (reg=127, ret==-19)
[    9.837317] mt352_read_register: readreg error (reg=127, ret==-19)
[    9.837412] em28xx #0: /2: dvb frontend not attached. Can't attach xc3028
[    9.837494] Em28xx: Initialized (Em28xx dvb Extension) extension

and

#find /lib/modules/`uname -r` -name 'em28xx*' | xargs -i ls -l {}
-rw-r--r-- 1 root root 21464 22 dic 17:07
/lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-alsa.ko
-rw-r--r-- 1 root root 26176 22 dic 17:07
/lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-dvb.ko
-rw-r--r-- 1 root root 184936 22 dic 17:07
/lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx.ko

shows that I have install only the just compiled modules

I also tried to update my downloaded v4l-dvb tree to its last version,
but I am not able to install it, I receive a lot of undefined symbol
error after modprobe em28xx.

Valerio

Re: em28xx driver - xc3028 tuner - readreg error

[Valerio Bontempi]

2009/12/22 Valerio Bontempi <valerio.bontempi@gmail.com>:
> 2009/12/22 Devin Heitmueller <dheitmueller@kernellabs.com>:
>> On Tue, Dec 22, 2009 at 10:11 AM, Valerio Bontempi
>> <valerio.bontempi@gmail.com> wrote:
>>> Before the update, v4l-dvb driver worked fine, and now it doesn't work
>>> even if I remove the updated packages.
>>> Checking for kernel modules conflict, I found only the modules
>>> installed by v4l-dvb sources.
>>> #find /lib/modules/`uname -r` -name 'em28xx*' | xargs -i ls -l {}
>>> totale 236
>>> -rw-r--r-- 1 root root 21464 22 dic 16:03
>>> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-alsa.ko
>>> -rw-r--r-- 1 root root 26176 22 dic 16:03
>>> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-dvb.ko
>>> -rw-r--r-- 1 root root 184936 22 dic 16:03
>>> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx.ko
>>
>> My guess is that these files were provided by your distro through a
>> kernel update (and in 2.6.31 this board is known to have problems
>> which have been fixed in the latest v4l-dvb tree).
>>
>> I would suggest the following going into your v4l-dvb tree and doing
>> the following:
>>
>> make distclean && make && make install && reboot
>>
>> And see if the problem clears up.
>>
>> Devin
>>
>> --
>> Devin J. Heitmueller - Kernel Labs
>> http://www.kernellabs.com
>>
>
> This is just I have done after removing the update packages (all
> related to v4l libs and tools, none related to opensuse kernel), but
> with no luck
>
> However I have just tried what you suggested, but the problem hasn't
> been cleared up
>
> [    7.276755] em28xx: New device TerraTec Electronic GmbH Cinergy T
> USB XS @ 480 Mbps (0ccd:0043, interface 0, class 0)
> [    7.276993] em28xx #0: chip ID is em2870
> [    7.310070] vc032x: Sensor ID 7673 (16)
> [    7.310075] vc032x: Find Sensor OV7670
> [    7.310187] gspca: /dev/video0 created
> [    7.310224] usbcore: registered new interface driver vc032x
> [    7.310228] vc032x: registered
> [    7.394941] em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 43 00 c0 12
> 5c 00 9e 24 6a 34
> [    7.394956] em28xx #0: i2c eeprom 10: 00 00 06 57 02 0c 00 00 00 00
> 00 00 00 00 00 00
> [    7.394967] em28xx #0: i2c eeprom 20: 44 00 00 00 f0 10 01 00 00 00
> 00 00 5b 00 00 00
> [    7.394977] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01
> 00 00 00 00 00 00
> [    7.394988] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00
> [    7.394998] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00
> [    7.395008] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00
> 34 03 54 00 65 00
> [    7.395021] em28xx #0: i2c eeprom 70: 72 00 72 00 61 00 54 00 65 00
> 63 00 20 00 45 00
> [    7.395032] em28xx #0: i2c eeprom 80: 6c 00 65 00 63 00 74 00 72 00
> 6f 00 6e 00 69 00
> [    7.395042] em28xx #0: i2c eeprom 90: 63 00 20 00 47 00 6d 00 62 00
> 48 00 00 00 24 03
> [    7.395052] em28xx #0: i2c eeprom a0: 43 00 69 00 6e 00 65 00 72 00
> 67 00 79 00 20 00
> [    7.395063] em28xx #0: i2c eeprom b0: 54 00 20 00 55 00 53 00 42 00
> 20 00 58 00 53 00
> [    7.395074] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00
> [    7.395084] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00
> [    7.395094] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00
> [    7.395104] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00
> 00 00 00 00 00 00
> [    7.395116] em28xx #0: EEPROM ID= 0x9567eb1a, EEPROM hash = 0xbfdf1b96
> [    7.395119] em28xx #0: EEPROM info:
> [    7.395120] em28xx #0:       No audio on board.
> [    7.395122] em28xx #0:       500mA max power
> [    7.395125] em28xx #0:       Table at 0x06, strings=0x249e, 0x346a, 0x0000
> [    7.395813] em28xx #0: Identified as Terratec Cinergy T XS (card=43)
> [    7.395816] em28xx #0:
> [    7.395816]
> [    7.395830] em28xx #0: The support for this board weren't valid yet.
> [    7.395838] em28xx #0: Please send a report of having this working
> [    7.395845] em28xx #0: not to V4L mailing list (and/or to other addresses)
> [    7.395846]
> [    7.412090] forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x1374 @
> 0, addr 00:1a:92:34:d4:d7
> [    7.412096] forcedeth 0000:00:0a.0: highdma csum gbit lnktim desc-v3
> [    7.412275] k8temp 0000:00:18.3: Temperature readouts might be
> wrong - check erratum #141
> [    7.414043] EDAC amd64: This node reports that Memory ECC is
> currently disabled.
> [    7.414048] EDAC amd64: bit 0x400000 in register F3x44 of the
> MISC_CONTROL device (0000:00:18.3) should be enabled
> [    7.414051] EDAC amd64: WARNING: ECC is NOT currently enabled by
> the BIOS. Module will NOT be loaded.
> [    7.414053]     Either Enable ECC in the BIOS, or use the
> 'ecc_enable_override' parameter.
> [    7.414055]     Might be a BIOS bug, if BIOS says ECC is enabled
> [    7.414056]     Use of the override can cause unknown side effects.
> [    7.414073] amd64_edac: probe of 0000:00:18.2 failed with error -22
> [    7.501404] usbcore: registered new interface driver snd-usb-audio
> [    7.843367] tuner 2-0061: chip found @ 0xc2 (em28xx #0)
> [    8.123514] xc2028 2-0061: creating new instance
> [    8.123519] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
> [    8.123530] usb 1-4: firmware: requesting xc3028-v27.fw
> [    8.134197] xc2028 2-0061: Loading 80 firmware images from
> xc3028-v27.fw, type: xc2028 firmware, ver 2.7
> [    8.167270] xc2028 2-0061: Loading firmware for type=BASE (1), id
> 0000000000000000.
> [    8.310475] ieee1394: Host added: ID:BUS[0-00:1023]  GUID[0011d80000f828c2]
> [    8.440483] ieee1394: Host added: ID:BUS[1-00:1023]  GUID[00023c01510ec213]
> [    9.574269] xc2028 2-0061: Loading firmware for type=(0), id
> 000000000000b700.
> [    9.600262] SCODE (20000000), id 000000000000b700:
> [    9.600267] xc2028 2-0061: Loading SCODE for type=MONO SCODE
> HAS_IF_4320 (60008000), id 0000000000008000.
> [    9.723270] em28xx #0: v4l2 driver version 0.1.2
> [    9.728271] em28xx #0: V4L2 video device registered as /dev/video1
> [    9.729313] usbcore: registered new interface driver em28xx
> [    9.729317] em28xx driver loaded
> [    9.811316] zl10353_read_register: readreg error (reg=127, ret==-19)
> [    9.837317] mt352_read_register: readreg error (reg=127, ret==-19)
> [    9.837412] em28xx #0: /2: dvb frontend not attached. Can't attach xc3028
> [    9.837494] Em28xx: Initialized (Em28xx dvb Extension) extension
>
> and
>
> #find /lib/modules/`uname -r` -name 'em28xx*' | xargs -i ls -l {}
> -rw-r--r-- 1 root root 21464 22 dic 17:07
> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-alsa.ko
> -rw-r--r-- 1 root root 26176 22 dic 17:07
> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx-dvb.ko
> -rw-r--r-- 1 root root 184936 22 dic 17:07
> /lib/modules/2.6.31.5-0.1-desktop/kernel/drivers/media/video/em28xx/em28xx.ko
>
> shows that I have install only the just compiled modules
>
> I also tried to update my downloaded v4l-dvb tree to its last version,
> but I am not able to install it, I receive a lot of undefined symbol
> error after modprobe em28xx.
>
> Valerio
>

Hi all,

I am still having problem using v4l-dvb drivers with Terratec Cinergy T USB XS.
As reported in first mail, I am using the last version of v4l-dvb
drivers with few lines adjustment in order to make this driver to
enable dvb for my dvb only device (this because official v4l-dvb
driver actually doesn't support my device at all)
I have cleaned my distro (openSuse 11.2 x86-64) about all the v4l
modules provided by distro's repositories, and I compiled modified
v4l-dvb source.
So acutally I am using a cleaned version of v4l-dvb.

But the
[ 1483.314420] zl10353_read_register: readreg error (reg=127, ret==-19)
[ 1483.315166] mt352_read_register: readreg error (reg=127, ret==-19)
error isn't solved yet.
Could it be related to the firmware I am using?


Regars,

Valerio Bontempi

Re: em28xx driver - xc3028 tuner - readreg error

[Devin Heitmueller]

On Mon, Jan 18, 2010 at 10:01 AM, Valerio Bontempi
<valerio.bontempi@gmail.com> wrote:
> Hi all,
>
> I am still having problem using v4l-dvb drivers with Terratec Cinergy T USB XS.
> As reported in first mail, I am using the last version of v4l-dvb
> drivers with few lines adjustment in order to make this driver to
> enable dvb for my dvb only device (this because official v4l-dvb
> driver actually doesn't support my device at all)
> I have cleaned my distro (openSuse 11.2 x86-64) about all the v4l
> modules provided by distro's repositories, and I compiled modified
> v4l-dvb source.
> So acutally I am using a cleaned version of v4l-dvb.
>
> But the
> [ 1483.314420] zl10353_read_register: readreg error (reg=127, ret==-19)
> [ 1483.315166] mt352_read_register: readreg error (reg=127, ret==-19)
> error isn't solved yet.
> Could it be related to the firmware I am using?

No, this has nothing to do with firmware.  It is probably an issue
where the gpio configuration is wrong and the demod is being held in
reset (hence it won't respond to i2c commands).

The 0ccd:0043 is on my todo list of devices to work on (they sent me a
sample board), although it's not the highest priority on my list given
how old it is.

Cheers,

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Info

[Adriano Gigante]

Hi Devin,
> The 0ccd:0043 is on my todo list of devices to work on (they sent me a
> sample board), although it's not the highest priority on my list given
> how old it is.
>    
Did they sent you also a 0ccd:0072 card (Terratec Cinergy Hybrid T USB 
XS FM)?
Adri

Re: Info

[Devin Heitmueller]

On Mon, Jan 18, 2010 at 11:03 AM, Adriano Gigante <adrigiga@yahoo.it> wrote:
> Hi Devin,
>>
>> The 0ccd:0043 is on my todo list of devices to work on (they sent me a
>> sample board), although it's not the highest priority on my list given
>> how old it is.
>>
>
> Did they sent you also a 0ccd:0072 card (Terratec Cinergy Hybrid T USB XS
> FM)?
> Adri

Terratec sent me two boards:  0ccd:0072 and 0ccd:0043.  I've actually
been working with a user on the #linuxtv irc channel who is in the
process of getting the 0ccd:0072 board to work (username Prahal).
He's making great progress, but if he gets stuck I will find some
cycles to work through whatever problem he finds.

Cheers,

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Info

[Markus Rechberger]

On Mon, Jan 18, 2010 at 5:17 PM, Devin Heitmueller
<dheitmueller@kernellabs.com> wrote:
> On Mon, Jan 18, 2010 at 11:03 AM, Adriano Gigante <adrigiga@yahoo.it> wrote:
>> Hi Devin,
>>>
>>> The 0ccd:0043 is on my todo list of devices to work on (they sent me a
>>> sample board), although it's not the highest priority on my list given
>>> how old it is.
>>>
>>
>> Did they sent you also a 0ccd:0072 card (Terratec Cinergy Hybrid T USB XS
>> FM)?
>> Adri
>
> Terratec sent me two boards:  0ccd:0072 and 0ccd:0043.  I've actually
> been working with a user on the #linuxtv irc channel who is in the
> process of getting the 0ccd:0072 board to work (username Prahal).
> He's making great progress, but if he gets stuck I will find some
> cycles to work through whatever problem he finds.
>

Just fyi there's a hardware bug with the 0072/terratec hybrid xs fm
(cx25843 - xc5000):

http://img91.imageshack.us/i/00000004qf8.png/
http://img104.imageshack.us/i/00000009cp4.png/

nothing that can be fixed with the driver.

Markus

Re: Info

[Devin Heitmueller]

Hello Markus,

On Mon, Jan 18, 2010 at 11:29 AM, Markus Rechberger
<mrechberger@gmail.com> wrote:
> Just fyi there's a hardware bug with the 0072/terratec hybrid xs fm
> (cx25843 - xc5000):
>
> http://img91.imageshack.us/i/00000004qf8.png/
> http://img104.imageshack.us/i/00000009cp4.png/
>
> nothing that can be fixed with the driver.

Interesting.  If it cannot be fixed with the driver, how does the
Windows driver work then?  Is this some sort of premature hardware
failure that occurs (after which point it is irreversible)?

Thanks for taking the time to point this out though, since I could
totally imagine banging my head against the wall for quite a while
once I saw this.

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Info

[Markus Rechberger]

On Mon, Jan 18, 2010 at 5:36 PM, Devin Heitmueller
<dheitmueller@kernellabs.com> wrote:
> Hello Markus,
>
> On Mon, Jan 18, 2010 at 11:29 AM, Markus Rechberger
> <mrechberger@gmail.com> wrote:
>> Just fyi there's a hardware bug with the 0072/terratec hybrid xs fm
>> (cx25843 - xc5000):
>>
>> http://img91.imageshack.us/i/00000004qf8.png/
>> http://img104.imageshack.us/i/00000009cp4.png/
>>
>> nothing that can be fixed with the driver.
>
> Interesting.  If it cannot be fixed with the driver, how does the
> Windows driver work then?  Is this some sort of premature hardware
> failure that occurs (after which point it is irreversible)?
>

conexant cx25843 - xceive xc5000 failure (as what I've heard conexant
laid off people in that area years ago while xceive (see their driver
changelog if you have access to it) tried to fix it with their
firmware but didn't succeed), it also happens with windows. Those
screenshots are taken from a videoclip
it was of course a big problem for business customers (almost all of
them happily switched away from it)
This is the same retail hardware as everyone else uses out there. XS
FM is not being sold anymore.
I only know one company in Ireland still sticking with it, also in
terms of videoquality I'd avoid that combination.

Markus

> Thanks for taking the time to point this out though, since I could
> totally imagine banging my head against the wall for quite a while
> once I saw this.
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
>

Re: Info

[fogna]

Il 01/18/2010 06:33 PM, Markus Rechberger ha scritto:
> On Mon, Jan 18, 2010 at 5:36 PM, Devin Heitmueller
> <dheitmueller@kernellabs.com> wrote:
>   
>> Hello Markus,
>>
>> On Mon, Jan 18, 2010 at 11:29 AM, Markus Rechberger
>> <mrechberger@gmail.com> wrote:
>>     
>>> Just fyi there's a hardware bug with the 0072/terratec hybrid xs fm
>>> (cx25843 - xc5000):
>>>
>>> http://img91.imageshack.us/i/00000004qf8.png/
>>> http://img104.imageshack.us/i/00000009cp4.png/
>>>
>>> nothing that can be fixed with the driver.
>>>       
>> Interesting.  If it cannot be fixed with the driver, how does the
>> Windows driver work then?  Is this some sort of premature hardware
>> failure that occurs (after which point it is irreversible)?
>>
>>     
> conexant cx25843 - xceive xc5000 failure (as what I've heard conexant
> laid off people in that area years ago while xceive (see their driver
> changelog if you have access to it) tried to fix it with their
> firmware but didn't succeed), it also happens with windows. Those
> screenshots are taken from a videoclip
> it was of course a big problem for business customers (almost all of
> them happily switched away from it)
> This is the same retail hardware as everyone else uses out there. XS
> FM is not being sold anymore.
> I only know one company in Ireland still sticking with it, also in
> terms of videoquality I'd avoid that combination.
>
> Markus
>
>   
>> Thanks for taking the time to point this out though, since I could
>> totally imagine banging my head against the wall for quite a while
>> once I saw this.
>>
>> Devin
>>
>> --
>> Devin J. Heitmueller - Kernel Labs
>> http://www.kernellabs.com
>>
>>     
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>
>   
Hi Markus, thanks for the info, i didn't know of this hardware problem,
i have this usb stick and at the moment all works normally, now i know
when it will be time to replace it :)

Re: Info

[Markus Rechberger]

On Mon, Jan 18, 2010 at 7:50 PM, fogna <fogna80@gmail.com> wrote:
> Il 01/18/2010 06:33 PM, Markus Rechberger ha scritto:
>> On Mon, Jan 18, 2010 at 5:36 PM, Devin Heitmueller
>> <dheitmueller@kernellabs.com> wrote:
>>
>>> Hello Markus,
>>>
>>> On Mon, Jan 18, 2010 at 11:29 AM, Markus Rechberger
>>> <mrechberger@gmail.com> wrote:
>>>
>>>> Just fyi there's a hardware bug with the 0072/terratec hybrid xs fm
>>>> (cx25843 - xc5000):
>>>>
>>>> http://img91.imageshack.us/i/00000004qf8.png/
>>>> http://img104.imageshack.us/i/00000009cp4.png/
>>>>
>>>> nothing that can be fixed with the driver.
>>>>
>>> Interesting.  If it cannot be fixed with the driver, how does the
>>> Windows driver work then?  Is this some sort of premature hardware
>>> failure that occurs (after which point it is irreversible)?
>>>
>>>
>> conexant cx25843 - xceive xc5000 failure (as what I've heard conexant
>> laid off people in that area years ago while xceive (see their driver
>> changelog if you have access to it) tried to fix it with their
>> firmware but didn't succeed), it also happens with windows. Those
>> screenshots are taken from a videoclip
>> it was of course a big problem for business customers (almost all of
>> them happily switched away from it)
>> This is the same retail hardware as everyone else uses out there. XS
>> FM is not being sold anymore.
>> I only know one company in Ireland still sticking with it, also in
>> terms of videoquality I'd avoid that combination.
>>
>> Markus
>>
>>
>>> Thanks for taking the time to point this out though, since I could
>>> totally imagine banging my head against the wall for quite a while
>>> once I saw this.
>>>
>>> Devin
>>>
>>> --
>>> Devin J. Heitmueller - Kernel Labs
>>> http://www.kernellabs.com
>>>
>>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>>
> Hi Markus, thanks for the info, i didn't know of this hardware problem,
> i have this usb stick and at the moment all works normally, now i know
> when it will be time to replace it :)
>

it happens sporadically sometimes 1 time/5 minutes sometimes 1 time/10 minutes.
I think in windows it sometimes drops frames it also happens there and
can be seen with VLC
maybe some codecs also compensate it a little bit. There's no generic
rule about this the xc5000
overdrives the videodecoder (it's not empia related issue actually
moreover conexant/xceive)

Markus

Re: em28xx driver - xc3028 tuner - readreg error

[Valerio Bontempi]

2010/1/18 Devin Heitmueller <dheitmueller@kernellabs.com>:
> On Mon, Jan 18, 2010 at 10:01 AM, Valerio Bontempi
> <valerio.bontempi@gmail.com> wrote:
>> Hi all,
>>
>> I am still having problem using v4l-dvb drivers with Terratec Cinergy T USB XS.
>> As reported in first mail, I am using the last version of v4l-dvb
>> drivers with few lines adjustment in order to make this driver to
>> enable dvb for my dvb only device (this because official v4l-dvb
>> driver actually doesn't support my device at all)
>> I have cleaned my distro (openSuse 11.2 x86-64) about all the v4l
>> modules provided by distro's repositories, and I compiled modified
>> v4l-dvb source.
>> So acutally I am using a cleaned version of v4l-dvb.
>>
>> But the
>> [ 1483.314420] zl10353_read_register: readreg error (reg=127, ret==-19)
>> [ 1483.315166] mt352_read_register: readreg error (reg=127, ret==-19)
>> error isn't solved yet.
>> Could it be related to the firmware I am using?
>
> No, this has nothing to do with firmware.  It is probably an issue
> where the gpio configuration is wrong and the demod is being held in
> reset (hence it won't respond to i2c commands).
>
> The 0ccd:0043 is on my todo list of devices to work on (they sent me a
> sample board), although it's not the highest priority on my list given
> how old it is.
>
> Cheers,
>
> Devin
>
> --
> Devin J. Heitmueller - Kernel Labs
> http://www.kernellabs.com
>

Hi Devin,

maybe it could be useful: today, without any change from yesterday,
the device has been fully initialized at boot time.
>From dmesg

  10.252753] xc2028 2-0061: Loading 80 firmware images from
xc3028-v27.fw, type: xc2028 firmware, ver 2.7
[   10.286264] xc2028 2-0061: Loading firmware for type=BASE (1), id
0000000000000000.
[   11.674270] xc2028 2-0061: Loading firmware for type=(0), id
000000000000b700.
[   11.701412] SCODE (20000000), id 000000000000b700:
[   11.701419] xc2028 2-0061: Loading SCODE for type=MONO SCODE
HAS_IF_4320 (60008000), id 0000000000008000.
[   11.824268] em28xx #0: v4l2 driver version 0.1.2
[   11.829157] em28xx #0: V4L2 video device registered as video1
[   11.830312] usbcore: registered new interface driver em28xx
[   11.830316] em28xx driver loaded
[   11.997659] xc2028 2-0061: attaching existing instance
[   11.997665] xc2028 2-0061: type set to XCeive xc2028/xc3028 tuner
[   11.997667] em28xx #0: em28xx #0/2: xc3028 attached
[   11.997671] DVB: registering new adapter (em28xx #0)
[   11.997675] DVB: registering adapter 0 frontend 0 (Zarlink ZL10353 DVB-T)...
[   11.998086] em28xx #0: Successfully loaded em28xx-dvb
[   11.998090] Em28xx: Initialized (Em28xx dvb Extension) extension

instead of (from /var/log/messages)

Jan 18 16:53:04 gandalf kernel: [ 4894.539028] xc2028 2-0061: Loading
80 firmware images from xc3028-v27.fw, type: xc2028 firmware, ver 2.7
Jan 18 16:53:04 gandalf kernel: [ 4894.575016] xc2028 2-0061: Loading
firmware for type=BASE (1), id 0000000000000000.
Jan 18 16:53:05 gandalf kernel: [ 4895.972018] xc2028 2-0061: Loading
firmware for type=(0), id 000000000000b700.
Jan 18 16:53:05 gandalf kernel: [ 4895.998010] SCODE (20000000), id
000000000000b700:
Jan 18 16:53:05 gandalf kernel: [ 4895.998022] xc2028 2-0061: Loading
SCODE for type=MONO SCODE HAS_IF_4320 (60008000), id 0000000000008000.
Jan 18 16:53:05 gandalf kernel: [ 4896.122024] em28xx #0: v4l2 driver
version 0.1.2
Jan 18 16:53:05 gandalf kernel: [ 4896.127126] em28xx #0: V4L2 video
device registered as video1
Jan 18 16:53:05 gandalf kernel: [ 4896.129142] usbcore: registered new
interface driver em28xx
Jan 18 16:53:05 gandalf kernel: [ 4896.129157] em28xx driver loaded
Jan 18 16:53:05 gandalf kernel: [ 4896.155171] zl10353_read_register:
readreg error (reg=127, ret==-19)
Jan 18 16:53:05 gandalf kernel: [ 4896.155914] mt352_read_register:
readreg error (reg=127, ret==-19)
Jan 18 16:53:05 gandalf kernel: [ 4896.156419] em28xx #0: /2: dvb
frontend not attached. Can't attach xc3028
Jan 18 16:53:05 gandalf kernel: [ 4896.156434] Em28xx: Initialized
(Em28xx dvb Extension) extension

Is there a reason of this behaviour?

Valerio

Re: Info

[Devin Heitmueller]

On Sun, Feb 14, 2010 at 12:33 PM, Florent NOUVELLON
<flonouvellon@gmail.com> wrote:
> Hi Devin,
>
> Did you with Prahal advanced the 0072/terratec hybrid xs fm support in
> linux-dvb driver ?
>
> If you need any kind of help (testing, or whatever) feel free to ask me.
>
> Regards,
> Florent

Hi Florent,

Prahal was making good progress, and I was helping him over irc when I
had time.  But I have not invested any of my own time working on the
driver at this point (as I've been tied up working on other projects).

Devin

-- 
Devin J. Heitmueller - Kernel Labs
http://www.kernellabs.com

Re: Info

[Adriano Gigante]

Devin,
can you ask Prahal to keep this mailing list updated with the progress 
of develop?
People from the list could help him in any need.
Thank you.
Adri


On 02/14/2010 06:33 PM, Florent NOUVELLON wrote:
 > > Hi Devin,
 > >
 > > Did you with Prahal advanced the 0072/terratec hybrid xs fm support in
 > > linux-dvb driver ?
 > >
 > > If you need any kind of help (testing, or whatever) feel free to 
ask me.
 > >
 > > Regards,
 > > Florent
 > >

Re: Info

[Adriano Gigante]

Hi Devin,

...do you think we will have our stick (0072/terratec hybrid xs fm) 
working before FIFA World Cup?


Thanks
Adriano


Il 14/02/2010 18:33, Florent NOUVELLON ha scritto:
> Hi Devin,
>
> Did you with Prahal advanced the 0072/terratec hybrid xs fm support in
> linux-dvb driver ?
>
> If you need any kind of help (testing, or whatever) feel free to ask me.
>
> Regards,
> Florent
>
>
> 2010/1/18 Markus Rechberger <mrechberger@gmail.com
> <mailto:mrechberger@gmail.com>>
>
>     On Mon, Jan 18, 2010 at 7:50 PM, fogna <fogna80@gmail.com
>     <mailto:fogna80@gmail.com>> wrote:
>      > Il 01/18/2010 06:33 PM, Markus Rechberger ha scritto:
>      >> On Mon, Jan 18, 2010 at 5:36 PM, Devin Heitmueller
>      >> <dheitmueller@kernellabs.com
>     <mailto:dheitmueller@kernellabs.com>> wrote:
>      >>
>      >>> Hello Markus,
>      >>>
>      >>> On Mon, Jan 18, 2010 at 11:29 AM, Markus Rechberger
>      >>> <mrechberger@gmail.com <mailto:mrechberger@gmail.com>> wrote:
>      >>>
>      >>>> Just fyi there's a hardware bug with the 0072/terratec hybrid
>     xs fm
>      >>>> (cx25843 - xc5000):
>      >>>>
>      >>>> http://img91.imageshack.us/i/00000004qf8.png/
>      >>>> http://img104.imageshack.us/i/00000009cp4.png/
>      >>>>
>      >>>> nothing that can be fixed with the driver.
>      >>>>
>      >>> Interesting.  If it cannot be fixed with the driver, how does the
>      >>> Windows driver work then?  Is this some sort of premature hardware
>      >>> failure that occurs (after which point it is irreversible)?
>      >>>
>      >>>
>      >> conexant cx25843 - xceive xc5000 failure (as what I've heard
>     conexant
>      >> laid off people in that area years ago while xceive (see their
>     driver
>      >> changelog if you have access to it) tried to fix it with their
>      >> firmware but didn't succeed), it also happens with windows. Those
>      >> screenshots are taken from a videoclip
>      >> it was of course a big problem for business customers (almost all of
>      >> them happily switched away from it)
>      >> This is the same retail hardware as everyone else uses out there. XS
>      >> FM is not being sold anymore.
>      >> I only know one company in Ireland still

ing with it, also in
>      >> terms of videoquality I'd avoid that combination.
>      >>
>      >> Markus
>      >>
>      >>
>      >>> Thanks for taking the time to point this out though, since I could
>      >>> totally imagine banging my head against the wall for quite a while
>      >>> once I saw this.
>      >>>
>      >>> Devin
>      >>>
>      >>> --
>      >>> Devin J. Heitmueller - Kernel Labs
>      >>> http://www.kernellabs.com
>      >>>
>      >>>
>      >> --
>      >> To unsubscribe from this list: send the line "unsubscribe
>     linux-media" in
>      >> the body of a message to majordomo@vger.kernel.org
>     <mailto:majordomo@vger.kernel.org>
>      >> More majordomo info at http://vger.kernel.org/majordomo-info.html
>      >>
>      >>
>      > Hi Markus, thanks for the info, i didn't know of this hardware
>     problem,
>      > i have this usb stick and at the moment all works normally, now i
>     know
>      > when it will be time to replace it :)
>      >
>
>     it happens sporadically sometimes 1 time/5 minutes sometimes 1
>     time/10 minutes.
>     I think in windows it sometimes drops frames it also happens there and
>     can be seen with VLC
>     maybe some codecs also compensate it a little bit. There's no generic
>     rule about this the xc5000
>     overdrives the videodecoder (it's not empia related issue actually
>     moreover conexant/xceive)
>
>     Markus
>     --
>     To unsubscribe from this list: send the line "unsubscribe
>     linux-media" in
>     the body of a message to majordomo@vger.kernel.org
>     <mailto:majordomo@vger.kernel.org>
>     More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>

Info

[BMW AUTOMOBILE]

-- 
You won BMW X6 XDrive Car and a £750,000.00GBP.Send name: tel: country: to Official E-mail: bmwautomobile322@yahoo.ie