I wish to retract the earlier bug report. First, I misidentified the kernel 
update as 100, but in fact it was 101, not 100 (which was the previous 
version), and second, I just retested and it works fine. 

I don't know what was causing this, but I can state that it did repeatedly not 
work on the new kernel (which, again, is actually 
linux-image-6.12.101+deb13-amd64) after multiple reboots. However, it is now 
working. Sorry for the confusion!

Reply via email to