coreboot May 2014

coreboot@coreboot.org

39 participants
89 discussions

imb-a180 won't boot from single DIMM 0
by Mark C. Mason 28 May '14

28 May '14

Is there a straightforward way to get an IMB-A180 to boot with a single DIMM in slot 0? It boots fine in slot 1. I've looked through the code at length, and thought it configures the dimm, it fails in coreboot/src/vendorcode/amd/agesa/Proc/Mem/Main/KB/mmflowKB.c //---------------------------------------------------- // If there is no dimm on the system, do fatal exit //---------------------------------------------------- if (NBPtr[BSP_DIE].RefPtr->SysLimit == 0) { PutEventLog (AGESA_FATAL, MEM_ERROR_NO_DIMM_FOUND_ON_SYSTEM, 0, 0, 0, 0, &(MemMainPtr->MemPtr->StdHeader)); return AGESA_FATAL; } Even though it has detected and configured the dimm in slot 0. Again, this does work with slot 1. Many thanks, Mark Mason Engineering Design Team

2 1

Re: [coreboot] [ANNOUNCE] SeaBIOS 1.7.5
by Patrick Georgi 28 May '14

28 May '14

Am 28.05.2014 16:36, schrieb WANG FEI: > XHCI support is what I want, currently what's payload have a better XHCI > support? Seabios or U-Boot? There are also FILO and depthcharge (both using the libpayload XHCI driver) Patrick

1 0

AMD A76M chipset?
by Carl-Daniel Hailfinger 28 May '14

28 May '14

Hi, HP and other laptop vendors claim to use an AMD A76M chipset in some of their machines. I have been unable to find any info about (or even confirm the existence of) the A76M on the AMD website or any other reliable source. https://en.wikipedia.org/wiki/Comparison_of_AMD_chipsets is also silent, but the numbers there suggest the A76M might be a Bolton chipset. Does anyone know if there are public docs for the A76M (possibly under another name), and how feasible it is to drive it with current public (or to-be-released) AGESA? Regards, Carl-Daniel -- http://www.hailfinger.org/

5 4

[ANNOUNCE] SeaBIOS 1.7.5
by Kevin O'Connor 28 May '14

28 May '14

The 1.7.5 version of SeaBIOS has now been released. For more information on the release, please see: http://seabios.org/Releases New in this release: * Support for obtaining SMBIOS tables directly from QEMU. * XHCI USB controller fixes for real hardware (now tested on several boards) * SeaVGABIOS improvements * New driver for "coreboot native vga" support * Improved detection of older x86emu versions with incorrect emulation. * Several bug fixes and code cleanups For information on obtaining SeaBIOS, please see: http://seabios.org/Download

3 2

Errors in Memtest86 with 4 or 8GB memory
by Krzysztof Pierwieniecki 27 May '14

27 May '14

I have a problem on Intel DQ77KB board. I have two the same boards and on every board Memtest86 reports a problem at 2990.8MB. That problem occur only if I use 4 or 8GB memory. With 2GB memory everything is OK. What may be causing errors in Test2 "Address test, own address, Parallel" in Memtest86? http://www.memtest86.com/technical.htm Chris

2 1

Is there a proper way to skip a specific PCI device during PCI enumeration
by WANG FEI 27 May '14

27 May '14

Gents, What I'm doing is to avoid PCI enumeration code allocating/setting/configuring resource to a specific PCI device (Bus:Device:Function), is there a mechanism in coreboot to achieve this? I've achieved this by setting this specific PCI device's read_resources to NULL, just wondering what's the best way to get this done. Many thanks, -Fei

1 0

Errors in Memtest86 with 4 or 8GB memory
by Krzysztof Pierwieniecki 27 May '14

27 May '14

This is my coreboot log. Chris

2 1

Errors in Memtest86 with 4 or 8GB memory
by Krzysztof Pierwieniecki 26 May '14

26 May '14

2 1

Timeline for Bayley Bay Support
by Mike Hibbett 26 May '14

26 May '14

Hi all ( but Martin in particular! ) I can see support for Baytrail and Bayley Bay going in at the moment. I'm interested in this board, and was wondering what the timeline for support might be - is there much more to do? And when will we see it? Thanks, Mike.

1 0

coreboot build of seabios payload broken
by Kevin O'Connor 22 May '14

22 May '14

I've received a few reports of people having problems building seabios within the coreboot build system. In my investigation I've uncovered at least two problems: 1 - on my machine, (with CONFIG_ANY_TOOLCHAIN=y) I can't build seabios from corebooat at all because of the LD definition. The .xcompile file gets created with: LD_x86_32:=ld.bfd -b elf32-i386 -melf_i386 and this gets passed to SeaBIOS as: make -C payloads/external/SeaBIOS [...] LD="ld.bfd -b elf32-i386 -melf_i386" unfortunately, the seabios build expects the LD variable to be a program - not the combination of a program and parameters. This breaks the build. (This also seems to happen with AS="as --32".) 2 - others are reporting problems with python3 even on seabios master (when using coreboot's build chain). This is actually a symptom of a much larger issue - for some reason section names are being corrupted by the tool chain. Here's a quick test case: echo 'int Foo __attribute__((section( ".data.varfseg." __FILE__ "." "123" )));' > foo.c ; gcc -c foo.c -o foo.o ; objdump -x foo.o | grep varfseg this should show section names like ".data.varfseg.foo.c.123", but on impacted machines the section names are actually showing up as ".data.varfseg.". This truncation of the section names results in SeaBIOS not being able to weed out unneeded content from the final binary, and it results in the seabios build getting confused on build options. -Kevin

2 1

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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

coreboot May 2014