January 2018 - coreboot - mail.coreboot.org

Re: [coreboot] BDX-DE PCI init fail
by Hilbert Tu(杜睿哲_Pegatron) Jan. 26, 2018

Jan. 26, 2018

Hi guys, Sorry for the late. I spent some time try to use U-Boot as payload but still get infinite reboot…maybe wrong TSC clock frequency in my dts file. About using the Grub2 as payload, it is now working after I modify “–unit=1” to “—unit=0” :P That’s why it hangs… Thanks for all your help. -Hilbert This e-mail and its attachment may contain information that is confidential or privileged, and are solely for the use of the individual to whom this e-mail is addressed. If you are not the intended recipient or have received it accidentally, please immediately notify the sender by reply e-mail and destroy all copies of this email and its attachment. Please be advised that any unauthorized use, disclosure, distribution or copying of this email or its attachment is strictly prohibited. 本電子郵件及其附件可能含有機密或依法受特殊管制之資訊，僅供本電子郵件之受文者使用。台端如非本電子郵件之受文者或誤收本電子郵件，請立即回覆郵件通知寄件人，並銷毀本電子郵件之所有複本及附件。任何未經授權而使用、揭露、散佈或複製本電子郵件或其附件之行為，皆嚴格禁止。

1 0

Re: [coreboot] I want to be a contributor (Cloud Dai)
by Taiidan＠gmx.com Jan. 25, 2018

Jan. 25, 2018

