fixing underscan might crash X

[Peruna]

The latest (8.11) Fglrx drivers are underscanning with my FullHD TV, but only with 60 and 50Hz. Frequencies 30, 25 and 24 are working as they should.

Now I can use aticonfig --set-dispattrib=tmds2i,positionX:0 ...sizeX:1920 ...positionY:0 ...sizeY=1080 to fix underscan with 60 and 50Hz.

That would be fine (since those settings will be saved to amdpcsdb), but if I have set those attributes and I change frequency to those lower ones my X crashes (or propably Fglrx drivers).

And since current Fglrx drivers also save used mode to amdpcsdb, X crashes on all reboots (until I modify amdpcsdb to 60Hz mode or remove position and size attributes).

My guess is that "Display scaling to HDTV timings/resolutions." is not working correctly if I have set attributes manually and it does not work with 60 and 50Hz modes (at least on my Toshiba TV).

Is there a way to disable automatic scaling or is this issue going to be fixed anytime soon?

I'm using Ubuntu 8.04 (amd64).

[bridgman]

Now I can use aticonfig --set-dispattrib=tmds2i,positionX:0 ...sizeX:1920 ...positionY:0 ...sizeY=1080 to fix underscan with 60 and 50Hz..

FYI that is not the recommended solution for underscan. Can you try the solution Matthew posted ?

http://www.phoronix.com/forums/showthread.php?p=36734#post36734

[Peruna]

If you see the next message after MTippet message, you can see that I answered that and told that it worked. Unfortunately it does absolutely nothing with 8.11 version (it worked in every version before that).

That's why I decided to try the old solution.

[bridgman]

OK, I'll ask around and see if I can find out what changed...

[Peruna]

Thanks, I appreciate it.

On basic use this is not a bad issue since this is my media pc and I rather keep default rate as 25Hz since that's correct for rate when I watch TV. Unfortunately rate resets to 60Hz when it stops sending signal (but running xset dpms force standby|suspend|off does not reset frequency to 60, even though they all stop signaling).

That is one thing that would be nice to be "fixed". Returning to the same frequency that was before stopping signal.

[Peruna]

Am I really the only one who is having this issue?

I tried new 8.12 version and it seems to be bit worse than 8.11 since 25 Hz is also having black bars. Now only 30Hz and 24Hz seems to fill the full screen. This is very irritating because it seems that there is no way to fix this problem.

[olympia]

Am I really the only one who is having this issue?

I tried new 8.12 version and it seems to be bit worse than 8.11 since 25 Hz is also having black bars. Now only 30Hz and 24Hz seems to fill the full screen. This is very irritating because it seems that there is no way to fix this problem.

No, you are not the only one. I have the same problem unsolved, and know several people in the same shoes.

So I am also very interested in a possible solution/ workaround/ bugfix.

[hylpro]

No, you are not the only one. I have the same problem unsolved, and know several people in the same shoes.

So I am also very interested in a possible solution/ workaround/ bugfix.

please count me, my toshibaTV (46"), 2600HD, same problem, very boring. i had hope the 8.12 would be nice than 8.11....

[Raybuntu]

I'm having exact the same problem with fglrx 8.12! Is there any solution yet?

[Peruna]

OK, once again I need to put this thread on top.

New 9.1 version of drivers managed to break next working frequency (24Hz). 30Hz is still working and not causing black borders (just like on previous version). I really don't understand how hard this can be since on every new version of drivers one new frequency has broken.

"aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0" does nothing.

Bridgman promised to ask about this and maybe he did, but no solution seems to be available. This issue seems to be available with more people than just me (this is not the only thread that talked about this) so should this at least be listed on the issue list on release notes?

I guess that 9.2 will break even the last 30Hz mode.

[Kano]

Just test the leaked 9-2 ;)

[bridgman]

I asked, but asking is not the same as making a solution appear instantly ;)

