Re: [Em28xx] ehci_hcd map_single: unable to map unsafe buffer on a standard NSLU2
On 9/11/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/10/07, David Anne-Sophie [EMAIL PROTECTED] wrote: David Anne-Sophie a écrit : Hello all, I am trying to use my hybrid USB tuner on my NSLU2. Tuner=Terratec cinergy XS Driver=http://mcentral.de/wiki/index.php/Em2880 I plugged it directly to the DISK-2 connector. On DISK-1 there is a USB hard-disk that contains the filesystems. The driver compiles fine on the standard debian etch kernel, and loads perfectly. I just did a minor patch of this driver around a udelay(2500); - udelay(2000);udelay(500); (2500 is a too big value for the ARM architecture, see bad_udelay). When I try tzap to activate the dvb-t stream, I get those errors: ehci_hcd :00:01.2: alloc_safe_buffer: could not alloc dma memory (size=36096) ehci_hcd :00:01.2: map_single: unable to map unsafe buffer ffc2c000! many times (I think one per USB packet). And the tuner does not stream anything... I did not modify anything in the NSLU2 (neither RAM or frequency), just upgraded to debian etch arm architecture following the nslu2-linux.org tutorials. Do you know what it means and how to solve the issue? Do not hesitate to ask for specific information. Thanks! Cheers, David. [EMAIL PROTECTED] ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx I have some informations that can help you to resolve my problem. These informations comes from the newlist of debian-arm : In this forum, I said that the driver works correctly on a PC with ubuntu, and the response is : Working on a PC does not mean the driver is correct. On a PC physical addresses match the kernel's point of view in general, while on the arm everything goes through interesting mappings, which make is essential for the driver to correctly use readX/writeX calls along with ioremap calls. Any attemps to directly access anything will fail on the arm while it almost always works on a PC. Not sure quite how that might impact a USB device, but even there the driver has to do DMA setup with corrected addresses, which again is not necesary on a PC but is on the arm. i'm at the suse conference this week there are some interesting people around who're into the usb subsystem. The em28xx driver makes use of the usb subsystem (which also includes allocation of memory) I'll try to get some answers tomorrow about this issue. Markus Hello Markus, Do you have news about my problem ? in em28xx.h there's a static defined value for the number of videopackets #define EM28XX_NUM_PACKETS 40 try to lower that value by about the half or less this will allocate less memory in the end. I'm not sure if that might out .. although that was the only idea which came up after the talk yesterday. Let me know if it works out otherwise I'll have a further discussion about it with the usb guys. Markus ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] Terratec Prodigy USB TV Stick BUG
Oh, yes, like me post on 09.08.2007 22:59 ;) - same error, i thinnk Markus Rechberger wrote: On 9/11/07, Walter Bender [EMAIL PROTECTED] wrote: Me problem is very similar. - lets say, the same... i can help debugging, too. You also have a Prodigy device? Markus ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
[Em28xx] Kworld VS-DVB-T 323UR not working
I have Kworld VS-DVB-T 323UR (Kworld Plustv Hybrid USB Stick).Here is product overview: http://www.kworld.com.tw/product_overview.aspx?P_id=43 This is Analog/digital hybrid tv usb stick. This is em2882 based. I wont to setup this tuner on linux ( kubuntu or debian distro). i was trying to do this by installing em2xx module without any sucess. Here is my conf: [] kubutnu Feisty Fawn [] kernel 2.6.20-15 [] dvb-apps [] v4l [] firmware4 [] mercurial dmesg: Sep 9 21:11:33 mivis-laptop kernel: [ 7800.244000] Linux video capture interface: v2.00 Sep 9 21:11:33 mivis-laptop kernel: [ 7800.304000] em28xx v4l2 driver version 0.0.1 loaded Sep 9 21:11:33 mivis-laptop kernel: [ 7800.304000] usbcore: registered new interface driver em28xx after i unpluged and pluged my tuner: Sep 9 21:28:50 mivis-laptop kernel: [ 8837.064000] usb 5-8: USB disconnect, address 5 Sep 9 21:28:53 mivis-laptop kernel: [ 8840.088000] usb 5-8: new high speed USB device using ehci_hcd and address 6 Sep 9 21:28:53 mivis-laptop kernel: [ 8840.228000] usb 5-8: configuration #1 chosen from 1 choice Sep 9 22:01:00 mivis-laptop kernel: [10767.50] usb 5-8: new high speed USB device using ehci_hcd and address 8 Sep 9 22:01:00 mivis-laptop kernel: [10767.64] usb 5-8: configuration #1 chosen from 1 choice lsusb Bus 005 Device 008: ID eb1a:e323 eMPIA Technology, Inc. Have anyone got work this usb tv stick? ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] Terratec Cinergy USB T XS
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
Re: [Em28xx] Terratec Cinergy USB T XS
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
Re: [Em28xx] Terratec Cinergy USB T XS
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
Re: [Em28xx] Terratec Cinergy USB T XS
On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: 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
Re: [Em28xx] sound problem: pinnacle PCTV USB2 200e
On Wed, 12 Sep 2007 10:45:53 +0200 Markus Rechberger [EMAIL PROTECTED] wrote: did you use the usbaudio_setup.sh tool for piping audio from the device to your soundcard's DSP? where can we find this script please? ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] sound problem: pinnacle PCTV USB2 200e
On 9/12/07, Dimitrios [EMAIL PROTECTED] wrote: On Wed, 12 Sep 2007 10:45:53 +0200 Markus Rechberger [EMAIL PROTECTED] wrote: did you use the usbaudio_setup.sh tool for piping audio from the device to your soundcard's DSP? where can we find this script please? it's part of the v4l-dvb-experimental package v4l/scripts/usbaudio_setup.sh Markus ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] Terratec Cinergy USB T XS
2007/9/12, Markus Rechberger [EMAIL PROTECTED]: On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: 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, which could be the reason that makes this drivers to work fine with kernel 2.16.18 and not with 2.16.20 one? if _this_ driver works fine with 2.6.18 then it must be a firmware issue. You might load the driver with the option reg_debug=1 and compare the output of both kernel versions. This might show up the difference immediatelly. Markus I can't load the driver with 2.6.18 because I removed openSuse 10.2 some months ago: I should compile and install this version on Ubuntu in order to try that if needed. Following I report the /var/log/messages on 2.6.20 using reg_debug=1: Sep 12 11:05:49 gandalf kernel: [ 1635.788000] em28xx v4l2 driver version 0.0.1 loaded Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: device is attached to a USB 2.0 bus Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: you're using the experimental/unstable tree from mcentral.de Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: there's also a stable tree available but which is limited to Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: linux =2.6.19.2 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: it's fine to use this driver but keep in mind that it will move Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernelhttp://mcentral.de/hg/%7Emrec/v4l-dvb-kernelas soon as it's Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: proved to be stable Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate settings: 8 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 0, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 1, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 2, max size= 1448 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 3, max size= 2048 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 4, max size= 2304 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 5, max size= 2580 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 6, max size= 2892 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 7, max size= 3072 Sep 12 11:05:49 gandalf kernel: [ 1635.916000] em28xx #0: [ OK] 40 00 00 00 0f 00 01 00 27 Sep 12 11:05:49 gandalf kernel: [ 1635.916000] em28xx #0: [ OK] 40 00 00 00 06 00 01 00 40 Sep 12 11:05:49 gandalf kernel: [ 1635.916000] em28xx #0: [ OK] c0 02 00 00 a0 00 01 00 1a Sep 12 11:05:49 gandalf kernel: [ 1635.916000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:49 gandalf kernel: [ 1635.916000] em28xx #0: [ OK] c0 02 00 00 a0 00 01 00 eb Sep 12 11:05:49 gandalf kernel: [ 1635.916000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:49 gandalf kernel: [ 1635.916000] attach_inform: eeprom detected. Sep 12 11:05:49 gandalf kernel: [ 1635.92] em28xx #0: [ OK] c0 02 00 00 a0 00 01 00 67 Sep 12 11:05:49 gandalf kernel: [ 1635.92] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:49 gandalf kernel: [ 1635.92] em28xx #0: [ OK] 40 02 00 00 a0 00 01 00 00 Sep 12 11:05:49 gandalf kernel: [ 1635.92] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:49 gandalf kernel: [ 1635.92] em28xx #0: [ OK] c0 02 00 00 a0 00 16 00 1a eb 67 95 cd 0c 43 00 c0 12 5c 00 9e 24 6a 34 Sep 12 11:05:49 gandalf kernel: [ 1635.92] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.924000] em28xx #0: [ OK] c0 02 00 00 a0 00 16 00 00 00 06 57 02 0c 00 00 00 00 00 00 00 00 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.924000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.924000] em28xx #0: [ OK] c0 02 00 00 a0 00 16 00 44 00 00 00 f0 10 01 00 00 00 00 00 5b 00 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.924000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.928000] em28xx #0: [ OK] c0 02 00 00 a0 00 16 00 00 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.928000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.928000] em28xx #0: [ OK] c0 02 00 00 a0 00 16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.928000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.932000] em28xx #0: [ OK] c0 02 00 00 a0 00 16 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Sep 12 11:05:50 gandalf kernel: [ 1635.932000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 00 Sep 12 11:05:50
[Em28xx] Terratec Cinergy USB T XS - Working with v4l-dvb-experimental-userptr
Hi Markus, I have finished to try v4l-dvb-experimental-userptr version and now the driver seems to be loaded well, as you can see in dmesg [ 107.30] put tuner! [ 107.30] put_tuner 71! [ 107.30] releasing tuner! [ 112.644000] em28xx v4l2 driver version 0.0.1 loaded [ 112.74] em28xx new video device (0ccd:0043): interface 0, class 255 [ 112.74] em28xx: device is attached to a USB 2.0 bus [ 112.74] em28xx: you're using the experimental/unstable tree from mcentral.de [ 112.74] em28xx: there's also a stable tree available but which is limited to [ 112.74] em28xx: linux =2.6.19.2 [ 112.74] em28xx: it's fine to use this driver but keep in mind that it will move [ 112.74] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's [ 112.74] em28xx: proved to be stable [ 112.74] em28xx #0: Alternate settings: 8 [ 112.74] em28xx #0: Alternate setting 0, max size= 0 [ 112.74] em28xx #0: Alternate setting 1, max size= 0 [ 112.74] em28xx #0: Alternate setting 2, max size= 1448 [ 112.74] em28xx #0: Alternate setting 3, max size= 2048 [ 112.74] em28xx #0: Alternate setting 4, max size= 2304 [ 112.74] em28xx #0: Alternate setting 5, max size= 2580 [ 112.74] em28xx #0: Alternate setting 6, max size= 2892 [ 112.74] em28xx #0: Alternate setting 7, max size= 3072 [ 112.756000] attach_inform: eeprom detected. [ 112.78] em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 43 00 c0 12 5c 00 9e 24 6a 34 [ 112.78] em28xx #0: i2c eeprom 10: 00 00 06 57 02 0c 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 20: 44 00 00 00 f0 10 01 00 00 00 00 00 5b 00 00 00 [ 112.78] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 34 03 54 00 65 00 [ 112.78] em28xx #0: i2c eeprom 70: 72 00 72 00 61 00 54 00 65 00 63 00 20 00 45 00 [ 112.78] em28xx #0: i2c eeprom 80: 6c 00 65 00 63 00 74 00 72 00 6f 00 6e 00 69 00 [ 112.78] em28xx #0: i2c eeprom 90: 63 00 20 00 47 00 6d 00 62 00 48 00 00 00 24 03 [ 112.78] em28xx #0: i2c eeprom a0: 43 00 69 00 6e 00 65 00 72 00 67 00 79 00 20 00 [ 112.78] em28xx #0: i2c eeprom b0: 54 00 20 00 55 00 53 00 42 00 20 00 58 00 53 00 [ 112.78] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] EEPROM ID= 0x9567eb1a [ 112.78] Vendor/Product ID= 0ccd:0043 [ 112.78] No audio on board. [ 112.78] 500mA max power [ 112.78] Table at 0x06, strings=0x249e, 0x346a, 0x [ 112.78] tuner 2-0061: chip found @ 0xc2 (em28xx #0) [ 112.78] attach inform (default): detected I2C address c2 [ 112.78] tuner 0x61: Configuration acknowledged [ 112.78] requesting Xceive 3028 tuner [ 112.78] tuner-core: loading xc3028! [ 112.78] /usr/local/src/v4l-dvb-experimental-userptr/v4l/xc3028- tuner.c: attach request! [ 112.78] tuner-core.c: loaded external driver! [ 112.788000] Loading base firmware: xc3028_init0.i2c.fw [ 113.796000] Loading default analogue TV settings: xc3028_BG_PAL_A2_A.i2c.fw [ 113.816000] ANALOG TV REQUEST [ 113.816000] em28xx #0: Found Terratec Cinergy T XS [ 113.816000] usbcore: registered new interface driver em28xx [ 113.836000] em2880-dvb.c: DVB Init [ 113.836000] Loading base firmware: xc3028_8MHz_init0.i2c.fw [ 114.84] Loading default dtv settings: xc3028_DTV8_2633.i2c.fw [ 114.86] Sending extra call for Digital TV! [ 114.964000] /usr/local/src/v4l-dvb-experimental-userptr/v4l/xc3028- tuner.c: attach request! [ 114.972000] DVB: registering new adapter (em2880 DVB-T). [ 114.972000] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)... [ 114.976000] Em28xx: Initialized (Em2880 DVB Extension) extension By this way I suppose it is not a firmware problem (although I haven't tried to use the dvb adapter yet). However neither the stable nor the experimental version work in this moment with kernel 2.6.20 I hope it can be useful for the driver development Thanks a lot for your support, Valerio ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] Terratec Cinergy USB T XS - Working with v4l-dvb-experimental-userptr
2007/9/12, Markus Rechberger [EMAIL PROTECTED]: On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: Hi Markus, I have finished to try v4l-dvb-experimental-userptr version and now the driver seems to be loaded well, as you can see in dmesg [ 107.30] put tuner! [ 107.30] put_tuner 71! [ 107.30] releasing tuner! [ 112.644000] em28xx v4l2 driver version 0.0.1 loaded [ 112.74] em28xx new video device (0ccd:0043): interface 0, class 255 [ 112.74] em28xx: device is attached to a USB 2.0 bus [ 112.74] em28xx: you're using the experimental/unstable tree from mcentral.de [ 112.74] em28xx: there's also a stable tree available but which is limited to [ 112.74] em28xx: linux =2.6.19.2 [ 112.74] em28xx: it's fine to use this driver but keep in mind that it will move [ 112.74] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's [ 112.74] em28xx: proved to be stable [ 112.74] em28xx #0: Alternate settings: 8 [ 112.74] em28xx #0: Alternate setting 0, max size= 0 [ 112.74] em28xx #0: Alternate setting 1, max size= 0 [ 112.74] em28xx #0: Alternate setting 2, max size= 1448 [ 112.74] em28xx #0: Alternate setting 3, max size= 2048 [ 112.74] em28xx #0: Alternate setting 4, max size= 2304 [ 112.74] em28xx #0: Alternate setting 5, max size= 2580 [ 112.74] em28xx #0: Alternate setting 6, max size= 2892 [ 112.74] em28xx #0: Alternate setting 7, max size= 3072 [ 112.756000] attach_inform: eeprom detected. [ 112.78] em28xx #0: i2c eeprom 00: 1a eb 67 95 cd 0c 43 00 c0 12 5c 00 9e 24 6a 34 [ 112.78] em28xx #0: i2c eeprom 10: 00 00 06 57 02 0c 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 20: 44 00 00 00 f0 10 01 00 00 00 00 00 5b 00 00 00 [ 112.78] em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 20 01 01 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 00 00 00 34 03 54 00 65 00 [ 112.78] em28xx #0: i2c eeprom 70: 72 00 72 00 61 00 54 00 65 00 63 00 20 00 45 00 [ 112.78] em28xx #0: i2c eeprom 80: 6c 00 65 00 63 00 74 00 72 00 6f 00 6e 00 69 00 [ 112.78] em28xx #0: i2c eeprom 90: 63 00 20 00 47 00 6d 00 62 00 48 00 00 00 24 03 [ 112.78] em28xx #0: i2c eeprom a0: 43 00 69 00 6e 00 65 00 72 00 67 00 79 00 20 00 [ 112.78] em28xx #0: i2c eeprom b0: 54 00 20 00 55 00 53 00 42 00 20 00 58 00 53 00 [ 112.78] em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 [ 112.78] EEPROM ID= 0x9567eb1a [ 112.78] Vendor/Product ID= 0ccd:0043 [ 112.78] No audio on board. [ 112.78] 500mA max power [ 112.78] Table at 0x06, strings=0x249e, 0x346a, 0x [ 112.78] tuner 2-0061: chip found @ 0xc2 (em28xx #0) [ 112.78] attach inform (default): detected I2C address c2 [ 112.78] tuner 0x61: Configuration acknowledged [ 112.78] requesting Xceive 3028 tuner [ 112.78] tuner-core: loading xc3028! [ 112.78] /usr/local/src/v4l-dvb-experimental-userptr/v4l/xc3028- tuner.c: attach request! [ 112.78] tuner-core.c: loaded external driver! [ 112.788000] Loading base firmware: xc3028_init0.i2c.fw [ 113.796000] Loading default analogue TV settings: xc3028_BG_PAL_A2_A.i2c.fw [ 113.816000] ANALOG TV REQUEST [ 113.816000] em28xx #0: Found Terratec Cinergy T XS [ 113.816000] usbcore: registered new interface driver em28xx [ 113.836000] em2880-dvb.c: DVB Init [ 113.836000] Loading base firmware: xc3028_8MHz_init0.i2c.fw [ 114.84] Loading default dtv settings: xc3028_DTV8_2633.i2c.fw [ 114.86] Sending extra call for Digital TV! [ 114.964000] /usr/local/src/v4l-dvb-experimental-userptr/v4l/xc3028- tuner.c: attach request! [ 114.972000] DVB: registering new adapter (em2880 DVB-T). [ 114.972000] DVB: registering frontend 0 (Zarlink ZL10353 DVB-T)... [ 114.976000] Em28xx: Initialized (Em2880 DVB Extension) extension By this way I suppose it is not a firmware problem (although I haven't tried to use the dvb adapter yet). However neither the stable nor the experimental version work in this moment with kernel 2.6.20 I hope it can be useful for the driver development Thanks a lot for your support, Hi, the userptr version breaks several devices, because of that it's in a separate repository, you might try to
Re: [Em28xx] Terratec Cinergy USB T XS
On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: I can't load the driver with 2.6.18 because I removed openSuse 10.2 some months ago: I should compile and install this version on Ubuntu in order to try that if needed. Following I report the /var/log/messages on 2.6.20 using reg_debug=1: Sep 12 11:05:49 gandalf kernel: [ 1635.788000] em28xx v4l2 driver version 0.0.1 loaded Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: device is attached to a USB 2.0 bus Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: you're using the experimental/unstable tree from mcentral.de Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: there's also a stable tree available but which is limited to Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: linux =2.6.19.2 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: it's fine to use this driver but keep in mind that it will move Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: proved to be stable Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate settings: 8 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 0, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 1, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 2, max size= 1448 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 3, max size= 2048 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 4, max size= 2304 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 5, max size= 2580 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 6, max size= 2892 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 7, max size= 3072 ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.952000] EEPROM ID= 0x9567eb1a Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Vendor/Product ID= 0ccd:0043 Sep 12 11:05:50 gandalf kernel: [ 1635.952000] No audio on board. Sep 12 11:05:50 gandalf kernel: [ 1635.952000] 500mA max power Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Table at 0x06, strings=0x249e, 0x346a, 0x ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.956000] tuner 2-0061: chip found @ 0xc2 (em28xx #0) Sep 12 11:05:50 gandalf kernel: [ 1635.96] attach inform (default): detected I2C address c2 Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel /v4l/tuner-core.c: setting tuner callback Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback I don't see any sign of the xc3028 driver doing anything here, which probably isn't a good sign. It doesn't even seem to be getting to the stage of trying to load the firmware. Sep 12 11:05:50 gandalf kernel: [ 1635.972000] em28xx #0: Found Terratec Cinergy T XS Sep 12 11:05:50 gandalf kernel: [ 1635.976000] usbcore: registered new interface driver em28xx Sep 12 11:05:50 gandalf kernel: [ 1636.00] em2880-dvb.c: DVB Init There ought to be a GPIO write here, but there isn't. It's probably related to the problem with the tuner code, since the GPIO write for your device is triggered by that. After looking at the code, it looks like, since your card is DVB-T only, the driver doesn't bother setting up the tuner driver for analog use. Unfortunately, the em2880-dvb driver uses an analog API (VIDIOC_INT_S_TUNER_MODE) to get the xc3028 tuner driver to switch modes (and call back into the em28xx driver to do the GPIO twiddling that enables the DVB-T demodulator), this is a problem. As a result, the GPIO twiddling doesn't get done, communication with the DVB-T demodulator fails and the driver bails out. Edit em28xx_set_tuner in linux/drivers/media/video/em28xx/em28xx-i2c.c to remove the dev-dev_modes != EM28XX_DVB and recompile - things should work better. (The reason v4l-dvb-experimental-userptr works is that it's based on an older version of the code before this was added.) Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] 40 03 00 00 1e 00 01 00 7f Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 10 Sep 12 11:05:50 gandalf kernel: [ 1636.104000] FIXME:em28xx_i2c_send_bytes(1e): write failed: Sep 12 11:05:50 gandalf kernel: [ 1636.104000] === Sep 12 11:05:50 gandalf kernel: [ 1636.104000] 7f Sep 12 11:05:50 gandalf kernel: [ 1636.104000] ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] Terratec Cinergy USB T XS
Hi, On 9/12/07, Aidan Thornton [EMAIL PROTECTED] wrote: On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: I can't load the driver with 2.6.18 because I removed openSuse 10.2 some months ago: I should compile and install this version on Ubuntu in order to try that if needed. Following I report the /var/log/messages on 2.6.20 using reg_debug=1: Sep 12 11:05:49 gandalf kernel: [ 1635.788000] em28xx v4l2 driver version 0.0.1 loaded Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: device is attached to a USB 2.0 bus Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: you're using the experimental/unstable tree from mcentral.de Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: there's also a stable tree available but which is limited to Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: linux =2.6.19.2 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: it's fine to use this driver but keep in mind that it will move Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: proved to be stable Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate settings: 8 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 0, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 1, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 2, max size= 1448 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 3, max size= 2048 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 4, max size= 2304 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 5, max size= 2580 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 6, max size= 2892 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 7, max size= 3072 ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.952000] EEPROM ID= 0x9567eb1a Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Vendor/Product ID= 0ccd:0043 Sep 12 11:05:50 gandalf kernel: [ 1635.952000] No audio on board. Sep 12 11:05:50 gandalf kernel: [ 1635.952000] 500mA max power Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Table at 0x06, strings=0x249e, 0x346a, 0x ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.956000] tuner 2-0061: chip found @ 0xc2 (em28xx #0) Sep 12 11:05:50 gandalf kernel: [ 1635.96] attach inform (default): detected I2C address c2 Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel /v4l/tuner-core.c: setting tuner callback Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback I don't see any sign of the xc3028 driver doing anything here, which probably isn't a good sign. It doesn't even seem to be getting to the stage of trying to load the firmware. yes you're right, could you guys check if tuner-xc3028 is loaded? lsmod | grep xc3028 Markus Sep 12 11:05:50 gandalf kernel: [ 1635.972000] em28xx #0: Found Terratec Cinergy T XS Sep 12 11:05:50 gandalf kernel: [ 1635.976000] usbcore: registered new interface driver em28xx Sep 12 11:05:50 gandalf kernel: [ 1636.00] em2880-dvb.c: DVB Init There ought to be a GPIO write here, but there isn't. It's probably related to the problem with the tuner code, since the GPIO write for your device is triggered by that. After looking at the code, it looks like, since your card is DVB-T only, the driver doesn't bother setting up the tuner driver for analog use. Unfortunately, the em2880-dvb driver uses an analog API (VIDIOC_INT_S_TUNER_MODE) to get the xc3028 tuner driver to switch modes (and call back into the em28xx driver to do the GPIO twiddling that enables the DVB-T demodulator), this is a problem. As a result, the GPIO twiddling doesn't get done, communication with the DVB-T demodulator fails and the driver bails out. Edit em28xx_set_tuner in linux/drivers/media/video/em28xx/em28xx-i2c.c to remove the dev-dev_modes != EM28XX_DVB and recompile - things should work better. (The reason v4l-dvb-experimental-userptr works is that it's based on an older version of the code before this was added.) Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] 40 03 00 00 1e 00 01 00 7f Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 10 Sep 12 11:05:50 gandalf kernel: [ 1636.104000] FIXME:em28xx_i2c_send_bytes(1e): write failed: Sep 12 11:05:50 gandalf kernel: [ 1636.104000] === Sep 12 11:05:50 gandalf kernel: [ 1636.104000] 7f Sep 12 11:05:50 gandalf kernel: [ 1636.104000] -- Markus
Re: [Em28xx] Terratec Cinergy USB T XS
2007/9/12, Markus Rechberger [EMAIL PROTECTED]: Hi, On 9/12/07, Aidan Thornton [EMAIL PROTECTED] wrote: On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: I can't load the driver with 2.6.18 because I removed openSuse 10.2some months ago: I should compile and install this version on Ubuntu in order to try that if needed. Following I report the /var/log/messages on 2.6.20 using reg_debug=1: Sep 12 11:05:49 gandalf kernel: [ 1635.788000] em28xx v4l2 driver version 0.0.1 loaded Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: device is attached to a USB 2.0 bus Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: you're using the experimental/unstable tree from mcentral.de Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: there's also a stable tree available but which is limited to Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: linux = 2.6.19.2 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: it's fine to use this driver but keep in mind that it will move Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: proved to be stable Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate settings: 8 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 0, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 1, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 2, max size= 1448 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 3, max size= 2048 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 4, max size= 2304 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 5, max size= 2580 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 6, max size= 2892 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 7, max size= 3072 ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.952000] EEPROM ID= 0x9567eb1a Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Vendor/Product ID= 0ccd:0043 Sep 12 11:05:50 gandalf kernel: [ 1635.952000] No audio on board. Sep 12 11:05:50 gandalf kernel: [ 1635.952000] 500mA max power Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Table at 0x06, strings=0x249e, 0x346a, 0x ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.956000] tuner 2-0061: chip found @ 0xc2 (em28xx #0) Sep 12 11:05:50 gandalf kernel: [ 1635.96] attach inform (default): detected I2C address c2 Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel /v4l/tuner-core.c: setting tuner callback Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback I don't see any sign of the xc3028 driver doing anything here, which probably isn't a good sign. It doesn't even seem to be getting to the stage of trying to load the firmware. yes you're right, could you guys check if tuner-xc3028 is loaded? lsmod | grep xc3028 Markus Sep 12 11:05:50 gandalf kernel: [ 1635.972000] em28xx #0: Found Terratec Cinergy T XS Sep 12 11:05:50 gandalf kernel: [ 1635.976000] usbcore: registered new interface driver em28xx Sep 12 11:05:50 gandalf kernel: [ 1636.00] em2880-dvb.c: DVB Init There ought to be a GPIO write here, but there isn't. It's probably related to the problem with the tuner code, since the GPIO write for your device is triggered by that. After looking at the code, it looks like, since your card is DVB-T only, the driver doesn't bother setting up the tuner driver for analog use. Unfortunately, the em2880-dvb driver uses an analog API (VIDIOC_INT_S_TUNER_MODE) to get the xc3028 tuner driver to switch modes (and call back into the em28xx driver to do the GPIO twiddling that enables the DVB-T demodulator), this is a problem. As a result, the GPIO twiddling doesn't get done, communication with the DVB-T demodulator fails and the driver bails out. Edit em28xx_set_tuner in linux/drivers/media/video/em28xx/em28xx-i2c.c to remove the dev-dev_modes != EM28XX_DVB and recompile - things should work better. (The reason v4l-dvb-experimental-userptr works is that it's based on an older version of the code before this was added.) Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] 40 03 00 00 1e 00 01 00 7f Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] c0 00 00 00 05 00 01 00 10 Sep 12 11:05:50 gandalf kernel: [ 1636.104000] FIXME:em28xx_i2c_send_bytes(1e): write failed: Sep 12 11:05:50 gandalf kernel: [ 1636.104000]
Re: [Em28xx] Terratec Cinergy USB T XS
On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: 2007/9/12, Markus Rechberger [EMAIL PROTECTED]: Hi, On 9/12/07, Aidan Thornton [EMAIL PROTECTED] wrote: On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: I can't load the driver with 2.6.18 because I removed openSuse 10.2some months ago: I should compile and install this version on Ubuntu in order to try that if needed. Following I report the /var/log/messages on 2.6.20 using reg_debug=1: Sep 12 11:05:49 gandalf kernel: [ 1635.788000] em28xx v4l2 driver version 0.0.1 loaded Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: device is attached to a USB 2.0 bus Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: you're using the experimental/unstable tree from mcentral.de Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: there's also a stable tree available but which is limited to Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: linux = 2.6.19.2 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: it's fine to use this driver but keep in mind that it will move Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: proved to be stable Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate settings: 8 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 0, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 1, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 2, max size= 1448 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 3, max size= 2048 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 4, max size= 2304 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 5, max size= 2580 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 6, max size= 2892 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 7, max size= 3072 ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.952000] EEPROM ID= 0x9567eb1a Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Vendor/Product ID= 0ccd:0043 Sep 12 11:05:50 gandalf kernel: [ 1635.952000] No audio on board. Sep 12 11:05:50 gandalf kernel: [ 1635.952000] 500mA max power Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Table at 0x06, strings=0x249e, 0x346a, 0x ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.956000] tuner 2-0061: chip found @ 0xc2 (em28xx #0) Sep 12 11:05:50 gandalf kernel: [ 1635.96] attach inform (default): detected I2C address c2 Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel /v4l/tuner-core.c: setting tuner callback Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback I don't see any sign of the xc3028 driver doing anything here, which probably isn't a good sign. It doesn't even seem to be getting to the stage of trying to load the firmware. yes you're right, could you guys check if tuner-xc3028 is loaded? lsmod | grep xc3028 Markus Sep 12 11:05:50 gandalf kernel: [ 1635.972000] em28xx #0: Found Terratec Cinergy T XS Sep 12 11:05:50 gandalf kernel: [ 1635.976000] usbcore: registered new interface driver em28xx Sep 12 11:05:50 gandalf kernel: [ 1636.00] em2880-dvb.c: DVB Init There ought to be a GPIO write here, but there isn't. It's probably related to the problem with the tuner code, since the GPIO write for your device is triggered by that. After looking at the code, it looks like, since your card is DVB-T only, the driver doesn't bother setting up the tuner driver for analog use. Unfortunately, the em2880-dvb driver uses an analog API (VIDIOC_INT_S_TUNER_MODE) to get the xc3028 tuner driver to switch modes (and call back into the em28xx driver to do the GPIO twiddling that enables the DVB-T demodulator), this is a problem. As a result, the GPIO twiddling doesn't get done, communication with the DVB-T demodulator fails and the driver bails out. Edit em28xx_set_tuner in linux/drivers/media/video/em28xx/em28xx-i2c.c to remove the dev-dev_modes != EM28XX_DVB and recompile - things should work better. (The reason v4l-dvb-experimental-userptr works is that it's based on an older version of the code before this was added.) Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] 40 03 00 00 1e 00 01 00 7f Sep 12 11:05:50 gandalf kernel: [ 1636.104000] em28xx #0: [ OK] c0 00 00 00 05
Re: [Em28xx] Terratec Cinergy USB T XS
Markus Rechberger ha scritto: On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: 2007/9/12, Markus Rechberger [EMAIL PROTECTED]: Hi, On 9/12/07, Aidan Thornton [EMAIL PROTECTED] wrote: On 9/12/07, Valerio Bontempi [EMAIL PROTECTED] wrote: I can't load the driver with 2.6.18 because I removed openSuse 10.2some months ago: I should compile and install this version on Ubuntu in order to try that if needed. Following I report the /var/log/messages on 2.6.20 using reg_debug=1: Sep 12 11:05:49 gandalf kernel: [ 1635.788000] em28xx v4l2 driver version 0.0.1 loaded Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: device is attached to a USB 2.0 bus Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: you're using the experimental/unstable tree from mcentral.de Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: there's also a stable tree available but which is limited to Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: linux = 2.6.19.2 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: it's fine to use this driver but keep in mind that it will move Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: to http://mcentral.de/hg/~mrec/v4l-dvb-kernel as soon as it's Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx: proved to be stable Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate settings: 8 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 0, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 1, max size= 0 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 2, max size= 1448 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 3, max size= 2048 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 4, max size= 2304 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 5, max size= 2580 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 6, max size= 2892 Sep 12 11:05:49 gandalf kernel: [ 1635.904000] em28xx #0: Alternate setting 7, max size= 3072 ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.952000] EEPROM ID= 0x9567eb1a Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Vendor/Product ID= 0ccd:0043 Sep 12 11:05:50 gandalf kernel: [ 1635.952000] No audio on board. Sep 12 11:05:50 gandalf kernel: [ 1635.952000] 500mA max power Sep 12 11:05:50 gandalf kernel: [ 1635.952000] Table at 0x06, strings=0x249e, 0x346a, 0x ...snip... Sep 12 11:05:50 gandalf kernel: [ 1635.956000] tuner 2-0061: chip found @ 0xc2 (em28xx #0) Sep 12 11:05:50 gandalf kernel: [ 1635.96] attach inform (default): detected I2C address c2 Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel /v4l/tuner-core.c: setting tuner callback Sep 12 11:05:50 gandalf kernel: [ 1635.96] /usr/local/src/v4l-dvb-kernel/v4l/tuner-core.c: setting tuner callback I don't see any sign of the xc3028 driver doing anything here, which probably isn't a good sign. It doesn't even seem to be getting to the stage of trying to load the firmware. yes you're right, could you guys check if tuner-xc3028 is loaded? lsmod | grep xc3028 Markus Sep 12 11:05:50 gandalf kernel: [ 1635.972000] em28xx #0: Found Terratec Cinergy T XS Sep 12 11:05:50 gandalf kernel: [ 1635.976000] usbcore: registered new interface driver em28xx Sep 12 11:05:50 gandalf kernel: [ 1636.00] em2880-dvb.c: DVB Init There ought to be a GPIO write here, but there isn't. It's probably related to the problem with the tuner code, since the GPIO write for your device is triggered by that. After looking at the code, it looks like, since your card is DVB-T only, the driver doesn't bother setting up the tuner driver for analog use. Unfortunately, the em2880-dvb driver uses an analog API (VIDIOC_INT_S_TUNER_MODE) to get the xc3028 tuner driver to switch modes (and call back into the em28xx driver to do the GPIO twiddling that enables the DVB-T demodulator), this is a problem. As a result, the GPIO twiddling doesn't get done, communication with the DVB-T demodulator fails and the driver bails out. Edit em28xx_set_tuner in linux/drivers/media/video/em28xx/em28xx-i2c.c to remove the dev-dev_modes != EM28XX_DVB and recompile - things should work better. (The reason v4l-dvb-experimental-userptr works is that it's based on an older version of the code before this was added.)
Re: [Em28xx] ehci_hcd map_single: unable to map unsafe buffer on a standard NSLU2
Markus Rechberger a écrit : On 9/11/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/10/07, David Anne-Sophie [EMAIL PROTECTED] wrote: David Anne-Sophie a écrit : Hello all, I am trying to use my hybrid USB tuner on my NSLU2. Tuner=Terratec cinergy XS Driver=http://mcentral.de/wiki/index.php/Em2880 I plugged it directly to the DISK-2 connector. On DISK-1 there is a USB hard-disk that contains the filesystems. The driver compiles fine on the standard debian etch kernel, and loads perfectly. I just did a minor patch of this driver around a udelay(2500); - udelay(2000);udelay(500); (2500 is a too big value for the ARM architecture, see bad_udelay). When I try tzap to activate the dvb-t stream, I get those errors: ehci_hcd :00:01.2: alloc_safe_buffer: could not alloc dma memory (size=36096) ehci_hcd :00:01.2: map_single: unable to map unsafe buffer ffc2c000! many times (I think one per USB packet). And the tuner does not stream anything... I did not modify anything in the NSLU2 (neither RAM or frequency), just upgraded to debian etch arm architecture following the nslu2-linux.org tutorials. Do you know what it means and how to solve the issue? Do not hesitate to ask for specific information. Thanks! Cheers, David. [EMAIL PROTECTED] ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx I have some informations that can help you to resolve my problem. These informations comes from the newlist of debian-arm : In this forum, I said that the driver works correctly on a PC with ubuntu, and the response is : Working on a PC does not mean the driver is correct. On a PC physical addresses match the kernel's point of view in general, while on the arm everything goes through interesting mappings, which make is essential for the driver to correctly use readX/writeX calls along with ioremap calls. Any attemps to directly access anything will fail on the arm while it almost always works on a PC. Not sure quite how that might impact a USB device, but even there the driver has to do DMA setup with corrected addresses, which again is not necesary on a PC but is on the arm. i'm at the suse conference this week there are some interesting people around who're into the usb subsystem. The em28xx driver makes use of the usb subsystem (which also includes allocation of memory) I'll try to get some answers tomorrow about this issue. Markus Hello Markus, Do you have news about my problem ? in em28xx.h there's a static defined value for the number of videopackets #define EM28XX_NUM_PACKETS 40 try to lower that value by about the half or less this will allocate less memory in the end. I'm not sure if that might out .. although that was the only idea which came up after the talk yesterday. Let me know if it works out otherwise I'll have a further discussion about it with the usb guys. Markus Hello Markus, I tried your patch. I set the value to 20. Now tzap seems to work correctly (tzap -r -c channels.conf TF1, for exemple) and I don't have any error with dmesg. But, when i try cat / /dev/dvb/adapter0/dvr0 test.ts/, the file is still empty ? and with cp /dev/dvb/adapter0/dvr0 foo, the command doesn't leave immediatly, I must break the command to leave ? Do you have an idea ? Thanks David ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] ehci_hcd map_single: unable to map unsafe buffer on a standard NSLU2
On 9/12/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/11/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/10/07, David Anne-Sophie [EMAIL PROTECTED] wrote: David Anne-Sophie a écrit : Hello all, I am trying to use my hybrid USB tuner on my NSLU2. Tuner=Terratec cinergy XS Driver=http://mcentral.de/wiki/index.php/Em2880 I plugged it directly to the DISK-2 connector. On DISK-1 there is a USB hard-disk that contains the filesystems. The driver compiles fine on the standard debian etch kernel, and loads perfectly. I just did a minor patch of this driver around a udelay(2500); - udelay(2000);udelay(500); (2500 is a too big value for the ARM architecture, see bad_udelay). When I try tzap to activate the dvb-t stream, I get those errors: ehci_hcd :00:01.2: alloc_safe_buffer: could not alloc dma memory (size=36096) ehci_hcd :00:01.2: map_single: unable to map unsafe buffer ffc2c000! many times (I think one per USB packet). And the tuner does not stream anything... I did not modify anything in the NSLU2 (neither RAM or frequency), just upgraded to debian etch arm architecture following the nslu2-linux.org tutorials. Do you know what it means and how to solve the issue? Do not hesitate to ask for specific information. Thanks! Cheers, David. [EMAIL PROTECTED] ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx I have some informations that can help you to resolve my problem. These informations comes from the newlist of debian-arm : In this forum, I said that the driver works correctly on a PC with ubuntu, and the response is : Working on a PC does not mean the driver is correct. On a PC physical addresses match the kernel's point of view in general, while on the arm everything goes through interesting mappings, which make is essential for the driver to correctly use readX/writeX calls along with ioremap calls. Any attemps to directly access anything will fail on the arm while it almost always works on a PC. Not sure quite how that might impact a USB device, but even there the driver has to do DMA setup with corrected addresses, which again is not necesary on a PC but is on the arm. i'm at the suse conference this week there are some interesting people around who're into the usb subsystem. The em28xx driver makes use of the usb subsystem (which also includes allocation of memory) I'll try to get some answers tomorrow about this issue. Markus Hello Markus, Do you have news about my problem ? in em28xx.h there's a static defined value for the number of videopackets #define EM28XX_NUM_PACKETS 40 try to lower that value by about the half or less this will allocate less memory in the end. I'm not sure if that might out .. although that was the only idea which came up after the talk yesterday. Let me know if it works out otherwise I'll have a further discussion about it with the usb guys. Markus Hello Markus, I tried your patch. I set the value to 20. Now tzap seems to work correctly (tzap -r -c channels.conf TF1, for exemple) and I don't have any error with dmesg. But, when i try cat / /dev/dvb/adapter0/dvr0 test.ts/, the file is still empty ? and with cp /dev/dvb/adapter0/dvr0 foo, the command doesn't leave immediatly, I must break the command to leave ? Do you have an idea ? Could you try to dump the stream with mplayer? If this doesn't work out we'll add some debug for the usb packets. I only have 2 days left to discuss this issue with the right guys here. Markus ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] ehci_hcd map_single: unable to map unsafe buffer on a standard NSLU2
Markus Rechberger a écrit : On 9/12/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/11/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/10/07, David Anne-Sophie [EMAIL PROTECTED] wrote: David Anne-Sophie a écrit : Hello all, I am trying to use my hybrid USB tuner on my NSLU2. Tuner=Terratec cinergy XS Driver=http://mcentral.de/wiki/index.php/Em2880 I plugged it directly to the DISK-2 connector. On DISK-1 there is a USB hard-disk that contains the filesystems. The driver compiles fine on the standard debian etch kernel, and loads perfectly. I just did a minor patch of this driver around a udelay(2500); - udelay(2000);udelay(500); (2500 is a too big value for the ARM architecture, see bad_udelay). When I try tzap to activate the dvb-t stream, I get those errors: ehci_hcd :00:01.2: alloc_safe_buffer: could not alloc dma memory (size=36096) ehci_hcd :00:01.2: map_single: unable to map unsafe buffer ffc2c000! many times (I think one per USB packet). And the tuner does not stream anything... I did not modify anything in the NSLU2 (neither RAM or frequency), just upgraded to debian etch arm architecture following the nslu2-linux.org tutorials. Do you know what it means and how to solve the issue? Do not hesitate to ask for specific information. Thanks! Cheers, David. [EMAIL PROTECTED] ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx I have some informations that can help you to resolve my problem. These informations comes from the newlist of debian-arm : In this forum, I said that the driver works correctly on a PC with ubuntu, and the response is : Working on a PC does not mean the driver is correct. On a PC physical addresses match the kernel's point of view in general, while on the arm everything goes through interesting mappings, which make is essential for the driver to correctly use readX/writeX calls along with ioremap calls. Any attemps to directly access anything will fail on the arm while it almost always works on a PC. Not sure quite how that might impact a USB device, but even there the driver has to do DMA setup with corrected addresses, which again is not necesary on a PC but is on the arm. i'm at the suse conference this week there are some interesting people around who're into the usb subsystem. The em28xx driver makes use of the usb subsystem (which also includes allocation of memory) I'll try to get some answers tomorrow about this issue. Markus Hello Markus, Do you have news about my problem ? in em28xx.h there's a static defined value for the number of videopackets #define EM28XX_NUM_PACKETS 40 try to lower that value by about the half or less this will allocate less memory in the end. I'm not sure if that might out .. although that was the only idea which came up after the talk yesterday. Let me know if it works out otherwise I'll have a further discussion about it with the usb guys. Markus Hello Markus, I tried your patch. I set the value to 20. Now tzap seems to work correctly (tzap -r -c channels.conf TF1, for exemple) and I don't have any error with dmesg. But, when i try cat / /dev/dvb/adapter0/dvr0 test.ts/, the file is still empty ? and with cp /dev/dvb/adapter0/dvr0 foo, the command doesn't leave immediatly, I must break the command to leave ? Do you have an idea ? Could you try to dump the stream with mplayer? If this doesn't work out we'll add some debug for the usb packets. I only have 2 days left to discuss this issue with the right guys here. Markus Sorry, but it is impossible to use mplayer on a nslu2. It doesn't have a video card. I have only a ssh connection. You can see some informations about it here : http://www.nslu2-linux.org/ For information, the scan command doesn't work too. Thanks David ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
Re: [Em28xx] ehci_hcd map_single: unable to map unsafe buffer on a standard NSLU2
On 9/13/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/12/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/11/07, David Anne-Sophie [EMAIL PROTECTED] wrote: Markus Rechberger a écrit : On 9/10/07, David Anne-Sophie [EMAIL PROTECTED] wrote: David Anne-Sophie a écrit : Hello all, I am trying to use my hybrid USB tuner on my NSLU2. Tuner=Terratec cinergy XS Driver=http://mcentral.de/wiki/index.php/Em2880 I plugged it directly to the DISK-2 connector. On DISK-1 there is a USB hard-disk that contains the filesystems. The driver compiles fine on the standard debian etch kernel, and loads perfectly. I just did a minor patch of this driver around a udelay(2500); - udelay(2000);udelay(500); (2500 is a too big value for the ARM architecture, see bad_udelay). When I try tzap to activate the dvb-t stream, I get those errors: ehci_hcd :00:01.2: alloc_safe_buffer: could not alloc dma memory (size=36096) ehci_hcd :00:01.2: map_single: unable to map unsafe buffer ffc2c000! many times (I think one per USB packet). And the tuner does not stream anything... I did not modify anything in the NSLU2 (neither RAM or frequency), just upgraded to debian etch arm architecture following the nslu2-linux.org tutorials. Do you know what it means and how to solve the issue? Do not hesitate to ask for specific information. Thanks! Cheers, David. [EMAIL PROTECTED] ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx I have some informations that can help you to resolve my problem. These informations comes from the newlist of debian-arm : In this forum, I said that the driver works correctly on a PC with ubuntu, and the response is : Working on a PC does not mean the driver is correct. On a PC physical addresses match the kernel's point of view in general, while on the arm everything goes through interesting mappings, which make is essential for the driver to correctly use readX/writeX calls along with ioremap calls. Any attemps to directly access anything will fail on the arm while it almost always works on a PC. Not sure quite how that might impact a USB device, but even there the driver has to do DMA setup with corrected addresses, which again is not necesary on a PC but is on the arm. i'm at the suse conference this week there are some interesting people around who're into the usb subsystem. The em28xx driver makes use of the usb subsystem (which also includes allocation of memory) I'll try to get some answers tomorrow about this issue. Markus Hello Markus, Do you have news about my problem ? in em28xx.h there's a static defined value for the number of videopackets #define EM28XX_NUM_PACKETS 40 try to lower that value by about the half or less this will allocate less memory in the end. I'm not sure if that might out .. although that was the only idea which came up after the talk yesterday. Let me know if it works out otherwise I'll have a further discussion about it with the usb guys. Markus Hello Markus, I tried your patch. I set the value to 20. Now tzap seems to work correctly (tzap -r -c channels.conf TF1, for exemple) and I don't have any error with dmesg. But, when i try cat / /dev/dvb/adapter0/dvr0 test.ts/, the file is still empty ? and with cp /dev/dvb/adapter0/dvr0 foo, the command doesn't leave immediatly, I must break the command to leave ? Do you have an idea ? Could you try to dump the stream with mplayer? If this doesn't work out we'll add some debug for the usb packets. I only have 2 days left to discuss this issue with the right guys here. Markus Sorry, but it is impossible to use mplayer on a nslu2. It doesn't have a video card. I have only a ssh connection. You can see some informations about it here : http://www.nslu2-linux.org/ For information, the scan command doesn't work too. The scan command is sufficient. Could you load the em28xx driver with reg_debug=1 and try to scan for channels with scan -vvv frequencymap Thanks, Markus ___ Em28xx mailing list Em28xx@mcentral.de http://mcentral.de/mailman/listinfo/em28xx
