New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Announcements and updates #96
Comments
|
5.5.6 was released! Build systemWe now have a build system for packages for Arch, Debian and Fedora which should make it easier for us to release new kernel versions. The Automated repositoriesWe have set up
As a result of these changes, installation is now as easy as adding the package repository, installing a bunch of packages and following the guide to add any necessary config files for your device. New IPTS driver (pen or single-touch)5.5 patchsets also feature a new IPTS driver which works without the Intel GuC submission APIs that were removed upstream. The caveat is that it supports either pen OR single-touch. If you want to continue using multi-touch, either use the LTS release (4.19) or please manually install the latest 5.3 release. By default pen support is enabled. If you want to switch to single-touch create a file under Note: The new driver works on gen7 (SL3 Intel & SP7) as well! |
mwifiex: power_save now disallowed by default to improve connection stabilityv5.5: fedora-31-5.5.9-3, fedora-30-5.5.9-3, debian-5.5.9-2, arch-5.5.9-2 You may have already noticed, since commit linux-surface/kernel@7182ea0b4b5e9a, power_save is disallowed by default. There have been many reports that configuring powr_save from userspace tools (e.g. via NetworkManager config file or udev rule) is not so solid. Now, no need to configure it manually. If you want to try to allow power_save, pass |
"v4.19: IPTS (touchscreen driver) stops working (SP4 and SB1)" has been hopefully fixedv4.19: debian_lts-4.19.123-1, arch_lts-4.19.123-1 Since commit linux-surface/kernel@8b45a31eb5977d, touch input on all kinds of SP4/SB1 devices should work without crashing. The EDIT: This fix is for "touch input crashing after some use" or "touch input broken when |
|
Noteworthy changes in the v5.7.7 and v4.19.131 releases There have been some changes to the Surface Aggregator Module driver that have now been integrated into the v5.7.7 and 4.19.131 releases (and also the 5.4 patches). More specifically:
|
|
New packaging structure for Debian/Ubuntu packages The packaging approach for Unfortunately, this means that to upgrade the kernels (only this time, after that everything should work normal/as before), you'll have to manually uninstall the current kernel packages ( Additionally, we recommend you manually remove outdated initrd files after the upgrade. These files can be found under Please remove only those that are outdated ending with See also linux-surface/repo#3 for the issue reporting this problem. In addition, we have decided to drop the custom |
|
Noteworthy changes in the v5.7.8 and v4.19.132 releases More Surface Book 3 support has been merged, specifically:
This means, that (apart from the known issues) only support for the detachment daemon is missing, which can be found in an experimental stage in https://github.com/linux-surface/surface-aggregator-module/tree/feature/sb3-v3. Additionally a bug in the dGPU part of the Surface Aggregator Module driver have been fixed, which caused the driver to deadlock when resuming from suspend with a dGPU turned on at boot time via module parameters (#223). More details can be found in the commit messages: b70e5fb (v5.7), 7a41e16 (v5.4), and f866ce0 (v4.19). |
|
Noteworthy changes in the v5.7.8-2 and v4.19.132-2 releases Unfortunately, the previous release introduced a bug, leading to HID devices handled via the SAM module (i.e. keyboard and touchpad) on the Surface Laptop not working any more. This should be fixed with the new releases. If this issue persists with those releases, please let us know at linux-surface/surface-aggregator-module#45. |
|
Noteworthy changes in the v5.7.11-1 and v4.19.135-1 releases The most notable changes are:
More details can, as always, be found in the respective commit messages (e.g. for v5.7). |
|
Changes in v5.8.1 We switched IPTS support from built-in single-touch to our new-ish iptsd daemon. This means, that to get touch support, you'll have to install the The iptsd daemon is still in somewhat early stages, but it should already provide a good replacement for the previous single-touch-only driver. It does support multi-touch (and stylus at the same time), but contact-area/pressure calculation is currently still missing, and things like jitter in contact points may need some improvement. Unfortunately, there have been no changes for Gen7 devices (SL3, SB3, SP7) yet. If you experience any issues, let us know. You can always revert to the previous, single-touch-/stylus-only implementation by installing the old driver from https://github.com/linux-surface/intel-precise-touch/tree/old-driver (see "Building (DKMS)"). |
|
Changes in v5.8.1-3 (Arch non-LTS), v5.8.1-2 (other), v4.19.139-3 (Arch LTS), and v4.19.139-2 (other) In these versions, a new bus and device type has been added for System Aggregator Module (SAM) devices. Due to this, a couple of things have been changed with regards to userspace:
Known issues: On 7th generation devices (SP7/SL3/SB3), there currently is a warning emitted to the kernel log when the charger is connected or disconnected. This can be safely ignored and will be addressed in the next release. This has been fixed in the v5.8.3 and v4.19.141 releases. |
|
Changes in v5.8.5 and v4.19.142
|
|
Changes in v5.8.7 and v4.19.143
|
|
Changes in v5.8.10 (Fedora v5.8.9) and v4.19.146 These releases contains two major changes that may need manual intervention:
Additionally:
Known Issues: There is a bug that may be triggered under certain conditions, preventing the Surface Aggregator Module drivers to load. This will be fixed with the next releases, new kernels with the fix applied are already being built. |
Changes in v5.8.12-2 and v4.19.149-1 regarding mwifiexsuspend (for S0ix and AP scanning fix)
firmware reset feature fix
auto_ds (auto deep sleep)
|
|
Changes in v5.8.14 and v4.19.150 Changes regarding the Surface Aggregator Module
|
|
Changes in v5.8.15 (Arch v5.8.14-2) and v4.19.151 Changes regarding the Surface Aggregator Module:
Additionally a patch has been added to fix a boot issue on the Surface Go series devices. |
|
Changes in v5.9.1, v5.8.16 Changes regarding IPTS:
Changes in v5.9.1, v5.8.16, v4.19.152 In addition to the changes above, there are the following changes have been made:
|
|
Changes in v5.9.3, v5.8.18, and v4.19.154 Changes regarding the discrete GPU (dGPU):
|
|
Changes in v5.9.6, v5.8.18-2, and v4.19.155
|
|
Changes in v5.10
|
|
After a long and exhausting battle against the evil forces of the CI I was finally victorious! Or so... Anyways. iptsd 0.3 was released With this release we ported the iptsd daemon from Go to C, which helps tremendously with resource usage. If you are packaging iptsd or compile it from source, you will have to adjust your build scripts. There are some other notable changes, mostly regarding the behaviour of the stylus. Check out the release notes for more details. |
|
Changes in v5.10.2 (Arch, Debian) and v5.9.16 (Fedora)
|
|
Changes in v5.10.10
|
|
Changes in The |
|
Changes in v4.19.176 and v5.10.16-2
|
|
Changes in v5.10.16-3 and v5.10.17
|
|
Changes in v5.10.21 and v5.11.5
|
|
Changes in v5.11.10 and v4.19.183 Thanks to @jonas2515, this update contains some noticeable WiFi improvements:
Have a look at the following PRs for more infos:
|
|
Changes in v5.14.15
|
|
Changes in v5.14.16
|
|
Changes in v5.14.16-2
|
|
Changes in v5.15.14 and v5.16.1
|
|
Changes in v5.16
Changes in v5.17
Changes in v5.17.5-2
Changes in v5.17.5-3
Changes in v5.17.7
|
|
Changes in v5.17.9
|
|
Changes in v5.17.9-2
|
|
Changes in v5.18.1
|
|
Changes in v5.18.3 and v5.17.14
|
|
Changes in v5.18.4
|
|
Changes in v5.18.7
|
|
Changes in v5.19
|
|
Changes in v6.0.7-2
|
|
Changes in v6.0.8
|
|
Changes in v6.0.8-3
|
|
Changes in v6.0.12
|
|
Changes in v6.0.17 / v6.1.3
|
|
Changes in v6.1.8-2 / v6.1.9
Since the new kernel drivers use a HID based userspace interface, an updated version of iptsd is required! See https://github.com/linux-surface/iptsd/releases/tag/v1.0.0 for the list of changes to iptsd (there are many). If you had previously installed one of the kernel drivers through DKMS or built iptsd from source, please remove it completely before updating. Otherwise the custom-built versions might continue to override the built-in ones. If you are building your own kernels from source, please note that the configuration option for IPTS has changed from |
|
Changes in v6.1.12
|
|
Changes in v6.1.12-2
|
|
Changes in v6.1.12-3 / v6.1.13
|
|
Changes in v6.1.14 / v6.2.2
|
|
Changes in v6.1.15-2 / v6.2.2-2
|
|
Changes in v6.1.18 / v6.2.5
|
|
iptsd 1.2.0 has been released This update to iptsd brings a very significant change: It replaces the old basic / advanced algorithms with a new algorithm that is a combination of both. This new algorithm is more robust towards noise (like the advanced one), while using vastly less resources (like the basic one). If you have calibrated iptsd, you must remove the old calibration, as the values will no longer be accurate. This update also changed the available config options. If you have a custom configuration, please check the values against the reference configuration. For a full list of (user-facing) changes, look here: https://github.com/linux-surface/iptsd/releases/tag/v1.2.0 |
|
Changes in v6.2.12 and v6.2.11 (Fedora)
|
|
Changes in v6.3.6 (Fedora) We have updated our Fedora packages to follow the upstream packages more closely. This fixes some issues with our old package, for example akmods should now work properly. Like the stock kernel, it will also keep around the last 3 However, because the transition between the old and new packages is hitting an edge case in DNF, you MUST temporarily disable the running kernel protection. Otherwise DNF will refuse to remove the old package and install the new one. You can do this by either rebooting into a stock kernel to do the upgrade, or by running the following command: $ sudo dnf update --setopt=protect_running_kernel=False |
|
Changes in v6.5.8
|
|
Changes in v6.6.1/v6.5.11-2
|
|
Changes in v6.6.10 (Arch Linux) / v6.6.11 (Ubuntu/Fedora)
|
Subscribe to this issue to be notified of announcements, changelogs and manual upgrade notices.
(For update announcements only)
The text was updated successfully, but these errors were encountered: