> On Friday 03 August 2007 20:10:56 Jurgen Goedbloed wrote: >> Hans Verkuil wrote: >> > On Friday 03 August 2007 13:57:53 Jurgen Goedbloed wrote: >> >>>> In an effort to get my PVR-350 working on my fedora 7 box, I >> >>>> updated the kernel and ivtv packages to 2.6.22. >> >>>> >> >>>> But now when I start X, it doesn't start, but gives an error. >> >>>> Has something (ie ivtv-fb) changed that the X driver doesn't >> >>>> work anymore? >> >>> >> >>> Yes, it has. The Xdriver is being converted but there is no >> >>> official release as yet. However, you can get a version that >> >>> should work here: >> >>> >> >>> http://ivtvdriver.org/viewcvs/xdriver/trunk.tar.gz?view=tar >> >>> >> >>> Feedback is appreciated. >> >> >> >> I tried to compile the driver, but it gave an error. >> >> ... >> > >> > You're missing the linux/limits.h header for some reason. You might >> > have to install the kernel-devel package (not sure if that's the >> > right package name, I'm no fedora expert). >> >> Yep, I needed the kernel-devel package. Compiling and installing OK. >> >> The drivers works fine. Some things I have noticed: >> - You need to load modules in a specific order: saa7127, then ivtv, >> then ivtv-fb. >> - When I load the saa7127 module after the ivtv driver, I have to set >> the standard again (first to something else, then back to PAL B). > > Huh? Loading ivtv should load saa7127 automatically. In fact, just > loading ivtv-fb should pull everything in.
You are right. Probably because of testing some modules were already loaded. When i load ivtv-fb then others load. >> - X server crashes after changing the screen settings in mythtv (GUID >> width, heigth and offset). I don't know what mythtv is telling the X >> server then. > > Read the README in the ivtv-1.0.1 archive: > > NOTE: users of MythTV who use the PVR350 for mpeg decoding need to > specify the option osd_compat=1 when loading the ivtv-fb module. This > is not required when using the default Xv output. > > I think you need to set this. Tried that, but then X won't start. I get (EE) IVTVDEV(0): FBIOPUT_VSCREENINFO: Invalid argument (EE) IVTVDEV(0): Mode init failed Without the osd_compat=1 X starts fine. Jurgen. _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
