Stylus and touchscreen on a Fujitsu Lifebook T4215

dino · 2024-09-24 21:33:58

hello! i'm kinda new on arch linux and even newer on arch linux 32, so be a bit patient with me. i have managed to install arch linux 32 on a fujitsu lifebook t4215, which comes with a touchscreen and a stylus that have worked fine on windows.

however, now the laptop can't seem to detect these devices. here's the xinput output:

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad              	id=14	[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)]
    ↳ Video Bus                               	id=8	[slave  keyboard (3)]
    ↳ Power Button                            	id=10	[slave  keyboard (3)]
    ↳ Sleep Button                            	id=11	[slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard            	id=13	[slave  keyboard (3)]
    ↳ Fujitsu FUJ02BF                         	id=9	[slave  keyboard (3)]
    ↳ Fujitsu FUJ02E3                         	id=7	[slave  keyboard (3)]
    ↳ Fujitsu Application Panel buttons       	id=12	[slave  keyboard (3)]

i tried building the input-wacom kernel drivers from https://linuxwacom.github.io/, but that didn't work either and might not have been a good idea.

i don't know what my next step should be, so does anyone here have any idea on what i could do?

abaumann · 2024-09-25 06:51:55

Sadly "working on Windows" is not enough, they must have explicit support for Linux. Sometimes things also
just work on a specific OEM-version of exactly that Windows and also if you update Windows you lack the drivers.

Can you also post the output of an 'lspci' and an 'lsusb' here, this might provide some more information..

dino · 2024-09-25 09:39:20

here's lspci:

00:00.0 Host bridge: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub (rev 03)
00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03)
00:02.1 Display controller: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller (rev 03)
00:1b.0 Audio device: Intel Corporation NM10/ICH7 Family High Definition Audio Controller (rev 02)
00:1c.0 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 1 (rev 02)
00:1c.1 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 2 (rev 02)
00:1c.2 PCI bridge: Intel Corporation NM10/ICH7 Family PCI Express Port 3 (rev 02)
00:1d.0 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #1 (rev 02)
00:1d.1 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #2 (rev 02)
00:1d.2 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #3 (rev 02)
00:1d.3 USB controller: Intel Corporation NM10/ICH7 Family USB UHCI Controller #4 (rev 02)
00:1d.7 USB controller: Intel Corporation NM10/ICH7 Family USB2 EHCI Controller (rev 02)
00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)
00:1f.0 ISA bridge: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge (rev 02)
00:1f.1 IDE interface: Intel Corporation 82801G (ICH7 Family) IDE Controller (rev 02)
00:1f.2 SATA controller: Intel Corporation 82801GBM/GHM (ICH7-M Family) SATA Controller [AHCI mode] (rev 02)
00:1f.3 SMBus: Intel Corporation NM10/ICH7 Family SMBus Controller (rev 02)
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12)
05:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG [Golan] Network Connection (rev 02)
08:03.0 CardBus bridge: O2 Micro, Inc. OZ711MP1/MS1 MemoryCardBus Controller (rev 20)
08:03.1 CardBus bridge: O2 Micro, Inc. OZ711MP1/MS1 MemoryCardBus Controller (rev 20)
08:03.2 SD Host controller: O2 Micro, Inc. Integrated MMC/SD Controller
08:03.3 Bridge: O2 Micro, Inc. Integrated MS/xD Controller

and lsusb:

Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 1199:6802 Sierra Wireless, Inc. MC8755 Device
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor
Bus 004 Device 002: ID 0c24:000f Taiyo Yuden Bluetooth Device (V2.0+EDR)
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

no trace of the stylus or the screen. on the slightly-positive side, i don't think the thing is OEM-specific since i've changed windows versions before and all i had to do was download the windows drivers from https://support.ts.fujitsu.com/IndexDownload.asp. i don't think there's any way of using those drivers in arch, right?

abaumann · 2024-09-25 16:22:12

zgrep FUJITSU /proc/config.gz
CONFIG_NET_VENDOR_FUJITSU=y
CONFIG_FUJITSU_ES=m
CONFIG_TOUCHSCREEN_FUJITSU=m
CONFIG_FUJITSU_LAPTOP=m
CONFIG_FUJITSU_TABLET=m

Maybe just those modules are not enabled on Arch32. This means we have to rebuild kernels with those modules enabled.
Can you check, what you get on your machine with the 'zgrep' statement above?

