Are there any guidelines for affected users who already updated before
they got the warning?
Interesting questions for affected users:
- Is it safe to assume that other filesystems (like BTRFS) are not
affected?
- Does this cause filesystem corruption or only file corruption?
- Does this affect me
Hello everybody
I can confirm the same problems. At first I thought the network problem
was due to proprietary Broadcom driver because network connectivity was
the most obvious problem.
However, most problems persisted after removing the driver. I do not
have any other proprietary or custom kerne
Hello everybody
Unfortunately, I can confirm the same problems for 2014 Macbook Pro
(Intel CPU and graphics).
At first I thought the network problem was due to the proprietary
Broadcom WLAN driver because network connectivity was the most obvious
problem. However, the problems persisted after rem
Hereby I confirm that linux-image-6.1.0-16-amd64 (6.1.67-1) from
bookworm-proposed-updates fixed the problems for me.
Regards
Stephan
signature.asc
Description: This is a digitally signed message part
I can confirm this on my machine (2014 Macbook Pro).
Note that DKMS for NVIDIA appears to work. I guess the problem is on
Broadcom side using deprecated APIs.
Regards
Package: src:linux
Version: 5.18.2-1
The touchpad on my 2014 Macbook (MacBookPro11,1) is no longer working
since kernel 5.18 was installed. This affects both X11 and Wayland. I
am using Sid with Gnome.
When booting back into kernel 5.17, the touchpad works without
problems. That's why I suspect t
When I filed the bug, I could not find any other reports. Now I found
an upstream report which has matching symptoms.
https://bugzilla.kernel.org/show_bug.cgi?id=215890
However, there is confusion about the resolution. One reply states that
it was resolved in 5.18.0, but other replies talk about
They merged it (on June 7) into kernel 5.19, but kernel 5.18.3
(released June 9) does not seem to have it yet.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/?id=v5.18.3&id2=v5.18&dt=2
I will just use 5.17 or external mouse until the fix lands in Sid.
Thank you and regards
Kernel 5.18.4 got the patch.
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/diff/drivers/input/mouse/bcm5974.c?id=v5.18.4&id2=v5.18.3
Regards
Package: src:linux
Version: 6.0.3-1
When I boot with kernel 6.0.x, grub-install, efibootmgr etc. keep
failing. With kernel 5.19.x it works on the same machine with the same
userland.
Hardware: MacBookPro11,1, Intel(R) Core(TM) i7-4578U CPU @ 3.00GHz
I am not sure if this app is Apple specific.
I support this request. This will bring new webcam support for a lot of
Intel-based laptops, including models that are actively advertised with
Linux support and sold with Ubuntu/Fedora preinstalled.
Example:
https://ubuntu.com/certified/202301-31165
The corresponding system is called Intel Image
Please note that the options are not configured in the current kernel
6.10.1-1~exp1 in Experimental.
# CONFIG_VIDEO_IPU3_CIO2 is not set
# CONFIG_VIDEO_INTEL_IPU6 is not set
# CONFIG_INTEL_VSC is not set
# CONFIG_IPU_BRIDGE is not set
Regards
Stephan
signature.asc
Description: This is a digital
I have installed the package “linux-source”, applied the patch,
compiled and booted it. The patch alone does not appear to fix the
issue. (“efibootmgr -o” still not working.)
Maybe I find time to try vanilla kernel 6.0.5 on the weekend.
Regards
Stephan
I have now compiled and booted vanilla kernel 6.0.5. “efibootmgr -o” is
not working.
I double-checked that with kernel 5.19.11 (Debian), it is working fine.
Regards
Some more information:
linux-image-5.19.0-2-amd64/now 5.19.11-1 (not affected)
linux-image-6.0.0-1-amd64/now 6.0.2-1+b1 (affected)
linux-image-6.0.0-2-amd64/unstable,now 6.0.3-1 (affected)
linux-image-6.0.5/now 6.0.5-1 (custom vanilla kernel build, affected)
Other relevant package versions (no re
For completeness: The problem persists with the new kernel in Sid.
> 6.0.0-2-amd64 / Debian 6.0.5-1 (2022-10-28) x86_64 GNU/Linux
Sice the latest vanilla kernel does not work, I have filed an upstream
bug.
https://bugzilla.kernel.org/show_bug.cgi?id=216640
Regards
Some updates.
linux-image-6.0.0-2-amd64 6.0.6-2 does not fix the bug.
In the upstream bug, a new set of new patches were mentioned which
should address this issue. I expect them to be merged into version
6.0.7.
New patches regarding EFI:
https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.gi
Update for completeness:
The EFI patches have not made it into 6.0.7. As expected, 6.0.7 from
Debian still has the problem.
New EFI patches have been merged into master on November 4. I hope to
find them in 6.0.8 or 6.1. Then I will test again.
Regards
Yesterday, kernel 6.0.8 was released with a number of EFI fixes. I have
compiled the vanilla kernel and I am happy to confirm that it solves
the issue.
Regards
I am happy to confirm that with Linux kernel 6.0.8-1 in Debian Sid, the
issue is fixed.
Regards
21 matches
Mail list logo
