[lizzi]

Ey - act sane or we will never find a solution.

I want to see photo of the "screen extending beyond the viewable" area ... that's an overscan issue. Also I want all the logfiles from above or we need until new year's eve to solve your issue. And while at it I also need: xrandr --verbose | pastebinit

And I want to see xrandr --verbose | pastebinit _before_ you manually fiddle anything, please (the xorg.conf is fine).

and from that pastebin

xrandr --verbose | pastebinit
http://pastebin.com/QYMfDa7Y

[lizzi]

Fritsch, i do appreciate your willingness to help with this. I thinks thats everything you asked for. Anything else?

[lizzi]

here's the dmesg | pastebinit. i had to sudo that

sudo dmesg | pastebinit
http://pastebin.com/yTZMkXhn

[lizzi]

if there's nothing else, i am tired. i spent all day on this with the folks from pacbang arch trying to get it to work with catalyst because manjaro has it working with catalyst.

I've spent several hours with you this evening and i am pooped. I listen for an email until i fall asleep

[fritsch]

1600x900_30.00 (0x56) 55.000MHz -HSync +VSync
h: width 1600 start 1648 end 1800 total 2000 skew 0 clock 27.50KHz
v: height 900 start 903 end 908 total 919 clock 29.92Hz

Which mode line is that? It's an interlaced one with just 30 hz.

xrandr --newmode "1600x900_59.94" 118.00 1600 1696 1856 2112 900 903 908 934 -hsync +vsync

please ^^ use this one and post again. Also post it after doing: xrandr --output HDMI-0 --mode 1600x900 and then we can see.

For the "picture too large", see:

underscan: off

Turn it on with xrandr and see if that fixes your issue. Best would be though to set the TV to "Just Scan" or "Fixed". Fglrx defaults underscans, but OSS driver does not. I am quite sure that will already fit on your screen.

[lizzi]

ok, that mode you quoted was me expirimenting because i seen that catalyst/fglrx used 30 htz for 1600x900 so i thought i'd try that in addition to the things you asked me to try.

I allready tried the newmode line you asked me to run and it gave me a blank screen. the mode yo see there was an expiriment with xorg.conf

[lizzi]

ok so setting under scan to on did not fix the desktop being bigger than the viewable area for 1920x1080 but did fix it for the 1280x720 resolution.

That's progress at least.

[lizzi]

so what else?

[lizzi]

sudo dmesg | pastebinit
http://pastebin.com/NFj3TMWV

xrandr --verbose
http://pastebin.com/YeCKkpDs

cat /var/log/Xorg.0.log | pastebinit
http://pastebin.com/CiEL6t9k

xrandr -q |pastebinit
http://pastebin.com/rNsTbTQf

[fritsch]

Add the 59.94 1600x900 mode and switch to it - what happens?

[lizzi]

Add the 59.94 1600x900 mode and switch to it - what happens?

the screen goes blank

[lizzi]

what else?

[fritsch]

Good or not good :-) so for now we have a working 1280x720 mode with vdpau and video acceleration support. Can you give me the model number of your TV, please I want to find out its native mode.

[Koying]

Haha... Linux is so much better than Android, indeed.
3 dysfunctional display drivers for the same hardware. Pick your choice

PS Apologies to the OP for the thread hijacking. Just to show how clueless posting is annoying

[asavah]

Haha... Linux is so much better than Android, indeed.
3 dysfunctional display drivers for the same hardware. Pick your choice

PS Apologies to the OP for the thread hijacking. Just to show how clueless posting is annoying

@Koying while I appreciate your work and your contribution to Kodi let me point this:

And now does Android not use Linux kernel?
Can you fix driver blobs' issues (mali and etc) in Android without source code?
GNU/Linux certainly is far from perfect, but if there are issues with OSS drivers skilled people (like yourself) could certainly fix those issues,
while in Android with a few exceptions you are bound to whatever crap the vendor gives you.

If OP's problem is driver related it certainly can be fixed if the right person looks into the issue, the sources are there ...