Created attachment 111020 [details] Capture of two monitors first card I have two Radeon HD7970 installed in my PC. The PC has installed Debian Jessie with XFCE as graphical enviroment. The PC had two monitors connected to the first Radeon card and it was working fine. Today I attached a old flat monitor in the second Radeon card. After some configuration in xorg.conf I can use the third monitor as second screen (xorg screen). The problem is the text have some corruption and make the read impossible. The graphics are fine only the text is affected. Text in terminal and xterm are fine. Only the fonts of the graphics programs are affected.
Created attachment 111021 [details] Capture of third monitor in second card
Created attachment 111022 [details] Xorg log
Created attachment 111023 [details] xorg.conf
This should be fixed in xserver 1.16.99.901 or later, specifically these commits: http://cgit.freedesktop.org/xorg/xserver/commit/?id=0acff6e4374340dc391014f396f190daf73d579c http://cgit.freedesktop.org/xorg/xserver/commit/?id=a4e8e6dff9a0c26944a325e4017faa68d93ae5b8 http://cgit.freedesktop.org/xorg/xserver/commit/?id=710d314ad16cf1eaca3b97b1736ff0ca43e598c4 http://cgit.freedesktop.org/xorg/xserver/commit/?id=1d32004ed5a3a20b2d5879867e213122dced69d0
Olaf, if you can confirm that those commits fix the problem, maybe Julien can consider backporting them to the 1.16 branch.
(In reply to Michel Dänzer from comment #5) > Olaf, if you can confirm that those commits fix the problem, maybe Julien > can consider backporting them to the 1.16 branch. Thanks Michel, I would like to confirm this by myself, but i'm not sure what to do. Can you give me some guidance?
(In reply to Michel Dänzer from comment #5) > Olaf, if you can confirm that those commits fix the problem, maybe Julien > can consider backporting them to the 1.16 branch. Ok, I think now understand. I'm gonna clone xorg-server-1.16.1.901 via git. Then apply the patches you indicated me (from the specific commits) and compile it. Then test if the problem is gone. This is correct? Sorry for this. I have no experience with xorg and I have basics skills in git.
(In reply to Olaf from comment #7) > I'm gonna clone xorg-server-1.16.1.901 via git. Then apply the patches you > indicated me (from the specific commits) and compile it. Then test if the > problem is gone. > > This is correct? Yes, exactly.
(In reply to Michel Dänzer from comment #8) > (In reply to Olaf from comment #7) > > I'm gonna clone xorg-server-1.16.1.901 via git. Then apply the patches you > > indicated me (from the specific commits) and compile it. Then test if the > > problem is gone. > > > > This is correct? > > Yes, exactly. I made the test using xorg-server-1.16.1.901 with the commits you indicated me and the text corruption is still present. Also made the test using xorg-server-1.16.2.901 with the same commits and I got text corruption. Does I need to pair the version of xserver with a specific version of radeon driver? In both tests I used version 7.5.0.
Now I tested the last version of xserver, radeon driver and glamor module and the xserver die with segmentation fault.
Created attachment 111060 [details] Xorg log with segmentation fault This happens using the last versions of xserver, radeon driver and glamor module.
I recompiled glamor again and now the segmentantion is gone. Now the graphics don't have fill, I see only black and blue boxes without text in login dialog. The background of debian looks fine. After a lot of blind tries I was able to login and see that the third monitor still have corruption in text even with the latest xorg and radeon driver.
Created attachment 111063 [details] xorg log with latest versions
Created attachment 111064 [details] picture of login dialog
> [ 126.087] (II) Loading sub module "glamoregl" > [ 126.087] (II) LoadModule: "glamoregl" > [ 126.087] (II) Loading /usr/local/lib/xorg/modules/libglamoregl.so > [ 126.087] (II) Module glamoregl: vendor="X.Org Foundation" > [ 126.087] compiled for 1.16.99.901, module version = 0.6.0 You're using glamor from the standalone tree. Please use glamor from the xserver tree instead.
(In reply to Michel Dänzer from comment #15) > > [ 126.087] (II) Loading sub module "glamoregl" > > [ 126.087] (II) LoadModule: "glamoregl" > > [ 126.087] (II) Loading /usr/local/lib/xorg/modules/libglamoregl.so > > [ 126.087] (II) Module glamoregl: vendor="X.Org Foundation" > > [ 126.087] compiled for 1.16.99.901, module version = 0.6.0 > > You're using glamor from the standalone tree. Please use glamor from the > xserver tree instead. Ok, Now, finally, I made a right compilation of xserver with the right glamor and yes! the text corruption is gone! (in last version of xserver) Thanks a lot! Also I applied the commits you told me to the last version of 1.16 branch (X.Org X Server 1.16.3) and I can confirm that the commits solves the text corruption in that branch. I have applied the changes manually because there are some functions affected in the 1.16 branch and I had to solve some minor errors in compilation. Now, how we inform Julien to backport this commits into the 1.16 branch? Or how can I integrate this changes in the 1.16 branch?
Created attachment 111294 [details] Xorg log of branch 1.16
(In reply to Olaf Hernandez B from comment #16) > Now, how we inform Julien to backport this commits into the 1.16 branch? I already added him to the CC list of this report. If you could create proper Git patches for the backported fixes and attach them here or send them to Julien and the xorg-devel mailing list by e-mail, that might be helpful.
> I already added him to the CC list of this report. If you could create > proper Git patches for the backported fixes and attach them here or send > them to Julien and the xorg-devel mailing list by e-mail, that might be > helpful. I have ready the patch. Thank you for your support.
Created attachment 111310 [details] [review] Backported code from 1.16.99 branch to correct text corruption in glamor
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.