Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 03/29/23 in all areas

  1. Laptop Specs: Intel Core i5 7300U RAM: 16 GB 2133 MHz DDR4 Graphics: Intel HD Graphics 620 SSD: 1Tb (macOS) SMBIOS: MacbookPro 15,1 Working: Graphic acceleration Brightness control Keyboard brightness control Wifi and Bluetooth: Intel Bluetooth and intel AirportItlwm All USB-C and USB3 (type-A) ports Video over USB-C Audio, incl. integrated microphone Sleep Ethernet HDMI output Touchpad Integrated camera Card reader MacBook Pro 15,1.ioreg WARNING: Generate your own SMBIOS EFI zip part 1: EFI_Sonoma_7280 2.zip to extract add to de file format .001 (EFI_Sonoma_7280_2.zip.001) EFI zip part 2: EFI_Sonoma_7280 2.zip to extract add to the file format .002 (EFI_Sonoma_7280_2.zip.002) I couldn't upload the full EFI here because the file is too large but you can download it here: https://mega.nz/file/xlhjlTjb#zCu_C5_k1pR6zqOXnVERUHdJjqHSA_JxYpvTOke5yn4 Enjoy! EFI_Sonoma_7280_1.zip
    3 points
  2. Just replace the SSDT in the E7470 with E7270 from my Ventura guide
    2 points
  3. List of dropped platforms extends to Intel 7th gen. Kaby Lake this year, yet KBL graphics drivers are retained to support ABL graphics (2018 MacBook Air8,1). This is good omen for Kaby Lake platforms of course but especially for Skylake platforms that are able to re-use the same tricks used for Ventura, i.e. fake a KBL iGPU id and call on a KBL framebuffer. At least in this 1st beta version.... Bad news on the wireless front: IO80211FamilyLegacy kext is gone and, with it, native support for Broadcom cards based on BCM4350 and BCM4360 chipsets which includes DW1820A and all those Apple BCM94360xxx that we could use up to Ventura. We'll see if this can somehow be addressed through a patch of some sort. Interestingly enough, support for Broadcom Bluetooth appears to remain untouched, at least as far as the BT module of the Apple BCM94360CS2 card is concerned. Meantime, I called on an old TP-Link TL-WN725N v3 Wireless N Nano USB adapter that I had lying around. It's crap (802.11n 150Mbps) but will do for the moment. It's based on Realtek chipset RTL8188EUS (PCI id 0bda:8179). Other than that, nothing to report after just a brief spell with Sonoma 1st beta. Installation on my Skylake Latitude E7270 was pretty much painless: from Ventura, I updated Clover to r5151 (just in case), updated my add-on kexts to latest versions (Lilu & PlugIns mostly) and, in my Ventura Clover config, changed SMBIOS to MBP15,2 (necessary) and added boot arg -lilubetaall (also necessary). I then rebooted Ventura and launched the Sonoma installation package. Upon completion, I found that LAN, audio and external video outputs worked better if I used the combined boot args -lilubeta -wegbeta -alcbeta instead of single boot arg -lilubetaall. NB: Sonoma boots/works the same way if, instead of SMBIOS MBP15,2, I boot it with SMBIOS MBP13,1/MBP14,1 and add -no_compat_check boot arg. Avoid MBP15,1 on Skylake laptops, it prevents external video outputs for instance. Working: graphics acceleration with same KBL settings as in Ventura brightness control HDMI output mini-DP output touchscreen audio (incl. DP/HDMI audio) LAN Apple (Broadcom) BCM94360CS2 Bluetooth but a bit erratic at times (on startup and after wake) touchPad USB ports sleep wake but troublesome if hibernation is disabled so it's best to leave things untouched for the moment SD card reader Not working: Apple (Broadcom) BCM94360CS2 wireless
    2 points
  4. There's so much non-sense (not to say worse) said and written all over the Hackintosh forums again with this forthcoming new release, I sometimes long for the death of Hackintosh so that it all stops once and for all. Sonoma 1st beta is hardly out that, once again, the weeping divas (who should all have accompanied Silvio Berlusconi's last concubine at his funeral to show their expertise on the matter) are at it! Among them, we find those whose life is being torn apart by Apple because they've lost Wifi with (unreleased) Sonoma, those who cry foul at Apple's renewed attacks against Hackintoshers, those who predict millions of business loss for Apple and those who just speak out of their arse (latter probably being a good summary of all the others)! This time, it's all about Broadcom wireless cards... So what's the situation? Well, it's very simple: Apple has completed its migration to Apple Silicon, the last Intel model (MacPro7,1) has been dropped. So, all those who write about "when Apple complete their migration" need a serious awakening. It's done boys, it's done! And exactly as expected... The last (Intel) Mac platforms that used Broadcom cards based on BCM4350 or BCM4360 are dropped. As such, Apple no longer intends to provide drivers, just as they do for dropped GPUs. It should come to no surprise to anyone, it's the way Apple has worked for the last... 11 years (remember Mountain Lion in 2012 ?) not to say more (14 years, if we consider the way PPC platforms were dropped in 2009 with the release of Snow Leopard). I've seen here and there so-called Hackintosh experts/gurus writing they believe Apple dropped the Broadcom legacy cards because the platforms supported by Sonoma don't even have Broadcom wireless inside, then that they have Broadcom wireless therefore support for older cards will return. That's a good example of what I mean about people talking out of their arse. Let's recap a few things here: Sonoma 1st beta officially drops 7th gen. Kaby Lake platforms (on top of older ones of course) but, for the moment, retains KBL graphics drivers. Why? Simple: because it's required to support Amber Lake UHD617 graphics of MBA8,1. Sonoma 1st beta drops Broadcom legacy 802.11ac wireless chipsets that Ventura still supported through IO80211FamilyLegacy kext: 14e4:43ba, 14e4:43a3 and 14e4:43a0, i.e. BCM43602, BCM4350 and BCM4360. Big Sur had already dropped support for the last 802.11bgn cards that Apple had retained up to Catalina. Supporting those older 802.11ac chipsets through a kext bearing the name "legacy" since macOS Monterey should have been quite an obvious hint in itself as far as what the future held... Sonoma 1st beta supports only the following Broadcom chipsets: 14e4:43dc, 14e4:4464, 14e4:4488, 14e4:4425, 14e4:4433 and 14e4:4434, i.e. BCM4355 (802.11ac), BCM4364 (802.11ac), BCM4377b (802.11ac), BCM4378 (802.11ax), BCM4387 (802.11ax) and BCM4388 (802.11ax). Afaik, all those are provided as specific SOCs to Apple by Broadcom, i.e. chips to be soldered on Apple motherboards and not available on add-on mini-PCIe/M.2 cards. https://wikidevi.wi-cat.ru/Broadcom With regards to the wireless chipsets fitted to Intel Mac platforms supported by Sonoma, it's as follows: 2018 Mac mini8,1 -> BCM4364 (pci14e4,4464) 2018/2019 MacBookAir8,x -> BCM4355 (pci14e4,43dc) 2020 MacBookAir9,1 -> BCM4377b (pci14e4,4488) 2018/2019 MacBookPro15,x -> BCM4364 (pci14e4,4464) 2019/2020 MacBookPro16,x -> BCM4364 (pci14e4,4464) 2019 iMac19,x -> BCM4364 (pci14e4,4464) 2020 iMac20,x -> BCM4364 (pci14e4,4464) 2017 iMacPro1,1 -> BCM4355 (pci14e4,43dc) 2019 MacPro7,1 -> BCM4364 (pci14e4,4464) Let's hope the weeping divas and would-be experts/gurus can put 2 and 2 together...
    2 points
  5. Ventura - OpenCore Installation: Download MacOS Ventura app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Note: Replace Config.plist with Config-IntelWifi.plist if you have an Intel combo card (not tested) SMBIOS, ig-platform-id, device-id, USBPorts kext set to MacBookPro14,1 to support Ventura OC 0.8.5 includes latest Alps by SkyrilHD, supports Alps v7/8 for multi touch Updated to 0.8.5 - Supports Ventura only, won't boot for Monterey and below E7270_OC_0.8.5.zip E7470_OC_0.8.5.zip
    2 points
  6. Revised wireless kexts for Sonoma 14.4, the previous ones not providing wifi service beyond Sonoma 14.3. OCLP 1.4.1 or later required too. Wifi_kexts_Sonoma_14.4.zip
    1 point
  7. Ok I’m a mechanic and not great with computers I was using proper tree to add kexts, it was putting them in the wrong order I rearranged them and it’s working, so dell e7440 touchscreen needs voodoo2c and voodoo2chid put them at the end manually not with proper tree, thanks for the help
    1 point
  8. @BillDH2k After pasting your GPU config block on top of my config, I've got HDMI with audio (1080p tested) and USB-C DP output (3440x1440 60Hz) running, and backlight control is working normally. I'm very grateful for your help. I'll try the other changes later.
    1 point
  9. Hallo I have a esprimo 756 too the Bios on the Fujitsu PC can't see the OC Bootloader the Trick is this : in your EFI directory, create a folder "MICROSOFT" , in this folder a folder "BOOT" then you put the BootX64.efi from your BOOT folder inside there and rename it to "BOOTMGFW.EFI" then it looks like this : then in the bootmenu you can select a "Windowsbootmanager" and that's it
    1 point
  10. MyHack v3.3.1 carrying bugs for Snow Leopard installations; use older version v3.1.2 instead. myHack_v3.1.2.zip myHack-3.3.1.dmg.zip NB: Those versions can only be run on OS X versions up to Mavericks. They cannot be run on Yosemite and later.
    1 point
  11. No official support for SKL graphics in Sonoma. It requires faking KBL hardware for graphics acceleration since Ventura or OCLP patching. But it's not 100% bug free. Remember that SKL was last officially supported in Monterey. My Skylake/HD520 E7270 does occasionally suffer from graphics bugs in Ventura (flickering, lines, pixelisation, etc.) -and, by extension, Sonoma- at which point laptop requires to be rebooted for macOS to be fully functional again You have to consider that latest macOS versions are not meant to support these older platforms and run on them.
    1 point
  12. can you post new IOReg file? I believe it's due to (_SB.PCI0.I2C0) and not (_SB.PCI0.I2C1) from files I posted Those 2 ssdt definitely suggested that
    1 point
  13. As specified in our wireless cards inventory: No ! Those Qualcomm cards have poor support in OS X/macOS anyway. Go for a fully supported Broadcom card or, better, an Apple Card BCM94360CD on an mini-PCIe adapter board. Look-up our existing threads about this.
    1 point
  14. https://github.com/Baio1977/DELL-Inspiron-5584 use this patch for I2C . Add SSDT I2C speed
    1 point
  15. Last update: 13 Nov 2023 This 2nd inventory comes to complement our original one created back in 2013 which is now restricted to cover wireless cards under Snow Leopard 10.6 to El Capitan 10.11. This new list will provide the equivalent for macOS versions (Sierra 10.12 and later) given that it's getting complicated to keep everything under a single text table and Apple has been increasingly dropping support for wireless cards since the introduction of macOS Sierra in 2016. I invite everyone to bring his/her own contribution and it'll be added to the list. This post will be updated as contributions come along in order to keep the list under control. Hardware specifications can be verified here: https://wikidevi.wi-cat.ru. A few OS X/macOS-related wireless cards buying guides also exist where summarised chipset support is available. Please use your preferred search engine to look these up, we won't provide links since this would infringe our own posted rules. Note: OOB = Out of the Box /!\ Sierra 10.12 dropped support for old Broadcom BCM431x and BCM4321 cards. There is no workaround, they have to be replaced. /!\ /!\ Mojave 10.14 dropped support for Atheros cards. The workaround is to install the Atheros40 kext from an earlier release like High Sierra 10.13.6, i.e. copy to /L/E + repair permissions + rebuild cache. /!\ 10.13.6_AirPortAtheros40.kext.zip /!\ Catalina 10.15 no longer supports injection or caching of High Sierra's AirPortAtheros40 kext. Instead, install High Sierra's IO80211Family kext, i.e. copy to /L/E + repair permissions + rebuild cache (leaving /S/L/E untouched) or, if that does not work, replace Catalina's IO80211Family kext in /S/L/E by High Sierra's. /!\ 10.13.6_IO80211Family.kext.zip /!\ Catalina 10.15 dropped support for BCM4322 (14e4:432b). AirPortBrcm4331 plugin kext of IO80211Family kext was abandoned. This affects cards such as DW1510. Workaround is to simply install Mojave's (or High Sierra's) IO80211Family kext, i.e. copy to /L/E + repair permissions + rebuild cache (leaving /S/L/E untouched) or, if that does not work, replace Catalina's IO80211Family kext in /S/L/E by Mojave's (or High Sierra's) but this will need to be done again after each update because vanilla kexts will be re-installed. /!\ 10.14.6_IO80211Family.kext.zip /!\ Intel wireless: some recent models may now enjoy support thanks to development detailed on OpenIntelWireless Github repo. /!\ Big Sur dropped support for BCM4331 (14e4:4331) and BCM43224 (14e4:4353). A patched version of Catalina's IO80211Family kext may be used as workaround (only AirPort4360 PlugIn is retained). Kext can then be called from OC config by setting minimum kernel to version 20. See here for details. /!\ /!\ Atheros cards previously supported in High Sierra and earlier (eg: AR928x, AR9380) can be supported under Big Sur with a patched version of High Sierra's IO80211Family kext . Kext can then be called from OC config by setting minimum kernel to version 18. See here for details. /!\ /!\ Monterey 12.x does not support patches/workarounds for dropped cards such as Atheros or Broadcom BCM4322. Same for Broadcom BCM4331 or BCM43324. Such cards have to be replaced by models supported in Monterey. /!\ Sonoma drops all official support for Broadcom "legacy" cards that were natively supported up to Ventura (chipsets BCM4350, BCM4360, BCM43602). OCLP patcher is now required for all non-Intel wireless cards that were previously supported. Unsupported: Vendor Model Format Ven-Dev Chip Rate Si HS Mj Ca BS Mt Vt OOB Kext/comment Intel - - - - - - - - - - - - N See here Atheros AR5BXB6 Mini PCIe 168c-001c AR5424 A/B/G N N N N N N N - - AzureWave AW-CB161H ½Min PCIe 10ec-8821 RTL8821AE A/B/G/N/AC N N N N N N N - - AzureWave AW-CB209NF NGFF/M.2 10ec-8821 RTL8821AE A/B/G/N/AC N N N N N N N - - AzureWave AW-CB210NF NGFF/M.2 14e4-43ec BCM4356 A/B/G/N/AC N N N N N N N - - AzureWave AW-NB155NF NGFF/M.2 14e4-4365 BCM43142 B/G/N N N N N N N N - - Dell DW1390 Mini PCIe 14e4-4311 BCM4311 B/G N N N N N N N - - Dell DW1395 Mini PCIe 14e4-4315 BCM4312 B/G N N N N N N N - - Dell DW1490 Mini PCIe 14e4-4312 BCM4311 A/B/G N N N N N N N - - Dell DW1505 Mini PCIe 14e4-4328 BCM4321 A/B/G/N N N N N N N N - - Dell DW1397 ½Min PCIe 14e4-4315 BCM4312 B/G N N N N N N N - (=DW1395) Dell DW1501 ½Min PCIe 14e4-4727 BCM4313 A/B/G/N N N N N N N N - - Dell DW1503 ½Min PCIe 14e4-4727 BCM4313 A/B/G/N N N N N N N N - - Dell DW1504 ½Min PCIe 14e4-4727 BCM4313 B/G/N N N N N N N N - - Dell DW1530 ½Min PCIe 14e4-4359 BCM43228 A/B/G/N N N N N N N N - - Dell DW1540 ½Min PCIe 14e4-4359 BCM43228 A/B/G/N N N N N N N N - - Dell DW1701 ½Min PCIe 14e4-4727 BCM4313 B/G/N N N N N N N N - - Dell DW1704 ½Min PCIe 14e4-4365 BCM43142 B/G/N N N N N N N N - - Dell DW1810 NGFF/M.2 168c:0042 QCA9377 A/B/G/N/AC N N N N N N N - (=QCNFA435) Dell DW1820 NGFF/M.2 168c:003e QCA6174A A/B/G/N/AC N N N N N N N - (=QCNFA344A) Qualcomm QCNFA435 NGFF/M.2 168c-0042 QCA9377 A/B/G/N/AC N N N N N N N - - Qualcomm QCNFA344A NGFF/M.2 168c-003e QCA6174A A/B/G/N/AC N N N N N N N - - Ralink RT5390 ½Min PCIe 1814-539b RT5390 B/G/N N N N N N N N - - Supported: Vendor Model Format Ven-Dev Chip Rate Si HS Mj Ca BS Mt Vt OOB Kext/comment Intel - - - - - - - - - - - - N See here Atheros AR5B91 Mini PCIe 168c-002a AR9281 B/G/N Y Y * * * N N Y * See above for Mojave Atheros AR5BXB72 Mini PCIe 168c-0024 AR5418/5133 A/B/G/N Y Y * * * N N N patch Atheros40 Atheros AR5BXB92 Mini PCIe 168c-002a AR9280 A/B/G/N Y Y * * * N N Y - Atheros AR5BXB112 Mini PCIe 168c-0030 AR9380 A/B/G/N Y Y * * * N N Y - Atheros AR5B22 Mini PCIe 168c-0034 AR94621 A/B/G/N Y ? * * ? N N N FW + Atheros40 patch Atheros AR5B93 ½Min PCIe 168c-002a AR9283 B/G/N Y Y * * * N N Y - Atheros AR5B95 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N DSDT/Atheros40 patch Atheros AR5B97 ½Min PCIe 168c-002e AR9287 B/G/N Y Y * * * N N N DSDT/Atheros40 patch Atheros AR5B195 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B95+BT3.0) Atheros AR5B197 ½Min PCIe 168c-002e AR9287 B/G/N Y Y * * * N N N (=AR5B97+BT3.0) Atheros AR5BHB92 ½Min PCIe 168c-002a AR9280 A/B/G/N Y Y * * * N N Y - Atheros AR5BHB112 ½Min PCIe 168c-0030 AR9380 A/B/G/N Y Y * * * N N Y - Atheros AR5B125 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * ? N N N FW + Atheros40 patch Atheros AR5B225 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * ? N N N FW + Atheros40 patch AzureWave AW-NB037H ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B195) AzureWave AW-NB048H ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B195) AzureWave AW-NB290H ½Min PCIe 14e4-4357 BCM43225 B/G/N Y Y Y Y Y Y Y N DSDT/kext patch AzureWave AW-CE123H ½Min PCIe 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y Y Y Y N DSDT/kext patch AzureWave AW-CB160H ½Min PCIe 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - Dell DW1502 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B95) Dell DW1506 ½Min PCIe 168c-0032 AR94851 B/G/N Y ? * * ? N N N (=AR5B125) Dell DW1510 ½Min PCIe 14e4-432b BCM4322 A/B/G/N Y Y Y * * N N Y - Dell DW1515 ½Min PCIe 168C-002a AR9280 A/B/G/N Y Y * * * N N Y (=Atheros xB92) Dell DW15202 ½Min PCIe 14e4-4353 BCM43224 A/B/G/N Y Y Y Y * * * Y/N MBA5,2/Brcm4360 patch Dell DW1550 ½Min PCIe 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y Y Y ? N DSDT/kext patch Dell DW1601 ½Min PCIe 168c-0034 AR94621 A/B/G/N/AD Y Y * * ? N N N (=AR5B22) Dell DW1702 ½Min PCIe 168c-002b AR9285 B/G/N Y Y * * * N N N (=AR5B195) Dell DW1703 ½Min PCIe 168c-0032 AR94851 B/G/N Y Y * * ? N N N (=AR5B225) Dell DW1705 ½Min PCIe 168c-0036 AR95651 B/G/N Y Y * * ? N N N FW + Atheros40 patch Dell DW1560 NGFF/M.2 14e4-43b1 BCM4352 A/B/G/N/AC Y Y Y Y Y Y ? N DSDT/kext patch Dell DW1707 NGFF/M.2 168c:0036 AR95651 B/G/N Y Y * * ? N N N FW + Atheros40 patch Dell DW1802 NGFF/M.2 168c-0034 AR94621 A/B/G/N Y Y * * ? N N N (=AR5B22) Dell DW1820A3 NGFF/M.2 14e4-43a3 BCM43503 A/B/G/N/AC Y Y Y Y * * * N DSDT patch/injection Dell DW1830 NGFF/M.2 14e4-43ba BCM43602 A/B/G/N/AC Y Y Y Y Y Y Y Y - Fenvi BCM94360NG NGFF/M.2 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - Asus USB-N10 USB 2.0 0b05-1786 RTL8188SU B/G/N ? ? ? ? ? ? ? N RealTek's v2.0.1 Asus USB-AC51 USB 2.0 0b05-17d1 MT7610U A/B/G/N/AC ? ? ? ? ? ? ? N Asus's driver CSL Nano V.2 USB 2.0 0bda-8176 RTL8188CUS B/G/N Y Y Y Y Y Y ? N ? D-Link DWA-121 A1 USB 2.0 2001-3308 RTL8188CUS B/G/N Y Y Y Y Y Y ? N ? Lafalink LF-D10 Nano USB 2.0 148f-7601 MT7601 B/G/N Y Y Y Y ? ? ? N Ralink's v4.2.9.10/RT2870 Driver Lafalink LF-D12 Nano USB 2.0 148f-5370 RT5370 B/G/N ? ? ? ? ? ? ? N Ralink's v4.2.9.2 NetGear WNA3100M USB 2.0 0846-F001 RTL8192CU B/G/N ? ? ? ? ? ? ? N Realtek's v2.0.1 On-Nwrks N300 USB 2.0 0846-F001 RTL8192CU B/G/N ? ? ? ? ? ? ? N Realtek's v2.0.1 Tenda W522U USB 2.0 148f-3572 RT3572 A/B/G/N Y Y ? ? ? ? ? N TP-Link/Ralink TP-Link TL-WN725N v2 USB 2.0 0bda-8179 RTL8188EUS B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN723N v3 USB 2.0 0bda-8179 RTL8188EUS B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN823N v1 USB 2.0 0bda-8178 RTL8192CU B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN823N v2 USB 2.0 2357-0109 RTL8192EU B/G/N Y Y Y ? ? ? ? N TP-Link's driver TP-Link TL-WN823N v3 USB 2.0 ????-???? ???? B/G/N Y Y Y Y ? ? ? N TP-Link's driver Asus USB-AC56 USB 3.0 0b05-17d2 RTL8812AU A/B/G/N/AC ? ? ? ? ? ? ? N Asus's driver Asus PCE-AC66 PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - Asus PCE-AC68 PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - TP-Link TL-WN781ND v1 PCIe x1 168c-002b AR9285 B/G/N Y Y * * * * * N DSDT/Atheros40 patch TP-Link TL-WDN4800 PCIe x1 168c-0030 AR9380 A/B/G/N Y Y * * * * * Y - TP-Link Archer T9E PCIe x1 14e4-43a0 BCM4360 A/B/G/N/AC Y Y Y Y Y Y Y Y - NB: Patching means adding the PCI ids of the listed card to the Info.plist file found inside the listed kext. In rare cases, binary patching may also be necessary. For some cards, DSDT Patching can be a suitable and permanent alternative to kext patching (no need to repatch a kext after OS X updates and upgrades or new installations). For instance, in the case of the Atheros AR5B95 card (chip AR9285 168c,2b), adding compatibility with a chip known to be supported OOB such as AR9380 168c,30 or AR9280 168,2a (as found in the vanilla Atheros40 kext) in a _DSM method for the identified DSDT device does the trick once and for all since it'll make the OS load the associated kext: Device (<YourDevice>) // Identified wireless device through IORegistryExplorer (usually: ARPT) { ... ... ... Method (_DSM, 4, NotSerialized) // Device Specific Method for the wireless card { Store (Package () { "model", Buffer (0x1E) { "Atheros AR5B95 b/g/n Wireless" }, "device_type", Buffer (0x08) { "AirPort" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x10) { "AirPort Extreme" }, "AAPL,slot-name", Buffer (0x09) { "Internal" }, "compatible", // Declares compatibility with a device Buffer (0x0B) { "pci168c,30" // PCI id of device supported OOB } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } ` In the same respect, in the case of the Broadcom BCM4322x cards (e.g.: chip BCM43225 14e4,4357) or BCM4352 cards (14e4,43b1), adding compatibility with a chip known to be supported OOB such as BCM94360 14e4,43ba or 14e4,43a0 (as found in the vanilla AirPortBrcm4360 kext or AirPortBrcmNIC) in a _DSM method for the identified DSDT device does the trick once and for all since it'll make the OS load the associated kext: Device (<YourDevice>) // Identified wireless device through IORegistryExplorer (usually: ARPT) { ... ... ... Method (_DSM, 4, NotSerialized) // Device Specific Method for the wireless card { Store (Package () { "model", Buffer (0x23) { "AzureWare AW-NB290H b/g/n Wireless" }, "device_type", Buffer (0x08) { "AirPort" }, "built-in", Buffer (One) { 0x00 }, "name", Buffer (0x10) { "AirPort Extreme" }, "AAPL,slot-name", Buffer (0x09) { "Internal" }, "compatible", // Declares compatibility with a device Buffer (0x0B) { "pci14e4,43a0" // PCI id of device supported OOB } }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } } ` Broadcom BCM43224-based cards with id 14e4:4353 (e.g.: DW1520) are subject to whitelisting in AirPortBrcm4360 kext. Wireless will only work if using the SMBIOS of a supported Mac model or after binary patching the kext to inject the Mac board-id of the desired SMBIOS. See our patching guide on the matter. ________________ 1 AR946x (168c,34), AR9485 (168c,32) and AR9565 (168c,36) work to some degree (i.e. not 100%) with alternative (re-written) Atheros40 driver as posted at InsanelyMac by Chunnann. Further patching facility posted here. These cards appear very poorly supported to plain unsupported from High Sierra. They are NOT recommended. 2 DW1520 (14e4,4353) is known to suffer from frequent and repeated wireless disconnections when plugged into mini PCIe-only slot and built-in Bluetooth is enabled. This may even lead to wireless turning off. This has been noticed on Dell Latitude E6x20 and E6x30. Wireless works Ok once built-in Bluetooth is disabled in BIOS or, as stated by wl_michael, if the card is fitted into combo PCIe/USB slot such as WWAN. 3 DW1820A and other BCM4350-based cards are supported. See our BCM4350 guide for these cards. * See top of post for Mojave, Catalina, Big Sur, Monterey and Ventura.
    1 point
  16. I already posted a guide and file in my guide above but haven't tested the Intel wireless.
    1 point
  17. Ok, I understand better now... 'was not aware of those very specific MacBookPro updates. I don't believe trying to add the PCI id 10de:0407 to whatever kext is required at all. Your GeForce 8600M GT carries the same id as the nVidia GPU of the MacBookPro3,1. If you look into the Info.plist file of the NV50Hal kext, you should notice the presence of support for 0x040010de with mask 0xfff0ffff. That covers your GPU. I guess you probably need to inject the nVidia properties of your nVidia card into Tiger, either through your bootloader or through a DSDT patch or through an injector kext (like NVInject) if you still manage to find one after all those years. Those would basically inject those necessary properties like NVDA,Parent, ports description, etc. You'll find plenty of examples on Hackintosh forums or here in the Dortania documentation.
    1 point
  18. To switch to Sonoma I recommend SMBios Macbookair 8.1 for Skylake, Kabylake and Kabylake Refresh, the HW gen is practically identical for these series and therefore the use of this SMBios guarantees the best functioning...... MacbookPro 15.x would be a stretch as it has a Coffelake CPU AAPL,ig-platform-id Data 0000C087 or 0500C087 device-id Data C0870000
    1 point
  19. Released Sep 26th, 2023 as announced. Version 14.0, build 23A344 (same as RC2 published Sep 21st). Sonoma drops official support for Kaby Lake platforms that remained supported in Ventura, Apple raising minimal requirements to Amber Lake and Coffee Lake platforms (with the exception of iMacPro1,1 as in Ventura). However, support for Kaby Lake graphics remain provided with all KBL kexts still present, this in order to ensure support for Amber Lake MacBookAir8,1. By extension, this means that graphics support for Skylake iGPUs can also be retained using those same KBL settings as used in Ventura. For other iGPUs, patches are available through OCLP tool to regain graphics acceleration. Officially supported Intel platforms are now limited to : iMac19,x (8th gen. Coffee Lake) iMacPro1,1 (Skylake Xeon) MacBookAir8,1 (8th gen. Amber Lake) MacBookPro15,x (8th gen. Coffee Lake) Macmini8,1 (8th gen Coffee Lake) MacPro7,1 (Cacade Lake) With Sonoma, Apple also dropped official support for what they call "legacy" Broadcom cards that remained supported up to Ventura. These include cards based on Broadcom BCM4350, BCM4360 or BCM43602 chipsets. If Bluetooth remains natively supported on such legacy cards, native Wifi support is now limited to those Apple proprietary Broadcom SOCs that have been fitted to the above Mac models. Support for "legacy" Broadcom cards can however be recovered with specific patching using OpenCore bootloader, kexts blocking and OCLP patches. Officially supported Broadcom SOCs include: BCM4355 (802.11ac): pci14e4,43dc (iMacPro1,1 + MacBookAir8,x) BCM4364 (802.11ac): pci14e4,4464 (Mac mini8,1 + MacBookPro15,x + MacBookPro16,x + iMac19,x + iMac20,x + MacPro7,1) BCM4377b (802.11ac): pci14e4,4488 (MacBookAir9,1) BCM4378 (802.11ax): Apple Silicon Mac models BCM4387 (802.11ax): Apple Silicon Mac models BCM4388 (802.11ax): Apple Silicon Mac models NB: macOS Big Sur is now officially unsupported. View full article
    1 point
  20. My Dell's specs: CPU: Intel Core i5 4210U RAM: 8GB DDR3 Graphics: Intel HD 4400 SSD: 512GB (macOS) HDD: 320GB (Kali Linux + Windows 11.5) Working: Graphics acceleration Brightness control WiFi. I'm using itlwm on a AC-7260 card by Intel + HELIPORT All USB 2.0 and 3.0 ports work Bluetooth, with IntelBluetoothFirmware/Injector Audio, incl. integrated microphone Sleep Ethernet HDMI output Touchpad Integrated camera Card reader To tell you the truth, I had only one problem when I tried to install the macOS Sonoma 14.0 RC1 update, it wouldn't start. According to the verbose -v it was a problem with audio kext, wifi and bluetooth.
    1 point
  21. I've removed your links to ebay or to DropBox that forced people to have an account. Please avoid such links in the future as per our published rules. I've posted your (basic) Clover stuff: ACPI folder + config file + kexts folder which I have cleaned of the useless stuff. Forget about the GeForce, it's Maxwell so never natively supported and required the nVidia Web Driver which only exists for OS X Yosemite to macOS High Sierra. No such drive since Mojave, no workaround, no solution. Just disable the dGPU to save on battery and run solely on the iGPU. You should have no issue getting graphics acceleration on HD5500, it's been supported for years. You just need to inject the correct properties and properly so... So, remove this from your config: and, instead, inject this: See here.
    1 point
  22. Ivy Bridge HD4000 has no support for VGA in OS X/macOS. It's been like that since Mountain Lion 10.8.2 so that shows you how far it goes. See here. nVidia GeForce GTX 950 is Maxwell so no support beyond macOS High Sierra and, even in macOS versions that could support the card, there was no native support and you needed the nVidia Web Driver. That died long ago when Mojave was introduced. "Fixing VRAM" does not mean much. If Big Sur only displayed "HD 4000 5MB", it meant you had no graphics acceleration. It's the only reason why you may have obtained video output on your VGA screen because you were running in unaccelerated, poor performing, VESA mode but Hackintosh was in limping mode and most probably very very slow with many graphics defects. Once you got graphics acceleration working, no VGA output, no. Since you now run Big Sur with HD4000 graphics, your only options for physical outputs are DVI, DP or HDMI and you can totally forget about VGA. If you really want VGA output, you only have 2 options: switch your GTX 950 card for a supported model: AMD or nVidia Kepler. See here. I get triple VGA/DVI/HDMI output out of my Asus GeForce GT730 (Kepler 2.0 GK208 chip) or my Yeston AMD Radeon RX560 (Polaris21/Baffin chip) on my old Core2Duo Dell Vostro 200 ST. if you have another (built-in) HDMI or a DVI or DP output port, use an adapter (has to be active (i.e. with a small chip) to convert digital signal to analog). That's fully supported.
    1 point
  23. It's based on Broadcom BCM4352, so, apply the necessary patch. It's never been natively supported. https://osxlatitude.com/forums/topic/11138-inventory-of-supportedunsupported-wireless-cards-2-sierra-ventura https://github.com/khronokernel/IO80211-Patches
    1 point
  24. @ZainAnjum - Your EFI is really messy. Try this and give us feedback: Dell 7490 Ventura Intel OC 0.9.4
    1 point
  25. 4K@24/30Hz over HDMI is perfectly normal, that's the limitation of those 8th gen Whiskey Lake CPUs. See those of the i5-8365U here. 4K@60Hz is only supported over DP output. On the 7400, that'll be out of the USB-c port with a DP adapter/cable (or TB if the port supports this).
    1 point
  26. Remove the OCLP patch, reboot and re-apply the minimum patches. Read the documentation before proceeding. At worst, re-install macOS from scratch.
    1 point
  27. The following serves to enable bluetooth in macOS Ventura 13.4+ for Broadcom & Intel Bluetooth 1. Navigate to the NVRAM > Add > 7C436110-AB2A-4BBB-A880-FE41995C9F82 section in your config.plist file and add the two child items: 2. Update BlueToolFixup from BrcmPatchRAM 2.6.7 3. Reboot and Reset NVRAM then boot again normally The fix is now working for both Intel and Broadcom Bluetooth, but the official acidanthera BrcmPatchRAM needs to be updated first. A test version is available at Github here: https://github.com/acidanthera/BrcmPatchRAM/pull/28 I attached the BrcmPatchRAM-2.6.7.zip to this post for reference. BrcmPatchRAM-2.6.7.zip Info: Source from gene-x from Hackintosh-Forum https://www.hackintosh-forum.de/forum/thread/58369-ventura-plötzlich-kein-bt-mehr/?postID=774484#post774484
    1 point
  28. @Baio77 it start, Brightness does not work, Trackpad very lag/slowly. Please see my attached IOReg below. @Hervé Yes, it is my screen's EDID. My Hack works well with/without it. IOReg20230530.zip
    1 point
  29. It works fine now with latest debug Aireportitlwm.kext Thank you I really appreciate it.
    1 point
  30. OP's setup is not optimised and partly contradictory. For instance: SSDT-UIAC patched table and USBPorts kext -> should only have one or the other SSDT-EC-USBX_Laptop and SSDT-USBX patches tables -> each with different power settings for USB ports SSDT-AC patched table -> really required? There are probably more patched tables than really necessary and a clean-up needed. SSDT-EC-USBX_Laptop table: Scope (\_SB) { Device (USBX) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x04) { "kUSBSleepPortCurrentLimit", 0x0BB8, "kUSBWakePortCurrentLimit", 0x0BB8 }) } [...] } SSDT-USBX table: Scope (\_SB) { Device (USBX) { Name (_ADR, Zero) // _ADR: Address Method (_DSM, 4, NotSerialized) // _DSM: Device-Specific Method { If (LEqual (Arg2, Zero)) { Return (Buffer (One) { 0x03 }) } Return (Package (0x08) { "kUSBSleepPowerSupply", 0x13EC, "kUSBSleepPortCurrentLimit", 0x0834, "kUSBWakePowerSupply", 0x13EC, "kUSBWakePortCurrentLimit", 0x0834 }) } } } Disabling sleep functionality in BIOS is a pretty poor workaround to a broken but most useful feature on a laptop...
    1 point
  31. I was equally surprised that it works with the SSD. I don't need the hibernation/sleep feature. I just didn't want the laptop to panic every time I closed it. I have enabled "Block Sleep" in the BIOS under Power Management. That is enough for me so far. Now it goes into lockscreen when I close the lid. Thanks anyway for the quick reply.
    1 point
  32. 1. Download the appropriate version from the Releases and extract the zip file. Let’s assume that you downloaded “ALCPlugFix-Swift-RELEASE-1.5.zip” to download folder, and extracted the zip file in the same place (by double-clicking). You would have a new folder “ALCPlugFix-Swift-RELEASE-1.5” created. Right-Mouse-Click on the new folder icon -> Services -> New Terminal at Folder. A new terminal window would be opened at the current folder path: /Users/YOURNAME/Downloads/ALCPlugFix-Swift-RELEASE-1.5 (You can type “pwd” to verify it) 2. Copy the edited sample.plist file (in this case: ALC295-DELL7400.plist) to somewhere safe. I placed it in “Monterey HD\users\shared”, where Monterey HD is the name for my macOS drive. You may have a different name. 3. At the terminal (opened in step 1), type: ./install.sh Follow the instruction. When it asked for .plist file, drag “ALC295-DELL7400.plist” icon to the terminal, from the location you stored in step 2 above (in my case, it is from “Monterey HD\users\shared\”). You may encounter message like "ALCPlugFix is from unknown source” (1st time install) , just ignore it. After install is completed, go to folder: /usr/local/bin (this is where ALCPlugFix is installed). Right-Mouse-Click on ALCPlugFix icon -> Open, then Open again to allow it to run. This would give it the permission to run. Add "alcverbs=1 alcid=77" to the boot args. Reboot.
    1 point
  33. Where are you with your current config ? Are you sure you have the best possible settings in place?
    1 point
  34. NB: This is a revival of the article I had initially published at InsanelyMac to answer recurring questions that had been raised in the Opencore thread that lives there. Posted October 2, 2021 The Dortania documentation refers to the DVMT pre-allocated memory or "stolen memory" when they mention "memory reserved for the iGPU". Years ago, @Firewolf described in details the relationship between stolen memory and DVMT pre-allocated memory on his blog: https://www.firewolf.science/2015/04/guide-intel-hd-graphics-5500-on-os-x-yosemite-10-10-3/ There's a more recent thread from him here: https://www.insanelymac.com/forum/topic/345377-surface-pro-patch-the-framebuffer-properly-to-get-rid-of-the-dvmt-assertion-patch/ It can be difficult to understand and differentiate DVMT pre-allocated memory, stolen memory, framebuffer memory, cursor memory, framebuffer size, cursor bytes, etc. And all of these have got nothing to do with VRAM of course... Some of us are familiar with the information provided by @Pike R Alpha many moons ago, the WhateverGreen User Manual or the Hackintool app though none of those clearly define what the various memory instances are. Several years ago, @Rehabman also attempted to explain this and his writings somehow collided with most people's comprehension of things. For instance, when @Pike, WhateverGreen or Hackintool refer to stolenmem and fbmem, @Rehabman spoke of framebuffer memory size and cursor bytes. In the case of the Haswell Azul framebuffer layouts, @Rehabman also spoke of the DVMT pre-alloc requirements when the others speak of stolenmem. Inevitably, this can lead to confusion... Definitions: See wikipedia and Google searches. VRAM = Video RAM. Common definition is that it stores the pixels and other graphics data rendered on a computer screen. DVMT = Dynamic Video Memory Technology. A technology used by Intel to dynamically allocate system memory to use as video memory to handle graphics. DVMT pre-allocated memory is the minimum amount, in multiples of 32MB, that will be allocated to the iGPU for handling graphics. By far and large, manufacturers set this to 32MB by default in BIOS (or certainly used to). Framebuffer = a memory buffer held in RAM and containing a bitmap of a video frame, i.e. all the data related to the pixels of an image to be displayed on screen (eg: colours, resolution, etc.). Stolen memory = basically, this is the same as the DVMT pre-allocated memory. As far as Apple's framebuffer drivers/kexts are concerned: framebuffer size (aka stolenmem for WhateverGreen*) = the size, in bytes, of a framebuffer layout (it may change according to image characteristics), as defined in the driver/kext. cursor bytes (aka fbmem for WhateverGreen*) = the size, in bytes, of a framebuffer layout's overlay used for handling mouse cursor (without modifying the framebuffer's data), as defined in the driver/kext. framebuffer VRAM (aka unifiedmem for WhateverGreen) = the max. amount, in bytes, of VRAM allocated by a framebuffer layout, as defined in the driver/kext (since Haswell and Yosemite, this usually is 1536MB). * As stated above, I believe that Whatevergreen only got it right for Haswell Azul framebuffer layouts with which stolenmem, fbmem and cursormem match their target. Thereafter, I'm of the opinion that WhateverGreen used incorrect names where stolenmem means the actual framebuffer size and fbmem means the actual cursor bytes (size), as stated by @Rehabman. Mac OS X/OS X/macOS graphics framebuffers: Let's start by looking at a few examples as illustrated in the WhateverGreen User Manual. 1) Haswell Azul mobile framebuffer 0x0a260006 (used for HD4200/HD4400/HD4600 iGPUs on laptops): ID: 0A260006, STOLEN: 32 MB, FBMEM: 19 MB, VRAM: 1536 MB, Flags: 0x0000000F TOTAL STOLEN: 52 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 116 MB, MAX OVERALL: 117 MB (123219968 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000030 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP [2] busId: 0x04, pipe: 9, type: 0x00000400, flags: 0x00000087 - ConnectorDP 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 If we look inside the binary code of the Haswell Azul framebuffer kext, we'll find: 0600260A 01030303 00000002 00003001 00006000 00000060 D90A0000 D90A0000 00000000 00000000 00000800 02000000 30000000 01050900 00040000 87000000 02040900 00040000 87000000 FF000000 01000000 40000000 0F000000 01010000 04000000 00000000 0E000000 00000000 which translates to: 0600260A -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00000002 -> 32MB stolen mem (framebuffer-stolenmem) // Rehabman's DVMT-prealloc requirement 00003001 -> 19MB FB mem (framebuffer-fbmem) // Rehabman's framebuffer size 00006000 -> 6MB Cursor mem (framebuffer-cursormem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) D90A0000 -> Backlight freq 2777MHz D90A0000 -> Max. backlight freq 2777MHz 00000000 00000000 00000800 02000000 30000000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 30020000 01050900 00040000 87000000 -> port #2/FB@1: index 01, busid 05, pipe 0900, type 00040000=DP (framebuffer-con1-type), flags 87000000 02040900 00040000 87000000 -> port #3/FB@2: index 02, busid 04, pipe 0900, type 00040000=DP (framebuffer-con2-type), flags 87000000 FF000000 01000000 40000000 0F000000 01010000 04000000 00000000 0E000000 00000000 2) Broadwell BDW mobile framebuffer 0x1626006 (used for HD5300/HD5500/HD5600 iGPUs on laptops): ID: 16260006, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x00000B0B TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Camellia: CamelliaDisabled (0), Freq: 2777 Hz, FreqMax: 2777 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000230 - ConnectorLVDS [1] busId: 0x05, pipe: 11, type: 0x00000400, flags: 0x00000507 - ConnectorDP [2] busId: 0x04, pipe: 11, type: 0x00000400, flags: 0x00000507 - ConnectorDP 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 If we look inside the binary code of the Broadwell BDW framebuffer kext, we'll find: 06002616 01030303 00002002 00005001 00000060 D90A0000 D90A0000 00000000 00000000 00000000 00000800 02000000 30020000 01050B00 00040000 07050000 02040B00 00040000 07050000 FF000000 01000000 40000000 0B0B0000 01010500 00000000 05000000 00000000 04000000 00000000 00000000 00000000 00000000 00000000 C8000000 which translates to: 06002616 -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00002002 -> 34MB stolen mem (framebuffer-stolenmem) // Rehabman's framebuffer size 00005001 -> 21MB FB mem (framebuffer-fbmem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) D90A0000 -> Backlight freq 2777MHz D90A0000 -> Max. backlight freq 2777MHz 00000000 00000000 00000000 00000800 02000000 30020000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 30020000 01050B00 00040000 07050000 -> port #2/FB@1: index 01, busid 05, pipe 0B00, type 00040000=DP (framebuffer-con1-type), flags 07050000 02040B00 00040000 07050000 -> port #3/FB@2: index 02, busid 04, pipe 0B00, type 00040000=DP (framebuffer-con2-type), flags 07050000 FF000000 01000000 40000000 0B0B0000 01010500 00000000 05000000 00000000 04000000 00000000 00000000 00000000 00000000 00000000 C8000000 3) Skylake SKL mobile framebuffer 0x19160000 (used for HD520/HD530/HD540 iGPU on laptops): ID: 19160000, STOLEN: 34 MB, FBMEM: 21 MB, VRAM: 1536 MB, Flags: 0x0000090F TOTAL STOLEN: 56 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 124 MB, MAX OVERALL: 125 MB (131608576 bytes) Model name: Intel HD Graphics SKL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 1, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [0] busId: 0x00, pipe: 8, type: 0x00000002, flags: 0x00000098 - ConnectorLVDS [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 02000000 98000000 01050900 00040000 87010000 02040A00 00040000 87010000 We can't look at the binary code of the Skylake SKL framebuffer because Apple changed the way things are coded inside but it basically translates as follows: 00001619 -> layout id (AAPL,ig-platform-id) 01 -> mobile type (framebuffer-mobile) 03 -> 3 x pipes (framebuffer-pipecount) 03 -> 3 x ports (framebuffer-portcount) 03 -> 3 x memories (framebuffer-memorycount) 00002002 -> 34MB stolen mem (framebuffer-stolenmem) // Rehabman's framebuffer size 00005001 -> 21MB FB mem (framebuffer-fbmem) // Rehabman's cursor bytes 00000060 -> 1536MB VRAM (framebuffer-unifiedmem) 6C050000 -> Backlight freq 1388MHz 6C050000 -> Max. backlight freq 1388MHz 00000800 02000000 98000000 -> port #1/FB@0: index 00, busid 00, pipe 0800, type 02000000=LVDS/eDP (framebuffer-con0-type), flags 98000000 01050900 00040000 87010000 -> port #2/FB@1: index 01, busid 05, pipe 0900, type 00040000=DP (framebuffer-con1-type), flags 87010000 02040a00 00040000 87010000 -> port #3/FB@2: index 02, busid 04, pipe 0a00, type 00040000=DP (framebuffer-con2-type), flags 87010000 With the exception of the Haswell Azul framebuffer, we can see that Broadwell BDW and Skylake SKL framebuffers define framebuffer size (WEG's stolenmem) and cursor bytes (WEG's fbmem) characteristics and no DVMT pre-allocated memory (i.e. proper stolen memory). This extends to Kaby Lake KBL framebuffers and later. In my opinion, it's fair to say that @Rehabman's description and wording are the most appropriate/best ones when the WEG view of things got somehow misled by following through on the Haswell framebuffer decoding. To me, there was some mixup, leading to confusion and the said confusion has remained ever since... Confusion... why? Because of several things: 1) the observation that the Haswell Azul framebuffers used on Hacks (0x0D220003 for desktops and 0x0A260006 for laptops) defined: a DVMT pre-allocated memory (= Stolen memory) size of 32MB a framebuffer size of 19MB a cursor bytes of 0MB (desktops) and 6MB (laptops; required to be increased to 9MB to fix a minor graphics glitch on some systems) 2) the observation that the Broadwell BDW framebuffers used on Hacks (0x16220007 for desktops and 0x16160006 for laptops) defined: no DVMT pre-allocated memory requirement at all framebuffer sizes of 38MB and 34MB respectively cursor bytes of 38MB and 21MB respectively 3) the observation that the sum of framebuffer size + cursor bytes must be lower than the size of the DVMT pre-allocated memory, failing which a KP occurs at graphics initialisation during startup/boot. 4) In the case of the Haswell Azul framebuffers: DVMT pre-allocated memory requirement is set at 32MB framebuffer size + cursor bytes = 19+0 | 19+6 (or 19+9) = 19MB | 25MB (or 28MB) which is lower than DVMT pre-allocated memory 32MB -> All is Ok by default. 5) In the case of the Broadwell BDW framebuffers: framebuffer size + cursor bytes for desktops = 38+38 = 76MB which is greater than the usual/default 32MB DVMT pre-allocated memory of most desktops, unless adjusted in BIOS framebuffer size + cursor bytes for laptops = 34+21 = 55MB which is greater than the usual/default 32MB DVMT pre-allocated memory of most laptops, unless adjusted in BIOS -> Not Ok by default, Kernel Panic (KP) encountered. 6) And the story is the same with subsequent Skylake, Kaby Lake, etc. framebuffers. Solution: 2 x solutions were engineered to address the issue of KP at graphics initialisation. increase the DVMT pre-allocated memory set in BIOS. Could be complicated and tricky for PCs that do not offer this in BIOS Setup but made easy with Grub Shell if DVMT pre-allocated memory can be identified in BIOS. This method is usually required to gain 4K output. patch the Broadwell, Skylake, Kaby Lake, etc. framebuffer layouts to reduce framebuffer size and cursor bytes so that the sum of them totals less than the usual default DVMT pre-allocated memory of 32MB. This solution does not usually support 4K output. Although some people do opt for the 1st solution, most people just adopt the 2nd one. How were the framebuffer patches derived? If we look at the framebuffer patches that are commonly and generally used, we can observe that they set: WEG's framebuffer-stolenmem property , i.e. framebuffer size to 0x01300000 = 19MB (DATA type set to 00003001) WEG's framebuffer-fbmem property, i.e. cursor bytes to 0x00900000 = 9MB (DATA type set to 00009000) i.e. the values typically used on laptops with Haswell iGPUs, this simply because 19+9=28MB which is < 32MB. This is where it all appears to come from. Is this correct? By far and large, it is. But the need to apply such framebuffer patches depends entirely on the host PC's default DVMT pre-allocated memory. On desktop and laptop PCs where DVMT pre-allocated memory can be adjusted in BIOS setup, the patches are unnecessary as long as the DVMT value that is set exceeds the total of the framebuffer size + cursor bytes of the selected/target graphics framebuffer. Typically, a value of 64MB or 96MB takes care of things perfectly, including 4K. Of course, those PCs manufactured with default DVMT pre-allocated memory set to 64MB or more are unlikely to encounter any issue at all. The framebuffer patches are also unnecessary if the default DVMT pre-allocated memory is increased either though BIOS binmod (difficult and risky) or through Grub shell mod (easy and quickly reversible). This is well illustrated on @Firewolf's blog, linked above (there are other places too such as @Jake Lo's FAQ item here). To give an example, on some Dell laptops (eg. Broadwell Latitude E7x50 or Skylake Latitude E7x70), DVMT pre-allocated memory can be increased by booting a Grub shell and entering the following command: setup_var 0x432 0x3 This sets DVMT pre-allocated memory parameter located at offset 0x432 to 96MB (0x1 for 32MB, 0x2 for 64MB, 0x3 for 96MB, etc.), the default setting for the laptop in this example being 32MB. This setting will remain valid/in place until BIOS is reset to default settings. It's required to obtain 4K output out of DP/HDMI. Of course, different computers will have different locations/offsets for DVMT pre-allocated memory. What should I do then? As stated above, the framebuffer patches apply to most if not all cases. But not for 4K output. Those who feel adventurous or who are computing-literate may opt for the BIOS adjustment alternative. In all cases, the 1st thing to do is to look at the default framebuffer size and cursor bytes settings of the targeted graphics framebuffer, then decide if the sum of them both fits or not in 32MB or any other value set in BIOS for DVMT pre-allocated memory. Can I use different values? Absolutely! As long as the golden rule is respected: framebuffer size + cursor bytes < DVMT pre-alloc mem or, in WEG's conventions, stolenmem + fbmem < DVMT pre-alloc mem. To give a practical example, I experimented on my Skylake/HD520 Dell Latitude E7270 Hackintosh laptop: default DVMT pre-allocated memory value set in BIOS: 32MB target SKL framebuffer layout: 0x19160000 default framebuffer size: 34MB default cursor bytes: 21MB sum of framebuffer size + cursor bytes: 55MB (i.e. > 32MB) Booting with default DVMT pre-alloc mem + no framebuffer patches -> KP/freeze Booting with default DVMT pre-alloc mem + framebuffer size 20MB + cursor bytes 12MB -> KP Booting with default DVMT pre-alloc mem + framebuffer size 19MB + cursor bytes 9MB -> Ok, full graphics acceleration, no 4K output Booting with default DVMT pre-alloc mem + framebuffer size 20MB + cursor bytes 10MB -> Ok, full graphics acceleration, no 4K output Booting with DVMT pre-alloc mem set to 64MB (Grub shell) + no framebuffer patches -> Ok, full graphics acceleration + 4K output Booting with DVMT pre-alloc mem set to 96MB (Grub shell) + no framebuffer patches -> Ok, full graphics acceleration + 4K output
    1 point
  35. @Hervé I've finally have managed to get full GA working with 0x05001C59 and external monitor using type-c to HDMI port. However, Built-in display is blank - I am still able to change brightness with fn keys and sys info show the builtin display is detecting resolution at 28" (1600x1200). Still not having any luck with the connector type... 15" Surface Book 2 15” PixelSense™ Display Screen: 15” PixelSense™ Display Resolution: 3240 x 2160, (260 PPI) 10 point multi-touch G5 Aspect ratio: 3:2 Contrast ratio: 1600:1 SB15 04.ioregopencore-2022-11-01-021006.txt.zip
    1 point
  36. OPENCORE - Ventura Supports Ventura Follow BIOS Configuration above Working: full graphics acceleration on Intel HD520 iGPU, including brightness control (F5 and F6) multi-display with DisplayPort (Video & Audio) audio, microphone input and headset output (F8 and F9) Mute button IS working by Human7900 GigEthernet LAN connection wireless and bluetooth with any compatible card (a DW1560 in my case, no Whitelisting) left and right USB ports including USB Type-C integrated webcam CPU power management sleep (Lid, Energy Saver settings, Apple menu, PWR button) & wake (Lid, PWR button) battery management keyboard and touchpad keyboard backlight (Fn + F3) touchpad with gestures, mouse buttons (can be disable with PrtScr key) RTS522a microSD card reader Not working: Trackpoint and mouse buttons Finger Print reader Wifi button Installation: Download macOS Ventura app Format a 16GB USB drive (GUID / Extended (Journaled)) Create USB Installer with createinstallmedia command Download attached folder and rename as EFI Mount EFI partition and add EFI folder Configure BIOS setting according to guide Boot with USB installer Complete installation Post Installation: Mount EFI partition of newly installed drive and copy EFI folder over Update / Change in Config.plist under PlatformID->Generic (use genSMBIOS or Hackintool.app) MLB, ROM, SystemSerialNumber and SystemUUID Resources: https://dortania.github.io/OpenCore-Install-Guide/ https://github.com/VoodooSMBus/VoodooRMI https://github.com/OpenIntelWireless/itlwm https://github.com/cholonam/Sinetek-rtsx https://github.com/0xFireWolf/RealtekCardReader/releases Updated to OC 0.9.5 Note: Config is set for Broadcom DW1830 If you have Intel, rename Config-IntelWifi to Config.plist Multiboot from OC picker is also working! HP840G3_OC_0.9.5.zip HP840G3_OC_0.8.5_Ventura.zip
    1 point
  37. Bananz0 test this EFI in USB if start ioreg https://drive.google.com/drive/folders/1Ub16WgZeBOPzYL1fIfJjGeZUV_qUUrUz?usp=sharing
    1 point
  38. Hi after reading this Forum and others, I am happy with my Dell 7040 this is my EFI Folder for my Optiplex 7040 with Monterey 12.1 Beta 4, OC 0.7.6 i5 6500, IntelHD 530, 1 Monitor to DP and 1 on HDMI Optiplex_7040.zip
    1 point
  39. Ok! I have come to the end practically everything works except the WIFI card not compatible to be replaced. Thanks to Hervè for the precious help. I leave attached my EFI which could be useful to someone. M4400-highsierra.zip
    1 point
  40. Dell Latitude E5550: Intel Broadwell i3-5010U @2.10GHz Intel HD5500 graphics 8GB DDR3L RAM Intel I218V LAN Intel AC 7265 Wireless OpenCore 0.7.3 and Clover r5138 with up-to-date kexts at time of writing. Updated: Dell Latitude E5550.zip Working: Full graphics acceleration HDMI output Wifi and Bluetooth LAN Audio (speakers, headphones & HDMI) Sleep with lid off and  > Sleep Brightness control Multimedia button Keyboard and touchpad (ALPS) SD card reader USB2.0 & USB3.0 ports (USB remapping required macOS installation because my laptop doesn't have camera so I've not remapped yet) Battery Indicator and charger Not working: VGA output (unsupported)
    1 point
  41. credit to : @r33int at github thanks you I just add nv_disable=1 at the line 771 at config.plist I tested it on Catalina 10.15.4 and Big Sur [@screen shoot] but I dont check another stuff working up yet wifi used intwl kext & heliport 1.0.0 ,hackintoll,but please master@Jake Lo please fixed the battery its like drainy the [EFI\APPLE,BOOT,OC] file both working for installed and booting up Catalina & big Sur by create installmedia both zip file [EFI\APPLE,BOOT,OC] OC.zip Archive.zip
    1 point
  42. Following BIOS update to v1.16.0, I revisited the patched DSDT since it was (finally) also causing a reset to me. I dumped all tables from BIOS and came to realise I had applied the brightness keys patch to a Clover pre-patched DSDT! I therefore re-applied the patch to the raw DSDT. My 7490 now boots Catalina without reset and brightness keys are fully operational. I've also updated the patch code above to return those Clover pre-patched lines to full vanilla code (XOSI returned to _OSI and XSID returned to OSID). Patched_DSDT_Lat7490_BIOS-1.16.0.aml.zip I invite Latitude 7490 users to test this revised patched DSDT and feedback to me by PM so that I can update the bootpacks accordingly. In case of issues (system reset), select BIOS.aml DSDT table in Options->ACPI patching->Dsdt name at Clover main boot menu to load the raw DSDT at macOS startup.
    1 point
  43. Dell Latitude/Inspiron/Precision/Vostro/XPS - Clover Guide Up to Sierra Only High Sierra Guide below Mojave Guide Catalina Guide Warning: Follow guide at your own risk, I hold no responsibility if you brick your system or destroy all data during the process. If you're creating the installer from a real Mac, make sure you don't accidentally select the real Mac drive when installing Clover loader. It may cause your Mac to not boot again. You've been warned! BIOS: Set to Default, apply, then set SATA Operations to AHCI, set Boot List Option to UEFI Disable Secure Boot, Disable Wake on LAN/WWAN/WLAN, Disable TPM (optional) Enable Legacy Options ROMs for Broadwell system and below Requirements: 1. A downloaded OS X El Capitan / Sierra Application from the Mac App Store 2. USB flash drive (16GB minimum) 3. Clover Configurator (Included in Hack_Tools attached below - might not be the latest) 4. Clover Loader 5. ShowHiddenFiles.app (Included in Hack_Tools attached below) 6. A system running OS X to create the USB Installer 7. A supported Wireless card, Intel wireless are NOT supported Overview 1. Prepare a Bootable USB Drive (8GB minimum) 2. Install OS X El Capitan / Sierra 3. Post Installation 1: Prepare Bootable USB Drive This step extracts the OS X Installer contents, then installs Clover bootloader to the USB stick. 1. Insert the USB drive on a running OS X system 2. Open /Applications/Utilities/Disk Utility 3. Highlight the USB drive in left column 4. Click on the Partition tab 5. Click Current and choose 1 Partition 6. Click Options... 7. Choose GUID Partition Table 8. Under Name: type USB (You can rename it later) 9. Under Format: choose Mac OS Extended (Journaled) 10. Click Apply then Partition 11. Go to Applications, right click on Install OS X El Capitan / Sierra =>Show Package Contents=>Contents=> SharedSupport 12. Mount InstallESD.dmg 13. Launch ShowHiddenFiles and select Show Special Files ( app attached at the end of guide) 14. Mount BaseSystem.dmg (hidden) from OS X Install ESD 15. Use Disk Utility to restore OS X Base System to USB (see image below) 16. After restore is complete, USB is now renamed to OS X Base System. Go ahead and rename it to Install OS X El Capitan 17. Go to Install OS X El Capitan/ Sierra=>System=>Installation and delete the alias Packages 18. Copy Packages from root of OS X Install ESD to Install OS X El Capitan/Sierra=>System=>Installation 19. Copy BaseSystem.dmg and BaseSystem.chunklist (hidden files) from OS X Install ESD to root of Install OS X El Capitan/Sierra 20. Launch ShowHiddenFiles and select Hide Special Files 21. Download Clover 22. Launch Clover package installer 23. Hit Continue, Continue, Change Install Location... 25. Choose Install OS X El Capitan/Sierra 26. Hit Continue, then hit Customize. Select these items: Install for UEFI booting only Install Clover in the ESP UEFI Drivers\Recommended Drivers ApfsDriverLoader AptioMemoryFix AudioDxe DataHubDxe FSInject HFSPlus SMCHelper (leave off if you have VirtualSMC.kext in bootpack) Additional drivers PartitionDxe Themes (Optional) Note: For non UEFI BIOS, see Note1 of post #2 27. Click Install 28. After installation of Clover, the hidden EFI Partition will appear on the Desktop 29. Download the Generic EFI + Bootpack for your model in post #2, replace the contents to the root of the EFI partition, replacing the existing folders ( Boot and Clover folders - not merge) Note: Make sure to check the Update section in Post #4 for updated file if any 30. You are now ready to install OS X El Capitan/Sierra Note: Make a directory in the USB Installer and copy Hack_Tools, Clover package and EFI folder to it for easy access in Step 3 2: Install OS X El Capitan/Sierra 1. Turn on the computer with the USB Installer connected 2. Press F2 to configure the BIOS Sata Operaton -> AHCI Secure Boot -> Disabled Boot List Option -> UEFI. Enable Legacy Option ROMs (Disabled for Skylake and above) Apply and Exit 3. Hit F12 during boot, choose under UEFI Boot: 4. When Clover boot screen appears, choose Install OS X El Capitan/Sierra 5. The system will then boot into the OS X Installer 6. Choose your language and hit -> to continue 7. For a new installation of OS X, you MUST erase and format the destination drive according to the following steps before continuing. *If you are upgrading from Lion, Mountain Lion, Mavericks, or Yosemite and you want to keep your files and apps, skip steps a-i. a. From the menu bar, click Utilities -> Choose Disk Utility b. Highlight your target hard drive for the El Capitan installation in left column. c. Click Erase tab d. Under Scheme: GUID Partition Map e. Under Name: type Macintosh SSD (You can rename it later) f. Under Format: choose Mac OS Extended (Journaled) g. Click Erase h. Click on Partition Tab to add more partition if you prefer i. Close Disk Utility 8. Click Continue, Continue, Agree 9. Select Macintosh SSD, or name of your existing drive, where you want to install El Capitan and click Continue 10. Upon completion, system will restart 11. Press the F12 to choose boot device 12. Choose under UEFI Boot: 13. When Clover boot screen appears, choose Macintosh SSD or name of your existing drive The system will boot into the new drive, and complete the installation: 14. Launch the terminal and enter the following command diskutil list Note: If you see the following, then follow steps in Post #3 Under Core Storage before proceeding /dev/disk1 (internal, virtual): 3: Post-Installation Install Clover loader to Macintosh SSD 1. Launch Clover package installer 2. Hit Continue, Continue, Change Install Location... 3. Choose Macintosh SSD 4. Hit Continue, then hit Customize. Select these items: Install for UEFI booting only Install Clover in the ESP UEFI Drivers\Recommended Drivers ApfsDriverLoader AptioMemoryFix AudioDxe DataHubDxe FSInject HFSPlus SMCHelper (leave off if you have VirtualSMC.kext in bootpack) Additional drivers PartitionDxe Themes (Optional) Install Clover Preference Pane (Optional) Note: For non UEFI BIOS, see Note1 of post #2 5. Launch ESP Mounter Pro, select the disk you have OS X installed on (ie. disk0s1) - app in Hack_Tools 6. Copy the EFI folder from the USB installer to EFI partition of Macintosh SSD (replace not merge) 7. Copy kexts from /EFI/Clover/Kexts/Other/CopytoLE to /Library/Extensions of Macintosh SSD Note: Ignore warning/error messages and click OK, then run commands below. 8. Repair permission and rebuild cache. Run command from terminal (or run permission.sh found in Hack_Tools) sudo chmod -Rf 755 /L*/E* sudo chown -Rf 0:0 /L*/E* sudo touch -f /L*/E* sudo chmod -Rf 755 /S*/L*/E* sudo chown -Rf 0:0 /S*/L*/E* sudo touch -f /S*/L*/E* sudo kextcache -Boot -U / 9. Go to System Preferences Enable Clicking for Trackpad Allow apps downloaded from: Anywhere for Security & Privacy (optional) Note: For Sierra and up, run this in terminal instead: sudo spctl --master-disable 10. Generate own SMBios and SSDT.aml (For Haswell and up, you can enable PluginType in Config instead) Launch /EFI/Clover/Config.plist with Clover Configurator (Included in Hack_Tools attached below) On the left, click on SMBIOS Click on the Up/Down arrow on the right Select the model most suited for your system or use same model included in bootpack, generate a new serial Close Clover Config and save the file. Execute ssdtPRGen.sh from terminal (Included in Hack_Tools attached below) Place generated SSDT.aml in /EFI/Clover/ACPI/Patched Please use beta version of ssdPRGen.sh to generate SSDT.aml for newer system 11. Make sure to disable hibernation as it's a prerequisite to get sleep & wake to work properly on a Hackintosh: sudo pmset hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo pmset hibernatefile /dev/null 12. Congratulations! You are done! Hack_Tools.zip When posting for HELP, please include full system specs and attach debug files. If you're not able to start the installer, then attach the Clover folder and include screenshot(s) of the error / KP by booting with verbose + debug 0x100 mode Credits: All apps, kexts and DSDT patches used in creating this guide go to the developers that created them. I take no credit other than putting this guide and bootpacks together.
    1 point
  44. Hello everyone Thank you very much for your wonderful and useful forum I want share with you after long search and fixes my final EFI Partition for Dell Precision WS M6800 & M4800 and will work 99 % on any similar Model All files , Kexts , ACPI , Guide are all included in zip file linked below This my final EFI with alots of fixes and tweaks works for both High Sierra and Mojave only you will need Nvidia web drivers and Cuda to get fully working machine for graphic designing , video editing and 3D ... - Fully working everything , audio , Bluetooth, Brightness slider , card reader , mSata , ethernet , Wifi , Camera ,all USB 3 Ports and many more you will explore it yourself ...... - Bios Reset issue fixed - Optimus Graphic enabled - Use Intel HD only or Intel HD + Nvidia (if you want Nvidia only then disable Optimus in bios) - External Monitor use Nvidia - No black Screen when external monitor is connected - What is missing and doesn't work !!!! You will tell me - all fixes files and instructions are included ************************* UPDATED 30 JUN 2019 ************************ - Alots of Tweaks has been added to ACPI , config.plist and IntelFrameBuffer - USB 3 all ports fixed natively - KEXTS has been updated -Clover bootloader has been updated - Fans has been adapted by ACPIPoller.kexts and SSDT for more cooling and less noise - CPU and RAM Tweaks - No more Kernel Panic with release or security update - Clean DSDT , SSDT , plist - Alots of work, search and tests to get this result with this Laptop - Ready for Catalina ( wait for the official release and Hacks developers final fixes to be ready ) All Updated Files are here ( 50 MB) ; https://drive.google.com/file/d/107_34arPRYoiObJUCH9l7TG_tZsK2FOD/view Thank You ********************* 30 Nov 2018 Fix OLD .zip If you need any help or have any questions or issue please let me know in the Support section of the forum and I will reply as soon as possible Cheers
    1 point
  45. In case the above Google link becomes unavailable... Dell_Precision-M6800_Jul2019.zip
    1 point
  46. 30-06-2019 Update Attached Files in First Post ( Google Drive Link 50 MB ) This instructions is for Dell Precision m6800 (and similar Dell Precision Models - Experimental) Before you start Please note that : I am using Dell Precision m6800 with these SPEC : Intel I7 4900MQ 2.8 Mhz - Intel HD Haswell 4600 32 GB RAM Nvidia Quadro K3100M 4GB Samsung EVO 250 GB Dell DW 1560 WiFi and BT Adapter BIOS A25 ( Latest 30 Oct 2018 ) This Process has been successfully tested with High Sierra and Mojave 10.14.5 Both IGPU and DGPU are Working Together Correctly like a Desktop No Bios reset issue when reboot , Works with Dual Boot ( Win + OSX ) ******* Step By Step ******** 1- Reset BIOS to its default and Update it to A25 2- Modify BIOS setting ( Press F12 to see Options ) * Advanced Boot Options = Enable Legacy * Integrated NIC = Enable * Parallel Ports = AT * Serial Ports = Disabled ( If you are using Dock station then Enable it - Expermental ) * Sata Operation = AHCI * Drivers = Check all * Switchable Graphics = Enable Switchable Graphics * Secure Boot = Disabled * Virtualization = Disable 3- Create your OSX Installation USB ( Search How , its not my Topic ) * Then I recommend to install Clover bootloader to create EFI Folder on your USB (UEFI Method) 4- Once you create OSX Installation USB ; mount USB EFI PARTITION and DELETE EFI Folder 5- Decompress my attached files 6- On my attched files ; Find ( install Folder ) Copy EFI Folder and Paste it in your USB EFI PARTITION ( instead of deleted one in step 4) 7- Now you are ready to Install OSX for Dell Precision M6800 * Power On your PC * Press F12 to see Options * Select BOOT from ( your USB ) * Start Installation Process ( it will reboot several time during installation so press F12 each time to boot from your USB ) - search Youtube videos to see the installation process 8- Once installation done and you reach your OSX desktop *Copy my attached files to your Desktop and Eject USB * Mount your OSX Drive EFI PARTITION and delete ( EFI Folder if existed ) * On my attached files Find ( Boot Disk EFI ); copy EFI Folder and Paste it in your Drive EFI PARTITION instead of deleted one "same as step 6" 9- Now the last step ( very Important ) - on my attached files Find (L/E Folder) - use any method or tool to install ALL KEXTS to Library/Extensions - Rebuild kextcache and repair permissions - I recommend using Hackintool by @headkaze to install kexts and rebuild kextcache 10- Reboot your PC and check everything is working correctly ( Audio , Bluetooth , WiFi , Internet , USB 3 , Trim ... ) IF you are using Mojave ; No Cuda drivers available till now but Nvidia GPU works with 4k External Monitor via DP Fully Accelerated Qi-Ci , also you can Disable Bios graphics Optimus to disable Intel HD GPU and use only Nvidia GPU - The same thing with High Sierra except that Nvidia Web Drivers are available and Cuda are ready - I use this PC all time with 4k external monitor while laptop led screen is closen using external mouse and Keyboard for Graphic design and video editing; H264 with hardware acceleration is working but no H265 hardware acceleration I think due to Haswell limitation - also I've found useful app to disable CPU turbo boost . I use it sometimes to reduce CPU temp ( search google ) Note : in case you have booting troubles ; Try to change SMBIOS in config.plist to diffrent model as MacbookPro 10.1, MacBookPro 11.2, MacBookPro 13.1 also you can try iMac 14.2 ( works nicely with me I don't know why ) Little Tweak for CPU and RAM : go to CPU section in config.plist using clover configurator and add values to this sections according to your CPU frequency (Be careful) For example: - Add 2800 to "frequency mhz" if your CPU base is 2.8 mhz ( 2700 if 2.7 and 2100 if 2.1 , ...) - Add 99790 to "Bus speed khz" - Add 47 to "TDP" ( Look intel CPU spec page for your model to know more info about your CPU and TDP value for your CPU ) For example in my case https://ark.intel.com/content/www/us/en/ark/products/75131/intel-core-i7-4900mq-processor-8m-cache-up-to-3-80-ghz.html GPU Power Management: Delete my dAGPM.kext from clover/Kexts/Others and make your own Kext according to your SMBios ID to get the correct power management There is a tool developed by @pavo to generate your Kext and another method by @toleda search forum and google to know more about that Disable Nvidia GPU: If you want to disable dGPU and use only Intel HD 4600 drop SSDT-4600.aml to clover/ACPI/Patched . But in this case no external monitor will be working only internal Disable Intel HD GPU : If you like to use only Nvidia GPU so disable Optimus Graphics in Bios and you can use internal and external monitor USB 3 Ports Fixes : Please Modify The Info.Plist inside USBPorts.Kext to Match Your SMBIOS Find and change this text (iMac 14.2) change to (Your Model) every where in plist For Example (iMac 14.2) To (MacBookPro 11.2) Now All Your USB 3 Ports And Camera Will Work Correctly Have Fun Franckenstien 30 Jun 2019 SSDT-4600.aml.zip
    1 point
  47. Note: This bootpack should also be compatible with any supported 4th Gen Intel CPU on H81 Intel Chipset Motherboard. Hi all, Just built my first budget desktop hackintosh and pleased to share the bootpack. Specification Gigabyte H81M DS2 4th Gen 3.5 GHz i3-4330 8 GB DDR3 1600 MHz Memory AMD Radeon RX560 (Supported natively by Mac OS Ventura) Intel Graphics HD 4600 (Working natively up to Mac OS Monterey but unusable. See notes below. Not tested yet on Mac OS Ventura) AMD Radeon 7750 1GB (Supported natively up to Mac OS Monterey) (See other post here : https://osxlatitude.com/forums/topic/11048-amd-radeon-hd-7750-supported-by-mac-os-mojave-catalina/) OpenCore Bootpack The OpenCore bootpack can be downloaded from the following link:- macOS Ventura 13.0 (OpenCore 0.8.5):- OpenCore-13.0-0.8.5.zip Looks like OpenCore can still boot Ventura using Mac Mini 18 smbios. However, supported GPU need to be used e.g. AMD RX 560 in my current case. Updated all kexts to latest versions macOS Monterey 12.6 (OpenCore 0.8.4):- OpenCore-12.6-0.8.4.zip Updated all kexts to latest versions macOS Monterey 12.4 (OpenCore 0.8.1):- OpenCore-12.4-0.8.1.zip Updated all kexts to latest versions macOS Monterey 12.3.1 (OpenCore 0.8.0):- OpenCore-12.3.1-0.8.0.zip Updated all kexts to latest versions macOS Monterey 12.2.1 (OpenCore 0.7.8):- OpenCore-12.2.1-0.7.8.zip Updated all kexts to latest versions macOS Monterey 12.1 (OpenCore 0.7.6):- OpenCore-12.1-0.7.6.zip Updated all kexts to latest versions macOS Monterey 12.0.1 (OpenCore 0.7.4):- OpenCore-12.0.1-0.7.4.zip macOS Monterey 12 Beta 9(OpenCore 0.7.4):- OpenCore-11.6-0.7.4.zip Updated OpenCore and all kexts to latest versions Changed SMBIOS to iMac Late 2015 for installer to work macOS Monterey 12 Beta (21A5248p) (OpenCore 0.7.0):- OpenCore-12-Beta-0.7.0.zip Updated all kexts to latest versions Changed SMBIOS to Mac Mini Late 2014 as Intel 4th Gen Haswell iMacs no longer supported macOS Big Sur 11.6 (OpenCore 0.7.4):- OpenCore-11.6-0.7.4.zip Updated opencore & all kexts to latest versions macOS Big Sur 11.3 & 11.3.1 (OpenCore 0.6.9):- OpenCore-11.3-0.6.9.zip So far everything should work Updated all kexts to latest versions macOS Big Sur 11.0.1 (OpenCore 0.6.4):- OpenCore-11.0.1-0.6.4.zip Updated all kexts to latest versions This bootpack is able to boot Mac OS Big Sur Beta 10. However, it is still getting issue where installer will exit prematurely after starting. If anyone managed to resolve this issue do give me a buzz. Found the cause of installer exiting prematurely after start. Its a hard disk issue. Also had issue similar issue when installing windows on the same hard disk. So far everything should works except sleep. integrated graphics need to be disabled in bios in order for sleep to work (i.e. no desktop freeze after wake). macOS Big Sur 11.0.1 (OpenCore 0.6.3):- OpenCore-11.0.1.zip macOS Big Sur Beta 10 (OpenCore 0.6.3):- OpenCore-11.0-Beta10.zip macOS Big Sur Beta 4 (20A5343i) (OpenCore 0.6.0):- OpenCore-11.0-Beta-20A5343i.zip So far everything works except sleep. System freezes after wake. This bootpack is based on latest OC and lilu & friends kext release based on OC 0.6.0 macOS Big Sur Beta 2 (20A4300b) (OpenCore 0.6.0):- OpenCore-11.0-Beta -20A4300b.zip So far everything works except sleep. System freezes after wake. This bootpack allow both updating of existing beta 1 to beta 2 and installing new hard drive by running the installer app from an existing Mac OS system. USB installer created from createmediainstall still cannot be booted. Resolved. As @Jake Lo advise, with latest lilu we can omit "-lilubetaall vsmcgen=1 booter-fileset-kernel booter-fileset-basesystem" stuff. Make sure to reset nvram on first OC boot and boot the usb installer on reboot. However, looks like "booter-fileset-kernel & booter-fileset-basesystem" need to be remove when booting usb only and 1st stage installation. 2nd stage looks like it still need those to boot. macOS Big Sur Beta 1 (20A4299v) (OpenCore 0.6.0) :- OpenCore-11.0-Beta-20A4299v.zip USB installer still cannot be booted using clover or opencore. Big Sur need to be cloned from existing real mac disk image. So far everything works except for sleep. Downloaded the real mac disk image and followed installation guide from here: https://www.olarila.com/topic/8977-guide-installrestore-bigsur-with-opencore/. Initial bootpack for OpenCore obtained from here: https://www.reddit.com/r/hackintosh/comments/fuf6z7/open_core_056_catalina_10154_gaz87mxd3h_i74770/. Updated network card kext from my clover bootpack and updated OpenCore to version 0.6.0. (Note: These bootpacks can also be used to boot macOS Catalina) Clover Bootpack The Clover bootpack can be downloaded from the following link:- Mac OS Monterey 12.1 (Clover v5142) CLOVER-12.1.zip Updated all kexts to latest versions too Mac OS Monterey 12.0.1 (Clover v5141) CLOVER-12.0.1.zip Mac OS Monterey 12 Beta 10 (Clover v5140) CLOVER-11.6.zip Working for Beta 10 with preferred Mac Mini Late 2014 smbios Mac OS Monterey 12 Beta (21A5248p) (Clover v5135) CLOVER-11.3.1.zip Working for Beta 1 to Beta 7 with Mac Mini Late 2014 smbios Working for Beta 8 but need to change smbios to iMac Late 2015 Not Working for Beta 9 at the moment. Getting boot loop. Mac OS Big Sur 11.6 (Clover v5140) CLOVER-11.6.zip Updated clover & all kexts to latest versions Mac OS Big Sur 11.3.1 (Clover v5135) CLOVER-11.3.1.zip So far everything should work Updated all kexts to latest version. Mac OS Catalina 10.15.7 (Clover v5126) CLOVER-10.5.7.zip Updated Clover and kexts to latest versions. Clover is already using the Quirks features which are normally required for Intel 4th Haswell desktops. Clover bootpack is able to boot Mac OS Big Sur 11.0.1 after it has been installed. Still not able to boot installer. Mac OS Catalina 10.15.4 (Clover v5116) :- CLOVER10.15.4.zip Updated Clover, Lilu.kext, VirtualSMC.kexts & Whatevergreen.kext to latest versions. Mac OS Catalina 10.15.1 (Clover v5070) :- CLOVER-10.15.1.zip Whatevergreen.kext updated to 1.3.4 to resolve blank screen after boot. Mac OS Catalina 10.15 (Clover v5070) :- CLOVER-10.15.zip Mac OS Mojave 10.14.4 (Clover v4910) :- CLOVER-10.14.4.zip Mac OS Sierra 10.12.6 / Mac OS High Sierra 10.13 (Clover v4241) :- CLOVER.zip So far, everything works including sleep with power nap! So far this motherboard is very compatible with Mac OS and patched DSDT / SSDT is not required. Credits goes to Jake Lo, Bronx Teck & Herve Notes on Integrated HD4600 GPU Although the integrated HD4600 GPU can be enabled by simply injecting intel from clover, the GPU cannot be utilized since my motherboard does not have a HDMI output! Using dedicated GPU such as RX 560 while the integrated HD4600 GPU is enabled may cause video playback in chrome to be jibrish and iTunes video playback to freeze the desktop. The integrated GPU need to be disabled from bios to resolve this. Let me know if the clover bootpack works for you. Cheers! OpenCore-13.0-0.8.5.zip
    1 point
  48. Hello everybody, these are my kexts to run Mac OS X 10.8 Mountain Lion on a Dell Precision M4400 with Nvidia Quadro FX 770M. What works: - Nvidia Card - Sound & Mic - Trackpad & Keyboard - Ethernet, Bluetooth & Wlan - Firewire - SDHC Not working: - Sleep - Shutdown Not tested: Webcam, Smartcard Reader Instructions: - Install the kexts from the "SLE" folder into System/Library/Extensions with Kext Wizard - Move the "Extra" to /(ML Volume) - Run the myHack Application -> "Run myFix" -> "/(ML Volume)" -> "Full" and wait a couple of minutes. - Boot with ML Enjoy ... Now with Kexts -.- M4400.zip
    1 point
×
×
  • Create New...