Hi
I am trying to compile coreboot cbfstool on Arch where gcc 5.1 is used. And
I see following compilation error. I wonder if it is coreboot or gcc issue.
==> Starting build()...
make: Entering directory
'/home/anatol/sources/archpackages/coreboot-utils-git/src/coreboot/util/cbfstool'
mkdir -p ./
cc -D_FORTIFY_SOURCE=2 -D_DEFAULT_SOURCE -D_POSIX_C_SOURCE=200809L
-Iflashmap -march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
--param=ssp-buffer-size=4 -g3 -std=c99 -Werror -Wall -Wextra -Wcast-qual
-Wmissing-prototypes -Wredundant-decls -Wshadow -Wstrict-prototypes
-Wwrite-strings -c -o rmodule.o rmodule.c
rmodule.c: In function ‘rmodule_create’:
rmodule.c:286:29: error: ‘phdr’ may be used uninitialized in this function
[-Werror=maybe-uninitialized]
(phdr->p_vaddr + phdr->p_memsz))) {
^
rmodule.c:203:14: note: ‘phdr’ was declared here
Elf64_Phdr *phdr;
^
cc1: all warnings being treated as errors
Makefile:55: recipe for target 'rmodule.o' failed
make: *** [rmodule.o] Error 1
make: Leaving directory
'/home/anatol/sources/archpackages/coreboot-utils-git/src/coreboot/util/cbfstool'
==> ERROR: A failure occurred in build().
Hi there,
I've read this thread
http://www.coreboot.org/pipermail/coreboot/2014-September/078664.html
started by John Lewis and followed by Aaron Durbin; I'd like to know
what is the current status.
As I understand it would be needed to do some wiring and use SPI to make
proficient tests?
Kind regards,
--
Giuseppe
Dear Michael,
Am Donnerstag, den 28.05.2015, 02:39 +0200 schrieb Michael Gerlach:
> I've done that for revision I used and latest HEAD for both, x201 and
> x230..
Thank you very much!
commit d46ebfbac6ad8bf3a38639c00f6874ebf4c563d5
Author: Michael Gerlach <n3ph(a)terminal21.de>
Date: Wed May 27 03:02:55 2015 +0200
lenovo/x201/4.0-9799-g075739e/2015-05-27T23:59:53Z
commit b32b539b80921c85c54d89a069c661471cb4e343
Author: Michael Gerlach <n3ph(a)terminal21.de>
Date: Thu May 28 01:47:59 2015 +0200
lenovo/x230/4.0-9799-g7b399b7/2015-05-27T23:38:30Z
commit b48d383f87160b47db3251ccfb37ea2eb5d798c3
Author: Michael Gerlach <n3ph(a)terminal21.de>
Date: Thu May 28 01:36:57 2015 +0200
lenovo/x230/4.0-9737-gf4f43f2/2015-05-27T23:35:38Z
Unfortunately, I’m unable to locate the commits you used in the upstream
repository.
$ git show f4f43f2
fatal: ambiguous argument 'f4f43f2': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
$ git show 7b399b7
fatal: ambiguous argument '7b399b7': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
$ git show 075739e
fatal: ambiguous argument '075739e': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
What commits do you have on top? Could you please upload results from
commit, present in the upstream repository.
Thanks,
Paul
PS: Looking at your timings, you could disable the PS/2 controller
initialization as it times out taking over 500 ms.
$ grep DRIVERS_PS2_KEYBOARD lenovo/x201/4.0-9799-g075739e/2015-05-27T23:59:53Z/config.txt
CONFIG_DRIVERS_PS2_KEYBOARD=y
$ more lenovo/x201/4.0-9799-g075739e/2015-05-27T23:59:53Z/coreboot_timestamps.txt
[…]
60:device initialization 3,055,712
(576)
70:device setup done 3,657,942 (602,229)
[…]
Most payloads take care of this anyway.
Hi all!
Long time since i started this topic!
As Zaolin mentioned quite some posts earlier UEFITool is the way to go
to get a working vbios option rom.
I got exactly the same file as zaolin attached in the post before.. And
this works wonderful...
For debug and documentation reasons i will attach the working config,
vgabios, pxe rom image (with disabled BANNER_TIMEOUT), the final cbmem
boot log, the old vgabios which i've dumped via /sys/devices and the
smaller one which i got from /proc/iomem...
Big thx to all of you for taking time to point me in the right
direction... And sorry for the noise ;)
best regards,
n3ph
On 05/27/15 17:46, Zaolin wrote:
> Hi Michael,
>
> again please use the UEFI Tool. Your VGA BIOS contains self modifying
> code and
> that's why the extraction inside the Linux does not work!
> I attached the Intel VGA BIOS for the X230 as reference.
>
> Regards Zaolin
>> Since SeaBios seems to be bothered about the checksum of the oprom i
>> tried to disable the checksum_check via:
>>
>> ./build/cbfstool build/coreboot.rom add-int -i 0 -n
>> etc/optionroms-checksum
>>
>> But it seems like there is sth. wrong with that vbios.. Multi-coloured
>> stripes and strange distortions until kernel boots...
>>
>> I guess i start using UEFITool to re-extract it...
>>
>>
>> best regards,
>>
>> n3ph
>>
>>
>> On 05/27/15 16:47, Michael Gerlach wrote:
>> > Here we go...
>>
>> > I guess cbmem.log should be enough?
>>
>> > Attached one boot with CONFIG_MAINBOARD_DO_NATIVE_VGA_INIT=y set
>> > and one with CONFIG_VGA_ROM_RUN=y and CONFIG_S3_VGA_ROM_RUN=y..
>>
>> > MAINBOARD_DO_NATIVE_VGA_INIT does nothing - display is initialzed
>> > as recently as kernel is already loaded and display driver starts
>> > working.
>>
>> > VGA_ROM_RUN at least corectly initialize the display, but - as
>> > already mentioned - no output from coreboot nor seabios is
>> > displayed - just a white blinking cursor until kernel gets loaded..
>> > I guess i have no timeout in grub2 - so this might be the reason
>> > why i also see no output from grub..
>>
>>
>>
>> > best regards,
>>
>>
>> > n3ph
>>
>>
>>
>>
>>
>>
>>
>
>
--
Bitte benutzt GPG: http://de.wikipedia.org/wiki/GNU_Privacy_Guard
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Patrick!
Uhm - I do not explicitly compressed it. I just added it to config..
Extracted it via
echo 1 > /sys/devices/pci0000\:00/0000\:00\:02.0/rom
cp /sys/devices/pci0000\:00/0000\:00\:02.0/rom vgabios.bin
How to check if it's compressed?
Best regards,
n3ph
On 05/23/15 03:22, Patrick Georgi wrote:
> 2015-05-23 1:06 GMT+02:00 Michael Gerlach <n3ph(a)terminal21.de>:
>> GET_VBIOS: 7b46 3714 8b a2 e9
>
>> printk(BIOS_DEBUG, "GET_VBIOS: %x %x %x %x %x\n",
>> oprom->signature, pcir->vendor, pcir->classcode[0],
>> pcir->classcode[1], pcir->classcode[2]);
>>
>> But Signature should be 0x55aa:
> Just to double check: did you add the vgabios with or without
> compression? coreboot only supports uncompressed vgabios images
> (while seabios allows them compressed as well, if the name
> matches)
>
>
> Patrick
>
- --
Bitte benutzt GPG: http://de.wikipedia.org/wiki/GNU_Privacy_Guard
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJVX+XmAAoJEE1l5S41evqaQRcH/2fBtgPODZzmDNHX03Vi8UJY
bRXIg4RwGo2lbfaepxfJuyi0EH5Rv5QAOCMBB6Eh7c6Tovf+wa4kbZivc+4Qn/k2
zBb/qvURAmthHQzqVuRUBL5zI5SRL/KbcGX5l7jkjx+d1KVLlfZR+rT4KHHOVJLF
FccnwT0P2OrSeyLMV31pCqkbK5Nf9lVsIRAJoQtcWwlaClTiaIUiji0TzJwjoJ5C
JibGCNCRJ4yjgCTty4EwmRxrUYvBEjFg87g33HhE61Ya73Dh4xcetEC2y/stdnMs
U4LV/Kzb/oDfOdmy6Em0+XnDAFTaSxkqTqU2V/zBGsZACNwj4fce4QrNi35DJpE=
=DNks
-----END PGP SIGNATURE-----
In the last months there was lots of activity in the coreboot
repository due to upstreaming the work that was done in Chrome OS’
branch. We’re happy to announce that both code bases are again
relatively close to each other.
In the last 7 months, about 1500 commits that landed in coreboot
originated in Chrome OS’ repository (of about 2600 total). Those came
from 20 domains, which represent pretty much every part of the
coreboot community: well known private and commercial coreboot
contributors, but also BIOS and silicon developers as well as device
manufacturers.
As a result, upstream benefits from lots of new features and hardware
support that was introduced during Chrome OS development, some of
which warrant a shout out:
First, new hardware support: There’s MIPS support, and on the ARM side
we now run on SoCs by Broadcom, Marvell, Qualcomm, and RockChip.
In terms of infrastructure, the biggest single item that came up
during upstreaming is probably a safe method to declare the memory map
on devices. Compared to x86, most architectures that prospered in
embedded applications have a more complicated view on memory, so more
care is required there.
Looking at files like
src/soc/nvidia/tegra132/include/soc/memlayout.ld, it becomes clear
what kind of memory is available for which purpose on that SoC.
In addition to that, there are efforts to make Chrome OS’ verified
boot available as an option in upstream coreboot, and also to update
the flash image format to allow for safer incremental updates.
One thing to note is that significant contributions that went into the
tree recently were written with active support by Broadcom,
Imagination Technologies, Intel, Marvell, Nvidia, Qualcomm, and
RockChip. Welcome to coreboot!
In the future, Chrome OS will move over to a new branch point from
upstream, and work on strategies to avoid diverging for two long years
again. Instead, we’re looking for ways to keep the trees closer while
also avoiding flooding the coreboot.org developer base with hundreds
of patches. More on that as it is implemented.
Regards,
Patrick
--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Christine Elizabeth Flores
Greetings,
I a attempting to build coreboot with grub2 payload. The host runs fedora
linux.
I used the Kconfig menu to select GRUB2 as coreboot payload and run make
crossgcc succcesfully.. On runing the next etep -make grub2 from git is
downloaded but the build fails on the ./configure of the downloaded
grub2 as follows:-
###############
configure error qemu powerpc-ieee1275 coreboot and longson ports need
unifonts,
###############
I checked the hosts' installation and I have unicode fonts installed. I
changed host with the same fesult.
Help would be appreciated
sincerely
Sibu
incidently
when running ./configure --with-platform=coreboot. grub-2.02beta2 failed
also though the older Grub-2.00 built succesfully. I am unclear if the
latter is too old for using as coreboot payload in the corrent instance and
if not how to go abot embedding it in the downloaded coreboot distribution
from the current git repo.
Greetings,
I a attempting to build coreboot with grub2 payload. The host runs fedora
linux.
I used the Kconfig menu to select GRUB2 as coreboot payload and run make
crossgcc succcesfully.. On runing the next etep -make grub2 from git is
downloaded but the build fails on the ./configure of the downloaded
grub2 as follows:-
###############
configure error qemu powerpc-ieee1275 coreboot and longson ports need
unifonts,
###############
I checked the hosts' installation and I have unicode fonts installed. I
changed host with the same fesult.
Help would be appreciated
sincerely
Sibu
incidently
when running ./configure --with-platform=coreboot. grub-2.02beta2 failed
also though the older Grub-2.00 built succesfully. I am unclear if the
latter is too old for using as coreboot payload in the corrent instance and
if not how to go abot embedding it in the downloaded coreboot distribution
from the current git repo.