I see they are present in our build configs:

config.i486:CONFIG_NET_VENDOR_FUJITSU=y
config.i486:CONFIG_FUJITSU_ES=m
config.i486:CONFIG_TOUCHSCREEN_FUJITSU=m
config.i486:CONFIG_FUJITSU_LAPTOP=m
config.i486:CONFIG_FUJITSU_TABLET=m
config.i686:CONFIG_NET_VENDOR_FUJITSU=y
config.i686:CONFIG_FUJITSU_ES=m
config.i686:CONFIG_TOUCHSCREEN_FUJITSU=m
config.i686:CONFIG_FUJITSU_LAPTOP=m
config.i686:CONFIG_FUJITSU_TABLET=m
config.pentium4:CONFIG_NET_VENDOR_FUJITSU=y
config.pentium4:CONFIG_FUJITSU_ES=m
config.pentium4:CONFIG_TOUCHSCREEN_FUJITSU=m
config.pentium4:CONFIG_FUJITSU_LAPTOP=m
config.pentium4:CONFIG_FUJITSU_TABLET=m

Can you check if something changes if you modprobe one of the modules below:

/lib/modules/5.15.167-1-lts515/kernel/drivers/input/touchscreen/fujitsu_ts.ko.zst
/lib/modules/5.15.167-1-lts515/kernel/drivers/platform/x86/fujitsu-tablet.ko.zst
/lib/modules/5.15.167-1-lts515/kernel/drivers/platform/x86/fujitsu-laptop.ko.zst

Though, they should have been detected and loaded automatically.

dino · 2024-09-25 20:58:43

ok! this is all pretty encouraging. my zgrep output is the same as yours but when i checked those modules i found i was missing the whole 5.15.167-1-lts515 directory, so i installed linux-lts through pacman and got the modules.

is running "pacman -S linux-lts" enough or does it need more work? i'm not sure at all how things work at this level

i runned modprobe for the modules and the 2nd and 3rd ones seemed to work but not fujitsu_ts, it threw this error:

modprobe: ERROR: could not insert 'fujitsu_ts': Exec format error

am i supposed to just run "modprobe module"?

Last edited by dino (2024-09-25 20:59:40)

abaumann · 2024-09-26 06:18:44

'modprobe module' or 'insmod /lib/modules/5.15.167-1-lts515/kernel/drivers/input/touchscreen/fujitsu_ts.ko.zst' or so.

modprobe handles dependencies between modules automatically, insmod just inserts the module and expects you
to check and load dependencies before, otherwise it fails.

What is 'dmesg' (the kernel log) telling you

dino · 2024-09-26 14:14:44

i did modprobe and didn´t obtain any result. here's my dmesg output https://pastebin.com/Rv5RsUpL. i couldn't make much of it.

i'm confused whether or not i should use linux-lts. the same modules seem to be available in the /lib/modules/6.10.10-arch1-1.0/ directory. does it make any difference?

abaumann · 2024-09-26 15:19:22

Looks promising:

...
[ 8.315734] input: Fujitsu FUJ02E3 as /devices/LNXSYSTM:00/LNXSYBUS:00/FUJ02E3:00/input/input11
...
[ 7.996783] input: Fujitsu FUJ02BF as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:05/FUJ02BF:00/input/input10
...

Probably there is no big difference between the modules in LTS or stick Linux kernels.

I think, everything is ok from the kernels point of view, it's a matter to configure the input devices in /etc/X11/xorg.conf or so.

So, the point to check here is '/var/log/Xorg.0.log', there you should see messages about libinput seing your Fujitsu devices.

dino · 2024-09-26 16:04:03

here's Xorg.0.log: https://pastebin.com/cQ7XHXNQ

like xinput says, FUJ02E3 and FUJ02BF seem to be recognized as a keyboard and a keyboard switch:

...
[    12.451] (II) event7  - Fujitsu FUJ02E3: is tagged by udev as: Keyboard
...
[    12.538] (II) event6  - Fujitsu FUJ02BF: is tagged by udev as: Keyboard Switch
...

i don't know what these devices are. is it possible that they represent the touchscreen but are incorrectly recognized?

abaumann · 2024-09-26 19:09:25

You could try to use 'xinput test <id>' to see. if you get events from the devices.. But for this Xorg has to be up and running and you need a terminal..
Mmh..

