Magick Rotation for Fujitsu tablet PC's.

**omskates** · July 8th, 2012

Favux,
Really great to see you still involved in assisting with installation issues for Fujitsu tablet PCs. Thankyou!

**Favux** · July 8th, 2012

Hi omskates,

Good to hear from you again. It's been a while, hasn't it?

Yes, I was very excited when, thanks to Robert, Magick Rotation was now able to support Fujitsu tablet PC's.

**purple_goat** · August 3rd, 2012

Favux, thanks a million for this.

Wanted to report it's working with Lubuntu 12.04, but only on the 2nd install.

I installed, added the Fujitsu folder, nothing. Checked /etc/udev/ and there was nothing, uninstall, reinstalled, works great and the proper files are all there.

This is with the Fujitsu Lifebook T4220.

**hondoslack** · August 15th, 2012

I have an issue regarding calibration on a Toshiba P1630. I'm running 12.10 (quantal quetzal). Installation ran well, and rotate works perfectly. I installed "Calibrate Touchscreen", ran the utility, and copied the values to /usr/share/X11/xorg.conf.d/10-evdev.conf. After a reboot, Landscape touch input worked perfect (it was not OOB). However, after rotating the screen, touch input did not work under Portrait, and rotating back to Landscape it was also screwed up. Any suggestions? Thanks!

**Favux** · August 15th, 2012

Hi hondoslack,

I gather the Toshiba P1630 does not have a Wacom digitizer and touchscreen. Is that correct?

Let's see what it has. Please post the output of the following terminal commands:

Code:

lsusb

and

Code:

xinput list

I think you've run into a bug in xrotate.py for the CTM method used for evdev rotation. Apparently this also has been affecting the N-Trig digitizers. I have what I think is an initial fix on the N-Trig HOW TO but unfortunately no tester as yet. How would you like the honors?

See the top two posts on the last page of the N-Trig thread: http://ubuntuforums.org/showthread.p...52492&page=164 The xrotate.py in the second post is the one I'd like you to test. If you do also let me know what video chipset you have:

Code:

lspci | grep VGA

and whether you run the proprietary driver (if available) for it.

Then if you happen to hook up to a second monitor great! Let me know what happens then. I think I need to reindex a for loop for the second monitor case but I need a tester.

**hondoslack** · August 20th, 2012

Sorry for not getting back sooner, I'll get these results back for you tomorrow, too late for tonight. Thanks!

**hondoslack** · August 20th, 2012

Originally Posted by Favux

Hi hondoslack,

I gather the Toshiba P1630 does not have a Wacom digitizer and touchscreen. Is that correct?

Let's see what it has. Please post the output of the following terminal commands:

Code:

lsusb

Code:

Bus 002 Device 003: ID 03ee:7320 Mitsumi 
Bus 006 Device 002: ID 08ff:2550 AuthenTec, Inc. AES2550 Fingerprint Sensor
Bus 007 Device 002: ID 0c24:0021 Taiyo Yuden Bluetooth Device
Bus 008 Device 002: ID 0430:0530 Sun Microsystems, Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

and

Code:

xinput list

Code:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Fujitsu Component USB Touch Panel       	id=12	[slave  pointer  (2)]
⎜   ↳ PS/2 Generic Mouse                      	id=15	[slave  pointer  (2)]
⎣ Virtual core keyboard                   	id=3	[master keyboard (2)]
    ↳ Virtual core XTEST keyboard             	id=5	[slave  keyboard (3)]
    ↳ Power Button                            	id=6	[slave  keyboard (3)]
    ↳ Fujitsu FUJ02E3                         	id=7	[slave  keyboard (3)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Fujitsu FUJ02B1                         	id=9	[slave  keyboard (3)]
    ↳ Fujitsu FUJ02BF                         	id=10	[slave  keyboard (3)]
    ↳ Power Button                            	id=11	[slave  keyboard (3)]
    ↳ USB Camera                              	id=13	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=14	[slave  keyboard (3)]

I think you've run into a bug in xrotate.py for the CTM method used for evdev rotation. Apparently this also has been affecting the N-Trig digitizers. I have what I think is an initial fix on the N-Trig HOW TO but unfortunately no tester as yet. How would you like the honors?

I'll see what I can do.

See the top two posts on the last page of the N-Trig thread: http://ubuntuforums.org/showthread.p...52492&page=164 The xrotate.py in the second post is the one I'd like you to test. If you do also let me know what video chipset you have:

Code:

lspci | grep VGA

and whether you run the proprietary driver (if available) for it.

Then if you happen to hook up to a second monitor great! Let me know what happens then. I think I need to reindex a for loop for the second monitor case but I need a tester.