Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About philstopford

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. OK. Linux boots now with that (it's kind of involved and I miss the automatic detection of Clover). Windows fails to boot from OC, though. Clover works fine. Still digging into that.
  2. Jake, your EFI folder posted here worked beautifully, and I also managed to get Messages, etc. working under Catalina with this. Thanks. I needed something to ease the move to OpenCore. One thing I have noticed is that the Linux install on the same machine isn't automatically detected - OpenCore shows Windows and macOS only. Clover sees all 3. Is there a way to allow OpenCore to detect Linux installs, or is manual intervention needed? (This might be somewhat off-topic asking about OpenCore+Linux, but a 3-way boot on this machine has proved very useful up to now so I wanted to take the risk in
  3. I wondered whether it was possible to install some form of macOS on this machine. It has a Xeon X5690 in place of the original CPU, and an nVidia 750 card (which GPU-Z claims is fake - the card was picked up on eBay). 24 GB RAM, with the latest available BIOS from Dell (hence the Xeon CPU). Hardware-wise, this looks ~similar to the last 'cheesegrater' Mac Pro.
  4. To come back to this, I'm still confused about how the update should be applied. Given an existing EFI driver with -64 in the name, and the supposed update that misses the -64, is the best approach to have both drivers side-by-side, or should the replacement driver be renamed to match (or can I simply remove the -64 driver and put the old one in place). It looks like the -64 is a Clover convention, but not perhaps something that is used upstream. I'm puzzled.
  5. Updating Clover made no difference at all. EDIT : It seems that this might be intermittent, possibly provoked by moving the mouse cursor on the FileVault login screen. I'm investigating - sometimes, the trackpad is fine and other times it's not working; I haven't found the pattern yet.
  6. Curious - for me, updating to 10.14.5 causes my trackpad to stop working, both at the FileVault login and then in macOS itself. External USB mice (including dongled wireless) are working. CLOVER_working11.zip
  7. The Discord invite code appears to be expired. Is the Discord still active?
  8. I did recently install iStat Menus Pro (5.x) and the sensors list is empty. Is there a set of kexts that would sort this out?
  9. Thanks. I now have a new revision of the bootpack here that also seems to greatly reduce the time to display for the filevault 2 screen. Brightness keys aren't working, but the volume keys are functional (with the on-screen display). That has me rather confused. No joy with HDMI - machine locks up, also get a boot error screen if HDMI plugged in then CLOVER_working6.zip
  10. To be honest, I'm not exactly sure. It is somewhat of a combination of your bootpack and the archive from here : https://osxlatitude.com/forums/topic/11155-latitude-7480-install-mojave/ Some of the efi and kext packages were updated as well, to match current releases.
  11. So I ended up with the attached which gets me booting with FileVault 2 on my 7600U based E7480, but HDMI causes an instant lock-up and the display isn't responding to the special function keys (changing brightness, etc.). I was originally using Jake Lo's bootpack, but there I couldn't get the FileVault 2 login window to come up. I wondered if anything obvious stood out. clover_7480_fv2_r1.zip
  12. OK. This seems to work. I took Jake Lo's original bootpack and rolled in elements from https://osxlatitude.com/forums/topic/11155-latitude-7480-install-mojave/ clover_7480_fv2_r1.zip
  13. Not sure whether the attached might be useful. Still no joy in getting FileVault2 bootable. efi.zip
  • Create New...