Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 04/18/19 in all areas

  1. 2 points
    Hi, Running OSXL have always been a mission we have been proud of - from the early days of D4x0 we could never have imagined that OSXL would grow to what it is today - a safe and nice place where hackintosh and macOS nerds can meet, have fun and play around. But running OSXL also have costs.. hosting.. the forum software.. mail service.. dns .. it cost.. and it never gets cheaper - so faar donations usually covers less than 5% of our operating cost. So.. what todo ? OSXL have always been against showing commercial ads our site - mostly because it slows down the site and ruin the user experience - personally .. i hate a slow website. So, we always explore new options (specially if its fun.. like the seedbox partnership) Anyway, today Brave browser launched - brave browser is (besides being a really nice web browser) - is a browser that allows its users to earn $BAT (a crypto currency) and donate those earned Bat(s) to websites they visit. We have enabled donations to the site - both automatic - but also by using the browsers build-in functionality. Wanna test brave browser? .. head over to: https://brave.com/osx926 (Btw, brave gives us 5 USD for each download, so you having fun testing a new browser, is also helping us and by that yourself) ... and may this be a hint of more fun stuff with cryptocurrencies coming your way //OSXLteam
  2. 2 points
    Last update: 11 Apr 2019 I've finally been able to play with that card on a laptop, fitted with an M.2 2230 Key A+E WLAN slot, that I targeted for Mojave. /!\ The 1st thing I want to report is that I encountered difficulties booting my Mojave USB installer and installing macOS with the card plugged in and without any particular tuning for it. I had to disable wireless in BIOS to be able to install Mojave. Once it was installed, booting Mojave with wireless enabled in BIOS would cause quite severe lag and performance degradation once at the desktop, as if the card just clogged up CPU ressources. /!\ Searching through the Web for that DW1820A/BCM4350, I came accross a few forum posts/threads that mentionned: rolling back the Yosemite IO80211Family kext to get the card to work, although with instability and regular KPs removing AirPortBrcmNIC plugin kext from IO80211Family kext, patching AirPortBrcm4360 plugin kext with the id of the DW1820A and installing AirportBrcmFixup kext with a couple of parameters (Credits to Hugotai, cf. his post @Voldemort's place, 2nd Dec 2018) Whilst I did not really contemplate doing the 1st thing, I did envisage the 2nd one and started to look at the differences between Yosemite's version of IO80211Family kext and Mojave's. The main difference I had already noticed was that device id 14e4:43a3 was handled by AirPortBrcm4360 up to Sierra 10.12 and by AirPortBrcmNIC since High Sierra 10.13. Building on Hugotai's success, I seeked to work out an easier solution that would not require kext removal and Info.plist patching but, instead, something that could be implemented through hardware properties injection, either through DSDT patching or Clover configuration. Once Hugotai's solution was verified and confirmed, I worked out the following Clover-based solution for HighSierra/Mojave: identify the IOReg/ACPI device to which the DW1820A card is attached (use IORegistryExplorer app to that effect) inject the following properties either in DSDT or through Clover (latter recommended): compatibility of the card with Broadcom chips 14e4:4331 or 14e4:4353 that are handled by IO80211Family's PlugIn kext AirPortBrcm4360 optionally, add SysProfiler's cosmetic info such as PCIe Slot, card's make and model, etc. if your raw/BIOS DSDT has no individual entry under the PCI root bridge for the device, select "FixAirport" ACPI Fix in Clover. That'll create a device "ARPT" @0 under the root bridge and that's what you'll inject properties to. and that's it ! Nothing to do to IO80211Family kext ir its PlugIns which all remain untouched/unmodified/full vanilla in /S/L/E. It really could not be simpler... NB: if your card's country code requires to be changed, add the following steps: install AirportBrcmFixup kext in /L/E + repair permissions + rebuild your cache or inject it through Clover's EFI/CLOVER/kexts/Other add boot argument brcmfx-country=XX (where XX is the target value, eg: US, FR, #a, etc.) to the Boot section of your Clover config but, beware, I found that using AirportBrcmFixup has some non-negligable negative impact on wireless performance (much reduced rate). Example: On my laptop, the DW1820A was found attached to device RP03.PXSX located at IO address 0x001C0002, i.e. 1C,2. The DSDT patch required to inject properties could look like this (devices names will differ from one computer to another of course!): Device (RP03) // PCIe Root Bridge { name (_ADR, 0x001C0002) [...] [...] [...] Device (PXSX) // DW1820A card attached to this device (FixAirport fix required if such device is missing) { Name (_ADR, Zero) [...] [...] [...] Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package () { "AAPL,slot-name", // Optional Buffer () { "WLAN" }, "device_type", // Optional Buffer () { "Airport Extreme" }, "name", // Optional Buffer () { "Airport" }, "model", // Optional Buffer () { "Dell DW1820A 802.11ac wireless" }, "compatible", // Mandatory Buffer () { "pci14e4,4331" // Declares compatibility with BCM94331; "pci14e4:4353" for BCM43224 may also be used } }) } } } An easier alternative is to inject those properties in Clover via Clover Configurator app. This can be done within the Devices section by injecting the desired properties in the Properties sub-section: In the left part, add the PCIe address of the targeted device in the form PciRoot(0x0)/Pci(<root device address>)/Pci(<actual device address>) In the right part, add the above properties in single lines and with the right types (String, Data, Number) For instance, in the case of my laptop, the target device will be PciRoot (0x0)/Pci(0x1C,0x02)/Pci(0x0,0x0) for PCI0@0->RP03@1C,2->PXSX@0. Then, properties will be injected as lines of keys of 3 x possible types: strings, hex data blocks or numbers. For instance, to declare compatibility with 14e4:4353, the line will consist of Property Key set to compatible, Key Value set to pci14e4,4353 and Key Type set to STRING. The complete properties injection will be: Device = PciRoot(0x0)/Pci(0x1c,0x02)/Pci(0x0,0x0) Key = compatible | Value = pci14e4,4353 | Type = STRING Key = AAPL,slot-name | Value = WLAN | Type = STRING (optional) Key = device_type | Value = Airport Extreme | Type = STRING (optional) Key = name | Value = Airport | Type = STRING (optional) Key = model | Value = Dell DW1820 (BCM4350) 802.11ac wireless | Type = STRING (optional) Once the device properties are injected in Clover or DSDT, there's nothing left to do but reboot the computer. The DW1820A card will then be fully active and capable to connect to 2.4/5GHz networks at full speed. On the Bluetooth side, once the usual Rehabman's kexts are installed (BrcmFirmwareRepo + BrcmPatchRAM), the BT4.1 module will be fully operational and capable of supporting AirDrop and Handoff! Links: Clover Configurator app Rehabman's Broadcom Firmware patching kexts Acidanthera AirportBrcmFixup kext
  3. 1 point
    HP Pavilion 17-f202ns Specifications: BIOS F.53 Intel i5-5200U CPU @ 2.20GHz chipset Intel Intel® HD Graphics 5500 8Gb DDR3-1600 RAM Realtek RTL8139 PCI Express Fast Ethernet HP Broadcom BCM94352HMB Combo WiFi + BT 4.0 Realtek (codec ALC290) HD Audio + HDMI Audio Realtek 5:1 SD*MS/pro*MMC*XD card reader USB-internal HP webcam Synaptics touchpad CD/DVD drive 1 x USB 2.0 2 x USB 3.0 1 x VGA output (Don't test work). 1 x HDMI output Combo minijack Headset jack output / Microphone jack input In this pack I upload all kext to work, DSDT patch, config plist and OsxAptioFix2Drv-64.efi patch I use Clover 4270 because an other breaks my WiFi or Bluetooth connection. If you not use my OsxAptioFix2Drv-64.efi patch, you can have sporadics kernel panic on boot. Special thanks to EMlyDinEsH & Sherlocks for your support... Enjoy this this full hack... PD. I add fix to right time in dual boot. Archivo comprimido.zip Local Time Toggle.pkg.zip
  4. 1 point
    As far as I know, that card will definitely cause trouble until the property injection is done (or the other older alternatives such as removing the BrcmNIC Plugin kext).
  5. 1 point
  6. 1 point
    You have a patched AppleHDA.kext or modified version in /S/L/E, restore it with a vanilla version from your USB installer. Repair permissions and rebuild cache.
  7. 1 point
    Try this one. Or just remove the Wifi FakeID and add to boot arg brcmfx-country=#a config.plist.zip
  8. 1 point
  9. 1 point
    No idea. I use latest Lilu + latest AppleALC on my laptop with ALC256 (injecting layout 11) and all is Ok. This being said, if this is the only gremlin with audio, I suggest you live with it.
  10. 1 point
    ??? If you're running full vanilla, could this be rogue leftovers from stuff you did during your efforts to get audio going? You could always try to temporarily set your Hack to a non-English language, log out or reboot, log back in or restart, then change again the English.
  11. 1 point
    Install or inject CodecCommander kext. I've no idea what you mean by changing the audio PrefPane to English. As far as I know, that should run with whatever language your Hackintosh is running/setup with. Or you don't have a vanilla installation but a distro that made a mess in there.
  12. 1 point
    Try these instead. Self-explanatory. config.plist_layout_11.zip config.plist_layout_13.zip config.plist_layout_56.zip
  13. 1 point
    Questions around this particular model have resurfaced again so I digged into the matter since most people reported it did not work. DW1820A is based on Broadcom BCM4350 chipset and carries id 14e4:43a3 (subsystem id 1028:0021). It's a pretty good combo card providing 2.4/5GHz 802.11ac wireless at 867Mbps + Bluetooth 4.1. Its Broadcom chipset is normally supported since Yosemite 10.10 and its hardware id is listed in the Info.plist file of IO80211Family's PlugIn kext AirPortBrcm4360 up to macOS Sierra 10.12, then AirPortBrcmNIC since macOS High Sierra 10.13: <key>Broadcom 802.11 PCI</key> <dict> <key>CFBundleIdentifier</key> <string>com.apple.driver.AirPort.BrcmNIC</string> <key>IOClass</key> <string>AirPort_BrcmNIC</string> <key>IOMatchCategory</key> <string>IODefaultMatchCategory</string> <key>IONameMatch</key> <array> <string>pci14e4,43ba</string> <string>pci14e4,43a3</string> <string>pci14e4,43a0</string> </array> <key>IOProbeScore</key> <integer>1241</integer> <key>IOProviderClass</key> <string>IOPCIDevice</string> <key>TruePowerOff</key> <true/> </dict>
  14. 1 point
    @M0CRT How did you get Mirone to come out of retirement? There's no existing ALC289 kexts, not even Mirone's AppleHDA Patcher.
  15. 1 point
    and what about headphone jack?
  16. 1 point
    Fitted the Mojave SSD of the E6220 in my D630 and added the necessary patches for MBP7,1 model: patched PlatformSupport plist (already in place for MBP8,1 SMBIOS on E6220) posted above nVidia kexts/pack from High Sierra 10.13.6 replacement of Mojave's /S/L/UserEventsPlugins/com.apple.telemetry.plugin by High Sierra 10.13.6's version com.apple.telemetry.plugin.zip The results are similar to what's achieved on the E6220 with HD3000: full graphics acceleration with minor defects (more visible in light mode than dark one). Other than the above small graphics limitations, D630 appears fully functional (sleep/wake, LAN, wifi, WWAN, audio, dGPU throttling/AGPM, etc.)
  17. 1 point
    Last update: 16 July 2018 Current Ver: 4.2.7 Suggestions/Discussions: HERE Hello guys, I have seen many instances where people start a thread with the problem they are facing on their hack. They try to describe the issue in their own way that most of the times, is not able to properly describe what's going wrong with their system. The developers and other advanced members on OSXL can point out the problem exactly when they have a set of files, called problem reporting files. These are basically a set of files that contain various logs and some other components. Many a times a normal user can not generate those files properly and it leads to a lot of wastage of good time, frustrated by this, I wrote a script to generate proper problem reporting files. You can have a look at the source code here The purpose of this guide is to tell the normal user on how to generate those files properly for debugging. I wrote a script that automatically installs that debug report generator script and then gives you a .zip output. If you are seeking help about a problem and you must attach problem reporting files as it saves a lot of time. How to generate debug report:- It is very simple, you just have to download the attached script and run it. The script in attachment will install the tool for you and will then prompt if you want to generate the files. If you want to generate files next time, you just have to invoke: "gen_debug" from terminal (without quotes) How to download and run attached script :- Unzip the downloaded zip file Open terminal Assuming your script is in Downloads folder, type the following code :- chmod a+x ~/Downloads/install_tools.sh ~/Downloads/install_tools.sh Args for gen_debug: You can use custom set of args for controlling gen_debug output, this list will be updated as new features become available gen_debug -u || To update your copy (available from ver2.1+) gen_debug -sysprofile || To include your system profile in the dump (available from ver2.2+) gen_debug -sysprofile txt || To include system profile in the dump but in TXT format Note: Whenever you change anything, you should attach new output of gen_debug. Note 2: It is recommended to update your copy of gen_debug every alternate month (for fixes and new features). To do so, If you are running version 2.1 or above, you can simply type "gen_debug -u" (without quotes) in terminal. If you are running version 2.0 or less, you can use the attached installer script to update your copy. Changelogs: Regards install_tools.zip
  18. 0 points
    i have had that exact issue before. i do not recall my solution though. audio would show in Hebrew. i think it had to do with the audio patches. like find replace.
  19. 0 points
    Tricks to get unsupported GPUs to work in Mojave are reported goosed with 10.4.4 latest beta. If confirmed, this would mean "No Metal = No graphics" from now on in Mojave and a definite/final goodbye to 1st gen Intel HD, HD3000 or other older Tesla cards. It was only a matter of time anyway...
This leaderboard is set to Amsterdam/GMT+02:00
×
×
  • Create New...