Intel i7-12700T in HP Elite Mini G9 600: How to get correct EFI BIOS File? · Issue #295 · strongtz/i915-sriov-dkms · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Configuration: Intel i7-12700T in HP Elite Mini G9 600, working but glitchy Xe drivers inside Windows 11 VM, having issues with error 43/corrupted installs when trying to update Xe drivers inside the VM.
Given the above, I decided to try the new EFI BIOS portion of the ReadMe. That wasn't there when I set this VM up.
Except, the SHA256 value from the .EFI file I extracted doesn't match what's in the ReadMe.
Is it possible HP has just done something that would result in a changed checksum, or should it match the ReadMe?
If it should match the ReadMe, is there a known good vBIOS I can pull from somewhere?
EDIT: The VM boots with the ROM file attached, but I don't know whether it's actually doing anything or not. Is there a way I can check? After updating, I was getting a Code 43 until I completely shut down the VM and started it again.
Thanks!
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Hello,
Configuration: Intel i7-12700T in HP Elite Mini G9 600, working but glitchy Xe drivers inside Windows 11 VM, having issues with error 43/corrupted installs when trying to update Xe drivers inside the VM.
Given the above, I decided to try the new EFI BIOS portion of the ReadMe. That wasn't there when I set this VM up.
I followed the directions here to extract the EFI VBIOS from HP's latest BIOS firmware update for this machine: https://github.com/strongtz/i915-sriov-dkms?tab=readme-ov-file#extract-graphics-efi-firmware
Except, the SHA256 value from the .EFI file I extracted doesn't match what's in the ReadMe.
Is it possible HP has just done something that would result in a changed checksum, or should it match the ReadMe?
If it should match the ReadMe, is there a known good vBIOS I can pull from somewhere?
EDIT: The VM boots with the ROM file attached, but I don't know whether it's actually doing anything or not. Is there a way I can check? After updating, I was getting a Code 43 until I completely shut down the VM and started it again.
Thanks!
The text was updated successfully, but these errors were encountered: