Hi Po-Hsu,
I installed the Focal kernel (using dpkg -i) then removed the
i8042.noloop=1 boot option and rebooted. The touchpad still works, and
I confirmed that I was actually running the 5.0.4-57 kernel you
provided. Looks really good for Focal.
Would you like me to do the same for the Bionic
Hi Po-Hsu,
I installed the Bionic kernel and booted it. Yes, it is also fixed.
4.15.0-127 works.
Thanks again for your help and Best Regards,
Tom
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.ne
Hi - I'm happy to help test if desired. If it's the right thing, I can
install and test kernels using these instructions:
https://askubuntu.com/questions/700214/how-do-i-install-an-old-kernel
However, I need a clue to exactly which kernels I should test. from
https://kernel.ubuntu.com/%7Ekernel-
Public bug reported:
Touchpad hardware is OK and works for Win10. Not working for live disc,
not for 18.04 and not for 20.04 after upgrading. I've attached a
Logitech wireless mouse with its USB adapter and that works. Bluetooth
is also missing, but I have not started trying to skull that out.
I've tried adding kernel boot switches: i8042.reset i8042.nomux
i8042.nopnp i8042noloop
and also noapic. They made no difference.
** Bug watch added: Linux Kernel Bug Tracker #93791
https://bugzilla.kernel.org/show_bug.cgi?id=93791
--
You received this bug notification because you are a me
Found something for same motherboard but different OEM:
commit 2e2679a168fe1a0a9089e4e401d6a51b26c4f557
Author: Marcos Paulo de Souza
Date: Sun Dec 18 15:26:12 2016 -0800
Input: i8042 - add Pegatron touchpad to noloop table
commit 41c567a5d7d1a986763e58c3394782813c3bcb03 upstream.
Found something for same motherboard but different OEM:
commit 2e2679a168fe1a0a9089e4e401d6a51b26c4f557
Author: Marcos Paulo de Souza
Date: Sun Dec 18 15:26:12 2016 -0800
Input: i8042 - add Pegatron touchpad to noloop table
commit 41c567a5d7d1a986763e58c3394782813c3bcb03 upstream.
Hi Po-Hsu,
Just reiterating that Groovy checked out fine. I did not see a proposed
kernel for Focal, even through the Bot said to try it. I get kernel
5.8.0-43 both before and after enabling proposed. Am I missing
something again, like with Bionic? It seems that regardless of the
20.04.* I ins
Hi Po-Hsu,
Happy New Year. I guess I was just too eager. Today I saw an update to
a proposed kernel in focal. That kernel was 5.8.0-44 and it works just
fine. So you can mark all of these as good to go.
Regards,
Tom
--
You received this bug notification because you are a member of Kernel
P
Hi Po-Hsu
I spent this evening installing Ubuntu. I tried Xenial, Bionic, Focal
and Groovy.
The proposed release worked on Xenial, but not on any of the others.
Just to confirm the process: I installed a fresh copy of the release,
then went to the developer options tab in the Software and Upda
Hi Po-Hsu,
I spent this evening installing Ubuntu. I tried Xenial, Bionic, Focal and
Groovy.
The proposed release worked on Xenial, but not on any of the others.
Just to confirm the process: I installed a fresh copy of the release,
then went to the developer options tab and ticked the proposed
Hi Po-Hsu,
Maybe I'm installing the wrong Bionic? I've installed
ubuntu-18.04.5-desktop-amd64.iso. That gives me kernel 5.4.0-62 before
proposed, and 5.4.0-64 after enabling proposed.
Thanks,
Tom
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
Hi Po-Hsu,
That one worked. Freshly installed, I had 4.15.0-29 and after enabling
proposed and upgrading I was left with 4.15.0-135 That kernel worked just
fine.
How long until I can expect to see the proposed kernels for Focal/Groovy?
Thanks and Regards,
Tom
--
You received this bug notif
Hi, I loaded groovy, enabled proposed, and the new kernel works just
fine. There were other problems with this install. I let the installer
update while installing, and that failed bad. I had to tell grub to
boot the previous kernel. I let the reporting app send those details.
But, after rebo
I just wanted to wrap up a loose thread. I upgraded my system to
ubuntu 23.10 (not a fresh install) and after the upgrade I no longer
have this issue. The system blanks the screen perfectly.
Thanks for taking the time to help troubleshoot.
--
You received this bug notification because you are
Hello again. Something strange happened today. The computer booted,
and bingwall ran successfully. (normally it hangs from some new
interaction with apparmor (I think). Also on this boot, the screen
blank went directly from on to off. (Normally it slowly dims the screen
before turning it off)
Seems I can only attach one file per comment. Attached is the prevboot
that crashed from my previous comment.
** Attachment added: "prevboot.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2032535/+attachment/5701814/+files/prevboot.txt
--
You received this bug notification becaus
I went back to confirm the problem on other systems. Despite what I
wrote before, Ubuntu 22.04.3 does crash when sleeping. My first post
stands as correct. Also, I tried Debian 12 with gnome and wayland.
That system does not crash - and it has a very similar look and feel to
Ubuntu.
--
You r
18 matches
Mail list logo
