Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


arsradu last won the day on August 4

arsradu had the most liked content!

1 Follower

About arsradu

  • Rank
    InsanelyMac Deity

Profile Information

  • Gender

Recent Profile Visitors

7,523 profile views
  1. arsradu

    AppleALC — dynamic AppleHDA patching

    Thanks. I guess that's why right now I only have two Line-Ins and no Microphone in Inputs. Also, it would help enormously if you could share the resource files you used for this build, so I can compare to what I have right now. I can't test this build right now, but I will test it as soon as I get home and let you know. So, if I got this right, you're saying there is no way to have something like in the screenshot below fully functional, right? Right now I've got two inputs, both configured as Line-in. I don't mind it. I just want to configure this to match the ports mapping as well as possible. So if this is it, then I'm very happy with the result! By the way, thank you very much for the feedback! Yesterday I spent almost all day trying different things. None of them brought the 3rd Input. :))) And now I know why. It just can't be done. I was expecting to be some limitations with this. I'm surprised it works so well for the Outputs (perfect match, no issues).
  2. That motherboard is not looking good. I remember you said you don't use a dedicated graphics card, so, you can't switch to that, but can you share the video options you've got and their status (enabled/disabled etc) from your BIOS? Screenshots would be even better. Config-wise, it looks good to me. So...I'm afraid all of this might go down to motherboard and BIOS. I never liked these pre-built systems. They put all kinds of c**p in them.
  3. arsradu

    AppleALC — dynamic AppleHDA patching

    @MacPeet Oh, I see!! I was wondering why it's so different in all the Platforms.xml files I've looked at (which was also another source of confusion). Hahaha. Ok, I'll try it! Thank you!!!
  4. arsradu

    AppleALC — dynamic AppleHDA patching

    You are correct. Node 20 is very common and it's also what my motherboard is using. I also have audio with Layout 28, for example (and others too). But the layout itself doesn't match my hardware. There is no Digital Out for example in my case. Also, the inputs are a bit tricky, as well. Cause my motherboard has a Line In and a dedicated Mic (on the back), and there's also a Mic on the front panel. Which I'm not sure if they can be configured like that. Meaning 2 Mics (Front and Back) and a Line In for the back... Any idea?
  5. arsradu

    AppleALC — dynamic AppleHDA patching

    With the attached files, at first I didn't have sound with Internal Speakers option. The layout itself was present (1 internal speaker & 3 Line Outs), but no actual sound with the Internal Speakers option. Turns out there was a duplicated entry in PinConfig.kext -> Info.plist. It was present at line 24 and 204 (as per your screenshot). So I removed my entry and recompiled, leaving only your entry. And that fixed the problem. And with that, I also saw some differences between my attempt and your editing. So far so good! Now I'll just have to take a look at the points you mentioned above and learn how to do it better in the future. Cause you're a wizard. And I've got so much to learn from you. @MacPeet, many, many thanks for this!
  6. arsradu

    [pre-release] macOS Mojave

    You could try this for a possible fix: https://lifehacker.com/how-to-fix-an-itunes-library-corrupted-after-enabling-a-1715400220 Or this: https://www.lairware.com/guide/fix_damaged_library.html Pretty sure it's not a general issue though (I personally have never encountered it).
  7. Well, you can keep the relevant serials for iMessage (MLB & ROM) in place, or get new ones for the new SMBIOS.
  8. Strange. This issue should not occur with the iGPU (and it didn't in my case). I know this is your first post, and I welcome you to this forum, but I'm gonna ask you to add your hardware information to your signature to see what we're dealing with. I can see you're using a Haswell system. But still, it would be nice to know a little more than that. If your WhateverGreen kext is up to date (as it should be), you shouldn't need IntelGraphicsFixup kext anymore since it's already included into WEG. Could you try to remove it (or move it to Desktop, so you can put it back in case of anything) and try again? About the config, I would strongly recommend you to always remove serial numbers from SMBIOS and RT Variables before uploading your config (or the entire EFI) for analysis. Also, could you try iMac14,2 for once and see if it makes any difference? You can simply make a copy of your current config.plist, edit it, and rename the old one for iMac13,3 to configiMac13,3.plist or something, so you can access it from Clover GUI in case you need it (you can name it whatever you want, but it needs to contain the "config" part). And could you please, check the option to Inject System ID in your config's System Parameters section? Otherwise, config looks ok.
  9. arsradu

    AppleALC — dynamic AppleHDA patching

    Thanks a lot! You would probably be surprised to know that I've actually read both of them. And I actually started this journey on the AppleALC wiki page. So yeah...I did some research on this, as well. It's not like I waited for someone to do it for me. And this is actually more about learning how to do it, than fixing the actual layout. I love to learn! And this has proven to be pretty damn challenging to learn. Also, I found the first tutorial to be mind boggling hard, though very detailed, maybe too detailed (especially for someone with 0 experience and knowledge in this area) and the second one, credit to MacPeet, really, really good, a lot more accessible and easier to understand. Still, I must be doing something wrong, or trying to do more than I should, or not doing something...cause I can't seem to get it to work. I get no sound and no options in System Preferences... I also thought it should be easier, since I'm not actually adding an entirely new codec, but rather just a new layout to an existing one. But yeah, so far, no luck. And, judging from what you said above, I guess I'm doing more than I should... So I'm breaking something by trying too hard. I just don't know what that is. Everything seems in order. It just...doesn't work.. Thank you very much for the suggestions.
  10. arsradu

    [pre-release] macOS Mojave

    Holy balls! Which SSD is that? You have a crapload of them in your signature. :)))
  11. That's how you do it. Good job. Glad you managed to fix it.
  12. arsradu

    AppleALC — dynamic AppleHDA patching

    Could you mention a good one? I'm trying to get my layout id fixed and...I couldn't find a complete guide on how to do this for AppleALC. I found plenty for patching AppleHDA (which is similar, but not quite the same thing). And I don't want to mess with that. I just want to compile an AppleALC kext for my motherboard layout. Shouldn't be that hard, should it? I suppose the problem in my case are probably the resources (LayoutID.xml and Platforms.xml). Also, I never understood why a specific Layout ID needs to be used. I mean, in this case, why 3? Why not 66? How do you choose? You flip a coin? There has to be some sort of reasoning behind it. But nobody seems to either know it, or explain it. I wish someone could point me to the right direction. I'm probably pretty close to getting this done. But it just doesn't work. And I don't know why. I tried taking examples from the other layout IDs for my codec, but nothing worked. And there are so many things that I don't understand why are they used. Or where do they come from. I feel there might be an easier way to accomplish what I want (which is just a better mapping of my ports for my particular motherboard). But I couldn't find a complete tutorial. I learned some things form one tutorial, others from other tutorials. But I couldn't find any tutorial to learn how to do it from A to Z. From the beginning which is taking a codec dump, to compiling AppleALC into a kext. I know that would probably be a huge thread. But there are too many missing informations right now. Too many variables to change. And it's getting really frustrating.
  13. arsradu

    [pre-release] macOS Mojave

    Which is exactly why we created this thread here. You might wanna check it out.
  14. arsradu

    [pre-release] macOS Mojave

    You might not like this...and I can't really advise you considering you've got some patches from that site which I never tried before...I don't know how good they are...so I don't really know if it's from that or not, BUT what you could try...is an OS reinstall. You could try to reinstall on top of the current installation, so that you don't lose any data. If that doesn't work, I would suggest backing up all the personal stuff you need and do a clean install. I know, it's like the ultimate solution. But I'm running out of ideas here. Also, I would highly recommend to use the default, unchanged/unpatched installer from the App Store. And, if possible, try to use video fixes from known sources (preferably official sources) so you can always be up to date. Also, if you have a spare HDD/SSD laying around, I would strongly recommend using it as Time Machine backup drive. Having one of these backups saved my butt many, many times. It does take a while to restore it, especially if the backup is on a mechanical drive, but it's totally worth it.
  15. arsradu

    [pre-release] macOS Mojave

    Hmm....are you using any kexts for fixing video issues? Such as WhateverGreen, NvidiaGraphicsFixup or IntelGraphicsFixup? For as far as I know, if you have such issues, you should only stick to WEG. The other ones are already included into it, if my information is correct. So it's probably not a good idea to combine them. Of course, you should make sure you're on the latest version of that. It would help to know what hardware do you have. I'd recommend adding this information to your signature for easy access. FV is not active by default. You need to activate it yourself from System Preferences -> Security & Privacy -> FileVault. But in this case, it's not gonna make any difference. Also, if you have a spare keyboard (connected via USB), it would be interesting to see if it works with that one.