[coreboot] What maintenance is expected from coreboot developers & companies

[Martin Roth]

I'd like to discuss the issue of what's expected from developers after
code is added to the coreboot tree.  It seems like there's a feeling
that if a company pushes code to coreboot, or hires someone to push
code to coreboot that there's an obligation to help maintain that code
going forward.  This seems to be different than if an individual adds
code, but maybe I'm wrong.

- Is there any expectation that work will continue to be done on
contributed code after the initial merge?

- Is there a different expectation of maintenance for when a company
pushes code vs when an individual contributor pushes code?

- If there's an expectation that the contributor will help maintain
that codebase, how long does that expectation last?

- If there's an expectation of maintaining the code and that
expectation isn't met, what are the consequences?
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: KGPE-D16: coreboot-4.5 stuck in boot loop. Help on getting the system to boot or flash newer version

[Pablo Correa Gómez]

Thank you all for your advice. I already have a BBB, so I will probably
end up using that. I believe with all this help I will be able to work
it out and I know some things that I should not do. I will answer once
I have been able to fix it.

Regards,
Pablo.

On mar, 2019-04-30 at 14:05 -0400, Matt B wrote:
> While I think it's great that it worked, I'd recommend flashing with
> a programmer before hotswapping the bios chip.
> 
> You could work through compiling a fresh copy of coreboot on another
> computer, or if someone knows how to extract the bios image from an
> asus download you could try restoring that.
> 
> -Matt
> 
> On Tue, Apr 30, 2019 at 11:50 AM Sean Lynn Rhone  .net> wrote:
> > I had to do something similar with a KCMA-D8 motherboard, but I had
> > an
> > old motherboard around that let me hotswap the BIOS chip, and I was
> > able to use flashrom from a Linux LiveUSB to flash the ASUS vendor
> > BIOS
> > to the chip, while socketed in another motherboard.
> > 
> > After the flash, I powered off the computer, took the BIOS chip
> > out,
> > tossed it into the KCMA-D8 motherboard, and was good to go.
> > 
> > For specific beginner-friendly steps:
> > 
> > 1. Boot an old motherboard (something without Intel ME is more
> > likely
> > to succeed; I have an AMD 700/800 Phenom II motherboard for this)
> > with
> > it's BIOS chip into a Linux LiveUSB (like Lubuntu)
> > 2. Install flashrom (apt/zypper/dnf/package manager should be fine,
> > but
> > worst-case if the chip isn't recognized, you'll need to compile
> > flashrom from source which has additional dependencies and steps)
> > 3. Download/copy the vendor BIOS ROM file somewhere
> > 4. Test if flashrom can read/write to the original BIOS chip
> > without
> > problem (dump the chip contents and attempt to re-write it back)
> > 5. With the computer/motherboard still powered, remove its BIOS
> > chip
> > (with usual anti-ESD measures; use a chip puller preferably but you
> > can
> > also "gently" wiggle it out with your fingers)
> > 6. Insert a different BIOS chip that you want flashed into the
> > socket
> > 7. Use flashrom to write to that BIOS chip (internal flash)
> > 8. If flashrom succeeds, power off the computer/motherboard
> > 9. Remove the flashed BIOS chip from that computer/motherboard, and
> > insert it into whatever other motherboard you were trying to fix
> > 10. Re-insert the original BIOS chip into the flasher motherboard
> > 
> > On Tue, 2019-04-30 at 18:02 +0300, Mike Banon wrote:
> > > These pre-flashed BIOS chips are overpriced. You could download
> > the
> > > latest BIOS from ASUS website and flash it directly to your
> > existing
> > > BIOS chip using another computer and flashrom-supported hardware
> > > flasher.
> > > ___
> > > coreboot mailing list -- coreboot@coreboot.org
> > > To unsubscribe send an email to coreboot-le...@coreboot.org
> > ___
> > coreboot mailing list -- coreboot@coreboot.org
> > To unsubscribe send an email to coreboot-le...@coreboot.org
> > 
> ___
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: KGPE-D16: coreboot-4.5 stuck in boot loop. Help on getting the system to boot or flash newer version

