Rudolf Marek :
Do you own also Trinity CPU?
No only a Richland CPU. But I can do the tests you want to send you the
results.
maybe we can do some #ifdef config option which would enable this hack
via
configuration option.
I test this hack since several days and I am very satisfied, I had no
Hi all,
I checked the BKDG on AMD website and there is not much register differences
between those CPUs:
42300 Rev 3.10 - June 04, 2013 BKDG for AMD Family 15h Models 10h-1Fh
Processors:
1.5.4 Changes For Revision RL-A1
• Changes that may result in BIOS modifications.
• Added 2.5.9.1
Scott wrote:
diff --git
a/src/vendorcode/amd/agesa/f15tn/Proc/CPU/Family/0x15/TN/F15TnLogicalIdTables.c
b/src/vendorcode/amd/agesa/f15tn/Proc/CPU/Family/0x15/TN/F15TnLogicalIdTables.c
index 8157b57..bfcaa9a 100644
---
David wrote:
It would still be helpful if you can post the details for this stick.
1 Corsair CMV4GX3M1A1333C9 (4Gb 1,5 Volt)
http://www.ldlc.com/fiche/PB00104214.html
You may also want to post the output of git diff for others who may want to
try Richland on the F2A85-M.
Ok, no problem :)
David wrote:
With just 1 stick in the A1 slot, please post a pastebin of the console
output.
Perfect! It is perfectly detailed, the cpu is not recognized:
http://pastebin.com/2Lbew82b
Thanks, best regards,
--
coreboot mailing list: coreboot@coreboot.org
On Wed, Feb 26, 2014 at 12:54 PM, HacKurx hack...@gmail.com wrote:
David wrote:
With just 1 stick in the A1 slot, please post a pastebin of the console
output.
Perfect! It is perfectly detailed, the cpu is not recognized:
http://pastebin.com/2Lbew82b
Great, this is another big step in
HacKurx [mailto:hack...@gmail.com] wrote:
] David wrote:
] With just 1 stick in the A1 slot, please post a pastebin of the console
] output.
]
]Perfect! It is perfectly detailed, the cpu is not recognized:
]http://pastebin.com/2Lbew82b
you could try adding your cupid to the list in
Scott wrote:
The cupid is not found because trinity support is included but
richland support is needed. I do not know if forcing the trinity
code to run on richland will work, but you could try it. One way
to try it is to change the == to != on line 255 of file
On Tue, Feb 25, 2014 at 1:39 PM, HacKurx hack...@gmail.com wrote:
Scott wrote:
The cupid is not found because trinity support is included but
richland support is needed. I do not know if forcing the trinity
code to run on richland will work, but you could try it. One way
to try it is
HacKurx [mailto:hack...@gmail.com] wrote:
]Thank you for adding this great feature that I hope will be added by
]default in Kconfig.
]Unfortunately, this option has no more help me to solve my problem
]with the richland architecture.
Your board is probably crashing at line 252 of file:
Peter wrote:
You might want to test my patch which exposes the IDS options in Kconfig:
Thank you for adding this great feature that I hope will be added by
default in Kconfig.
Unfortunately, this option has no more help me to solve my problem
with the richland architecture.
With no response
Peter wrote:
You might want to test my patch which exposes the IDS options in Kconfig:
Ok thank you I'll test it soon (I'm in the middle of moving).
Idwer wrote:
I'll add it to the board's wiki page.
Perfect thank you. I am in contact with a responsable from AMD I hope
get the Richland AGESA
Very odd. I had hoped it was something easy. I wonder what differs for
Richland (as Idwer said) so that it doesn't work. My best understanding of
Richland (A10-6800K) is that the memory controller has higher rated speeds
but should work with Trinity AGESA code, since the Trinity AGESA code
Thank you for this information. Please indicate the compatible
processor on the motherboard page.
See this list:
http://en.wikipedia.org/wiki/List_of_AMD_Accelerated_Processing_Unit_microprocessors#Virgo_-_.22Trinity.22_.282012.2C_32_nm.29
I'll add it to the board's wiki page.
--
coreboot
2014-02-04 22:36 GMT+01:00 Rudolf Marek r.ma...@assembler.cz:
Perfect thank you for this whole procedure. This is what I obtain:
My rom (with my vga bios):
coreboot-4.0-5394-gba6b07e Thu Jan 30 19:48:58 CET 2014 starting...
BSP Family_Model: 00610f31
cpu_init_detectedx =
On Mon, Feb 10, 2014 at 11:59 AM, David Hubbard
david.c.hubbard+coreb...@gmail.com wrote:
On Mon, Feb 10, 2014 at 12:16 AM, HacKurx hack...@gmail.com wrote:
Please double check IDSOPT_IDS_ENABLED.
I have first-hand experience with Rudolf's suggestion to use that
#define, I
have an
David Hubbard wrote:
It seems the problem is getting a good debug log with IDSOPT_IDS_ENABLED,
You might want to test my patch which exposes the IDS options in
Kconfig:
git fetch http://review.coreboot.org/coreboot refs/changes/61/5161/1 \
git checkout FETCH_HEAD
This adds an AGESA menu
Please double check IDSOPT_IDS_ENABLED.
I have first-hand experience with Rudolf's suggestion to use that #define, I
have an F2A85-M as well. With IDSOPT_IDS_ENABLED, the serial output is
significantly longer. I suspect the build system does not catch the change
since it's not in menuconfig.
On Thu, Feb 6, 2014 at 12:28 AM, HacKurx hack...@gmail.com wrote:
OK. Please can you enable AGESA debug stuff. It should produce more
output.
You can do that by uncommenting #define IDSOPT_IDS_ENABLED in mainboard
directory OptionsIds.h file.
We dont have a menuconfig for that yet.
OK. Please can you enable AGESA debug stuff. It should produce more
output.
You can do that by uncommenting #define IDSOPT_IDS_ENABLED in mainboard
directory OptionsIds.h file.
We dont have a menuconfig for that yet.
I made it. There is in my file:
grep #define IDSOPT_IDS_ENABLED
Perfect thank you for this whole procedure. This is what I obtain:
My rom (with my vga bios):
coreboot-4.0-5394-gba6b07e Thu Jan 30 19:48:58 CET 2014 starting...
BSP Family_Model: 00610f31
cpu_init_detectedx =
agesawrapper_amdinitreset
OK. Please can you enable AGESA debug stuff. It
2014-02-01 Rudolf Marek r.ma...@assembler.cz:
You should see some output of coreboot. Capture it via (ctrl a l shortcut in
minicom) to a file and send it back to list.
If is something unclear, please let us know. You need to make it up to next
Friday. I will be then long time AFK and I will
On 31.1.2014 13:53, HacKurx wrote:
No way. You will need to use serial port. Just plug the header to mainboard and
use some USB 2 serial from other computer (together with null
modem cable) if you need more info please let me know.
Do you have any links, diagram or picture for this method?
No way. You will need to use serial port. Just plug the header to mainboard
and use some USB 2 serial from other computer (together with null
modem cable) if you need more info please let me know.
Do you have any links, diagram or picture for this method? Thanks
It looks some people can send
Is it Richland or Trinity? Seems it is Richland. I haven't tried with
Richland yet.
Yes indeed it's Richland.
It would be helpful if you could include log from serial console. Maybe you
hit some other problem.
How without serial port?
You can also try to put memory only to blue slots.
On 30.1.2014 11:03, HacKurx wrote:
Is it Richland or Trinity? Seems it is Richland. I haven't tried with Richland
yet.
Yes indeed it's Richland.
It would be helpful if you could include log from serial console. Maybe you hit
some other problem.
How without serial port?
No way. You will
Hi,
_F2A85-M REV 1.02
_AMD A8-6600K APU (Radeon HD 8570D vga = 1002,990e)
_Corsair Value Select 4 Go DDR3 1333 MHz CL9 (CMV4GX3M1A1333C9)
Is it Richland or Trinity? Seems it is Richland. I haven't tried with Richland
yet.
I proceeded to build a standard coreboot image using seabios as a
27 matches
Mail list logo
