coreboot June 2017

coreboot@coreboot.org

57 participants
159 discussions

Re: [coreboot] FILO 0.6.0 payload bootloader - Bug Reports!
by Ivan Ivanov 13 Jun '17

13 Jun '17

Sadly "filo> kernel hda1:/vmlinuz" doesnt work as well: gives Disk read error dev=1 drive=0 sector=0 Error 15: File not found My current situation seems like a standard use case: 1) ext2 boot partition at /dev/sda1 (or which is called "hda1" in this case), size of which is 1GB and it is at DOS-partitioned MBR hard drive 2) vmlinuz is at hda1:/vmlinuz , initrd is at hda1:/initrd But so far I am unable to even load a kernel. Either I am doing something very wrong or there is a fundamental problem with FILO which makes it useless outside of QEMU and maybe a couple of IDE legacy systems.... which is really sad if indeed the case :P By the way, when I run "probe" command it tells: IDE channel 0 not found IDE channel 0 not found IDE channel 1 not found IDE channel 1 not found IDE channel 2 not found IDE channel 2 not found IDE channel 3 not found IDE channel 3 not found No word about SATA, but maybe this is a correct behaviour? or not? Please tell me what extra info do you need, and I will try my best to extract and provide it Best regards, Ivan Ivanov aka qmastery 2017-06-13 20:40 GMT+03:00 Stefan Reinauer <reinauer(a)google.com>: > > > On Tue, Jun 13, 2017 at 10:33 AM Ivan Ivanov <qmastery16(a)gmail.com> wrote: >> >> === If you have some ideas about one or more of FILO problems, please tell >> === >> >> %%% 1st problem - FILO is impossible to build on the modern x86_64 >> system (Ubuntu 16.04.2 LTS with gcc 5.4.0) : >> ... >> CC build/x86/context.o >> AS build/x86/switch.S.o >> /bin/sh: 1: --32: not found >> Makefile:177: error while executing receipt for target >> «/home/owner/filo/build/x86/switch.S.o» >> make: *** [/home/owner/filo/build/x86/switch.S.o] Error 127 >> >> No matter what crosscompiling stuff I am trying or what edits I do to >> Makefile - it always fails with this error. However it compiles fine >> at the 32-bit version of the same OS with the same versions of >> packages except for a different architecture >> >> FILO is probably the only payload which has this problem - and this is >> indeed a major problem, because all the major Linux distributions are >> abandoning 32-bit soon. To fix this error, most likely the edits of >> Makefile are needed, but sadly looks like my skills are not enough to >> fix it (spent the whole day without a success) ... > > > Look at the xcompile script. It seems to not detect your assembler > correctly. > > Your xcompile output should look like this: > > ~/git/filo/ > sh util/xcompile/xcompile > # x86 TARCH_SEARCH= ..../git/filo/util/crossgcc/xgcc/bin/i386-elf- > i386-elf- ..../git/filo/util/crossgcc/xgcc/bin/i386-eabi- i386-eabi- > ..../git/filo/util/crossgcc/xgcc/bin/x86_64-elf- x86_64-elf- > ..../git/filo/util/crossgcc/xgcc/bin/x86_64-eabi- x86_64-eabi- > # elf32-i386 toolchain (i386-elf-gcc) > CC_i386:=i386-elf-gcc -Wno-unused-but-set-variable -Wa,--divide > -fno-stack-protector -Wl,--build-id=none -fuse-ld=bfd -march=i686 > AS_i386:=i386-elf-as > LD_i386:=i386-elf-ld.bfd > NM_i386:=i386-elf-nm > OBJCOPY_i386:=i386-elf-objcopy > OBJDUMP_i386:=i386-elf-objdump > READELF_i386:=i386-elf-readelf > STRIP_i386:=i386-elf-strip > AR_i386:=i386-elf-ar > > # arm TARCH_SEARCH= ..../git/filo/util/crossgcc/xgcc/bin/armv7a-elf- > armv7a-elf- ..../git/filo/util/crossgcc/xgcc/bin/armv7a-eabi- armv7a-eabi- > Warning: no suitable GCC for arm. > IASL:=iasl > > # native toolchain > HOSTCC:=gcc > > > >> >> %%% 2nd problem: There are only three "tested" SATA controllers in >> FILO built-in "approved" list - and FILO does not even try to >> initialize the not-listed controllers, despite that the attempt could >> have been successful if tried! By default, FILO just outputs "ahci: >> Not using untested SATA controller" message, without any option for a >> user to try forcing its usage... The only currently available >> workaround for this is to manually edit >> *./coreboot/payloads/libpayload/drivers/storage/ahci.c * and remove >> two " #if >> IS_ENABLED(CONFIG_LP_STORAGE_AHCI_ONLY_TESTED) ... #endif " parts, >> > > Just disable CONFIG_LP_STORAGE_AHCI_ONLY_TESTED in your libpayload config. > > >> >> %%% 3rd problem: while trying to access hard drive with commands like >> filo> kernel hda:/vmlinuz I am getting the following errors: >> >> Disk read error dev=1 drive=0 sector=0 >> Disk read error dev=1 drive=0 sector=2 >> Disk read error dev=1 drive=0 sector=2 >> Disk read error dev=1 drive=0 sector=128 >> Disk read error dev=1 drive=0 sector=16 >> Disk read error dev=1 drive=0 sector=64 >> Disk read error dev=1 drive=0 sector=0 >> Disk read error dev=1 drive=0 sector=64 >> Disk read error dev=1 drive=0 sector=0 >> Disk read error dev=1 drive=0 sector=0 >> Unknown filesystem type. >> > >> >> Error 15: File not found. >> >> Is there any workaround for this? Or maybe I am using the wrong >> commands? If so, please tell - what are the correct FILO real-hardware >> commands for trying to boot a Linux kernel thats stored on FAT16 >> partition at the beginning of DOS-partitioned MBR hard drive? Or this >> is a problem with my hardware? > > > It seems you would have to look inside of a partition, not just on the raw > disk. e.g. hda1:/... > > >> >> >> Best regards, >> qmastery > > > > Stefan

