2007/9/12, Markus Rechberger <[EMAIL PROTECTED]>:
>
> On 9/12/07, Valerio Bontempi <[EMAIL PROTECTED]> wrote:
> > 2007/9/11, Aidan Thornton <[EMAIL PROTECTED]>:
> > >
> > > On 9/11/07, Valerio Bontempi <[EMAIL PROTECTED]> wrote:
> > > > Hi Markus,
> > > >
> > > > I have a problem with a Terratec adapter Cinergy USB T XS and kernel
> > > 2.16.20
> > > > too.
> > > > (with kernel 2.16.18 everything works well)
> > > > This is the message found in dmesg:
> > > >
> > > > [ 2438.614225
> > > > ] /usr/local/src/v4l-dvb/v4l/tuner-core.c: setting tuner
> > > > callback
> > > > [ 2438.614343] /usr/local/src/v4l-dvb/v4l/tuner-core.c:
> > > > setting tuner
> > > > callback
> > > > [ 2438.619249] tuner 1-0061: Tuner has no way to set tv freq
> > > >
> > > > [ 2438.619367] em28xx #0: Found Terratec Cinergy T XS
> > > > [ 2438.619472] usbcore: registered new interface driver em28xx
> > > > [ 2438.655151] em2880-dvb.c: DVB Init
> > > > [ 2438.757779] FIXME:em28xx_i2c_send_bytes(1e): write
> > > > failed:
> > > >
> > > > [ 2438.757786] ===============================
> > > > [ 2438.757787] 7f
> > > > [ 2438.757789] ================================
> > > > [ 2438.759026] zl10353_read_register: readreg error (reg=127,
> ret==-19)
> > > > [ 2438.759125] em2880-dvb.c
> > > >  : failed initializing zl10353 DVB-T demodulator
> > > > [ 2438.759128] em2880-dvb.c: retrying with mt352 DVB-T demodulator
> > > > [ 2438.760024] FIXME:em28xx_i2c_send_bytes(1e): write
> > > > failed:
> > > > [ 2438.760027] ===============================
> > > >
> > > > [ 2438.760029] 7f
> > > > [ 2438.760030] ================================
> > > > [ 2438.761024] mt352_read_register: readreg error (reg=127,
> ret==-19)
> > > > [ 2438.761053] em2880-dvb.c: no luck with mt352 demodulator, not
> > > attaching
> > > >
> > > > em2880-dvb
> > > > [ 2438.761056] em2880-dvb.c: DVB-T demodulator not reachable, did
> you
> > > try
> > > > "modprobe em28xx device_mode=1"
> > > > [ 2438.761059] Em28xx: Initialized (Em2880 DVB Extension) extension
> > > >
> > > > I tried also device_mode = 1 without any effect.
> > > >
> > > > Do you know the reason for this problem (met only using new kernel
> > > 2.16.20)?
> > > > Thanks and regards,
> > > >
> > > > Valerio
> > > > _______________________________________________
> > >
> > > Looks like something's gone horribly wrong with the tuner driver. (All
> > > the subsequent write failure and demodulator not reachable errors are
> > > probably irrelevant; the GPIO-twiddling to bring the demodulator out
> > > of standby is done in a callback from the tuner driver, and so they're
> > > most likely due to it still being in standby.)
> > >
> > > Which driver are you using (v4l-dvb-stable, v4l-dvb-experimental,
> > > userspace, ...)? Are there any other errors before the ones you've
> > > pasted? (Unfortunately, I don't know the tuner driver well enough to
> > > figure out what's causing it, but I doubt it's firmware-related.)
> > >
> >
> > I'm using v4l-dvb-stable driver (but experimental one has the same
> error)
> >
> > Following all the /var/log/messages after modprobe em2880-dvb
> >
> > Sep 12 10:41:48 gandalf kernel: [  193.964000] em28xx v4l2 driver
> version
> > 0.0.1 loaded
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx: device is
> attached to
> > a USB 2.0 bus
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx: you're using the
> > experimental/unstable tree from mcentral.de
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx: there's also a
> stable
> > tree available but which is limited to
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx: linux <=2.6.19.2
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx: it's fine to use
> this
> > driver but keep in mind that it will move
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx: to
> > http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx: proved to be
> stable
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> > settings: 8
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 0, max size= 0
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 1, max size= 0
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 2, max size= 1448
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 3, max size= 2048
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 4, max size= 2304
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 5, max size= 2580
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 6, max size= 2892
> > Sep 12 10:41:48 gandalf kernel: [  194.084000] em28xx #0: Alternate
> setting
> > 7, max size= 3072
> > Sep 12 10:41:48 gandalf kernel: [  194.096000] attach_inform: eeprom
> > detected.
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 00:
> 1a
> > eb 67 95 cd 0c 43 00 c0 12 5c 00 9e 24 6a 34
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 10:
> 00
> > 00 06 57 02 0c 00 00 00 00 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 20:
> 44
> > 00 00 00 f0 10 01 00 00 00 00 00 5b 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 30:
> 00
> > 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 40:
> 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 50:
> 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 60:
> 00
> > 00 00 00 00 00 00 00 00 00 34 03 54 00 65 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 70:
> 72
> > 00 72 00 61 00 54 00 65 00 63 00 20 00 45 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 80:
> 6c
> > 00 65 00 63 00 74 00 72 00 6f 00 6e 00 69 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom 90:
> 63
> > 00 20 00 47 00 6d 00 62 00 48 00 00 00 24 03
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom a0:
> 43
> > 00 69 00 6e 00 65 00 72 00 67 00 79 00 20 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom b0:
> 54
> > 00 20 00 55 00 53 00 42 00 20 00 58 00 53 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom c0:
> 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom d0:
> 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom e0:
> 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] em28xx #0: i2c eeprom f0:
> 00
> > 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] EEPROM ID= 0x9567eb1a
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] Vendor/Product ID=
> 0ccd:0043
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] No audio on board.
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] 500mA max power
> > Sep 12 10:41:48 gandalf kernel: [  194.124000] Table at 0x06,
> > strings=0x249e, 0x346a, 0x0000
> > Sep 12 10:41:48 gandalf kernel: [  194.128000] tuner 2-0061: chip found
> @
> > 0xc2 (em28xx #0)
> > Sep 12 10:41:48 gandalf kernel: [  194.128000] attach inform (default):
> > detected I2C address c2
> > Sep 12 10:41:48 gandalf kernel: [  194.128000]
> > /usr/local/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback
> > Sep 12 10:41:48 gandalf kernel: [  194.128000]
> > /usr/local/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback
> > Sep 12 10:41:48 gandalf kernel: [  194.136000] tuner 2-0061: Tuner has
> no
> > way to set tv freq
> > Sep 12 10:41:48 gandalf kernel: [  194.136000] em28xx #0: Found Terratec
> > Cinergy T XS
> > Sep 12 10:41:48 gandalf kernel: [  194.136000] usbcore: registered new
> > interface driver em28xx
> > Sep 12 10:41:48 gandalf kernel: [  194.156000] em2880-dvb.c: DVB Init
> > Sep 12 10:41:48 gandalf kernel: [  194.260000]
> > FIXME:em28xx_i2c_send_bytes(1e): write failed:
> > Sep 12 10:41:48 gandalf kernel: [  194.260000]
> > ===============================
> > Sep 12 10:41:48 gandalf kernel: [  194.260000] 7f
> > Sep 12 10:41:48 gandalf kernel: [  194.260000]
> > ================================
> > Sep 12 10:41:48 gandalf kernel: [  194.260000] zl10353_read_register:
> > readreg error (reg=127, ret==-19)
> > Sep 12 10:41:48 gandalf kernel: [  194.260000] em2880-dvb.c: failed
> > initializing zl10353 DVB-T demodulator
> > Sep 12 10:41:48 gandalf kernel: [  194.260000] em2880-dvb.c: retrying
> with
> > mt352 DVB-T demodulator
> > Sep 12 10:41:48 gandalf kernel: [  194.264000]
> > FIXME:em28xx_i2c_send_bytes(1e): write failed:
> > Sep 12 10:41:48 gandalf kernel: [  194.264000]
> > ===============================
> > Sep 12 10:41:48 gandalf kernel: [  194.264000] 7f
> > Sep 12 10:41:48 gandalf kernel: [  194.264000]
> > ================================
> > Sep 12 10:41:48 gandalf kernel: [  194.264000] mt352_read_register:
> readreg
> > error (reg=127, ret==-19)
> > Sep 12 10:41:48 gandalf kernel: [  194.264000] em2880-dvb.c: no luck
> with
> > mt352 demodulator, not attaching em2880-dvb
> > Sep 12 10:41:48 gandalf kernel: [  194.264000] em2880-dvb.c: DVB-T
> > demodulator not reachable, did you try "modprobe em28xx device_mode=1"
> > Sep 12 10:41:48 gandalf kernel: [  194.264000] Em28xx: Initialized
> (Em2880
> > DVB Extension) extension
> >
> > Note that everything worked well with old kernel 2.16.18 on openSuse
> 10.2
> >
> > Can I use some specific configuration in compiling the driver?
>
> seems like wrong GPIO values for switching the device to DVB-T
> although it would be interesting if there's any other user with such a
> device which works. I know it has been supported a longer time ago but
> Terratec might have updated the device too.
>
> Markus
>


Hi Marks,

which could be the reason that makes this drivers to work fine with kernel
2.16.18 and not with 2.16.20 one?

Valerio



-- 
*********************************************
Valerio Bontempi
Blog: http://mithland.wordpress.com/
*********************************************
_______________________________________________
Em28xx mailing list
Em28xx@mcentral.de
http://mcentral.de/mailman/listinfo/em28xx

Reply via email to