BTW I'm running FC4 and I am running mythtv (though I'm having some trouble getting through mythtv-setup because of this problem). Currently I'm running KDE, but I've used other window managers in the past. Any recommendations for a window manager that is quick and easy to get up and running on FC4?
Thanks for your help... --- John Harvey <[EMAIL PROTECTED]> wrote: > It's not a problem as such, it's just the way it > works. > Sollutions are to use window managers that allow you > to choose a smaller virtual desktop. > Or if you are running mythtv then you can set it's > overscan settings to work round this. > > We are however working on implementing something > that > will allow for setting this somehow. > > John > --- korebantic <[EMAIL PROTECTED]> wrote: > > > So maybe I should just disable the use of the X > > driver > > and use the fbdriver only? > > > > Current=> > > > > Section "Device" > > Identifier "Hauppauge PVR 350 iTVC15 > > Framebuffer" > > Driver "ivtvdev" > > > > ### change fb1 to whatever your card > grabbed > > Option "fbdev" "/dev/fb1" > > Option "ivtv" "/dev/fb1" > > > > ### change the BusID to whatever is > reported > > by lspci, > > ### converted from hex to decimal > > BusID "PCI:1:5:0" # lspci says 00:08.0 > > ### More examples > > #BusID "PCI:0:10:0" # lspci says 00:0a.0 > > #BusID "PCI:1:14:0" # lspci says 01:0e.0 > > #BusID "PCI:0:5:1" # lspci says 00:05.1 > > EndSection > > > > Change To=> > > > > Section "Device" > > Identifier "Hauppauge PVR 350 iTVC15 > > Framebuffer" > > Driver "fbdev" > > > > ### change fb1 to whatever your card > grabbed > > Option "fbdev" "/dev/fb1" > > Option "ivtv" "/dev/fb1" > > > > ### change the BusID to whatever is > reported > > by lspci, > > ### converted from hex to decimal > > BusID "PCI:1:5:0" # lspci says 00:08.0 > > ### More examples > > #BusID "PCI:0:10:0" # lspci says 00:0a.0 > > #BusID "PCI:1:14:0" # lspci says 01:0e.0 > > #BusID "PCI:0:5:1" # lspci says 00:05.1 > > EndSection > > > > Is there any diagnostic output I can provide that > > would help the xdriver devs track down the > problem? > > > > --- Duncan Webb <[EMAIL PROTECTED]> wrote: > > > > > korebantic wrote: > > > > > > >I'm trying to get X working on the PVR350 > TV/Out > > > but, > > > >I can't see any of the edges. This document has > a > > > >section addressing: > > > > > > > > > > >http://ivtv.writeme.ch/tiki-index.php?page=XDriverHowTo > > > > > > > >But the url it references takes you to > > wonderland. > > > > > > > >Any help would be appreciated. > > > > > > > >Thanks > > > > > > > It's a problem with the current X-driver, > waiting > > > for a fix too. > > > > > > Duncan > > > > > > _______________________________________________ > > > ivtv-devel mailing list > > > [email protected] > > > > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > > > > > > > > > > > > __________________________________ > > Yahoo! FareChase: Search multiple travel sites in > > one click. > > http://farechase.yahoo.com > > > > _______________________________________________ > > ivtv-devel mailing list > > [email protected] > > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > > > > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
