I finally got my Hauppauge WinTV USB working under Linux (with v4l in the kernel and usbvision-0.3.3-test4 compiled as a module) -- but with a far from perfect result:

* Colors are inverted -- faces are blue, grass is purple, etc. (Luminance is right, though.)

* Image proportions don't seem right -- xawtv shows black borders on the right and left sides of the actual image and unsightly VBI garbage below it. On some channels, it also chops off a bit of the left part of the image.

* xawtv only renders every other pixel at image sizes above 320x240 (or thereabouts), and won't go beyond 640x480 (or so) at all.

* I can't adjust hue, brightness, contrast, etc. independently. Whenever I change one, all the others return to their (undesirable) default values. Editing .xawtv has no effect.

* Changing channels usually (but not always) takes about a second and produces an error message:
v4l: timeout (got SIGALRM), hardware/driver problems?
ioctl: VIDIOCSYNC(0): Interrupted system call

I'd be grateful for any ideas as to how these problems can be solved, suggestions for what log files to check for error messages (I'm pretty new to Linux hardware issues), or even just confirmation that this is as good as it gets.

--nfisk

Hi, I am a linux newbie, I've just tried to install the usbvision modules, so that I can use my card under Linux and get rid off Windows, but the whole process has puzzle me much. I followed the instructions indicated in the readme.txt file, but not all the steps are that obvious to me. Can you help me out? Could you give me a hand?

Tell me which steps you're having problems with and which TV card you're using and I'll try to help.

--nfisk

Hi, thanx for your answer.

This are the steps I've been having problems with:

1.) the instructions of the usbvision.txt file tell me to copy all
the contents of the src directory to the /usr/src/linux/drivers/usb directory, but the src directory contains a Makefile which will overwrite the Makefile of the /usr/src/linux/drivers/usb directory. Should I overwrite that Makefile or leave it untouched? What I've done is to leave it as it is, 'cause they don't seem similar at all.

2.) the instruction of how to configure the kernel are rather vague. I've manage to edit the Config.in. But after doing a make xconfig all that options puzzle me. I don't know if everything that's
marked is present in my current kernel. What I would like to do is to choose all the options that are present in my current kernel and just add that one module, anything else. This is the part that causes me problems.

3.) Next is the make dep and make modules commands. As I don't understand what all those options stand for (some are obvious other not), some times a make dep renders errors some times is the make modules...errors that don't have to do with the
usbvision files copied. Would you like me to send a list of all errors generated?

I tried to work the problem around, I compile the src files doing a make all into that directory then placing the .o files into the /lib/modules/... directory and issuing a modprobe usbvision but the command renders a cannot locate usbvision module. I'm lost there.

I have a Hauppauge WinTV-USB PAL-B/G Model 40204 card, I use Redhat 8.0 no upgrades. Thanks for all the help you might provide me.

Well, I'm no expert, but, like I said, I did manage to get my card working. Like you, I had never attempted to compile a kernel before this. If memory serves me, this is what I did differently from what you've described:

1. I don't think I copied the Makefile; I think I just edited the existing one according to the instructions in usbvision.txt (adding i2c-algo-usb.o).

2. Hmm... I had some trouble with this step as well. The set of pre-made selections the first time I ran make xconfig seemed more or less random and had little to do with what was reasonable. Basically, I simply braced myself and went through everything once, selecting stuff based on what I knew about my machine. Then I compiled and installed the kernel and rebooted the machine. The result was, predictably, far from perfect, but I carefully observed error messages during the boot process and generally tried to figure out what wasn't working to decide which selections I should change. Then I compiled, installed and rebooted again. After I had done this a few times, pretty much everything worked, including the usbvision module.

I don't know that there isn't a better way than this rather laborious process, but it's what I did and with a little persistence I succeeded. Two things to keep in mind: (a) You can have multiple kernels installed, at least with grub; while you're tinkering, it's a good idea to keep a kernel around that works in case you change something that renders your new kernel unbootable. (b) I also found it useful to save a copy of each new version of .config so I could keep track of what I had done so far.

I don't think compiling the usbvision stuff separately and just slapping the .o files into place is likely to work.

When you get your setup working, I'd be very interested to hear if you have the same problems as me with the image. I ended up editing usbvision.c to get the colors right (swapping red and green, if I recall) -- unattractive, quick, dirty, but it worked.

--nfisk

To whomever can help

I recently implemented the usbvision0.3.3-test4 drivers and editied the usbvision.h file to recognize my Hauppauge USB WinTV (0x573 4d32). After recompiling the kernel (2.4.20) on my Slackware 9, I managed to successfully start XAWTV to grabdisplay with PAL and Western Europe settings, as well as setting up the channels.

This all worked with no problems. However, I am experiencing the same issues with the red, green and blue colours being mixed up. Plus the picture is somewhat grainy and as was mentioned previously a small resolution.

With regards to the red, green and blue colour issues I will modify the usbvision.c file.

Is there any way to improve the graininess and the resolution or can that be fixed in the usbvision.c file too?

Also would using KWintv/QtVision be better to t use than XAWTV or is the app have no bearing on the way the grabdisplay is handled.

Any information would be much appreciated

I haven't had the chance to try it out on my 2.4.20 and 2.6-test9 kernel versions yet, but I will keep you updated

Regards

The Penguin from the Highlands in bonnie Scotland

Again, I'm no expert, but I do have a couple of comments...

First, I think the perceived graininess is caused by incorrect brightness, contrast, and/or saturation levels. I've been trying to figure out a way of adjusting them, but so far to no avail.

Second, I've started using MPlayer instead of XAWTV. I can crop out the black edges I mentioned, I can resize the window, and full-screen mode works.

Now, if someone knows how to adjust brightness etc., I'd love to hear it. Then I wouldn't have to boot into Windows just to get an enjoyable TV image (some movies and other programs are currently too dark, especielly when viewed from a distance).

--nfisk