Thanks, before testing I disabled the intel_iommu= workaround, and this
kernel does indeed fix the flicker issue for me.
For reference this is my hardware:
$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620
[8086:5917] (rev 07)
DeviceName: O
Hi @rebbel, the kernel version you cite is the "fixed" version, but it
does not include a fix for *all* affected hardware. Since you have
already provided in comment 116 the hardware info that AceLan requested,
you have done everything you need to at this time. Hopefully AceLan can
soon prepare a
> If adding "intel_iommu=igfx_off" works for you, but you still encounter the
> flicker issue with 6.8.0-48.48,
> please attch your gfx info here, thanks.
>lspci -nnk | grep -A3 VGA
$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620
[8086
4. Or per comment 73 your CPU/GPU is affected by this issue but is not
yet covered by the patch in 6.8.0-48? I'm hoping AceLan can chime in
concerning what hardware is covered by the patch and what is still
planned.
--
You received this bug notification because you are a member of Kernel
Package
The proposed kernel does not fix the issue for me, but maybe this is
expected? AceLan, does the workaround include Kaby Lake R CPUs yet?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-6.8 in Ubuntu.
https://bugs.launchpad.net/b
Hi Adam,
I believe there are different flickering bugs affecting different
processors at this time. Does the `intel_iommu=igfx_off` workaround
work for you? That would go toward understanding whether you are
affected by #2062951.
--
You received this bug notification because you are a member o
> And in this bug, we are trying to fix the flicker issue that can be worked
> around by intel_iommu=igfx_off
> I'll need your VGA PCI ID if intel_iommu=igfx_off works for you.
>lspci -nnk | grep -A3 VGA
$ lspci -nnk | grep -A3 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation U
> model name : Intel(R) Core(TM) Ultra 7 155H
Hi Sean, this processor does not appear to have a Gen9 GPU. You are
likely experiencing another bug. You may consider opening a new bug
report.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed t
> Thank you for doing your research into the issue but I am confused by
> your results.
>
> Are you claiming that removing mentioned Ubuntu specific commit resolves
> the issue?
Specifically it's the first commit where I experience the bug, so I
would assume that reverting it will resolve the iss
Despite some of the nondeterminism behind this bug, I believe I have
bisected this bug to the following commit in the Ubuntu kernel tree:
14ebfcacaeb07b02235f2ea881fd6e34e3de0d6f .
More info is available on this commit here:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/unsta
** Changed in: linux (Ubuntu)
Status: Expired => Incomplete
--
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/1320022
Title:
[Dell Latitude E6540] ALPS touchpad keeps having state re
Øyvind, I experienced that when I upgraded to BIOS A10 from A08.
Fortunately, I was able to downgrade from A10 back to A08. I suspect
that either A10 has an issue or it just pokes even harder at this bug
than A08 did. (A10 cites "Keyboard input improvement" as one of its
fixes, which is probably
There's no actual regression though because, although the generic mouse
driver doesn't have the sync issue, using it is even worse since it
doesn't expose any touchpad-specific functionality.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Allan, do the older kernels that don't seem to exhibit the bug recognize
the touchpad as a touchpad? For instance, with the older kernels that
don't seem to exhibit the bug, does the 'xinput' command list a generic
mouse instead of what's normally listed as your touchpad?
--
You received this bu
This sync issue with the E7440 touchpad can cause spurious clicks too.
One thing that I found helps is to add psmouse.resetafter=1 to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub (and then run update-
grub and reboot).
This will cause the driver to reset when it loses sync, causing the
touchpa
15 matches
Mail list logo