The initial answer surprised me a bit -- apparently we *are* enabling underscan in VBIOS, not just in the driver, so I need to talk to a lot *more* people to find out the full story ;(

[Peruna]

Thanks for your reply. My message was not too well written as I did not expect actual solution but some info that this issue somehow registered by developers.

I did know (or guessed) that underscan is enabled before drivers as I have noticed that black borders are visible in boot process (and even when BIOS shows up). It would be nice if underscanning can be removed from there too, but it is not really important.

I haven't tested with this new driver will system crash if I manually set the coordinates with "aticonfig --set-dispattrib=tmds2i,positionX:0 ...sizeX:1920 ...positionY:0 ...sizeY=1080" and then change frequency. That would be acceptable temporary solution. Temporary because these settings need to be resetted every time I change frequency (if that hasn't changed).

[Peruna]

Time for another Catalyst version... 9.2...

Funnily that last working frequency (30Hz) also has black borders. Just as I assumed. DigitalHDTVDefaultUnderscan is not helping either as anyone could have guessed.

That "set-dispattr PositionX" etc. seems to be disabled for tmds2i. That maybe better since it only caused crashing on 9.1.

Is that DigitalHDTVDefaultUnderscan working for anyone anymore? If not, maybe ATI could check what broke it and do something about it...

Yet I want to add something positive too and I want to say that this 9.2 seems to be very fast. XV is not working too well, but I can actually watch FullHD video using OpenGL (with vsync) quite well. Also the MythTV fullscreen bug is fixed at last.

I find it more important that you fix current issues from drivers than add new features and this 9.2 seemed to do that for some problems. Best version ever (even with this stupid and irritating "black borders" issue).

[soder]

Time for another Catalyst version... 9.2...

Funnily that last working frequency (30Hz) also has black borders. Just as I assumed. DigitalHDTVDefaultUnderscan is not helping either as anyone could have guessed.

That "set-dispattr PositionX" etc. seems to be disabled for tmds2i. That maybe better since it only caused crashing on 9.1.

Is that DigitalHDTVDefaultUnderscan working for anyone anymore? If not, maybe ATI could check what broke it and do something about it...

Yet I want to add something positive too and I want to say that this 9.2 seems to be very fast. XV is not working too well, but I can actually watch FullHD video using OpenGL (with vsync) quite well. Also the MythTV fullscreen bug is fixed at last.

I find it more important that you fix current issues from drivers than add new features and this 9.2 seemed to do that for some problems. Best version ever (even with this stupid and irritating "black borders" issue).

I was hoping that the Cat 9.2 had fixed the "aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0"-problem, but appairently not..

Im now running a script at bootup in cat 9.1 that remove the "old" amdpcsdb and copy and default one, and then runs the
"aticonfig --set-dispattrib=tmds2i,positionX:0
aticonfig --set-dispattrib=tmds2i,positionY:0
aticonfig --set-dispattrib=tmds2i,sizeX:1280
aticonfig --set-dispattrib=tmds2i,sizeY:720 "

This works, but are not the right way to go..

Damned ATI fucking with the underscan....

/Söder

[bibi]

May you give us your script (specially how to create a default amdpcsdb)?

Bibi

[ivanovic]

The default file is automatically used at startup when no amdpcsdb is existing. That is: the file /etc/ati/amdpcsdb.default is simply copied over to /etc/ati/amdpcsdb if the file is not available when starting xorg.

[soder]

May you give us your script (specially how to create a default amdpcsdb)?

Bibi

1. Make your changes in CCC and save

2. cp /etc/ati/amdpcsdb /etc/ati/amdpcsdb.working

3. Create /etc/init.d/amdpcsdb-recover.sh with this content:
#!/bin/bash
cp /etc/ati/amdpcsdb.working /etc/ati/amdpcsdb

4. chmod +x /etc/init.d/amdpcsdb-recover.sh

5. ln -s /etc/init.d/amdpcsdb-recover.sh /etc/rcS.d/S50amdpcsdb-recover.sh

6: Create atiunderscan.sh with following content (make changes for your TV):
#!/bin/bash
aticonfig --set-dispattrib=tmds2i,sizeX:1280
aticonfig --set-dispattrib=tmds2i,positionX:0
aticonfig --set-dispattrib=tmds2i,sizeY:720
aticonfig --set-dispattrib=tmds2i,positionY:0

7. chmod +x atiunderscan.sh

