So the HP 
Envy 2 in 1 I have which runs Endeavour OS is one of those Ryzen machines that uses the Sensor Fusion Hub [1022:15e4] to rotate. This sensor fusion hub has been around since the first mobile Ryzen gen and is still used in the Ryzen 5000 mobile machines, mostly convertibles. But it don't rotate.
Setting KDE's tablet mode does nothing, iio-sensor-proxy is installed but will not return anything, monitor-sensor --accel just waits infinitely. Force starting iio with systemctl and checking it shows No sensors or missing kernel drivers for the sensors. Exiting and deactivates. Modprobing pcie_mp2_amd gives FATAL: Module pcie_mp2_amd not found in directory /lib/modules/7.1.8-arch1-3 which is cool. You can also modprobe amd_sfh to no avail.
I found this totally useless archbbs thread full of dead links, and funny enough I was dual booting Windows 10 on this machine, but no amount of rebooting nor disabling Fast Boot in Windows nor entirely reinstalling EndeavourOS fixes this. A live image of Cachy OS behaves the same.
If you know anything about amd_sfh or pcie_mp2_amd I am begging you, just let me rotate my screen automatically. Or y'know, if you wanna write a patch to make it work, together. Totally.
Bugzilla thread about this gamer hardware issue
EDIT: after a bit of research I see that the Linux kernel has been fighting for its life against AMD's shitass SFH driver... For over six years...
My question also. I am choosing to discontinue installing Endeavour and plan to replace it with either normal Arch or CachyOS. I see lots of people gripe that Cachy uses Fish by default but dracut over mkinitcpio is way worse imo.
Uhhh, if that's the default login shell I would call that worse because fish is not a POSIX compliant shell. Like I use fish, its great, but I have my bashrc drop me into fish. Like that's going to be a problem everyday.
Also I heard cachy doesn't use grub or systemd-boot but some weird bootloader called limine. So you might want to check what else they are doing weird in cachy land.
You can choose between all three at install
Limine is their own ✨ special little guy! ✨ but you can use Grub or systemd-boot just fine and I do. I have one Limine test setup and I mean, it's fine, but they say "you can use it on a legacy EFI/BIOS system!" which might be cool as a Grub alternative, and you sure as hell cannot, the install errors out or fails to boot. Epic.
FYI:You can always hit the kernel terminal with Ctrl+Alt+F1-12. One of those is your DE, usually F2 or F7. It depends on the DM. F1 should be the systemd boot log.
Oh yeah, I forgor. So I did that and
it's fish all the way down on Cachy. Heroic.
So, why should I care about POSIX compliance or fish over bash as an end user? I've heard a lot about it but never any reasoning and am legit curious.
POSIX compliant shell means its backwards compatible with
/bin/sh. If you encounter a script from some package that doesn't specify its interpreter with a shebang,#!, it default to your login shell. Usually that script will be forshwhich fish will fail to parse. IIRC fish will actually refuse to execute scripts that don't have a shebang for this reason.Okay, fairly compelling. I guess I'm off to discover how to have bashrc drop me into fish instead of it being default. Ty for the knowledge.
There's different ways to do it but the main thing is you don't want bash to always drop into fish. Or else you could never run bash. You only want it to be fish if its in interactive mode.
Dropping this at the end of the bashrc should work:
But I have
[[ $- != *i* ]] && returnat the top of my bashrc because I don't want any of the other settings processed.