Jump to content
1561 posts in this topic

Recommended Posts

@glasgood did you ever look into and Unlock the 0xE2 MSR register on your board?

 

I've eneded up reverting back to the old EFI now as until I can find a resolve for the cold boot after wake from sleep problem i cant be risking my system from a disaster. I'm gutted because I'm loving the way the new EFI works but i have to go with fully stable over problematic. :(

@glasgood Mald0n also generated a DSDT for my build, and I'm curious if it is any different than the one you were given (aside from cosmetic PCI names). Would be interesting to know how these differ given we are both running the same board with same bios. Maybe any differences could shed some light on why others like @AudioGod are having issues - or why I need that custom SSDT to fix my ACPI errors.

 

Not sure how easy it is to spot differences in DSDT files, but I don't think I have the knowledge to do that yet :P

 

tasc-DSDT.aml

33 minutes ago, tasc said:

@glasgood Mald0n also generated a DSDT for my build, and I'm curious if it is any different than the one you were given (aside from cosmetic PCI names). Would be interesting to know how these differ given we are both running the same board with same bios. Maybe any differences could shed some light on why others like @AudioGod are having issues - or why I need that custom SSDT to fix my ACPI errors.

 

Not sure how easy it is to spot differences in DSDT files, but I don't think I have the knowledge to do that yet :P

 

tasc-DSDT.aml

Il give it a in a moment buddy to see if it has and different effect to my system. Should I try it with your ssdt too?

1 hour ago, AudioGod said:

Il give it a in a moment buddy to see if it has and different effect to my system. Should I try it with your ssdt too?

 

I went ahead and disassembled both of our DSDTs to see if the differences would be easy to spot, and actually they are fairly easy to see when using a diff tool. I can see glasgood has the broadcom wireless adapter in his, while I do not use any wireless card. It looks like mald0n renamed my SAT0 to SATA and GIGE to GLAN, but those are patched in clover anyways so should result in the same thing.

 

There's only a couple other areas that differ - I can see where glasgood added in the EC power patch and the wake patch, and I have an additional display section probably due to my nvidia card in slot 2. Other than that there a just a few discrepancies:

 

(-) lines are my DSDT, (+) lines are glasgood DSDT

+    External (UMAP, IntObj)    // (from opcode)

-    OperationRegion (GNVS, SystemMemory, 0x3936E000, 0x0866)
+    OperationRegion (GNVS, SystemMemory, 0x3E484000, 0x0866)

-    Name (PNVB, 0x39421B98)
+    Name (PNVB, 0x3E557B98)

-    OperationRegion (BNVS, SystemMemory, 0x393DA000, 0x43)
+    OperationRegion (BNVS, SystemMemory, 0x3E4F0000, 0x43)

I don't think using my DSDT will make a big difference. In fact that SSDT patch that mald0n gave me only works when I use glasgood's DSDT, so that's what I'm using.

Edited by tasc
21 minutes ago, tasc said:

 

I went ahead and disassembled both of our DSDTs to see if the differences would be easy to spot, and actually they are fairly easy to see when using a diff tool. I can see glasgood has the broadcom wireless adapter in his, while I do not use any wireless card. It looks like mald0n renamed my SAT0 to SATA and GIGE to GLAN, but those are patched in clover anyways so should result in the same thing.

 

There's only a couple other areas that differ - I can see where glasgood added in the EC power patch and the wake patch, and I have an additional display section probably due to my nvidia card in slot 2. Other than that there a just a few discrepancies:

 


(-) lines are my DSDT, (+) lines are glasgood DSDT

-DefinitionBlock ("", "DSDT", 2, "ALASKA", "Olarila", 0x01072009)
+DefinitionBlock ("", "DSDT", 2, "ALASKA", "GlasGood", 0x01072009)

+    External (UMAP, IntObj)    // (from opcode)

-    OperationRegion (GNVS, SystemMemory, 0x3936E000, 0x0866)
+    OperationRegion (GNVS, SystemMemory, 0x3E484000, 0x0866)

-    Name (PNVB, 0x39421B98)
+    Name (PNVB, 0x3E557B98)

-    OperationRegion (BNVS, SystemMemory, 0x393DA000, 0x43)
+    OperationRegion (BNVS, SystemMemory, 0x3E4F0000, 0x43)

I don't think using my DSDT will make a big difference. In fact that SSDT patch that mald0n gave me only works when I use glasgood's DSDT, so that's what I'm using.

 

I gave it a shot anyway as it's good to have a b sample and sure enough I'm getting exactly the same problems with your dsdt.

