Kenneth G Eitenmiller Jr writes:
Sam,All that I have done in regards to ivtv include whats on the wilsonet.com hotwo.This includes: yum install ivtv-firmware yum install ivtv-kmdl-$KVER yum install ivtv yum install ivtvdevIf i need to do anything other installs, I will need a little more guidance. It has been quite some time since I have compliled anything for linux.Any hints?
Looks like the only thing you're missing are the hacks to xorg.conf. The canned ivtvdev driver package is not going to do that for you.
The problem here is that ivtv xdriver's source code tells you what you need to hack in xorg.conf, but you never see those docs because you're installing the canned, precompiled, driver.
You must take your existing xorg.conf, and do some major surgery on it. It really helps to know how various parts of xorg.conf work. Briefly, the monitor definition for the PVR-350 TV-Out framebuffer is:
Section "Monitor"
Identifier "NTSC Monitor"
HorizSync 30-68
VertRefresh 50-120
Mode "720x480"
DotClock 34.564
HTimings 720 752 840 928
VTimings 480 484 488 504
Flags "-HSync" "-VSync"
EndMode
EndSection
You need to replace your existing Monitor section with this.
The device section, which initializes the ivtvdev module should be:
Section "Device"
Identifier "Hauppauge PVR 350 iTVC15 Framebuffer"
Driver "ivtvdev"
Option "fbdev" "@FRAMEBUFFER@"
BusID "@LSPCI@"
EndSection
Replace @FRAMEBUFFER@ with the framebuffer device the kernel allocates for
ivtv_fb, which you can obtain from /proc/fb. My /proc/fb reads:
$ cat /proc/fb 0 VESA VGA 1 cx23415 TV outThat means that my PVR-350 framebuffer is /dev/fb1 (yours is probably /dev/fb0), so I have
Option "fbdev" "/dev/fb1"in my xorg.conf. Your PVR-350 framebuffer will probably be /dev/fb0. Caution: after you do this, you will find that starting X on PVR-350's framebuffer is going to break your system console. It's some kind of a known kernel problem, for which I've yet to find a meaningful explanation, but the partial workaround for that is to boot using the VESA framebuffer, so you'll probably have to do that (and update your xorg.conf, since the PVR-350 framebuffer will then become /dev/fb1), at some point down the road. But, anyway, right now your #1 priority is to teplace "@LSPCI@" with your PVR-350's PCI ID. The format of the BusID option is a frequent source of grief. My "lspci" gives me:
# lspci [..]00:0b.0 Multimedia video controller: Internext Compression Inc iTVC15 MPEG-2 Encoder (rev 01)
lspci's PCI IDs are _hexadecimal_, while xorg.conf expects the PCI ids in decimals, and prefixed by "PCI:", so my xorg.conf contains:
BusID "PCI:0:11:0"You need to get your PVR-350's PCI bus ID, convert it to decimal, attach the PCI: part, and put it into xorg.conf.
Finally, you need to get the resolution of the framebuffer correctly, in your xorg.conf's screen section. Your Device section should be something like:
Section "Screen"
Identifier "Screen0"
Device "Hauppauge PVR 350 iTVC15 Framebuffer"
Monitor "NTSC Monitor"
DefaultDepth 24
DefaultFbbpp 32
Subsection "Display"
Depth 24
FbBpp 32
Modes "720x480"
EndSubsection
EndSection
You need to have the xorg.conf man page handy while doing all of this.
And, if by some miracle of miracles you get this working in less then two
weeks, congratulate yourself on figuring everything out in less time than it
took me the first time I sat down in front of a box with a PVR-350 card, a
stock install of Fedora, and absolutely nothing else.
pgpXeFToLaWJR.pgp
Description: PGP signature
_______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
