This bug is awaiting verification that the linux-mtk/5.15.0-1030.34
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy-linux-mtk' to 'verification-done-jammy-
linux-mtk'. If the
No worries, your report and testing so far has been an immense help, so
thank you for that!
https://git.kernel.org/linus/07eab0901ede ("efi/x86: Remove
EfiMemoryMappedIO from E820 map") is essentially the same as the test
patch from comment #62, and it appeared in v6.2-rc1, so just wait for a
Hello, since I do not like the idea of maintaining quirks neither, I
could help you, but the problem is I'm very busy lately - if you could
describe (or provide link to) more detailed howto, I would test it. I
just cannot spend extra time figuring-out the details... I've become
more of a "just
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product
This bug is awaiting verification that the linux-
gkeop-5.15/5.15.0-1003.5~20.04.2 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-nvidia/5.15.0-1007.7
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-nvidia/5.15.0-1006.6
kernel in -proposed solves the problem. Please test the kernel and
update this bug with the results. If the problem is solved, change the
tag 'verification-needed-jammy' to 'verification-done-jammy'. If the
problem still exists,
This bug is awaiting verification that the linux-
hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the problem
This bug is awaiting verification that the linux-lowlatency-
hwe-5.15/5.15.0-48.54~20.04.1 kernel in -proposed solves the problem.
Please test the kernel and update this bug with the results. If the
problem is solved, change the tag 'verification-needed-focal' to
'verification-done-focal'. If the
It's booting fine indeed with the regular Ubuntu kernel
(5.15.0-47-generic here) but I have many error messages like:
[0.802115] kernel: ACPI: button: Sleep Button [SLPB]
[0.802196] kernel: ACPI BIOS Error (bug): Could not resolve symbol
[\_SB.PR00._CPC], AE_NOT_FOUND
I am confirming *no more need* of `pci=nocrs` after latest update.
debug info:
```
$ uname -a
Linux SPIN5 5.19.0-76051900-generic #202207312230~1660780566~22.04~9d60db1 SMP
PREEMPT_DYNAMIC Thu A x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID: Pop
This bug was fixed in the package linux - 5.15.0-47.51
---
linux (5.15.0-47.51) jammy; urgency=medium
* jammy/linux: 5.15.0-47.51 -proposed tracker (LP: #1983903)
* Jammy update: v5.15.46 upstream stable release (LP: #1981864)
- UBUNTU: [Packaging] Move python3-dev to
Well, @acelankao, I am the one who created this bugreport originally, so
my platform is certaily affected and I had already posted any info
needed.
As @bjorn-helgaas writes, it seems to be fixed in 5.19, I just got
confused by #48 and #49 stating it works in 5.15, but I missed the part
with
crysman,
The patch lists the affected platforms that have been reported with the
issue. If the test kernel doesn't work for you(but pci=nocrs works),
please post the output of 'sudo dmidecode --type 1' here, so that we can
add the affected platform to the list.
--
You received this bug
I don't know what's in the 5.18.10-76051810-generic kernel (I assume that's
v5.18 + some Ubuntu patches). The upstream fixes for this went into v5.19:
https://git.kernel.org/linus/3cc30140dbe2
I think v5.18 + the following patches (which somebody added in the "Bug
Description" at the very
Still does not work without pci=nocrs on 22.04 (jammy), up-to-date
5.18.10-76051810-generic - what does it mean? It had been working on
5.15 generic and on 5.18 not any more?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
** Changed in: linux (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Jammy)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Description changed:
+ [Impact]
+ E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
+
+ [Fix]
+ It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
+
+
I can confirm that with your 5.15.0-1043-generic kernel, touchpad and
touchscreen work without the pci=nocrs kernel parameter. Good job and
thank you.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
AceLan, I have tested your kernel and touchscreen and touchpad work,
without the pci=nocrs GRUB option. Thank you very much!
I have two pieces of feedback on it that I think are specific to my
system, but I want to log them in case they aren't. After selecting the
patched 5.15 kernel in GRUB, I
Here is the test kernel and patches I applied, please give it a try.
BTW, remember to disable secure boot in BIOS if you want to try the test
kernel
https://people.canonical.com/~acelan/bugs/lp1884232/
--
You received this bug notification because you are a member of Kernel
Packages, which is
It requires below 5 commits for Jammy 5.15 kernel
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Jammy)
Status: New => In
v5.19-rc1 was tagged Sun Jun 5 17:18:54 2022 -0700. Final release
likely to be July 24 or 31. The crystal ball:
https://hansen.beer/~dave/phb/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks for informing us, Bjorn. That means the safest way to go is wait
until one's favourite distro ships kernel 5.19, which requires 5.19 be
oficially out (non-rc stable final) - any estimates how long this might
be (how much time kernel updates usually need to get from RC1 to final
release?)
Should be fixed by https://git.kernel.org/linus/d341838d776a, which will
appear in v5.19-rc1.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and touchscreen
The pci=nocrs option is working again with kernel 5.18. It's still
needed to get the touchpad working.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and
There are several users of this laptop, so once patched test kernel is
available, we would certainly test it out... This bug is quite SERIOUS
and it causes me to stay at 20.10...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
Sorry that it is taking so long to fix this. There have been several
attempts at fixing this upstream already, but all of them had to be
reverted/dropped because they were causing issues on other laptop
models.
The latest attempt at fixing this is here:
This workaround is no longer working when upgraded to 22.04. I have
added all the details on ask ubuntu and ubuntu forums:
https://askubuntu.com/questions/1402796/touch-pad-and-touch-screen-are-
not-working-after-upgrading-to-ubuntu-22-04
This workaround (pci=nocrs) sorted my Touchpad issues on a Clevo NL51LU; it
wasn't being detected due to the 'resource claim' issue at boot, as above.
See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1904052.
Incidentally, I tried kernels up to 5.10.0 and same problem.
--
You received
Actually, it looks like the pen is working in X11. Never mind that part.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1884232
Title:
touchpad and touchscreen doesn't work at all on
Thank you for the workaround! With the latest Ubuntu this works with
just the "pci=nocrs" parameter. The pen input works fully in Wayland,
but not at all in X11.
Also, I wrote an installation guide for this laptop with more fixes and tips:
** Summary changed:
- touchpad and touchscreen doesn't work at all on ACER Spin 5
+ touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
35 matches
Mail list logo