Do you remember what bios came with your board out of the box?

Was it F5 or F8?

 

Maybe the person that did your dsdt can shed some light on my problem for me.

What's hes name and where do I find him buddy? :)

19 minutes ago, AudioGod said:

Do you remember what bios came with your board out of the box?

Was it F5 or F8?

 

Maybe the person that did your dsdt can shed some light on my problem for me.

What's hes name and where do I find him buddy? :)

 

I'm fairly sure my board shipped with F8. If I were still having shutdown/startup issues I might try resetting CMOS yet again with the jumper. It seems these things get corrupted in strange ways when switching back and forth with these memory drivers.

 

Mald0n is a moderator on this site, check this thread here for the DSDT patches: 

 

17 minutes ago, tasc said:

 

I'm fairly sure my board shipped with F8. If I were still having shutdown/startup issues I might try resetting CMOS yet again with the jumper. It seems these things get corrupted in strange ways when switching back and forth with these memory drivers.

 

Mald0n is a moderator on this site, check this thread here for the DSDT patches: 

 

 

Nice one buddy :)

On 3/6/2019 at 10:58 AM, glasgood said:

1st RECOMMENDED WIFI CARD →  ABWB BCM943602CS 802.11AC WI-FI With Bluetooth 4.0 PCI-Express (PCI-E)   

 

This card is really OOB, installed and BAM! WIFI and Bluetooth recognized in Mojave!

Also  Airdrop is working!

 

But Shared-Clipboard or HandOff don't seems to work,

