Re: X stopped working with 5.14 on iBook
Hi Riccardo,
On 10/12/21 4:52 PM, Riccardo Mottola wrote:
> ...
>
> Sorry I fail to understand fully. You cannot reproduce using Debian's
> config file with the current kernel: this is good news, since it means
> that possibly there is no upstream bug.
Debian's 5.10.0-8 config file works (as expected) with Debian's 5.10.0-8
kernel source.
Debian's 5.14 config file fails (as expected) with Debian's 5.14 kernel
source.
X works with 5.14 using a tuned config file derived from 5.13 testing.
X fails using Debian's 5.10.0-8 config file to build a 5.14 kernel. So
either there is a kernel regression from 5.10 and 5.14 that causes the
problem, or there are one or more config file options that Debian is
using trigger different kernel behavior from 5.10 to 5.14, or some
combination.
> However you were not able to build a Debian-like kernel: so it might
> still be something specific to the Debian configuration and/or building?
I'm guessing it's a Debian config file option issue or an Xorg issue,
since I don't see any kernel messages when it fails.
>
> About the super-big kernel, I remember this, but there was a fix that
> Adrian suggested which I don't remember. That would be the cross-check.
> ...
Adrian solved that; I just needed to strip the kernel.
I'm attempting to modify Debian's 5.10.0-8 config file slightly so it'll
work on my G4 Cube without having to compile modules (I want to make as
few changes as possible to the config file, which currently causes 10 GB
of disk space to be used during cross-compilation of modules). Then I'll
use that config file and try a kernel bisect to locate a possible kernel
regression. But that may not work if the problem turns out to be a
Debian config file option that, for example, triggers something in the
kernel that hasn't changed but has never worked on G4 systems. Then the
only way to identify the problem could be to remove config file options
one at a time until it works, and I probably won't try to do that. It's
also possible that a change was made in Xorg that caused the problem. So
I'm not optimistic that I have the necessary skills to identify the
issue, but I'm still looking.
-Stan
Reply to: