Dear coreboot folks, dear Vladimir,
although this is a GRUB problem, I am posting this to the coreboot list
as it is in the GRUB payload and I am not subscribed to the GRUB list.
Currently using GRUB revision 4778 as a payload [1], loading the module
`ahci` I see the following errors (formatted serial output, “garbled”
one at the end) on the AMD SB800 based ASRock E350M1 [2].
grub> set debug=ahci,ata
grub> insmod ahci
disk/ahci.c:291: Requesting AHCI ownership
disk/ahci.c:294: Waiting for BIOS to give up ownership
disk/ahci.c:305: AHCI ownership obtained
disk/ahci.c:311: AHCI is in compat mode. Switching
disk/ahci.c:357: 6 AHCI ports
disk/ahci.c:367: status 0:123
disk/ahci.c:184: found device ahci0 (port 0)
disk/ahci.c:225: couldn't start CR
grub> insmod ata
grub> insmod mdraid
grub> insmod mdraid09
grub> ls
(memdisk)
SeaBIOS has no problems finding the attached ATA drive.
If more information is needed, please tell me what and how I can get it,
and I will try to provide it.
Thanks,
Paul
[1] http://www.coreboot.org/GRUB2
[2] http://www.coreboot.org/ASRock_E350M1
grub> ins set debug=ahci,ata
grub> insom mot d ahci
disk/ahci.c:291: Requesting AHCI ownership
disk/ahci.c:294: Waiting for BIOS to give up ownership
disk/ahci.c:305: AHCI ownership obtained
disk/ahci.c:311: AHCI is in compat mode. Switching
disk/ahci.c:357: 6 AHCI ports
disk/ahci.c:367: status 0:123
disk/ahci.c:184: found device ahci0 (port 0)
disk/ahci.c:225: couldn't start CR
grub> insmod ata
grub> insomd mod mdraid
grub> insmod mdraid09
grub> ls
(memdisk)
Dear Coreboot Folks
http://www.coreboot.org/QEMU
in this site, there are some readymade coreboot payloads , which I thought of using it to see the output.
But when I tried to unzip the file Qemu_coreboot_coreinfo.zip, it throws an error.
I am doing this because i was not able to compile libpayload, as libpayload makes use of coreinfo, I cannot use coreinfo as well.
If you guys can upload a good working image of coreboot+libpayoad+coreinfo, that would be great!!
Regards
Pradish
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
Dear Pradish,
in my last message I asked you *not* to send any HTML messages!
Additionally you did not reply to the list. Please use a decent mail
client which has the option to reply to the list. (As a workaround you
might use the reply to all feature.
Am Mittwoch, den 27.03.2013, 13:08 +0530 schrieb Pradish MP:
[…]
> but i get new errors
>
> pradish@pradish-VirtualBox:~/coreboot/payloads/libpayload$ make install
> build/libpayload-config.h build/config.h differ: byte 93, line 4
> CC libpci/libpci.libpci.o
> AR build/libpci.a
> CC arch/x86/main.libc.o
> CC arch/x86/sysinfo.libc.o
> CC arch/x86/timer.libc.o
> CC arch/x86/coreboot.libc.o
> CC arch/x86/util.libc.o
> CC arch/x86/exec.libc.o
> CC arch/x86/virtual.libc.o
> CC arch/x86/string.libc.o
> CC arch/x86/multiboot.libc.o
> CC crypto/sha1.libc.o
> CC libc/malloc.libc.o
> CC libc/printf.libc.o
> CC libc/console.libc.o
> CC libc/string.libc.o
> In file included from libc/string.c:35:0:
> include/inttypes.h:250:2: error: unknown type name 'intmax_t'
> include/inttypes.h:251:2: error: unknown type name 'intmax_t'
> include/inttypes.h:255:1: error: unknown type name 'intmax_t'
> include/inttypes.h:255:1: warning: parameter names (without types) in function declaration [enabled by default]
> include/inttypes.h:256:1: warning: parameter names (without types) in function declaration [enabled by default]
> include/inttypes.h:257:1: error: unknown type name 'intmax_t'
> include/inttypes.h:258:1: error: unknown type name 'uintmax_t'
> libc/string.c: In function 'strtoul':
> libc/string.c:542:12: error: 'UINT32_MAX' undeclared (first use in this function)
> libc/string.c:542:12: note: each undeclared identifier is reported only once for each function it appears in
> make: *** [build/libc/string.libc.o] Error 1
>
> how to resolve this one?
Thanks to Stefan Reinauer these errors should be fixed with the
following commit.
commit c7b6d7db092cfd925f1fb6333e166a54663310e7
Author: Stefan Reinauer <reinauer(a)chromium.org>
Date: Mon Mar 25 15:03:41 2013 -0700
libpayload: Fix type issues
There were a number of type issues in libpayload that
sneaked in
with 903f8e0.
- size_t and ssize_t were conflicting with gcc builtins
- some stdint types were used in libpayload but not defined
in our stdint.h
[…]
Reviewed-on: http://review.coreboot.org/2903
Please do `git remote update` and `git rebase origin/master` to get the
latest revision and everything should be fine.
[…]
Thanks,
Paul