also (maybe it's just an impression)  WIFI is not really fast, do I need some specific kext?

 

4 minutes ago, gino8080 said:

 

This card is really OOB, installed and BAM! WIFI and Bluetooth recognized in Mojave!

Also  Airdrop is working!

 

But Shared-Clipboard or HandOff don't seems to work,

also (maybe it's just an impression)  WIFI is not really fast, do I need some specific kext?

 

 

Shared clipboard works and hands off works for me. Wifi is absolutely slower than real Mac. What router are you using? 

 

@AudioGod what are the list of your current problems buddy? 

On 8/1/2019 at 12:19 PM, glasgood said:

What framebuffer is your Vega card using in macOS, is it using ATY,AMD,RadeonFrambuffer ? I know the proper frambuffer for RX 580 is Orinoco. Does the Vega 56 use Iriri or  Kamarang ? 

 

I just checked and also mine Vega 64 is showing ATY,AMD,RadeonFrambuffer

 

1250636586_Screenshot2019-08-05at22_47_00.thumb.png.9549d25115255b0819f98ac95b8e3455.png612668479_Screenshot2019-08-05at22_52_53.thumb.png.82cb0f0e4fd3bee80ea64522976f8fd1.png

What does it means? 

and what I need to do?

 

thank youuu

 

 

10 minutes ago, larabee said:

Shared clipboard works and hands off works for me. Wifi is absolutely slower than real Mac. What router are you using

 

Did you done something special a part from enabling the option on System preferences?

1796703197_Screenshot2019-08-05at22_58_11.png.45f8feb4aea7627c781f93741fcedc3d.png

 

I'm using a FRITZ!Box 7530,  5G & 2.4G

 

18 minutes ago, larabee said:

 

@AudioGod what are the list of your current problems buddy? 

 

Just the cold boot after you wake from sleep but it's really bad on my system and causing all sorts of after problems leading me to have to constantly reset my bios over and over.

Edited by AudioGod
On 8/3/2019 at 12:47 PM, erikmay said:

Hi, 

I am new to the Hackintosh Topic and I just cant resolve this issue.
When I boot up for the installation everything goes perfectly fine.. until I want to install Mojave on the previously formatted drive.
No matter what I do, I cant get past the Installer.
It loads shows 3min remaining, 2min and then crashes. Everytime.

I made a Video that shows the problem.
I really hope someone can give me a keyword to search for, because I am lost.
Is it the Mainboard Bios Version?

Video <- here is a video of the process.

Setup:
Z390 Aorus Pro (Bios ver F10)
i5 9600k
RX580 
Samsung Evo 860

73E7D181-AE47-484D-B16E-929A225FB1C3.png

 

I wanted to give a short update on this problem.

In the end the problem was the iMac from my neighbor I got the Installer Image from. The iMac was still running Yosemite (from 2014) and probably downloaded some different installer.

After I updated the Mac in two steps (Yosemite -> High Sierra -> Mojave) and downloaded the Mojave Installer again everything went absolutely fine.

I am so impressed by the power my new Hackintosh. The Samsung 970 Evo Plus M.2 really opens everything *lightning* fast. Even if I open all installed apps at once, incredible.

And I am also impressed by the OOB experience I got with your Efi config @glasgood!

  • Like 2
2 hours ago, gino8080 said:

 

I just checked and also mine Vega 64 is showing ATY,AMD,RadeonFrambuffer

 

 

 

 

If you're using Vega56 and it shows as 64, that's normal for the new EFI. I've been running fine with it. In Clover Configurator, please type in Kamarang in the frame buffer area. That should change your framebuffer into Kamarang and works better for vega 56.  

imageproxy.php?img=&key=c17464ef1b1b51c71511369230_ScreenShot2019-08-05at4_05_53PM.png.81df7d2569194ae58d1cb24430b197e8.png

 

 

2 hours ago, gino8080 said:

 

Did you done something special a part from enabling the option on System preferences?

1796703197_Screenshot2019-08-05at22_58_11.png.45f8feb4aea7627c781f93741fcedc3d.png

 

I'm using a FRITZ!Box 7530,  5G & 2.4G

 

Everything works normally for me. Sometimes handsoff is funky, even with my real iMac. So, there's a high chance that it's not hackintosh but an actually Apple problem haha. 

For your modem, it's 867Megabit / second, that means it's around 100MB/second max speed. Usually if you can get to 50 or 70MB/sec it's considered good enough depending on how much interference. 

 

 

 

2 hours ago, AudioGod said:

Just the cold boot after you wake from sleep but it's really bad on my system and causing all sorts of after problems leading me to have to constantly reset my bios over and over.

I tried to get mine to reset, but the only way to kill my board is changing EFI haha. I wanted to switch back to Glasgood pre-dsdt EFI to test out a build for my friend, but my motherboard just stop working. I could not get into BIOS this time and flashing BIOS consistently failed. I removed the battery and waited for 30 mins then reflash the F9 old bios, then it works. 

@AudioGod can you re-flash the old F9 instead of F10 bios and try? Mine doesn't get reset after sleep - cold boot. Still I have to press power button 2 times, but all settings are intact and system appeared to be stable.

Edited by larabee
10 minutes ago, larabee said:

I tried to get mine to reset, but the only way to kill my board is changing EFI haha. I wanted to switch back to Glasgood pre-dsdt EFI to test out a build for my friend, but my motherboard just stop working. I could not get into BIOS this time and flashing BIOS consistently failed. I removed the battery and waited for 30 mins then reflash the F9 old bios, then it works. 

 

I find pulling the battery for a length of time always brings me back to stock. I've not needed to reflash my bios yet but now I've typed that it's just a matter of time...lol

 

I'm talking to MaLd0n about it currently and hes got a dump file of my system so fingers crossed he can shed some light on it  and find a fix. 

 

Il let you know when I do as too what's going on :)

Edited by AudioGod
1 minute ago, AudioGod said:

 

I find pulling the battery for a length of time always brings me back to stock. I've not needed to reflash my bios yet but now I've typed that it's just a matter of time...lol

 

I'm talking to MaLd0n about it currently and hes got a dump file of my system so fingers crossed he can shed some light on it  and find a fix. 

 

Il let you know when I do as too what's going on :)

 

Hopefully he can shed some light into this matter. Finger crossed. 

Right now, I'm living in insomnia city haha. No sleep for you baby hack. 

 

 

 

@larabee If you want to roll back to the older EFI then just make sure you pull the battery for 10 mins after you change over to the old EFI and before you boot back up with it. That's the only way it will work for me but after that the Old EFI will work just fine. :)

43 minutes ago, larabee said:

Still I have to press power button 2 times, but all settings are intact and system appeared to be stable.

 

Strange, I wake from sleep with single keypress, although I also added darkwake=0 to boot flags. Are you using glasgood's latest EFI?

 

@AudioGod if you get a DSDT from M4ld0n, please post it here so we can compare. Thanks!

Edited by tasc
1 hour ago, larabee said:

If you're using Vega56 and it shows as 64, that's normal for the new EFI. I've been running fine with it. In Clover Configurator, please type in Kamarang in the frame buffer area. That should change your framebuffer into Kamarang and works better for vega 56.  

 

Sorry it was a typo I have a MSI Radeon RX Vega 56 Air Boost

 

I just added Manually Kamarang in Config (because it was NOT in the select list) and nothing changed

THEN I added also the Inject ATI flag ( I had no inject before)

and now it shows Kamarang framebuffer

 

788736292_Screenshot2019-08-06at01_47_35.thumb.png.3d87ac22d195fbe3af66de106b35f0bc.png

But GPU fans spins like hell, also I'm not sure is performing better, at least it seems:

 

 

1262387905_Screenshot2019-08-06at02_06_58.thumb.png.08eae29c3e6b092242fd7d3ba2e22486.png

 

EDIT also Iriri is slight lower

 

Maybe my GPU is ok with default framebuffer? (also no problems with fans)

 

 

Edited by gino8080
more details
2 hours ago, tasc said:

 

Strange, I wake from sleep with single keypress, although I also added darkwake=0 to boot flags. Are you using glasgood's latest EFI?

 

 

It's Sleep, then shutdown, then the next power up = trouble

 

 

@gino8080 Yeah if you notice your machine runs slower, just use the original. I'm using Sapphire Pulse vega56, so maybe different BIOS and board layout leads to different results. 

Edited by larabee
14 hours ago, larabee said:

 

It's Sleep, then shutdown, then the next power up = trouble

 

@larabee I'm finally getting somewhere bro, I've noticed something within the bios itself (corruption of saved profiles)

I reset my bios and started again and did my default setup manually and it worked. Then I loaded up my default settings profile in the bios instead (exactly the same as the first test but loaded instead of typed) and it borked my system like it has been.

Still testing but defo making progress now.

Also have a new dsdt and Mald0n has my EFI to see if all is ok there.

More news soon :)

 

Scrap that it was nothing more then a fluke...lol.  back to square one again.

 

 

Edited by AudioGod
On 8/4/2019 at 2:13 AM, glasgood said:

 

I'm no longer maintaining EFI for intel ==> :Aorus Pro Z390 EFI - Intel UHD630.zip 

 

Updates required:

  •  Update to latest Clover
  • Kext Update
  • Switch form SMBIOS for iMac 18,1 to iMac 19,2

And you could also try: 

  •  DSDT.aml ( would provide native NVRAM, you would then delete EmuVariableUefi-64.efi)

Best!

Thanks for replying. 

Should i use same efi for pre and post install ?

Has anybody experienced a random crash where the monitor goes blank - white - and the keyboard is unresponsive? The only way to get out of that state is to turn the power off.

 

I've had it happen yesterday and today. No real way to reproduce it either.

1 hour ago, hackinbot said:

Has anybody experienced a random crash where the monitor goes blank - white - and the keyboard is unresponsive? The only way to get out of that state is to turn the power off.

 

I've had it happen yesterday and today. No real way to reproduce it either.

 

Monitor goes blank white - complete freezing, random static sounds are coming from the speakers. 

I had all of those because one of my USB device is causing it: my old sound card has been troublesome for me. 

Do you remember which software is running or which additional hardware you put into the hack when it happened? 

 

4 hours ago, AudioGod said:

 

@larabee I'm finally getting somewhere bro, I've noticed something within the bios itself (corruption of saved profiles)

I reset my bios and started again and did my default setup manually and it worked. Then I loaded up my default settings profile in the bios instead (exactly the same as the first test but loaded instead of typed) and it borked my system like it has been.

Still testing but defo making progress now.

Also have a new dsdt and Mald0n has my EFI to see if all is ok there.

More news soon :)

 

Scrap that it was nothing more then a fluke...lol.  back to square one again.

 

 

 

@AudioGod Last resort: Try flashing it with F9 instead of F10 and let me know if the reset / corruption still exist? 

41 minutes ago, larabee said:

 

Monitor goes blank white - complete freezing, random static sounds are coming from the speakers. 

I had all of those because one of my USB device is causing it: my old sound card has been troublesome for me. 

Do you remember which software is running or which additional hardware you put into the hack when it happened? 

 

Interesting.

 

New devices plugged into the connected USB hub include:

1. An old Fujitsu Scanner - not powered up when the crashes happened. I'll unplug this.

2. APC UPS battery backup - I'll unplug this usb cable for now.

3. Logitech C920 webcam - plugged in but not powered up. I'll unplug this also.

 

As for software - whenever it happened I was using Safari - but that can just be a coincidence because the majority of the time I'm in Safari on this workstation. One crash occurred when a lot of ads were loading on some blog. Once was on GitHub which is just text.


We'll see how this goes. If it still has a random lock up, I'll try clearing the BIOS like you guys have been doing.


Thanks for helping.

×
×
  • Create New...