-
#1
All-
I’m really struggling with this update. I was initially running Sierra (which was rock solid) and took the plunge to update directly to Catalina. The update appeared to succeed with the exception that sound and wifi were broken. I managed to snatch defeat from the jaws of victory when I attempted to fix those issues, and after multiple failed attempts I opted for a clean install. I have yet to get Catalina to boot on this system again, and I can’t event get it to install. Things have now degenerated to the point that Clover loads, it attempts to boot the installer and immediately crashes with the error «In Memory Panic Stackshot Succeeded ** Bytes Traced 33424.» I’m really at a loss where to go from here, and I don’t know if I have a BIOS problem, a hardware problem, or a software problem. Any suggestions would be greatly appreciated. Thanks!
-
stackshot.jpg
317.5 KB
· Views: 985
-
#2
It appears this was a BIOS problem. I reinstalled the BIOS and reset CMOS. After that, I was able to boot the installer. Still can’t get Catalina to finish the install, but that is a topic for another thread.
-
#3
Hey! What did you change in BIOS exactly? I am having the exact same problem and I just cannot get past it. Did the CMOS reset, optimized defaults, changed couple settings in BIOS like VT-d etc and it still won’t let me get past this.
-
#4
Hey! What did you change in BIOS exactly? I am having the exact same problem and I just cannot get past it. Did the CMOS reset, optimized defaults, changed couple settings in BIOS like VT-d etc and it still won’t let me get past this.
Hello, do you path » Ec Spoofing » dsdt for desktop? If yes please check your Fake cpuid. If not please try path your «ec spoofing» catalina dsdt for desktop.
-
#5
It could be conflict between VirtualSMC and FakeSMC (check that you have only one of them in both EFI and /Library/Extensions) and in my case it has been caused by obsolete sensor kext (I used legacy NVidia sensor kext for very old GPU and then after graphic card upgrade the system started crashing)
-
#6
Hello, do you path » Ec Spoofing » dsdt for desktop? If yes please check your Fake cpuid. If not please try path your «ec spoofing» catalina dsdt for desktop.
Fake CPUID? What for is that necessary? Didn’t read anything about that in the vanilla guide either. I have done that EC part BUT it gives me this error (see picture attached). Sorry for hijacking this thread.
-
#7
Hey, I’m having the same problem. Did this guy ever find a fix?
I am able to get Catalina running but not Big Sur. After running the docker command, I see the bootloader, but when I select macOS Base System, the process gets stuck on In memory panic stackshot succeeded.
uname -a
; echo «${DISPLAY}»
; echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs
; grep NAME /etc/os-release
; df -h .
; qemu-system-x86_64 —version
; libvirtd —version
; free -mh
; nproc
; egrep -c ‘(svm|vmx)’ /proc/cpuinfo
; ls -lha /dev/kvm
; ls -lha /tmp/.X11-unix/
; ps aux | grep dockerd
; docker ps | grep osx
; grep «docker|kvm|virt» /etc/group
Linux xps-box 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux
:0
1
NAME="Manjaro Linux"
PRETTY_NAME="Manjaro Linux"
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/luks-e41457f4-a9e3-4f31-87e4-8365507c3181 452G 268G 161G 63% /
QEMU emulator version 6.1.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 7.8.0
total used free shared buff/cache available
Mem: 15Gi 10Gi 299Mi 1.8Gi 4.0Gi 2.0Gi
Swap: 16Gi 4.5Gi 12Gi
8
16
crw-rw-rw- 1 root kvm 10, 232 Nov 13 13:51 /dev/kvm
total 0
drwxrwxrwt 2 root root 80 Oct 31 09:35 .
drwxrwxrwt 29 root root 800 Nov 13 14:33 ..
srwxr-xr-x 1 adi adi 0 Oct 31 09:35 X0
srwxr-xr-x 1 adi adi 0 Oct 31 09:35 X1
root 547362 0.1 0.2 2418796 37588 ? Ssl 13:37 0:06 /usr/bin/dockerd -H fd://
adi 698413 0.0 0.0 6496 2308 pts/4 S+ 14:36 0:00 grep dockerd
209c6b81bd47 sickcodes/docker-osx:big-sur "/bin/bash -c 'sudo …" 44 minutes ago Up 44 minutes 0.0.0.0:50923->10022/tcp, :::50923->10022/tcp festive_grothendieck
6895b58f973a sickcodes/docker-osx:latest "/bin/bash -c 'sudo …" 50 minutes ago Up 50 minutes 0.0.0.0:50922->10022/tcp, :::50922->10022/tcp charming_moser
kvm:x:992:adi
docker:x:963:adi
libvirt:x:960:adi
I’ve gone through the troubleshooting section in README. I also haven’t seen this problem mentioned in any of the issues.
docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
sickcodes/docker-osx:big-sur
37 minutes ago, MaLd0n said:
bootloader and kexts is updated?
Yes, Clover is upgraded to current version 5127. Kexts are a mix of ne ones and old ones.
So now I upgraded every kext to the latest version. Removed what I guess could be problematic, and left only these:
It panicked again, but the issue seems a different one. This time I was able to copy the output:
Quote
panic(cpu 2 caller 0xffffff800ddefa76): Kernel trap at 0xffffff80106313bd, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000028, CR3: 0x0000000023bbc000, CR4: 0x00000000001626e0
RAX: 0x0000000000000000, RBX: 0xffffff937ac3dd80, RCX: 0xffffffa07cd13cbc, RDX: 0x0000000000000001
RSP: 0xffffffa07cd13c60, RBP: 0xffffffa07cd13ca0, RSI: 0x00000000f0ffffff, RDI: 0xffffff937ac3dd80
R8: 0x0000000000000001, R9: 0x0000000000000030, R10: 0x0000000000000001, R11: 0x0000000000000070
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffffa07cd13cbc
RFL: 0x0000000000010282, RIP: 0xffffff80106313bd, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x0000000000000028, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1Backtrace (CPU 2), Frame : Return Address
0xffffffa07cd13680 : 0xffffff800dcbc66d mach_kernel : _handle_debugger_trap + 0x3dd
0xffffffa07cd136d0 : 0xffffff800ddff073 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa07cd13710 : 0xffffff800ddef6aa mach_kernel : _kernel_trap + 0x55a
0xffffffa07cd13760 : 0xffffff800dc61a2f mach_kernel : _return_from_trap + 0xff
0xffffffa07cd13780 : 0xffffff800dcbbf0d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa07cd138a0 : 0xffffff800dcbc1f8 mach_kernel : _panic_trap_to_debugger + 0x268
0xffffffa07cd13910 : 0xffffff800e4bee1a mach_kernel : _panic + 0x54
0xffffffa07cd13980 : 0xffffff800ddefa76 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa07cd13b00 : 0xffffff800ddef75d mach_kernel : _kernel_trap + 0x60d
0xffffffa07cd13b50 : 0xffffff800dc61a2f mach_kernel : _return_from_trap + 0xff
0xffffffa07cd13b70 : 0xffffff80106313bd com.apple.iokit.IOPCIFamily : __ZN17IOPCIConfigurator17findPCICapabilityEP16IOPCIConfigEntryjPj + 0x41
0xffffffa07cd13ca0 : 0xffffff8010622ff5 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge25extendedFindPCICapabilityE17IOPCIAddressSpacejPy + 0x39
0xffffffa07cd13cd0 : 0xffffff8010621c28 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge8probeBusEP9IOServiceh + 0x1bc
0xffffffa07cd13d60 : 0xffffff801061e3ed com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge5startEP9IOService + 0xcb
0xffffffa07cd13d90 : 0xffffff800ecaa7a8 com.apple.driver.AppleACPIPlatform : __ZN12AppleACPIPCI5startEP9IOService + 0x10c
0xffffffa07cd13dd0 : 0xffffff800e3ef09b mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xeb
0xffffffa07cd13e40 : 0xffffff800e3eec46 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xce6
0xffffffa07cd13ef0 : 0xffffff800e3eddcf mach_kernel : __ZN9IOService14doServiceMatchEj + 0x30f
0xffffffa07cd13f50 : 0xffffff800e3f0b46 mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x186
0xffffffa07cd13fa0 : 0xffffff800dc6113e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8010617000->0xffffff801063efff
com.apple.driver.AppleACPIPlatform(6.1)[D5E73559-87FF-3A4D-A884-3C734F0BB103]@0xffffff800ec8e000->0xffffff800ed04fff
dependency: com.apple.driver.AppleSMC(3.1.9)[30ACBB00-67A3-36BD-AF95-1E6F0CB38447]@0xffffff800f290000->0xffffff800f2a8fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[65A1D60D-F9AF-37E7-B854-4127FBB3172A]@0xffffff80100d2000->0xffffff80100d3fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8010617000->0xffffff801063efffProcess name corresponding to current thread: Unknown
Boot args: npci=0x3000 -v keepsyms=1 debug=0x100 alcid=17 root-dmg=file:///BaseSystem/BaseSystem.dmgMac OS version:
Not yet setKernel version:
Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64
Kernel UUID: 84C6DC45-6B02-335F-9439-5D2A9BC385A4
KernelCache slide: 0x000000000da00000
KernelCache base: 0xffffff800dc00000
Kernel slide: 0x000000000da10000
Kernel text base: 0xffffff800dc10000
__HIB text base: 0xffffff800db00000
System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0System uptime in nanoseconds: 4520421733
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000000010f1581d0
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000185a821930 0x0000000000000000
last started kext at 3711014651: com.insanelymac.RealtekRTL8111 2.2.2 (addr 0xffffff8011bf1000, size 458752)
loaded kexts:
com.insanelymac.RealtekRTL8111 2.2.2
ru.joedm.SMCSuperIO 1.1.9
as.acidanthera.voodoo.driver.PS2!C 2.1.9
as.vit9696.SMCProcessor 1.1.9
as.vit9696.VirtualSMC 1.1.9
com.rehabman.driver.USBInjectAll 0.7.6
as.vit9696.WhateverGreen 1.4.5
as.vit9696.!AALC 1.5.5
as.vit9696.Lilu 1.5.0
>!AAHCIPort 346
@private.KextAudit 1.0
>!AHPET 1.8
>!AACPIButtons 6.1
>!ARTC 2.0
>!ASMBIOS 2.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>!A!ICPUPowerManagement 222.0.0
>usb.!UEHCIPCI 1.2
>usb.!UEHCI 1.2
|IOAHCI!F 294
|IONVMe!F 2.1.0
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 900.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.1f5
|IOReport!F 47
|IO!BPacketLogger 8.0.1f5
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.40.9
|IOUSBMass!SDriver 184.40.6
|IOSCSIBlockCommandsDevice 436.40.6
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.40.6
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
Edited December 19, 2020 by ChristoAta
Installed Catalina 10.15.2 a couple of weeks ago following Jake Lo’s guide.
It was working flawless.
Now that I saw that the update to 10.15.3 upgrade was like a walk in the park as long as I updated Clover, kexts and repaired permissions and rebuild cache I decided to take my chances.
So, I checked Clover, was latest version already. Updated a few kexts with the help of Kext Updater app.
(For some reason it wouldn’t boot if I moved BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext. I now have BrcmFirmwareData.kext and BrcmPatchRAM3.kext in my «Other» folder.)
So, even though I have all my kexts in the EFI partition , I ran the following just in case:
sudo chmod -Rf 755 /L*/E*
sudo chown -Rf 0:0 /L*/E*
sudo chmod -Rf 755 /S*/L*/E*
sudo chown -Rf 0:0 /S*/L*/E*
sudo touch -f /L*/E*
sudo touch -f /S*/L*/E*
sudo kextcache -Boot -U /
The upgrade started and rebooted, then got stuck.
I can still get in to the 10.15.2 installation so I set the boot mode to verbose and restarted.
Now it tells me:
** In Memory Panic Stackshot Succeded ** Bytes Traced 30512 **
Willkommen! Melde dich an oder registriere dich.
Um schreiben oder kommentieren zu können, benötigst du ein Benutzerkonto.
Du hast schon ein Benutzerkonto? Melde dich hier hier an.
Jetzt anmelden
Hier kannst du ein neues Benutzerkonto erstellen.
Neues Benutzerkonto erstellen
-
- #1
Hallo zusammen,
ich versuche seit mehreren Tagen Catalina auf meinem Rechner zu installieren.
Währen Clover bootet, (egal ob ich einen Installationsstick mit Catalina starten will oder eine alte OSX Installation von meinem alten Rechner der leider defekt ist) erscheint zuerst eine Reihe mit ++++++++++ und zum Schluss «In Memory Panic Stackshoot Suceeded»
Nach kurzer Zeit startet der Rechner neu. Mein RAM läuft auf 2666 Mhz.
Ich verwende folgendes EFI hier aus dem Forum: siehe Anhang (habe aber auch schon diverse andere EFIs erfolglos getestet).
Ich habe hier schon sämtliche Beiträge über mein Board durchforstet. Leider blieb bei mir alles ohne Erfolg.
Bitte nicht falsch verstehen, ich bin bestimmt nicht so faul und möchte andere Leute für mich arbeiten lassen. Nur bin ich der Verzweiflung nahe. Darum meine Bitte.
Hat ggf. jemand ein Clover EFI oder OpenCore als zip für mich das ich mal testen kann?
So langsam stehe ich kurz davor den Rechner aus dem Fenster segeln zu lassen
Ich bedanke mich schonmal vorab für eure Hilfe.
LG
-
- #2
Hallo und herzlich Willkommen im Forum…
Die EFI kommt mir sehr bekannt vor…
Da ich diese selbst lange Zeit im Einsatz hatte, kann ich mir schwer vorstellen, dass es damit solch ein Problem geben sollte.
An der Stelle wäre spannend zu wissen, welche BIOS-Version bei dir auf dem Board im Einsatz ist und welche Settings dort hinterlegt sind.
Meine nicht mehr ganz aktuellen Einstellungen findest du in der Sammlung von BIOS-Pics aus Februar 2019…
Die wichtigsten Elemente sind damit aber abgedeckt.
-
- #3
Hallo al6042,
zuerst herzlichen Dank für deine Unterstützung.
Ich habe das aktuelle BIOS 1502 installiert und deine Einstellung übernommen.
An der Fehlermeldung hat sich leider nichts geändert.
«Die EFI kommt mir sehr bekannt vor…
» —> da hatte ich gehofft, dass UEFI vom Profi würde mich retten Sonst noch eine Idee?
-
- #4
An welchem PCIe-Slot hast du die RX580 eingebaut?
PCIEX16_1 oder einer der beiden anderen?
-
- #5
Die RX580 steckt in PCIEX16_1
-
- #6
Wieviel RAM-Module nutzt du und in welchen der Slots sind diese eingesetzt?
Hast du auch mal ein anderes Betriebssystem getestet?
-
- #7
Jetzt verwende ich nur noch ein RAM-Modul und habe es komplett in allen Slots getestet. Nun steckt es wieder im ersten Slot.
Linux läuft auf dem System ohne Probleme.
Ich habe gerade die SATA-Ports in Verdacht.
Werde mal umstecken und mich in 20 Minuten zurückmelden.
Danke für deine Hilfe
-
- #8
Hm,
interessant…
Was für Datenträger sind den im System an welchen Ports verbaut?
Zudem wäre wichtig, welche tatsächliche Grund für den Reboot angezeigt wird.
Der «Stackshoot»-Hinweis kommt nämlich am Ende einer langen Liste an Details, die den eigentlichen Ursprung des Fehlers aus dem Bild schubsen.
Ggf. macht hier das erstellen eines Handy-Videos Sinn.
Achte darin auf die letzten Hinweise bevor die lange Litanei anfängt.
Auf der anderen Seite sollten die Einträge in der config.plist dafür sorgen, dass das Bild an der richtigen Stelle stehenbleibt.
-
- #9
An SATA 1 hängt, besser gesagt hing, eine SSD 500GB 840EVO.
Nun habe ich da testweise eine SSD 500GB WD Blue angeschlossen.
Ich habe nun die Maus, Tastatur und den Boot Stick mit Clover direkt ins Board in den USB 2.0 gesteckt.
Nun lässt er mich bis ins Installationsmenü. Das ist doch schon ein Erfolg
Nun lasse ich den Rechner installieren und melde mich zurück, sobald die Installation durchgelaufen ist.
Momentan scheinen nur die USB Ports zu funktionieren, die direkt am Board sind. Ich hatte noch die USB 2.0 und USB 3.0 vom Gehäuse angeschlossen. Am alten Board hatten sie funktioniert.
Ich teste jetzt und melde mich zurück.
-
- #10
Viel Erfolg…
Das Thema USB-Ports müssen wir sowieso im Nachgang angehen, da das ja auch direkt mit dem Bedarf an Front-Buchsen und internen Headern zusammenhängt.
-
- #11
Juhu,
es hat funktioniert. Die Installation ist einwandfrei durchgelaufen
USB 3.0 am Gehäuse funktioniert auch. Nur USB2.0 will noch nicht.
Nun werde ich erstmal alles konfigurieren und testen. Sobald alles läuft gebe ich eine Rückmeldung.
Spätestens morgen hört ihr von mir.
Nochmals vielen Dank an Al6042 für deine Hilfe. Ich hätte den Rechner ohne deine Hilfe nicht mehr zum laufen gebracht.
Die EFI von dir und deine Bios Settings waren ausschlaggebend. Nun läuft es erstmal.
Als Dank habe ich mal eine kleine Spende per Paypal hinterlassen.
Danke und bis bald
-
- #12
Coole Sache…
Vielen lieben Dank.
-
- #13
Gerne doch
Viele Grüße
iPXL
-
Become a Premium Member for $25/year with no ads to improve your community experience.
Lenovo IdeaPad Z500 Boot time error In Memory Panic Stackshot Succeeded
-
Thread startersinamcr7
-
Start dateMay 12, 2020
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
- Joined
- Aug 15, 2019
- Messages
- 80
- Motherboard
-
Lenovo Z500
- CPU
-
Intel Core i7 3632QM
- Graphics
-
Nvidia Geforce GT-635m
- OS X/macOS
-
11.0.x
- Bootloader
-
- Clover (UEFI)
- Mobile Phone
-
- Android
-
#1
Hi there again
I tried to reinstall and give a larger partition size to Mac OS
it installed successfully but after applying DSDT and SSDT patch + Enabling native power management + Disabling Nvidia I placed patched files all in one time and then restarted it to apply all of them but in the boot process it shows this error :
** In Memory Panic Stackshot Succeeded ** Bytes Traced 13840 **
Attempting system restart… MACH Reboot
it passes error first message quickly so I could just record a video of that
and this is its video
Please help to fix this
Last edited: May 12, 2020
- Joined
- Jul 22, 2018
- Messages
- 4,373
- Motherboard
-
Supermicro X11SPA-T
- CPU
-
Intel Xeon W-3275 28 Core
- Graphics
-
2xAMD RX 580 8GB
- OS X/macOS
-
12.0.x
- Bootloader
-
- OpenCore (UEFI)
- Mac
-
- Mac mini
- MacBook Pro
- Mobile Phone
-
- Android
- iOS
-
#2
Hi there again
I tried to reinstall and give a larger partition size to Mac OS
it installed successfully but after applying DSDT and SSDT patch + Enabling native power management + Disabling Nvidia I placed patched files all in one time and then restarted it to apply all of them but in the boot process it shows this error :
** In Memory Panic Stackshot Succeeded ** Bytes Traced 13840 **
Attempting system restart… MACH Reboot
it passes error first message quickly so I could just record a video of that
and this is its video
Please help to fix this
No PR files attached.
- Joined
- Aug 15, 2019
- Messages
- 80
- Motherboard
-
Lenovo Z500
- CPU
-
Intel Core i7 3632QM
- Graphics
-
Nvidia Geforce GT-635m
- OS X/macOS
-
11.0.x
- Bootloader
-
- Clover (UEFI)
- Mobile Phone
-
- Android
-
#3
because I have no access to Mac OS even with USB boot it shows that error and hangs
- Joined
- Jul 22, 2018
- Messages
- 4,373
- Motherboard
-
Supermicro X11SPA-T
- CPU
-
Intel Xeon W-3275 28 Core
- Graphics
-
2xAMD RX 580 8GB
- OS X/macOS
-
12.0.x
- Bootloader
-
- OpenCore (UEFI)
- Mac
-
- Mac mini
- MacBook Pro
- Mobile Phone
-
- Android
- iOS
-
#4
because I have no access to Mac OS even with USB boot it shows that error and hangs
Use any other system and use the USB files for PR.
- Joined
- Aug 15, 2019
- Messages
- 80
- Motherboard
-
Lenovo Z500
- CPU
-
Intel Core i7 3632QM
- Graphics
-
Nvidia Geforce GT-635m
- OS X/macOS
-
11.0.x
- Bootloader
-
- Clover (UEFI)
- Mobile Phone
-
- Android
-
#5
Use any other system and use the USB files for PR.
ok this is the ACPI files(origin + patched)
Attachments
- Joined
- Jul 22, 2018
- Messages
- 4,373
- Motherboard
-
Supermicro X11SPA-T
- CPU
-
Intel Xeon W-3275 28 Core
- Graphics
-
2xAMD RX 580 8GB
- OS X/macOS
-
12.0.x
- Bootloader
-
- OpenCore (UEFI)
- Mac
-
- Mac mini
- MacBook Pro
- Mobile Phone
-
- Android
- iOS
-
#6
ok this is the ACPI files(origin + patched)
PR files doesn’t only includes ACPI sets.
- Joined
- Aug 15, 2019
- Messages
- 80
- Motherboard
-
Lenovo Z500
- CPU
-
Intel Core i7 3632QM
- Graphics
-
Nvidia Geforce GT-635m
- OS X/macOS
-
11.0.x
- Bootloader
-
- Clover (UEFI)
- Mobile Phone
-
- Android
-
#7
PR files doesn’t only includes ACPI sets.
but I can’t boot into mac anyway to access other needed files how can I do this?
should I reinstall it and do all of these and before restart take those files?
- Joined
- Jul 22, 2018
- Messages
- 4,373
- Motherboard
-
Supermicro X11SPA-T
- CPU
-
Intel Xeon W-3275 28 Core
- Graphics
-
2xAMD RX 580 8GB
- OS X/macOS
-
12.0.x
- Bootloader
-
- OpenCore (UEFI)
- Mac
-
- Mac mini
- MacBook Pro
- Mobile Phone
-
- Android
- iOS
-
#8
but I can’t boot into mac anyway to access other needed files how can I do this?
should I reinstall it and do all of these and before restart take those files?
Submit the complete files.
- Joined
- Sep 30, 2020
- Messages
- 3
- Motherboard
-
Lenovo Z500
- CPU
-
i7 3236qm
- Graphics
-
intel hd 4000
- OS X/macOS
-
10.15.x
- Bootloader
-
- Clover (UEFI)
- Mac
-
- iMac
- Mobile Phone
-
- Android
-
#9
hello i would like to know if you managed to install big sur on lenovo z500 with opencore … i currently installed catalina with clover from distro niresh
- Joined
- Sep 30, 2020
- Messages
- 3
- Motherboard
-
Lenovo Z500
- CPU
-
i7 3236qm
- Graphics
-
intel hd 4000
- OS X/macOS
-
10.15.x
- Bootloader
-
- Clover (UEFI)
- Mac
-
- iMac
- Mobile Phone
-
- Android
-
#10
You can send me your EFI folder?
Similar threads
-
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Hello there,
I have the same thing, although I didn’t try Big Sur, but I got it to work both with Monterey & Ventura. Monterey is much more stable compare to Ventura, so I’m sticking with Monterey. The only thing that doesn’t work is the built in mic, and it seems like sleep mode is not really sleeping. Below is the kext that I use:
- Airportitlwm.kext
- AppleALC.kext
- BlueToolFixup.kext
- CPUFriend.kext
- ECEnabler.kext
- IntelBluetoothFirmware.kext
- IntelBTPatcher.kext
- IntelMausi.kext
- Lilu.kext
- NVMEFix.kext
- RTCMemoryFixup.kext
- SMCBatteryManager.kext
- SMCLightSensor.kext
- SMCSuperIO.kext
- USBInectAll.kext
- VirtualSMC.kext
- VoodooI2C.kext
- VoodooI2CHID.kext
- VoodooI2CSynaptics.kext
- VoodooPS2Controller.kext
- WhateverGreen.kext
I have the Intel AX200 wireless card, so if your’s different then try something else.
One thing that I found is start with a minimal list of kexts (just like the guide) just to get it installed. Once it is, then identify the issues then search for solutions.
The recommendation is not using USBInjectAll, but rather map your own, but I didn’t do it right, so I’m using that for now.
Good luck on your hack
-
#1
Hello,
I receive my Mac Pro 2019 (24 thread) and put 6×64 from OWC in it. I started the computer and made OS X update like usual. Since this moment, impossible to boot the computer. It entered in a boot loop.
So I put back the 4×8 Ram from Apple, and boot again… impossible to restart the computer. It boots, the apple logo and progress bar appears and when it reaches 3/4 it restarts.
I called Apple and we tried everything to reboot the computer… impossible. They gonna change my computer, but before send it back I booted it in Detail mode (command + V). The boot sequence crashes (and reboot) after this message : In Memory panic stackshot succeeded ** bytes traced 324304 **
So, do you think it’s connected with a OWC RAM problem (that corrupted the machine during the OS X update) ? Is it a T2 chip problem (Does Apple want we use their expensive RAM ?) ?
Anyway, it’s not very reassuring to ave a problem like that with a 26’000 USD machine.
Does someone else succeed installing OWC Ram into the new Mac Pro ?
Best
Robin
PS : sorry for my English, French is my mother tongue
-
#2
Sorry to hear your problem, that’s a bummer.
But I really don’t get why you would spend $26000 on a mac and then get inferior ram to save $2500…
If I get a new mac, I will definitely stick with Apple components initially to ensure compatibility.
-
#3
Sorry to hear your problem, that’s a bummer.
But I really don’t get why you would spend $26000 on a mac and then get inferior ram to save $2500…
If I get a new mac, I will definitely stick with Apple components initially to ensure compatibility.
So you could imagine the problem comes from the RAM ?
Quu
macrumors 68040
-
#4
My opinion, your CPU isn’t seated correctly. Some of the pins that connect to the memory are not making full or proper contact causing the issue.
-
#5
My opinion, your CPU isn’t seated correctly. Some of the pins that connect to the memory are not making full or proper contact causing the issue.
Assembled in the USA. ?
-
#6
I had a very similar problem, but with a new 2019 i9 iMac (€4,000). Continuous restarts until it finally died. Even putting the original RAM did not solve the problem. I returned it for the money, bought a powerful laptop PC and did not look back (same GB5 score as the base Mac Pro 2019). Now I am a happy Windows 10 Pro user .
-
#7
TBH it’s BS isn’t it.
If you bought a Ferrari, it would arrive perfect without any issue.
If your spending upwards of 10-30k on something it should be perfect without a doubt…. ?
Since Steve passed, standards have plummeted in all latest hardware.
-
#8
In china… European Mac Pro are assembled in China.
[automerge]1577706638[/automerge]
TBH it’s BS isn’t it.
If you bought a Ferrari, it would arrive perfect without any issue.
If your spending upwards of 10-30k on something it should be perfect without a doubt…. ?
Since Steve passed, standards have plummeted in all latest hardware.
Indeed but RAM is RAM, there isn’t really «magic» behind this. I wouldn’t change the processor but RAM upgrade is a standard.
-
#9
Exactly, so there shouldn’t be a problem with your setup……
-
#10
What is «TBH it’s BS» ? as poor English speaker I need an English class
-
#11
What is «TBH it’s BS» ? as poor English speaker I need an English class
![;-)]()
‘To be honest it’s bull s@#t’
-
#12
TBH it’s BS isn’t it.
If you bought a Ferrari, it would arrive perfect without any issue.
If your spending upwards of 10-30k on something it should be perfect without a doubt…. ?
No amount of money can change reality. Wear and tear still happens, human mistakes happen, etc.
-
#13
I started the computer and made OS X update like usual.
What does this mean? What exactly did you do?
-
#14
No amount of money can change reality. Wear and tear still happens, human mistakes happen, etc.
That is true, but unacceptable for a purchase of this amount, many people buy Apple products due to the high quality and being problem free (come on Apple get it together).
If it’s not Apple it‘s Samsung rushing out products and every time having to fix something.
Every product I have bought (iphones / iPods / ipads / g4 / g5 / macpro) have been perfect.
It is only during the past 7-8 years it seems every product release has a recall or problem.
-
#15
Every product I have bought (iphones / iPods / ipads / g4 / g5 / macpro) have been perfect.
It is only during the past 7-8 years it seems every product release has a recall or problem.
You don’t have a long enough memory. My 2005 powerbook G4 — repair nightmare. I sent it in for keyboard (3X), screen, RAM slot, fan repairs, all within the course of its 3 year warranty. Then my 2008 MBP had to get sent back twice for a faulty NVIDIA GPU — this is the reason I avoid NVIDIA GPUs like the plague. No products are trouble free, but in my experience the newer machines are significantly higher quality than the older kit. For instance, my 2013 MBP has only needed one GPU replacement! At this rate my next MBP (probably a 2020) won’t need to replace the GPU at all!
-
#16
What does this mean? What exactly did you do?
Hello, I just launched the Update from OS X. The normal update.
-
#17
I must be extremely lucky then…… ?
I would be seriously pissed though if I received a macpro in December for 10k+ and had issues I am reading here…..?
-
#18
I must be extremely lucky then…… ?
I would be seriously pissed though if I received a macpro in December for 10k+ and had issues I am reading here…..?
Yeah, I’m trying my best to hold off getting a new MP for the next 6-12 months to work out some of the infant mortality manufacturing bugs. Waiting is painful, but I know getting a new machine with hardware issues would be infuriating.
-
#19
cmon people lets not making broad sweeping statements condemning apple for quality issues from a few incidents, when you don’t even have an idea of the number of people with flawless machines
and beyond satisfied customers with flawless machines, there are those people that have ordered 8 core machines, and received 16, and 24 cores by accident. When they contact apple, apple either offers them a refund, or lets them choose to keep the machine.
Last edited: Dec 30, 2019
-
#20
Yeah, I’m trying my best to hold off getting a new MP for the next 6-12 months to work out some of the infant mortality manufacturing bugs. Waiting is painful, but I know getting a new machine with hardware issues would be infuriating.
That applies to everything including MacOS.
Unless people absolutely need a new hardware or software release, it’s alway better to wait and not be a beta tester.
Aboo
macrumors 6502a
-
#21
cmon people lets not making broad sweeping statements condemning apple for quality issues from a few incidents, when you don’t even have an idea of the number of people with flawless machines
and beyond satisfied customers with flawless machines, there are those people that have ordered 8 core machines, and received 16, and 24 cores by accident. When they contact apple, apple either offers them a refund, or lets them choose to keep the machine.
I’ve heard of one YouTuber getting a significantly upgraded machine but are there others?
-
#22
cmon people lets not making broad sweeping statements condemning apple for quality issues from a few incidents, when you don’t even have an idea of the number of people with flawless machines
and beyond satisfied customers with flawless machines, there are those people that have ordered 8 core machines, and received 16, and 24 cores by accident. When they contact apple, apple either offers them a refund, or lets them choose to keep the machine.
REALLY……… wow now that would make a few people’s xmas…
Unless the 8 core has gone to someone who ordered more Cores, and the deliveries have been mixed up.
You are right though.
Most of the issues I have read are related to non-standard components being installed to save a buck.
In about 6 months if I have the urge I would get all Apple components in a build.
-
#23
Most of the issues I have read are related to non-standard components being installed to save a buck.
In about 6 months if I have the urge I would get all Apple components in a build.
You know. It’s not to save «a buck», but more than 3000 USD. And I didn’t save a buck by choosing two Dual Radio Pro Vega II. RAM is RAM, OWC makes RAM for Apple computer since long time.
If Apple had wrote : «Use only our RAM», I wouldn’t choose OWC RAM. But it’s not the case, so this one should work (in fact it worked until the OS X update).
Robin
-
#24
Hello,
I receive my Mac Pro 2019 (24 thread) and put 6×64 from OWC in it. I started the computer and made OS X update like usual. Since this moment, impossible to boot the computer. It entered in a boot loop.
So I put back the 4×8 Ram from Apple, and boot again… impossible to restart the computer. It boots, the apple logo and progress bar appears and when it reaches 3/4 it restarts.
I called Apple and we tried everything to reboot the computer… impossible. They gonna change my computer, but before send it back I booted it in Detail mode (command + V). The boot sequence crashes (and reboot) after this message : In Memory panic stackshot succeeded ** bytes traced 324304 **
So, do you think it’s connected with a OWC RAM problem (that corrupted the machine during the OS X update) ? Is it a T2 chip problem (Does Apple want we use their expensive RAM ?) ?
Anyway, it’s not very reassuring to ave a problem like that with a 26’000 USD machine.
Does someone else succeed installing OWC Ram into the new Mac Pro ?
Best
Robin
PS : sorry for my English, French is my mother tongue
It’s possible the ram installation went poorly, static damage, etc? Could have caused Mainboard problems?
Have you tried booting from internet recovery mode to wipe the system and start again? Maybe the update went badly. To manually start up from macOS Recovery over the Internet, press and hold Option-Command-R or Shift-Option-Command-R at startup.
If this fails, have you tried running diagnostics to see if anything comes up? https://support.apple.com/en-us/HT202731
-
#25
It’s possible the ram installation went poorly, static damage, etc? Could have caused Mainboard problems?
Have you tried booting from internet recovery mode to wipe the system and start again? Maybe the update went badly. To manually start up from macOS Recovery over the Internet, press and hold Option-Command-R or Shift-Option-Command-R at startup.
If this fails, have you tried running diagnostics to see if anything comes up? https://support.apple.com/en-us/HT202731
Hello,
Yes I tried booting from internet recovery mode. But nothing changed, it didn’t let me install anything because it rebooted before to reach Install Menu. I also tried the diagnostics, and the result was positif (no problem).
Maybe it was really a hardware problem from the beginning.
-
#1
All-
I’m really struggling with this update. I was initially running Sierra (which was rock solid) and took the plunge to update directly to Catalina. The update appeared to succeed with the exception that sound and wifi were broken. I managed to snatch defeat from the jaws of victory when I attempted to fix those issues, and after multiple failed attempts I opted for a clean install. I have yet to get Catalina to boot on this system again, and I can’t event get it to install. Things have now degenerated to the point that Clover loads, it attempts to boot the installer and immediately crashes with the error «In Memory Panic Stackshot Succeeded ** Bytes Traced 33424.» I’m really at a loss where to go from here, and I don’t know if I have a BIOS problem, a hardware problem, or a software problem. Any suggestions would be greatly appreciated. Thanks!
-
stackshot.jpg
317.5 KB
· Views: 1,023
-
#2
It appears this was a BIOS problem. I reinstalled the BIOS and reset CMOS. After that, I was able to boot the installer. Still can’t get Catalina to finish the install, but that is a topic for another thread.
-
#3
Hey! What did you change in BIOS exactly? I am having the exact same problem and I just cannot get past it. Did the CMOS reset, optimized defaults, changed couple settings in BIOS like VT-d etc and it still won’t let me get past this.
-
#4
Hey! What did you change in BIOS exactly? I am having the exact same problem and I just cannot get past it. Did the CMOS reset, optimized defaults, changed couple settings in BIOS like VT-d etc and it still won’t let me get past this.
Hello, do you path » Ec Spoofing » dsdt for desktop? If yes please check your Fake cpuid. If not please try path your «ec spoofing» catalina dsdt for desktop.
-
#5
It could be conflict between VirtualSMC and FakeSMC (check that you have only one of them in both EFI and /Library/Extensions) and in my case it has been caused by obsolete sensor kext (I used legacy NVidia sensor kext for very old GPU and then after graphic card upgrade the system started crashing)
-
#6
Hello, do you path » Ec Spoofing » dsdt for desktop? If yes please check your Fake cpuid. If not please try path your «ec spoofing» catalina dsdt for desktop.
Fake CPUID? What for is that necessary? Didn’t read anything about that in the vanilla guide either. I have done that EC part BUT it gives me this error (see picture attached). Sorry for hijacking this thread.
-
#7
Hey, I’m having the same problem. Did this guy ever find a fix?
I am able to get Catalina running but not Big Sur. After running the docker command, I see the bootloader, but when I select macOS Base System, the process gets stuck on In memory panic stackshot succeeded.
uname -a
; echo «${DISPLAY}»
; echo 1 | sudo tee /sys/module/kvm/parameters/ignore_msrs
; grep NAME /etc/os-release
; df -h .
; qemu-system-x86_64 —version
; libvirtd —version
; free -mh
; nproc
; egrep -c ‘(svm|vmx)’ /proc/cpuinfo
; ls -lha /dev/kvm
; ls -lha /tmp/.X11-unix/
; ps aux | grep dockerd
; docker ps | grep osx
; grep «docker|kvm|virt» /etc/group
Linux xps-box 5.10.68-1-MANJARO #1 SMP PREEMPT Wed Sep 22 12:29:47 UTC 2021 x86_64 GNU/Linux
:0
1
NAME="Manjaro Linux"
PRETTY_NAME="Manjaro Linux"
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/luks-e41457f4-a9e3-4f31-87e4-8365507c3181 452G 268G 161G 63% /
QEMU emulator version 6.1.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
libvirtd (libvirt) 7.8.0
total used free shared buff/cache available
Mem: 15Gi 10Gi 299Mi 1.8Gi 4.0Gi 2.0Gi
Swap: 16Gi 4.5Gi 12Gi
8
16
crw-rw-rw- 1 root kvm 10, 232 Nov 13 13:51 /dev/kvm
total 0
drwxrwxrwt 2 root root 80 Oct 31 09:35 .
drwxrwxrwt 29 root root 800 Nov 13 14:33 ..
srwxr-xr-x 1 adi adi 0 Oct 31 09:35 X0
srwxr-xr-x 1 adi adi 0 Oct 31 09:35 X1
root 547362 0.1 0.2 2418796 37588 ? Ssl 13:37 0:06 /usr/bin/dockerd -H fd://
adi 698413 0.0 0.0 6496 2308 pts/4 S+ 14:36 0:00 grep dockerd
209c6b81bd47 sickcodes/docker-osx:big-sur "/bin/bash -c 'sudo …" 44 minutes ago Up 44 minutes 0.0.0.0:50923->10022/tcp, :::50923->10022/tcp festive_grothendieck
6895b58f973a sickcodes/docker-osx:latest "/bin/bash -c 'sudo …" 50 minutes ago Up 50 minutes 0.0.0.0:50922->10022/tcp, :::50922->10022/tcp charming_moser
kvm:x:992:adi
docker:x:963:adi
libvirt:x:960:adi
I’ve gone through the troubleshooting section in README. I also haven’t seen this problem mentioned in any of the issues.
docker run -it
--device /dev/kvm
-p 50922:10022
-v /tmp/.X11-unix:/tmp/.X11-unix
-e "DISPLAY=${DISPLAY:-:0.0}"
sickcodes/docker-osx:big-sur
I solved the problem! it is the igpu problem, i just disabled the igpu and connect the display cable to my Rx 5700XT, then succeed to install the OS Catalina.
Thanks all 
Hello all,
This is my first time to build hackintosh and i have this «memory panic stackshot succeeded» Problembefore load in to MacOS Catalina installation, and my Clover EFI bootloader is 5103 versionPlease tell me how to fix it, thanks
My Build :i9-9900KGigabyte Aorus Z390 Pro Wifi (Bios F10)Samsung 970 Pro 512Gb M.2 SSDRx 5700 XTCorsair vengeance 3200mhz 8gb ram x 4
https://preview.redd.it/apzz86xa6ha41.jpg?width=1200&format=pjpg&auto=webp&s=49c3af2cacfd897b545341ca5da706841e093e58
37 minutes ago, MaLd0n said:
bootloader and kexts is updated?
Yes, Clover is upgraded to current version 5127. Kexts are a mix of ne ones and old ones.
So now I upgraded every kext to the latest version. Removed what I guess could be problematic, and left only these:
It panicked again, but the issue seems a different one. This time I was able to copy the output:
Quote
panic(cpu 2 caller 0xffffff800ddefa76): Kernel trap at 0xffffff80106313bd, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000028, CR3: 0x0000000023bbc000, CR4: 0x00000000001626e0
RAX: 0x0000000000000000, RBX: 0xffffff937ac3dd80, RCX: 0xffffffa07cd13cbc, RDX: 0x0000000000000001
RSP: 0xffffffa07cd13c60, RBP: 0xffffffa07cd13ca0, RSI: 0x00000000f0ffffff, RDI: 0xffffff937ac3dd80
R8: 0x0000000000000001, R9: 0x0000000000000030, R10: 0x0000000000000001, R11: 0x0000000000000070
R12: 0x0000000000000000, R13: 0x0000000000000000, R14: 0x0000000000000000, R15: 0xffffffa07cd13cbc
RFL: 0x0000000000010282, RIP: 0xffffff80106313bd, CS: 0x0000000000000008, SS: 0x0000000000000000
Fault CR2: 0x0000000000000028, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 1Backtrace (CPU 2), Frame : Return Address
0xffffffa07cd13680 : 0xffffff800dcbc66d mach_kernel : _handle_debugger_trap + 0x3dd
0xffffffa07cd136d0 : 0xffffff800ddff073 mach_kernel : _kdp_i386_trap + 0x143
0xffffffa07cd13710 : 0xffffff800ddef6aa mach_kernel : _kernel_trap + 0x55a
0xffffffa07cd13760 : 0xffffff800dc61a2f mach_kernel : _return_from_trap + 0xff
0xffffffa07cd13780 : 0xffffff800dcbbf0d mach_kernel : _DebuggerTrapWithState + 0xad
0xffffffa07cd138a0 : 0xffffff800dcbc1f8 mach_kernel : _panic_trap_to_debugger + 0x268
0xffffffa07cd13910 : 0xffffff800e4bee1a mach_kernel : _panic + 0x54
0xffffffa07cd13980 : 0xffffff800ddefa76 mach_kernel : _sync_iss_to_iks + 0x2c6
0xffffffa07cd13b00 : 0xffffff800ddef75d mach_kernel : _kernel_trap + 0x60d
0xffffffa07cd13b50 : 0xffffff800dc61a2f mach_kernel : _return_from_trap + 0xff
0xffffffa07cd13b70 : 0xffffff80106313bd com.apple.iokit.IOPCIFamily : __ZN17IOPCIConfigurator17findPCICapabilityEP16IOPCIConfigEntryjPj + 0x41
0xffffffa07cd13ca0 : 0xffffff8010622ff5 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge25extendedFindPCICapabilityE17IOPCIAddressSpacejPy + 0x39
0xffffffa07cd13cd0 : 0xffffff8010621c28 com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge8probeBusEP9IOServiceh + 0x1bc
0xffffffa07cd13d60 : 0xffffff801061e3ed com.apple.iokit.IOPCIFamily : __ZN11IOPCIBridge5startEP9IOService + 0xcb
0xffffffa07cd13d90 : 0xffffff800ecaa7a8 com.apple.driver.AppleACPIPlatform : __ZN12AppleACPIPCI5startEP9IOService + 0x10c
0xffffffa07cd13dd0 : 0xffffff800e3ef09b mach_kernel : __ZN9IOService14startCandidateEPS_ + 0xeb
0xffffffa07cd13e40 : 0xffffff800e3eec46 mach_kernel : __ZN9IOService15probeCandidatesEP12OSOrderedSet + 0xce6
0xffffffa07cd13ef0 : 0xffffff800e3eddcf mach_kernel : __ZN9IOService14doServiceMatchEj + 0x30f
0xffffffa07cd13f50 : 0xffffff800e3f0b46 mach_kernel : __ZN15_IOConfigThread4mainEPvi + 0x186
0xffffffa07cd13fa0 : 0xffffff800dc6113e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8010617000->0xffffff801063efff
com.apple.driver.AppleACPIPlatform(6.1)[D5E73559-87FF-3A4D-A884-3C734F0BB103]@0xffffff800ec8e000->0xffffff800ed04fff
dependency: com.apple.driver.AppleSMC(3.1.9)[30ACBB00-67A3-36BD-AF95-1E6F0CB38447]@0xffffff800f290000->0xffffff800f2a8fff
dependency: com.apple.iokit.IOACPIFamily(1.4)[65A1D60D-F9AF-37E7-B854-4127FBB3172A]@0xffffff80100d2000->0xffffff80100d3fff
dependency: com.apple.iokit.IOPCIFamily(2.9)[A18ACD60-A811-3624-B50D-4F929836EE79]@0xffffff8010617000->0xffffff801063efffProcess name corresponding to current thread: Unknown
Boot args: npci=0x3000 -v keepsyms=1 debug=0x100 alcid=17 root-dmg=file:///BaseSystem/BaseSystem.dmgMac OS version:
Not yet setKernel version:
Darwin Kernel Version 20.1.0: Sat Oct 31 00:07:11 PDT 2020; root:xnu-7195.50.7~2/RELEASE_X86_64
Kernel UUID: 84C6DC45-6B02-335F-9439-5D2A9BC385A4
KernelCache slide: 0x000000000da00000
KernelCache base: 0xffffff800dc00000
Kernel slide: 0x000000000da10000
Kernel text base: 0xffffff800dc10000
__HIB text base: 0xffffff800db00000
System model name: MacPro6,1 (Mac-F60DEB81FF30ACF6)
System shutdown begun: NO
Panic diags file unavailable, panic occurred prior to initialization
Hibernation exit count: 0System uptime in nanoseconds: 4520421733
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000000010f1581d0
Sleep : 0x0000000000000000 0x0000000000000000 0x0000000000000000
Wake : 0x0000000000000000 0x000000185a821930 0x0000000000000000
last started kext at 3711014651: com.insanelymac.RealtekRTL8111 2.2.2 (addr 0xffffff8011bf1000, size 458752)
loaded kexts:
com.insanelymac.RealtekRTL8111 2.2.2
ru.joedm.SMCSuperIO 1.1.9
as.acidanthera.voodoo.driver.PS2!C 2.1.9
as.vit9696.SMCProcessor 1.1.9
as.vit9696.VirtualSMC 1.1.9
com.rehabman.driver.USBInjectAll 0.7.6
as.vit9696.WhateverGreen 1.4.5
as.vit9696.!AALC 1.5.5
as.vit9696.Lilu 1.5.0
>!AAHCIPort 346
@private.KextAudit 1.0
>!AHPET 1.8
>!AACPIButtons 6.1
>!ARTC 2.0
>!ASMBIOS 2.1
>!AAPIC 1.7
>!A!ICPUPowerManagementClient 222.0.0
@!ASystemPolicy 2.0.0
@nke.applicationfirewall 310
|IOKitRegistryCompatibility 1
|EndpointSecurity 1
>!A!ICPUPowerManagement 222.0.0
>usb.!UEHCIPCI 1.2
>usb.!UEHCI 1.2
|IOAHCI!F 294
|IONVMe!F 2.1.0
>!AEFINVRAM 2.1
>!AEFIRuntime 2.1
|IOHID!F 2.0.0
$!AImage4 3.0.0
|IOTimeSync!F 900.11
|IONetworking!F 3.4
>DiskImages 493.0.0
|IO!B!F 8.0.1f5
|IOReport!F 47
|IO!BPacketLogger 8.0.1f5
$quarantine 4
$sandbox 300.0
@kext.!AMatch 1.0.0d1
|CoreAnalytics!F 1
>!ASSE 1.0
>!AKeyStore 2
>!UTDM 511.40.9
|IOUSBMass!SDriver 184.40.6
|IOSCSIBlockCommandsDevice 436.40.6
|IO!S!F 2.1
|IOSCSIArchitectureModel!F 436.40.6
>!AMobileFileIntegrity 1.0.5
@kext.CoreTrust 1
>!AFDEKeyStore 28.30
>!AEffaceable!S 1.0
>!ACredentialManager 1.0
>KernelRelayHost 1
|IOUSBHost!F 1.2
>!UHostMergeProperties 1.2
>usb.!UCommon 1.0
>!ABusPower!C 1.0
>!ASEPManager 1.0.1
>IOSlaveProcessor 1
>!AACPIPlatform 6.1
>!ASMC 3.1.9
|IOPCI!F 2.9
|IOACPI!F 1.4
>watchdog 1
@kec.pthread 1
@kec.corecrypto 1.0
@kec.Libm 1
Edited December 19, 2020 by ChristoAta