[Matt B]

While I think it's great that it worked, I'd recommend flashing with a
programmer before hotswapping the bios chip.

You could work through compiling a fresh copy of coreboot on another
computer, or if someone knows how to extract the bios image from an asus
download you could try restoring that.

-Matt

On Tue, Apr 30, 2019 at 11:50 AM Sean Lynn Rhone 
wrote:

> I had to do something similar with a KCMA-D8 motherboard, but I had an
> old motherboard around that let me hotswap the BIOS chip, and I was
> able to use flashrom from a Linux LiveUSB to flash the ASUS vendor BIOS
> to the chip, while socketed in another motherboard.
>
> After the flash, I powered off the computer, took the BIOS chip out,
> tossed it into the KCMA-D8 motherboard, and was good to go.
>
> For specific beginner-friendly steps:
>
> 1. Boot an old motherboard (something without Intel ME is more likely
> to succeed; I have an AMD 700/800 Phenom II motherboard for this) with
> it's BIOS chip into a Linux LiveUSB (like Lubuntu)
> 2. Install flashrom (apt/zypper/dnf/package manager should be fine, but
> worst-case if the chip isn't recognized, you'll need to compile
> flashrom from source which has additional dependencies and steps)
> 3. Download/copy the vendor BIOS ROM file somewhere
> 4. Test if flashrom can read/write to the original BIOS chip without
> problem (dump the chip contents and attempt to re-write it back)
> 5. With the computer/motherboard still powered, remove its BIOS chip
> (with usual anti-ESD measures; use a chip puller preferably but you can
> also "gently" wiggle it out with your fingers)
> 6. Insert a different BIOS chip that you want flashed into the socket
> 7. Use flashrom to write to that BIOS chip (internal flash)
> 8. If flashrom succeeds, power off the computer/motherboard
> 9. Remove the flashed BIOS chip from that computer/motherboard, and
> insert it into whatever other motherboard you were trying to fix
> 10. Re-insert the original BIOS chip into the flasher motherboard
>
> On Tue, 2019-04-30 at 18:02 +0300, Mike Banon wrote:
> > These pre-flashed BIOS chips are overpriced. You could download the
> > latest BIOS from ASUS website and flash it directly to your existing
> > BIOS chip using another computer and flashrom-supported hardware
> > flasher.
> > ___
> > coreboot mailing list -- coreboot@coreboot.org
> > To unsubscribe send an email to coreboot-le...@coreboot.org
> ___
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org
>
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: Coreboot support for Gigabyte GA-78LMT-USB3 (rev. 5.0)

[Branden Waldner]

I believe the recommendation is to start with one of the boards
closest to what you have (ie. one of the boards with the same
northbridge, southbridge, and superio), try to figure out any
adjustments you can tell it needs and test and debug.

The northbridge is part of the cpu and depends on which cpu you
install. For the fx series it would be agesa family 15tn. I'm not sure
how the cpu support works, depending on your build, you may only get
support for certain processor families? I don't think the agesa code
is very well supported.

You posted your flashrom log in place of your superiotool log, but the
manual says it has an ITE superio. There are amd sb700 boards on
boardstatus with either the ITE IT8712F or ITE IT8718F.

For flashing you would need a testclip and something to drive it. The
dual bios feature won't help with coreboot, since it isn't jumper/
hardware switched based that I can tell.

I was going to mention needing to figure out the option rom or
graphics init for the onboard graphics, but it looks like your using a
separate video card, so it can probably be ignored.

Hopefully this helps you and I didn't get too much of it wrong.
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: KGPE-D16: coreboot-4.5 stuck in boot loop. Help on getting the system to boot or flash newer version

[Sean Lynn Rhone]

