Red Hat Bugzilla – Bug 379221
Unable to rotate screen on Toshiba Portege 3500 using trident driver
Last modified: 2008-08-02 19:40:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:184.108.40.206) Gecko/20071022 Ubuntu/7.10 (gutsy) Firefox/220.127.116.11
Description of problem:
When I add the line:
Option "Rotate" "CW"
to my /etc/X11/xorg.conf file to rotate the screen, the display comes up garbled. The system has not frozen as I am able to kill the X server and switch VTs.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add Option "Rotate" "CW" to the device section in xorg.conf
2. Restart X Server
The display comes up garbled.
The display should have been rotated 90 degrees clockwise.
Thanks for the bug report. We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.
Please attach your X server config file (/etc/X11/xorg.conf) and X server log
file (/var/log/Xorg.*.log) to the bug report as individual uncompressed file
attachments using the bugzilla file attachment link below.
Could you please also try to run without any /etc/X11/xorg.conf whatsoever and
let X11 autodetect your display and video card? Attach to this bug
/var/log/Xorg.0.log from this attempt as well, please.
We will review this issue again once you've had a chance to attach this information.
Thanks in advance.
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Have you tried using xrandr? Did it work?
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.