Jump to content

All Activity

This stream auto-updates

  1. Yesterday
  2. Try this file. Platforms11.xml.zip
  3. Last week
  4. Hi everybody. Wish everyone have a happy new day Today I created this Topic to ask for everyone's help in Fixing HeadphoneALC295PlugFix.zip with ALC295. I have tried all the layout-ids and I have compiled them all in the following picture: Like the photo above. Currently only layouts 3,11,24 have sound when headphones are plugged in. but lost the Speaker or Mic. I searched a few forums and found the following macOS daemon tool is ALC295PlugFix below When using this my Headphones work. I tried diving into the ALC295-Plug-Fix tool and found that it configures Node 0x19 to Param 0x24 using SET_PIN_WIDGET_CONTROL. So I tried converting them to Pinconfig: 01970724 and adding it to Pinconfig in the current AppleALC.kext but it didn't work. I couldn't use the headphones until I used the ALC295-Plug-Fix tool. But I realized that it doesn't sound really good (because I'm a music maker). And I also wanted a more permanent fix, so I learned how to Build Layout-id. Then I tried comparing them with each other and found that Layout-id 11 has the best headphone sound. Therefore, I came up with the idea of combining Layout-id 77 and Layout-id 11 together because Layout-id 77 can use Speaker and Mic, and Layout-id 11 can use Headphones. Here's what I tried: I followed this page: https://github.com/5T33Z0/AppleALC-Guides/tree/main/AppleALC_Layout-ID to Build Layout-id, to understand the steps to build AppleALC kext and to understand it too. Followed the above guide and I dumped codec_dump.txt containing information about my codec and codec_dump.png a visual representation of the data inside the codec dump. all is below. And a visual representation of the data inside the codec dump: I tried reading the above diagram in combination with opening Platform11.xml and Platform77.xml for comparison and realized that: - Int Speaker is: 20 - 2 ( in 77 ) - Headphones: 33 - 2 ( in 11 ) - Int Mic: 8 - 35 - 18 (in 77) So I edited Platform11.xml as follows below: I then edited Layout 11.xml like this: ( combine Layout-id 11 with Layout-id 77 ) Finally, for PinConfig. I use PinConfigurator software to edit PinConfig. Follow the Build AppleALC guide in OCLittle and this Guide: https://osxlatitude.com/forums/topic/1946-complete-applehda-patching-guide/ to know how to understand and fix that PinConfig. After I merged the PinConfig of Layout-id 77 and Layout-id 11 and deleted the duplicate values. I got the following values: But unfortunately even for them. My headphones still don't work. Only Speaker and Mic work. If I want Headphones to work. I still have to use ALC295-Plug-Fix. I don't know where I went wrong. If you know, please help me. Thank you very much <3. dumps.zip
  5. Released Mar 7th, 2024. Build 23E214 Enhancements, bug fixes ans security updates. Safe to install on our Hackintosh platforms. Note that it's important to update wireless kexts IO80211FamilyLegacy + IOSkywalkFamily to new versions tuned for Sonoma 14.4 (kexts used up to 14.3 no longer work). No wifi without those revised kexts. All details are available here in our dedicated thread on the matter. Also released at the same time: macOS Ventura Security Update 13.6.5 (build 22G621) macOS Monterey Security Update 12.7.4 (build 21H1123)
  6. Hervé

    macOS Sonoma is out

    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.
  7. You now call upon KBL/ABL framebuffer 0x87C00000: ID: 87C00000, STOLEN: 34 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000078B TOTAL STOLEN: 35 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 103 MB, MAX OVERALL: 104 MB (109588480 bytes) Model name: Intel HD Graphics KBL 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 Your patches, as found in your posted Opencore config file: i.e. [0], busId: 0x00, pipe: 8, type: 0x00000200, flags: 0x00000098 - Connector Analog DVI [1], busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2], busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 00000800 00020000 98000000 --> analog DVI connector type 01050900 00040000 87010000 02040A00 00040000 87010000 Other than the strange patch of connector type 00020000 for con0 (which does not matter because con0 is not used, IOReg showing screen attached to con2), I fail to see the relevance of your other patches given that the values you inject are exactly the same as those natively defined in the framebuffer. As such, you most definitely do not patch any connector's pipe and you most definitely do not patch any property of the connector used for your LG TV. Since that you've now opted for a KBL/ABL framebuffer which attaches your screen to con2, why don't you just adjust con2's pipe to 0x12? framebuffer-patch-enable 1 NUMBER framebuffer-con2-enable 1 NUMBER framebuffer-con2-pipe 12000000 DATA
  8. ok today I tried a different approach I specified pipe and types in config but l gets connected as dp but colours are violet and no audio with dp What's the problem did I do something wrong ?????? I enclose config file ioreg Funny thing Hackintool thinks I am connected with HDMI??? forgot to mention on bootup no display got it after I fidgit with connector in and out a few times. config 3.plist.zip iMac18.1.zip
  9. Im not having much luck It always connects to HDMI instead of DP If I set connector to dp black screen on boot and then I have to figit with dp cable until display work but then colours are violet. hopeless cause also after sleep screen stays black I think putting back windows and sell it again
  10. Earlier
  11. 14.4, 0.9.8 Release. I'll disable SecureBootModel and let you know about the results. Disabling SecureBootModel fixed it, Sonoma is now working with no issues, thank you!
  12. What version of Sonoma? What version of OpenCore? Try and set SecureBoot to disabled rather than default. I understand that's required for Sonoma 14.4.
  13. im trying to install Sonoma on my Latitude 5401, however on the second phase, it reboots at 22 minutes remaining, then goes into this reboot loop. Anyone have a solution? Ventura works fine. The ZIP file contains a video of the bootloop and my config.plist Archive.zip
  14. Sonoma guide revised for version 14.4 (new wireless kexts) as detailed in thread linked right above.
  15. 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
  16. the "SSDT-TPDX" helped me get the i2c trackpad working in dell latitude 7410
  17. Try and change con1's pipe to 0x12.
  18. Hey, salut Hervé! Yes, I'm using VMWare to create the installer, but it seems to be creating the USB properly. I'll go back and try again, although I might just use the terminal to do a chmod on the EFI partition.
  19. Hi colour was like violet and if I dont specify connectords it would connet as hdmi and not dp as I checked with ioreg
  20. Doesn't seem to be a standard disk or USB disk but some form of virtual setup. This matter is unrelated to the boot loader but your platform arrangement. A VM it would seem?
  21. Hi everyone! I've been off the forum for a while, and things have changed! OpenCore doesn't seem to be the preferred bootloader any more and of course, I'm having a problem with Clover. I created a boot disk for Sonoma following the instructions found here: https://osxlatitude.com/forums/topic/15648-dell-latitude-e7270-with-i7-6600u-hd520-and-1920x1080-touchscreen-high-sierramojavecatalinabig-surmontereyventurasonoma/ (Merci Hervé!) However, when I run the recommended Clover_r5157.pkg, for some reason, the EFI partition is read only: Any suggestions as to what I'm doing wrong. I did try with Clover configurator, but I had the same results. Thanks!
  22. Released Mar 7th, 2024. Build 23E214 Enhancements, bug fixes ans security updates. Safe to install on our Hackintosh platforms. Note that it's important to update wireless kexts IO80211FamilyLegacy + IOSkywalkFamily to new versions tuned for Sonoma 14.4 (kexts used up to 14.3 no longer work). No wifi without those revised kexts. All details are available here in our dedicated thread on the matter. Also released at the same time: macOS Ventura Security Update 13.6.5 (build 22G621) macOS Monterey Security Update 12.7.4 (build 21H1123) View full article
  23. No idea what you mean by colour being "funny". If colours look funny to you on screen, maybe you just need to tune/calibrate your screen profile or use a different one. IOReg shows KBL framebuffer 0x59120000, yet you still inject patches to set con0/con1/con2 to DP, which is what they natively are... ID: 59120000, STOLEN: 38 MB, FBMEM: 0 bytes, VRAM: 1536 MB, Flags: 0x0000110B TOTAL STOLEN: 39 MB, TOTAL CURSOR: 1 MB (1572864 bytes), MAX STOLEN: 115 MB, MAX OVERALL: 116 MB (122171392 bytes) Model name: Intel HD Graphics KBL CRB Camellia: CamelliaDisabled (0), Freq: 1388 Hz, FreqMax: 1388 Hz Mobile: 0, PipeCount: 3, PortCount: 3, FBMemoryCount: 3 [1] busId: 0x05, pipe: 9, type: 0x00000400, flags: 0x00000187 - ConnectorDP [2] busId: 0x04, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP [3] busId: 0x06, pipe: 10, type: 0x00000400, flags: 0x00000187 - ConnectorDP 01050900 00040000 87010000 02040A00 00040000 87010000 03060A00 00040000 87010000 No harm of couse, just totally useless.
  24. hi still trying but why is it that when I manage to connect with dp colour is funny???? I enclose ioreg iMac.zip
  25. After some additional testing this method also didn't help solving this issue
  26. Good, thanks for the feedback.
  27. It seems switching Serial Port to COM2 and using original DSDT without any patches solves the problem.
  28. The WEG manual details the connectors patches very clearly and as follows; I really don't know where you copied your values from... framebuffer-conX-enable (enabling patches for connector X) framebuffer-conX-index framebuffer-conX-busid framebuffer-conX-pipe framebuffer-conX-type framebuffer-conX-flags framebuffer-conX-alldata (completely replace the connector) framebuffer-conX-YYYYYYYY-alldata (completely replace the connector, if the current framebuffer matches YYYYYYYY) Where X is the connector index. Alldata patches can patch multiple connectors in sequence by putting them in a single string and specifying the index of a connector to start with. The string length should be a multiple of 12 bytes (the length of a single connector) You may have missed that 12-bytes alldata property is comprised of index + busid + pipe + type + flags. I specified the size of each element in my previous post. This parameter can cover multiple connectors as long as you specify a multiple of 12 bytes and these will cover the specified connector and the following multiple-1 connectors. For instance: framebuffer-con0-alldata AAAAAAAABBBBBBBBCCCCCCCCLLLLLLLLMMMMMMMMNNNNNNNNXXXXXXXXYYYYYYYYZZZZZZZZ DATA is the same as framebuffer-con0-alldata AAAAAAAABBBBBBBBCCCCCCCC DATA framebuffer-con1-alldata LLLLLLLLMMMMMMMMNNNNNNNN DATA framebuffer-con2-alldata XXXXXXXXYYYYYYYYZZZZZZZZ DATA and framebuffer-con1-alldata DDDDDDDDEEEEEEEEFFFFFFFFRRRRRRRRSSSSSSSSTTTTTTTT DATA is the same as framebuffer-con1-alldata DDDDDDDDEEEEEEEEFFFFFFFF DATA framebuffer-con2-alldata RRRRRRRRSSSSSSSSTTTTTTTT DATA Note that you can't patch con0 and con2 (without patching con1) in a single 24-bytes alldata injection. This being said, experiment with iGPU properties injections such as this: AAPL,ig-platform-id 00001659 DATA (-> KBL framebuffer 0x59160000) AAPL,slot-name Built-in STRING (-> this is purely cosmetic) force-online 1 NUMBER (-> same as igfxonln=1 boot-arg) Given that your screen appeared attached to connector con1 in a previous IOReg extract, it's fair to say that you may experiment with any other framebuffer that has con1 as DP by default. These include: Desktop: 0x59120000 (the recommended framebuffer for KBL desktop but does not seem to suit you) 0x59230000 0x59260000 0x59260007 (watch, max stolenmem set to 79MB so DVMT must be 96MB, else KP most probably) 0x59270000 Laptop: 0x59160000 (this is the default framebuffer if you do not inject any specific AAPL,ig-platform-id property) 0x59160009 0x591C0005 0x591E0000 0x591E0001 0x59260002 0x59270004 0x59270009 0x87C00000 0x87x00005 Mobile framebuffer 0x591B0000 defines 3 ports: LVDS + HDMI + DP so, if you use that one, you'll have to patch con1 to DP by adding the following properties: framebuffer-patch-enable 1 NUMBER framebuffer-con1-enable 1 NUMBER framebuffer-con1-type 00040000 DATA If you do not get anywhere with any of those framebuffer and default/native device id 0x5912 (that of your particular iGPU), then you may add the following property: device-id 0x16590000 DATA and start your experimentation again with all those frame buffers above. Then, you may consider doing it all again with other device ids but that's a rather unusual thing to do. Supported device ids are listed in the WEG user manual. If nothing works out to provide you 4K@60Hz, you may then consider patching connector's Flags but I'm dry on that one; never had to. This would be done with the following additional properties: framebuffer-patch-enable 1 NUMBER framebuffer-conX-enable 1 NUMBER (-> where X is target connector framebuffer-conX-flags XXXXXXXX DATA (-> where X is target connector and XXXXXXXX target flags value) NB: Please note that you never enter any space in DATA values; spaces are simply displayed by tools such as OCC or CC for ease of reading. Good luck.
  1. Load more activity
×
×
  • Create New...