1 0

Re: [coreboot] FILO 0.6.0 payload bootloader - Bug Reports!
by Stefan Reinauer 13 Jun '17

13 Jun '17

On Tue, Jun 13, 2017 at 10:33 AM Ivan Ivanov <qmastery16(a)gmail.com> wrote: > === If you have some ideas about one or more of FILO problems, please tell > === > > %%% 1st problem - FILO is impossible to build on the modern x86_64 > system (Ubuntu 16.04.2 LTS with gcc 5.4.0) : > ... > CC build/x86/context.o > AS build/x86/switch.S.o > /bin/sh: 1: --32: not found > Makefile:177: error while executing receipt for target > «/home/owner/filo/build/x86/switch.S.o» > make: *** [/home/owner/filo/build/x86/switch.S.o] Error 127 > > No matter what crosscompiling stuff I am trying or what edits I do to > Makefile - it always fails with this error. However it compiles fine > at the 32-bit version of the same OS with the same versions of > packages except for a different architecture > > FILO is probably the only payload which has this problem - and this is > indeed a major problem, because all the major Linux distributions are > abandoning 32-bit soon. To fix this error, most likely the edits of > Makefile are needed, but sadly looks like my skills are not enough to > fix it (spent the whole day without a success) ... > Look at the xcompile script. It seems to not detect your assembler correctly. Your xcompile output should look like this: ~/git/filo/ > sh util/xcompile/xcompile # x86 TARCH_SEARCH= ..../git/filo/util/crossgcc/xgcc/bin/i386-elf- i386-elf- ..../git/filo/util/crossgcc/xgcc/bin/i386-eabi- i386-eabi- ..../git/filo/util/crossgcc/xgcc/bin/x86_64-elf- x86_64-elf- ..../git/filo/util/crossgcc/xgcc/bin/x86_64-eabi- x86_64-eabi- # elf32-i386 toolchain (i386-elf-gcc) CC_i386:=i386-elf-gcc -Wno-unused-but-set-variable -Wa,--divide -fno-stack-protector -Wl,--build-id=none -fuse-ld=bfd -march=i686 AS_i386:=i386-elf-as LD_i386:=i386-elf-ld.bfd NM_i386:=i386-elf-nm OBJCOPY_i386:=i386-elf-objcopy OBJDUMP_i386:=i386-elf-objdump READELF_i386:=i386-elf-readelf STRIP_i386:=i386-elf-strip AR_i386:=i386-elf-ar # arm TARCH_SEARCH= ..../git/filo/util/crossgcc/xgcc/bin/armv7a-elf- armv7a-elf- ..../git/filo/util/crossgcc/xgcc/bin/armv7a-eabi- armv7a-eabi- Warning: no suitable GCC for arm. IASL:=iasl # native toolchain HOSTCC:=gcc > %%% 2nd problem: There are only three "tested" SATA controllers in > FILO built-in "approved" list - and FILO does not even try to > initialize the not-listed controllers, despite that the attempt could > have been successful if tried! By default, FILO just outputs "ahci: > Not using untested SATA controller" message, without any option for a > user to try forcing its usage... The only currently available > workaround for this is to manually edit > *./coreboot/payloads/libpayload/drivers/storage/ahci.c * and remove > two " #if > IS_ENABLED(CONFIG_LP_STORAGE_AHCI_ONLY_TESTED) ... #endif " parts, > > Just disable CONFIG_LP_STORAGE_AHCI_ONLY_TESTED in your libpayload config. > %%% 3rd problem: while trying to access hard drive with commands like > filo> kernel hda:/vmlinuz I am getting the following errors: > > Disk read error dev=1 drive=0 sector=0 > Disk read error dev=1 drive=0 sector=2 > Disk read error dev=1 drive=0 sector=2 > Disk read error dev=1 drive=0 sector=128 > Disk read error dev=1 drive=0 sector=16 > Disk read error dev=1 drive=0 sector=64 > Disk read error dev=1 drive=0 sector=0 > Disk read error dev=1 drive=0 sector=64 > Disk read error dev=1 drive=0 sector=0 > Disk read error dev=1 drive=0 sector=0 > Unknown filesystem type. > > > Error 15: File not found. > > Is there any workaround for this? Or maybe I am using the wrong > commands? If so, please tell - what are the correct FILO real-hardware > commands for trying to boot a Linux kernel thats stored on FAT16 > partition at the beginning of DOS-partitioned MBR hard drive? Or this > is a problem with my hardware? > It seems you would have to look inside of a partition, not just on the raw disk. e.g. hda1:/... > > Best regards, > qmastery > Stefan

