Jump to content

lvs1974

Coders
  • Content Count

    81
  • Joined

  • Last visited

About lvs1974

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. lvs1974

    AirportBrcmFixup

    I don't think driver can fix it. Once I isolated pins by scotch tape -> it works. I never tried to remove it and check again.
  2. lvs1974

    AirportBrcmFixup

    When I started using this 43b1 device in may laptop I couldn't turn it on. I had to isolate two pins.
  3. lvs1974

    AirportBrcmFixup

    You can try Clover DSDT Fix_Airport + Fake ID: 4353 + AirportBrcmFixup.kext
  4. lvs1974

    AirportBrcmFixup

    Just for debugging/checking of faking id functionality in AirportBrcmFixup.
  5. lvs1974

    AirportBrcmFixup

    @rooney08, I would try to install 10.13.6 and check it with the same hardware. Sometimes ACPI methods can turn off hardware using dedicated pins.
  6. lvs1974

    AirportBrcmFixup

    @rooney08, it is hardware issue, your device is turned off. You should try to isolate one or two pins on you card, please read here: https://gsid.in/using-old-mini-pcie-wlan-cards-in-modern-laptops/
  7. lvs1974

    RTCMemoryFixup?

    The goal is the same - to avoid of cmos reset, but with RTCMemoryFixup it is possible to use all banks of cmos memory (256 bytes), and simulate writing into some critical bytes (you need to find which ones).
  8. lvs1974

    AirportBrcmFixup

    @KristFlex, On laptops the same cards can work/don't work in a different way since DSDT can control this card using PCIe pins. There are two ways to fix it: 1 - isolate this pin, 2 - fix DSDT For desktops might be easier.
  9. lvs1974

    AirportBrcmFixup

    @KristFlex, You could try to fake using arbitrary properties in clover (you will find examples in this topic). brcmfx-driver actually forces OSX to use only one driver, it is possible to achieve this by removing AirPortBrcmNIC or AirPortBrcmNIC-MFG. And you always have an alternative: ask people with cards work with 10.13/10.14 and replace yours. I can't help you if your card just incompatible with OSX for some reason.
  10. lvs1974

    AirportBrcmFixup

    No, it is not quite true about 43a3 and 10.11 (it was not moved): 10.8 AirPortBrcm4360: 43a0, IOProbeScore = 641 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 615 10.9 AirPortBrcm4360: 43a0, IOProbeScore = 842 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 700 10.10 AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 930 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 900 10.11 AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1040 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 10.12 AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1152 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 10.13 AirPortBrcm4360: 4331, 4353, IOProbeScore = 1240 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1241 AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000 10.14 AirPortBrcm4360: 4331, 4353, IOProbeScore = 1400 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400 AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000 43a3 was moved in 10.13. So, till 10.13 it should work. In 10.13 and higher you could try other fake-id (see this topic how to properly set fake-id).
  11. lvs1974

    AirportBrcmFixup

    @fallen00sniper, Sorry to hear that. You can check by yourself in any hex-editor all patches - you will find a patch pattern if it is compatible. You can save all wi-fi drivers from 10.13 DP0, try to install 10.13.1-10.13.6, check all patch pattern, if they are incompatible -> replace all wi-fi drivers with ones from 10.13 DP0 and continue investigation. Also you can try to find people with the same wi-fi card and ask them what do they use (OSX version + patches/fake-id/AirportBrcmFixup).
  12. lvs1974

    AirportBrcmFixup

    @ellaosx, Yes, it is correct.
  13. lvs1974

    AirportBrcmFixup

    By default it is "-1", it means MFG kext will be disabled.
  14. lvs1974

    AirportBrcmFixup

    @fallen00sniper Anyway, it would make sense to fix DSDT issues.
  15. lvs1974

    AirportBrcmFixup

    @fallen00sniper Yes, that was my idea - first of all to try these patches, without AirportBrcmFixup. Once you get Wi-Fi working, we need to find a critical patch.
×