- Oct 13, 2011
- Asus ROG Z270 Maximus IX Hero
- RX 580
- Mobile Phone
Added an update to explain why I took this build back to HFS+.
The switch was prompted by a discussion about it here, and mainly because the 18,3 definition contained support for the Kaby Lake processor family, which we're using. It's just more aligned with the hardware this system is pretending to be! Ad for noticeable advantages, it's difficult to say. I certainly didn't degrade performance in any way.I was curious as to why you switched over to 18,3. Do you find any advantages in doing so since you changed over?
1) Depends on how much work/effort you want to go through. I went from HS to Mojave to Catalina (over time) and it wasn't too bad. This is documented in my build.I didn't think I'd ever upgrade this again, but with the prospect of me buying Apple hardware once again once the transition to ARM-based silicon is complete, and the EOL of High Sierra with the release of Big Sur, an Intel-free future for Apple has meant I want to eek a couple of more years from this Hack. I've bitten the bullet and bought a Sapphire RX 580 Pulse. I know it's not as powerful as the 1070, but I didn't want to spend too much money. I'm undecided if I'll keep the 1070 for Windows (I dual-boot) or just sell it so that I come out even-money.
I have a couple of main decisions, now:
1) Do I upgrade my (pretty-much fully functioning) High Sierra install, or go for a clean install?
2) Regardless of which I choose for (1), do I go for Mojave as it's relatively bug-free, or go for what I perceive to be a worse OS in Catalina?
I guess if I upgrade, Mojave makes more sense as it's still mostly the same as HS. I also haven't done ANY research on which of my apps may be 32-bit yet, so that could be a bar to going with Catalina anyway.
If @JCMunsonII or @Stork want to chime in I'd be very happy to hear your opinions, as I value them highly as the inspirations for this build.
Things I'd like to fix post-install would be:
a) Front-panel headphone socket not working (worked with VoodooHDA in Sierra, doesn't with Lilu/ALC in HS, although haven't tried every layout-id).
b) Fenvi wireless card wouldn't connect to any WiFi networks so I removed it (I use wired ethernet as primary), and I do have a USB dongle for WiFi that works, so not critical
c) Sleep issues (again!)
See the Apple News forum section. A couple of good long threads talk about the Apple Silicon (ARM) transition....
What's this about Apple going to ARM??? Not that I'm paying attention, but maybe I need to...
I'll run Multibeast after I've upgraded and see if it fixes it. Layout-id '1' worked for me for the rear sockets, just not the front panel. Neither did 3, or 7. Loads more to try, though!My case's Front Panel audio connections work. I'm using the latest AppleALC audio kext as found in MultiBeast. I haven't change the audio layout-id; IIRC, it's "1".
I have a custom manual SSDT-USB set up from my original install, but I'd been looking at Hackintool and may use that instead. Could be that something got screwed up in the upgrade from Sierra to High Sierra I guess. I'll look at your builds for Hackintool advice. The Fenvi card was identified fine, it would just never actually connect to a WiFi network.My Fenvi WiFi/BT card works as it should. Make sure you are using the motherboard USB Header #1. (I think it's labeled like that.) Additionally, your USB 15 point limit might need updating. I've converted to a SSDT-USB as created by using Hackintool which I've documented in several of my build descriptions.
Good call on trying it in a different slot, could have been an issue I guess.b) My Fenvi card works just peachy, and it's in the further slot from the CPU (whatever number that is).