ok I converted to linux from windows to put myth on my computer but can't get anything to work....... I can't get my sound card or my caputer card to work... please help i have been trying to get this stuff to work for like 4 months....here is my lspci:
00:00.0 Host bridge: ALi Corporation M1647 Northbridge [MAGiK 1 / MobileMAGiK 1] (rev 04)
00:01.0 PCI bridge: ALi Corporation PCI to AGP Controller
00:04.0 IDE interface: ALi Corporation M5229 IDE (rev c4)
00:06.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
00:07.0 ISA bridge: ALi Corporation M1533 PCI to ISA Bridge [Aladdin IV]
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
00:09.0 Multimedia audio controller: Creative Labs SB Audigy LS
00:0a.0 Multimedia controller: Philips Semiconductors SAA713X Audio+video broadcast decoder (rev d0)
00:11.0 Bridge: ALi Corporation M7101 Power Management Controller [PMU]
00:14.0 USB Controller: ALi Corporation USB 1.1 Controller (rev 03)
01:00.0 VGA compatible controller: nVidia Corporation NV20 [GeForce3 Ti 200] (rev a3)

I have an motherboard sound card that was "working" and i disabled that in the bios and when i do sound card detection it says sound card not found. when i go to hardware browser ;it is not there either. When i go to hardware browser my capture card is there but when i run tvtime i get no video...i am using fedor core 3 here is my kernel:
2.6.9-1.667

I am sure i am the 90th person to post something like this but i tried searching first and did not find my solution....please help i just want mythtv to work!!!!

lspci is telling you what the hardware reports tothe kernel, when the device is interrogated. You still need the kernel module that supports it, so applications can talk with it. Google keywords like " linux driver <name of card>" (or substitute "module" for "Driver".

Now its also important to know that the kernel itself, needs to support the card. What I'm referring to is the fact that the kernel now supports loadable modules. So, either the module was compiled into the kernel (which, in this case isn't likely since you have the trouble that you have) or it needs to have been compiled as a loadable module. If neither of these is true you will need to compile a new kernel, yourself. BUT ...

This is one heck of a lot easier than it sounds and a heck of a lot easier than it was 10 years ago. So, don't become intimated by the sound of the task or by anyone who implies you need to be a guru to do it. All that is necessary is that someone has written the module and that you know how to read things like this reply.

I hope this helps.