[ATrpms-users] yum install for ivtv failing w/Missing Dependency

[Steve B.]

Hi All,

I'm trying to create a MythTV server box, and I'm running into problems 
installing ivtv with yum.

I've started with a completely clean Fedora FC4 "Everything" install, and 
I'm following the directions here: http://wilsonet.com/mythtv/fcmyth.php.  I 
have a Hauppauge PVR-500 card, so I've followed the directions here ( 
http://www.ivtvdriver.org/index.php/Firmware ) to download the firmware.

However, upon running this command:

yum install ivtv-kmdl-2.6.17-1.2139_FC4

I'm getting this error:

Setting up Install Process
Setting up repositories
atrpms                    100% |=========================|  951 B    00:00
freshrpms                 100% |=========================|  951 B    00:00
extras                    100% |=========================| 1.1 kB    00:00
updates-released          100% |=========================|  951 B    00:00
base                      100% |=========================| 1.1 kB    00:00
Reading repository metadata in from local files
Parsing package install arguments
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package ivtv-kmdl-2.6.17-1.2139_FC4.i686 1:0.7-114.rhfc4.at set to be 
updated
--> Running transaction check
--> Processing Dependency: /lib/modules/v4l-cx2341x-init.mpg for package: 
ivtv-kmdl-2.6.17-1.2139_FC4
Importing Additional filelist information for dependency resolution
filelists.xml.gz          100% |=========================| 2.3 MB    00:04
extras    : ################################################## 3289/3289
Added 41 new packages, deleted 6 old in 14.29 seconds
--> Finished Dependency Resolution
Error: Missing Dependency: /lib/modules/v4l-cx2341x-init.mpg is needed by 
package ivtv-kmdl-2.6.17-1.2139_FC4

The file it's complaining about (from the firmware install step) does exist 
in that directory, so I'm not sure what the problem is.  I've tried 
rebuilding the yum repository with this line:

rm -f /var/lib/rpm/__db*
rpmdb -vv --rebuilddb

but I'm still getting the same error.  Any ideas on how to get past this 
sticking point?

-Steve