1 0

FILO 0.6.0 payload bootloader - Bug Reports!
by Ivan Ivanov 13 Jun '17

13 Jun '17

=== If you have some ideas about one or more of FILO problems, please tell === %%% 1st problem - FILO is impossible to build on the modern x86_64 system (Ubuntu 16.04.2 LTS with gcc 5.4.0) : ... CC build/x86/context.o AS build/x86/switch.S.o /bin/sh: 1: --32: not found Makefile:177: error while executing receipt for target «/home/owner/filo/build/x86/switch.S.o» make: *** [/home/owner/filo/build/x86/switch.S.o] Error 127 No matter what crosscompiling stuff I am trying or what edits I do to Makefile - it always fails with this error. However it compiles fine at the 32-bit version of the same OS with the same versions of packages except for a different architecture FILO is probably the only payload which has this problem - and this is indeed a major problem, because all the major Linux distributions are abandoning 32-bit soon. To fix this error, most likely the edits of Makefile are needed, but sadly looks like my skills are not enough to fix it (spent the whole day without a success) ... %%% 2nd problem: There are only three "tested" SATA controllers in FILO built-in "approved" list - and FILO does not even try to initialize the not-listed controllers, despite that the attempt could have been successful if tried! By default, FILO just outputs "ahci: Not using untested SATA controller" message, without any option for a user to try forcing its usage... The only currently available workaround for this is to manually edit *./coreboot/payloads/libpayload/drivers/storage/ahci.c * and remove two " #if IS_ENABLED(CONFIG_LP_STORAGE_AHCI_ONLY_TESTED) ... #endif " parts, %%% 3rd problem: while trying to access hard drive with commands like filo> kernel hda:/vmlinuz I am getting the following errors: Disk read error dev=1 drive=0 sector=0 Disk read error dev=1 drive=0 sector=2 Disk read error dev=1 drive=0 sector=2 Disk read error dev=1 drive=0 sector=128 Disk read error dev=1 drive=0 sector=16 Disk read error dev=1 drive=0 sector=64 Disk read error dev=1 drive=0 sector=0 Disk read error dev=1 drive=0 sector=64 Disk read error dev=1 drive=0 sector=0 Disk read error dev=1 drive=0 sector=0 Unknown filesystem type. Error 15: File not found. Is there any workaround for this? Or maybe I am using the wrong commands? If so, please tell - what are the correct FILO real-hardware commands for trying to boot a Linux kernel thats stored on FAT16 partition at the beginning of DOS-partitioned MBR hard drive? Or this is a problem with my hardware? Best regards, qmastery

