Welcome to AMD OS X

Why not register now to gain full access.

Chat about almost anything as long as it is within the rules.
User avatar
by: ErikW
#50895
I've been trying to figure this out. I've put together a successful hackintosh on the Gigabyte X570 mini-ITX board with a Ryzen 3900x.

One thing lacking is any sort of thermal monitoring.

SSDs/HDDs have worked natively.

I've installed FakeSMC successfully, along with all the kexts (ACPI, LPC, GPU) *except* the CPUSensors one (this gives a kernel panic). I've tried the AmdCpuSensors kext floating around.

All I've been able to get working is GPU Die monitoring, and two sensors called "Thermal Zone 1" and "Thermal Zone 2" -- which report C values in the teens, so I have no idea what that is monitoring.

I've attached what I've been able to figure out. Here's the kexts that are loaded:

Image


[bcode]Index Refs Address Size Wired Name (Version) UUID <Linked Against>
16 0 0xffffff7f85877000 0x2000 0x2000 org.tgwbd.driver.NullCPUPowerManagement (1.0.0d2) 93D39664-55FB-9220-39AD-A436B33DB160 <8 5 3>
39 3 0xffffff7f8587b000 0x11000 0x11000 org.netkas.driver.FakeSMC (1802) B2673C65-0FB6-38DC-A6A8-5FD128002C3D <12 8 6 5 3 1>
40 3 0xffffff7f8588c000 0x22000 0x22000 as.vit9696.Lilu (1.3.8) FC38993B-FBDB-3E9A-AC3E-73704D26ACF6 <8 6 5 3 2 1>
41 0 0xffffff7f858ae000 0x7000 0x7000 as.lvs1974.AirportBrcmFixup (2.0.3) 1C09F269-6015-3A31-BAA5-2A8FCD9FD2A8 <40 17 13 8 6 5 3 2 1>
42 0 0xffffff7f858b5000 0x119000 0x119000 as.vit9696.AppleALC (1.4.0) 2009BAFC-6FB0-3304-B88E-94D2FCAE3E15 <40 13 8 6 5 3 2 1>
43 0 0xffffff7f859ce000 0x66000 0x66000 as.vit9696.WhateverGreen (1.3.1) B0A00E8E-0D64-32BE-85CB-B5893B9C31DE <40 13 8 6 5 3 2 1>
55 0 0xffffff7f85a34000 0x8000 0x8000 org.hwsensors.driver.ACPISensors (1802) E723182C-170A-371F-807F-3A7916A80EF5 <39 12 8 6 5 3>
60 0 0xffffff7f85a3e000 0xd000 0xd000 org.hwsensors.driver.LPCSensors (1802) 02B6D983-3844-3184-8508-A1441DABE03C <39 13 12 8 6 5 3>
61 0 0xffffff7f85a4b000 0x12000 0x12000 org.hwsensors.driver.GPUSensors (1802) DB5EA141-1685-3424-9197-161B62AEAC8B <39 13 12 8 6 5 3>
68 0 0xffffff7f85a60000 0x1a000 0x1a000 com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <17 13 6 5 3 1>
74 0 0xffffff7f80dde000 0x8000 0x8000 org.rehabman.driver.FakePCIID (1.3.15) B185B092-1FC9-308E-B093-32FD88E5822D <13 8 6 5 3 1>
114 1 0xffffff7f80c34000 0x6000 0x6000 com.no-one.BrcmFirmwareStore (2.2.10) 5DD4CFA3-AB5A-3AB4-BBA2-8ACE9BCD72D8 <6 5 3>
115 0 0xffffff7f80d4f000 0x6000 0x6000 com.no-one.BrcmPatchRAM2 (2.2.10) EA8FADAF-E7F3-3CDF-8440-49C15C0E25F8 <114 24 6 5 3 1>
147 0 0xffffff7f85a7a000 0x7000 0x7000 com.parallels.virtualsound (1.0.36 36) E9131806-D073-8482-AC46-B4AAE55EA6FE <93 6 5 3 1>
153 3 0xffffff7f85a81000 0xf0000 0xf0000 org.virtualbox.kext.VBoxDrv (6.0.10) FD628542-B180-34C4-AF29-CE70F4F9F587 <8 6 5 3 1>
154 0 0xffffff7f85b71000 0x5000 0x5000 com.parallels.virtualhid (1.0.3 3) B0C355DF-4268-359B-9654-0A67F4305F7B <52 6 5 3 1>
157 0 0xffffff7f85b76000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (6.0.10) 8626D518-71CF-3493-A7BC-5A5F24561525 <156 153 76 8 6 5 3 1>
158 0 0xffffff7f85b7e000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (6.0.10) E9EF0869-64B9-3C71-9133-4082F8227256 <153 8 6 5 3 1>
159 0 0xffffff7f85b83000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (6.0.10) 9F140CBD-4713-3F03-AAD1-FBBC2B6C49A1 <153 6 5 1>
160 0 0xffffff7f80f4a000 0x6000 0x6000 com.getdropbox.dropbox.kext (1.10.3) F29DD0CB-48D6-311A-9B69-E39CF775493C <8 6 5 2 1>
[email protected]  ~ [/bcode]

 Advertising

