[coreboot] ASUS KGPE-D16 Automated Test Failure [master]

The ASUS KGPE-D16 fails verification for branch master as of commit 27f3ce6337b293cfc7be0eb8592feb411cf2cc5f The following tests failed: BOOT_FAILURE Commits since last successful test: 27f3ce6 board_status/to-wiki: Update bucketize script See attached log for details This message was

Re: [coreboot] Let’s solve the Asus KCMA-D8 mess

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/26/2017 05:13 PM, Paul Menzel via coreboot wrote: > Dear coreboot folks, > > > As many of you know, last week was not pretty [1]. Unfortunately, no > solution was found. > > Chances are slim, that the involved parties will get along in the >

[coreboot] Let’s solve the Asus KCMA-D8 mess

Dear coreboot folks, As many of you know, last week was not pretty [1]. Unfortunately, no solution was found. Chances are slim, that the involved parties will get along in the future, but hopefully they will. I had hoped, that the community would have been asked for help before to find a

[coreboot] SeaBIOS IRC channel: #seab...@irc.freenode.net

Dear coreboot folks, No idea, if you already new this, but I didn’t know that there was a dedicated SeaBIOS IRC channel, until somebody mentioned it in #coreboot. Just wanted to let you know, as it’s not documented yet [1]. Thanks, Paul [1] https://www.seabios.org signature.asc

Re: [coreboot] Offtopic - tapping TxFP packages with flat cables?

Andrey Korolyov wrote: > > Buy another chip, make a breakout board, remove onboard chip, connect > > probes to breakout board, connect breakout board to mainboard. > > Thanks, but this is a pretty time-consuming method if I need to tap > four consecutive legs out of one hundred. Yes for sure! In

Re: [coreboot] Offtopic - tapping TxFP packages with flat cables?

> > Buy another chip, make a breakout board, remove onboard chip, connect > probes to breakout board, connect breakout board to mainboard. > Thanks, but this is a pretty time-consuming method if I need to tap four consecutive legs out of one hundred. Also BBs adding extra crosstalk which could

Re: [coreboot] Offtopic - tapping TxFP packages with flat cables?

Andrey Korolyov wrote: > tap 0.5mm pitched packages - how it could be done Buy another chip, make a breakout board, remove onboard chip, connect probes to breakout board, connect breakout board to mainboard. > i945, so initial porting has been done with very small effort, but .. > raminit run

Re: [coreboot] KGPE-D16 BMC Port Offer (was: Fund a TALOS Secure Workstation as coreboot build system)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/19/2017 11:36 AM, Martin Roth wrote: > Hey Merlin, > I was taking and keeping track of the pledges for Talos, so I'd be > happy to continue. > > Martin I just wanted to bring this back up for discussion. Raptor is chipping in funding for

Re: [coreboot] Does the 62xx Series Opteron work *securely* without microcode?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/26/2017 10:14 AM, taii...@gmx.com wrote: > On 01/26/2017 10:12 AM, ron minnich wrote: >> On Thu, Jan 26, 2017 at 3:41 AM Sam Kuper wrote: >> >>> >>> Hypothetical example: I buy a machine with built-in microcode from the

Re: [coreboot] Does the 62xx Series Opteron work *securely* without microcode?

On 01/26/2017 10:12 AM, ron minnich wrote: On Thu, Jan 26, 2017 at 3:41 AM Sam Kuper wrote: Hypothetical example: I buy a machine with built-in microcode from the young Anakin Skywalker. A decade later, Darth Vader releases a microcode update. Should I apply it? A

[coreboot] Offtopic - tapping TxFP packages with flat cables?

Hi, probably several people in the list met the same struggle to tap 0.5mm pitched packages (almost all SIOs and at least all H8/300 chips) - how it could be done without using micromanipulator or sticking flat cable with an equal pitch size on side of a chip? While it is possible to solder a

Re: [coreboot] Does the 62xx Series Opteron work *securely* without microcode?

On Thu, Jan 26, 2017 at 3:41 AM Sam Kuper wrote: > > > Hypothetical example: I buy a machine with built-in microcode from the > young Anakin Skywalker. A decade later, Darth Vader releases a > microcode update. Should I apply it? > A decade later? You should buy a new

[coreboot] Adding our company to www.coreboot.org/Products

Hello, Our company [1] offers a coreboot flashing service [2] for various coreboot-supported devices. We would like to be added to https://www.coreboot.org/Products if possible. If there are any steps we have to undertake, please let us know. Thanks in advance! [1] https://www.datraverse.com/

Re: [coreboot] How to extract fsp.bin from image?

Thank you. It is very useful to me. 2017-01-26 오전 1:45에 Andy Knowles 이(가) 쓴 글: Hi, Use the cbfstool, like so: build/util/cbfstool/cbfstool build/coreboot.rom extract -n fsp.bin -f fsp.bin Good luck! Andy *From:*coreboot [mailto:coreboot-boun...@coreboot.org] *On Behalf Of *???

Re: [coreboot] Does the 62xx Series Opteron work *securely* without microcode?

On 26.01.2017 12:41, Sam Kuper wrote: > On 25/01/2017, ron minnich wrote: >> If you have a machine with microcode updates, you >> should load the updates. I have never understood the objections to >> microcode blobs. If you accept the microcode that's on the machine already,

Re: [coreboot] Does the 62xx Series Opteron work *securely* without microcode?

On 25/01/2017, ron minnich wrote: > If you have a machine with microcode updates, you > should load the updates. I have never understood the objections to > microcode blobs. If you accept the microcode that's on the machine already, > then objecting to the microcode blob is

Re: [coreboot] Coreboot binary for ASUS F2A85-M

It is very strange, but my keyboard doesn't work. I have tried to connect another keyboard - LEDs blinked 20 percent of cases and also diesn't work. I took your advice Martin and increased the delay (200, 500, 5000) - didn't help. cbfstool coreboot.rom add-int -i 200 -n "etc/usb-time-sigatt"

Re: [coreboot] Does the 62xx Series Opteron work *securely* without microcode?

On Wed, Jan 25, 2017 at 11:26:53AM -0600, Aaron Durbin via coreboot wrote: > On Wed, Jan 25, 2017 at 11:24 AM, Timothy Pearson > wrote: > > -BEGIN PGP SIGNED MESSAGE- > > Hash: SHA1 > > > > On 01/24/2017 10:55 PM, taii...@gmx.com wrote: > >> I know the 63xx