On Mon, Mar 17, 2025 at 01:59:24PM +0000, Andy Smith via GLLUG wrote:
Hi,
Report it to Kali then.
At this point if this were me on Debian and a bug report didn't result
in a quick fix then I'd be building my own kernel from the source of the
kernel package that fails, confirming that it fails and then doing a
"git bisect" to go further back. I'd repeat this until I got a kernel
that didn't fail at which point I'd be able to further bisect down to
the exact commit that caused the problem for me. I'd then report that in
the Debian bug.
I don't know if you can do that with Kali. If you can't, it might be
possible to find two upstream (i.e. kernel.org) source versions that are
stable and fail respectively, and do the same bisect there. Knowing
which upstream commit breaks it for you would still be useful
information for your distribution.
Thanks,
Andy
Thanks,
I've just been made "redundant" in a kangaroo court (after submitting an
Employment Tribunal case, oddly enough) (any jobs going?) so I now have all the time in
the world to try this.
Regards,
Henrik Morsing
--
GLLUG mailing list
[email protected]
https://mailman.lug.org.uk/mailman/listinfo/gllug
