Hi Jorge, On 6/14/07, Jorge Cisneros <jorgecis@xxxxxxxxx> wrote: > Hi, > > I follow the messange in > http://www.mail-archive.com/em28xx@xxxxxxxxxxx/msg00043.html, but my card > is not working > > My system is gentoo 64 bits Intel pentium dual core > Kernel 2.6.20 > The driver load with any error > > Module > em28xx 92728 0 > compat_ioctl32 8064 1 em28xx > ir_common 36100 1 em28xx > videodev 25856 1 em28xx > v4l2_common 17664 3 em28xx,compat_ioctl32,videodev > v4l1_compat 11524 2 em28xx,videodev > tveeprom 16656 1 em28xx > > > The syslog show > Jun 14 13:17:04 tux kernel: usb 1-7: new high speed USB device using > ehci_hcd an > d address 7 > Jun 14 13:17:04 tux kernel: usb 1-7: configuration #1 chosen from 1 choice > Jun 14 13:17:04 tux kernel: em28xx new video device (2304:0227): interface > 0, cl > ass 255 > Jun 14 13:17:04 tux kernel: em28xx: device is attached to a USB 2.0 bus > Jun 14 13:17:04 tux kernel: em28xx: you're using the experimental/unstable > tree > from mcentral.de > Jun 14 13:17:04 tux kernel: em28xx: there's also a stable tree available but > whi > ch is limited to > Jun 14 13:17:04 tux kernel: em28xx: linux <=2.6.19.2 > Jun 14 13:17:04 tux kernel: em28xx: it's fine to use this driver but keep in > min > Jun 14 13:17:04 tux kernel: em28xx: to > http://mcentral.de/hg/~mrec/v4l-dvb-kerne > l as soon as it's > Jun 14 13:17:04 tux kernel: em28xx: proved to be stable > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate settings: 8 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 0, max size= 0 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 1, max size= 0 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 2, max size= 1448 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 3, max size= 2048 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 4, max size= 2304 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 5, max size= 2580 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 6, max size= 2892 > Jun 14 13:17:04 tux kernel: em28xx #0: Alternate setting 7, max size= 3072 > Jun 14 13:17:04 tux kernel: input: em2880/em2870 remote control as > /class/input/ > input5 > Jun 14 13:17:04 tux kernel: em28xx-input.c: remote control handler attached > Jun 14 13:17:04 tux kernel: attach_inform: eeprom detected. > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 00: 1a eb 67 95 04 23 27 > 02 d0 > 12 5c 03 8e 16 a4 1c > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 10: 6a 24 27 57 46 07 01 > 00 00 > 00 00 00 00 00 00 00 > > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 20: 46 00 01 00 f0 10 02 > 00 b8 > 00 00 00 5b 1c 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 30: 00 00 20 40 20 80 02 > 20 01 > 01 00 00 00 00 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 40: 00 00 00 00 00 00 00 > 00 00 > 00 00 00 00 00 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 50: 00 00 00 00 00 00 00 > 00 00 > 00 00 00 00 00 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 60: 00 00 00 00 00 00 00 > 00 00 > 00 24 03 50 00 69 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 70: 6e 00 6e 00 61 00 63 > 00 6c > 00 65 00 20 00 53 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 80: 79 00 73 00 74 00 65 > 00 6d > 00 73 00 00 00 16 03 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom 90: 50 00 43 00 54 00 56 > 00 20 > 00 38 00 30 00 30 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom a0: 65 00 00 00 1c 03 30 > 00 37 > 00 30 00 34 00 30 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom b0: 31 00 39 00 31 00 35 > 00 30 > 00 30 00 35 00 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom c0: 00 00 00 00 00 00 00 > 00 00 > 00 00 00 00 00 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom d0: 00 00 00 00 00 00 00 > 00 00 > 00 00 00 00 00 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom e0: 00 00 00 00 00 00 00 > 00 00 > 00 00 00 00 00 00 00 > Jun 14 13:17:04 tux kernel: em28xx #0: i2c eeprom f0: 00 00 00 00 00 00 00 > 00 00 > 00 00 00 00 00 00 00 > Jun 14 13:17:04 tux kernel: EEPROM ID= 0x9567eb1a > Jun 14 13:17:04 tux kernel: Vendor/Product ID= 2304:0227 > Jun 14 13:17:04 tux kernel: AC97 audio (5 sample rates) > Jun 14 13:17:04 tux kernel: 500mA max power > Jun 14 13:17:04 tux kernel: Table at 0x27, strings=0x168e, 0x1ca4, 0x246a > Jun 14 13:17:04 tux kernel: em28xx #0: V4L2 device registered as /dev/video0 > Jun 14 13:17:04 tux kernel: em28xx #0: Found Pinnacle PCTV HD Pro > > module autoloading is probably not enabled in your kernel. Markus > The code of the driver is from hg clone http://mcentral.de/hg/~mrec/v4l-dvb > The firmware using is firmware_v4.tgz > > 134d3b77b40d1b1298a91bb32c44544cebf77e64 firmware_v4.tgz > xawtv -hwscan > > This is xawtv-3.95, running on Linux/x86_64 (2.6.19-gentoo-r5) > looking for available devices > /dev/video0: OK [ -device /dev/video0 ] > type : v4l2 > name : Pinnacle PCTV HD Pro > flags: capture tuner > This is xawtv-3.95, running on Linux/x86_64 (2.6.19-gentoo-r5) > WARNING: v4l-conf is compiled without DGA support. > /dev/video0 [v4l2]: no overlay support > v4l-conf had some trouble, trying to continue anyway > Warning: Cannot convert string "-*-ledfixed-medium-r-*--39-*-*-*-c-*-*-*" to > type FontStruct > v4l2: oops: select timeout > > > > Any idea, the what is the problem. > > > but when i run the xawtv > > > > the program xawtv show > -- Markus Rechberger _______________________________________________ linux-dvb mailing list linux-dvb@xxxxxxxxxxx http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