User avatar
by: nbishop8
#50900
ErikW wrote:I've been trying to figure this out. I've put together a successful hackintosh on the Gigabyte X570 mini-ITX board with a Ryzen 3900x.

One thing lacking is any sort of thermal monitoring.

SSDs/HDDs have worked natively.

I've installed FakeSMC successfully, along with all the kexts (ACPI, LPC, GPU) *except* the CPUSensors one (this gives a kernel panic). I've tried the AmdCpuSensors kext floating around.

All I've been able to get working is GPU Die monitoring, and two sensors called "Thermal Zone 1" and "Thermal Zone 2" -- which report C values in the teens, so I have no idea what that is monitoring.

I've attached what I've been able to figure out. Here's the kexts that are loaded:

Image


[bcode]Index Refs Address Size Wired Name (Version) UUID <Linked Against>
16 0 0xffffff7f85877000 0x2000 0x2000 org.tgwbd.driver.NullCPUPowerManagement (1.0.0d2) 93D39664-55FB-9220-39AD-A436B33DB160 <8 5 3>
39 3 0xffffff7f8587b000 0x11000 0x11000 org.netkas.driver.FakeSMC (1802) B2673C65-0FB6-38DC-A6A8-5FD128002C3D <<a href="tel:12 8 6 5 3 1" data-original-title="" title="">12 8 6 5 3 1</a>>
40 3 0xffffff7f8588c000 0x22000 0x22000 as.vit9696.Lilu (1.3.8) FC38993B-FBDB-3E9A-AC3E-73704D26ACF6 <8 6 5 3 2 1>
41 0 0xffffff7f858ae000 0x7000 0x7000 as.lvs1974.AirportBrcmFixup (2.0.3) 1C09F269-6015-3A31-BAA5-2A8FCD9FD2A8 <<a href="tel:40 17 13 8 6 5 3 2" data-original-title="" title="">40 17 13 8 6 5 3 2</a> 1>
42 0 0xffffff7f858b5000 0x119000 0x119000 as.vit9696.AppleALC (1.4.0) 2009BAFC-6FB0-3304-B88E-94D2FCAE3E15 <<a href="tel:40 13 8 6 5 3 2 1" data-original-title="" title="">40 13 8 6 5 3 2 1</a>>
43 0 0xffffff7f859ce000 0x66000 0x66000 as.vit9696.WhateverGreen (1.3.1) B0A00E8E-0D64-32BE-85CB-B5893B9C31DE <<a href="tel:40 13 8 6 5 3 2 1" data-original-title="" title="">40 13 8 6 5 3 2 1</a>>
55 0 0xffffff7f85a34000 0x8000 0x8000 org.hwsensors.driver.ACPISensors (1802) E723182C-170A-371F-807F-3A7916A80EF5 <<a href="tel:39 12 8 6 5 3" data-original-title="" title="">39 12 8 6 5 3</a>>
60 0 0xffffff7f85a3e000 0xd000 0xd000 org.hwsensors.driver.LPCSensors (1802) 02B6D983-3844-3184-8508-A1441DABE03C <<a href="tel:39 13 12 8 6 5 3" data-original-title="" title="">39 13 12 8 6 5 3</a>>
61 0 0xffffff7f85a4b000 0x12000 0x12000 org.hwsensors.driver.GPUSensors (1802) DB5EA141-1685-3424-9197-161B62AEAC8B <<a href="tel:39 13 12 8 6 5 3" data-original-title="" title="">39 13 12 8 6 5 3</a>>
68 0 0xffffff7f85a60000 0x1a000 0x1a000 com.smalltree.driver.SmallTreeIntel82576 (1.0.6) F6C5E33A-97AA-37A0-8794-64FAA19FC153 <<a href="tel:17 13 6 5 3 1" data-original-title="" title="">17 13 6 5 3 1</a>>
74 0 0xffffff7f80dde000 0x8000 0x8000 org.rehabman.driver.FakePCIID (1.3.15) B185B092-1FC9-308E-B093-32FD88E5822D <<a href="tel:13 8 6 5 3 1" data-original-title="" title="">13 8 6 5 3 1</a>>
114 1 0xffffff7f80c34000 0x6000 0x6000 com.no-one.BrcmFirmwareStore (2.2.10) 5DD4CFA3-AB5A-3AB4-BBA2-8ACE9BCD72D8 <6 5 3>
115 0 0xffffff7f80d4f000 0x6000 0x6000 com.no-one.BrcmPatchRAM2 (2.2.10) EA8FADAF-E7F3-3CDF-8440-49C15C0E25F8 <<a href="tel:114 24 6 5 3 1" data-original-title="" title="">114 24 6 5 3 1</a>>
147 0 0xffffff7f85a7a000 0x7000 0x7000 com.parallels.virtualsound (1.0.36 36) E9131806-D073-8482-AC46-B4AAE55EA6FE <93 6 5 3 1>
153 3 0xffffff7f85a81000 0xf0000 0xf0000 org.virtualbox.kext.VBoxDrv (6.0.10) FD628542-B180-34C4-AF29-CE70F4F9F587 <8 6 5 3 1>
154 0 0xffffff7f85b71000 0x5000 0x5000 com.parallels.virtualhid (1.0.3 3) B0C355DF-4268-359B-9654-0A67F4305F7B <52 6 5 3 1>
157 0 0xffffff7f85b76000 0x8000 0x8000 org.virtualbox.kext.VBoxUSB (6.0.10) 8626D518-71CF-3493-A7BC-5A5F24561525 <<a href="tel:156 153 76 8 6 5 3" data-original-title="" title="">156 153 76 8 6 5 3</a> 1>
158 0 0xffffff7f85b7e000 0x5000 0x5000 org.virtualbox.kext.VBoxNetFlt (6.0.10) E9EF0869-64B9-3C71-9133-4082F8227256 <<a href="tel:153 8 6 5 3 1" data-original-title="" title="">153 8 6 5 3 1</a>>
159 0 0xffffff7f85b83000 0x6000 0x6000 org.virtualbox.kext.VBoxNetAdp (6.0.10) 9F140CBD-4713-3F03-AAD1-FBBC2B6C49A1 <153 6 5 1>
160 0 0xffffff7f80f4a000 0x6000 0x6000 com.getdropbox.dropbox.kext (1.10.3) F29DD0CB-48D6-311A-9B69-E39CF775493C <8 6 5 2 1>
[email protected]  ~ [/bcode]


