jsutton,

Sorry, but what do you mean by the sources for my kernel?

Totally stuck, I have no clue how to move forward.
I read the README file for my CX88 driver, which is as follows:


cx8800 release notes
====================

This is a v4l2 device driver for the cx2388x chip.


current status
==============

video
- Basically works.
- Some minor image quality glitches.
- Red and blue are swapped sometimes for not-yet known
reasons (seems to depend on the image size, try to resize
your tv app window as workaround ...).
- For now only capture, overlay support isn't completed yet.

audio
- The chip specs for the on-chip TV sound decoder are next
to useless :-/
- Neverless the builtin TV sound decoder starts working now,
at least for PAL-BG. Other TV norms need other code ...
FOR ANY REPORTS ON THIS PLEASE MENTION THE TV NORM YOU ARE
USING.
- Most tuner chips do provide mono sound, which may or may not
be useable depending on the board design. With the Hauppauge
cards it works, so there is mono sound available as fallback.
- audio data dma (i.e. recording without loopback cable to the
sound card) should be possible, but there is no code yet ...

vbi
- some code present. Doesn't crash any more, but also doesn't
work yet ...


how to add support for new cards
================================

The driver needs some config info for the TV cards. This stuff is in
cx88-cards.c. If the driver doesn't work well you likely need a new
entry for your card in that file. Check the kernel log (using dmesg)
to see whenever the driver knows your card or not. There is a line
like this one:

cx8800[0]: subsystem: 0070:3400, board: Hauppauge WinTV \
34xxx models [card=1,autodetected]

If your card is listed as "board: UNKNOWN/GENERIC" it is unknown to
the driver. What to do then?

(1) Try upgrading to the latest snapshot, maybe it has been added
meanwhile.
(2) You can try to create a new entry yourself, have a look at
cx88-cards.c. If that worked, mail me your changes as unified
diff ("diff -u").
(3) Or you can mail me the config information. I need at least the
following informations to add the card:

* the PCI Subsystem ID ("0070:3400" from the line above,
"lspci -v" output is fine too).
* the tuner type used by the card. You can try to find one by
trial-and-error using the tuner=<n> insmod option. If you
know which one the card has you can also have a look at the
list in CARDLIST.tuner

Have fun,

Gerd

--
Gerd Knorr <kraxel@bytesex.org> [SuSE Labs]


===============================================
I typed dmesg and there is no line with "cx8800"

Sorry Dudski,
But I ain't having fun.

i've just downloaded the driver to have a look at it, but while i do that, run 'lsmod' and post the output.

Make sure that you have the source code for the version of the kernel that you're running. You can find your kernel version by typing this into a terminal:

I don't use Suse, so I don't know if there is a simple package for this or not. In earlier versions of Fedora, there was a kernel-source package (later renamed to kernel-sourcecode, and even later, it was removed altogether and replaced with a kernel*.src.rpm). Any Suse people out there that know how to get the kernel sources installed?

that's 'cos the driver isn't loaded. i hope that suse comes with the 2.6 kernel, 'cos the driver should be on you computer already. If they are, then all you need to do is insert them into your kernel i know it must sound like gibberish, but it's actually quite easy. If you think of the kernel as the brain, so the kernel is to linux what the cpu is to the PC(almost) and modules...well they're the drivers(probably more than that, but that's how i think of them).

so when you run lsmod, it gives you a list of all the modules which have been inserted and are running.
to insert a module you use modprobe [module name], eg. modprobe cx8800 and cx88xx and seeing as video4linux uses i2c, it wouldn't hurt to insert i2c_core and i2c_algo_bit, maybe even v4l(i think that's module)

the two i2c mods might need to be inserted in a specific order, so if you get an error try the next one and do the other one after.

well my kernel has just finished compiling.... it's time for me to take a deep breath and reboot

Suse 9.2 does use a 2.6 kernel, but I haven't had the best of luck with the cx88xx driver that's included with the kernel. The driver that I linked to above worked fine for me (on Fedora 2/3 at least).