@Alex: works great. I am using EFI mode and mainly the Intel graphics adapter on my MBP6,2 for about 3 months now.
@Anders: at least for 6,x MBPs.
@Pedro: thats bad -- seems like earlier firmware/models default to AHCI when booted in pure EFI and newer don't. To confirm this, could you please verify that you're really in pure EFI mode?
e.g.: load efivars (modprobe efivars) and look for /sys/firmware/efi/vars/
or look for EFI range messages in your kernel log (dmesg):
> NX (Execute Disable) protection: active
> EFI v1.10 by Apple
> ACPI=0x8b70e000 ACPI 2.0=0x8b70e014 SMBIOS=0x8b674000
> Kernel-defined memdesc doesn't match the one from EFI!
> EFI: mem00: type=7, attr=0xf, range=[0x0000000000000000-0x000000000008e000) (0MB)
> EFI: mem01: type=0, attr=0xf, range=[0x000000000008e000-0x000000000008f000) (0MB)
> EFI: mem02: type=10, attr=0xf, range=[0x000000000008f000-0x0000000000090000) (0MB)
> ...
> but I do hope the patch gets merged into mainline kernel.
My hopes aren't too high. I haven't heard anything from the maintainer and that usually means: no, sorry.
Sorry for getting back to this so late.
@Alex: works great. I am using EFI mode and mainly the Intel graphics adapter on my MBP6,2 for about 3 months now.
@Anders: at least for 6,x MBPs.
@Pedro: thats bad -- seems like earlier firmware/models default to AHCI when booted in pure EFI and newer don't. To confirm this, could you please verify that you're really in pure EFI mode? efi/vars/ 0x0000000000000 000-0x000000000 008e000) (0MB) 0x000000000008e 000-0x000000000 008f000) (0MB) 0x000000000008f 000-0x000000000 0090000) (0MB)
e.g.: load efivars (modprobe efivars) and look for /sys/firmware/
or look for EFI range messages in your kernel log (dmesg):
> NX (Execute Disable) protection: active
> EFI v1.10 by Apple
> ACPI=0x8b70e000 ACPI 2.0=0x8b70e014 SMBIOS=0x8b674000
> Kernel-defined memdesc doesn't match the one from EFI!
> EFI: mem00: type=7, attr=0xf, range=[
> EFI: mem01: type=0, attr=0xf, range=[
> EFI: mem02: type=10, attr=0xf, range=[
> ...
> but I do hope the patch gets merged into mainline kernel.
My hopes aren't too high. I haven't heard anything from the maintainer and that usually means: no, sorry.