Jump to content

Broadcom BCM94350ZAE on Mojave


End3rPower50
 Share

23 posts in this topic

Recommended Posts

On 4/17/2019 at 11:29 PM, Hervé said:

Ok, started from the Clover EFI folder you attached in post #1 and adjusted things.

 

Clover config:

  • added SMBIOS of MBP13,1 (SKL model)
  • generated serial #, MLB, SMUUID, etc.
  • removed all the useless patches you had added  for Brcm4360 kext + IOBluetooth
  • removed all those BrcmFixup related boot options (to begin with)
  • removed the AICPUPM patch (only applicable to Sandy Bridge + Ivy Bridge laptops)

 

Kexts:

  • Cleaned thing up
  • updated to latest versions of Lilu + WEG

 

Give that a try and report accordingly.

 

CLOVER.zip

 

yes, but this error is displayed when I start macOS with your Clover (Many times it doesn't start)

Link to comment
Share on other sites

  • 4 months later...
On 4/26/2019 at 7:39 PM, End3rPower50 said:

I do not know what to do.

On windows, the chipset works perfectly.
On Mac, it doesn't work, on your clover it works but does not always start up and after some minutes macOS is slowing down and Wifi disconnected.

 

is there another way?

Hey Good day, i'm using alienware 15r4 with the exact same card and facing the exact same issue. My wifi works, BT doesn't and when i'm booted into the system it starts to slow down after some time and then the cursor freezes. After that the only way to get in is to reboot the system but then it freezes again. i have the kernel panic logs, i will paste those in some time. If you get any help let me know as well.

Link to comment
Share on other sites

On 4/17/2019 at 3:59 PM, Hervé said:

No need for any kexts, BCM4350 is natively supported since Yosemite. I'm currently using one in my Latitude 7490 running Mojave.

https://osxlatitude.com/forums/topic/11322-dw1820a-broadcom-bcm4350-chipset-under-high-sierramojave/

 

@Hervé can you share your EFI folder from Lattitude 7490? I have a problem even to start installation, I get KP, or restarts or a crossed circle... im fighting with that couple days... :(

Link to comment
Share on other sites

On 9/8/2019 at 5:18 PM, Hervé said:

'Seems you're off-topic... Re: Latitude 7490, there's a guide at OSXL. Now let's keep this old thread dead or on-topic.

Hello Herve, first of all a big thanks to your for your guide on this card. I have followed the guide very closely and everything works for me but the only problem is now my laptop freezes/slow down completely. I notice this specifically happenss when the kernel process exceeds CPU utilization(over and above 100%). I'm attaching my debug files with the kernel panic.

My kexts in S/L/E are all vanilla and untouched. I'm using the bcrmfixes but i can remove then and test. DW1820A gets detected fine. Bluetooth works as well.

 

I'm having problems with the laptop shutting down after maybe 10 min of usage on dell DW1820A. I have added RehabMan's brcm files. Added debug files for the same, the specific kernel panic during the issue was captured here as the debug might not have it, cos the wifi card disappears after reboot once the computer has gotten into a stuck state.

Also, all my kexts are in /L/E and vanilla in S/L/E. I do have injection of properties in devices in config file.

KP stack:
==============================================
*** Panic Report ***

panic(cpu 0 caller 0xffffff8008b8780f): Kernel trap at 0xffffff7f8b0b9880, type 13=general protection, registers:

CR0: 0x000000008001003b, CR2: 0xffffff83b11bd000, CR3: 0x000000001e7a9000, CR4: 0x00000000003627e0

RAX: 0x451b0000c00cdefa, RBX: 0x0000000000000000, RCX: 0xb7ca618dfcc4abbb, RDX: 0x00000000000004e2

RSP: 0xffffff83c4083db0, RBP: 0xffffff83c4083e40, RSI: 0xb7ca618dfcc4abbb, RDI: 0xffffff835091a000

R8: 0xffffff805850b680, R9: 0x0000000000000030, R10: 0x0000000000000003, R11: 0xffffff7f8b5507f0

R12: 0x0000000000000000, R13: 0xffffff83507d6000, R14: 0x0000000000000000, R15: 0xffffff835091a000

RFL: 0x0000000000010286, RIP: 0xffffff7f8b0b9880, CS: 0x0000000000000008, SS: 0x0000000000000010

Fault CR2: 0xffffff83b11bd000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 0, VF: 0


Backtrace (CPU 0), Frame : Return Address

0xffffff800894c290 : 0xffffff8008a6bf96

0xffffff800894c2e0 : 0xffffff8008b95354

0xffffff800894c320 : 0xffffff8008b875e4

0xffffff800894c390 : 0xffffff8008a1dfb0

0xffffff800894c3b0 : 0xffffff8008a6ba0c

0xffffff800894c4e0 : 0xffffff8008a6b7cc

0xffffff800894c540 : 0xffffff8008b8780f

0xffffff800894c6b0 : 0xffffff8008a1dfb0

0xffffff800894c6d0 : 0xffffff7f8b0b9880

0xffffff83c4083e40 : 0xffffff7f8b0bb072

0xffffff83c4083e80 : 0xffffff8009072ae4

0xffffff83c4083f00 : 0xffffff8009072437

0xffffff83c4083f50 : 0xffffff8009074096

0xffffff83c4083fa0 : 0xffffff8008a1d557

Kernel Extensions in backtrace:

com.apple.driver.AirPort.Brcm4360(1250.20.1a4)[02416E9C-DABE-382E-A149-6560D4C0374A]@0xffffff7f8b0a8000->0xffffff7f8b633fff

dependency: com.apple.driver.corecapture(1.0.4)[628D1E92-6155-3541-A46E-0A7BA6DDBC09]@0xffffff7f8af74000

dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[378074CD-44A2-3884-9C27-FE4D45DEB99E]@0xffffff7f8abe2000

dependency: com.apple.iokit.IO80211Family(1200.12.2)[ED57651A-7FF4-394B-9662-81C19B00007A]@0xffffff7f8afa7000

dependency: com.apple.iokit.IOPCIFamily(2.9)[9C640A56-0FCC-39B4-B469-31F6ED15228E]@0xffffff7f892cf000

dependency: com.apple.iokit.IONetworkingFamily(3.4)[5A99D802-B477-3D83-9F76-304605479B9F]@0xffffff7f8a2b4000


BSD process name corresponding to current thread: kernel_task

Boot args: dart=0 nvda_drv=1 kext-dev-mode=1 -xcpm -disablegfxfirmware brcmfx-driver=1 brcmfx-country=IN

 

Thanks in advance.

debug_16404.zip

Link to comment
Share on other sites

1 hour ago, Hervé said:

Let's not re-invent the wheel here... Since April, BCM5350 / DW1820A matters have been subject to substantial discussions at OSXL. Now that we've reached September, I do not see the relevance of engaging in renewed or identical discussions here at IM and will not do so. I suggest you go back to OSXL, read all the literature posted there about BCM4350 / DW1820A and, once you've done that, eventually report your own issue which clearly does not differ from what many other people have too reported in the past. What you'll find, however, are suggestions of actions you may take to try and fix the issue.

Appreciate your reply but I have gone through the OSXL forum for the same as well, as i mentioned everything works except for the slowness and getting frozen issue.

Link to comment
Share on other sites

 Share

×
×
  • Create New...