Contribute
Register

[solved] BrcmFirmwareRepo.kext not working

Status
Not open for further replies.
Galileo6373637

Galileo6373637

Joined
Nov 12, 2017
Messages
57
Motherboard
Gigabyte Z390 Designare
CPU
i7-8700K
Graphics
Vega 64LC
Hi,

I installed bcm94352z in my Gigabyte Z370N and installed these kexts:
  1. FakePCIID.kext in Clover
  2. FakePCIID_Broadcom_WiFi.kext in Clover
  3. BrcmPatchRAM2.kext in Clover
  4. BrcmFirmwareRepo.kext in /S/L/E
WiFi worked immediately, but BT not. And there was no Hardware in Systemprofiler. I then deinstalled BrcmFirmwareRepo.kext and used BrcmFirmwareData.kext in Clover instead. Now BT works fine. But according to the Guideline https://github.com/RehabMan/OS-X-BrcmPatchRAM (@RehabMan ) it is recommend to use BrcmFirmwareRepo.kext, since it has much better memory efficiency.

So what can be the reason ?

How can I built my own kext, to try BrcmBluetoothInjector.kext.

Edit: System is 10.13.2
 
Last edited:
Galileo6373637 said:
Hi,

I installed bcm94352z in my Gigabyte Z370N and installed these kexts:
  1. FakePCIID.kext in Clover
  2. FakePCIID_Broadcom_WiFi.kext in Clover
  3. BrcmPatchRAM2.kext in Clover
  4. BrcmFirmwareRepo.kext in /S/L/E
WiFi worked immediately, but BT not. And there was no Hardware in Systemprofiler. I then deinstalled BrcmFirmwareRepo.kext and used BrcmFirmwareData.kext in Clover instead. Now BT works fine. But according to the Guideline https://github.com/RehabMan/OS-X-BrcmPatchRAM (@RehabMan ) it is recommend to use BrcmFirmwareRepo.kext, since it has much better memory efficiency.

So what can be the reason ?

How can I built my own kext, to try BrcmBluetoothInjector.kext.

Edit: System is 10.13.2
Click to expand...

No "Problem Reporting" files attached.
Read FAQ, "Problem Reporting" again. Carefully. Attach all requested files/output.
https://www.tonymacx86.com/threads/faq-read-first-laptop-frequent-questions.164990/
Use the tool mentioned in the FAQ, that way it is less likely you'll omit something.
 
Hi RehabMan,

files are attached, thanks
 

Attachments

  • Archiv.zip
    5.8 MB · Views: 844
RehabMan said:
Your kextcache output shows no kexts installed.
All kexts you need must be installed to the system volume (typically /L/E with 10.11 and later).
Note that your USB configuration is wrong.
Read here:
https://www.tonymacx86.com/threads/guide-creating-a-custom-ssdt-for-usbinjectall-kext.211311/
Click to expand...
Do they all have to be in /L/E ? What about FackeSMC ?

I'll check your guide this weekend, thank you.

But where is the relationship to BrcmFirmwareRepo.kext ? Does this kext only work, when the others are in /L/E ?

Note: One of the terminal outputs said, that I don't have TRIM support. Mac OS is installed on NVME, which has TRIM support according to system profiler. and on the SSD is only Windows installed.
 
Galileo6373637 said:
Do they all have to be in /L/E ?
Click to expand...

Yes.

What about FackeSMC ?
Click to expand...

Also in /L/E and /EFI/Clover/kexts/Other.
It is explained in post #2 of my laptop Clover guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/

But where is the relationship to BrcmFirmwareRepo.kext ? Does this kext only work, when the others are in /L/E ?
Click to expand...

Proper kext installation leads to proper kernel cache generation.

Note: One of the terminal outputs said, that I don't have TRIM support. Mac OS is installed on NVME, which has TRIM support according to system profiler. and on the SSD is only Windows installed.
Click to expand...

The script does not check for TRIM on NVMe, as NVMe can easily be seen from ioreg, and we all know that TRIM is default with NVMe.

Note: TRIM (either on NVMe or SATA) + APFS + non-Apple SSD causes problems. NVMe hacks should use HFS+J, not APFS.
 
Galileo6373637 said:
Hi,

I installed bcm94352z in my Gigabyte Z370N ...

Edit: System is 10.13.2
Click to expand...

I am thinking to build another rig using this board. Did you replace the existing wifi card? Or you add another one on the one of the free slots?
 
RehabMan said:
Yes.



Also in /L/E and /EFI/Clover/kexts/Other.
It is explained in post #2 of my laptop Clover guide:
https://www.tonymacx86.com/threads/guide-booting-the-os-x-installer-on-laptops-with-clover.148093/



Proper kext installation leads to proper kernel cache generation.
Click to expand...

It works now, great !

RehabMan said:
The script does not check for TRIM on NVMe, as NVMe can easily be seen from ioreg, and we all know that TRIM is default with NVMe.

Note: TRIM (either on NVMe or SATA) + APFS + non-Apple SSD causes problems. NVMe hacks should use HFS+J, not APFS.
Click to expand...

I don't have a NVMe hack. It worked OOB with High Sierra.
So do I still have then to convert from APFS to HFS+J ?
 
Status
Not open for further replies.
Copyright © 2010 - 2024 tonymacx86 LLC
Back
Top