I had to do something similar with a KCMA-D8 motherboard, but I had an
old motherboard around that let me hotswap the BIOS chip, and I was
able to use flashrom from a Linux LiveUSB to flash the ASUS vendor BIOS
to the chip, while socketed in another motherboard.

After the flash, I powered off the computer, took the BIOS chip out,
tossed it into the KCMA-D8 motherboard, and was good to go.

For specific beginner-friendly steps:

1. Boot an old motherboard (something without Intel ME is more likely
to succeed; I have an AMD 700/800 Phenom II motherboard for this) with
it's BIOS chip into a Linux LiveUSB (like Lubuntu)
2. Install flashrom (apt/zypper/dnf/package manager should be fine, but
worst-case if the chip isn't recognized, you'll need to compile
flashrom from source which has additional dependencies and steps)
3. Download/copy the vendor BIOS ROM file somewhere
4. Test if flashrom can read/write to the original BIOS chip without
problem (dump the chip contents and attempt to re-write it back)
5. With the computer/motherboard still powered, remove its BIOS chip
(with usual anti-ESD measures; use a chip puller preferably but you can
also "gently" wiggle it out with your fingers)
6. Insert a different BIOS chip that you want flashed into the socket
7. Use flashrom to write to that BIOS chip (internal flash)
8. If flashrom succeeds, power off the computer/motherboard
9. Remove the flashed BIOS chip from that computer/motherboard, and
insert it into whatever other motherboard you were trying to fix
10. Re-insert the original BIOS chip into the flasher motherboard

On Tue, 2019-04-30 at 18:02 +0300, Mike Banon wrote:
> These pre-flashed BIOS chips are overpriced. You could download the
> latest BIOS from ASUS website and flash it directly to your existing
> BIOS chip using another computer and flashrom-supported hardware
> flasher.
> ___
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: [TF-A] [LPC] Bootloader miniconf

[Marek Vasut]

On 4/29/19 7:23 PM, Matteo Carlini wrote:
> Hi Marek,

Hi,

> Thanks for raising the topic across the communities. The question is probably 
> how many people from the various projects are going to attend Plumbers this 
> year in Lisbon, so to create some critical mass.
> 
> The TF.org project is planning a significant presence at the Open Source 
> Firmware Conference happening the week before in California 
> (https://osfc.io/), sponsoring the event and submitting few engineering 
> topics. This is another great opportunity to meet and chat on Boot/Firmware 
> topics as well.

The conf being in the US is a barrier for some, for various reasons.

Another upside of LPC miniconf is that you have the kernel people there,
who are taking over once the bootloader starts them, so it would give us
an unique opportunity to synchronize with their needs.

I had some exchange(s) on IRC and Alex Graf mentioned that rather then a
pure bootloader miniconf, we should also pull in OpTee and other such
"resident service provider" projects, since the kernel also communicates
with those and they're installed before the kernel takes over.

> Having a boot miniconf the week after in Europe may be a natural extension, 
> but I'm wondering if people would be willing to travel and attend two similar 
> events in a row...
I cannot answer that, maybe the result of this email can :)

-- 
Best regards,
Marek Vasut
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: KGPE-D16: coreboot-4.5 stuck in boot loop. Help on getting the system to boot or flash newer version

[Mike Banon]

Hi there Pablo!

> 1) Buy a new chip with the original ASUS BIOS in order to
> boot the system.

These pre-flashed BIOS chips are overpriced. You could download the
latest BIOS from ASUS website and flash it directly to your existing
BIOS chip using another computer and flashrom-supported hardware
flasher.

> 2) Externally flash the chip I have right now with a newer version
> of coreboot.

