Hi, After a reboot of the computer the driver seem to be loaded correctly. I still have no image at all. ex: cat /dev/video0 > test.mpeg - give me an empty file. If I plug the cable on an old tv this is working. Is that possible to the cable distributor to prevent diffusion on a PVR device ? It seem to me that the problem is not a driver installation issue ? Is the problem is a file access right ? (ext4 instead ext3)...
Any how - when I get access to a windows/xp system and / or an external hard drive- I will do the test you suggested. Thanks a lot for your help and time! Sylvain. sylv...@sylvain-desktop2:~$ dmesg |grep pvrusb2 [ 8.307569] usbcore: registered new interface driver pvrusb2 [ 8.307601] pvrusb2: 20090509 (from www.isely.net):Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner [ 8.307603] pvrusb2: Debug mask is 31 (0x1f) [ 8.308230] pvrusb2: Automatic loading ir-kbd-i2c has been disabled. [ 8.498375] saa7115' 0-0021: saa7115 found (1f7115d0e100000) @ 0x42 (pvrusb2_a) [ 8.729065] msp3400' 0-0040: MSP3445G-B8 found @ 0x80 (pvrusb2_a) [ 8.824263] tuner' 0-0043: chip found @ 0x86 (pvrusb2_a) [ 8.867070] tuner' 0-0061: chip found @ 0xc2 (pvrusb2_a) [ 8.897221] pvrusb2: Supported video standard(s) reported available in hardware: PAL-M/N/Nc;NTSC-M/Mj/Mk [ 8.897228] pvrusb2: Mapping standards mask=0xb700 (PAL-M/N/Nc;NTSC-M/Mj/Mk) [ 8.897232] pvrusb2: Setting up 6 unique standard(s) [ 8.897237] pvrusb2: Set up standard idx=0 name=NTSC-M [ 8.897241] pvrusb2: Set up standard idx=1 name=NTSC-Mj [ 8.897245] pvrusb2: Set up standard idx=2 name=NTSC-Mk [ 8.897249] pvrusb2: Set up standard idx=3 name=PAL-M [ 8.897253] pvrusb2: Set up standard idx=4 name=PAL-N [ 8.897256] pvrusb2: Set up standard idx=5 name=PAL-Nc [ 8.897261] pvrusb2: Initial video standard guessed as NTSC-M [ 8.897272] pvrusb2: Device initialization completed successfully. [ 8.897619] pvrusb2: registered device video0 [mpeg] [ 8.897682] pvrusb2: registered device radio0 [mpeg] sylv...@sylvain-desktop2:~$ lsmod |grep pvr pvrusb2 150336 0 cx2341x 20996 1 pvrusb2 v4l2_common 20992 5 tuner,msp3400,saa7115,pvrusb2,cx2341x videodev 41600 3 tuner,msp3400,pvrusb2 v4l1_compat 21764 2 pvrusb2,videodev tveeprom 20100 1 pvrusb2 sylv...@sylvain-desktop2:/dev$ ls -l|grep video crw-rw---- 1 root video 81, 1 2009-07-31 19:59 radio0 crw-rw---- 1 root video 81, 0 2009-07-31 19:59 video0 Le vendredi 31 juillet 2009 à 00:04 -0500, Mike Isely a écrit : > On Thu, 30 Jul 2009, sylvain arbour wrote: > > > Hi, > > > here is the result of the command: > > > > sylv...@sylvain-desktop2:~$ dmesg |grep pvrusb2 > > [ 8.143906] usbcore: registered new interface driver pvrusb2 > > [ 8.143933] pvrusb2: 20090509 (from www.isely.net):Hauppauge > > WinTV-PVR-USB2 MPEG2 Encoder/Tuner > > [ 8.143936] pvrusb2: Debug mask is 31 (0x1f) > > [ 8.144063] usb 1-2: firmware: requesting v4l-pvrusb2-29xxx-01.fw > > [ 8.220760] pvrusb2: Device microcontroller firmware (re)loaded; it > > should now reset and reconnect. > > [ 8.235072] pvrusb2: Device being rendered inoperable > > If you got nothing after this, then the device crashed when it tried to > start from the new firmware. This makes me suspect that you have a > faulty firmware image or that something is preventing it from being > cleanly loaded into the hardware. The v4l-pvrusb2-29xxx-01.fw firmware > file is the actual executable image loaded onto the microcontroller > which operates the entire device. It is critical to all aspects of > operation. What you see above is the pvrusb2 driver attempting to > download that firmware image and reboot the device. If the reboot > succeeds (which should ALWAYS be the case), then the rest of the driver > initialization will commence. > > > > sylv...@sylvain-desktop2:~$ lsmod |grep pvrusb > > pvrusb2 150336 0 > > cx2341x 20996 1 pvrusb2 > > v4l2_common 20992 2 pvrusb2,cx2341x > > videodev 41600 1 pvrusb2 > > v4l1_compat 21764 2 pvrusb2,videodev > > tveeprom 20100 1 pvrusb2 > > > > I do the compilation of the driver version of may 2009. My hauppaupe > > wintv pvr usb2 device is 29032 rev D158 NTSC/NTSC-J > > That looks good. > > > > This time I don't even get the /dev/video0... I can see that the > > device is inoperable but I don't know what's is the problem. > > So you *did* get a /dev/video0 at some point in the past? If you ever > get a /dev/video0, then the driver did successfully initialize, which is > only possible if the device's firmware initializes correctly (among a > number of things that must work). If the firmware file is itself > corrupt, then you should always get stuck after reloading the firmware. > If the firmware file is fine but something is trashing the transfers, > that's more of a probabilistic thing which means it will probably fail > at different points of initialization at various times, or sometimes it > might actually work. Knowing which of these two cases you are > experiencing would help. > > Can you attach a USB hard drive to that same cable endpoint and verify > that you can transfer large blocks of data (multiple megabyte size) > to/from that hard drive? That would be a good way to rule out any USB > connectivity / reliability problems. Another thing to try - if you can > - is to try the same pvrusb2 device on another computer. If you get the > same bad behavior there, you might have a device with a hardware > problem (trying it under a Windows system would be further proof if this > this the case). > > -Mike > > _______________________________________________ > pvrusb2 mailing list > [email protected] > http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2 > > _______________________________________________ pvrusb2 mailing list [email protected] http://www.isely.net/cgi-bin/mailman/listinfo/pvrusb2
