Unable to rotate screen with trident chipset

[MikeShoup]

Binary package hint: xorg

I am unable to rotate the screen on my Toshiba Portege 3500 which uses a Trident Cyberblad XPi chipset.

When I add the line Option "Rotate" "CW" to the device section in the xorg.conf file, the option is simply ignored.

This has worked in older (pre-Xorg) distributions of linux.

[Dog (brische)]

Same issue/same hardware. RandR settings in Xorg.conf seem to be ignored and xrandr commands generate an error if attempting to set screen orientation to anything other than standard (xrandr -o 0). Although probably not related, switching input orientation via xsetwacom works fine.

Output of command xrandr -o 3

X Error of failed request: BadMatch (invalid parameter attributes)
  Major opcode of failed request: 154 (RANDR)
  Minor opcode of failed request: 2 (RRSetScreenConfig)
  Serial number of failed request: 12
  Current serial number in output stream: 12

[Brian Murray (brian-murray)]

I am changing the status of the bug report to Confirmed based on the fact that there is a second person having this issue. For further information about bug statuses please look at https://wiki.ubuntu.com/Bugs/Status .

[Timo Aaltonen (tjaalton)]

The driver simply doesn't support that, at least not anymore.

[adam (afb3)]

Does anyone know when/if support will be added? This is the only part of my tablet that I cannot get to work.

[Dan Cotruta (dan-cotruta)]

I'm having the same problem - on the same Portege 3500. Did the Trident driver at some time support rotation, and if so, is there any way to roll back to that version?

[Dog (brische)]

Not to be smarmy, but why was this changed to invalid? I realize the current driver apparently doesn't support this, but it would be very helpful to know if this is something that will be addressed in the future or if there is a previous version of the driver that can be used. If this isn't going to be addressed would the maintainer be willing to change the status to 'Won't Fix' so this issue shows up in searches for others? As I understand it the 'Invalid' status means an entry will no longer show up in searches. My apologies if I'm missing the obvious here - no flame intended in anyone's direction on this.

[Timo Aaltonen (tjaalton)]

It was only the 'xorg' component. The driver is still left as 'confirmed'.

[xzero1 (kdogn)]

I also have a Toshiba Protege 3500 tablet running Ubuntu Hardy Heron. Not that it does anything good but by adding the following lines to the screen section,

Option "RandRRotation" "true"
Option "Rotate" "CW"

xorg does seem to manipulate the screen after restarting.

[adamcrume (adamcrume)]

I'm affected by this too, using Ubuntu Intrepid Ibex on a Toshiba Portege 3500. I'd upvote this if we could vote for bugs. (If we can, and I'm just not seeing it, let me know.)

[gorcq (robert-morson)]

I also have this problem on a Toshiba Portege. I'm using Ubuntu 7.10.

[littlematt (10026-elizcoll)]

I have this problem as well on Hardy.

Has anyone found a solution?

[Jim Trigg (jtrigg)]

I am having this problem on Jaunty with a NEC Versa Litepad.

[James Le Cuirot (chewi)]

Gentoo user here. I've just been trying to figure out exactly where this fails to see whether I can do something about it. I'm thinking that if it's already possible to rotate through xorg.conf, making it work through RandR can't be that hard. The request is made in XRRSetScreenConfigAndRate of libXrandr and the BadMatch reply is received here. What I can't figure out is where the request actually gets handled and where that BadMatch reply is actually generated. The request/response mechanism seems to be handled by libX11 but this doesn't have anything to do with the actual operation. It must surely be driver-specific so I've looked at xf86-video-intel and xf86-video-radeonhd and while there is RandR rotation stuff in there, I can't see anything that looks like it's dealing with such a request. I've not really hacked X before. Maybe I'll ask on a mailing list unless you guys have any ideas?

[penalvch (penalvch)]

MikeShoup, thank you for reporting this bug to Ubuntu. Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 162312

Please ensure you have xdiagnose installed, and that you click the Yes button for attaching additional debugging information.

[Launchpad Janitor (janitor)]

[Expired for xorg (Ubuntu) because there has been no activity for 60 days.]