coreboot November 2019

coreboot@coreboot.org

52 participants
51 discussions

VBOOT_ENABLE_CBFS_FALLBACK config option
by Jorge Fernandez Monteagudo 14 Nov '19

14 Nov '19

Hi all, I've found in 'https://doc.coreboot.org/security/vboot/index.html' the next configuration: VBOOT_ENABLE_CBFS_FALLBACK but nothing in the code for this configuration! Anyone knows something? Any code in some repository? Is it deprecated? Removed? Regards Jorge

2 2

coreboot and linuxboot
by Jorge Fernandez Monteagudo 14 Nov '19

14 Nov '19

Hi all, I've built a coreboot with the LinuxBoot payload. The kernel is the stable 5.3.8 version and the intiramfs is the u-root master version. All with the default choices. I'm using coreboot 4.10. Once the system boots I get a framebuffer console without usb keyboard support and the u-root welcome message. How can I boot my debian system on a SATA or a USB disk? Maybe, first I've to add SATA and usb storage support? Is there someway to looks for the grub configuration automatically? Sorry my noob questions, just arrived to LinuxBoot... Thanks! Jorge

3 4

Contact Info payload
by Tom Hiller 14 Nov '19

14 Nov '19

Is there a way to store contact information or in case of emergency information in a payload in the event my laptop if lost or stolen?

3 2

Re: No framebuffer available until amdgpu driver is loaded
by Jorge Fernandez Monteagudo 12 Nov '19

12 Nov '19

Hi Nico! >but it is. It's part of 0xd0000000-0xffffffff. > >Beside little SMM and some ACPI, coreboot is no resident firmware like >a BIOS that leaves some code to call into. Hence, if you run the VBIOS >inside coreboot, it will also leave nothing for the OS to query the >framebuffer info. > >You have to make use of the framebuffer info coreboot leaves in it's >own tables. With the current payload loading (I assume the kernel is >wrapped into a SELF binary), this information is not handed over to >the kernel (it could, though). So you need a driver that can fetch it. > >Have a look into drivers/firmware/google/ in the kernel. GOOGLE_ >FRAMEBUFFER_COREBOOT=y should do the trick. > Yes! That's makes sense! I didn't understand how the info was received by the kernel. Now I've patched my kernel with the https://lore.kernel.org/patchwork/cover/875704/ patches and I have framebuffer. Thanks a lot! Jorge

1 0

Howdy!
by Eli Duttman 12 Nov '19

12 Nov '19

I want to update the boot firmware used by an "ancient" ISA bus PC that I'm trying to reactivate. Kevin O'C. told me to use SeaBIOS, I need to use Coreboot. So, here I am. FWIW, I'm a retired IBM mainframe system programmer, with more than 45 years of experience. Please be very gentle with me. What is "old hat" to me doesn't necessarily map onto x86 hardware. The machine in question uses the 3 IC (386DX) version of VTI's "Topcat" chipset. From the day I acquired it, a 486-33DX has been in situ. Part of the reactivation scheme includes the installation of an already on hand IBM/Cyrix 3X clock multiplying 586 CPU. If I read the chipset reference (URL follows immediately) correctly, as much as 64 MB of RAM can be employed. https://ia800603.us.archive.org/0/items/bitsavers_vtiVTITOPCTChipsetOct90_1… I have several reasons for wanting to upgrade the firmware: a Y2K date handling flaw, PIO IDE (PATA) limited to 5nn MB (no LBA) plus no optical drive support, no support of the 586's performance features, and a possible inability to deal with 64 MB of RAM. If the chipset can do it, I want to do it. BTW, an Adaptec AHA1542 SCSI controller will handle the HDD, but full PATA capability, if needed, can't be bad. No EEPROM here. (E)PROM burning will have to be done. While Win 98 as the OS would not be disastrous, I BADLY want to use Linux. Candidate distros seem to be TinyCore and Gentoo. Gentoo has been done on similar hardware and that project's URL follows. http://yeokhengmeng.com/2018/01/make-the-486-great-again/ TIA for your responses. Eli D.