8 Add "sh /path/to/atiunderscan.sh" in autostart under Preferenes > Sessions in Gnome.

9. Reboot

/Söder

[Peruna]

It should be noted that Söder's fix only works with Catalyst 9.1 and older. And I would assume that it crashes if you try to change frequency on the fly using xrandr (for example "xrandr -r 50" or what ever is available on your TV).

I myself want to watch 24p movies with 24Hz mode, but still have 60Hz when I do something else.

Yet Söder's fix probably is sufficient for many. So thanks!

[bibi]

Thank you :), i'll try it tonight with 9.2.

[soder]

It should be noted that Söder's fix only works with Catalyst 9.1 and older. And I would assume that it crashes if you try to change frequency on the fly using xrandr (for example "xrandr -r 50" or what ever is available on your TV).

I myself want to watch 24p movies with 24Hz mode, but still have 60Hz when I do something else.

Yet Söder's fix probably is sufficient for many. So thanks!

That workd for now for me. You saying that
aticonfig --set-dispattrib=tmds2i,positionX:0
aticonfig --set-dispattrib=tmds2i,positionY:0
aticonfig --set-dispattrib=tmds2i,sizeX:1280
aticonfig --set-dispattrib=tmds2i,sizeY:720

are not working in the Cat 9.2?

What the fuck are ATI doing? First the screw up the aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0 and now this.

How are we gonne compensate for the underscan there shitty drivers cause.....

/Söder

[Peruna]

Yep, setting those values in 9.2 just causes error message telling that they can not be used with used input (which is tmds2i for me).

At least bridgman said in other thread that this is a real issue that needs to be fixed. I have been waiting for fix since 8.11 broke DigitalHDTVDefaultUnderscan,0.

[soder]

Yep, setting those values in 9.2 just causes error message telling that they can not be used with used input (which is tmds2i for me).

At least bridgman said in other thread that this is a real issue that needs to be fixed. I have been waiting for fix since 8.11 broke DigitalHDTVDefaultUnderscan,0.

Oh, so that was allready broken in 8.11..?

I used the 8.552 or something from the normal installation+upgrade in Ubuntu 8.10 before this 9.1

Maybe better to go back to the that version again if ATI cant do better.

Dont know if I have something to win with the newer drivers since I only use it for XBMC.

/Söder

[cyrus_mc]

That workd for now for me. You saying that
aticonfig --set-dispattrib=tmds2i,positionX:0
aticonfig --set-dispattrib=tmds2i,positionY:0
aticonfig --set-dispattrib=tmds2i,sizeX:1280
aticonfig --set-dispattrib=tmds2i,sizeY:720

are not working in the Cat 9.2?

What the fuck are ATI doing? First the screw up the aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0 and now this.

How are we gonne compensate for the underscan there shitty drivers cause.....

/Söder

Not sure if this will help, but when I ran those commands (only did it one time cause this work around for the underscan sucks) I had to use positionx, positiony, sizex and sizey, not the capital X, Y. If I used capital it said value not supported by my monitor or outside allowable range.

[mrechte]

Hi,

After hours of Internet researches to solve the underscanning issue (HD3200 chip), I was happy with aticonfig fix, despite the fact of having to reset the ati dafaults upon reboot.

A few days ago Fedora 10 upgraded to version 9.2 and aticonfig now refuses to change position and size, as stated above:

aticonfig --set-dispattrib=tmds2i,positionX:0
Try to Set positionX adjust of monitor tmds2i value : 0 failed.
It may not supported by monitor or the value beyond the range.


Is there a fix planned soon ?

Why does fglrx underscans whereas ati does not (I checked the modeline they are the same with both drivers, consistant with EDID data sent my the Samsung TV) ?

Many thanks

[cyrus_mc]

Hi,

After hours of Internet researches to solve the underscanning issue (HD3200 chip), I was happy with aticonfig fix, despite the fact of having to reset the ati dafaults upon reboot.

A few days ago Fedora 10 upgraded to version 9.2 and aticonfig now refuses to change position and size, as stated above:

