On Mon, Feb 13, 2006 at 08:51:56PM -0800, Don Gafford wrote: > Hey Brad, > > I have the same exact card as you do with the same. I am on Fedora Core > 4 and am using the RPMs for ivtv version 0.4.2 from ATRPMS. I was > getting something similar to what you were getting when I first tried to > set things up. What worked for me was the following:
Please note that with the latest kernels in FC4 (2.6.15 based) the ivtv kmdls only carry ivtv.ko, as the rest is to be taken from the kernel. E.g. remove the alias foo foo-ivtv lines. > My modprobe.conf looked like this: > > alias char-major-81-0 ivtv > alias char-major-81 ivtv > alias msp3400 msp3400-ivtv > alias tuner tuner-ivtv > alias tveeprom tveeprom-ivtv > alias char-major-81-1 ivtv > > I would get a very similar modprobe to what you got with the 2 "tuner > 1-0061: tuner type not set" lines. I was looking at another post of > someone's modprobe and saw that their modprobe looked like this: > > alias char-major-81-0 ivtv > alias char-major-81 ivtv > alias tveeprom tveeprom-ivtv > alias msp3400 msp3400-ivtv > alias tuner tuner-ivtv > #options ivtv ivtv_std=1 tuner=57,57 > alias char-major-81-1 ivtv > > I swapped the location of the tveeprom lines around and that's what got > me working. Before that I read a lot on the older tuner.ko files around > your machine. I made sure I deleted or renamed all of the older ones and > made the ones that ivtv 0.4.2 installed named tuner-ivtv.ko as was > recommended in other faq's that I found. > > If you are unsure what set of modules you are using, they should match > what your uname -r is. If you are curious, you can get a list of all the > .ko files in the driver subdirectory and find the same files in your > modules directory and move them to another directory. Then install the > .ko files from the driver subdirectory to the ivtv folder and rename > them with a -ivtv extension. Then change your modprobe to match mine. > That way you can replace the files that you moved if necessary. > > Also make sure you have the correct firmware and make sure they are in > the correct locations: http://www.ivtvdriver.org/index.php/Firmware. > Fedora placed my firmware files in /lib/firmware. > > Hopefully you have read through the howto: > http://www.ivtvdriver.org/index.php/Howto > > Sorry if this is at all cryptic or unclear. I had to play with things a > little to get it working and I am still having a problem tuning in one > channel. > > What Linux version are you using? > > -Don > > > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Brad > Sent: Monday, February 13, 2006 6:41 PM > To: [email protected] > Subject: [ivtv-users] Getting a Hauppauge PVR-500 to work > > Well, the mysterious channel stickiness disappeared when I booted. Now > I'm getting the same results I've always gotten. > > I noticed that when I "make install" the new driver that it's actually > putting everything in /lib/modules/2.6.15-1-486-1-486/ivtv instead of > /lib/modules/2.6.15-1-486/ivtv. I copied everything from the former into > > the latter, but that didn't seem to help. > > Here's my dmesg: > <snip> > > tuner 1-0061: tuner type not set > tuner 1-0061: tuner type not set > ivtv0: Initialized WinTV PVR 500 (unit #1), card #0 > > <snip> > > tuner 2-0061: tuner type not set > tuner 2-0061: tuner type not set > ivtv1: Initialized WinTV PVR 500 (unit #2), card #1 > > > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users -- Axel.Thimm at ATrpms.net
pgpRek2LE4cXi.pgp
Description: PGP signature
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
