Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Byte Mk I] Add coreboot firmware #56

Open
wanderer opened this issue Nov 28, 2022 · 16 comments
Open

[Byte Mk I] Add coreboot firmware #56

wanderer opened this issue Nov 28, 2022 · 16 comments

Comments

@wanderer
Copy link

Hello, I would like to install coreboot on a new byte. But I don't see any bin's.

@Skirmisher
Copy link

Same here. Not sure when I should be expecting a stable coreboot release for the Byte—there hasn't been a peep on the subject from the general info channels (their Twitter account or the "news" section on the website). Pretty disappointing when the Byte was, and still is, advertised with coreboot support, with no mention of an ETA other than "not at launch" (mentioned once in like a Twitter reply or something, I don't even remember). I know Star Labs' coreboot tree has a config for the Byte, but I have no reference for how complete the port is. I wouldn't mind nearly as much if status updates were more forthcoming.

@Sean-StarLabs
Copy link
Contributor

Website does say but it'll be released when ready. NDAs are annoyingly restrictive but just waiting on AMD to fix one "thing" and then we're good to go

@Sean-StarLabs Sean-StarLabs changed the title Firmware for byte is missing [Byte Mk I] Add coreboot firmware Jan 23, 2023
@FreeSpaceByte
Copy link

Hello Starlabs Systems Ltd Support, has something gone on in the AMD firmware AMI or Coreboot development?
Please let us know about the current status of firmware development and about good work around.

@FreeSpaceByte
Copy link

Wouldn't it be possible to pre-release AMI firmware with Intel ME disabled? Then waiting for Coreboot would not be so important and unbearable to wait, because I mean, most of those who choose Starlab's system do this because they want to close the Intel ME security hole and which firmware is up to you. The byte has now done about 6 months nothing and it should finally go something forward, at least the Intel ME option deactivated, no matter what firmware, the main thing is that this one thing is made possible for us customers. All those who have opted for AMD CPU should not be put off forever. Best Regards!!

@Sean-StarLabs
Copy link
Contributor

The Intel ME is disabled by default on all platforms that have it/ AMD SOCs don't have the Intel ME - they have the PSP, and that cannot be disabled on any firmware.

@FreeSpaceByte
Copy link

Thank you for your helpful explanation. I read up on AMD PSP on a search engine and the big difference to Intel ME is that PSP runs at the hardware level. Again learned something from the knowledge base! One source also said that there are also vulnerabilities in the AMD PSP system, but are easier to fix because of the hardware level than instead of Intel ME in an Update.

Sorry, then I somehow imagined something that wasn't the case at all. Now I know why I was satisfied with the byte from the beginning. I solved my other problem with a VPN service from Switzerland, had confused that. Now I finally understand all this. For me, the hard way was necessary, sorry. Thank you very much. Understanding is just something different than being able to use it.

Then I pushed myself a monkey although that's not the case. Please forgive me, I did not understand this correctly. Now I have the information and I am happy again. Just right. It's just the thing that first have to understand. Stay with community, cause good to know about base to end users and explains good. I got was worked around in the case i choose and finally i can handle with this one "thing" very good. Good By(t)e * * * * *

@FreeSpaceByte
Copy link

This is only a message, not an issues. Perhaps this should still be mentioned here.

"Coreboot coming soon" I had overlooked.

The information

Please` note - the coreboot firmware for AMD processors is currently in development. It is likely to be ready by dispatch, but it
might not be.

appeared later.

In addition, the Byte Configure -> firmware -> Learn more about Firmware, contains information about Intel CPU, whereby the Bytes are only available to AMD CPU. This should be extended with a version with AMD CPU information, so that you are easily clear. That's kind of missing. As a new customer, the technical conditions are not yet familiar. Better only AMD CPU information for the Byte.

Your Byte will support American Megatrends (AMI) Aptio V and coreboot firmware.

Comparing AMI Aptio V to coreboot; it is closed-source and has many features, including Secure Boot and capsule updates. coreboot is open-source and very lightweight, allowing faster boot time and less power consumption.
By default, the Intel ME is disabled on both coreboot and AMI.

You can can switch between AMI and coreboot firmware anytime, as often as you want.

Please` note - the coreboot firmware for AMD processors is currently in development. It is likely to be ready by dispatch, but it

