Jump to content
InsanelyMac Forum

shrieken213

Members
  • Content count

    73
  • Joined

  • Last visited

About shrieken213

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  1. Trouble with HD 4600+ HDMI audio setup

    Made a fresh new config.plist, the new script works. Thanks!
  2. Trouble with HD 4600+ HDMI audio setup

    Here's the files. The config-script.plist is what the script returns; config-manual.plist is what I installed manually. FakePCIID.kext is also in place and is correctly loading on IOReg. (also a side note: the CloverALC script is broken; attached here as well just in case) Archive.zip AppleHDA.log.zip
  3. Trouble with HD 4600+ HDMI audio setup

    Even if I answer yes in the script it does not add the patch. I went to your GitHub and grabbed the example config.plist with all the patches included, then copied the appropriate patch into my config.plist. <dict> <key>Item 0</key> <dict> <key>Comment</key> <string>10.9-10.11-HD4600_HDMI_Audio-1of2</string> <key>Find</key> <data>PQsMAAA=</data> <key>Name</key> <string>AppleHDAController</string> <key>Replace</key> <data>PQwMAAA=</data> </dict> <key>Item 1</key> <dict> <key>Comment</key> <string>t2-10.9-10.11-HD4600_HDMI_Audio-2of2</string> <key>Find</key> <data>PQwKAAA=</data> <key>Name</key> <string>AppleHDAController</string> <key>Replace</key> <data>PQwMAAA=</data> </dict> <key>Item 2</key> <dict> <key>Name</key> <string>AppleIntelFramebufferAzul</string> <key>Find</key> <data>AwYIAAAEAAARAAAA</data> <key>Replace</key> <data>AwYSAAAIAAAGAAAA</data> <key>Comment</key> <string>10.10-10.11-Azul-Port_0x7-DP2HDMI</string> </dict> </dict> Do you mean these 3 patches? Of these, the script only installs Audio-2of2. I manually copied the last 0x7-DP2HDMI patch, and haven't installed Audio-1of2. No combination of any of these patches work.
  4. Trouble with HD 4600+ HDMI audio setup

    I've looked more into the IOReg and found that the port numbering does not line up with what the script or toleda's kext patches. VGA and DVI ports are assigned 0x5 and 0x6 respectively, but the HDMI port is 0x0. The script detects a display at port 0x7, which does not exist, and offers to add the framebuffer patch for port 0x7, which is not added. I tried manually adding the Azul framebuffer DP2HDMI patch for 0x7 and it didn't make any difference.
  5. Trouble with HD 4600+ HDMI audio setup

    All of those patches are already in the DSDT. Archive.zip
  6. Hi everyone, I'm having a little trouble getting my HDMI port to output audio. I'm using toleda's script, and I've noticed a couple things. His guide mentions installing an SSDT, which contains framebuffer and hda-gfx edits that I already have in the the DSDT from previous patches. The script detects this and doesn't install the SSDT, which is good. When I'm given the option to patch DP to HDMI, if I say yes it installs a kext patch; if I say no it does not. Regardless I do not get audio. I also don't quite understand why it needs to patch an HDMI port for DP? toleda provides little explanation on this (or why one would need this). I have FakePCIID installed, which loads correctly I think. kextstat shows the kext loaded and the IOReg has the RM,device-id injected. Since my graphics is HD 4600+ (8086:0412), I don't need any graphics injections or the FakePCIID Intel graphics injector. If it's worth anything, toleda's AppleHDA script works for enabling onboard audio; I've disabled all audio patches while I worked on the HDMI patch. Can anyone help me through this? I've attached my ioreg, DSDT and config.plist.
  7. Long time no see everyone, I'm trying to upgrade my Sierra installation to High Sierra via vanilla installer. Upgrades never caused issues before (minus Pascal web drivers) until now. It seems the High Sierra installer cannot boot from a Fusion Drive. Clover says it encounters errors loading the kernel cache, with code 0xe. I believe what the installer does before rebooting into the file copy process is try to upgrade the JHFS+ partition to APFS from what I saw on a verbose reboot, and that might be the issue. But from what I read from the Apple support documents, Fusion Drives should not be converted and indeed my drive is not (since I can reboot to Sierra after the error). Or it could be that the installer itself has compatibility issues with Fusion Drives. *note: I've also tried a createinstallmedia USB, which shows the hack can boot High Sierra via USB but not from a Fusion Drive. I'll try installing with the no conversion flag through the terminal. In the meantime, can we think of any other reasons why this might be happening? Update: no luck with the no conversion flag. It doesn't look like it's related to APFS at all, but rather an issue unique to Fusion Drives.
  8. Is there real documentation for clover

    Welcome! The official full documentation for Clover can be found in the wiki: https://clover-wiki.zetam.org It's currently offline but google cache has the pages you need in the meantime. Until it gets fixed (which it really needs to be; Sierra was just released), here's the solutions for your issues. - when I do have several boot disks which clover config is actually used? Sometimes I have the impression I am selected HD 1 for boot but config.plist from HD 2 is used....?? The config.plist on that specific boot disk/Clover installation is used. For example if you have a 250GB SSD and a 1TB HDD, both with Clover on it, and you boot from the SSD, the config.plist on the SSD is loaded. - Specifying the default boot HD in (any) config.plist seems never to be obeyed. The default Boot HD seems to be randomly selected..? Root -> Boot -> DefaultVolume parameter is used to manually set the default boot partition. It can be the volume name (e.g. Macintosh HD), the GUID of the volume, the device path shown in Clover (e.g. HD(1,GPT...) ), or LastBootedVolume. - manual overwriting of parameter settings seems to work. I'm not sure what you mean: entering config.plist configurations from Clover itself (available under Options) or manually selecting the boot option. When you do change configurations from Clover, it is temporary and will be erased on the next boot up. Feel free to ask any questions you have, there's a lot of people here that'd be happy to help.
  9. IntelMausiEthernet

    FaceTime and iMessages has been working with both of my builds for 7 months with this godly kext. Kudos again to the giant cat!
  10. Enabling PS/2 Support for Desktop Motherboards?

    VoodooPS2 also does not work. I think I'll just call it quits for now...
  11. A Guide on Fixing Sleep Issues

    I discovered the repercussions of the _PRW patch. Changing to 0x09, 0x04 disables wake by that device completely, at least on the two boards that I tested on. If it's applied to a USB device (EHC, XHC) it will disable wake by USB keyboard and mouse, etc. This will probably limit how you wake the computer to the power button. If we could investigate this further I'd appreciate it.
  12. Fixed it up! My DSDT's XHC device was apparently misconfigured by Asus. For SSP1, UPCP had the wrong values; all SSPx devices were missing a bunch of code in method PLD. After editing those in, everything is working fine. I also noticed that even with the device named XHC, the kext itself has a hard limit of 15 ports on the XHC device. This meant that I still had to cull the unused HSxx devices. However, the SSPx devices were automatically matched to their corresponding HSxx counterparts, so I didn't have to get rid of the unused SSPx devices (SSP3 and SSP4). I used VCH888's DSDT as the source, with a bunch of other DSDTs floating around to make sure this would not fubar my DSDT. I'll try the USB high current mod next, using my 2011 MBP's DSDT as base! Archive.zip
  13. Removing the dummy kext results in the system detecting the HSxx ports (USB 2.0) 1 through 14 but not the SSPx ports. In other words, the XHC device works fine but USB 3.0 does not work. I'm aware of the port restriction, so I'll dive into the DSDT, remove the extraneous HSxx ports and hopefully this will get USB 3.0 working. However, I'm not sure about the repercussions this will have on my system. Also, it only recognized 14 out of the 15 port limit. Does anyone have experience with this? EDIT: I removed the unused ports, which I presume stem from the USB 2.0 headers on the motherboard which I don't use. However, USB 3.0 is not working. The system is simply not recognizing the SSPx devices. I've attached the IOReg with the dummy kext removed and one with the ports removed. Balthasar.iojones.zip Removed.iojones.zip
  14. Hi guys, I've already finished installing El Capitan and it runs fine except for the USB and PS/2 ports. But since the USB problem is more relevant to this forum, I'll be posting the issue here. I own a Maximus VII Gene running a 4790K and a GTX 770. The board uses a mix of Intel and ASMedia USB controllers, and so far (and surprisingly) only the ASMedia controller provides reliable USB 3.0 connections. I am not using the EHC controllers. I've looked into the new USB issue as the sticky says, and I'm completely stuck. My DSDT already uses the device name XHC instead of XHC1, but the Intel XHC device makes 6 out of 8 ports available, and all on USB 2.0 speeds. If the thread is right, it should have automatically detected all the ports and assigned USB 3.0 to the appropriate ports. This time I tried a dummy kext on SMBIOS iMac14,2. After figuring out which of the port devices are actually active, I used UsbTreeViewer on Windows, identified each port's device and edited Info.plist to match the DSDT. Right now XHC only has HS05, HS06, HS12 and HS14 available, none of which are working, and the remaining Intel ports are being picked up by EHC1. I've attached the dummy kext, ioreg and DSDT. Can you guys figure this out? Archive.zip
  15. Enabling PS/2 Support for Desktop Motherboards?

    So far I made a little progress in getting the kext to recognize the PS/2 controllers. The CID for the devices PS2K and PS2M did not match those found in both PS2 kexts. They were changed to PNP0303 and PNP030B respectively. Now the ApplePS2Controller.kext that you linked recognizes the controller properly and creases a PS/2 keyboard device tree in IOJones when the keyboard is plugged in. However, I can't type anything at all. I'll try VoodoPS2Controller in a bit to see if that changes anything.
×