Archive for the 'Apple' Category

Fixing Radeon5700/5500 with MacOS 10.15.5

Macos 10.15.5 update caused kernel panics for owners of many Radeon Navi cards. Your card have to be POSTed (aka inited) at system boot to hit this issue.

So if you use flashed card on MacPro5,1 or you use the card in hackintosh (init is done by UEFI) then you might hit it pretty well

It could easily be fixed, you need to downgrade just one kext (kernel extension) to make things working again

First of all, you can still boot system without facing kernel panic in safe mode (hold shift on boot for mac, -x boot-arg on hackintoshes)

Get this kext from macos 10.15.4  – /System/Library/Extensions/AMDRadeonX6000HWServices.kext

Not posting it here as it would be pirating

steps to do

  1. disable csr if enabled
  2. boot 10.15.5 in safe mode
  3. open command line and type next command:
  4. mount -uw /
  5. sudo mv /System/Library/Extensions/AMDRadeonX6000HWServices.kext /Users/YourUserName/Desktop (replace YourUserName with your user name)
  6. sudo cp -a /Path/Where/You/Downloaded/Kext/From/10.15.4/AMDRadeonX6000HWServices.kext  /System/Library/Extensions/
  7. sudo chown -R 0:0 /System/Library/Extensions/AMDRadeonX6000HWServices.kext
  8. sudo chmod -R 755 /System/Library/Extensions/AMDRadeonX6000HWServices.kext
  9. sudo xattr -r -d /System/Library/Extensions/AMDRadeonX6000HWServices.kext
  10. sudo touch /System/Library/Extensions/AMDRadeonX6000HWServices.kext /System/Library/Extensions
  11. Now reboot, you can reenable csr (if it was enabled before) once your card starts working, as the kext we copied is original unmodified kext from apple.

Bringing back 32-bit apps to life

I have found out that 32-bit apps support in Catalina was disabled but not completely removed

Current state is enough to run some console 32-bit apps in catalina

to have it run this command:

sudo nvram boot-args=”no32exec=0″

if one wants more, like gui app, need to use some libs from mojave probably.

next is some output from console

$ uname -a

Darwin Macs-Mac-Pro.local 19.0.0 Darwin Kernel Version 19.0.0: Wed Sep 25 20:18:50 PDT 2019; root:xnu-6153.11.26~2/RELEASE_X86_64 x86_64

$ file EfiDecompress.macosx

EfiDecompress.macosx: Mach-O executable i386

$ ./EfiDecompress.macosx

EfiDecompress v1.1 -Efi File Decompress Utility

Copyright (c) 2005-2006 Intel Corporation. All rights reserved.

Usage: EfiDecompress Inputfile Outputfile

$ otool -L EfiDecompress.macosx


/usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)

/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.3)

$ file /usr/lib/libSystem.B.dylib

/usr/lib/libSystem.B.dylib: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit dynamically linked shared library x86_64] [i386:Mach-O dynamically linked shared library i386]

/usr/lib/libSystem.B.dylib (for architecture x86_64): Mach-O 64-bit dynamically linked shared library x86_64

/usr/lib/libSystem.B.dylib (for architecture i386): Mach-O dynamically linked shared library i386

$ nvram boot-args

boot-args no32exec=0


here is how one can try to run 32-bit gui app, can’t say it’s working very well

DYLD_ROOT_PATH=/Volumes/Macintosh\ SSD/ ./CrossOver


DYLD_ROOT_PATH should specify root volume for macos mojave

Sometimes Mac break

Yeaterday I booted old Catalina DP on MY NMP, it showed update – DP beta 11.
I thought, ok, lets see.

Update got downloaded… reboot…. firmware update… reboot… mac is dead.

Mac doesn’t boot anymore.
It just starts up, no bootchime (and I have it disabled anyway), after like 5 mins it lights up connected display, displaying black screen on it (even tho at proper resolution)

That’s it, no boot, wait many hours, nothing changes.

PRAM reset – didn’t help. SMC reset – didn’t help..

A secret way to do pram reset – didn’t help. (take out cmos battery, it clears RTC, mac will boot in “EFI_BOOT_WITH_DEFAULT_PARAMETERS” mode next time, ignoring NVRAM on startup, at least in PEI mode)

