Eric, Judging by the output you've posted you've forgotten to load the module for the video decoder. In your case it probably the saa7111-new that comes with the usbvision driver, simply modprobing usbvision won't load it, you have to do it manually. I have found that sometimes it helps if you load the modules in the following order: insmod ./i2c-algo-usb.o insmod ./usbvision.o modprobe tuner insmod ./saa7111-new.o Also the output from when you load the tuner is normal. The tuner module scans the I2C bus on the WinTV for all the tuners it recognises. You'll see it finds yours at 0xc2: >tuner: chip found @ 0xc2 >usb_usbvision-0: i2c attach [Philips NTSC] but it also keeps searching to see if it can find any others and this is where the error messages come from. They are from the WinTV saying there is nothing at those addresses, which is fine because you don't have any of those tuners. Let us know if you have any luck, Cameron Maxwell On Wed, 27 Feb 2002 16:34, Eric Jorgensen wrote: > I picked up a Hauppauge WinTV-USB very cheaply at a thrift store a while > back ($5), verified that it worked on a windows box, and now i've decided > to try and use it on my notebook. > > It doesn't work. When i try motv -hwscan with the motv binary from > debian/woody, i get this: > > This is motv-3.70, running on Linux/i686 (2.4.17) > Warning: Actions not found: Remote > Warning: Actions not found: Remote > Segmentation fault > > So I built xawtv 3.72, and with that i get this: > > This is xawtv-3.72, running on Linux/i686 (2.4.17) > WARNING: no plugins found [/usr/local/lib/xawtv] > looking for available devices > port 46-46 > type : Xvideo, image scaler > name : ATI mach64 Video Overlay > > /dev/video0: initialization failed > > So, well, I'm stuck. It doesn't work. What can i say. I'd appriciate any > input. > > I'm using debian/woody on a Thinkpad X21 - PIII-700, ATi Rage Mobility-M. > kernel is 2.4.17 built from kernel.org sources. I've installed the ati.2 > xserver (binaries), so my display supports XVideo. At least, xvinfo has a > lot of positive things to say about my display, and mplayer is definately > able to use the BES. I have instructed X to load the v4l module, I haven't > independently verified that it's being loaded. > > I've followed the instructions included with the > usbvision-0.3.1-test2-2.4.6 tarball at http://www.emuit.com/webcam.html. > Everything built ok. > > When i load the module, I get the warning about tainting the kernel, but > no other errors. dmesg says this: > > i2c-algo-usb.o: i2c usb algorithm module > usb.c: registered new driver usbvision > usbvision: HAUPPAUGE WINTV-USB USA found > i2c-algo-usb.o: hw routines for usbvision #0 registered. > i2c-core.o: adapter usbvision #0 registered as adapter 0. > > When i load tuner.o, things don't look so pretty: > > i2c-algo-usb.o: hw routines for usbvision #0 registered. > i2c-core.o: adapter usbvision #0 registered as adapter 0. > i2c-core.o: driver i2c TV tuner driver registered. > i2c-algo-usb.o: needed 3 retries for 192 > i2c-algo-usb: NAK from device adr 0x60 msg #0 > tuner: chip found @ 0xc2 > usb_usbvision-0: i2c attach [Philips NTSC] > i2c-core.o: client [Philips NTSC] registered to adapter [usbvision > #0](pos. 0). i2c-algo-usb.o: needed 3 retries for 196 > i2c-algo-usb: NAK from device adr 0x62 msg #0 > i2c-algo-usb.o: needed 3 retries for 198 > i2c-algo-usb: NAK from device adr 0x63 msg #0 > i2c-algo-usb.o: needed 3 retries for 200 > i2c-algo-usb: NAK from device adr 0x64 msg #0 > i2c-algo-usb.o: needed 3 retries for 202 > i2c-algo-usb: NAK from device adr 0x65 msg #0 > i2c-algo-usb.o: needed 3 retries for 204 > i2c-algo-usb: NAK from device adr 0x66 msg #0 > i2c-algo-usb.o: needed 3 retries for 206 > i2c-algo-usb: NAK from device adr 0x67 msg #0 > i2c-algo-usb.o: needed 3 retries for 208 > i2c-algo-usb: NAK from device adr 0x68 msg #0 > i2c-algo-usb.o: needed 3 retries for 210 > i2c-algo-usb: NAK from device adr 0x69 msg #0 > i2c-algo-usb.o: needed 3 retries for 212 > i2c-algo-usb: NAK from device adr 0x6a msg #0 > i2c-algo-usb.o: needed 3 retries for 214 > i2c-algo-usb: NAK from device adr 0x6b msg #0 > i2c-algo-usb.o: needed 3 retries for 216 > i2c-algo-usb: NAK from device adr 0x6c msg #0 > i2c-algo-usb.o: needed 3 retries for 218 > i2c-algo-usb: NAK from device adr 0x6d msg #0 > i2c-algo-usb.o: needed 3 retries for 220 > i2c-algo-usb: NAK from device adr 0x6e msg #0 > i2c-algo-usb.o: needed 3 retries for 222 > i2c-algo-usb: NAK from device adr 0x6f msg #0 > > > > _______________________________________________ > Video4linux-list mailing list > Video4linux-list@xxxxxxxxxx > https://listman.redhat.com/mailman/listinfo/video4linux-list
