On Monday, 31 July 2023 21:52:44 CEST Olaf Skibbe wrote: > > Yep, now we know it's a regression between 6.1.27-1 and 6.1.38-2. > > > > https://wiki.debian.org/DebianKernel/GitBisect describes the best way as > > it would identify the exact (upstream) commit which introduced the > > problem. If you can do that, great. > > I'd love to contribute here, but I am afraid this would be a bit beyond > my capabilities. I now have only remote access to the computer in > question (I have to ask somebody to verify whether the display is > working) and I am not very experienced. Sorry. That's ok, I (kind of) expected that a `git bisect` would be too difficult. That's why I also described a simpler procedure which is specifically meant for people who aren't experienced. It will result in a new kernel being build, but all the complexity should be hidden for you. It probably sounds daunting/scary, but it shouldn't be. There is a subsequent step, but that is (far) more likely to succeed if we'd have more detailed data which the above procedure would provide. So it would be great if you could try it. If it turns out to be too difficult, don't worry about it :-) Cheers, Diederik
Attachment:
signature.asc
Description: This is a digitally signed message part.