Cool update I thought. At least I can swap ssd to macmini and get my data back.

The final solution was to get access to eeprom, it’s on bottom pcb, inside NMP.

Using CH341A/AsProgrammer (thanks Alex for CH341A), I was able to read and write the EEPROM chip with main bios rom.

I tried to make pram reset in hard way, wiping out content of two VSS partitions inside efi ( they hold nvram arguments).
That helped, mac booted.

Appearently it’s a bug in new fw of parsing some nvram params.

Apple, Wanna that firmware ? I still have that dump.

P.S. this is how mac looked for few days, still can boot it this way. bios rom IC is on the other side of pcb you can see.


A way to freeze 10.14.2

Just enter this in command line then type in your admin user password:

sudo vmmap -v 1

After some short time the system will completely hard freeze

EFI BIOS of Imac Pro leaked some time ago

A bit old news, but
With some of DP for high sierra Apple has accidentially released fw for imac pro.
You can find it here –

Why I think it’s imac pro ? dsdt has name of model – imac. ALso there is uefi driver for amd radeon vg10.

That matches imac pro.

few other interesting things I’ve found: apple secure boot and microsoft secure boot support. first time spi flash rom is 16 mb (prevuously it waws 8 mb). voice over uefi driver (siri on separate cpu will work even in uefi ?)

Come on Apple, improve your 3d drivers

Few tests with same config (R9 290x, MP3,1, 2×2.8 GHZ cpu) in Unigine Valley. I know this cpu sucks for valley, but it’s enough to compare different OS/drivers.

(Read the article)

OSX 10.11 DP5 disables rootless=0 option

Since osx 10.11 dp5 (15A235d) it’s now not possible to disable rootless security by using boot argument rootless=0.

you now have to boot into osx recovery and disable system integrity protection from security settings there.

El Capitan Obvio

Collecting some information in this post:

iMac (Mid 2007 or newer) • MacBook Air (Late 2008 or newer) • MacBook (Late 2008 Aluminum, or Early 2009 or newer) • Mac mini (Early 2009 or newer) • MacBook Pro (Mid/Late 2007 or newer) • Mac Pro (Early 2008 or newer) • Xserve (Early 2009)

kext-dev-mode still works

Nvidia driver is….. still 310.42.05a43 , no love for maxwell

New root-less security is based on sandboxing shell and its commands, so you can’t edit system files even if you a root and file has 755 mode

files are editable if you boot yosemite

To disable rootless mode set boot argument rootless=0

You can still set boot-args with sudo nvram even in rootless mode.

No Metal for pre-Fermi nvidia cards

OpenGL still at level 4.1

What’s inside new rMBP ?

Found a screenshot of new rMBP with amd card inside:

Device-id is 6821, looking at it’s closest brother 6820 –

It’s mobile variant of cape verde chip that’s found in radeon hd 7770.
640 shaders, 16 ROPs, 40 TMUs, 128-bit bus.

And, just x8 pcie ?

Well, x8 pcie 3.0 would be equal to x16 pcie 2.0, but why?

The cpu has total of 16 pcie 3.0 lanes, x8 to gpu, two of x4 to TB controllers?

gtx 750ti is much faster than hd7770, cosuming less power, if only apple would include gm107 into new rmbps…

If OSX 10.10 update fails for you…

With next message:

“This partition map modification would make a windows partition unbeatable”

It means that some Apple programmers are lazy dumbasses.

Here is how to fix it: you need to backup current mbr on your OSX drive, remove any partitions in mbr except the first one with type EE (so disk will look like pure gpt disk). Install osx update. Then restore mbr from backup. Then show middle finger to Apple (it’s not that hard to fix for lazy apple programmers)

you can do it with gptsync or with fdisk and dd.

It happens because of missing recovery volume. I miss recovery volume because I had to restore osx partition from TM backup. HFS+ isn’t that great and can be easily crashed with few resets.
P.S. it’s all for MAC, not HACK (even tho hacks ccan use that way too). Owners of genuine Macs have to mess with it. It’s shame !

Next Page »