feature request: a downloadable .efi x86_64 binary... #1

Closed
opened 2024-08-17 15:42:44 +02:00 by Wyk72 · 2 comments
Wyk72 commented 2024-08-17 15:42:44 +02:00 (Migrated from github.com)

I am trying to build ASPMenabler.efi, to patch the FADT of my bios as you did (using refind to launch it automatically) but the requirements for compiling are pretty..big.

Can you provide a simple "binary release" in .efi format for this ?

Thanks a lot.

I am trying to build ASPMenabler.efi, to patch the FADT of my bios as you did (using refind to launch it automatically) but the requirements for compiling are pretty..big. Can you provide a simple "binary release" in .efi format for this ? Thanks a lot.
0x666690 commented 2024-08-17 16:01:39 +02:00 (Migrated from github.com)

Try this. I don't have access to my server at the moment or else I would've pulled it from the USB but this one built just fine. (had to zip it because .efi is not a supported extension within the GitHub comment file attachments).

ASPMEnabler.zip

Let me know if that works for you.

Try this. I don't have access to my server at the moment or else I would've pulled it from the USB but this one built just fine. (had to zip it because .efi is not a supported extension within the GitHub comment file attachments). [ASPMEnabler.zip](https://github.com/user-attachments/files/16645149/ASPMEnabler.zip) Let me know if that works for you.
Wyk72 commented 2024-08-17 16:35:14 +02:00 (Migrated from github.com)

Thanks for your fast response!

ACPIenabler works PERFECTLY on a chinese fake-X99 board that have a
disastrous/hacked BIOS that reports erratic values..everywhere.

It's a QUIDYA X99 with a (hacked) H81 Chipset, using a 2011-3 Intel Xeon
E5-2680 v4 14core cpu.

Now I have full ASPM/OS control from my linux (it's Alpine Linux 3.20
kernel 6.6.46) for all pci-e devices at boot time.

I launch the .efi as suggested, installing refind and copying the .efi
into /boot/efi/EFI/refind/drivers_x64/

Works as a charm.

Thanks a lot for this.

Il giorno sab 17 ago 2024 alle ore 16:02 z8 @.***> ha
scritto:

Try this. I don't have access to my server at the moment or else I
would've pulled it from the USB but this one built just fine. (had to zip
it because .efi is not a supported extension within the GitHub comment file
attachments).

ASPMEnabler.zip
https://github.com/user-attachments/files/16645149/ASPMEnabler.zip

Let me know if that works for you.


Reply to this email directly, view it on GitHub
https://github.com/0x666690/ASPM/issues/1#issuecomment-2294868427, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AL33K2N3FWIXF5QZJB5RMFTZR5JVRAVCNFSM6AAAAABMVN7FMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA3DQNBSG4
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks for your fast response! ACPIenabler works PERFECTLY on a chinese fake-X99 board that have a disastrous/hacked BIOS that reports erratic values..everywhere. It's a QUIDYA X99 with a (hacked) H81 Chipset, using a 2011-3 Intel Xeon E5-2680 v4 14core cpu. Now I have full ASPM/OS control from my linux (it's Alpine Linux 3.20 kernel 6.6.46) for all pci-e devices at boot time. I launch the .efi as suggested, installing refind and copying the .efi into /boot/efi/EFI/refind/drivers_x64/ Works as a charm. Thanks a lot for this. Il giorno sab 17 ago 2024 alle ore 16:02 z8 ***@***.***> ha scritto: > Try this. I don't have access to my server at the moment or else I > would've pulled it from the USB but this one built just fine. (had to zip > it because .efi is not a supported extension within the GitHub comment file > attachments). > > ASPMEnabler.zip > <https://github.com/user-attachments/files/16645149/ASPMEnabler.zip> > > Let me know if that works for you. > > — > Reply to this email directly, view it on GitHub > <https://github.com/0x666690/ASPM/issues/1#issuecomment-2294868427>, or > unsubscribe > <https://github.com/notifications/unsubscribe-auth/AL33K2N3FWIXF5QZJB5RMFTZR5JVRAVCNFSM6AAAAABMVN7FMCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEOJUHA3DQNBSG4> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >
Sign in to join this conversation.