On Wed, 27 Feb 2002 17:02:25 +1100 Cameron Maxwell <cmaxwell@xxxxxxxxxxxxxxxxxx> wrote: > 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. Guh, how did i miss that. It's right there in the readme. It worked, once. but for some reason the image wasn't scaled. I guess that's ok, since it was almost more of a slide show than live video. i think i got about 5fps, maybe less. I realize that USB is extremely limited, but it was a lot faster in windows. I guess that has something to do with the compressed video mode that we're not using. Now it's not initializing again, i'm not sure what's going on. I unloaded everything, even usb-uhci, and loaded it all again like i did the time it worked, still no dice. *shrug*. I'm gonna throw out the debian packages and install my own build, tho. The debian binary can't even get as far as telling me it failed initialization. > 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. That's, well, curious, since I'm specifying tuner=2 when i load usbvision.o, but ok, as long as it's normal. Thanks for your help, I can't believe i forgot to insmod that driver . . - eric
