Re: [gentoo-user] Kernel 5.15.11 won't boot

[Neil Bothwick]

On Tue, 28 Dec 2021 18:14:51 +0000, Michael wrote:

> On Tuesday, 28 December 2021 16:09:09 GMT Peter Humphrey wrote:
> > On Tuesday, 28 December 2021 13:40:44 GMT Neil Bothwick wrote:
> > > I recently upgraded several systems from gentoo-sources-5.10.76-r1
> > > to 5.15.11, using my usual approach
> > >
> > > copy current config to new sources
> > > make oldconfig
> > > all modules_install install
> > > run dracut
> > > reboot
> > >
> > > All worked well except my desktop, which just sits there showing
> > >
> > > EFI stub: Loaded initrd from command line option
> > >
> > > So the bootloader has loaded the kernel but then there is absolutely
> > > nothing. I tried removing the initrd option, but then it went
> > > straight to a blank screen without the above message. I left it for
> > > a while, in case it was just a case of no output, but nothing
> > > happened, not disk or network activity, nothing.
> >
> > Did you touch the new frame-buffer settings? I did at first and got
> > something like your experience, but then after a distclean and
> > oldconfig, making sure to leave the new frame buffer at their
> > defaults, everything now works.
> >
> > I'll look into how it's supposed to work when I get back home.
>
> I also ended up with a blank screen followed by a reboot, which showed
> some partitions were not unmounted cleanly, followed by repeated
> reboots in the same fashion, until I interfered to stop this madness.
> I then booted with the previous kernel and as my first task I disabled
> some framebuffer setting, which I now fail to recall!  LOL!
>
> I think it is this one:
> =======================
> CONFIG_DRM_SIMPLEDRM:

I don't have that one set. About the only framebuffer I have set is
CONFIG_FB_EFI and changing that makes no difference.

I'm not convinced it is display related as I do get the initial message
from the bootloader displayed as normal.

>
> DRM driver for simple platform-provided framebuffers.
>
> This driver assumes that the display hardware has been initialized
> by the firmware or bootloader before the kernel boots. Scanout
> buffer, size, and display format must be provided via device tree,
> UEFI, VESA, etc.
>
> On x86 BIOS or UEFI systems, you should also select SYSFB_SIMPLEFB
> to use UEFI and VESA framebuffers.
>
> Symbol: DRM_SIMPLEDRM [=n]
> Type  : tristate
> Defined at drivers/gpu/drm/tiny/Kconfig:54
>   Prompt: Simple framebuffer driver
>   Depends on: HAS_IOMEM [=y] && DRM [=y]
>   Location:
>     -> Device Drivers
>       -> Graphics support
> Selects: DRM_GEM_SHMEM_HELPER [=y] && DRM_KMS_HELPER [=y]
>
> Simple framebuffer driver (DRM_SIMPLEDRM) [N/m/y/?] (NEW)
> ======================================================


-- 
Neil Bothwick

I wonder how much deeper would the ocean be without sponges.