4 9

No framebuffer available until amdgpu driver is loaded
by Jorge Fernandez Monteagudo 12 Nov '19

12 Nov '19

Hi all, I have a little problem trying to get a vesa framebuffer when booting my system. I have the system with the original bios and the vesa fb working. These are the relevant dmesg traces: [ 0.263974] PCI host bridge to bus 0000:00 [ 0.263976] pci_bus 0000:00: root bus resource [io 0x0000-0x03af window] [ 0.263977] pci_bus 0000:00: root bus resource [io 0x03e0-0x0cf7 window] [ 0.263978] pci_bus 0000:00: root bus resource [io 0x03b0-0x03df window] [ 0.263979] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.263980] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff window] [ 0.263981] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff window] [ 0.263982] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xfed3ffff window] <------------------ [ 0.263983] pci_bus 0000:00: root bus resource [mem 0xfedca000-0xffffffff window] [ 0.263985] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.263992] pci 0000:00:00.0: [1022:1576] type 00 class 0x060000 [ 0.264083] pci 0000:00:01.0: [1002:9874] type 00 class 0x030000 [ 0.264098] pci 0000:00:01.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref] [ 0.264105] pci 0000:00:01.0: reg 0x18: [mem 0xf0000000-0xf07fffff 64bit pref] [ 0.264109] pci 0000:00:01.0: reg 0x20: [io 0xf000-0xf0ff] [ 0.264114] pci 0000:00:01.0: reg 0x24: [mem 0xfeb00000-0xfeb3ffff] [ 0.264118] pci 0000:00:01.0: reg 0x30: [mem 0xfeb40000-0xfeb5ffff pref] [ 0.264121] pci 0000:00:01.0: enabling Extended Tags [ 0.264151] pci 0000:00:01.0: supports D1 D2 [ 0.264153] pci 0000:00:01.0: PME# supported from D1 D2 D3hot ... [ 0.279059] pci_bus 0000:00: resource 4 [io 0x0000-0x03af window] [ 0.279061] pci_bus 0000:00: resource 5 [io 0x03e0-0x0cf7 window] [ 0.279062] pci_bus 0000:00: resource 6 [io 0x03b0-0x03df window] [ 0.279063] pci_bus 0000:00: resource 7 [io 0x0d00-0xffff window] [ 0.279064] pci_bus 0000:00: resource 8 [mem 0x000a0000-0x000bffff window] [ 0.279065] pci_bus 0000:00: resource 9 [mem 0x000c0000-0x000dffff window] [ 0.279066] pci_bus 0000:00: resource 10 [mem 0xe0000000-0xfed3ffff window] <-------------------- [ 0.279067] pci_bus 0000:00: resource 11 [mem 0xfedca000-0xffffffff window] ... [ 0.427777] vesafb: mode is 800x600x16, linelength=1664, pages=47 [ 0.427777] vesafb: scrolling: redraw [ 0.427778] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 [ 0.427789] vesafb: framebuffer at 0xe0000000, mapped to 0x (ptrval), using 1950k, total 49152k [ 0.427821] fb0: VESA VGA frame buffer device With the sytem and my modified coreboot I can get a vesa fb working and I get no image on screen until the amdgpu driver is loaded and the Xorg is running. The suspicious dmesg traces are: [ 0.253527] PCI host bridge to bus 0000:00 [ 0.253529] pci_bus 0000:00: root bus resource [io 0x0000-0x0cf7 window] [ 0.253530] pci_bus 0000:00: root bus resource [io 0x0d00-0xffff window] [ 0.253531] pci_bus 0000:00: root bus resource [mem 0x000a0000-0x000bffff] [ 0.253532] pci_bus 0000:00: root bus resource [mem 0x000c0000-0x000dffff] [ 0.253533] pci_bus 0000:00: root bus resource [mem 0xd0000000-0xffffffff] [ 0.253535] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.253544] pci 0000:00:00.0: [1022:1576] type 00 class 0x060000 [ 0.253640] pci 0000:00:01.0: [1002:9874] type 00 class 0x030000 [ 0.253658] pci 0000:00:01.0: reg 0x10: [mem 0xe0000000-0xefffffff 64bit pref] [ 0.253666] pci 0000:00:01.0: reg 0x18: [mem 0xf0000000-0xf07fffff 64bit pref] [ 0.253672] pci 0000:00:01.0: reg 0x20: [io 0x2000-0x20ff] [ 0.253677] pci 0000:00:01.0: reg 0x24: [mem 0xf0b00000-0xf0b3ffff] [ 0.253682] pci 0000:00:01.0: reg 0x30: [mem 0xf0b40000-0xf0b5ffff pref] [ 0.253723] pci 0000:00:01.0: supports D1 D2 [ 0.253724] pci 0000:00:01.0: PME# supported from D1 D2 D3hot ... [ 0.267038] pci_bus 0000:00: resource 4 [io 0x0000-0x0cf7 window] [ 0.267039] pci_bus 0000:00: resource 5 [io 0x0d00-0xffff window] [ 0.267041] pci_bus 0000:00: resource 6 [mem 0x000a0000-0x000bffff] [ 0.267042] pci_bus 0000:00: resource 7 [mem 0x000c0000-0x000dffff] [ 0.267043] pci_bus 0000:00: resource 8 [mem 0xd0000000-0xffffffff] In this case the resource 10 related to the mem address 0xe0000000 is not int the pci_bus 0000:00: root bus resource list and is not in pci_bus 0000:00: resourceX list... and this is the address related to the framebuffer. What could it be the source of the problem? Thanks! Jorge