aticonfig --set-dispattrib=tmds2i,positionX:0
Try to Set positionX adjust of monitor tmds2i value : 0 failed.
It may not supported by monitor or the value beyond the range.


Is there a fix planned soon ?

Why does fglrx underscans whereas ati does not (I checked the modeline they are the same with both drivers, consistant with EDID data sent my the Samsung TV) ?

Many thanks

Did you look at the post right above your post from me? It basically tells you what to do.

[Peruna]

For me it makes no difference whether I use capital X and Y or not.

It prints exactly the same error message.

This is with 9.2 x64 and tmds2i connection.

[mrechte]

Capital or or not does not change anything for me either.

[soder]

What are you all users with hd3200 doing now? Staying on 9.1 and using the scripts, or staying at 8.x and uses the UNDERSCAN_0 option?

All I want is to run XBMC as good as possible, and with no underscan.

Im getting tired of my script. I cant use suspend, cause when the htpc wake up theres no screen. I also cant boot the htpc without turning my TV on first...

=(

/Söder

[Mr. Hilarious]

What are you all users with hd3200 doing now? Staying on 9.1 and using the scripts, or staying at 8.x and uses the UNDERSCAN_0 option?


For me, I fixed the problem in 8.12 (might have been 9.1 or 8.11, I really don't recall) by running:

aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0

and, I believe something was recorded in my grapchics BIOS, since once I upgraded I've never had a ******d up scan on my TV since. I believe the above doesn't record anything into amdbcsdb, but the

aticonfig --set-dispattrib=tmds2i,positionX:0
aticonfig --set-dispattrib=tmds2i,positionY:0
aticonfig --set-dispattrib=tmds2i,sizeX:1920
aticonfig --set-dispattrib=tmds2i,sizeY:1080

on the other hand, does, and locks up the Xorg at the next start. So, if you get a hang system at X.org start, make sure you delete the amdpcsdb (or move it away) while X.org is not running to make sure you start clean (the file gets written again at every X.org exit so deleting it while X.org is running will not work).

Oh, and I using:

Gentoo
Gigabyte GA-MA78GM-S2H (with the builtin 780G integrated HD3200)
Catalyst 9.2 currently


Hope this helps someone =)

[soder]

For me, I fixed the problem in 8.12 (might have been 9.1 or 8.11, I really don't recall) by running:

aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0

and, I believe something was recorded in my grapchics BIOS, since once I upgraded I've never had a ******d up scan on my TV since. I believe the above doesn't record anything into amdbcsdb, but the

aticonfig --set-dispattrib=tmds2i,positionX:0
aticonfig --set-dispattrib=tmds2i,positionY:0
aticonfig --set-dispattrib=tmds2i,sizeX:1920
aticonfig --set-dispattrib=tmds2i,sizeY:1080

on the other hand, does, and locks up the Xorg at the next start. So, if you get a hang system at X.org start, make sure you delete the amdpcsdb (or move it away) while X.org is not running to make sure you start clean (the file gets written again at every X.org exit so deleting it while X.org is running will not work).

Oh, and I using:

Gentoo
Gigabyte GA-MA78GM-S2H (with the builtin 780G integrated HD3200)
Catalyst 9.2 currently


Hope this helps someone =)

Well, as I understand, both options are not working on the 9.2 driver.

I used the underscan options before, and it worked well. It saved the info in the amdpcsdb.

/Söder

[Mr. Hilarious]

Well, as I understand, both options are not working on the 9.2 driver.


This is how I've understood it, too. At some point the first solution stopped working (might have been around 8.12~ish) and then the latter solution stopped working. In addition, the latter solution always hung up peoples boxes at the next X.org sartup, so people needed to use some script to delete the amdpcsdb.

So, you might want to downgrade to a some earlier version, run the first fix, and downgrade again if it doesn't work. If it does, you could then upgrade back to the newest version and pray. I'd presume this would work, since I don't have this problem; though I've never actually done the above (I just used the fix when a version where it worked was recent).

Yeah, this sucks.

[mrechte]

Now it has become very bad on my install: I am no longer able to use the 9.2 catalyst, X server produces a seg fault at start up.

With ati driver, at X startup, 50% of the time the Samsumg TV indicates a "not supported mode". I have to switch from terminal mode to X mode (Ctl+Alt+F2 / Alt+F1) many times until eventually I get the TV displays the Gnome desktop (or until I am tired) !

It is really depressing to have reached such a usefulness state after so many efforts...

Will CC 9.3 version be our saver ?

Regards

[Peruna]

You probably need to remove your /etc/ati/amdpcsdb file. If I use amdcccle at some point it (or driver or whatever) saves current resolution there just to set it again when X is restarted. For some unknown reason that causes crash on startup.

By removing the whole file or just needed lines in the file you can probably start it again.

[Peruna]

New 9.3 release actually fixes overscan perfectly. It also seems to have as good performance as 9.2. So good work ATI!

The issue mentioned in previous message (crash on startup if amdpcsdb contains resolution set on startup) is still available, but if this driver is as stable as previous I don't care for now. I rebooted this computer about twice when 9.2 was used (and neither of boots was caused by ATI drivers).

[mrechte]

New 9.3 release actually fixes overscan perfectly. It also seems to have as good performance as 9.2. So good work ATI!
.

In 9.3 Catalyst Centre there is a setting (slider) for adjusting the underscanning that when put to 0% fixes the problem. However next time X will start it will crash (fix is to restore /etc/ati/amdpcsdb file to the default before starting X).

I could not find the equivalent aticonfig for adjusting the underscanning. Any idea ? (ps.*I tried aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0 and aticonfig --set-dispattrib tmds2i,positionX:0... without any success).

Thanks

[cyrus_mc]

In 9.3 Catalyst Centre there is a setting (slider) for adjusting the underscanning that when put to 0% fixes the problem. However next time X will start it will crash (fix is to restore /etc/ati/amdpcsdb file to the default before starting X).

I could not find the equivalent aticonfig for adjusting the underscanning. Any idea ? (ps.*I tried aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0 and aticonfig --set-dispattrib tmds2i,positionX:0... without any success).

Thanks

Using 9.3 and the Control panel to set underscan to 0% does not crash X for me. Work perfectly. It is about time ATI fixed that issue.

[bridgman]

mrechte, can you give some info about your configuration (GPU, bus, distro etc...) ?

[mrechte]

mrechte, can you give some info about your configuration (GPU, bus, distro etc...) ?

I confirm that X start up crashes at the nex start-up unless I reset the default values.

My config is Fedora 10 on a Gigabyte MA78GPM-DS2H mother boeard (HD3200 chipset with 128MB of dedicated video RAM). Monitor a Samsumg TV (LEA52) on HDMI port.

Please, if at least I could issue an aticonfig command to restore my parameters automatically when Gnome session is opened, that would be nice (rather than going manually into CCC each time)

Thanks

[soder]

I just picked up my new Nvidia GeForce 9400 GT. Not ATI for me for a while...

/Söder

[JAR72]

I confirm that X start up crashes at the nex start-up unless I reset the default values.

My config is Fedora 10 on a Gigabyte MA78GPM-DS2H mother boeard (HD3200 chipset with 128MB of dedicated video RAM). Monitor a Samsumg TV (LEA52) on HDMI port.

Please, if at least I could issue an aticonfig command to restore my parameters automatically when Gnome session is opened, that would be nice (rather than going manually into CCC each time)

Thanks

I was having the same issue when fixing underscan using CCC. What worked for me was to fix the underscan in CCC for the display and then clicking the override default button right below it. The settings were saved on the next reboot. No more underscan.

I could not, however, change the refresh rate from 24Hz to 60Hz.

Hope this helps.

[mrechte]

I am pleased to inform that my HD3200 is now working fine (on Fedora 10) with catalyst 9.5 (including desktop effects and video playback and no more under-scanning).

Thanks to Fedora and AMD.

Please don't break it again.

[Mr. Hilarious]

WARNING:

With Catalyst 9.6., you might get Overscan breakage AGAIN. I couldn't find a way to fix it quickly but I will post here again if I do.

I already tried:

aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0

And I will now try the other fix. EDIT: The other way (with aticonfig --set-dispattrib) doesn't work, either. Also, in amdcccle, the option is greyed out. Also, I still can only run amdcccle as root, btw (if I run it as a regular user, all it's bits and segments fault terribly).

