Bochs
docs
Bochs | docs | |
---|---|---|
4 | 236 | |
734 | 1,714 | |
9.5% | 0.0% | |
9.7 | 0.0 | |
4 days ago | about 2 years ago | |
C++ | ||
GNU Lesser General Public License v3.0 only | GNU General Public License v3.0 or later |
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.
Bochs
-
Ask HN: Where can I find a primer on how computers boot?
The following is a pretty decent historical page about the pre-(U)EFI MBR (Master Boot Record) boot process:
https://thestarman.pcministry.com/asm/mbr/STDMBR.htm
Note that EFI/UEFI -- occurred much later in time than MBR...
Related: https://en.wikipedia.org/wiki/Master_boot_record
You might also wish to check out some emulators, most notably Bochs (https://bochs.sourceforge.io/) and QEMU (https://www.qemu.org/) because they simulate the boot process, and if you're in their debuggers, you should be able to inspect that process step by step -- but also more generally emulators for other machines/platforms/architectures (https://en.wikipedia.org/wiki/List_of_computer_system_emulat...) -- because in general, most of those emulators should simulate the given machine/platform/architecture's boot process...
-
Can anyone recommend some good free tools for programming, debugging, and virtualization on Ubuntu?
With both of those you can make some really nice DOS programs. Which you can then run in bochs (not virtualized, but an emulator. Close enough :) ).
-
80286 ROM BIOS - open-source code base?
Just took a look myself, check this out:
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
What are some alternatives?
TinyBIOS - A mirror of TinyBIOS repository
idevicerestore - Restore/upgrade firmware of iOS devices
tianocore
tinygrad - You like pytorch? You like micrograd? You love tinygrad! ❤️ [Moved to: https://github.com/tinygrad/tinygrad]
linux-insides - A little bit about a linux kernel
FEX - A fast usermode x86 and x86-64 emulator for Arm64 Linux
8088_bios - BIOS for Intel 8088 based computers
asahi-installer - Asahi Linux installer
All-Stages-of-Linux-Booting-
AsahiLinux
QEMU - Official QEMU mirror. Please see https://www.qemu.org/contribute/ for how to submit changes to QEMU. Pull Requests are ignored. Please only use release tarballs from the QEMU website.
nixos-apple-silicon - Resources to install NixOS bare metal on Apple Silicon Macs