Finally I managed to compile the kernel via
debian/bin/test-patches
../0001-Revert-drm-nouveau-add-nv_encoder-pointer-check-for-.patch
../0002-Revert-drm-nouveau-dp-check-for-NULL-nv_connector-na.patch
../0003-Revert-drm-nouveau-don-t-detect-DSM-for-non-NVIDIA-d.patch
../0004-Revert-nouveau-fix-client-work-fence-deletion-race.patch
(apparently successfully, but it took several hours). But now I am a
little clueless: how do I install this kernel? Any hint?
Cheers,
Olaf
On Mon, 31 Jul 2023 at 22:42, Diederik de Haas wrote:
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