Good work AMD!

If anyone has any suggestions, they are deeply appreciated.

[bridgman]

Wondering if it might be some kind of permission issue. Maybe try renaming or deleting the amdpcsdb and running aticonf --initial again. Try not to run aticonfig --initial as root.

[Mr. Hilarious]

With Catalyst 9.6., you might get Overscan breakage AGAIN. I couldn't find a way to fix it quickly but I will post here again if I do.


I was able fix it, but then I was hit by a different bug. The:

aticonfig --set-pcs-val=MCIL,DigitalHDTVDefaultUnderscan,0

did eventualy fix the underscan, but I needed to 1) run it when X.org was NOT running (i.e. from a VC), and, also I needed to 2) delete the amdpcsdb file prior to running it. If I didn't do either one of those, then there was the underscan still present next start of Xorg.

BUT, while figuring that out, I got the other problem. At some point the fonts got all screwy, probably because of deleting the amdpcsdb file. After upgrading to 9.6, initially the fonts were OK (with the underscan), but then, suddenly all the fonts were changed to unreadable size; i.e. 3 pixels high (and at this point I got the underscan fixed). There used to be a very old bug in X.org that caused the same issue (but that was fixed). I got the dimensions of my LCD TV told (or lied, because Xorg does not have settings for viewing distance) in xorg.conf.

