This is not a bug, but expected behavior. More of a feature / advice request.
Tablet mode won’t work on Drallion360 because:
1: drallion_ish.bin referenced in devicetree is not in stock firmware or full uefi rom layout, per cbfstool
2: I found a firmware blob located in the Chrome Recovery Image at lib/firmware/intel/drallion_ish.bin so apparently ChromeOS loads it at runtime.
Elly helped me identify the two points above.
So, I’m wondering whether we can include the blob in Coreboot, or if loading at runtime is the only way it’d work.
Also, I’m not familiar with how to load a firmware at runtime in Linux to test, if anyone has any ideas. (Windows would never allow this, AFAIK).
@isi95010@toil to load the firmware you got from the Chrome recovery image simply copy the drallion_ish.bin to the same location on your GNU/Linux installation and reboot.
In this case /lib/firmware/drallion_ish.bin.
Arcada owner here, tablet mode works after doing so. I recommend getting the wacom firmware as well, writing works better on my Arcada using the firmware from the image. In my image it was in /opt/google/touch symlinked to /lib/firmware/. I replicated that on my system.
Are you using Gentoo on your Arcada? I prefer Fedora, and it seems there’s no module that supports the Drallion ISH firmware. The firmware loads and detects changes when flipping the lid, however.
I’m using arch, it shouldn’t make a difference anyway. The firmware modules are called intel-ish* and they’re in the main linux kernel. You’ll see ish-loader loading the bin file on dmesg.
If it detects the flipping the lid then the sensor is working, your desktop environment just doesn’t have preprogrammed actions for it. You’ll need to configure it yourself.
I’m using only a Wayland compositor, niri. It has a convenient configuration switch for the tablet mode sensor. I’m using it to call these when I flip the screen:
I’ve also bound the touchscreen and wacom digitizer to the main screen in the compositor configuration so they rotate together. They’re separate inputs as far as libinput is concerned.
The distribution or desktop environment you’re using doesn’t matter, these are features of the display server (X or Wayland). You can safely follow instructions from other distributions.
If all else fails and your desktop environment doesn’t provide a convenience function to act on the lid flip then you can still use ACPId to launch actions yourself though if you can see that the switch is detected it seems like the DE supports it.