Depending on which MacBook you have, you maybe be trying to setup to new an OS for it!
Review this listing to locate your system and then roll now to the ‘Pre-Installed MacOS:’ section to locate what is the highest you can go to MacBook A1181 models listing
As an example, the Late 2006 MacBook the highest it can handle is OS-X Lion (10.7.5) and the Mid 2009 MacBook can only go to OS-X El Capitan (10.11.6)
Make sure you are using the correct OS for your system! Even still you can encounter an issue! As Apple uses a certificate system to expire out older OS’s So installing a fresh copy of OS that has an expired certificate (which is based on a year and month) can drive you nuts!
As an example Apple messed up the certificates in the last three macOS’s (Sierra, High Sierra & Mojave) Here’s a bit more on what happened If you've got an old macOS install image, it will probably stop working today
While this is all well and good it won’t help you here! As Apple has not redone the OS Installer images for the older OS-X releases you would need.
So if the boy can’t get to the mountain, then the mountain needs to go to the boy!
So if we can’t install the OS as the certificate check will fail we need to figure out how to fake out the check so it doesn’t fail! And we can do that by programing the systems clock to year the certificate the installer has passes the check! So as an example altering the systems clock via the current OS following this approach:
You can also do this from within a terminal session as well. The important part is making sure your system doesn’t reset its year setting on its own before you’ve finished the OS install so make sure it can’t connect to the internet as it all automatically connect to the time server and correct its self.
crwdns2934105:0crwdne2934105:0
crwdns2934113:0crwdne2934113:0
crwdns2915270:0crwdne2915270:0
crwdns2889612:0crwdne2889612:0
0
I had wished you had stuck with your original question here: Why am I getting a kernel panic at boot than opening up a new one.
If you could not see a log file that tells us you are not installing a valid OS version for your system.
crwdns2934271:0crwdnd2934271:0 Dan crwdne2934271:0
I figured out that one, the hard drive is bad and has bad sectors on it so it causes the kernel panic when I try to boot from it. The usb throws up a kernel panic only when I try to boot a mac osx install from it. The hard drive had no recent log on it for the times I tried to boot it up
crwdns2934271:0crwdnd2934271:0 Cheap gamer crwdne2934271:0