In the spirit of board report coverage, I pulled out the (used, but new to
me) AM1I-A I have and spent a day or two trying to install the latest
coreboot on it.
The board boots fine under the stock bios, and returns to working order if
flashed with my backup, but shows little signs of life with coreboot.
Along the way I extracted and included the vgabios rom, as well as tried
with a nivida card, so I'm pretty sure that's not it.
I tried having it save the console output to flash, but that made the build
Yesterday evening I noticed it was configured by default to use open-source
init (and for some reason the build finishes without error), but as far as
I know that doesn't exist for family 16h. Switching to BinaryPI causes the
build to fail.  3rd party blobs are cloned and enabled.
I'm running an Athlon 5250, or something of that nature, with a couple of
gigs of ram on one dimm. My current .config is .
I have a CompuLab Intense PC that has not been patched for
CVE-2017-8083 (no CloseMnf protection mechanism for write protection
of flash memory regions), which should allow me to install coreboot
without an external programmer according to
So far I have successfully compiled coreboot from master branch, with
binary blobs extracted from stock firmware.
1. The coreboot toolchain is built with command
'make crossgcc-i386 CPUS=$(nproc)' as shown in the tutorial, but my
system is x86-64 so should I have used 'make crossgcc-x64' instead?
2. As I'm not using an external programmer to flash coreboot, is it
correct to run flashrom like this 'flashrom -w coreboot.rom -p
internal'? or do I need to pass more arguments?
3. In my configuration, this option is set by default:
CONFIG_UNLOCK_FLASH_REGIONS=y, just to be sure, this will allow me to
flash all regions, including ME, again without an external programmer
after coreboot is installed?
Sequel of a Turtle RAM issue  I had on fam16h AM1I-A : a pair of
 modules crawls as 1333MHz CL9 on A88XM-E (F2A85-M clone) with
A10-6700. That's despite a really similar pair , just 1600MHz CL9
and in a SO-DIMM shape, runs on its' top 1600MHz CL9 speed at Lenovo
G505S with A10-5750M which is also fam15h. I hoped this Turtle RAM
problem is isolated to fam16h (thought that fam16h AGESA was a bit
immature at its' time of release), but seems it affects fam15h also!
I tried making buildOpts.c of A88XM-E at  as similar as possible to
a successful G505S, considering they are from the same fam15h family
and hoping that my change  will force it running at least on
1600MHz - but didn't help. :( Consider installing those SO-DIMM
modules with a SO-DIMM to DIMM adapter, but not sure it will change
Why AGESA memory training is such a crap on fam15h desktop, while
working fine on fam15h laptop? My clumsy hacking of AGESA wasn't
successful on fam16h AM1I-A - but maybe because I was trying to do
that at the wrong places! So I really need your advice, where exactly
are the critical AGESA source code places I should hack to force that
Thank you very much in advance, wish you a Happy New Year ;-)
 Crucial Ballistix Tactical Series DDR3 1866MHz CL9 (PC3-14900
9-9-9-24) UDIMM 240-Pin modules, part number BLT8G3D1869DT1TX0
 Crucial Ballistix Sport Series DDR3 1600MHz CL9 (PC3L-12800
9-9-9-24) SO-DIMM 204-Pin modules, part number BLS2K8G3N169ES4
Could someone with a Fam16 using integrated graphics test
https://review.coreboot.org/c/coreboot/+/38056 and comment there whether
it worked (still boots and display still shows)?
- don't top post
Mailing list etiquette:
- trim quoted reply to only relevant portions
- when possible, copy and paste text instead of screenshots