Timeline for How can I attempt to boot an older version of macOS than my hardware supports?
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 6, 2022 at 21:47 | comment | added | 1110101001 | Hm you are right, gpu accel will be a major issue then. The issue you saw isn't a missing kernel symbol per se but a missing symbol in one of the other kexts in the driver hierarchy the broadwell driver depends on. It is quite possible they completely changed the graphics acceleration backend on 10.10 in order to support things like metal, and if so porting will be nearly impossible since not much of the graphics stack has been reverse engineered. Doubly so on 10.11+ where the entire graphics stack was definitely overhauled. | |
| Jan 6, 2022 at 15:00 | comment | added | Wowfunhappy | @1110101001 One day, I'd really like to get Mavericks on a modern Ryzen system. A custom kernel already exists, courtesy of "Bronya". For a few days in 2019, I likely had what was the most powerful Mavericks computer to ever exist, but I couldn't get graphics acceleration to work with the GPU I had on hand at the time, and I was time limited by MicroCenter's one-week return window. macintoshgarden.org/apps/custom-kernels-ryzen-processors | |
| Jan 6, 2022 at 15:00 | comment | added | Wowfunhappy | @1110101001 (To be clear, this was a MBA, not a MBP.) There's a tad more info in this thread on MacRumors: forums.macrumors.com/threads/…. Someone else also thought that the keyboard and trackpad might be due to protocol changes, and I actually did try moving over the Broadwell graphics kexts from Yosemite. The Yosemite kexts actually may have partially worked, but I did run into a missing symbol, and I decided to cut my losses rather than get into kernel patching. I ultimately just swapped the motherboard with one from a 2014 MBA. | |
| Jan 6, 2022 at 10:02 | comment | added | 1110101001 | Last missing piece is then graphics acceleration. I don't know enough about this – have people in the hackintosh community written drivers, or do they just rely on the ones built in with the OS? If it's the latter then we seem stuck. I wonder what would happen if you took kexts from a newer version and tried them on mavericks, possibly patching the kernel as needed to provide any missing symbols. Unlike userspace stuff which links against a bunch of libraries, the kernel interface should remain relatively stable over time so I think it might work? | |
| Jan 6, 2022 at 9:55 | comment | added | 1110101001 | But it is still possible I think. Linux clearly runs on those machines, so they should have reverse engineered how to communicate with the SMC on the newer machines as well. And the hackintosh community has VirtualSMC so all you need to do is write a shim layer where virtualsmc will call out to real smc. Maybe it already supports it, I don't know. But I think it is absolutely possible overall. | |
| Jan 6, 2022 at 9:52 | comment | added | 1110101001 | This will also technically work for fore touch trackpad as well, so I definitely think running mavericks on 2015 MBP is not too difficult. 2016 onwards will be a bit trickier because of the T1 nonsense, but in principle I do not see why it wouldn't work. Linux (and/or hackintosh folks) have drivers to support all the relevant peripherals on the newer systems (for linux you may have to port them over yourself). The only tricky parts might be something like the smc/pram interfaces, since that presumably changed a lot with the T1 chips and mavericks won't know what to do. | |
| Jan 6, 2022 at 9:49 | comment | added | 1110101001 | "I still couldn't use the internal keyboard or trackpad" – I wonder why this is... the 2015 MBA still has the physical click trackpad so it should have worked. Although possibly they might have changed the communication protocol. I think we can leverage work from the linux and hackintosh community here and write out own keyboard/trackpad driver. I wouldn't say it's trivial, but it can be a weekend project for someone who's familiar with it, as all the hard lifting has been done by the guys who wrote VoodooMultitouch framework and reverse engineered the hardware protocols. | |
| Oct 29, 2020 at 0:00 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 165 characters in body
|
| Oct 9, 2020 at 1:43 | vote | accept | Wowfunhappy | ||
| Oct 8, 2020 at 10:06 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 3 characters in body
|
| Oct 7, 2020 at 2:11 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
I keep finding stupid typos! :(
|
| Oct 7, 2020 at 1:19 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 6 characters in body
|
| Oct 5, 2020 at 21:03 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 36 characters in body
|
| Oct 5, 2020 at 20:47 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
deleted 12 characters in body
|
| Oct 5, 2020 at 17:15 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
deleted 12 characters in body
|
| Oct 5, 2020 at 17:08 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 29 characters in body
|
| Oct 5, 2020 at 17:00 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
deleted 5 characters in body
|
| Oct 5, 2020 at 16:53 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 12 characters in body
|
| Oct 5, 2020 at 16:44 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 1 character in body
|
| Oct 5, 2020 at 16:37 | history | edited | Wowfunhappy | CC BY-SA 4.0 |
added 20 characters in body
|
| Oct 5, 2020 at 16:25 | history | answered | Wowfunhappy | CC BY-SA 4.0 |