RPL: Touchpad doesn't work

[bdaisley]

Trying to install Windows 10 on a addw3 model laptop but running into issues with the trackpad not working.

Background:

• Initially was having issues with BSOD when attempting to usb boot Windows 10
• Updated to the latest open firmware (2023-05-17) and then Windows 10 install went smoothly
• After install, touchpad and wifi were not working
• The wifi issue was fixed by installing the recommended drivers for addw3 described here: #17

• Touchpad remains an issue, with 2 yellow bangs in the Device Manager that I believe are relevant

  • I2C HID Device (Code 51: The device is currently waiting on another device or set of devices to start)
  • GPIO controller (Code 12: The device cannot find enough free resources that it can use)

I have tried all reasonable attempts to fix the GPIO controller based on what I could find through extensive google searching, but with no success.

Any direction others could offer at this point would be great!

[leviport]

Make sure the SerialIO and chipset drivers are installed. Probably worth reinstalling them, just to be certain. Also, make sure Windows updates are run. These drivers should only cover what Windows can't automatically install by itself.

[bdaisley]

@leviport I can confirm the Serial IO and Chipset drivers are installed. I tried uninstalling and reinstalling them, and in different orders (Serial IO > Chipset, Chipset > Serial IO), but no success.

Windows updates do no solve the issue either. I even attempted to update to Windows 11 but the issue remained. A fresh install of Windows 10 via USB installer led to the same situation with the I2C HID and GPIO controller issues + no touchpad function.

[leviport]

Do you have a 15" or a 17" addw3? They have different trackpads, so maybe they need different drivers.

[bdaisley]

@leviport It is a 17” addw3 model!

[leviport]

Gotcha, I'll begin testing on my 17" model to see if that's what's going on.

[leviport]

Well I can't get the touchpad on the 15" or the 17" working with our Windows drivers. Hopefully @jackpot51 can take a look when he's back from vacation. I bet there's another driver somewhere that we need to add. Thanks for the report!

[bdaisley]

@leviport Thanks for checking this out. Under hardware ID dropdown menu for the I2C HID Device I found "ACPI/VEN_ELAN&DEV_0412". I downloaded and tried all the Elan touchpad drivers I could find, as well as Synaptics/ALPS drivers, but none worked. Seems like a firmware issue. I will wait for a response from @jackpot51

[dfoxfranke]

Hoping for an update on this or #22 soon (I'd really like my new serw13's touchpad to work properly). The GPIO driver gives a problem status of "C0000018 {Conflicting Address Range} The specified address range conflicts with the address space", which sounds to me like it's trying to map some device memory that the firmware doesn't think is valid. But, if I look at the "Resources" tab, the five memory ranges it gives:

00000000E06E0000 - 00000000E06EFFFF
00000000E06D0000 - 00000000E06DFFFF
00000000E06B0000 - 00000000E06BFFFF
00000000E06A0000 - 00000000E06AFFFF
00000000E0690000 - 00000000E069FFFF

…look like a correct match for what you get from https://github.com/system76/coreboot/blob/system76/src/soc/intel/alderlake/acpi/gpio.asl using the port IDs defined in https://github.com/system76/coreboot/blob/system76/src/soc/intel/alderlake/include/soc/pcr_ids.h and the PCR base address defined in https://github.com/system76/coreboot/blob/system76/src/soc/intel/alderlake/Kconfig#L286. So the firmware problem isn't obvious to me.

[calmitchell617]

Would like to mention that I'm having similar troubles for darp9, on Windows 11, and opened #24.

I followed very similar steps to @bdaisley and his addw3.

Unsure if it should be a separate issue.

[dougkeester]

