Solved: disable_overscan=1 not working
|
17th Jan, 2013, 09:57 AM
Post: #3
|
|||
|
|||
RE: disable_overscan=1 not working
I had a bit of a hack, and found that using start.elf from Raspbmc and everything else from XBian gave the correct (lack of) overscan on the earliest kernel boot display. Though it ran into trouble later during bootup. Using almost all the Raspbmc boot binaries got further, but still gave a black screen on starting XBMC.
Reverting back to the original XBian files, I tried forcing CEA resolutions in config.txt but the overscan was still bad. Though an accidental hdmi_group=2 gave me 640x480, and overscan was correct there. The only trouble was that XBMC was also stuck at that resolution, with no other video modes available for selection. I guess I need to learn a bit more about the boot file difference between the two distros. I also don't understand why a seemingly successful boot would give a black screen on starting XBMC (a known issue with earlier builds I believe?). It could also be a quirk with my TV (Panasonic TH-37PX80B), but it seems odd it's only XBian affected. |
|||
« Next Oldest | Next Newest »
|
Messages In This Thread |
disable_overscan=1 not working - obo - 16th Jan, 2013, 10:17 AM
RE: disable_overscan=1 not working - CurlyMo - 16th Jan, 2013, 10:34 AM
RE: disable_overscan=1 not working - raspberry_pd - 17th Jan, 2013, 04:55 PM
RE: disable_overscan=1 not working - obo - 17th Jan, 2013 09:57 AM
RE: disable_overscan=1 not working - CurlyMo - 17th Jan, 2013, 10:14 AM
Re: disable_overscan=1 not working - rikardo1979 - 17th Jan, 2013, 03:52 PM
RE: disable_overscan=1 not working - CurlyMo - 17th Jan, 2013, 08:09 PM
RE: disable_overscan=1 not working - obo - 17th Jan, 2013, 11:52 PM
Re: disable_overscan=1 not working - rikardo1979 - 18th Jan, 2013, 01:05 AM
RE: disable_overscan=1 not working - obo - 18th Jan, 2013, 02:00 AM
Re: RE: disable_overscan=1 not working - rikardo1979 - 18th Jan, 2013, 04:45 AM
RE: disable_overscan=1 not working - obo - 18th Jan, 2013, 04:45 AM
|