Western Digital, a leading provider of drive solutions, has upgraded its product line of My Passport HDDs by a new model My Passport Edge. In accordance with the company's developers, the new HDD is known to be compatible both with PC and Mac computers, as well as, with Apple Time Machine.

Atheros Ar5007eg Driver

Compaq Atheros Ar5007 Drivers For Mac

• Similar Content

  • By bostonsam10
    

    Hi to everyone this is my first post if I'm doing something wrong please send me the link with the inications for the forum.
    I have a dell 15 vostro with QUALCOMM ATHEROS QCNFA453 where can I see if this card is supported ? Do anyone know if I can find a guide to help me?
    Mojave version 10.14.1 installed via niresh mojave
    
  • By Drovosek
    

    Hello.
    I have system unit Dell Vostro 3267 (i5-6400, Skylake). Information in signature.
    In this system block module installed Atheros AR9565 802.11 b/g/n Wireless Network Adapter, which, as I understand it, combines Wi-Fi - Atheros AR9565 and Bluetooth Qualcomm QCA9565.
    I managed to get working Wifi with kext from chunnann.
    https://www.insanelymac.com/forum/topic/312045-atheros-wireless-driver-os-x-101112-for-unsupported-cards/?page=17&tab=comments#comment-2509900
    https://www.insanelymac.com/forum/topic/328426-qualcomm-atheros-ar9565-wireless-for-os-x-108-1014/
    Bluetooth works only if you first boot into Windows and then reboot into macOS from it. At the same time, you need to install drivers for bluetooth in Windows from the official Dell website, because the original drivers that Windows downloaded and installed itself - did not allow the bluetooth module to work even in Windows.
    In bluetooth settings, the power button was inactive and there was an eternal search for devices (if macOS was loaded immediately after the PC started). Enable button disable I cured just by adding the folder /kexts/Other kext BrcmBluetoothInjector by writing inside it in the Info.the plist file corresponds to the VendorID and ProductID of my bluetooth (which are displayed in the system report). BrcmBluetoothInjector_Mod.kext.zip
    I am disappointed that Windows is able to automatically download the firmware to the bluetooth module during the download, and Hackintosh macOS has not yet done such a kext.
    In the search for solutions to the problem I came across here are the options for the text:
    IOath3kfrmw (OS-X-Atheros-3k-Firmware)
    https://bitbucket.org/RehabMan/os-x-atheros-3k-firmware/downloads/
    https://github.com/RehabMan/OS-X-Atheros-3k-Firmware
    OS-X-BrcmPatchRAM
    https://github.com/the-darkvoid/BrcmPatchRAM
    https://github.com/RehabMan/OS-X-BrcmPatchRAM
    https://bitbucket.org/RehabMan/os-x-brcmpatchram/downloads/
    https://bitbucket.org/anonymous_writer/os-x-brcmpatchram-catalina/downloads/
    https://github.com/headkaze/OS-X-BrcmPatchRAM
    BTFirmwareUploader (as I understand it, this is an improved IOath3kfrmwr)
    https://osxlatitude.com/forums/topic/2925-bluetooth-firmware-uploader/
    And here's a way - to use a virtual machine to the OS from it to download the firmware to the bluetooth module
    https://osxlatitude.com/forums/topic/10127-updated-nov-2017-fix-btfirmwareuploader-in-macos-high-sierra/
    Unfortunately, not one of these options did not help me to ensure that bluetooth worked when 'cold' start the PC in macOS.
    1.
    I started to read more about kexts. In texte BrcmPatchRAM says that it is possible to add support for their bluetooth module in this kext. I downloaded the drivers for my bluetooth from the official site and extracted from .exe installer driver files themselves (This is easily done using 7-zip in Windows or using Keka in macOS). There were more files .dfu than others. As I found out .dfu files are compiled firmware files that the driver loads into the bluetooth module. In the instructions to BrcmPatchRAM States only .hex firmware files for Broadcom.
    I started looking for information on the Internet and found out that .hex files are the original 'text' of the firmware as well .dfu is compiled .hex files.
    I immediately started looking for converters/decompilers/disassemblers from .in dfu .hex, but found only what's out .hex does .dfu file:
    https://github.com/pjsg/hex2dfu
    https://github.com/plietar/dfuse-tool
    https://github.com/kuro68k/ihex2dfu
    https://github.com/vpelletier/python-dfu
    As well as console utilities 'dfu-tool' and 'dfu-util' in Linux. I found out that dfu-util can be installed in macOS using Homebrew or use this option (it differs in functionality) https://github.com/the-darkvoid/dfu-util-osx
    2.
    I also learned that .dfu files are used in macOS /System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothUSBDFU.kext/Contents/Resources
    I think we should try to replace all of them on that file that Windows loads the bluetooth module (I think if you try to do so, you need to make several copies of this file and rename it to the original ones .dfu files to be deleted).
    3.
    As is the idea is just mine .dfu file rename to file .zhx and add it to the kext OS-X-BrcmPatchRAM (in BrcmFirmwareRepo.kext). But there is a problem - first, I don't know which one .dfu files are downloaded to my bluetooth, maybe even a few, because there are 3 files > 40 KB IN size and a lot of files ~ 2 KB in size.
    4.
    In 'dfu-tool' and 'dfu-util' I saw commands that extract firmware from the device. Maybe it will be possible to boot into Linux and if bluetooth starts working there, then try to extract the firmware from bluetooth with these utilities, and then add this firmware to kexts somehow.
    5.
    In the file BTFirmwareUploader.kex/Contents/MacOS/BTFirmwareUploader inside already have a list of firmwares, but they are in .hex format. Maybe there's a way to replace them with the contents .dfu file?
    I will continue to describe the ideas and results of the experiments. If you have any ideas or you can help to solve this problem, do not hesitate to write.
    Screenshots:
    Links to download drivers:
    
  • By Slice
    

    I successfully installed macOS 10.11.6 and Windows 7 Pro SP1 in UEFI mode on the laptop.
    I know, there are detailed guides here and on osxlatitude.com but I was not agree with them and carefully check and test every step to tune my Mac.
    Hardware
    Intel® Core� i5-3320M CPU @ 2.60GHz, speedstep works with Clover default settings
    Chipset Intel 7 series, no patches needed
    Video: IntelHD4000 or NVS5200M switchable in BIOS, work in both cases
    LAN; Intel 82579LM, works with IntelMausiEthernet.kext v2.2.1
    Audio: IDT 92HD93BXX, works with VoodooHDA 2.9.0.
    SDHC reader O2Micro; works with native AppleSDHC.kext with Clover Arbitrary properties.
    USB3.0 works natively if not disabled in DSDT
    PS2 keyboard and touchpad works with VoodooPS2.
    WiFi: Dell Intel WiFi was replaced by Dell DW1520, Broadcom BCM943224HMS. DeviceID=4353
    LCD Screen 1366x768
    BIOS A12. Initially was A02. Then I flashed A23 and found it is quite bad. The screen is full of artefacts. Flash A12 and all is OK. Not tested other versions.
    For some reason BIOS can switched from Intel to Nvidia by itself so I have to do my solution working independent on this state.
    WiFi
    It is not working OOB although it has DeviceID known to Apple. The reason is WhiteList in the driver.
    I set MacModel as MacBookPro10,1 while the WiFi will work on MacBookAir. I make a patch in Clover.
    As well a patch for channels.
    I deleted a kext Brcm4331 because it has the same DeviceID. Let kext Brcm4360 to work alone.
    VideoCards
    In Bios we can set Optimus = Enable/Disable
    If Enable then we have two videocards Intel first and Nvidia second. In this case additional SSDT-3.aml will switch off Nvidia.
    If Disable then we have only Nvidia card. It will work if Board-ID taken from iMac13,2.
    But here there is contradiction with WiFi with required Board-ID from MacBookAir.
    So I take MacModel as MacBookPro10,1 which is most close by CPU IvyBridge.
    Set BoardID like iMac13,2 to make Nvidia working.
    Patch BoardID in Brcm4360 to make WiFi working.
    Now I have
    Inject->
    ->Intel=YES
    ->Nvidia=YES
    and SSDT-3.aml in ACPIpatched folder. This SSDT will switch off Nvidia if Intel card ON.
    For Intel graphics there is a patch against 8 apples at start.
    This Nvidia 5200 is Fermi and works in ElCapitan.
    Brightness
    No special kexts.
    The brightness controlled by keys F1,F2 and slider in Control Panel in both case Intel or Nvidia. Details here #72
    DSDT and SSDT
    This is very long story and finally I have working sleep in both cases Intel or Nvidia.
    Sensors
    I use my HWSensors3 with FakeSMC 3.5.2.
    I got monitoring:
    CPU temperature
    GPU temperature
    GPU main frequency
    GPU shader frequency
    Battery state % full, time to charged or time to empty.
    Battery voltage dinamically.
    Battery amperage dynamically. I can see it changes on heavy games.
    HDD temperature.
    Audio
    I like VoodooHDA and have no problems with it.
    The sound is clear, loud, and switchable between internal speaker and headphone.
    Mic is working.
    Bluetooth
    Just tested with BTFirmwareUpdate.kext and it works in 10.11.6. I not needed it so switched off by wireless switch at right side.
    For 10.13.6 there is other kext BRCMInjector.
    Keyboard, Touchpad and Touchstick
    Post #14
    I made my fork of the VoodooPS2 driver, take here sources and release version
    https://github.com/SergeySlice/VoodooPS2-for-ALPS
    My config, ACPI files and kexts are in attachment.
    05.12.2017
    EFI.7z
    EDITED:
    Better DSDT in the post #6.
    Sleep working even when AC inserted.
    EDITED 06.12.2018
    Now I have HighSierra and this is my EFI folder. Note, HighSierra is possible only with Intel graphics (Optimus is enabled in BIOS)
    Welcome to discussion!
    EFI-E6430.7z
    BRCMInjector.kext.zip
    
  • By Gabigeek
    

    Hi everybody,
    First this is my first post on this forum so I hope Im creating a topic at the right place
    Im french, so sorry for my bad english
    So I recently made a Hackintosh Laptop (on a ROG GL553VD-DM078T )
    This laptop is based on a i7 7700HQ and a GTX1050.
    I installed MacOS Sierra using the Clover bootloader and succesfully installed the kexts needed but one of them is causing trouble.
    I Broke my internal ethernet Port so I must use a USB-C ethernet dongle in order to acces the internet ( The Integrated Wifi chipset isn't compatible so that's my only way to connect.)
    Without the UsbInjectAll.kext everything works exept my laptop keyboard wich use USB (yes, the internal ASUS Aura keyboard use USB interface, not PS2 or IC2 ).
    But if I load the UsbInjectAll kext the keyboard works, but the USB-C ethernet dongle is no more recognized at all ( not even in the system report menu)
    The weird thing is that if I plug a USB stick in the USB-C port, it works, but the ethernet dongle won't.
    So now I have 2 options :
    -or I load the UsbInjectAll kext and I get my keyboard to work
    -or I disable the UsbInjectAll kext so i can get back my ethernet USB-C dongle to work, but no more keyboard....
    Can someone explain why do this happen ? Is there a way to get both The Ethernet dongle and my internal keyboard to work at the same time ?
    If Needed, I can provide more information about the hardware Used etc.
    Have a good Day/night
    
  • By metaphysician
    

    hi folks! i'm just checking for opinions here on a Clover based install of High Sierra. currently i can't boot directly from the internal drive on my hackbook, an ASUS ROG GL502-VS laptop (with the replaced WiFi card), though i can boot from the USB bootloader/installer
    i installed 10.13.6 fine using a prepared vanilla installer on HFS+ (not APFS), but my configuration is somewhat unusual. i have two drives. the first SSD has the Windows system, the second has two partitions with the 2nd partition holding the macOS system. when i ran Clover installer i could not use the UEFI option to copy to the EFI partition because it couldn't find one on that drive. so it installed the EFI folder on the root of the macOS partition instead.
    however, after a bit of tinkering around, i found out that there is an existing EFI partition on the primary drive called SYSTEM. it has a EFI folder and underneath that is a Windows folder, a Boot folder, and one called APPLE. i can mount this partition with Clover Configurator and copy files to it, but i don't know if this is a good or risky solution. i was thinking i would manually copy the CLOVER folder and the uefi64.boot file to this partition , making sure not to overwrite anything existing. using the UEFI setup, i can create a boot path from the SYSTEM partition to the Clover boot file, but i'm just curious if this is a useful solution or not, and i don't want to ruin the existing Windows 10 installation for sure. any advice appreciated!
    

Atheros Ar5007 Wireless Network Adapter