Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 problem with him. Indeed, I think we should add it in the F2A85-M menu under a name "Experimental Support for Richand APU." Thanks -- Best regards, hackurx.wordpress.com -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 [Hybrid Boost] • Added D0F0xBC_x1F428[HybridBoostEn] • Other changes • Added D0F0xBC_x1F8EC It is just related to hybridboost enable. The only thing which might really need an update is a SMU firmware. It would be interesting to try with original BIOS if some other SMU firmware is used when trinity or richland CPU is used. Do you own also Trinity CPU? As for the errata, I think I have seen somewhere that the processors share the lists. I wrote just a note to the board wiki page about Richland, maybe we can do some #ifdef config option which would enable this hack via configuration option. We would also need some more sane error handling code in AGESA. I guess we can fix it with some patch. Any takers? Thanks Rudolf -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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
> ---
> 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
> @@ -86,6 +86,12 @@ STATIC CONST CPU_LOGICAL_ID_XLAT ROMDATA
> CpuF15TnLogicalIdAndRevArray[] =
> 0x6101,
> AMD_F15_TN_A1
>},
> +
> + { // HACK: let Richland run Trinity agesa code
> +0x6131,
> +AMD_F15_TN_A1
> + },
> +
>{
> 0x6100,
> 0x0100ull
Perfect! It works, thank you very much!
Coreboot log:
http://pastebin.com/B0Z1bTQu
Diff (I used CROSSGCC 1.23 because CROSSGCC 1.24 can not be compil on
my system - Debian Wheezy amd64) :
http://pastebin.com/nbt0JmqN
My config file :
http://pastebin.com/zJLQPkgX
My CPU seems a little slower but it works :)
It remains only to integrate this into the wiki and coreboot, I know
that I can count on you ;)
>From my side I will continue my tests. Thank you everybody, best regards.
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
HacKurx [mailto:hack...@gmail.com] wrote:
]> 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 :)
]http://pastebin.com/sTFzE5YN
]
]> Scott wrote:
]> you could try adding your cupid to the list
]One more step :)
]http://pastebin.com/kD2zmbua
It looks like the wrong file was modified. That probably causes
Orochi code to be used instead of Trinity as desired. Only change
the one file in the family15tn directory:
diff --git a/src/cpu/amd/agesa/family15tn/model_15_init.c
b/src/cpu/amd/agesa/family15tn/model_15_init.c
index f396201..1dbc064 100644
--- a/src/cpu/amd/agesa/family15tn/model_15_init.c
+++ b/src/cpu/amd/agesa/family15tn/model_15_init.c
@@ -123,6 +123,7 @@ static struct device_operations cpu_dev_ops = {
static struct cpu_device_id cpu_table[] = {
{ X86_VENDOR_AMD, 0x610f00 }, /* TN-A0 */
+ { X86_VENDOR_AMD, 0x610f31 }, /* RL-A1 (HACK) */
{ 0, 0 },
};
Here is an optional change. That first hack that changes == to != is
quite unreadable and confusing. I believe the following is a better
solution. Also remember that running Trinity agesa on Richland is a
hack and hopefully a temporary solution. Possible problems are:
1) desired microcode patch is not available 2) Any Richland errata
workarounds embedded in the agesa code are not present 3) There
might be some differences between Trinity and Richland recommended
register settings.
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
---
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
@@ -86,6 +86,12 @@ STATIC CONST CPU_LOGICAL_ID_XLAT ROMDATA
CpuF15TnLogicalIdAndRevArray[] =
0x6101,
AMD_F15_TN_A1
},
+
+ { // HACK: let Richland run Trinity agesa code
+0x6131,
+AMD_F15_TN_A1
+ },
+
{
0x6100,
0x0100ull
]Thanks,
]
]2014-02-26 23:20 GMT+01:00 Scott Duplichan :
]> 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
]> src/cpu/amd/agesa/family15tn/model_15_init.c:
]>
]> static struct cpu_device_id cpu_table[] = {
]> { X86_VENDOR_AMD, 0x610f00 }, /* TN-A0 */
]> { X86_VENDOR_AMD, 0x610f31 }, /* RL-A1 */
]> { 0, 0 },
]> };
]> Thanks,
]> Scott
]>
]>
]> ]Thanks, best regards,
]
]--
]Best regards,
]
]HacKurx
]www.hackurx.info
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
On Thu, Feb 27, 2014 at 2:53 PM, HacKurx wrote: > > 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 :) > http://pastebin.com/sTFzE5YN > > > Scott wrote: > > you could try adding your cupid to the list > One more step :) > http://pastebin.com/kD2zmbua > Ok, this is actually a step backward. In your previous output ( http://pastebin.com/2Lbew82b) I see "agesawrapper_amdinitpost failed: 4" on line 4296. In this latest output it only gets a little farther and dies at "Fch OEM config in INIT ENV Done". Try doing a full power cycle of the board and see if you get something better. I've seen coreboot die at "Fch OEM config in INIT ENV Done" doing a reboot, but I could fix it with a power cycle. This is really the point where you can start to dig in and try to get Richland working in coreboot. I'm probably of only limited usefulness, but others may have a better idea what needs to happen. Regards, David -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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 :)
http://pastebin.com/sTFzE5YN
> Scott wrote:
> you could try adding your cupid to the list
One more step :)
http://pastebin.com/kD2zmbua
Thanks,
2014-02-26 23:20 GMT+01:00 Scott Duplichan :
> 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
> src/cpu/amd/agesa/family15tn/model_15_init.c:
>
> static struct cpu_device_id cpu_table[] = {
> { X86_VENDOR_AMD, 0x610f00 }, /* TN-A0 */
> { X86_VENDOR_AMD, 0x610f31 }, /* RL-A1 */
> { 0, 0 },
> };
> Thanks,
> Scott
>
>
> ]Thanks, best regards,
>
>
--
Best regards,
HacKurx
www.hackurx.info
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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
src/cpu/amd/agesa/family15tn/model_15_init.c:
static struct cpu_device_id cpu_table[] = {
{ X86_VENDOR_AMD, 0x610f00 }, /* TN-A0 */
{ X86_VENDOR_AMD, 0x610f31 }, /* RL-A1 */
{ 0, 0 },
};
Thanks,
Scott
]Thanks, best regards,
--
coreboot mailing list: coreboot@coreboot.org
http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
On Wed, Feb 26, 2014 at 12:54 PM, HacKurx 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 the right direction. It would still be helpful if you can post the details for this stick. You may also want to post the output of "git diff" for others who may want to try Richland on the F2A85-M. At this point, you'll need to study the code and find out exactly where it is dying. There may be someone who can spot it quickly, but I'm unsure of exactly what the issue is. I do think the line "Initializing devices" may mean that this is related to the devicetree code. It has successfully run the first part of AGESA, specifically initializing the memory controller, PCI-E, so you have a sort-of-working system. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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 http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
On Tue, Feb 25, 2014 at 1:39 PM, HacKurx 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 to change the == to != on line 255 of file > > vendorcode/amd/agesa/f15tn/Proc/CPU/cpuFamilyTranslation.c. > > Thank you very much, it is more verbose: > http://pastebin.com/Nszbv9p1 > > What do you think from this? > This is significant progress. It is trying to initialize the memory controller. Several people (myself included) have had problems in the past getting DDR3 memory to work, so we might be able to help you. Please check that the memory voltage in your .config matches your memory. Choices are 1.5V or 1.65V. Can you also reply with all the details for your memory? Please try removing all but 1 stick and put that one in the A1 slot. (See the motherboard manual for the slot numbering.) If that doesn't work you can try the other slots, but you will want to get 1 stick working before trying dual-channel etc. With just 1 stick in the A1 slot, please post a pastebin of the console output. If you have access to any other DDR3 RAM, especially if it is rated for a lower speed than your current RAM, you may want to try that also. Regards, David -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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 > vendorcode/amd/agesa/f15tn/Proc/CPU/cpuFamilyTranslation.c. Thank you very much, it is more verbose: http://pastebin.com/Nszbv9p1 What do you think from this? Thanks -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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: vendorcode/amd/agesa/f15tn/Proc/CPU/cpuFamilyTranslation.c SubFamilyIdPtr[j] ((CONST CPU_LOGICAL_ID_XLAT **)&CpuLogicalIdAndRevPtr, &LogicalIdEntries, &LogicalFamily, StdHeader); The reason is that the loop is processing each element of table F15LogicalIdTable until a match is found. But that table includes a NULL terminator (line 1176 of file: vendorcode/amd/agesa/f15tn/Include/ OptionFamily15hInstall.h) This means that if no CPUID match is found, a NULL function pointer will be called. That problem is an agesa bug that shows up only when an unsupported cpu is found. 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 vendorcode/amd/agesa/f15tn/Proc/CPU/cpuFamilyTranslation.c. Thanks, Scott -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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 from AMD I despair. -- Best regards, -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 code. Time will tell... -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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 mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
>> 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 >> already had the ability to overclock to 2133 MHz DDR3. >> >> It seems the problem is getting a good debug log with IDSOPT_IDS_ENABLED, >> and that is baffling. I've attached a coreboot image, but please check the >> config and use cbfstool for payloads *before* flashing it. >> >> David >> >> Here is the .config I used. Also, this is a pretty old version of coreboot >> (7bb29d72ab89c300fa899a8cf39803ae8f101ff4). > > The email with the rom attached is too big for the coreboot list, but > HacKurx, please let me know if you try out the rom. > > David Thank you, I tested your rom and I get the same result: coreboot-4.0-4561-g7bb29d7 Wed Jul 24 23:26:25 MDT 2013 starting... BSP Family_Model: 00610f31 cpu_init_detectedx = agesawrapper_amdinitreset > The problem is that we don't have Richland AGESA code: > src/vendorcode/amd/agesa/f15rl/ does, unfortunately, not exist. > > Idwer Thank you for this information. Please indicate the compatible processor on the motherboard page. I think tried to contact people from AMD to get the Richland AGESA code. -- Best regards, HacKurx www.hackurx.info -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 where Integrated Debug Support can be enabled fairly easily. I haven't tested this on actual hardware, but config.h looks good. I would appreciate feedback from real testing; I don't have any AGESA hardware myself. //Peter -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 wrote: > >> > 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. >> > >> > Perhaps try 'make clean' followed by all the normal build steps? >> >> I tried several times but I still get the same result. I tried to >> start with clean git, and I've already used "make clean" to no avail. >> If in doubt, do not hesitate to create a rom for me that I test. >> >> So the output now that I can get without this: >> coreboot-4.0-5454-g400c05c-dirty vendredi 7 février 2014, 09:25:15 >> (UTC+0100) starting... >> POST: 0x34 >> BSP Family_Model: 00610f31 >> cpu_init_detectedx = >> POST: 0x37 >> agesawrapper_amdinitreset >> >> > 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 > already had the ability to overclock to 2133 MHz DDR3. > > It seems the problem is getting a good debug log with IDSOPT_IDS_ENABLED, > and that is baffling. I've attached a coreboot image, but please check the > config and use cbfstool for payloads *before* flashing it. > > David > > > > Here is the .config I used. Also, this is a pretty old version of coreboot > (7bb29d72ab89c300fa899a8cf39803ae8f101ff4). > > The email with the rom attached is too big for the coreboot list, but HacKurx, please let me know if you try out the rom. David -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
2014-02-04 22:36 GMT+01:00 Rudolf Marek : >> 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 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. > > Thanks > Rudolf The problem is that we don't have Richland AGESA code: src/vendorcode/amd/agesa/f15rl/ does, unfortunately, not exist. Idwer -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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. > > Perhaps try 'make clean' followed by all the normal build steps? I tried several times but I still get the same result. I tried to start with clean git, and I've already used "make clean" to no avail. If in doubt, do not hesitate to create a rom for me that I test. So the output now that I can get without this: coreboot-4.0-5454-g400c05c-dirty vendredi 7 février 2014, 09:25:15 (UTC+0100) starting... POST: 0x34 BSP Family_Model: 00610f31 cpu_init_detectedx = POST: 0x37 agesawrapper_amdinitreset Thank -- Best regards, HacKurx www.hackurx.info -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
On Thu, Feb 6, 2014 at 12:28 AM, HacKurx 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. > > I made it. There is in my file: > grep "#define IDSOPT_IDS_ENABLED" > coreboot/src/mainboard/asus/f2a85-m/OptionsIds.h > #define IDSOPT_IDS_ENABLED TRUE > > I get exactly the same result with this option... > > I also tested the following options without success. : > CONFIG_DEBUG_CBFS > CONFIG_DEBUG_MALLOC > CONFIG_DEBUG_ACPI > CONFIG_DEBUG_SPI_FLASH > > What can I do now? Thanks. > > 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. Perhaps try 'make clean' followed by all the normal build steps? David -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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" coreboot/src/mainboard/asus/f2a85-m/OptionsIds.h #define IDSOPT_IDS_ENABLED TRUE I get exactly the same result with this option... I also tested the following options without success. : CONFIG_DEBUG_CBFS CONFIG_DEBUG_MALLOC CONFIG_DEBUG_ACPI CONFIG_DEBUG_SPI_FLASH What can I do now? Thanks. Best regards, -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 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. Thanks Rudolf -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
2014-02-01 Rudolf Marek : > 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 back in March. 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 Your rom (with your vga bios): coreboot-4.0-5310-g065289c Tue Jan 21 15:52:56 CET 2014 starting... BSP Family_Model: 00610f31 cpu_init_detectedx = agesawrapper_amdinitreset idwer rom (http://ra.openbios.org/~idwer/f2a85-m/coreboot_1002_990c.rom): coreboot-4.0-4745-g1ce4860-dirty Tue Oct 29 17:29:28 UTC 2013 starting... BSP Family_Model: 00610f31 cpu_init_detectedx = agesawrapper_amdinitreset Obviously this should be the processor that is the problem. Thanks, Best regards, HacKurx -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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? Thanks Yes sure. You will need at least those things: 1) serial header connector http://www.ebay.com/itm/DB9-Male-RS232-COM-Port-Serial-Header-Cable-for-Asus-Gigabyte-ATX-Motherboard-/151124424976?pt=LH_DefaultDomain_0&hash=item232fb7b910 You can take any from some old motherboard. Usually there where two variants of pinout. The newer one fits the most mainboards. You need to plug it to a header on the f2a85-m board. (pin1 to the color stripe on the cable) I think it is called "COM header" in the manual. 2) null modem cross cable The header from 1) needs to be plugged to 2) This cable is very common. It is also called "crossed" cable with female/female 9 pin connector. http://www.ebay.com/itm/Serial-RS232-Null-Modem-Cable-Female-to-Female-DB9-FTA-/270787845377?pt=AU_CablesConnectors&hash=item3f0c369d01 (female / female) 3) USB to serial cable Either find some other computer which has a serial header (and you will need second header from 1)) or buy this convertor. Most of them use pl2303 or ftdi chip which is well supported under linux. http://www.ebay.com/itm/USB-to-RS232-Serial-Port-9-Pin-DB9-Cable-Serial-COM-Port-Adapter-Convertor-2014-/201011761929?pt=US_Parallel_Serial_PS_2_Cables_Adapters&hash=item2ecd3c1309 4) other computer (any laptop/desktop) Plug in the USB serial with all cables plugged, and use /dev/ttyUSB0 use "minicom" or "hyperterminal" if you use windows. Set it 115200 8N1 (8 byte 1 stop bit no parity) 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 back in March. Thanks Rudolf -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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 me some money and I could buy the richland to > see if it works... but this could happen somewhere in March. Okay, I could send you the ddr3 memory if you need it. > The image I sent to you will most likely not POST the image because of > different IDs, but X.org could initialize it. I tested it and I do not even turn on the LEDs on my keyboard. I also think that I do not even reaches grub. I also designed several Roms defining "1002,990e" for the vga bios but I get the same result. I can put online my vgabios if you want. Thank you very much. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 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. Is it Richland or Trinity? Seems it is Richland. I haven't tried with Richland yet. It looks some people can send me some money and I could buy the richland to see if it workks... but this could happen somewhere in March. Can you send me a link to a known-good image that you use? So that i can verify my hardware is compatible. The image I sent to you will most likely not POST the image because of different IDs, but X.org could initialize it. Thanks Rudolf -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
> 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. Okay I'll test this. >Mine board is also 1.02 version. I think something wrong is with memory setup >or cpu setup. Does original BIOS use 1.65V for DDR2 memory? >You should select >that in configuration too. In the original bios I saw 1.5V for DDR3 memory. But I'll look and test it. Thanks. 2014-01-29 Rudolf Marek : > 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 >> payload (using a local copy of the VGA bios and embedding this into >> the coreboot image), leaving all the settings as >> default apart from selecting the motherboard, upon writing this to the >> flash and rebooting the machine I had no output from the VGA & HDMI >> adapter and >> and my keyboard is frozen. > > > It would be helpful if you could include log from serial console. Maybe you > hit some other problem. > > You can also try to put memory only to blue slots. > >> Can you send me a link to a known-good image that you use? So that i can >> verify my hardware is compatible. > > > >> Does he work the revision 1.02 of this motherboard in coreboot? > > Mine board is also 1.02 version. I think something wrong is with memory > setup or cpu setup. Does original BIOS use 1.65V for DDR2 memory? You should > select that in configuration too. > > You can come to IRC #coreboot on freenode.net > > I'm here until midnight GMT+2 > > Thanks > Rudolf > > > >> >> >> Thank you for your help. >> > -- Best regards, HacKurx www.hackurx.info -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
Re: [coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
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 payload (using a local copy of the VGA bios and embedding this into the coreboot image), leaving all the settings as default apart from selecting the motherboard, upon writing this to the flash and rebooting the machine I had no output from the VGA & HDMI adapter and and my keyboard is frozen. It would be helpful if you could include log from serial console. Maybe you hit some other problem. You can also try to put memory only to blue slots. Can you send me a link to a known-good image that you use? So that i can verify my hardware is compatible. > Does he work the revision 1.02 of this motherboard in coreboot? Mine board is also 1.02 version. I think something wrong is with memory setup or cpu setup. Does original BIOS use 1.65V for DDR2 memory? You should select that in configuration too. You can come to IRC #coreboot on freenode.net I'm here until midnight GMT+2 Thanks Rudolf Thank you for your help. -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
[coreboot] Unable to start correctly coreboot on Asus f2a85-m REV 1.02
Hi, Despite my many test I can not run correctly coreboot on my motherboard. Here is my hardware: _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) lspci 00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Root Complex 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Richland [Radeon HD 8570D] 00:01.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Trinity HDMI Audio Controller 00:10.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 03) 00:10.1 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB XHCI Controller (rev 03) 00:11.0 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 40) 00:12.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:12.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:13.0 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB OHCI Controller (rev 11) 00:13.2 USB controller: Advanced Micro Devices, Inc. [AMD] FCH USB EHCI Controller (rev 11) 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 14) 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD] FCH Azalia Controller (rev 01) 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 11) 00:14.4 PCI bridge: Advanced Micro Devices, Inc. [AMD] FCH PCI Bridge (rev 40) 00:15.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 0) 00:15.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Hudson PCI to PCI bridge (PCIE port 1) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 0 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 1 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 2 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 3 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 4 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 15h (Models 10h-1fh) Processor Function 5 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 09) I proceeded to build a standard coreboot image using seabios as a payload (using a local copy of the VGA bios and embedding this into the coreboot image), leaving all the settings as default apart from selecting the motherboard, upon writing this to the flash and rebooting the machine I had no output from the VGA & HDMI adapter and and my keyboard is frozen. Can you send me a link to a known-good image that you use? So that i can verify my hardware is compatible. Does he work the revision 1.02 of this motherboard in coreboot? Thank you for your help. -- Best regards, HacKurx (Loic) hackurx.wordpress.org -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot
