Actually, the last time I remember doing something like this it was a setting in XFree86Config, where you could create a larger virtual desktop than the actual screen resolution your card supported. I don't think it had anything to do with the window manager per se.
Now that I think about it, I seem to recall olvwm had a simliar feature, but I always used it to make a smaller resolution larger. I did manage to get through mythtv-setup and found the setting in the mythfrontend settings that lets me scale the screen size down, so I'm ok for now. Thanks for the help! --- Duncan Webb <[EMAIL PROTECTED]> wrote: > John Harvey 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. > >>> > Wouldn't happen to know of overscan options for > WindowMaker? Can't fine > anything from a quick google search. > > Thanks, > Duncan > > _______________________________________________ > ivtv-devel mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-devel > __________________________________ Start your day with Yahoo! - Make it your home page! http://www.yahoo.com/r/hs _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
