Contribute
Register

deadbeef Kernel Panic when booting from Unibeast USB

Joined
Mar 26, 2014
Messages
14
Motherboard
Hackle Fastbender
CPU
Intel 4770K
Graphics
MSI GTX 650 Ti Boost
Mac
  1. MacBook Pro
Classic Mac
Mobile Phone
After building the Yosemite USB stick with Unibeast and attempting to boot from it, I'm greeted with a deadbeef kernel panic (see attached).

Any suggestions on how to get past this kernel panic would be helpful. I've tried the usual boot options (-x, npci=3000, GraphicsEnabler=No, maxmem=4096, PCIRootUID=0), with no success.

My system:

CPU Intel 4770KGraphics MSI GTX 650 Ti BoostOther Hardware Mobo: MSI Z87-G45 Gaming
NIC: Intel 100/1000
Cooling: Corsair H100i, Noctura case fans
Optical: LG Blu-ray Reader/Writer
 

Attachments

  • IMG_2663.jpg
    IMG_2663.jpg
    591.1 KB · Views: 659
Last edited by a moderator:
Joined
Sep 29, 2013
Messages
166
Motherboard
Gigabyte Z390 Aorus Ultra
CPU
i9-9900K
Graphics
UHD 630, RTX 2080 Super
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
I had the same, the only thing that got me past that was booting with -no-zp
 
Joined
Mar 26, 2014
Messages
14
Motherboard
Hackle Fastbender
CPU
Intel 4770K
Graphics
MSI GTX 650 Ti Boost
Mac
  1. MacBook Pro
Classic Mac
Mobile Phone
What does "-no-zp" do? I'm not familiar with this option. Also, is that the correct formatting?
 
Joined
Oct 19, 2014
Messages
1
Mac
Classic Mac
Mobile Phone
I was getting the same exact error. Used maxmem=4096 and it worked just fine.
 
Joined
Sep 29, 2013
Messages
166
Motherboard
Gigabyte Z390 Aorus Ultra
CPU
i9-9900K
Graphics
UHD 630, RTX 2080 Super
Mac
  1. MacBook Air
Mobile Phone
  1. iOS
I was getting the same exact error. Used maxmem=4096 and it worked just fine.

I tried with maxmem too, but for some reason it didn't work.. -no-zp did, no idea why that is.
 

P1LGRIM

Moderator
Joined
Mar 2, 2012
Messages
23,953
Motherboard
Lenovo ThinkStation p300 ⌘
CPU
i7-4790K
Graphics
HD 4600
Mac
  1. MacBook Pro
  2. Mac mini
Classic Mac
  1. Power Mac
Mobile Phone
  1. iOS
Was anyone able to solve this??

I am having this exact problem

Perhaps if you read the thread ?

Post #2
I had the same, the only thing that got me past that was booting with -no-zp

Post #5
I was getting the same exact error. Used maxmem=4096 and it worked just fine.

Post #6
I tried with maxmem too, but for some reason it didn't work.. -no-zp did, no idea why that is.
 
Top