Jump to content


  • Content Count

  • Joined

  • Last visited

About tufty

  • Rank
    InsanelyMac Protégé
  1. tufty

    Lenovo ThinkPad T420 with UEFI Only

    Windows? Ain't no steenkin' Windows here ... which is causing me a slight headache, actually; I'm going to need to de-whitelist my BIOS and the only patched version of 1.39 I can find (*ahem* yours *ahem*) requires Windows to update. Your dsdt works impeccably on my machine, though. Cheers Simon
  2. tufty

    Lenovo ThinkPad T420 with UEFI Only

    Thanks Do you happen to know what patches you applied to your DSDT? Simon
  3. tufty

    Lenovo ThinkPad T420 with UEFI Only

    Hello So, I decided to give 10.9 / UEFI a go on my Thinkpad. It's an x220 (i5-2520M @ 2.5GHz). Thanks to this thread in general, and to tluck's exceptionally helpful guide, I've got as far as a working 10.9 install using clover and the "generic" config.plist. Everything (that's expected to) appears to work. So far, so good. However, going the "step further" to booting off the hard disk isn't going anywhere. I've installed the latest Clover (r2482) and figured I'd give it a shot with tluck's T420 set. Now, my x220 has a 1366x768 screen, so I renamed OEM/ProductID.1366x768 to OEM/4290CE3, slapped the various kexts into S/L/E using _kext-install-SLE.bash, created and installed my custom ssdt, synced, pulled the USB sticks, rebooted, and prayed. Startup got as far as the Apple logo with spinning indicator, but crashed / hung with a black screen at the point windowserver was trying to come up. Booting with -v got me no further, it was crashing / hanging at the point it stopped showing me anything. Rebooting with the install stic's Clover was fine, nothing particularly useful in /var/log *except* a pile of cryptic WindowServer crashlogs. So. Figured it was either an extension or something in config.plist (dsdt.aml is identical between the "stock" and "OEM" setups, and I'd tried without my ssdt.aml). Eventually, it was to do with the "Graphics" section in config.plist. "Generic" config.plist <key>Graphics</key> <dict> <key>DualLink</key> <string>0</string> <key>Inject</key> <dict> <key>Intel</key> <true/> </dict> </dict> from config.plist for the biggerer, betterer screen (OEM/ProductID.1600x900/config.plist) <key>Graphics</key> <dict> <key>Comment</key> <string>LCD 1600x900</string> <key>CustomEDID</key> <data> AP///////wAw5OICAAAAAAEUAQOAHxF46jOFmVZVkScXUFQAAAABAQEBAQEB AQEBAQEBAQEBgCVAgGCEGjAwIDUANq4QAAAYQB9AgGCEGjAwIDUANq4QAAAY AAAA/gBMZW5vdm8KICAgICAgAAAA/gAxNjAweDkwMAogICAgAMc= </data> <key>DualLink</key> <string>1</string> <key>Inject</key> <dict> <key>Intel</key> <true/> </dict> <key>InjectEDID</key> <true/> </dict> And finally, from OEM/ProductID.1366x768/config.plist <key>Graphics</key> <dict> <key>Comment</key> <string>LCD 1366x768</string> <key>CustomEDID</key> <data> </data> <key>DualLink</key> <string>0</string> <key>Inject</key> <dict> <key>Intel</key> <true/> </dict> <key>InjectEDID</key> <true/> </dict> Oh dear. We appear to be trying to inject a null EDID. Removing the CustomEDID and InjectEDID entries gets me booting. I'm not sure if this is a complete fix. I had troubles copying / merging the S/L/Displays/Overrides stuff when I was trying a 10.8 install, (and, in fact, haven't done it at all on this install) so I might be missing something obvious. But a null EDID screams "trouble" to me. Any idea how I'd go about generating a "proper" one? Simon