On 01/25/2018 05:42 AM, echelon(a)free.fr wrote: > Hello Taiidan, > I have 2 questions: > -1) why is 6328 better for games? (compared to 6386SE?) Faster clock speeds rather than an extra 8 un-used cores, there are very few games that can use more than 8 cores fewer still that would cooperate with the 16 core opteron NUMA arrangement that divides your RAM (the 16 core optys are two 8 core CPU's on a single die) You can also use isolcpus=2,3,4,5 to get Turbo 2 in case your games only use 4 cores. 6328 is equivilant to an FX-8310 > -2) where can I buy 6386SE for less than 250 USD? Is this price for preowned units? Yeah it is, there isn't any reason to buy a new CPU as they last 20 years versus the much shorter lifespan for motherboard components such as capacitors. > I have been hunting for these items on ebay for 2 months or more, but I see only offers @ 400USD and more!.. 6328: There are a few for $100/ea right now 6386SE: There were some working scratch and dent (how?!?!) for $170/ea a few weeks ago, $120/ea a month ago for one that had missing capacitors that made it only work in a single CPU configuration. As always don't be afraid to use best offer and if nothing suits you just wait a week or so one will probably show up then. Btw if you don't have all the D8/D16 boards you want I would buy them new while you still can, they are going to stop selling/making them soon if they haven't already. As always feel free to ask any questions, and if you want something off list just change the reply title to something else and add a note.

1 0

Re: [coreboot] I want to be a contributor (Cloud Dai)
by 戴，曉政 Jan. 25, 2018

Jan. 25, 2018

Dear Taiidan, Thank for your suggestion, I will search 6328 and 6386E CPU on a auction website. I have paid money tor seller of auction website today, I think I can get KGPE-D16 in the near future. >Feel free to ask any questions you have :D >I suggest that you purchase a 6386SE (16 cores, good for compiling) or >6328 (8 cores, better for games) CPU > >6328 average $80-120 USD >6386SE average $150-250 USD --- Avast 防毒軟體已檢查此封電子郵件的病毒。 https://www.avast.com/antivirus

1 0

Is CONFIG_USE_OPTION_TABLE option stable?
by Аладышев Константин Jan. 25, 2018

Jan. 25, 2018

Hello! I'm trying to include CMOS variables use to my Coreboot, but when I enable "CONFIG_USE_OPTION_TABLE" option strange things happen. Windows stucks at boot logo and coreinfo payload displays very strange NVRAM RTC data (completely incorrect time with year and second that increment every second). I checked this with upstream code on Google/Panther motherboard. This motherboard uses "mc146818rtc" driver for RTC. Without "CONFIG_USE_OPTION_TABLE" option coreinfo displays time correctly. What can be the source of such thing? Best Regards, Aladyshev Konstantin

2 1

Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
by Robert Reeves Jan. 25, 2018

Jan. 25, 2018

2 1

Re: [coreboot] I want to be a contributor (Cloud Dai)
by Taiidan＠gmx.com Jan. 24, 2018

Jan. 24, 2018

On 01/24/2018 07:46 AM, 戴，曉政 via coreboot wrote: > Dear Taiidan & Ron, > > I will purchase USB CH341A along of purchase KGP-D16, thank for your suggestion Feel free to ask any questions you have :D I suggest that you purchase a 6386SE (16 cores, good for compiling) or 6328 (8 cores, better for games) CPU 6328 average $80-120 USD 6386SE average $150-250 USD

1 0

Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
by Zheng Bao Jan. 24, 2018

Jan. 24, 2018

Or, I can ask my quesion in another way. After extract the shellball of chromebook, how can I know what the processor exactly is? Zheng ________________________________ From: coreboot <coreboot-bounces(a)coreboot.org> on behalf of Zheng Bao <fishbaoz(a)hotmail.com> Sent: Wednesday, January 24, 2018 2:53 PM To: Robert Reeves Cc: coreboot(a)coreboot.org Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board But it seems that ifdtool can only get ME, not MRC. Zheng ________________________________ From: Robert Reeves <xiinc37(a)gmail.com> Sent: Wednesday, January 24, 2018 1:35 PM To: Zheng Bao Cc: coreboot(a)coreboot.org Subject: Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board They might not be the same. I would try using ifdtool to get an mrc.bin from a rom for your specific board. Rob On Jan 24, 2018 5:53 AM, Zheng Bao <fishbaoz(a)hotmail.com> wrote: > > Hi, All, > The output of my board is attached below. The MRC.bin is extracted from panther, which I assume matches my board. > But the meminit fails. Do all the haswell use the same MRC, or how can I decide which mrc.bin is the one I should extract? > > Thanks. > > Zheng > > coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage starting... > Disabling Watchdog reboot... done. > SMBus controller enabled. > Setting up static northbridge registers... done. > Initializing Graphics... > Back from haswell_early_initialization() > CPU id(40651) ucode:0000001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz > AES supported, TXT supported, VT supported > PCH type: LP Premium, device id: 9c43, rev id 4 > Starting UEFI PEI System Agent ___ > CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0) > CBFS: Locating 'mrc.cache' > CBFS: Found @ offset fec0 size 10000 > find_current_mrc_cache_local: No valid MRC cache found. > CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0) > CBFS: Locating 'mrc.bin' > CBFS: Found @ offset 9fec0 size 2eb04 > System Agent: Starting up... > System Agent: Initializing PCH > install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845} > install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276} > System Agent: Initializing PCH (SMBUS) > System Agent: Initializing PCH (USB) > System Agent: Initializing PCH (SA Init) > System Agent: Initializing PCH (Me UMA) > System Agent: Initializing Memory > System Agent: Done. > Sanity checking heap. > sdram_initialize,153: rv=0 > here. > sdram_initialize,186 > sdram_initialize,189 > ME: FW Partition Table : OK > ME: Bringup Loader Failure : NO > ME: Firmware Init Complete : NO > ME: Manufacturing Mode : YES > ME: Boot Options Present : NO > ME: Update In Progress : NO > ME: Current Working State : Normal > ME: Current Operation State : Bring up > ME: Current Operation Mode : Security Override via Jumper > ME: Error Code : No Error > ME: Progress Phase : BUP Phase > ME: Power Management Event : Pseudo-global reset > ME: Progress Phase State : 0x66 > RAM INIT FAILURE! >

1 0

Re: [coreboot] [Haswell i7-4600U]: How can I decide which MRC.bin match my board
by Robert Reeves Jan. 24, 2018

Jan. 24, 2018

