I am running Arch on my AMD Framework. I’ve had the laptop for a couple months now and have not been able to get the touchpad working. If I run ubuntu live from usb the touchpad works.
Those are the biggies. You must be missing something much more fundamental.
Post the full dmesg and kconfig somewhere I can see, I’ll see if anything stands out to me.
This means it can’t access a register properly. Can you please try to reset BIOS default settings (if you haven’t already)?
If that doesn’t help - what bootloader and boot process are you using? Any patches you’ve added to the kernel that could cause this?
Also tangentially related this stands out but isn’t the cause. I don’t know what is setting it, but I’ve never heard of that parameter for the i2c-hid driver.
Might be worth it to check if grabbing a new kernel works and what you modified.
From my experience on Arch though, it’s usually easier to just backup your /home and reinstall. I don’t know anyone with FW AMD on Arch who’s experienced these issues (albeit with a sample size of 2), so it might just be your setup.
Most of that shouldn’t matter. The kernel will only load what’s applicable. From the error above the base address register seems wrong, or something is blocking the read of the register.
From my experience on Arch though, it’s usually easier to just backup your /home and reinstall.
This is true. You can then also check if thing work in the installer and whittle down what causes the breakage. I’m not sure what patches go into making ZFS work in the kernel, but I’d question whether any of those are part of the problem.
I’m going to give that a shot in the next day or two when I can dedicate a few hours to it. (I’ve got a pretty robust dotfiles repo and a set of ansible scripts to setup my system the way I like it now so a reinstall should only take a few hours.)
Thanks for your help!! I’ll report back what I find in case anyone else comes accross this in the future.
Oh, I didn’t notice that this topic is about FW13 AMD, I’m experiencing the issue on a FW16.
I’m thinking that the issue might be caused by some driver non properly tearing down hardware state during kexec.
Today I’ll probably try blacklisting a couple modules in ZBM kernel, I was thinking about either i2c_designware or the whole i2c, maybe @Mario_Limonciello (sorry for the necroping btw ) might have some useful insights.
Sadly that didn’t work out. I also tried booting an UKI with zfs modules built into it and that made the trackpad work correctly.
It’s probably some driver that has bugs in its teardown logic and/or leaves hardware in a borked state.