Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers
Hi Tobias, On Thu, Dec 30, 2021 at 11:50:18PM +0100, Tobias Gruetzmacher wrote: > Hi, > > On Mon, Dec 13, 2021 at 10:14:22PM +0100, Uwe Kleine-König wrote: > > > it would be nice if the Debian kernel would provide drivers to interact > > > with CoreBoot. As far as I can see, those are "hidden" behind > > > CONFIG_GOOGLE_FIRMWARE ... > > > > The helptext for GOOGLE_FIRMWARE reads: > > > > These firmware drivers are used by Google's servers. They are > > only useful if you are working directly on one of their > > proprietary servers. If in doubt, say "N". > > Yes, that is a very unfortunate help text... > > > Is this text wrong, or are you working on Google's servers? In case > > you're not on Google's servers: Did you verify these settings are > > beneficial on your machine? > > I'm not working on Google servers, but on a "generic" CoreBoot-device. I > can confirm that when using linux-image-5.16.0-rc7-amd64-unsigned, I can > load memconsole-coreboot, which in turn gives me access to CoreBoot logs > in /sys/firmware/log, so the feature is working as intended! > > (As an aside: The file /sys/firmware/log is world-readable after the > module is loaded, this might leak some information about the hardware to > users) Can you report this to upstream? Regards, Salvatore
Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers
Hi, On Mon, Dec 13, 2021 at 10:14:22PM +0100, Uwe Kleine-König wrote: > > it would be nice if the Debian kernel would provide drivers to interact > > with CoreBoot. As far as I can see, those are "hidden" behind > > CONFIG_GOOGLE_FIRMWARE ... > > The helptext for GOOGLE_FIRMWARE reads: > > These firmware drivers are used by Google's servers. They are > only useful if you are working directly on one of their > proprietary servers. If in doubt, say "N". Yes, that is a very unfortunate help text... > Is this text wrong, or are you working on Google's servers? In case > you're not on Google's servers: Did you verify these settings are > beneficial on your machine? I'm not working on Google servers, but on a "generic" CoreBoot-device. I can confirm that when using linux-image-5.16.0-rc7-amd64-unsigned, I can load memconsole-coreboot, which in turn gives me access to CoreBoot logs in /sys/firmware/log, so the feature is working as intended! (As an aside: The file /sys/firmware/log is world-readable after the module is loaded, this might leak some information about the hardware to users) Regards, Tobias
Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers
Hello Tobias, On Sun, Dec 22, 2019 at 04:45:12PM +0100, Tobias Gruetzmacher wrote: > Package: src:linux > Version: 5.3.15-1 > Severity: wishlist > > it would be nice if the Debian kernel would provide drivers to interact > with CoreBoot. As far as I can see, those are "hidden" behind > CONFIG_GOOGLE_FIRMWARE ... > > These seem to be all available as modules, so it won't hurt to switch > them on, right? (If I understand drivers/firmware/google/Makefile > correctly) > > For reference: > > CONFIG_GOOGLE_FIRMWARE=y > CONFIG_GOOGLE_SMI=m > CONFIG_GOOGLE_COREBOOT_TABLE=m > CONFIG_GOOGLE_MEMCONSOLE=m > CONFIG_GOOGLE_MEMCONSOLE_X86_LEGACY=m > CONFIG_GOOGLE_FRAMEBUFFER_COREBOOT=m > CONFIG_GOOGLE_MEMCONSOLE_COREBOOT=m > CONFIG_GOOGLE_VPD=m The helptext for GOOGLE_FIRMWARE reads: These firmware drivers are used by Google's servers. They are only useful if you are working directly on one of their proprietary servers. If in doubt, say "N". Is this text wrong, or are you working on Google's servers? In case you're not on Google's servers: Did you verify these settings are beneficial on your machine? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | https://www.pengutronix.de/ | signature.asc Description: PGP signature
Bug#947179: linux-image-5.3.0-3-amd64: Please provide CoreBoot (Google) firmware drivers
Package: src:linux Version: 5.3.15-1 Severity: wishlist Hi, it would be nice if the Debian kernel would provide drivers to interact with CoreBoot. As far as I can see, those are "hidden" behind CONFIG_GOOGLE_FIRMWARE ... These seem to be all available as modules, so it won't hurt to switch them on, right? (If I understand drivers/firmware/google/Makefile correctly) For reference: CONFIG_GOOGLE_FIRMWARE=y CONFIG_GOOGLE_SMI=m CONFIG_GOOGLE_COREBOOT_TABLE=m CONFIG_GOOGLE_MEMCONSOLE=m CONFIG_GOOGLE_MEMCONSOLE_X86_LEGACY=m CONFIG_GOOGLE_FRAMEBUFFER_COREBOOT=m CONFIG_GOOGLE_MEMCONSOLE_COREBOOT=m CONFIG_GOOGLE_VPD=m Thanks for consideration! Tobias -- Package-specific info: ** Version: Linux version 5.3.0-3-amd64 (debian-ker...@lists.debian.org) (gcc version 9.2.1 20191130 (Debian 9.2.1-21)) #1 SMP Debian 5.3.15-1 (2019-12-07) ** Command line: \\vmlinuz-5.3.0-3-amd64 ro root=/dev/mapper/ssd-root quiet splash initrd=\initrd.img-5.3.0-3-amd64 ** Tainted: OE (12288) * Out-of-tree module has been loaded. * Unsigned module has been loaded. ** Kernel log: Unable to read kernel log; any relevant messages should be attached ** Loaded modules: vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.3.0-3-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), LANGUAGE=de:en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-5.3.0-3-amd64 depends on: ii initramfs-tools [linux-initramfs-tool] 0.135 ii kmod26-3 ii linux-base 4.6 Versions of packages linux-image-5.3.0-3-amd64 recommends: pn apparmor ii firmware-linux-free 3.4 Versions of packages linux-image-5.3.0-3-amd64 suggests: pn debian-kernel-handbook ii grub-efi-amd64 2.04-5 pn linux-doc-5.3 Versions of packages linux-image-5.3.0-3-amd64 is related to: ii firmware-amd-graphics 20190717-2 pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-cavium pn firmware-intel-sound pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux-nonfree ii firmware-misc-nonfree 20190717-2 pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-realtek pn firmware-samsung pn firmware-siano pn firmware-ti-connectivity pn xen-hypervisor -- no debconf information
