Maximilian Luz
Maximilian Luz
@floion Quoting from the module description, "It currently only works with the atomisp driver.". Atomisp is a ISP (Image Signal Processor) for the Intel Atom platform. This driver as included...
@floion I'm not sure what you're trying to achieve here. If you want to adapt the ov5693 driver for the Surface/general use, I'd suggest you have a look at the...
Have a look at our community-maintained fork: https://github.com/linux-surface/linux-surface (and the [wiki](https://github.com/linux-surface/linux-surface/wiki/Installation-and-Setup) for install instructions). That does support the Surface Book 3.
Seems a bit like this issue: https://bugzilla.redhat.com/show_bug.cgi?id=1505058 and https://www.spinics.net/lists/linux-wireless/msg168245.html. Andy Shevchenko (a kernel dev) mentions that: > The behaviour is not changed for a while. > The workaround is to...
Hmm that's a bummer, I hoped that this would at least be a workaround. If it really is the firmware, we're screwed. I still want to have a look at...
So I've finally managed to test that myself. Yeah... doesn't work for me either.
> I think I'm actually going to switch to using hibernate. The latest update for the linux-surface kernel (5.8.5) is supposed to fix the keyboard going unresponsive after resuming from...
> Perhaps a regression of this older problem? #310 Might be, any chance https://github.com/jakeday/linux-surface/issues/305#issuecomment-442900609 helps?
@AlexeyPogorelov This seems to be the same underlying issue as https://github.com/qzed/linux-surfacegen5-acpi/issues/19. Can you try a hard-reset and check if it's some kind of EC hangup (unfortunately the communication there does...
@AlexeyPogorelov Sorry for the delay. Can you try the surface-acpi development module (the one you linked above) and get some logs from it? For this you may need to enable...