RPi is a bit of an overkill: the cheapest flashrom supported
programmer is USB CH341A which costs just a couple of dollars and
perhaps is easier to use (since you don't have to worry about the
configuration of onboard Linux and some other things). Check out the
last part of this article -
http://dangerousprototypes.com/docs/Flashing_a_BIOS_chip_with_Bus_Pirate
- for more CH341A + flashrom instructions. If your BIOS chip is
supported by flashrom, hopefully you could easily flash it following
these instructions. The only difference is that the BIOS chip of
KGPE-D16 seems to be a DIP-8 instead of SOIC-8, so you could insert
this DIP-8 chip right in CH341A and SOIC-8 test clip isn't needed of
course. Although there are DIP-8 test clips, if your chip is socketed
- they aren't needed.

> 3) The moderboard datasheet has a section called:
> "Force BIOS recovery setting"

Of course this method relies on the functionality of proprietary UEFI,
like Matt said.

Best regards,
Mike Banon
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org

[coreboot] Re: KGPE-D16: coreboot-4.5 stuck in boot loop. Help on getting the system to boot or flash newer version

[Matt B]

That method of emergency recovery with a USB stick has already been wiped
out by installing coreboot.

-Matt

On Mon, Apr 29, 2019 at 4:09 PM Pablo Correa Gómez 
wrote:

> Hello and thank you in advance for your time.
>
>  I recently bought a KGPE-D16 motherboard with a single AMD Opeteron
> 8262SE and coreboot installed. I bought from another supplier 4 memory
> sticks Samsung 8GB (M393B1K70DH0-YK0) that per this thread[1] should
> work with coreboot. I am able to start the assembled system and to get
> serial output. According to the logs, coreboot first does the
> initialisation and training of the memory and then start working on the
> PCIs. At one point in the boot sequence, I get the following message:
>
> Loaded segments
> BS: BS_PAYLOAD_LOAD times (us): entry 0 run 80561 exit 0
> POST: 0x7b
> Jumping to boot code at 000ff06e(b7cc1000)
> POST: 0xf8
> CPU0: stack: 0015 - 00151000, lowest used address 001509e0, stack
> used: 1568 bytes
> entry= 0x000ff06e
> lb_start = 0x0010
> lb_size  = 0x00116270
> buffer   = 0xbfdd3000
>
> Then it stalls for like 20-30 seconds and the booting process restarts
> from the beginning. I had considered different options in order to boot
> and I would like to know if someone would have any recommendations.
> Right now my priority is to get the system up and working. I can worry
> about installing coreboot later, but having it now is for sure a plus:
>   1) Buy a new chip with the original ASUS BIOS in order to boot the
> system.
>   2) Externally flash the chip I have right now with a newer version of
> coreboot. I probably have enough things at home to flash it, but I have
> not found information from ASUS. In coreboot there is some information
> but very general and not enough for my knowledge. As far as I have read
> from flashrom, I should be able to flash it using a Raspberry Pi or a
> BeagleBone Black, but KGPE-D16 is not marked as supported and I don't
> know which model is the BIOS chip to check if it is supported.
>   3) The moderboard datasheet has a section called: "Force BIOS
> recovery setting", which says that in order to flash the proprietary
> BIOS, it is as simple as changing a jumper an inserting an USB stick. I
> would have already done it if I would not be reluctant to believe that
> it is that simple.
>
> Which are your thoughts about this ideas? Any other one that would be
> simpler and would let me boot the full system?
>
> Thank you very much,
> Pablo.
>
>
> NOTE: I have tried with the 4 sticks in the orange slots, the 4 sticks
> in the 4 further DIMMs from the CPU (2 orange, 2 black) and those
> configurations both 1.35 and 1.5V. Logs are slightly different, in the
> training section, but the problem while booting remains. A USB stick
> with Debian Installer has been plugged-in during since boot process
> begins.
>
> [1] https://mail.coreboot.org/pipermail/coreboot/2017-February/083151.h
> tml
> 
> ___
> coreboot mailing list -- coreboot@coreboot.org
> To unsubscribe send an email to coreboot-le...@coreboot.org
>
___
coreboot mailing list -- coreboot@coreboot.org
To unsubscribe send an email to coreboot-le...@coreboot.org