1 0

How to give control to bootable USB
by Dhanasekar Jaganathan 13 Jun '17

13 Jun '17

Hi All, I am trying to install ONIE from USB which has ONIE installer. Actually, I am using GRUB2 as a payload. If Coreboot display list of bootable device,I can select USB which will install a OS in the hard disk. As I understood that Coreboot won't display list of available bootable device (not like vendor bios).I don't know how to give control to bootable USB or boot a bootable USB by coreboot. Can you please help me on this?. Thanks, Dhanasekar

1 0

SPI Flash debug console
by Youness Alaoui 13 Jun '17

13 Jun '17

Hi everyone, I mentioned this during my presentation at the coreboot conference last week, and I was waiting for it to be merged before I announced it on the mailing list. For those of you working on recent hardware (this was tested on skylake only, for broadwell to work, we need to add the spi controller to romstage and convert it to use CAR_GLOBAL, I don't know about other archs), if you don't have a debug header, or if you don't want to go through the trouble of soldering on UART pads or you just don't have any easy access to the debug console, then you can enable the "SPI Flash console output" option in the Console menu. It will automatically add an area to the FMAP which will contain your console log. After you turn on the machine, you can dump the SPI flash and use cbfstool to get the full console log : cbfstool coreboot.rom read -r CONSOLE -f console.log The console log will contain all stages including the bootblock and romstage, so it's useful to debug memory init issues. Since most of us debugging coreboot on new mainboards will already have our external SPI flasher hooked up, we can just read the rom before writing a new one to it and get the log at the same time. Note that the console log will not be reset on poweroff/reboot, it will continue to grow until the whole area is full, at which point it will stop writing anything to the flash. This is to avoid excessive SPI writes in case you forget to disable the option once you get the machine booting. That's it, I hope it's useful to someone else! Thanks to Matt DeVillier and Aaron Durbin for helping debug/test/review the implementation. Youness.

1 0

FYI - KGPE-D16's are $30 off on newegg with a coupon code
by Taiidan＠gmx.com 13 Jun '17

13 Jun '17

$30 off the usual $415 is nice if anyone is considering getting one. The open box one for $311 probably doesn't have a warranty, so ask asus first by email if you want to buy it open box. "ASUCENT58FF6"

1 0

ASUS KFSN4-DRE Automated Test Failure [master]
by Raptor Engineering Automated Coreboot Test Stand 12 Jun '17

12 Jun '17

The ASUS KFSN4-DRE fails verification for branch master as of commit 43dcbfd85581de4f173953282a4917c1ee9a5922 The following tests failed: VIDEO_FAILURE Commits since last successful test: 43dcbfd soc/braswell: fix ACPI table by recollecting TOLM debb785 purism/librem13v2: Update PCI config 0ff3b73 purism/librem13v2: Don't disable PM timer 9d8cd50 purism/librem13v2: Enable SATA, disable eMMC support 6b8570d purism/librem13v2: Add microcode values in Kconfig <24 commits skipped> 2e7f6cc fsp/gop: Add running the GOP to the choice of gfx init d4ebeaf device/Kconfig: Put gfx init methods into a `choice` 26ce9af device/Kconfig: Introduce MAINBOARD_FORCE_NATIVE_VGA_INIT eb881d4 3rdparty/libgfxinit: Update submodule pointer 7b79a33 3rdparty/libhwbase: Update submodule pointer See attached log for details This message was automatically generated from Raptor Engineering's ASUS KFSN4-DRE test stand Want to test on your own equipment? Check out https://www.raptorengineering.com/content/REACTS/intro.html Raptor Engineering also offers coreboot consulting services! Please visit https://www.raptorengineering.com for more information Please contact Timothy Pearson at Raptor Engineering <tpearson(a)raptorengineering.com> regarding any issues stemming from this notification

3 3

Re: [coreboot] Where to buy the KCMA-D8? *brand new*
by Timothy Pearson 12 Jun '17

12 Jun '17

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 06/11/2017 01:09 PM, Johnysecured88 wrote: > The problem is there are no heavy duty apps for the power arch. > Photoshop, Premiere, All Adobe apps, all Autocad/3ds max, the list goes > on an on. Respectfully, if you are using those applications, you have far larger issues to worry about than whether the underlying system can be owner controlled -- you have zero control over the application layer and (probably) the kernel and firmware due to the increasing DRM requirements for those applications. That being said, as POWER systems become more widespread I expect ports of big name software to become available; at least software that already had a Linux port. For others, the best course of action is really to somehow get development of the competing open source solution off the ground and up to feature parity with the commercial offering(s) -- by the time you get a vendor's attention with a multi-million dollar proposition, you could just directly fund development of one of the open source packages and bring it up to a high degree of polish. I myself am building an opteron server build but I also plan > on taking you up on the upcoming offering. > > The question is, what options are there for running x86 on power9? If > there were a good performing emulation layer it would be great. Ive seen > the qemu demo and it doesnt seem to be on par with normal > virtualizations. Ive heard of hardware assisted emulation but I dont > believe power9 chips will have that? POWER has had hardware virtualization extensions since at *least* POWER7, and IIRC significantly before that. However, they help POWER run on POWER, and do not directly help x86 run on POWER. The biggest issue with QEMU cross-arch emulation for heavy-duty apps is really the fact that there is no direct mapping of vector instructions. If someone could invest the $$$ needed to make that happen, x86 apps could run with only a several time slowdown versus the hundredfold or more slowdown due to guest vector instructions being serialised on the host platform. There are a few demos from some Chinese researchers exploring this idea (x86-->ARM), and the results are very impressive. Of course, if you start relying on this for anything other than academic purposes you *might* run into the same legal problem that prevents the manufacture of non-Intel and non-AMD x86 chips -- you'd be using the patented, copyrighted x86 instruction set without the express permission of Intel. The reason I say "might" is that if your x86 apps are old enough, or support an old enough version of the x86 instruction set, you might be able to use a modified version of QEMU that avoids any patent infringement and still have your x86 application(s) run. - -- Timothy Pearson Raptor Engineering +1 (415) 727-8645 (direct line) +1 (512) 690-0200 (switchboard) https://www.raptorengineering.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJZPsEwAAoJEK+E3vEXDOFb8WcH/RjCqCKzS0sfeXMih0FdIQxa e6bAoX+w1aNuFE7qsq6MMhLHSKjKGaPw/MOqc9HB9/+aFbm5b8v900MtvibDw8Tb Kn7IUNntxkLBNEt79/FiOtOHGEp6YRa83gbUOohORRun/S6bhav6OkBph+Dxl7BQ Y9wN8gDy5XDaGlxY6aUlDjHtqO2N1skf96460OzqkoOXYXtTID8GZQQ2bho59iv9 NVZvSE0xs3nt7yk594EfRHIgTA1EVHIBA5TO+hwnUqyXRHsQWWPqVpwn+Ph6SoSJ HsS7wz8banKvQFE/eh0eBM8FiAj2ZBdAgbquYP4wX1285BbhPNp2OG+X3DgLECg= =pc+h -----END PGP SIGNATURE-----

1 0

riscv: How to implement configstring
by 王翔 12 Jun '17

12 Jun '17

I try to boot linux use coreboot. But I get some error. -------------------------------------------------------------------------------- Jumping to boot code at 0000000090000000(0000000000000000) CPU0: stack: 0000000080800000 - 0000000080801000, lowest used address 0000000080800004, stack used: 4092 bytes Config string: '' We don't have virtual memory... OK, let's go Got timer interrupt but found no timer. -------------------------------------------------------------------------------- This is due to the inability to get configstring. -------------------------------------------------------------------------------- const char *configstring(void) { uint32_t addr = *(uint32_t *)CONFIG_RISCV_CONFIGSTRING; return (const char *)(uintptr_t)addr; } -------------------------------------------------------------------------------- The configstring implement by spike or other SOC? If this is done through coreboot, maybe a global variable is more appropriate. This avoids modifying the link script. ------------------ 王翔安全研究员广州市腾御安信息科技有限公司广州市天河区珠江新城华穗路406号保利克洛维二期中景A座1020-1024

2 1

ECC'17 Call for papers is out now !
by Zaolin 12 Jun '17

12 Jun '17

All information about the CFP can be found via https://ecc2017.coreboot.org/speakers Best Regards, Philipp **

1 0

← Newer
1
2
3
4
5
6
7
8
9
...
16
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot June 2017