Tubardus
-
Posts
92 -
Joined
-
Last visited
Content Type
Profiles
Articles, News and Tips
Forums
Posts posted by Tubardus
-
-
Hello everyone,
It's been several months without any trouble with my Hackintosh. Nevertheless, I noticed that my wifi tx rate is only 20 Mbps and I think it's rather slow. I'm using a BCM94360NG and all my kexts are placed in L/E. Also the BT sometimes seems to be a little slow. I think it's linked to the wifi problem. Any thoughts about it?
Thanks!
-
Same issue "your computer has restarted because of a problem" even after rebuilding the cache.
I found that by pressing F11 at the clover boot menu, it does boot without any problem. If I don't press F11 to clear NVRAM, it cannot boot properly. Also sometimes I lose the brightness control. I think it has something to do with it. Maybe something about the BIOS, no?
-
Ok, understood. I don't know what exactly is doing the DSDT.aml file. I only saw that it has something to de with the motherboard (nothing less...). Nevertheless, since I removed this file, the computer is not able to boot the first time. It always takes two times to boot properly with a message saying (your computer didn't boot normally etc.). Is that normal?
-
Hello,
Should we all remove the DSDT file from ACPI/Patched et reboot according to your recent post about Revised Clover pack #3? Is this file was the responsible?
-
I think I know what happened when I lost the MacOS partition.Actually all was working fine before. I had my laptop connected to an external screen by HDMI, with a wireless keyboard and a wireless mouse. The laptop was closed all the time. Usually, I activate the "sleep" mode when I don't use it. But the last time, I shut down the computer while closed and connected (HDMI). At this point, the macOS partition was lost. Does anyone experienced this issue?
-
Ok thanks, I don't have this directory. O only have the hard disk in /System/Volumes.
-
Ok! Seems to be working with VBoxHfs.efi alone. I will try to replace it by HFSPlus.efi and see if it works. I'm sure there something awkward between 10.15.4 and 10.15.5...
@Hervé, when you say : "The macOS Install Data folders in /System/Volumes/Data, however, had to be manually removed to get rid of the temp partition" in updating to 10.15.5, can you explain to me what exactly need to be done?
-
Since I'm doing it form scratch I just noticed that HSFPlus is not in the menu of clover bootloader version r5107. Should I replace HSFPlus by something else? Say VBoxHfs?
-
Thank you for your reply!
Unfortunately I don't have VboxHfs.efi. I tried to use HFSPlus.efi alone. No difference. I'm now reinstalling from the beginning. I think it has something to do with a certain update of Catalina which changes profoundly the names and locations of important files.
Do you know why HFSPlus.efi is gone? Is it because I'm now running 10.15.5?
-
Hello everyone,
For the first time in weeks, I shutted down my computer for a fresh restart. Unfortunately, the clover boot manager doesn't show the MacOs installation anymore. I was on Catalina 10.15. Can I do something? The version of Clover is 5107.
Also by pressing F3 (checked in the clover boot help) it showed the recovery boot option. I tried to reinstall Catalina from there. But it didn't worked saying something about an APFS problem.
Last hypothesis : maybe I must follow this lead in order to put the missing OsxAptioFix2Drv-64.efi file in the right place?
After some searching, I found that the HFSPlus.efi is now missing in FS1:\EFI\CLOVER\drivers\UEFI. I think this is why the MacOS is not showing in the clover boot manager. Can anyone telle me how I can put it back? And why it disappeared in the first place?
Thanks!
-
Hello Everyone!
I finally received my BCM94360NG! I plugged it and wifi and bluetooth are working fine even when I removed the DW1820A from the config.plist and set to "detect" the kext. It then works without any BRCMPatch or what so ever.
I found that the wifi is rather slow compared to the DW1820A. Is there something to do in config.plist to get te wifi card recognized?
-
Unfortunately adding bpr_presetdelay=250 didn't worked. I had to do a cold boot to see the version of the firmware change to v5974. All the devices are seen but none of them be be connected with BT. And no KP to report with the two ways of booting.
-
So if a kext in installed in both LE and EC/k/O, it will be injected twice? Should I remove all kexts but Brcm ones before of E/C/k/O?
-
I wondered if it is possible to inject only some kext from E/C/k/O (BRCM kexts and fakePCIID) and all the others from L/E. Is three something to do with config.plist to do so? I saw "ForceKextToLoad" in clover configurator. can I indicate here which kext I want to be loaded from E/C/k/O and set inject kexts to "detect"?
I think it is more desirable to have working kext loaded from L/E until we find a solid solution for BT.
-
Sorry @Hervé, it's not working this way (even after cold and warm boots). The firmware is correctly loading (v5794).
-
Ok, after several tests I can tell you that I haven't found a way to have a good behavior of BT when caching kexts. No matter which BRCM kexts (2.5.2 or 2.2.10) Data or Repo. All with fakePCIID of course. None of those configuration gave back to me BT.
For now the only way is to inject from E/C/k/O I order to have BT. The associated firmware is then 4689 (= 8785 - 4096). It seems that a "mini driver" is loaded which corresponds to BCM4350C5_003.006.007.0222.4689_v8785 by brcmpatchram2. Maybe I should load it from Repo in L/E?
Spoiler2020-04-21 14:10:00.922997+0200 0x73 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Firmware store start
2020-04-21 14:10:04.627062+0200 0x240 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
2020-04-21 14:10:04.627113+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000
2020-04-21 14:10:04.757306+0200 0x240 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
2020-04-21 14:10:04.757360+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000
2020-04-21 14:10:04.816034+0200 0x240 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
2020-04-21 14:10:04.816070+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource: 00000000
2020-04-21 14:10:04.836481+0200 0x240 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: OSKextRequestResource Callback: dc008006.
2020-04-21 14:10:04.836520+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Loaded compressed embedded firmware for key "BCM4350C5_003.006.007.0222.4689_v8785".
2020-04-21 14:10:04.836739+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Decompressed firmware (12582 bytes --> 31740 bytes).
2020-04-21 14:10:04.836922+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware.
2020-04-21 14:10:04.836946+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: USB [3052CBE79732 v274] "BCM2045A0" by "Broadcom Corp"
2020-04-21 14:10:05.237080+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: Available composite configurations: 1.
2020-04-21 14:10:05.238360+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: Set device configuration to configuration index 0 successfully.
2020-04-21 14:10:05.238365+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: USBDeviceShim::findFirstInterface
2020-04-21 14:10:05.238370+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: getValidatedInterface returns <private>
2020-04-21 14:10:05.238374+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: Interface 0 (class ff, subclass 01, protocol 01) located.
2020-04-21 14:10:05.238390+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: set configuration and interface opened
2020-04-21 14:10:05.238393+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: findPipe: direction = 1, type = 3
2020-04-21 14:10:05.238396+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: endpoint found: epDirection = 1, epType = 3
2020-04-21 14:10:05.238399+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: found matching endpoint
2020-04-21 14:10:05.238577+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: findPipe: direction = 0, type = 2
2020-04-21 14:10:05.238580+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: endpoint found: epDirection = 1, epType = 3
2020-04-21 14:10:05.238583+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: endpoint found: epDirection = 1, epType = 2
2020-04-21 14:10:05.238587+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: endpoint found: epDirection = 0, epType = 2
2020-04-21 14:10:05.238589+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: found matching endpoint
2020-04-21 14:10:05.238762+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: got pipes
2020-04-21 14:10:05.438794+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: State "Unknown" --> "Initialize".
2020-04-21 14:10:05.440138+0200 0x165 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: READ VERBOSE CONFIG complete (status: 0x00, length: 10 bytes).
2020-04-21 14:10:05.440143+0200 0x165 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: Firmware version: v4096.
2020-04-21 14:10:05.440150+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: State "Initialize" --> "Firmware version".
2020-04-21 14:10:05.440155+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: getFirmware
2020-04-21 14:10:05.440158+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Retrieved cached firmware for "BCM4350C5_003.006.007.0222.4689_v8785".
2020-04-21 14:10:05.441109+0200 0x165 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: DOWNLOAD MINIDRIVER complete (status: 0x00, length: 4 bytes).
2020-04-21 14:10:05.441117+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: State "Firmware version" --> "Mini-driver complete".
2020-04-21 14:10:05.799130+0200 0x165 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: END OF RECORD complete (status: 0x00, length: 4 bytes).
2020-04-21 14:10:05.799138+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: State "Instruction write" --> "Firmware written".
2020-04-21 14:10:06.051283+0200 0x165 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: Unknown event code (0xff).
2020-04-21 14:10:06.051305+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: State "Firmware written" --> "Reset complete".
2020-04-21 14:10:06.051444+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: Device status 0x00000003.
2020-04-21 14:10:06.051453+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: State "Reset complete" --> "Update complete".
2020-04-21 14:10:06.051462+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: Firmware upgrade completed successfully.
2020-04-21 14:10:06.051521+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 5.709 seconds.
2020-04-21 14:10:06.055522+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: probe
2020-04-21 14:10:06.055537+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Version 2.2.10 starting on OS X Darwin 19.4.
2020-04-21 14:10:08.055684+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: [0a5c:6412]: BrcmPatchRAMResidency does not appear to be available.
2020-04-21 14:10:08.055690+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: getFirmware
2020-04-21 14:10:08.055695+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Retrieved cached firmware for "BCM4350C5_003.006.007.0222.4689_v8785".
2020-04-21 14:10:08.055723+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: uploadFirmware could not open the device!
2020-04-21 14:10:08.055726+0200 0x1ab Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM2: Processing time 2.0 seconds.
Sorry @swatchie-1, I don't have an apple watch to perform your test.
-
I just tried the solution proposed by @swatchie-1 that is inject 4 additional kexts which are the 3 of this thread
and PCIID version 1.3.15 (old one). And it worked! I confirm that the version of BT shows now v_4689. Mouse, keyboard, speakers earphones all connected and fully working.
Now we know that the proper way to use kext is to install them in L/E rebuild and repair. So maybe we should try to load them from L/E and see if it works keeping in mind that BRCMFirmwareData is not made to be in L/E. Repo is.
Thanks!
-
Happy to see that I'm not alone with this issue (and hoping we'll all find solutions!).
I don't know how this can be important but I noticed that in in.plist of BRCM bluetoothInjector the IOProbeScore is 3000 and is 4000 in BrcmPatchRam all two for our 0a5c_6412. Shouldn't it be the same, say 4000?
-
Hello!
I tried different firmwares to try to fix it. Some of them just don't load while others effectively change the version of the firmware. Among them the 5799 seems to be compatible (but BT doesn't work). However, I found strange to read BCM2045A0 since the card is a BCM4350C50. Could it explain some of the issues? Maybe there's a link between BT and USB? How can I see if USB is well configured (from Hackintool?)?
@Hervé, can you tell me what do you see in SysInfo? I see
BCM2045A0 : Identifiant du produit : 0x6412 ,Identifiant du fournisseur : 0x0a5c (Broadcom Corp.). It should be BCM4350C50 no?
Spoiler2020-04-19 15:06:18.014611+0200 0x4e2 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.2 starting on OS X Darwin 19.4.
2020-04-19 15:06:18.636338+0200 0x4e2 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Loaded firmware "0a5c-6412_v5799.hex" from resources.
2020-04-19 15:06:18.638933+0200 0x4e2 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Non-compressed firmware.
2020-04-19 15:06:18.813378+0200 0x4e2 Default 0x0 0 0 kernel: (kernel) BrcmPatchRAM: Firmware is valid IntelHex firmware.
2020-04-19 15:06:18.922334+0200 0x4e2 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: uploadFirmware could not open the device!
2020-04-19 15:06:18.923745+0200 0x4e2 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.103 seconds.
2020-04-19 15:06:18.928231+0200 0x608 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Version 2.5.2 starting on OS X Darwin 19.4.
2020-04-19 15:06:19.028789+0200 0x608 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6412]: USB [3052CBE79732 v274] "BCM2045A0" by "Broadcom Corp"
2020-04-19 15:06:19.391180+0200 0x608 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: [0a5c:6412]: Firmware upgrade completed successfully.
2020-04-19 15:06:19.411191+0200 0x608 Default 0x0 0 0 kernel: (BrcmPatchRAM3) BrcmPatchRAM: Processing time 0.482 seconds.
-
I made the changes in the BIOS, disabling and enabling. Nothing changed.
Maybe my DW1820A is slightly different from yours and therefore need another version of firmware?
-
Hello Hervé,
I installed your kexts as you suggested, did a cold boot. First I didn't saw any KP but after some reboots it did. What I can say is that the firmware shows now v5974 as expected. Also BT is now "discoverable“. BT detects most of devices around but unfortunately, it fails to connect.
I saw what you did by renaming the .hex in Repo. In my tests I also used .hex instead of .zhx. I think the zhx are only compressed hex but the gain is not very big due to the small size of these files. It sound strange that a rename of the firmware file can be sufficient to have it work. Maybe the firmware is used by another program which needs the file to be named in a precise manner.
Do you think I should test your method (renaming hex in Repo and change the patch) for different firmawares?
-
OK! I will see that one and the DW1560
I have installed one "fake" 0VW3T3. It appears to be a BCM2045A0. I remember I saw zhx of that in resources of some Repo. I was wrong. Even with some searching I haven't found any available firmware for that card. Some people have tried to load it with Other BCM zhx without any success on macOS and Linux. I was just loosing time.
When I will receive either the DW1560 or BCM94360NG, will I have to just plug it and maybe change some tings in the BRCM kexts or will I have to do a completely new installation (editing correctly from scratch config.plist)?
-
Thank you very much for all the time spent so far.
I will continue to test all BCM4350 zhx I find but with no real hope (v.6043, 6214, 6820 and 8784).
I have also another Wifi/BT card which was a "fake" dw1820a. I'll give it a try also and as well the original card which was delivered with the 7490. Who knows?
Until we figure a solution, can you please tell me what wifi/BT card do you would advise me to buy?
-
I am now able to change the firmware of the BT card as I want. I just put the right zhx in the resource of brcmRepo and change the info.plist of BrcmPatchRam3 accordingly. I've been able to test several firmwares (5799, 5803 and others also higher). I think what I did was purely cosmetic as none of those different firmwares helped getting back BT.
I installed parallels desktops and Windows 10. Wifi is working well but bluetooth is not detected. Are you thinking to another way to install windows in order to update the BT card firmware?
Also, in your point 3, do I have to understand that this method will not allow me to have a full operational BT? How did you do to have one working?
[Solved] BCM94360NG: poor performance
in The Archive
Posted
Tank you @Hervé. Once again you were right about it. My wifi performance is very good now. I don't know how the chip is build but at the same time the BT is now also working fine! Perhaps, wifi and BT are linked in some way.