-
Notifications
You must be signed in to change notification settings - Fork 5
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
Comments
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. |
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 |
Hello Starlabs Systems Ltd Support, has something gone on in the AMD firmware AMI or Coreboot development? |
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!! |
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. |
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 * * * * * |
This is only a message, not an issues. Perhaps this should still be mentioned here. "Coreboot coming soon" I had overlooked. The information
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.
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! Best Regards! |
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? |
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.
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!) |
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. |
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) |
@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? |
Yes |
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? |
Depends - see https://support.starlabs.systems/kb/firmware/lvfs-requirements
Yes |
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. |
Hello, I would like to install coreboot on a new byte. But I don't see any bin's.
The text was updated successfully, but these errors were encountered: