Jump to content

onemanosx

Members
  • Posts

    1,541
  • Joined

  • Last visited

Everything posted by onemanosx

  1. You should be looking at ioreg instead of system report window. See my screenshot. HS01 is a USB 2.0 speed although physically you are using the USB3.0 port. SSxx is USB 3.0 speed. To get USB 3.0 speed you should be connecting to a SSxx port. I suggest you do the USB test again after DSDT is patched by our good friend @Mald0n
  2. [ref]tarantababu2002[/ref], here is my comment 1. SSDT is pointless without a DSDT. Not required. Your SSDT is not even configured to your specific. 2. Boot argument - You should choose either exclude or include method. I propose exclude method. 3. You are using a 2.0 hub on a USB 2.0 port. Hence the 2.0 speed. 4. Non related - You are running full IGPU acceleration alongside your Radeon setup. Quick sync doesnt require igpu to run on full acceleration. I also suggest you have your DSDT properly patched - visit here https://Olarila.com/forum/viewtopic.php?f=19&t=1131 Edit: I also suggest you test the ports again properly by using a USB 2.0 device to test for HSxx ports and use a USB 3.0 device to test for SSxx ports.
  3. Thanks!
  4. New update boots faster I think.
  5. Provided you did not use patched AppleHDA and did not install VoodooHDA or sound related kexts in S/L/E, you will need to choose correct layout-id for your laptop if you decide to use AppleALC + Lilu kexts. Check layout ids here: https://github.com/acidanthera/AppleALC/tree/master/Resources/ALC255 Looking at your ioreg you posted, DSDT injection for layout id is working as expected.
  6. [ref]duyseo[/ref], thats funny. I updated bios and still bootable. But, the new acpi tables cannot be extracted properly. In any case, the bios update has no major impact and no need to be alarmed Great to knw the guide helps and double glad to know someone else is also using the same mobo!
  7. [ref]duyseo[/ref], awesome! Thanks for the share. Connected using DP or Dvi?
  8. [ref]duyseo[/ref], can you share the smbios u used?
  9. You are expected to reuse your i2c patched dsdt from High Sierra or repatch your current dsdt to enable i2c trackpad. However I am not sure which method is working for you since you had used 2 different kexts for trackpad which is unrelated to each other
  10. [ref]tarantababu2002[/ref], Please insert all USB ports with your USB device and run this app http://Olarila.com/files/Utils/RunMe.app.zip and upload the output folder.
  11. [ref]foliasis[/ref], Use this folder with your working I2c High Sierra DSDT. Boot and rebuild cache and reboot. Upon reboot run this app and upload here http://Olarila.com/files/Utils/RunMe.app.zip CLOVER 2.zip
  12. Is your dsdt from HIgh Sierra attached? Cos I dont dare to patch for I2c from scratch
  13. For I2C you probably need to rebuild cache after upgrade. I am sure you are still using the dsdt from HSierra. Let me know if that helps. Otherwise post send me file
  14. Are you using Olarila image? Try re-write USB image or use a different thumb drive.
  15. Use older version of applealc probably version 1.3.0 and below. And your codec is actually ALC887. Use this app and upload your whole dump http://Olarila.com/files/Utils/RunMe.app.zip
  16. Oprah on insanely? Cool!!
  17. This post is reproduced with permission. Original author: https://www.facebook.com/samuel.cabral.583?fref=gs&dti Original Post: https://www.facebook.com/groups/hackintoshbrazil/ Preparation: Source: https://web.archive.org/web/20170825221050/http://www.osx86.net:80/forums/topic/20664-guide-edid-injection/ The tutorial is targeted for DVI-I, DP (Displayport) or HDMI connection. If you use VGA Monitor, a small tweak will be required. The involved tweak is to inject the edid of the monitor. Please refer to below guide. How to get custom EDID (for VGA only if using HDMI, DVI-I or DP, please skip this step) 1. On Windows, download and run RW-Everything (this one has multiple interesting utilities but you can use any other, like EDID Viewer, Phoenix EDID Designer, and possibly others...) Note: Linux is also capable of dumping EDIDs, but for my laptop's built-in display, it was only possible through Windows. If you want to try it from Linux, I recommend this guide here https://web.archive.org/web/20170314141954/http://hotcashew.com/2013/08/fixing-invalid-edid-in-linux-wit-fglrx/. 2. Assuming you're using RW-Everything, click on EDID button. You'll see something like this: (don't copy, it won't work for you, EDIDs differ for each display) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F00 00 FF FF FF FF FF FF 00 4C A3 00 02 FF FF FF FF10 00 15 01 03 80 1D 10 FF 2F 00 00 A0 57 49 9B 2620 10 48 4F 00 00 00 01 01 01 01 01 01 01 01 01 0130 01 01 01 01 01 01 9E 1B 56 78 50 00 18 30 30 2040 25 00 25 A5 10 00 00 19 00 00 00 FD 00 00 3C 0050 D9 08 00 00 00 00 00 00 00 00 00 00 00 00 00 0060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0070 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CC 3. Copy and paste it on notepad. Erase the first line and the first column, they are just references, not part of the EDID. You will have something like this: 00 FF FF FF FF FF FF 00 4C A3 00 02 FF FF FF FF00 15 01 03 80 1D 10 FF 2F 00 00 A0 57 49 9B 2610 48 4F 00 00 00 01 01 01 01 01 01 01 01 01 0101 01 01 01 01 01 9E 1B 56 78 50 00 18 30 30 2025 00 25 A5 10 00 00 19 00 00 00 FD 00 00 3C 00D9 08 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CC 4. Remove every line break and spaces, ending up with a single line of hexadecimal code, then use HEX -> Base64 to convert it to base 64. Save the result as EDID64.txt on a pen drive. This is my base 64 EDID, the general format of yours will resemble it: Note: Skip this conversion if using Clover configurator. In Clover configurator the HEX can be input directly AP///////wBMowAC/////wAVAQOAHRD/LwAAoFdJmyYQSE8AAAABAQEBAQEBAQEBAQEBAQEBnhtWeFAAGDAwICUAJaUQAAAZAAAA/QAAPADZCAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMw= 5. Final steps: just add it to your Clover config.plist like the example below: Source: https://web.archive.org/web/20170825221050/http://clover-wiki.zetam.org/Configuration/Graphics#InjectEDID <key>Graphics</key> <dict> <key>InjectEDID</key> <true/> <key>CustomEDID</key> <data>AP///////wBMowAC/////wAVAQOAHRD/LwAAoFdJmyYQSE8AAAABAQEBAQEBAQEBAQEBAQEBnhtWeFAAGDAwICUAJaUQAAAZAAAA/QAAPADZCAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAMw=</data> </dict> Desktop users only Please follow these sets of instructions: 1. Set 128MB or more for DVMT memory in bios. 2. Set 1024MB of pre-allocated memory to the bios (Note: The names of these features may vary depending on the motherboard model) 3. Open your config.plist in the Clover Configurator. 4. Enter 0x01668086 in Devices / FakeID / IntelGFX. 5. Enable Intel Graphics & Inject EDID option. 6. Type 0x0166000a in Graphics ig-platform-id. 7. Set the SMBIOS for iMac13.1, iMac13.2, MacMini6.1, or MacMini6.2 Known Issues Here's how to solve the main problems that can occur with the HD2500. 1. Black screen One situation that can cause black screen is the use of the WhateverGreen kexts and the old IntelGraphicsFixup. Use of mentioned Lilu plugins should be avoided. There is also another situation where the graphics may not work. The source of the problem may be on the motherboard itself as Sandy Bridge and Ivy Bridge generations share the same socket 1155. However, this can be easily fixed by using fake id of the latter generation board. 1. Open your config.plist in the Clover Configurator. 2. Enable addDTGP and addIMEI in ACPI / DSDT / Fixes 3. Enter 0x1e3a8086 in Devices / FakeID / IMEI. 4. This FakeID serves to camouflage an Intel 6 Series for Intel 7 Series. 5. Save Changes. 2. Glitches and artifacts The fix does not solve the problem completely but merely reduces its artifacts. 1. Open config.plist in the Clover Configurator. 2. Turn on the slide=0 flag in the Boot / Arguments option. 3. Save Changes. 3. Crashes in certain applications Some apps and Chrome browser itself often crash and display glitches when opened. The reason is somewhat obvious. Such software is optimized by OpenGL / Metal. And it turns out that the HD2500 has never been able to perform the advanced features of these APIs as the HD4000 and newer ones do. The solution is simply to disable the hardware acceleration (GPU) of these applications. Credits: Samuel Cabral Other Reading Resource Understanding Framebuffer Patching https://osxlatitude.com/forums/topic/10267-understanding-and-patching-framebuffer-haswell/ IntelHD4000 QE/CI Acceleration http://blog.stuffedcow.net/2012/07/intel-hd4000-qeci-acceleration/
  18. 1. Place kext in clover>kexts>other folder 2. In clover, set Inject Kext in System Parameter tab to YES This should load kext everytime you boot.
  19. [ref]Akshunhiro[/ref], You need to find HSxx first with USB 2.0 device, followed by SSxx with a USB 3.0 device. Looking at your boot arg, it doesnt look right.
  20. [ref]Naveed Ahmad[/ref], Run app and upload here http://Olarila.com/files/Utils/RunMe.app.zip
×
×
  • Create New...