docs
coreboot
docs | coreboot | |
---|---|---|
236 | 92 | |
1,714 | 2,076 | |
0.0% | 1.3% | |
0.0 | 10.0 | |
about 2 years ago | 7 days ago | |
C | ||
GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
docs
-
A Brief History of the U.S. Trying to Add Backdoors into Encrypted Data
marcan of the Asahi Linux project got into a discussion on reddit about this, and says that when it comes to hardware, you just can’t know.
> I can't prove the absence of a silicon backdoor on any machine, but I can say that given everything we know about AS systems (and we know quite a bit), there is no known place a significant backdoor could hide that could completely compromise my system. And there are several such places on pretty much every x86 system
(Long) thread starts here, show hidden comments for the full discussion https://old.reddit.com/r/AsahiLinux/comments/13voeey/what_is...
I highly recommend reading this if you’re interested https://github.com/AsahiLinux/docs/wiki/Introduction-to-Appl...
-
The Register looks at the first release of Fedora Asahi Remix
Depends on the box. In general if there is a hardwired HDMI port it works, if it's an alt mode it doesn't yet. The feature pages give detail by hardware, heres a direct link to the M2 page https://github.com/AsahiLinux/docs/wiki/M2-Series-Feature-Su...
-
Fedora Asahi Remix
https://github.com/AsahiLinux/docs/wiki/M1-Series-Feature-Su...
According to this page it should work on M1 MBP, but there is also a note about a specific patch released next week.
-
Sonoma updates bricking MBPs
I'm just refuting that OP's dot update problem on Sonoma was caused by the refresh rate bug. In all likelihood OP doesn't have a weird Sonoma/Ventura dual boot situation going on (or Ashai Linux for that matter, who wrote a great article about this). In all my testing (and with a large enterprise sample size) we had zero reports of the refresh bug impacting an Apple Silicon Mac running just Sonoma itself.
- Speaker Support in Asahi Linux
-
Tuxedo Pulse Gen 3
> They don't support variations of software at all. They support the hardware. [...] Asahi does not need to support applications at all.
From their FAQ page[1]:
> We will eventually release a remix of Arch Linux ARM, packaged for installation by end-users, as a distribution of the same name. The majority of the work resides in hardware support, drivers, and tools, and it will be upstreamed to the relevant projects. The distribution will be a convenient package for easy installation by end-users and give them access to bleeding-edge versions of the software we develop.
As distro maintainers, it is their job to make sure the applications they package work on the hardware they support. This includes submitting patches upstream when that is not the case, as application maintainers likely wouldn't want to support such a niche environment directly. So, yes, they rely on volunteers to fix issues, but they will likely have to support many applications themselves.
There is still a lot of broken software, as this list[2] is surely not exhaustive.
> Same deal for any other hardware manufacturer. [...] Really not much different to other hardware manufacturers since Linux started.
No, it's very different. First of all, the amount of Linux hackers who volunteered to reverse engineer the wide variety of hardware was orders of magnitude larger than the Asahi team. Even if they limit the amount of devices they support, modern computers are far more complex than in the early days of Linux. Regardless of how talented the Asahi team is, maintaining all the hardware of a modern computer is a sisyphean task for a project run by volunteers.
Secondly, hardware manufacturers could see the benefit of getting their hardware to run in Linux, and many eventually took over support from volunteers. Apple has shown no interest in doing so, and has historically been hostile to open source.
> Asahi devs have made it clear that Apple has chosen to avoid blocking installation of other operating systems.
The fact they allow installation of other operating systems today, doesn't mean that this decision couldn't change in the future. Services are a large part of their business, and allowing a group of hackers to use their hardware without being part of their software ecosystem may seem like a non-issue today, but if this group grows larger assuming projects like Asahi are successful, this might become a considerable loss of income which wouldn't be in their best interest.
> Apple has no issue with it.
Can you point me to an official ackgnowledgment of Asahi Linux by Apple? Or any indication that leaving this door open was a sign of good will, instead of a lack of interest in closing it? What makes you think they wouldn't eventually lock down Macbooks in the same way they do iPhones and iPads?
> ARM is a stable well supported platform for Linux
It's really not. A lot of software works, but when it doesn't, the user is SOL. As you can see on their Broken Software page[2], the major issue is precisely with AArch64 support. This should improve eventually, and Asahi is certainly a torchbearer in this scenario, but today it's yet another hurdle of using Apple hardware.
[1]: https://asahilinux.org/about/#is-this-a-linux-distribution
[2]: https://github.com/AsahiLinux/docs/wiki/Broken-Software
- Asahi Linux Team Uncovers macOS Refresh Rate Bugs: Sonoma Boot Failures
-
Update on the Sonoma bug situation
More information about the macOS Sonoma ProMotion bug here.
-
PSA: Don't upgrade to Ventura 13.6+ or Sonoma 14.0+ on Apple Silicon with custom display settings
Here’s the actual issue for anyone that cares, fully documented : https://github.com/AsahiLinux/docs/wiki/macOS-Sonoma-Boot-Failures
coreboot
-
Chromebooks will get 10 years of automatic updates
Why BIOS (did you mean UEFI?) when it runs the best boot loader, which is Coreboot¹. Many users would love to re-flash their bios/uefi for it, if it’s supported.
1: https://www.coreboot.org/
-
C++ is everywhere, but noone really talks about it. What are people's thoughts?
Coreboot is 0.6% C++.
-
Laptops with best Linux support (latest gen, battery life, performance)?
NovaCustom ; some models come with Dasharo a coreboot distribution.
-
Asus flip c302 last update
You can also use Mr. Chromebox Script to install Coreboot on your chromebook to get a UEFI BIOS on your Chromebook and then you can go an install either a linux distro or even Windows if you want. It's a pretty straightforward process and also reversable if you want to go back to just using ChromeOS.
-
A Linux laptop under 1350€
Some models are available with Dasharo a [coreboot]https://www.coreboot.org/) distribution.
-
why no haswell_ult_dmi_registers for broadwell? in https://github.com/coreboot/coreboot/blob/master/util/inteltool/pcie.c
why no haswell_ult_dmi_registers for broadwell? in https://github.com/coreboot/coreboot/blob/master/util/inteltool/pcie.c
-
Having issues restoring the firmware with u/MrChromebox's utility
use croshfirmware.sh from https://github.com/coreboot/coreboot/tree/master/util/chromeos
-
AMD to move to open source firmware in 2026
There may be other protections to restrict SPI flash access for security reasons (so you might not be able to flash your custom firmware in the OS), but worst case you can use a HW flasher (or maybe USB flashback). Still, this doesn't address the elephant in the room - platform initialization code might be open-sourced, but that isn't everything. You'll still need to figure out the board-specific stuff (the Super I/O chip, chipset GPIOs, other peripherals, etc.). Using coreboot as an example, Intel provides the Firmware Support Package blob to handle platform initialization. I think AGESA is somewhat similar to this, though Intel publicly releases the binaries for use in coreboot/etc. Thanks to the FSP, coreboot has support for recent Intel chipsets. However, there is only support for two recent consumer boards: the MSI PRO Z690-A WiFi DDR4 and DDR5.
-
what is VCU (Validation Control Unit) mailbox in haswell nri
does anyone know what is https://github.com/coreboot/coreboot/blob/b12caef23bc1b29c2e658f2b728cc4beac1e62b9/src/northbridge/intel/haswell/vcu_mailbox.c
-
Need stock ROM for Acer Chromebook CB314 - DROID
Download crosfirmware.sh and run it from command line: bash crosfirmware.sh droid
What are some alternatives?
idevicerestore - Restore/upgrade firmware of iOS devices
1vyrain - LiveUSB Bootable exploit chain to unlock all features of xx30 ThinkPad machines. WiFi Whitelist, Advanced Menu, Overclocking.
tinygrad - You like pytorch? You like micrograd? You love tinygrad! ❤️ [Moved to: https://github.com/tinygrad/tinygrad]
edk2 - EDK II
FEX - A fast usermode x86 and x86-64 emulator for Arm64 Linux
u-boot - "Das U-Boot" Source Tree
asahi-installer - Asahi Linux installer
UEFITool - UEFI firmware image viewer and editor
AsahiLinux
OpenCore-Install-Guide - Repo for the OpenCore Install Guide
nixos-apple-silicon - Resources to install NixOS bare metal on Apple Silicon Macs
thinkpad-firmware-patches - Collection of ThinkPad UEFI patches.