3 2

Re: No framebuffer available until amdgpu driver is loaded
by Jorge Fernandez Monteagudo 12 Nov '19

12 Nov '19

> How do you know that the monitor receives something? Well, when no receives nothing there is a no signal message on screen and disappears when the console is initialized by coreboot. >Please try it to know that the VGA Option ROM you are using is >correct for example. It’s a valuable data point. The VGA option rom is correct. Previously I was using tianocore payload and was able to initialize a EFI console. No clue about the entry not enumerated in the pci_bus 0000:00 ? Thanks!

1 0

Re: No framebuffer available until amdgpu driver is loaded
by Jorge Fernandez Monteagudo 12 Nov '19

12 Nov '19

>I do not understand that sentence. Do you see anything at all on >the monitor before Linux starts? If so, what payload? But judging >from the payload size, you are using the Linux kernel payload. No, the monitor is black but is receiving a 800x600 signal, then the mode is set. I'm using linuxboot payload. I'm using it to load my final kernel and check the kernel and initramfs signatures. I prefer stay with this payload. Thanks! Jorge

2 1

Re: No framebuffer available until amdgpu driver is loaded
by Jorge Fernandez Monteagudo 12 Nov '19

12 Nov '19

Hi Paul! Sorry, I've done a lot of tests with different configuration but I've attached a coreboot.log and the CBFS from my last coreboot with this problem. >What board with what graphics device is it? I'm testing and AMD bettong board on coreboot-4.10. The graphic card is integrated in the SOC. > Do you run the VGA Option ROM? Without it, you won’t get any output until >a proper driver sets up the device to my knowledge. Yes, I see a graphic mode set in coreboot and the next lines in coreboot log, but no framebuffer once the linux kernel is run. Maybe I have to close this console somehow... VBE: Getting information about VESA mode 4122 VBE: resolution: 800x600@32 VBE: framebuffer: e0000000 VBE: Setting VESA mode 4122 Thanks! Jorge

2 1

Coreboot Stuff for Sale in Germany
by Kinky Nekoboi 11 Nov '19

11 Nov '19

Dont want to spam here, but maybe somebody has interest. https://m.ebay-kleinanzeigen.de/s-anzeigen/deutschland/c0-l0?userIds=229127…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot November 2019