After deleting everything in /etc/ati and re-installing the 9.6, I gave up and downgraded to 9.5 (aka. 8.612 - previosly I had 9.4), and all the fonts are puffy again as they should be. If someone is interested, I got the Xorg.0.log file for 9.6 when the fonts didn't work, and one right after the downgrade to 9.5 (where everything is as it should be).

Wondering if it might be some kind of permission issue. Maybe try renaming or deleting the amdpcsdb and running aticonf --initial again. Try not to run aticonfig --initial as root.

Bridgman: I didn't try your suggestion, as I red it after I downgraded. I did run 'aticonfig --initial', but I did so as root. It added one line to my Xorg.conf (a line for PCIID of the card, but that didn't change anything, since the driver did find the card without one). I thought running aticonfig --initial only checks the current xorg.conf (or one given to it on the command line) and makes changes if needed - and as such it would not make sense to run it as non-root. Am I missing something? Maybe I should try it again at some point.

You might be right in that there might have been some permission issue somewhere for a long time, since suddenly I am able to run amdcccle as a regular user, after this upgrade-downgrade hassle.

[Mr. Hilarious]

Hi again. I've been using 9.5 for a while, but decided to return to this issue. I made some discoveries and thought I'll share my findings here :)

It seems, that the issue with the fonts might actually be a X.org bug. With all other drivers than <=9.5 fglrx, I get the same behaviour; the fonts are way too small (1-2 pixel high). By looking at the Xorg.0.log file, I found out, that the DisplaySize option is read correctly by X.org. But the EDID information overrides this later on! Here's a snippet from my xorg.log:


(II) fglrx(0): ***Display: ConnectedDisplayTypes=0x00000080, disabled=0x00000000
(II) fglrx(0): Connected Display1: DFP on secondary TMDS [tmds2i]
(II) fglrx(0): Display1 EDID data ---------------------------
(II) fglrx(0): Manufacturer: SNY Model: 5c01 Serial#: 16843009
(II) fglrx(0): Year: 2008 Week: 1
(II) fglrx(0): EDID Version: 1.3
(II) fglrx(0): Digital Display Input
(II) fglrx(0): Max Image Size [cm]: horiz.: 160 vert.: 90
(II) fglrx(0): Gamma: 2.20
(II) fglrx(0): No DPMS capabilities specified
(II) fglrx(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
(II) fglrx(0): First detailed timing is preferred mode
(II) fglrx(0): redX: 0.625 redY: 0.340 greenX: 0.280 greenY: 0.595
(II) fglrx(0): blueX: 0.155 blueY: 0.070 whiteX: 0.283 whiteY: 0.298
(II) fglrx(0): Supported established timings:
(II) fglrx(0): 640x480@60Hz
(II) fglrx(0): 800x600@60Hz
(II) fglrx(0): 1024x768@60Hz
(II) fglrx(0): Manufacturer's mask: 0
(II) fglrx(0): Supported standard timings:
(II) fglrx(0): #0: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
(II) fglrx(0): Supported detailed timing:
(II) fglrx(0): clock: 148.5 MHz Image Size: 1600 x 900 mm
(II) fglrx(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
(II) fglrx(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
(II) fglrx(0): Supported detailed timing:
(II) fglrx(0): clock: 74.2 MHz Image Size: 1600 x 900 mm
(II) fglrx(0): h_active: 1280 h_sync: 1390 h_sync_end 1430 h_blank_end 1650 h_border: 0
(II) fglrx(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
(II) fglrx(0): Monitor name: SONY TV XV
(II) fglrx(0): Ranges: V min: 48 V max: 62 Hz, H min: 14 H max: 70 kHz, PixClock max 150 MHz
(II) fglrx(0): Number of EDID sections to follow: 1
(II) fglrx(0): EDID (in hex):
(II) fglrx(0): 00ffffffffffff004dd9015c01010101
(II) fglrx(0): 0112010380a05a780a0dc9a057479827
(II) fglrx(0): 12484c21080081800101010101010101
(II) fglrx(0): 010101010101023a801871382d40582c
(II) fglrx(0): 450040846300001e011d007251d01e20
(II) fglrx(0): 6e28550040846300001e000000fc0053
(II) fglrx(0): 4f4e592054562058560a2020000000fd
(II) fglrx(0): 00303e0e460f000a20202020202001e4
(II) fglrx(0): End of Display1 EDID data --------------------
(II) fglrx(0): Output CRT1 using monitor section aticonfig-Monitor[0]
(II) fglrx(0): Output DFP2 has no monitor section
(II) fglrx(0): Output CRT1 disconnected
(II) fglrx(0): Output DFP2 connected
(II) fglrx(0): Using exact sizes for initial modes
(II) fglrx(0): Output DFP2 using initial mode 1920x1080
(**) fglrx(0): Display dimensions: (480, 270) mm
(**) fglrx(0): DPI set to (101, 180)


Note the size reported by EDID: 160 x 90cm! In addition, that it is not true (the right measurements are around 90cm x 50cm for this 40" display, which would actually give something readable, albeit not comfortably sized when wieving from your couch), one would like to "lie" to X.org that the display is actually smaller than it is, since the viewing distance is longer. So the EDID information makes things even worse than they were with the right measurements. The DisplaySize setting I have in xorrg.conf (480X270, that will give something around ~110DPI'sh), is detected correctly above.

But with every other driver than fglrx 9.5, the EDID information given by my LCD overrides the option! Somewhat later in the Xorg.0.log file:

(II) fglrx(0): Setting screen physical size to 1600 x 900

xdpyinfo also gives the same figures (once I get a usable font size set into a terminal window).

I got this behavious with the radeonhd driver also (the only one that should work with the 780G / HD3200; well I didn't try vesa), in addition to the fglrx driver 9.6.. For some reason, DisplaySize option DOES work correctly with fglrx 9.5.

As a workaround, I put "xrandr --dpi 125" into /usr/share/config/kdm/Xsetup (I'm using KDE4 KDM). It was the only way I could figure out to force the DPI setting. For some reason, the login screen doesn't use the DPI setting, even though it should. But, after I login, the KDE session does use the setting.

Well, I hope this helps, in case someone is hit by the same issue.

[Mr. Hilarious]

Hi once again!

After upgrading to 9.7 and xorg-server 1.6.2-r1 (among some other X.org, DRM and Mesa libraries), the DisplaySize option started to working again. Now, at the physical size setting part in Xorg.conf, Xorg.0.log says:

(WW) fglrx(0): Probed monitor is 1600x900 mm, using Displaysize 448x252 mm

I also cleaned up (made a fresh one) xorg.config. I'm not sure what actually was the culprit, but I'm happy that it works now :).

And sorry for hijacking this old(ish) thread :D