[SOLVED] Stuck at IOConsoleUsers

[Val10M]

My system:
MB: GA-Z170MX-Gaming 5
CPU: i7-6700K
RAM: Crucial Ballistix Sport LT 16GB x 2
GPU: XFX Radeon R9 280x
SSD: 850 EVO M.2 250GB
HDD: Hitachi 2TB x 2

Working on my first Hackintosh. I installed Sierra without any glitch but when rebooting, the system is stuck at the Apple logo at 3/4 of the way on the progress bar. When running in verbose mode, the system stops at:
IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, sm 0x0 (see attached screenshot)
I have tried different BIOS settings without any success. I disabled Serial Port (which seems to help with some but not me). Any help from you guys would be much appreciated. Thank you.

 

[jonothonroyes]

I'm having the same issue, it's being stopped at the exact same line.

 

[BreBo]

@Val10M, @jonothonroyes, please update your profile (personal details) with your build (Motherboard, CPU and Graphics Card).

Profiles need to contain at least your primary system to assist others with helping you.

 

[arkspeed]

uncheck Inject Nvidia to Inject Intel, and see if you can boot.

 

[Val10M]

After more research, I found out that the problem was my XFX R9 280x video card. I had to load the vbios for it to boot. Thanks for everyone's suggestions.

 

[TomRao]

Hi, @Val10M. This is my first Hackintosh and I have exactly the same issue with you. Could you tell me how to solve this issue in details? Thank you very much!

 

[Val10M]

@TomRao, read the following post on Radeon video cards: https://www.tonymacx86.com/threads/radeon-compatibility-guide-ati-amd-graphics-cards.171291/
For my XFX R9 280x card, I had to download the latest Asus vbios and renamed it to 1002_6798.rom. I copied this to EFI/CLOVER/ROM directory. When booting up into Clover, go to options, select graphics, select Inject ATI and Load Vbios. This was the fix. Once you are in MacOS Sierra for the first time, mount EFI of your new drive and move that same rom file into the same directory. Use clover configurator to Inject ATI and Load vbios in your config file. There have been a lot of threads about this problem. Just have to do some digging to find the answer.

 

[TomRao]

@TomRao, read the following post on Radeon video cards: https://www.tonymacx86.com/threads/radeon-compatibility-guide-ati-amd-graphics-cards.171291/
For my XFX R9 280x card, I had to download the latest Asus vbios and renamed it to 1002_6798.rom. I copied this to EFI/CLOVER/ROM directory. When booting up into Clover, go to options, select graphics, select Inject ATI and Load Vbios. This was the fix. Once you are in MacOS Sierra for the first time, mount EFI of your new drive and move that same rom file into the same directory. Use clover configurator to Inject ATI and Load vbios in your config file. There have been a lot of threads about this problem. Just have to do some digging to find the answer.

Your suggestion and links are great helps to me! I'm trying to work it out with these though it may takes me a lot of time. Thank you very much!

 

[daksi99]

Hi, I have same issue but with nvidia after update to 10.12.4. After 3 or 4 restarts and stuck on same problem? Sorry for my English! Any help?

 

[absurdio]

@TomRao, read the following post on Radeon video cards: https://www.tonymacx86.com/threads/radeon-compatibility-guide-ati-amd-graphics-cards.171291/
For my XFX R9 280x card, I had to download the latest Asus vbios and renamed it to 1002_6798.rom. I copied this to EFI/CLOVER/ROM directory. When booting up into Clover, go to options, select graphics, select Inject ATI and Load Vbios. This was the fix. Once you are in MacOS Sierra for the first time, mount EFI of your new drive and move that same rom file into the same directory. Use clover configurator to Inject ATI and Load vbios in your config file. There have been a lot of threads about this problem. Just have to do some digging to find the answer.

Hey, @Val10M.

I'm stuck at the same IOConsoleUsers line, but I've got a GTX 660 in there. Your fix sounds like it'd be specific to ATI cards, is that right? I've got the latest NVIDIA web drivers and all. Same problem, though.