Hi. I just wanted to chime in with my experience also. I just purchased a 17 inch addw3 at the end of July (order 161452). I am dual booting Pop!_OS with Windows 11 Pro on the second hard drive. The most I have been able to get out of the touchpad is basic PS/2 Mouse functionality. I can point and click, but cannot use gestures (i.e. I can't two-finger scroll). For now I will be using a USB mouse, but I would really like to get full use of the touchpad. Thanks!

[Raikiri]

I have the same exact problem on bonobo 15.

Wanted to add that the problem is not just missing gestures, the trackpad has a really gimped precision in windows: even in the most sensitive mode it seems to have a huge deadzone for tiny cursor movements that makes it very hard to hit any UI elements unless you land your cursor precisely on your first try. If you stop the cursor next to a button, shifting the pointer slightly is going to be a challenge because of the deadzone. It's a strange problem that makes the trackpad unusable for me and it's definitely a software thing, because in popos the trackpad works fine : precision is good + gestures, it's specifically a windows thing.

Reproduces both with windows 10 and windows 11. Should we be making issues for different models or are these the same issue?

[crawfxrd]

Verified touchpad+gestures works on galp6 (ADL), and doesn't work on galp7 (RPL) on b9622a6.

SerialIO driver for MR2 (WW26-2023) is the same version as in MR1 (WW15-2023).

I did notice the GPIO Controller has the wrong ACPI DID (CB:77150), but I don't think that affects it (should use the I2C device).

[Raikiri]

any updates on this? workarounds? is it viable to use the unreleased firmware?

[crawfxrd]

Several GPIO configurations work on Linux, but Windows always reports the device not attached. I'm not sure what's wrong.

[tecguru]

Also having the same issue on the bonw15 and darp9, after installing all the drivers still no trackpad.

[tecguru]

Hoping there is a resolution for this soon. In order to meet my 30 day return window I need to make a decision by next Thursday Aug 31st on if I am keeping these two laptops. I hate to send them back over a track-pad, but they are unless to us without it.

[jackpot51]

I believe this will be fixed by https://github.com/system76/coreboot/pull/194

[leviport]

Probably want to keep this open to track individual releases:

• [ ] bonw15
• [ ] addw3
• [ ] serw13

I'll also investigating whether other RPL models are affected.

[tecguru]

I believe this will be fixed by system76/coreboot#194

This is great news. Does this mean that I will need to boot into PopOS and do a firmware update?

[leviport]

Once it is released, yes.

[tecguru]

Is there a way to get a notification when it is released?

[Raikiri]

I'd like to know an ETA if possible. Is it days/weeks/months/years from now?

[leviport]

The reason I made a checklist in https://github.com/system76/windows-drivers/issues/21#issuecomment-1690569490 is so that we could check the boxes off as they get released. I can post a comment each time one is released, if that is easier for you. Each firmware release needs to undergo extensive regression testing. All three of them will probably be done within a few weeks. I can parallelize them to some degree, but they won't all be released simultaneously.

years

I understand this is frustrating, but c'mon...

[Raikiri]

c'mon

When I encountered the issue I found this one that seemed related https://github.com/system76/windows-drivers/issues/12 and it was created almost a year ago. Your support page explicitly says that windows functionality is not guaranteed and the support person also said they couldn't give me any promises whether it's going to be fixed or not. Also bonw15 came with firmware from 2022 (I think?), so I literally have no clue what to expect.

[jackpot51]

The specific issue that was fixed is only on the three systems @leviport mentioned: addw3, bonw15, and serw13. A BIOS resource was not reserved for the memory range that the GPIO driver uses, this fixes only RPL-HX systems, and only Windows needed this. If there are issues with touchpads on other systems on Windows, it would have a different root cause, including the darp9 and lemp12. As such, we will keep this issue open for RPL-U/P/H systems.

The bonw15 production firmware was built and released on 2023-07-10. I have prepared new firmware for all three systems, and expect us to release them within about two weeks.

[dfoxfranke]

Since I'm in the same boat facing a return deadline, and since I happen to have flash programmer with which I can unbrick myself if necessary, today I'll cherry-pick the patch, apply it against the git revision of my currently-installed firmware, and build and flash it. If it works I'll post a (unofficial, obviously) HOWTO.

[leviport]

master of the firmware-open repo has the fix, so cherry-picking isn't necessary. Just make sure all the submodules are up to date, since the fix was in Coreboot.

[dfoxfranke]

I know, but I'm going to cherry-pick so that I get just that one patch to what I'm currently running and don't get my results muddled by any possible regressions in other unreleased changes.

[leviport]

Ah I see. Well the update we'll be releasing was built from master. If you're worried, I'll have it flashed on all 3 units in just a few hours. That won't catch all possible regressions, but it's at least a smoke test.

[dfoxfranke]

Anything that doesn't cause literal smoke I can recover from, so no real worry there. I'm busy for the next few hours so if you get to it ahead of me and tell me what revision is a release candidate then I'll use that.

[jackpot51]

Current firmware-open master is the one built for release. I have tested it on my bonw15.

[dfoxfranke]

Thanks. Noting for anyone coming back to this thread later that current is 81731199f23b716adc0b25001b583e98689c96d3.

[jackpot51]

For anyone following along, make sure to run ./scripts/update.sh to update all submodules after checking out that commit.

[leviport]

My addw3 and serw13 have been flashed and successfully booted without any smoke.

[dfoxfranke]

I've been trying to build the firmware using WSL but for some reason the existing firmware doesn't think the boot.efi that gets built for doing the flashing is a valid EFI app and it won't run it. Going to try this again from a PopOS boot stick.

[dfoxfranke]

Okay, a few unspeakable hacks later I now have a working touchpad. The flashing was difficult for me because I already completely blew away my PopOS system; I was able to build the firmware under WSL but then I couldn't figure out how to boot the flashing utility after any amount of fussing with bcdedit or manually frobbing EFI variables. Trying to do everything from a PopOS live system, even with 64GB of RAM, got me OOM-killed while building dependencies. But I was able to take the image I built under WSL and then boot into a PopOS live system just to run efibootmgr.

Anyway, I'm not going to recommend this approach to anybody else. Instead, if you still PopOS installed, you should be able to just do this (replace all instances of serw13 with your correct model):

git clone https://github.com/system76/firmware-open --recurse-submodules
cd firmware-open
./scripts/update.sh
./scripts/deps.sh
source  ~/.cargo/env
./scripts/build.sh serw13
./scripts/flash.sh serw13

If you don't still have PopOS installed, then rather than endure the pain that I just did, I recommend you just take my word for it that the fix works and wait for an official release, and then boot a PopOS live system to flash it.

[calmitchell617]

The specific issue that was fixed is only on the three systems @leviport mentioned: addw3, bonw15, and serw13. A BIOS resource was not reserved for the memory range that the GPIO driver uses, this fixes only RPL-HX systems, and only Windows needed this. If there are issues with touchpads on other systems on Windows, it would have a different root cause, including the darp9 and lemp12. As such, we will keep this issue open for RPL-U/P/H systems.

The bonw15 production firmware was built and released on 2023-07-10. I have prepared new firmware for all three systems, and expect us to release them within about two weeks.

Hi @jackpot51

Sorry for a noob-ish question. Just to confirm, you believe that the upcoming release of bonw15, which should happen soon, will fix the windows trackpad issue on my darp9?

I decided not to return my darp9 at the return window because I believe you guys will eventually come through. Plus, it's not that big of a deal to use a mouse until then.

[leviport]

I'm still not certain it's a firmware thing for darp9. At one point, I had a working trackpad on darp9 after installing the available drivers, letting Windows auto update for a couple hours, then rebooting. But after a couple more reboots, it stopped working again. I can't prioritize Windows testing at this moment, unfortunately, so I'll have to look into it some other time.

[Raikiri]

Umm.. a month later, is there any news? Unsurprisingly, the problem still has not resolved itself.

[vweaver]

I'm having similar issues with a new Lemur Pro under Win10.

Touchpad is nonfunctional until I put the computer in sleep mode, then wake it up. After doing that, I get basic functionality (no guestures).

Firmware and Windows are fully updated, and latest drivers installed.

[leviport]

@Raikiri for RPL-HX there is a firmware component. The fix has been made in https://github.com/system76/firmware-open but a release has not been approved yet. QA testing firmware releases is a slow process, and we have limited bandwidth. Sorry for the delay, but we will have the update completed as soon as we can.

[rylativity]

I just received my bonobo (bonw15) three days ago and it did not have trackpad, wireless, or Ethernet support.

Wireless works if I install the drivers after install, but trackpad still doesn’t work after driver install. And the wireless issue means that I cannot install windows 11 (since it requires internet during install).

Is there a solution for this issue on bonw15 yet? And if not, what’s the ETA?

[rylativity]

Update on the above - using Ventoy instead of a regular bootable usb let me bypass the Windows 11 internet requirement on install. And similar to @vweaver, the trackpad starts working once the computer has been put into sleep mode and woken up.

[liam-clink]

Just wanted to chime in again, I got a serw13 a week ago, and I'm having the same sort of touchpad issues, where it intermittently won't work, sometimes sleep/wake cycle helps it work, but it only has basic PS/2 functionality of moving and clicking. It's not seen as a precision touchpad by Windows, and there's no multitouch capability. Since I got it so recently, it should have the most recent firmware installed, just that this isn't officially patched yet.

[liam-clink]

Chiming in again, I was using the 2023-05-17_9560b2e firmware when my trackpad wasn't working. I got Pop_OS! installed again, updated the firmware, and now the trackpad works in Windows 10 (serw13 machine), the version I just installed is 2023-09-19_16ef69c. I did not need to reinstall drivers or anything on windows, after the firmware update on Pop_OS!, it works flawlessly on Windows with no other action taken.

[aarnold89]

Adding in here: I just installed Windows 11 on my lemp12 over the weekend and have not been able to get the trackpad to work. I'm on the most updated versions of everything on the Pop and Windows sides. Trackpad has no functionality at all.

[ahoneybun]

@aarnold89 and others please include what firmware version and what version of the Intel SerialIO and Chipset driver you have installed.

[DiZeroX]

@ahoneybun Sleep/wake does not make touchpad work for me.

model: darp9 Firmware: 2024-01-18_3e19b73 Intel SerialIO and Chipset from this repo OS: Windows 11 (Windows Update ran)

[DiZeroX]

@jackpot51 Tagging since you are still assigned to this issue. I want to bring some more visibility here.

[leviport]

This might have helped: https://github.com/system76/ec/pull/464