I've retested and it seems that my errors with memtest86+ 5.01 floppy
happen only if there are any other floppies than this memtest. Errors
are at bfce2c80 ( 3068.1MB ). Although I don't have this error on f15h
board, perhaps need to somehow improve my unofficial multiple_floppies
SeaBIOS patch.
O
I've fixed 45 format-related warnings/errors of IDS_HDT_CONSOLE at AMD
16h vendorcode. Now a coreboot for fam16 could be built successfully
with IDS_HDT_CONSOLE enabled (IDSOPT_IDS_ENABLED TRUE and
IDSOPT_TRACING_ENABLED TRUE at board/OptionsIds.h) even with config
WARNINGS_ARE_ERRORS. Joined error
I have same issue, memtest86+ failed on all fam16 family for me(AM1ML, AMD
devboard and so on) (usually in first 10Mb and near a dedicated video
memory). BTW i'm choose to use last free memtest86 (without plus), it
work's.
вс, 10 нояб. 2019 г. в 21:07, Mike Banon :
> No problem (this log is reall
No problem (this log is really huge for some reason). At the beginning
of it - the most interesting part - I've found that "MemBusFreqLimit :
800" and "MemoryClockSelect : 667". Perhaps I'd try again forcing
either 933 (for 1866, although don't know if possible on this
platform) or 800 (for 1600) a
On Sun, Nov 10, 2019 at 3:52 PM Mike Banon wrote:
>
> Sorry it took me so long: using FT232H and screen Ctrl+A h option,
> finally I got a complete boot log on AM1I-A Fam16h with these IDS
> options enabled. Please could you take a look, to see if it contains
> any hints why this 1866MHz CL9 RAM h
On Fri, Jul 5, 2019 at 5:36 PM Mike Banon wrote:
>
> Thank you for advice. I followed the instructions of this change, and
> after fixing a few compilation errors (had to replace a few %x with
> %llu at printf's) - using the same .config - I got a ROM which is
> unbootable! Maybe because I don't h
Thank you for advice. I followed the instructions of this change, and
after fixing a few compilation errors (had to replace a few %x with
%llu at printf's) - using the same .config - I got a ROM which is
unbootable! Maybe because I don't have AMD HDT Debugger, and it
should've been connected to som
On Wed, Jul 3, 2019 at 8:54 PM Mike Banon wrote:
>
> A pair of 1866MHz CL9 RAM modules* runs only as 1333MHz CL9 on 16h
> AM1I-A with coreboot is installed, but worked faster when a
> proprietary UEFI was installed. To fix this "turtle RAM" coreboot
> problem I tried to play with buildOpts.c -
> h
8 matches
Mail list logo
