Summary: | Rotated Display Output Fractured | ||
---|---|---|---|
Product: | xorg | Reporter: | klsu |
Component: | Driver/Radeon | Assignee: | xf86-video-ati maintainers <xorg-driver-ati> |
Status: | RESOLVED FIXED | QA Contact: | Xorg Project Team <xorg-team> |
Severity: | normal | ||
Priority: | medium | ||
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
Description
klsu
2016-09-06 22:51:35 UTC
Please attach the corresponding Xorg log file. Anyway, this is probably fixed by https://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=6d91fb4fc701895473ff675f440a8eef655e80ca . Can you try a PPA which contains an xf86-video-ati Git snapshot? Created attachment 126258 [details]
Most recent Xorg log file
The attached Xord.0.log is the only Xorg log on the machine with 2 displays, and has a date stamp of the same day, so I assume it's most recent.
I'll see if I can figure out your other comments.
Created attachment 126261 [details]
XUbuntu Boot Splash screen (note broken mouse).
Herr Dänzer, Using the link you provided and one I found looking for a "PPA which contains an xf86-video-ati Git snapshot": https://cgit.freedesktop.org/xorg/driver/xf86-video-ati/commit/?id=38797a33117222dadbc89e5f21ed8cd5deef9bea ...present me with 1 and 3 files (respectively) that appear to be C (or C++) program files. It has been a good 20 years since I've compiled anything, and have never had to compile anything on a linux machine, nor have I ever had anything to do with video drivers. I understand a bit about mapping a virtual desktop to display memory, because of something I did in the late 1980s, therefore, I suspect that if whoever wrote the drivers for this sees the desktop, they'll know what's wrong. Therefore I'm attaching photos during boot, at the login screen and at the desktop, plus a screen shot of the same desktop using Print Screen. I am not afraid to try to do whatever needs to be done, but have yet to find clear instructions on how to compile and install code on a linux machine, so I guess I'll just have to wait until the drivers in the Ubuntu PPAs for 16.04 have been updated. Created attachment 126263 [details]
XUbuntu Logon Screen shows the problem even with a solid background.
Created attachment 126264 [details]
Desktop after loging on.
Created attachment 126265 [details]
Desktop after logging on, as seen by Print Screen.
The commit referenced in comment 1 most likely fixes this. Please reopen this report if it doesn't. You can try either of these PPAs: (doesn't involve compiling anything) https://launchpad.net/~paulo-miguel-dias/+archive/ubuntu/mesa/ https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers 2 minor corrections to my previous posts: A 64 bit installation with a Radeon (not NVIDIA) video card does not have the problem. Attachment 126261 [details] XUbuntu Boot Splash screen is the wrong description; the splash occurs after logging on before the desktop is displayed.
Thank you Herr Dänzer; the solution corrects the problem on this machine. The instructions on the first link tell how to add the PPA but not what to do after that. The instructions on the second link were better; but "...update your Ubuntu with the package herein" doesn't say what the name of the package is.
sudo add-apt-repository ppa:oibaf/graphics-drivers
sudo apt-get install mesa-vdpau-drivers
...didn't install any depends or upgrades, and did not solve the problem.
So I followed the instructions for reverting to the original drivers. In a terminal I ran:
sudo add-apt-repository ppa:oibaf/graphics-drivers
Then I started the Synaptic package manager, forced it to update its package list, searched for mesa-v and found one that was shown as requiring upgrade. Marked for upgrade it and everything else that could be upgraded, and let Synaptic make the changes. After re-boot, the rotated screen displayed properly. Shouldn't the UBuntu Xenial repository be updated with this fix?
|
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.