alfakup wrote:Hello World,
Today I bought my first raspberry pi2, I installed the noob files to get this machine going everything worked except for the black bars on each side of my screen. I went through all the tutorials on how to fix the problem but I haven't had any success. Could part of the problem be that I am using and HDMI to DVI cable ( i wouldn't think this would be a problem)? I would appreciate any feedback. The monitor is a Samsung 75.0kHz 1600x1200.
It is unlikely that the HDMI to DVI cable would cause a problem.
Also, the stackoverflow.com link that @elatllat posted, suggests setting framebuffer_width and framebuffer_height, but these settings actually cause a lot of confusion and
won't fix the problem of
black bars around the screen.
Mostly, the black bars are caused either by the overscan settings or less often because the the automatically selected video mode isn't the optimum mode.
Could you run the following commands from a terminal and tell us the output.
On the Raspberry Pi I have at hand connected to a 1080p TV, the output is as follows:-
Code: Select all
% tvservice -s
state 0x12000a [HDMI CEA (16) RGB lim 16:9], 1920x1080 @ 60.00Hz, progressive
%fbset
mode "1920x1080"
geometry 1920 1080 1920 1080 16
timings 0 0 0 0 0 0 0
rgba 5/11,6/5,5/0,0/16
endmode
The important numbers are, in the output to tvservice, you want to see 1600x1200. In the fbset output, you want the mode to match you screen so 1600x1200.
If you the resolution reported by tvservice is not 1600x1200, run the tvservce with the following two command lines:-
This will give you a list of display mode that your screen has reported that it will support. Here is the list I got:-
Code: Select all
% tvservice -m CEA
Group CEA has 15 modes:
mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive
mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive
mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive
mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced
mode 6: 720x480 @ 60Hz 4:3, clock:27MHz x2 interlaced
mode 7: 720x480 @ 60Hz 16:9, clock:27MHz x2 interlaced
(prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive
mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive
mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive
mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced
mode 21: 720x576 @ 50Hz 4:3, clock:27MHz x2 interlaced
mode 22: 720x576 @ 50Hz 16:9, clock:27MHz x2 interlaced
mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive
% tvservice -m DMT
Group DMT has 5 modes:
mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive
mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive
mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive
mode 39: 1360x768 @ 60Hz 16:9, clock:85MHz progressive
mode 82: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive
If the resolution reported by tvservice is 1600x1200, but the mode reported by fbset isn't 1600x1200, then it is an issue with the overscan settings. The first thing to try is to turn overscan off. This may be counter intuitive, but by default with overscan on there is (if I remember correctly) a 16 pixel band of pixels left, right, top and bottom that is not used. To disable overscan you need to find the line in config.txt
Code: Select all
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
#disable_overscan=1
and change it to
Code: Select all
# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=1
As you are using NOOBS, the easiest way to edit conig.txt is to use the config editor on the NOOBS recovery screen. To get to the NOOBS recovery screen, hold down the [Shift] key on your keyboard when you power up your Raspberry Pi.