https://bbs.archlinux.org/viewtopic.php?id=78072

There seems to have been discussions in the past, how to get things to work..

dino · 2024-09-26 22:09:39

no result from "xinput test". it seems like back in 2009 people used the linuxwacom package and everything would work almost out of the box. also for some reason, the wiki page on tablet pcs still say to use "wacdump" to troubleshoot this though that command is part of linuxwacom i think? i really dont know

abaumann · 2024-09-27 06:27:32

This starts to get complicated. One option is to use older kernels (like linux-lts515) from the AUR, till things change. That is, if the Fujitsu code
in the kernel has bit-rotten.

dino · 2024-09-28 12:02:33

i learned that these devices are managed through serial though i have no idea how that works. i saw that the xorg.conf file from that old discussion connects the device from /dev/ttyS0 and used the setserial package

in my computer, however, the /dev/ttyS0 serial returned an I/O error and i can't find anyway to install the setserial package on this architecture. i can't even find old versions of the package or smth.

now, i noticed on my dmesg that the /dev/ttyS0 serial wasn't being initiated or something but the ttyS4 was, so i checked that one with 'dterm /dev/ttyS4' and i got a reaction from the stylus! first sign of life. the serial was getting information everytime i put the stylus on the screen.

i changed /dev/ttyS0 to /dev/ttyS4 on the xorg conf files but that didnt work either. checking the xorg logs, i got an error like "can not ioctl version" for the three devices "stylus", "cursor" and "eraser". idk what that is. idk what im doing. im making a backup of my system and reinstalling arch rn to see if that fixes something

abaumann · 2024-09-28 21:10:39

There is an AUR package of setserial: https://aur.archlinux.org/packages/setserial (I had to fix it, patch is mentioned in the AUR comments).

There should also be a modern alternalive to setserial, but it currently just slips my mind.

dino · 2024-09-29 00:17:43

thanks! i could install it but following the instructions from old threads and wikis isnt working. its helped me realize that the touchscreen is connected to serial port 0x0220 but thats pretty much all I've managed to do. couldnt get anything working yet.

ive come across inputattach which comes with some touchscreen presets and responds to the stylus which seemed promising but none of the presets seem to match this touchscreen. not even the fujitsu one

i tried installing linux-lts but ran into some problems. ill try again tomorrow

thank you so much for all your help btw

dino · 2024-09-30 14:43:19

ok great development. reading through the readme file of inputattach was the exact solution i needed apparently (https://sourceforge.net/projects/linuxconsole/files/). it describes attaching a wacom touchscreen through udev rules and it specifically gives the example of a wacom w8001 on a fujitsu computer, specifically the device with the id FUJ02e5, which i should have said from the start, was the id windows gave to the touchscreen.

it specified the profile and baud rate (w8001 at 19200 bauds) to use and i tried that and it works perfectly:

inputattach --baud 19200 -w8001 /dev/ttyS4

the pen is working great, buttons and all. even the eraser. now i need to figure out the udev rules or another way to make it attach on boot. thank you so much andreas!

abaumann · 2024-09-30 14:58:59

Oh, no problem. Glad you made it work. :-)

dino · 2024-09-30 15:00:38

i've kinda bricked arch trying to setup the udev rules and i can't be bothered to try anymore. i've been at this for a week so i'm gonna restore my drive backup and add the inputattach line to my i3 config file and call it a day. i'm so happy

Arch Linux

#1 2024-09-24 21:33:58

Stylus and touchscreen on a Fujitsu Lifebook T4215

#2 2024-09-25 06:51:55

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#3 2024-09-25 09:39:20

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#4 2024-09-25 16:22:12

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#5 2024-09-25 20:58:43

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#6 2024-09-26 06:18:44

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#7 2024-09-26 14:14:44

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#8 2024-09-26 15:19:22

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#9 2024-09-26 16:04:03

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#10 2024-09-26 19:09:25

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#11 2024-09-26 22:09:39

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#12 2024-09-27 06:27:32

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#13 2024-09-28 12:02:33

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#14 2024-09-28 21:10:39

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#15 2024-09-29 00:17:43

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#16 2024-09-30 14:43:19

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#17 2024-09-30 14:58:59

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

#18 2024-09-30 15:00:38

Re: Stylus and touchscreen on a Fujitsu Lifebook T4215

Board footer