Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PATA and macOS Monterey support #707

Open
khronokernel opened this issue Nov 7, 2021 · 3 comments
Open

PATA and macOS Monterey support #707

khronokernel opened this issue Nov 7, 2021 · 3 comments
Labels
back-end Core functionality help wanted Extra attention is needed

Comments

@khronokernel
Copy link
Member

khronokernel commented Nov 7, 2021

With macOS Monterey, the AppleIntelPIIXATA we use to restore PATA support broke. Because of this, numerous 2008 era Macs have lost support for their DVD drive when booted into Monterey.

Currently unknown where the issue lies, further investigation required.

Affected Models

  • MacBook4,1
  • MacBookPro4,1
  • iMac7,1
  • iMac8,1
  • MacPro3,1
  • Xserve2,1
@khronokernel khronokernel added back-end Core functionality help wanted Extra attention is needed labels Nov 7, 2021
@HackintoshHD
Copy link

HackintoshHD commented Nov 10, 2021

Not that I had a direct answer to the question - I just want to mention that AppleIntelPIIXATA is open source (maybe helpful in this context).

@joevt
Copy link

joevt commented Nov 14, 2021

First version: 10.2 - 10.2.8 AppleIntelPIIXATA-6
Last version: 10.6.3 - 10.6.8 AppleIntelPIIXATA-251.0.1
Starting with 10.7, the only ATA stuff is IOATAFamily.

@Ivantroniks
Copy link

Hello

Just a suggestion, AppleIntelPIIXATA.kext makes Monterey take 3 times longer to boot than with kext disabled, my suggestion is to limit the use of kext to big sur using the max kernel to 20.99.99, in which a solution is found.

Boot time with kext enabled 1min 20sec
Boot time with kext disabled 23sec
(MacPro 3.1, NVMe)

Also the boot time is affected in an iMac8,1 I suppose in all the machines that use the kext.

(This only affects Monterey)...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
back-end Core functionality help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants