Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #75171 > unrolled thread

Bug#1010346: linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel

Back to article view | Back to linux.debian.kernel

Contents

  Bug#1010346: linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel Vasudev Kamath <vasudev@debian.org> - 2022-04-29 12:10 +0200
    Bug#1010346: linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel Bastian Blank <waldi@debian.org> - 2022-04-29 14:10 +0200

#75171 — Bug#1010346: linux-image-cloud-amd64: Enable CONFIG_FB_EFI=y in Buster Cloud Kernel

Package: linux-image-cloud-amd64
Version: 4.19+105+deb10u15
Severity: important

Dear Maintainer,

Booting a KVM based VM with UEFI enabled using Buster image with cloud kernel will have
a non working VNC console. Console seems to be frozen on debugging we figured out that 
its because buster cloud kernel does not have CONFIG_FB_EFI enabled.

This issue is not present in Bullseye kernel as it was enabled in following commit [1].
Can we also enable same option for Buster cloud kernel?. Else for using VNC like console
VM image needs to be running regular kernel (linux-image-amd64).


[1] https://salsa.debian.org/kernel-team/linux/-/commit/aa2bac77ef935f38b64a080a29318792c895eb12

Thanks and Regads,
Vasudev

-- System Information:
Debian Release: bookworm/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 5.16.0-6-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-cloud-amd64 depends on:
pn  linux-image-5.17.0-1-cloud-amd64  <none>

linux-image-cloud-amd64 recommends no packages.

linux-image-cloud-amd64 suggests no packages.

[toc] | [next] | [standalone]

#75172

Hi Vasudev

On Fri, Apr 29, 2022 at 03:27:26PM +0530, Vasudev Kamath wrote:
> Booting a KVM based VM with UEFI enabled using Buster image with cloud kernel will have
> a non working VNC console. Console seems to be frozen on debugging we figured out that 
> its because buster cloud kernel does not have CONFIG_FB_EFI enabled.

The cloud kernel is marked for specific environments only.  All of them
use the serial console first.

> This issue is not present in Bullseye kernel as it was enabled in following commit [1].
> Can we also enable same option for Buster cloud kernel?. Else for using VNC like console
> VM image needs to be running regular kernel (linux-image-amd64).

Buster is in maintenance mode.  So, why?

Bastian

-- 
Time is fluid ... like a river with currents, eddies, backwash.
		-- Spock, "The City on the Edge of Forever", stardate 3134.0

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web