parts will arrive in the next couple of days, in the meantime I am preparing the files, usb stick etc and I got this error when downloading bigsur with gibMacOs and then making it an installer file:
View attachment 497781
maybe is necessary to start with catalina and then update.
I had that problem, delete the entire subdirectory and then try again, took me three tries before I was able to download the full install files.
If your using gibMacos to create a Big Sur usb drive, it won't work last time I checked, you need to click on the InstallAssistant.pkg from the Big Sur download, which will manually open the Big Sur installer in the Application location, and in terminal providing you have all ready formatted your USB stick and names it USB run this commandparts will arrive in the next couple of days, in the meantime I am preparing the files, usb stick etc and I got this error when downloading bigsur with gibMacOs and then making it an installer file:
View attachment 497781
maybe is necessary to start with catalina and then update.
parts will arrive in the next couple of days, in the meantime I am preparing the files, usb stick etc and I got this error when downloading bigsur with gibMacOs and then making it an installer file:
View attachment 497781
maybe is necessary to start with catalina and then update.
This is a common issue:I had that problem, delete the entire subdirectory and then try again, took me three tries before I was able to download the full install files.
This is a common issue:
- Do not re-download the installer. It's not necessary.
- Do not run BuildmacOSInstallApp.command.
- Instead, run InstallAssistant.pkg
- This should be present inside the same folder as all the other files that were downloaded
- Now you should see Install macOS Big Sur.app in your Applications folder
OK I reverted back to F5. Further testing shows that it seem that the only seeeting that causes problem is exterme memory profile. As long as I leave that disabled I have no boot errors, but still no Thunderbolt either.The F4 BIOS, as I recall, does not expose CFG-Lock, and it is disabled by default, so F4 BIOS will not work. In the newer versions we must go to BIOS Setup and disabled CFG-Lock from the Boot section.
Is Thunderbolt enabled in BIOS, along with GPIO3 Force Pwr?OK I reverted back to F5. Further testing shows that it seem that the only seeeting that causes problem is exterme memory profile. As long as I leave that disabled I have no boot errors, but still no Thunderbolt either.