Mailing List Archive

On Fri, Feb 02, 2024 at 11:54:49AM -0500, Walter Dnes wrote
> As per the subject line, I upgraded kernel 5.15.69 ==> 6.6.13. No
> console on bootup, but I can ssh in. Fortunately I make it a habit to
> keep the previous kernel around, so I can fall back to it. But I'd like
> to get the latest kernel working. This is an old BIOS-boot Lenovo.
> File-attached is the diff between the .config files from 5.15.69 to
> 6.6.13 kernels. In "vim" or "less" go "/2191a2330,2331" and you'll get
> to the beginning of the video stuff. Any ideas?

Oops, forgot the attachment. Here it is...

--
Roses are red
Roses are blue
Depending on their velocity
Relative to you

I got linux-6.1.57-gentoo kernel built and working, but
linux-6.6.13-gentoo still comes up with no console. Here's my latest
.config attempt for 6.6.13 attached. Any ideas?

--
Roses are red
Roses are blue
Depending on their velocity
Relative to you

Le 03/02/24 à 03:06, Walter Dnes a tapoté :
> I got linux-6.1.57-gentoo kernel built and working, but
> linux-6.6.13-gentoo still comes up with no console. Here's my latest
> .config attempt for 6.6.13 attached. Any ideas?
>

You should try to enable an early framebuffer driver, CONFIG_FB_VESA=y
for example. See:

https://wiki.gentoo.org/wiki/Framebuffer#DRM_framebuffer_drivers

On Saturday, 3 February 2024 09:23:15 GMT netfab wrote:
> Le 03/02/24 à 03:06, Walter Dnes a tapoté :
> > I got linux-6.1.57-gentoo kernel built and working, but
> >
> > linux-6.6.13-gentoo still comes up with no console. Here's my latest
> > .config attempt for 6.6.13 attached. Any ideas?
>
> You should try to enable an early framebuffer driver, CONFIG_FB_VESA=y
> for example. See:
>
> https://wiki.gentoo.org/wiki/Framebuffer#DRM_framebuffer_drivers

It could well be more than 15-20 years since I had VESA FB enabled and not
once since then, without any detriment to a console coming up at boot. Try
switching to [*] the following:

# CONFIG_SYSFB_SIMPLEFB is not set

# CONFIG_DRM_SIMPLEDRM is not set

# CONFIG_FB_SIMPLE is not set

Then hopefully you'll get a console kicking in. Also, unless you use an
initrd don't forget any firmware blobs which may be be needed by your graphics
card and while you're at it add your CPU microcode there too. Currently you
only show the firmware for your wireless:

# Firmware loader
#
CONFIG_FW_LOADER=y
CONFIG_EXTRA_FIRMWARE="iwlwifi-6000-4.ucode"

Then, if you still fail to get a console, connect over ssh to check what dmesg
reports for any hints of missing drivers.

HTH.

On Sat, Feb 03, 2024 at 10:18:41AM +0000, Michael wrote

> Try > switching to [*] the following:
>
> # CONFIG_SYSFB_SIMPLEFB is not set
>
> # CONFIG_DRM_SIMPLEDRM is not set
>
> # CONFIG_FB_SIMPLE is not set
>
> Then hopefully you'll get a console kicking in.

It teased me. Text console present first part of bootup with the
fast-scrolling output, then it disappears. It may be a kernel bug
that's solved in the 6.7.x series, so I'll revert the changes and wait
fpr a 6.7.x kernel to show up in "emerge --sync". See...
https://discussion.fedoraproject.org/t/f39-kernel-6-6-x-no-video-on-intel-integrated-graphics/98360

] I was filling out the details for a bug report. Under the description,
] it asked if I have tried rawhide. I installed 6.7.0-0.rc4.35.fc40 and
] it fixed the issue!

> Also, unless you use an initrd don't forget any firmware blobs which
> may be be needed by your graphics card and while you're at it add
> your CPU microcode there too.

The graphics is a bog standard Intel i915 integrated chip that's been
running on the laptop for years without blobs.

--
Roses are red
Roses are blue
Depending on their velocity
Relative to you

On Saturday, 3 February 2024 16:16:42 GMT Walter Dnes wrote:
> On Sat, Feb 03, 2024 at 10:18:41AM +0000, Michael wrote

> > Also, unless you use an initrd don't forget any firmware blobs which
> > may be be needed by your graphics card and while you're at it add
> > your CPU microcode there too.
>
> The graphics is a bog standard Intel i915 integrated chip that's been
> running on the laptop for years without blobs.

It is running for years with the blobs included in the OEM's BIOS firmware.
The hardware could do with the patches for bugs and vulnerabilities issued
since you bought the PC.