Something that is interesting me since I started using an HDMI connection on my AMD graphics card.
Some distros, such as Crunchbang, work flawlessly and boot to the expected screen display, in my case @1920x1080res.
VSIDO and LinuxBBQ also succeed in this task, amongst other distros.
However, some distros result in 'overscan' whereby the image display is squashed into the centre of the screen.
Or rather, a band around the monitor display area is not active...
My solution here has been to use the AMD Catalyst driver and use amdcccle control centre to adjust the overscan to zero.
One problem is that, sometimes and on some distros, this setting is not kept between reboots (and I have used sudo).
I would also rather not have to go through this routine.
So, in short, why is it that some distros, such as the almighty Crunchbang, have no issues with overscan on HDMI, whereas some,using the same kernels, do have this isssue?
Last edited by chameleon (2013-03-17 20:14:24)
Could be the way Debian compiles it's kernels, as Crunchbang, LinuxBBQ, & VSIDO are all Debian based.
My solution to this has been to install an nvidia card on my AMD motherboard.
Poor show AMD life is to short to mess around with graphics configs.
OK bang for buck AMD processors Rock but for graphics nvidia rules in Linux land!
This is not a bug but an intended feature from AMD/ATI, supposedly to work with all HDMI screens/TVs out there. Unfortunately changing the overscan/underscan slider on amdcccle utility doesn't stick on reboot. You may correct this by manually changing (as root):
# aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0
Rebooting will keep this setting permanent.