@ErikW, I can’t see you image by the way.

Looking at the log above, why the hell is the printout above mentioning Dropbox?!?! I’ve NEVER seen that before. With that being the last of the log file. I have no f$^*%$g clue what that could even mean about startup errors. That is not something I think (damn near positive) is native to macOS - so keep that in mind when troubleshooting. Also, if you figure it out let us know.

That being said, I do Know a few reasons why component temperature monitoring may be an issue on an a hackintosh.

You need to understand that sensor reporting is basically **** on macOS, as Apple doesn’t want to be transparent about CPU and GPU (if you’re lucky) throttling. Therefore, the kernel and other programs related to hardware monitoring are much less robust compared to Linux or microsoft’s monstrosity. Because it isn’t native, it is important to utilize the correct files in the correct combination for the ase features to function properly.

  • You have to be sure you are using the necessary EFI (64) files as well as the HWSensors plugins when using VirtualSMC or FakeSMC. Monitoring of hardware will not function without these on any hackintosh.
    • Devs of FakeSMC also contribute to HWSensors plugin kexts. You just load them alongside FakeSMC as documented. There may be plugins for VirtualSMC, but I haven’t checked in some time. Though because FakeSMC is older and more documented, it may have better compatibility with certain things - like hardware monitoring for example.
  • You must be consistent when using FakeSMC or VirtualSMC. If you use one, you must delete all files of the other.
    • For example, if using VirtualSMC you must remove all FakeSMC files from the clover EFI - or move them in a different, custom directory so clover doesn’t recognize them if you want to save them for future use.
  • Get HWSensors or Macs Fan Control for monitoring. As explained above, macOS has little to no native hardware monitoring
User avatar
by: ErikW
#51030
Dropbox kext is just from the software. Sorry, I disagree with a lot of your post.

1. Sensor reporting on macOS is very good. See, for example, the picture from my MacBook Pro. Apple has no issue, and never has, with reporting sensor temperatures. Making that work in Hackintosh is a different story.
2. I am using iStatMenus, but it draws from the same data that HWMonitor or any other program does. I've tested them all.
3. I have tried recent versions of FakeSMC and VirtualSMC. With FakeSMC, I can get a Northbridge temperature and a GPU temperature using RadeonSensors. No CPU temperatures.

Do people have any better luck on X470 or below? What sensors do you get?
You do not have the required permissions to view the files attached to this post.

The 9, 10 and 20 series cards are not supported […]

Screen Shot 2019-09-19 at 6.28.48 PM.png Specs:[…]

nvidia gpu laggy

I use this driver on my GTX 1070: https://images.n[…]

Install the nvidia web driver for 10.13.6 here: ht[…]