Jump to content

skoon432

Members
  • Content Count

    13
  • Joined

  • Last visited

About skoon432

  • Rank
    InsanelyMac Protégé

Profile Information

  • Gender
    Male
  • Location
    NC, USA
  • Interests
    RF Engnear
  1. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Well this didn't take long at all! High Sierra is suffering the same problem as Yosemite. It tries to start and it simply stalls out. OSX is seeing something it doesn't like, period. At this point, I give up. Whatever is wrong is far beyond my scope of understanding but I still firmly believe the fault lies in a bad version of Clover. I'm convinced that it had some sort of very bad bug in this specific version and it totally trashed up the OSX partition in some weird way. Oh how I wished I had just left it all alone and not tried upgrading to a newer Clover release. A lesson learned and now its too late!
  2. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    tluck- I'll try an installation of High Sierra. I do have an untouched USB stick of that ready to go. If I have any sort of success, I'll let you know. Regarding a rollback to an earlier version of Clover.. There might be a way to do it from the Windows side but I'm far too much of a novice to know how to do that. I could roll back if I could get into OSX, but obviously that isn't happening at the moment Let me try an HS install and go from there. Thanks- Steve
  3. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Hi tluck- Are these drivers for a later macOS installation (10.12 or later) or are they meant for ANY Apple installation? Because I'm still using OSX 10.10 Yosemite. Not one of the later macOS versions. I'll verify what I have from this list you provided and attempt to install them from Clover assuming that's even possible. The thing I can't understand is that Win7 / OSX 10.10 dual boot was working perfectly until I attempted the Clover upgrade. After that, OSX boot was broke and nothing I do seems to fix it. I've been learning to live without it but it sure was a handy thing to use out in the field when I needed it. It has been sorely missed!
  4. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Hi all- I'm hoping for some advice. I own an X220 that I originally set up as a dual boot Win 7 and OSX Yosemite 10.10 via Clover bootloader. All had been working fine until dummy here decided to update Clover. The result was that it somehow trashed the OSX side (thankfully Win7 survived). Anyway, the OSX side has been inaccessible since June and I've been afraid to mess with it as I can't afford to hose up the Windows partition. The last Clover upgrade I attempted was 2.4k rev 4586. This is the one that hosed up OS X. If I force a verbose boot from clover and attempt to boot OSX, here is the result: I hope it can be seen well enough. Apologies for the smaller image as I didn't know how else to grab a shot of the erroneous boot sequence. This is as far as OSX goes before it stalls out and goes no further. Does anyone anywhere have a thought on this, or should I contact the Clover devs for additional support? I'm well out of my league of understanding things at this point. Thanks- Steve
  5. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    An update - I ended up losing everything installed on my X220. This was a crushing blow as I had important radio programming information some of which I was able to recover from a recovery/repair command window, but most got away from me. OSX was not as much of a loss but even so I had a number of working papers that is all lost. My entire episode started when I attempted to remove EmuVariable. That apparently is a VERY CRUCIAL item for the X220, perhaps something a bit different from the T420. I did attempt to reinstall the EmuVariable driver but the system had gone far too unstable at that point to recover. It was just like I had knocked its legs from underneath. It was over and that was it. So for you X220 users, beware from someone who had to learn the hard way. Leave the EmuVariable alone and don't touch! I have spent the past couple of days rebuilding the SSD and starting over from scratch. I'll get back to normal, it will just take time as it always does from a catastrophic crash such as this. Next time I keep my backups a bit closer to the vest Some brief installation notes with the X220 that I have encountered so far: 1) For a fresh rebuild, start with tluck's OSX build on an 8gb USB stick and follow his instructions. Be sure to include EmuVariable in the Clover driver installation procedure. 2) Using Disk Utility, make two hard drive partitions both GUID. Install OSX FIRST on the first partition. Install Win7 on the second partition. In fact, I found that I could simply leave the second partition as free space and let the Windows installer handle the partitioning itself. I tried installing Win7 on the first partition and it did NOT work. OSX refused to install. 3) Clover behaves strangely. It's a pain to manipulate on an X220 but once you get it going, it works fine. After both OSes are installed, go into BIOS and configure BOOT position #1 to be the SSD or your hard drive. That one took me a while to figure out and nearly drove me insane. What is so odd about all this is that I had to do none of this with the very first attempt from a couple of months ago with Mavericks. Clover versions have changed a lot since then and I wonder if bugs/issues etc have cropped up in it from those days, because my first attempt at any of this on the X220 was so amazingly simple. It simply worked, no fuss no muss. This time around, it has been literally days of utter misery and there has been no rhyme or reason for it. tluck, a question for you. How do I configure the Clover boot screen? It chose on its own to set OSX as the default OS and it also set itself to auto boot with a 5 second timer. How do I eliminate this? It's a huge headache and I don't know how to turn off that feature. Any thoughts?
  6. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Hi all- I am in need of some desperate help here. What used to be a perfectly working dual boot X220 has now turned into a big mess. I have been trying to recover from the removal of the EmuVariable-64.efi (does the X220 require this?) and my attempts of getting back to some level of normal use has now resulted in not only my Mavericks installation to be toast but now I cannot access my Windows 7 partition. That I must get back somehow. The partition isn't damaged, it's just that Clover doesn't see it for some reason. I did a fresh install of Mavericks and lost all my data on that build in an attempt to save the Windows partition. The only partition that Clover now sees is Mavericks and that's it. Question: Can someone please offer a URL or a help file or something that can explain in laymans terms how to get Clover to recognize a UEFI partition? If I can just retrieve Windows, I'll find a way to go back and deal with the OSX part of the equation later. Thanks!
  7. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Grrrrrrrrrrrrrrr........ This migration from EmuVariable just destroyed my perfectly working 10.9.5. I can no longer boot to OSX. This is NOT cool. I think we need some clearer instructions than the ones given.
  8. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    I'm using a DW1515 WiFi card in my Lenovo X220 with 100% success after the bios mod. This along with tluck's guide makes for an ideal hackintosh solution that WORKS. Very stable and reliable.
  9. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Hi all- I was able (with a little help) to get an F5521gw WWAN card to work "properly" in OSX as a reported WWAN card rather than a simple USB dial-up modem. I can offer the kext if anyone needs it. Also, I assume that upgrading to 10.9.4 is not a good idea. Would it trash the current build? My X220 still working like a champ. Best hack I've built to date.
  10. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Understood. I'll stick to a USB card reader as well.
  11. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    tluck (or anyone following this post)- Are you aware of any existing/modified VoodooSDHC.kext file that allows the card reader to work for the T420/X220? The reader is a model Ricoh R5C822.
  12. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    tluck- Success! This installation works 100% for the X220 Thinkpad including the battery manager. Compared to yesterday's repeated attempts which pretty much ate up most of my Saturday, today's new method had me up and running on the first build in under an hour! I am now wondering if my original installation attempts were somehow getting corrupted because when I started, the OS kept reporting that I was installing 10.9.3 via battery power which I knew I was not. This new installation method however supports battery management (and recognition) from the beginning of the installation. A couple of brief installation notes for what it is worth: 1) I did not have to install the E1000 ethernet kext separately with either the original installation or this new one. Networking worked fine immediately following the kext installations. 2) There is something not working (at least for me) regarding the SSDT generation script. It goes out to download the iasl tool from the 'net but so far all attempts have failed. Not sure if the path is broken..? Fortunately, I had already manually created my own ssdt.aml file several days ago while attempting another OSX build. If this script works for others, please advise as I am learning and would like to know what I'm doing wrong. If I come across anything else in question, I will post.. So far, very nice. My hats off to tluck for a very stable OSX build on our beloved Thinkpads!
  13. skoon432

    Lenovo ThinkPad T420 with UEFI Only

    Hi tluck- Would you please explain to dumb knuckles here how to install the custom DSDT in the OEM folder? I'm also using an X220 with amazing success, yet this is the only piece of the puzzle that I can't get to work and I've literally spent hours trying to figure out how to do this. I have an X in the battery bar icon. I did install ACPIBatteryManager.kext and it didn't fix the problem. Thanks much for your assistance. PS- I vote to abandon the OEM folder. Anything to make the process easier!
×