They might not be the same. I would try using ifdtool to get an mrc.bin from a rom for your specific board. Rob On Jan 24, 2018 5:53 AM, Zheng Bao <fishbaoz(a)hotmail.com> wrote: > > Hi, All, > The output of my board is attached below. The MRC.bin is extracted from panther, which I assume matches my board. > But the meminit fails. Do all the haswell use the same MRC, or how can I decide which mrc.bin is the one I should extract? > > Thanks. > > Zheng > > coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage starting... > Disabling Watchdog reboot... done. > SMBus controller enabled. > Setting up static northbridge registers... done. > Initializing Graphics... > Back from haswell_early_initialization() > CPU id(40651) ucode:0000001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz > AES supported, TXT supported, VT supported > PCH type: LP Premium, device id: 9c43, rev id 4 > Starting UEFI PEI System Agent ___ > CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0) > CBFS: Locating 'mrc.cache' > CBFS: Found @ offset fec0 size 10000 > find_current_mrc_cache_local: No valid MRC cache found. > CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0) > CBFS: Locating 'mrc.bin' > CBFS: Found @ offset 9fec0 size 2eb04 > System Agent: Starting up... > System Agent: Initializing PCH > install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845} > install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276} > System Agent: Initializing PCH (SMBUS) > System Agent: Initializing PCH (USB) > System Agent: Initializing PCH (SA Init) > System Agent: Initializing PCH (Me UMA) > System Agent: Initializing Memory > System Agent: Done. > Sanity checking heap. > sdram_initialize,153: rv=0 > here. > sdram_initialize,186 > sdram_initialize,189 > ME: FW Partition Table : OK > ME: Bringup Loader Failure : NO > ME: Firmware Init Complete : NO > ME: Manufacturing Mode : YES > ME: Boot Options Present : NO > ME: Update In Progress : NO > ME: Current Working State : Normal > ME: Current Operation State : Bring up > ME: Current Operation Mode : Security Override via Jumper > ME: Error Code : No Error > ME: Progress Phase : BUP Phase > ME: Power Management Event : Pseudo-global reset > ME: Progress Phase State : 0x66 > RAM INIT FAILURE! >

2 1

Re: [coreboot] I want to be a contributor (Cloud Dai)
by 戴，曉政 Jan. 24, 2018

Jan. 24, 2018

Dear Taiidan & Ron, I will purchase USB CH341A along of purchase KGP-D16, thank for your suggestion > I would suggest purchasing a USB CH341A programmer, I use it for my > KGPE-D16 and it is great. > > >me too. --- Avast 防毒軟體已檢查此封電子郵件的病毒。 https://www.avast.com/antivirus

1 0

[Haswell i7-4600U]: How can I decide which MRC.bin match my board
by Zheng Bao Jan. 24, 2018

Jan. 24, 2018

Hi, All, The output of my board is attached below. The MRC.bin is extracted from panther, which I assume matches my board. But the meminit fails. Do all the haswell use the same MRC, or how can I decide which mrc.bin is the one I should extract? Thanks. Zheng coreboot-4.6-894-ga26344d-dirty Wed Jan 24 05:38:45 UTC 2018 romstage starting... Disabling Watchdog reboot... done. SMBus controller enabled. Setting up static northbridge registers... done. Initializing Graphics... Back from haswell_early_initialization() CPU id(40651) ucode:0000001c Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz AES supported, TXT supported, VT supported PCH type: LP Premium, device id: 9c43, rev id 4 Starting UEFI PEI System Agent ___ CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0) CBFS: Locating 'mrc.cache' CBFS: Found @ offset fec0 size 10000 find_current_mrc_cache_local: No valid MRC cache found. CBFS: 'Master Header Locator' located CBFS at [300100:3fffc0) CBFS: Locating 'mrc.bin' CBFS: Found @ offset 9fec0 size 2eb04 System Agent: Starting up... System Agent: Initializing PCH install_ppi: overwrite GUID {ed097352-9041-445a-80b6-b29d509e8845} install_ppi: overwrite GUID {908c7f8b-5c48-47fb-8357-f5fd4e235276} System Agent: Initializing PCH (SMBUS) System Agent: Initializing PCH (USB) System Agent: Initializing PCH (SA Init) System Agent: Initializing PCH (Me UMA) System Agent: Initializing Memory System Agent: Done. Sanity checking heap. sdram_initialize,153: rv=0 here. sdram_initialize,186 sdram_initialize,189 ME: FW Partition Table : OK ME: Bringup Loader Failure : NO ME: Firmware Init Complete : NO ME: Manufacturing Mode : YES ME: Boot Options Present : NO ME: Update In Progress : NO ME: Current Working State : Normal ME: Current Operation State : Bring up ME: Current Operation Mode : Security Override via Jumper ME: Error Code : No Error ME: Progress Phase : BUP Phase ME: Power Management Event : Pseudo-global reset ME: Progress Phase State : 0x66 RAM INIT FAILURE!

1 0