On Wed, Sep 08, 2021 at 07:30:49AM +0200, Greg KH wrote:
That is a vt change that handles an issue with a console driver, so this feels like a false failure.
If you revert this change on a newer kernel release, does it work?
Oh, you mean a higher version number (which wasn't directly obvious to me). Make oldconfig gives an awful lot of output which I'm not going to read. Just keep pressing the return key for all the defaults. Kernel-5.10.10 runs into a black screen, I can perform a blind login and play an audio file. I then tried to revert the patch, but git couldn't complete it. The closest uplevel version is 4.14.246 which I then tried. It runs into a black screen, but I can login and play audio, but no reaction on modprobe fbcon. Git revert ran fine, but that also gave me a black screen. It appeared that there was no fbcon.ko, even worse, the option to modularize it was gone! Insane. Since that option was now invalid, make oldconfig chose for a default no, which I didn't know. In-kernel fbcon gives no problems, I guess. This led to the discovery that the hard crash in 4.9.270(-282) did NOT occur when fbcon.ko was not loaded. Modprobe fbcon after i915 went fine.
So here you have another reason to not wanting to run a kernel version above 4.9. I need fbcon.ko as a diagnostics tool. In many machines with i915 I loose sound when i915.ko gets loaded. I need to fiddle with the rc scripts to make sure that the snd modules got loaded first. And because the changing fonts and layout drives me nuts while looking at the progress, I need to put fbcon/i915 the very last (in rc.local).
Regards, Wim.