tluck Posted December 29, 2014 Share Posted December 29, 2014 @mircsisz do you have old zip version and log before 3094 - i.e. when it used to work? where was it getting this before you switched to use a custom entry method? Custom entry 0 FullTitle:"Windows 8.1" Path:"/EFI/WINDOWS/Boot/bootmgr.efi" Options:"-s -h" Type:7 Flags:0x0 matching all volumes also not sure about win 8 but the windows boot manager for me (win 7) is bootmgfw.efi not bootmgr.efi. have you tried my config.plist? Link to comment Share on other sites More sharing options...
mircsicz Posted December 29, 2014 Share Posted December 29, 2014 @tluck I don't have boot.log from older boot's but just created some, think I've most versions since 2967... Here's the config I use: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>DSDT</key> <dict> <key>Debug</key> <false/> <key>DropOEM_DSM</key> <dict> <key>ATI</key> <false/> <key>Firewire</key> <false/> <key>HDA</key> <false/> <key>HDMI</key> <false/> <key>IDE</key> <false/> <key>IntelGFX</key> <false/> <key>LAN</key> <false/> <key>LPC</key> <false/> <key>NVidia</key> <false/> <key>SATA</key> <false/> <key>SmBUS</key> <false/> <key>USB</key> <false/> <key>WIFI</key> <false/> </dict> <key>Fixes</key> <dict> <key>AddDTGP_0001</key> <true/> <key>AddHDMI_8000000</key> <true/> <key>AddIMEI_80000</key> <false/> <key>AddMCHC_0008</key> <false/> <key>AddPNLF_1000000</key> <true/> <key>DeleteUnused_400000</key> <true/> <key>FIX_ACST_4000000</key> <true/> <key>FIX_ADP1_800000</key> <false/> <key>FIX_INTELGFX_100000</key> <true/> <key>FIX_RTC_20000</key> <true/> <key>FIX_S3D_2000000</key> <true/> <key>FIX_TMR_40000</key> <true/> <key>FIX_WAK_200000</key> <false/> <key>FakeLPC_0020</key> <false/> <key>FixAirport_4000</key> <true/> <key>FixDarwin_0002</key> <true/> <key>FixDisplay_0100</key> <true/> <key>FixFirewire_0800</key> <false/> <key>FixHDA_8000</key> <true/> <key>FixHPET_0010</key> <false/> <key>FixIDE_0200</key> <false/> <key>FixIPIC_0040</key> <true/> <key>FixLAN_2000</key> <true/> <key>FixRegions_10000000</key> <true/> <key>FixSATA_0400</key> <false/> <key>FixSBUS_0080</key> <true/> <key>FixShutdown_0004</key> <false/> <key>FixUSB_1000</key> <true/> <key>NewWay_80000000</key> <true/> </dict> <key>Name</key> <string>DSDT.aml</string> </dict> <key>DropTables</key> <array> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>Cpu0Ist</string> </dict> <dict> <key>Signature</key> <string>SSDT</string> <key>TableId</key> <string>CpuPm</string> </dict> <dict> <key>Signature</key> <string>DMAR</string> </dict> <dict> <key>Signature</key> <string>MCFG</string> </dict> </array> <key>ResetAddress</key> <string>0x0CF9</string> <key>ResetValue</key> <string>0x06</string> <key>SSDT</key> <dict> <key>Generate</key> <dict> <key>CStates</key> <true/> <key>PStates</key> <true/> </dict> </dict> </dict> <key>Boot</key> <dict> <key>Arguments</key> <string>slide=0 kext-dev-mode=1</string> <key>CustomLogo</key> <false/> <key>DefaultVolume</key> <string>MacOS</string> <key>Fast</key> <false/> <key>IgnoreNVRAMBoot</key> <true/> <key>Log</key> <false/> <key>Timeout</key> <integer>2</integer> <key>UseAlternateLogo</key> <true/> <key>XMPDetection</key> <false/> </dict> <key>Devices</key> <dict> <key>Audio</key> <dict> <key>Inject</key> <string>12</string> </dict> <key>Inject</key> <false/> <key>USB</key> <dict> <key>AddClockID</key> <true/> <key>FixOwnership</key> <true/> <key>HighCurrent</key> <true/> <key>Inject</key> <false/> </dict> <key>UseIntelHDMI</key> <true/> </dict> <key>GUI</key> <dict> <key>Hide</key> <array> <string>Windows</string> </array> <key>Mouse</key> <dict> <key>DoubleClick</key> <integer>500</integer> <key>Enabled</key> <true/> <key>Speed</key> <integer>8</integer> </dict> <key>Scan</key> <dict> <key>Entries</key> <true/> <key>Legacy</key> <false/> <key>Tool</key> <true/> </dict> <key>ScreenResolution</key> <string>960x600</string> <key>Theme</key> <string>ThinkPad</string> </dict> <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> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> <key>AsusAICPUPM</key> <true/> <key>Debug</key> <false/> <key>KextsToPatch</key> <array> <dict> <key>Comment</key> <string>change AD198B for Conexant 20672</string> <key>Find</key> <data> ixnUEQ== </data> <key>Name</key> <string>AppleHDA</string> <key>Replace</key> <data> blDxFA== </data> </dict> <dict> <key>Comment</key> <string>Replace 4th port with VGA</string> <key>Find</key> <data> AQIEABAHAAAQBwAABQMAAAIAAAAwAAAAAgUAAAAEAAAH AAAAAwQAAAAEAAAJAAAABAYAAAAEAAAJAAAA </data> <key>Name</key> <string>AppleIntelSNBGraphicsFB</string> <key>Replace</key> <data> AQIEABAHAAAQBwAABQMAAAIAAAAwAAAAAgUAAAAEAAAH AAAAAwQAAAAEAAAJAAAABgIAABAAAAAJAAAA </data> </dict> <dict> <key>Comment</key> <string>TRIM for SSD</string> <key>Find</key> <data> QVBQTEUgU1NE </data> <key>Name</key> <string>IOAHCIBlockStorage</string> <key>Replace</key> <data> AAAAAAAAAAAA </data> </dict> </array> </dict> <key>SMBIOS</key> <dict> <key>BoardVersion</key> <string>MacBookPro8,1</string> <key>Mobile</key> <true/> <key>ProductName</key> <string>MacBookPro8,1</string> <key>Trust</key> <true/> </dict> <key>RtVariables</key> <dict> <key>MLB</key> <string>C0335550lsadjlöfdk5A3</string> <key>ROM</key> <data> AxxxxKvA== </data> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Detect</string> <key>InjectSystemID</key> <true/> </dict> </dict> </plist> Except from DefaultVolume, Timeout and MLB&ROM it's your config1600x900.plist. It's the one that worked for me from the beginning of my OSx86 Setup on my T420s... Here's the 2967 boot.log http://paste.debian.net/138545/ 2988 boot.log http://paste.debian.net/138546/ 3025 boot.log http://paste.debian.net/138549/ 3048 boot.log http://paste.debian.net/138551/ 3094 boot.log http://paste.debian.net/138552/ and 3097 boot.log http://paste.debian.net/138553/ All tested with the config.plist from above... Link to comment Share on other sites More sharing options...
tluck Posted December 30, 2014 Share Posted December 30, 2014 mircsizc well that must be an older config.plist - but the output looks different - and ok. no weird stuff around custom entries. so remove the hide windows thing or get the latest config.plist and you should be seeing all your bootable partitions. Link to comment Share on other sites More sharing options...
dauren Posted December 30, 2014 Share Posted December 30, 2014 Hello, I'm happily running my hackintosh for over a month now and finally decided to add a second display, Dell 2414H. I'm using DP-DP connection and OS doesn't see the display.I'm running 1600x900 plist with HD3000 only enabled, OSX 10.10.1. and Clover v3025. What should I check? Link to comment Share on other sites More sharing options...
tluck Posted December 30, 2014 Share Posted December 30, 2014 @all - i reposted a new bundle with clover r3108 - the change is I recompiled it to remove (annoying) text before the GUI. @dauren - hmm not sure. you should have DP buffer/port available? are you using the zip/config.plist from my guide? can it find it on cold boot up? if you look at the kexts do you see these kexts $ kextstat|grep -i grap 77 15 0xffffff7f812ea000 0x47000 0x47000 com.apple.iokit.IOGraphicsFamily (2.4.1) <12 7 5 4 3 1> 78 0 0xffffff7f81bea000 0x2e000 0x2e000 com.apple.driver.AppleIntelSNBGraphicsFB (10.0.0) <77 12 11 7 6 5 4 3 1> 80 0 0xffffff7f81c77000 0x67000 0x67000 com.apple.driver.AppleIntelHD3000Graphics (10.0.0) <77 12 7 5 4 3 1> 97 2 0xffffff7f82011000 0x3000 0x3000 com.apple.driver.AppleGraphicsControl (3.7.21) <77 12 11 7 5 4 3 1> 119 1 0xffffff7f81ff0000 0x6000 0x6000 com.apple.AppleGraphicsDeviceControl (3.7.21) <7 6 5 4 3 1> you could dump out registry (run: ioreg -l) and and there should be 4 frame buffers. this with LCD and external monitor on my DP (left side). $ ioreg -l |grep AppleIntelF|grep -v IOK | | | | "attached-gpu-control-path" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/AGPM" | | | +-o AppleIntelFramebuffer@0 <class AppleIntelFramebuffer, id 0x1000002ea, registered, matched, active, busy 0 (18 ms), retain 18> | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-30e4-2e2" | | | +-o AppleIntelFramebuffer@1 <class AppleIntelFramebuffer, id 0x1000002eb, registered, matched, active, busy 0 (48 ms), retain 17> | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@1/display0/AppleDisplay-22f0-2869" | | | +-o AppleIntelFramebuffer@2 <class AppleIntelFramebuffer, id 0x1000002ec, registered, matched, active, busy 0 (43 ms), retain 16> | | | +-o AppleIntelFramebuffer@3 <class AppleIntelFramebuffer, id 0x1000002ed, registered, matched, active, busy 0 (26 ms), retain 15> 1 Link to comment Share on other sites More sharing options...
dreddtech Posted January 1, 2015 Share Posted January 1, 2015 I have followed this guide 100%, but my audio is not working. Everything else is working.. What am I missing? I have a t420 with Conexant 20672. Is there something extra I am meant to do that isnt in the guide? Link to comment Share on other sites More sharing options...
Tetonne Posted January 1, 2015 Share Posted January 1, 2015 I have followed this guide 100%, but my audio is not working. Everything else is working.. What am I missing? I have a t420 with Conexant 20672. Is there something extra I am meant to do that isnt in the guide? the expert is tluck but i would add again all the kext in /S/L/E use Kext Utility again reboot it shoud work Happy new year to all Link to comment Share on other sites More sharing options...
tluck Posted January 1, 2015 Share Posted January 1, 2015 @dreddtech welcome to the club! key factors for the AppleHDA_20672.kext: is that the file Contents/MacOS/AppleHDA is symbolic link to the native binary. which means you keep the original version in place. you can check that from the command line. and the kext must be installed in /S/L/E versus left in the /EFI partition. $ cd /System/Library/Extensions/AppleHDA_20672.kext/Contents/MacOS $ ls -l total 8 lrwxr-xr-x 1 root wheel 64 Dec 24 16:50 AppleHDA -> /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA Link to comment Share on other sites More sharing options...
dreddtech Posted January 2, 2015 Share Posted January 2, 2015 @dreddtech welcome to the club! key factors for the AppleHDA_20672.kext: is that the file Contents/MacOS/AppleHDA is symbolic link to the native binary. which means you keep the original version in place. you can check that from the command line. and the kext must be installed in /S/L/E versus left in the /EFI partition. $ cd /System/Library/Extensions/AppleHDA_20672.kext/Contents/MacOS $ ls -l total 8 lrwxr-xr-x 1 root wheel 64 Dec 24 16:50 AppleHDA -> /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA Just to confirm, I am meant to copy all the kexts you provided to S/L/E then run them through kext utility? Do I still keep them in the clover folder? Link to comment Share on other sites More sharing options...
tluck Posted January 2, 2015 Share Posted January 2, 2015 yes. to make a copy in /S/L/E drag them all onto the Kext Utility. (refer to the post OS install section of the guide) Link to comment Share on other sites More sharing options...
walid-wah Posted January 2, 2015 Share Posted January 2, 2015 I did all the steps and everything work perfectly! but what about the wifi?Is there anyway to get the wifi working or i must use external wifi adapter? Link to comment Share on other sites More sharing options...
dreddtech Posted January 2, 2015 Share Posted January 2, 2015 Ok so my audio still isn't working.. But after running that cmd you advised tluck it looks like the symbolic link isnt working. What would cause this? Link to comment Share on other sites More sharing options...
tluck Posted January 3, 2015 Share Posted January 3, 2015 @walid-wah the built-in intel wifi will not work. you need to replace it with a OSX-compatible chip/card. there are a number of broadcom or atheros options. or you can get a USB version. @dreddtech well you can make a new symbolic link and then rebuild the caches. do this: cd /System/Library/Extensions/AppleHDA_20672.kext/Contents/MacOS sudo rm AppleHDA sudo ln -s /System/Library/Extensions/AppleHDA.kext/Contents/MacOS/AppleHDA sudo touch /System/Library/Extensions 1 Link to comment Share on other sites More sharing options...
dreddtech Posted January 3, 2015 Share Posted January 3, 2015 Sound is now working Cheers tluck. Link to comment Share on other sites More sharing options...
dauren Posted January 4, 2015 Share Posted January 4, 2015 @all - i reposted a new bundle with clover r3108 - the change is I recompiled it to remove (annoying) text before the GUI. @dauren - hmm not sure. you should have DP buffer/port available? are you using the zip/config.plist from my guide? can it find it on cold boot up? if you look at the kexts do you see these kexts $ kextstat|grep -i grap 77 15 0xffffff7f812ea000 0x47000 0x47000 com.apple.iokit.IOGraphicsFamily (2.4.1) <12 7 5 4 3 1> 78 0 0xffffff7f81bea000 0x2e000 0x2e000 com.apple.driver.AppleIntelSNBGraphicsFB (10.0.0) <77 12 11 7 6 5 4 3 1> 80 0 0xffffff7f81c77000 0x67000 0x67000 com.apple.driver.AppleIntelHD3000Graphics (10.0.0) <77 12 7 5 4 3 1> 97 2 0xffffff7f82011000 0x3000 0x3000 com.apple.driver.AppleGraphicsControl (3.7.21) <77 12 11 7 5 4 3 1> 119 1 0xffffff7f81ff0000 0x6000 0x6000 com.apple.AppleGraphicsDeviceControl (3.7.21) <7 6 5 4 3 1> you could dump out registry (run: ioreg -l) and and there should be 4 frame buffers. this with LCD and external monitor on my DP (left side). $ ioreg -l |grep AppleIntelF|grep -v IOK | | | | "attached-gpu-control-path" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/AGPM" | | | +-o AppleIntelFramebuffer@0 <class AppleIntelFramebuffer, id 0x1000002ea, registered, matched, active, busy 0 (18 ms), retain 18> | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-30e4-2e2" | | | +-o AppleIntelFramebuffer@1 <class AppleIntelFramebuffer, id 0x1000002eb, registered, matched, active, busy 0 (48 ms), retain 17> | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@1/display0/AppleDisplay-22f0-2869" | | | +-o AppleIntelFramebuffer@2 <class AppleIntelFramebuffer, id 0x1000002ec, registered, matched, active, busy 0 (43 ms), retain 16> | | | +-o AppleIntelFramebuffer@3 <class AppleIntelFramebuffer, id 0x1000002ed, registered, matched, active, busy 0 (26 ms), retain 15> Sorry for a late reply, holidays Yes I am using your config from zip file. Also tried to connect from dock station with same negative result. Here is the output: dauren@dmbp:~$kextstat|grep -i grap 73 15 0xffffff7f8141e000 0x47000 0x47000 com.apple.iokit.IOGraphicsFamily (2.4.1) <12 7 5 4 3 1> 74 0 0xffffff7f82051000 0x2e000 0x2e000 com.apple.driver.AppleIntelSNBGraphicsFB (10.0.0) <73 12 11 7 6 5 4 3 1> 82 0 0xffffff7f820de000 0x67000 0x67000 com.apple.driver.AppleIntelHD3000Graphics (10.0.0) <73 12 7 5 4 3 1> 110 2 0xffffff7f82478000 0x3000 0x3000 com.apple.driver.AppleGraphicsControl (3.7.21) <73 12 11 7 5 4 3 1> 118 1 0xffffff7f82457000 0x6000 0x6000 com.apple.AppleGraphicsDeviceControl (3.7.21) <7 6 5 4 3 1> dauren@dmbp:~$ioreg -l |grep AppleIntelF|grep -v IOK | | | | "attached-gpu-control-path" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/AGPM" | | | +-o AppleIntelFramebuffer@0 <class AppleIntelFramebuffer, id 0x1000002bc, registered, matched, active, busy 0 (19 ms), retain 19> | | | | | "IODisplayPrefsKey" = "IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/IGPU@2/AppleIntelFramebuffer@0/display0/AppleBacklightDisplay-30e4-2e2" | | | +-o AppleIntelFramebuffer@1 <class AppleIntelFramebuffer, id 0x1000002bd, registered, matched, active, busy 0 (16 ms), retain 15> | | | +-o AppleIntelFramebuffer@2 <class AppleIntelFramebuffer, id 0x1000002be, registered, matched, active, busy 0 (16 ms), retain 15> | | | +-o AppleIntelFramebuffer@3 <class AppleIntelFramebuffer, id 0x1000002bf, registered, matched, active, busy 0 (16 ms), retain 15> Link to comment Share on other sites More sharing options...
OneMore Posted January 4, 2015 Share Posted January 4, 2015 (edited) Hello everyone, One more T420 user here, trying to make it to run Yosemite as the primary and maybe the only OS. My model is 4236AT9 which is the same as tluck's (btw THANKS MAN for your amazing work here!!! This is an example of dedication and community support for all of us!). Given the above, I hoped for an easy walkthrough, but guess what... kicking the tires for the 3rd day already. May I ask for some help? I believe the cause of my pain is that I only have access to old MacMini running Snow Leo (10.6.8), though probably my lame hands and lack of expertise exacerbate that ;-) Long story short... I transferred a 10.10 image to my Mac Mini, createinstallmedia failed with "incorrect CPU type" error (which didn't surprise me), but unfortunately Clover_v2_r1625.pkg failed as well. Fortunately, a Mountain Lion Install Disk Build Tool (found in another thread here) supports Yosemite now, so I was able to run it on my Snow Leo. And Clover_v2k_r3113.pkg works as well, though I am not sure if I need to use it on Yosemite install disk prepared with above tool... I followed the guide where I could (upgraded BIOS, switched to UEFI, disabled virtualization, put the contents of T420/EFI dir to manually mounted ESP of USB partition, renamed ACPI.1600x900 to ACPI, etc... Here is where things stand now: The USB boots to Clover in UEFI mode, there's a ThinkPad theme, and I can get to options and shell and such, but when I kick "Boot Mac OS X from Yosemite Install Disk - 10.10", I get an apple logo for like 25 sec., and then the laptop reboots. My semi-educated guess is that I need to put some pieces in place, that are normally put by either Clover_v2_r1625.pkg or createinstallmedia. Can I still get through without running these two? Thanks, Me. Update: I followed this guide to manually create install image. So maybe my question is just about where to put the remaining kexts, DSDTs, AMLs and other small pieces that I have very vague understanding of. Or, to realize that I am heading in a totally wrong direction. Edited January 4, 2015 by OneMore Link to comment Share on other sites More sharing options...
tluck Posted January 4, 2015 Share Posted January 4, 2015 @dauren - no idea - does this same cable work with windows to the external monitor? @OneMore so you still struggling with making the Yosemite installer? I presume you have downloaded a proper Yosemite version (installer) from AppStore? so you have /Applications/Install OS X Yosemite.app for 10.10.1 it will installer version 1.6.7 I take it that you cannot use the built-in (creatinstallmedia) method because the macMini is not yosemite compatible? then perhaps try the more recent version of Lion Disk maker. http://diskmakerx.com - which is yosemite capable and can run on 10.6.8. once you get the bits onto the USB (format the USB GUID/GPT formatted) then you can replace the /EFI partition with the same zip. the Diskmaker process will erase the disk and put all the installation bits onto the 2nd partition. once this is done, follow my guide at Part 1 installation common steps. Link to comment Share on other sites More sharing options...
OneMore Posted January 5, 2015 Share Posted January 5, 2015 (edited) @tluck Thanks for chiming in! Sorry, yes, still there... And yes, I used the same latest Disk Maker X 4b4, rebooted/re-ran again, now in the end of the build process I noticed an error (attaching screen)... Now checked the FAQ section on diskmakerx and found the following: I can’t use DiskMaker X with Mac OS X 10.6.x if I try to use it with my Mavericks installer! Because of a bug (or a feature?) in Apple’s built-in command createinstallmedia with 10.6.X, DiskMaker X is not compatible with versions of OS X prior to 10.7. I’m working on a fix, but it may take some time to make it available as it means using another completely different method. So now I am not even sure if it supposed to work on my MacMini, even though it launches and does the job for the most part (or so it looks like). Regardless... Is there a way to validate my newly built install disk, at least for most common user/environment errors? Or to collect some info on what's going on before ThinkPad reboots trying to launch the installer - like enable diag output instead of apple logo? In lieu of better options, attaching the filelists from this USB. Maybe something looks not as expected and can be fixed by simple file manipulation? MyUSB-AllFiles.zip Truth be told, I have quite marginal Mac exposure (hope to make it better with this exercise), and my Win / Linux experience is almost 10 years behind the time, so the gut feeling is I may be missing something so trivial that it's not even mentioned. Like... should I have created partitions on the USB stick, after switching to GPT? Especially keeping in mind case sensitive filesystem or otherwise? Can existing HDD layout on the T420 be a problem? (I didn't kill a few Linux partitions there yet). Thanks again, Me Edited January 5, 2015 by OneMore Link to comment Share on other sites More sharing options...
tluck Posted January 5, 2015 Share Posted January 5, 2015 @OneMore things seem to be pretty much as they should be from the USB standpoint. when you boot up and land on the Clover GUI, you can hit the space bar to then boot with options. boot the OSX Installer with verbose to see where it goes. or stops. it may take 5 minutes or so boot up. However, there is alternate manual way to make an installer from OSX - i just tested on Yosemite 10.10.1 and it worked just fine. on your Mac mini... 1) format an 8GB USB as GUID with 1 partition HFS - which makes EFI partition as well. 2) follow the "dev method' in this link: this guide Note: I renamed the USB copy of "OS X Base System" to "Installer" (to make it more obvious in Clover) when it finished copying everything to it. 3) mount the ESP and then copy the zip contents - the full EFI folder set to the ESP. 4) rename ACPI.1600x900 to ACPI 5) rename config.1600x900.plist to config.plist then reboot and hit F12 to select boot from USB select Installer - you can hit space to boot verbose - but otherwise the Installer booted for me. Link to comment Share on other sites More sharing options...
juniorprofi Posted January 5, 2015 Share Posted January 5, 2015 Hey everybody, trying to install Windows 7 on my t420 from a DVD I created by downloading the Windows 7 installer. Strangly the installer tells me that I can't install on a particular partition because it's MBR, but it is GUID in fact. I want to install on disk1s4 partition. Any ideas? Thanks, juniorprofi /dev/disk0 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *120.0 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_HFS SSD 119.7 GB disk0s2/dev/disk1 #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *1.0 TB disk1 1: EFI EFI 209.7 MB disk1s1 2: Apple_HFS Pladde 899.7 GB disk1s2 3: Apple_Boot Recovery HD 650.0 MB disk1s3 4: Microsoft Basic Data 99.7 GB disk1s4/dev/disk2 #: TYPE NAME SIZE IDENTIFIER 0: GSP1RMCPRXFRER_DE_DVD *3.3 GB disk2 Link to comment Share on other sites More sharing options...
Sheep_Reaper Posted January 5, 2015 Share Posted January 5, 2015 Re-make your win7 installation using Rufus. Select gpt for uefi computers when making it. Make sure your Iso is 64bit. And you may have issues if the image is x86 x64 multi Link to comment Share on other sites More sharing options...
tluck Posted January 5, 2015 Share Posted January 5, 2015 @juniorprofi if you created the NTFS partition with Disk Utility it will have converted your GUID disk with a PMBR to one with MBR. this confuses the windows installer. search this forum for PMBR - i have gone over this many times! Note: i suppose i will add it the GUIDE - of what NOT to do - when dual booting windows. gdisk can fix this - i.e. get rid of the MBR. Here is a script I used recently to clone my HD when it was failing. the script makes 4 partitions. EFI OSX Recovery HD Windows (NTFS) you can decide how big to make your OSX vs Windows partitions but this was on a 750GB drive. it is roughly a ~48GiB windows partition. see list at the end. if one already has the first 3 sections and there is enough space on the disk (or one can shrink the OSX and add free space if needed) then one can use the partition 4 section below to add a Windows partition that is UEFI/hackintosh compatible. the script is meant to be run as root: save the lines below into a file for example make_disk.bash edit all the size parameters to match your case suppose disk1 is the one you want to (re)partition then run by: sudo make_disk.bash disk1 if you want to just add a 4th partition then put the section 4 in a script (and fix the sizes) #!/bin/bash # use gtp to add windows partition - to keep PMBR # partition 1 EFI diskutil unmountDisk $1 sleep 3 gpt add -s 409600 -t C12A7328-F81F-11D2-BA4B-00A0C93EC93B $1 sleep 3 diskutil unmountDisk $1 gpt label -i 1 -l "EFI" $1 sleep 3 # partition 2 OSX diskutil unmountDisk $1 sleep 3 gpt add -s 1362786480 -t 48465300-0000-11AA-AA11-00306543ECAC $1 sleep 3 diskutil unmountDisk $1 gpt label -i 2 -l "OSX" $1 sleep 3 # partition 3 Recovery HD diskutil unmountDisk $1 sleep 3 gpt add -s 1269544 -t 426F6F74-0000-11AA-AA11-00306543ECAC $1 sleep 3 diskutil unmountDisk $1 gpt label -i 3 -l "Recovery HD" $1 sleep 3 # partition 4 NTFS diskutil unmountDisk $1 sleep 3 gpt add -s 100681728 -t EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 $1 sleep 3 diskutil unmountDisk $1 gpt label -i 4 -l "Windows" $1 sleep 3 diskutil unmountDisk $1 gpt -r show $1 exit # #$ gpt -r show disk1 # start size index contents # 0 1 PMBR # 1 1 Pri GPT header # 2 32 Pri GPT table # 34 6 # 40 409600 1 GPT part - C12A7328-F81F-11D2-BA4B-00A0C93EC93B # 409640 1362786480 2 GPT part - 48465300-0000-11AA-AA11-00306543ECAC # 1363196120 1269544 3 GPT part - 426F6F74-0000-11AA-AA11-00306543ECAC # 1364465664 100681728 4 GPT part - EBD0A0A2-B9E5-4433-87C0-68B6B72699C7 # 1465147392 1743 # 1465149135 32 Sec GPT table # 1465149167 1 Sec GPT header Link to comment Share on other sites More sharing options...
OneMore Posted January 6, 2015 Share Posted January 6, 2015 (edited) @tluck Thanks for your efforts, but sorry, no cigar - I am still stuck in mud, kicking tires, slamming doors and flashing the headlights. And the idea of voodoo dances doesn't seem too weird already... The dev method you referred to is exactly what I did last time, so now I tried to do better and rule out a few 'suspects' with the following: - I found someone with a Mac (Lion) who allowed me to play on their system a little bit, so I could re-download Yosemite from the app store, and run the creatinstallmedia in a standard/easy way (command line). - And I tried to boot the installer in all different modes, thanks to your hint (verbose, single user, safe, no cache/kexts etc), but with exactly same result: machine goes to reboot in a few seconds (or immediately, depend on option selected), after local hard drive is detected. Or so I interpret the output, see picture attached. - To rule out anything HDD related, I swapped it with a 25GB drive from some ancient ThinkPad. This drive has just one empty NTFS partition. I can even zero it out, if that can make a difference. Still no progress, but now once we have installer and HDD 'cleared', the next suspects are hardware/firmware guts, nuts and bolts, correct? This laptop was used to run various Linuxes before, and I just confirmed it boots to Windows 8 PE x32 and x64 live CD (this is how I flashed the BIOS). I don't see reason to suspect odd ACPI config, or faulty hardware, or custom flashing. The machine is not secured/locked in any way that I could identify, no system/disk passwords etc. So, can we confirm these two things: 1. Should I have unpacked all contents of T420_UEFI-Clover-b3108_10.9_10.10_2014-12-30.zip to ESP-USB partition completely, or just EFI directory, as I did (renaming two 1600x900 items of course)?(for example, this ":System:Library:Displays:Overrides/" directory looks quite fancy, never seen anything like that... No need for it to be on USB? Just curious...) 2. I upgraded the BIOS to "stock" 1.46 as your guide suggests, but did not flash the whitelisted one (the link in patchers' forum is broken, and I didn't find another copy - maybe someone here has it), and same about DSDT and such, I didn't do anything like that. Could it make a difference? That's what I could think of and try at the moment. Knowing that we have 100% identical machines makes this situation look a bit crazy. What could I possibly do wrong there??? Thx, Me Edited January 6, 2015 by OneMore Link to comment Share on other sites More sharing options...
tluck Posted January 6, 2015 Share Posted January 6, 2015 @OneMore. well you have made the installer. and added the entire EFI folder (just need the EFI folder for the USB) onto the ESP. that's done. and it looks like its trying to load from the USB. what size USB is this? did you try different USB ports? very odd as you say. we have the same system. it must be a system BIOS setting. you have v1.46 so good. did you reset to defaults? BIOS settings: - disable VT-d - SATA set AHCI mode - Enable Execution Bit Link to comment Share on other sites More sharing options...
OneMore Posted January 6, 2015 Share Posted January 6, 2015 @tluck Yes, I tried all 4 USB ports. The flash is PNY 8Gb, never had problems with it. VT-d disabled, Virtualization enabled, SATA set to AHCI, everything else reset to defaults multiple times. Execution bit... I do not see this language in BIOS setup, do you mean Security / Memory Protection / Execution Prevention? This is set to "disabled" (default) which I believe is the same meaning. Do you have patched / un-whitelisted BIOS 1.46? Thx, Me Link to comment Share on other sites More sharing options...
Recommended Posts