edk2
uefi-ntfs
edk2 | uefi-ntfs | |
---|---|---|
51 | 15 | |
4,262 | 722 | |
1.9% | - | |
9.9 | 5.3 | |
3 days ago | about 1 month ago | |
C | 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.
edk2
-
Future of 32-bit platform support in FreeBSD
For the modern server/desktop and even laptop, that's also no bad thing. It is somewhat ridiculous that UEFI bioses, internally, still boot in 16-bit real mode and have to do all the steps your bios bootloader used to do to set up a 64-bit environment ready to go: https://github.com/tianocore/edk2/blob/edc6681206c1a8791981a..., https://github.com/tianocore/edk2/blob/edc6681206c1a8791981a..., https://github.com/tianocore/edk2/blob/edc6681206c1a8791981a...
Why not just start the CPU in "long mode", which is what everyone is using it for, in the first place?
These newer ARM processors support 32-bit code at EL0 only (userspace). That seems like a reasonable approach for x86 as well and the freebsd announcement has this to say:
> There is currently no plan to remove support for 32-bit binaries on 64-bit kernels.
So for the moment, you can run 32-bit applications just fine.
-
Precision 7520: 64GB memory 3200MHz support
Download this UEFI shell and place it in the BOOT subfolder
-
Just about every Windows and Linux device vulnerable to new LogoFAIL firmware attack
They could have at least informed TianoCore. the affected code in edk2 hasn't been modified in 2 years.... https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Library/BaseBmpSupportLib/BmpSupportLib.c
-
VM not booting with host-passthrough or host-model
I have half fixed it.. Using this solution: https://github.com/tianocore/edk2/discussions/4662
-
All gaming laptop owners know this is never true...
You need only EDK2 and some lööps.
-
AMD openSIL open source firmware proof of concept
What is the difference between this and https://github.com/tianocore/edk2
-
AMD to move to open source firmware in 2026
From there you'll need to get an EFI Shell. There may be one built into your system, but you can also get one here from Tianocore (aka, the people mostly making UEFI). Neither this EFI Shell nor Keytool.efi (the thing you need to load the keys) are signed of course, so you will need to turn off SecureBoot to continue. From there just run Keytool with your new keys, turn back on SecureBoot, and move on with your life.
-
Windows installation doesn't boot up when I try to use UEFI firmware
I had the same issue. What fixed it for me was compiling my own OVMF.fd file from here and using that to boot. The version of OVMF that shipped with fedora was broken for me for some reason.
- why chatgpt knows about (haswell NRI) [ERROR] REUT timed out, ch_done: 0 but not in google?
- EDK II Project: cross-platform firmware development environment
uefi-ntfs
-
How long would it take for USB 2.0 to boot windows2go?
Because we use UEFI:NTFS to ensure that:
-
Does anyone know why Rufus creates a second "UEFI" volume that's <1MB?
Indeed, that 1 MB volume is the UEFI:NTFS partition that is described here.
-
MSI's (In)Secure Boot
> Can you please link me some articles/references?
Well explained here: https://gabrielsieben.tech/2022/07/29/remote-assertion-is-co...
So the issue is not the SecureBoot itself, but the ways it can and has been and will be leveraged against the user. If a desktop computer example is not enough, look at how Android phones have increasingly tightened down everything. You can't just take any model and install a custom OS (aka ROM in Android community). It was universally easy 10 years ago, that's why Cyanogenmod became so popular. Now your choices are very limited.
> \> > But that is besides the fact that these acts of aggression
A great thread and arguments provided here, how Microsoft (who love open source, according to own PR) will not sign anything GPLv3 for SecureBoot: https://github.com/pbatard/uefi-ntfs/issues/20#issuecomment-...
Microsoft has the defacto monopoly over the signature process, because nobody embeds any CAs in UEFI except for Microsoft's. What would be a user-friendly way? To preload UEFI with major Linux distros' keys, disabled by default, with an easy first-time setup menu to select what to do.
My laptop came with SecureBoot enabled by default although being "OS: FreeDOS" on paper. I had to figure out to disable it to boot into a live distro else it fell into an EFI shell.
> Vote with your wallet, don't buy the hardware.
> ... I am much more concerned about Intel ME and AMD PSP, where's the outrage about that?
With this I just want to say the wallet argument doesn't work when something slowly becomes the status quo and it takes experts/activists to fight back (a minority by numbers).
> I still can't easily utilise a TPM [...] and nobody bothered to integrate the functionality?
I agree, I'd have liked to enforce SecureBoot post-installation but it is too much hassle for me, I think only RedHat made good improvements in this area where it's actually easily usable (auto signing the kernel image etc.)
> Security isn't about what's unlikely, it's about the entire chain.
... But if I followed through, then still the weakest point is/becomes the keyboard. It would be trivial for an evil maid to add a keylogging device between your desktop and the physical keyboard. Do you check the rear IO on each boot? The considerations differ for laptops where you can't just plug something inbetween and need to disassemble it (time required: over night or airport luggage).
-
Windows 10 ISO with a large WIM - can’t boot
Please see here or here.
-
Looking for help installing a specific distro on a very peculiar computer.
I am the developer of Rufus, and I have spent an inordinate amount of time making sure that, YES, EVEN UEFI COMPUTERS THAT ARE "ALLEGEDLY" ONLY MEANT TO SUPPORT FAT32 FOR BOOT CAN ACTUALLY BOOT FROM THE NTFS PARTITION CREATED BY RUFUS (through the magic of a little solution called UEFI:NTFS). See also this entry from our FAQ.
-
Rufus made 2 UEFI partitions. Which one to choose?
For more details about the second UEFI:NTFS partition, see https://github.com/pbatard/uefi-ntfs.
-
I made a USB for Build 25120 with Rufus and for some reason it is also displaying the UEFI partition for it. It is meant to happen?
Rufus dev here. That's the UEFI:NTFS partition, needed to boot computers that don't have a native NTFS driver and it is completely harmless (and uses a negligible amount of space since it's just 1 MB). So, yes, this is meant to happen.
-
Anyone able to install windows on steam deck while only owning a mac?
So if you want to copy the contents of the ISO as is, you need to extract them to exFAT or NTFS (which are file systems that the Windows installer can also read outside of FAT), but this means that you may have to install an exFAT or NTFS UEFI driver to chain load the Windows installer, which is why utilities like Rufus and WoeUSB add a 1 MB UEFI:NTFS partition at the end of the drive, that takes care of that.
-
Can't get Windows 11 image to boot.
Rufus uses UEFI:NTFS, and therefore WILL allow your firmware to boot from NTFS. So, no, you don't have to use FAT32, and you should let Rufus create the drive with NTFS, as, even when using NTFS, it will create a drive that can be booted from UEFI.
-
[Discussion] Tool to burn in USB a standalone media created in SCCM
If it's because Rufus creates 2 partitions, then you should read about this (UEFI:NTFS is what Rufus uses to boot drives that are NOT compatible with UEFI, such as ones where you cannot use FAT32 because they contain a file that is larger than 4 GB), and understand that the data on the NTFS partition is exactly the same as the one you'd have found on a FAT32 drive, if your data was suitable for FAT32.
What are some alternatives?
vTPM - libtpms / swtpm software emulation of a Trusted Platform Module (TPM 1.2 and TPM 2.0) compile script
webMAN-MOD - Extended services for PS3 console (web server, ftp server, netiso, ntfs, ps3mapi, etc.)
tianocore
ntfs3 - ntfs3 Linux kernel module by Paragon Software
coreboot - Mirror of https://review.coreboot.org/coreboot.git. We don't handle Pull Requests.
WoeUSB - A Microsoft Windows® USB installation media preparer for GNU+Linux
OpenCorePkg - OpenCore bootloader
Reverse-Engineering-Tutorial - A FREE comprehensive reverse engineering tutorial covering x86, x64, 32-bit ARM & 64-bit ARM architectures.
Getting-Started-With-ACPI - Repo for Getting Started With ACPI
IRISMAN - All-in-one backup manager for PlayStation®3. Fork of Iris Manager.
limine - Modern, advanced, portable, multiprotocol bootloader.
SynapseOS - Синапс ОС (SynapseOS) - российская микроядерная операционная система.