might not be. Should that happen, we will send your Byte with AMI firmware, and you can install coreboot from the LVFS once it is available.

AMD SOCs don't have the Intel ME - they have the PSP, and that cannot be disabled on any firmware.

Only from a new customer who does not yet know about the differences between AMD CPU and Intel CPU, just as a hint.

I just wanted to tell you this because I wasn't clear about it when I bought it. This would be a future help for new customers to be better informed in advance.

Just a cosmetic point!
I hope it's nicely worded for you.

Best Regards!

@FreeSpaceByte
Copy link

I don't want to be a spam bot, but I just have to get rid of that.

I come from a time when people work from top to bottom, but also work from bottom to top. This makes a lot of things easier. I think it's a pity that it is no longer desirable to work from the bottom up. Just because mistakes creep in from the bottom up, even if you don't want to give it!

For a long time I withdrew into privacy because I didn't like the new school. Only when I had read through the new fine print, I dared to go public again. And I'm really angry and disappointed that the old school is only allowed to exist in privacy.

My blow is completely old school and in today's there is no place for people like me in public, which is again something private and according to the new school you are not allowed to say.

It is a pity for old school and people like me!

That probably doesn't belong here, but where does old school still belong?

@Sean-StarLabs
Copy link
Contributor

has something gone on in the AMD firmware AMI or Coreboot development?

Still back and forth but I wrote some code yesterday that will hopefully do the trick - I should have a chance to test it Friday.

By default, the Intel ME is disabled on both coreboot and AMI.

Good point, I'll look at that. It might end ups trying as there will be an Intel variant of the byte soon (AMD availability leaves something to be desired!)

@FreeSpaceByte
Copy link

AMD doesn't seem to take it that seriously with the Coreboot project, because otherwise they would have released the fix long ago and wouldn't have let it mess around like that. It's a pity, although AMD appeals to me more than Intel...

However, an update of the AMI version would be really appropriate so that a stable version is finally available, even if the byte, as it seems, is a small margin.

@Sean-StarLabs
Copy link
Contributor

They openly agree with that (save for chromebooks).

If you ping [email protected], they'll be able to provide some new firmware (few variables based on the distro and spec)

@wanderer
Copy link
Author

wanderer commented May 7, 2023

If you ping [email protected], they'll be able to provide some new firmware (few variables based on the distro and spec)

@Sean-StarLabs will the new firmware prevent the byte from turning itself off when under a load? And can we have an updated ETA for coreboot?

@Sean-StarLabs
Copy link
Contributor

Yes
It's with the PSP team now; never had dealing with them before so it's hard to say an ETA. We are pushing them via every single contact we have though!

@FreeSpaceByte
Copy link

Hi,

Does updating the firmware via LFVS also work with an encrypted operating system?

I read the news about the Byte MK2, so the Byte Mk1 dropped out of the product placement...

But will the Byte Mk1 still have the long-awaited firmware updates for AMI and a coreboot release?

@Sean-StarLabs
Copy link
Contributor

Does updating the firmware via LFVS also work with an encrypted operating system?

Depends - see https://support.starlabs.systems/kb/firmware/lvfs-requirements

But will the Byte Mk1 still have the long-awaited firmware updates for AMI and a coreboot release?

Yes

@Logiar
Copy link

Logiar commented Nov 8, 2023

Is there anything new on this subject? I'm still struggling with the byte shutting down under load and needing to be physically unplugged from power to restart. Been hoping the coreboot firmware will fix the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants