Jump to content

mrjayviper

Members
  • Content Count

    324
  • Joined

  • Last visited

About mrjayviper

  • Rank
    InsanelyMac Sage

Profile Information

  • Gender
    Male

Recent Profile Visitors

4,343 profile views
  1. So I have enabled -v on my clover config.plist but it's too fast to see the messages. Basically, I'm getting a boot loop and wants to see what's causing it. Thanks!
  2. mrjayviper

    WhatEverGreen Support Topic

    I'm on 10.13.6 on MacPro5.1 SYMBIOS. 1. to get sound working on NvidiaGraphicsFixup, I only need Lilu+NvidiaGraphicsFixup. When using WhateverGreen, I need Lilu+WhateverGreen+AppleALC. Is this normal? 2. Is it possible to change the "GFX" assigned to the video card? it's originally S3F0. With WhateverGreen, it shows up as GFX0. Can I change it to GFX2? Thanks a lot!
  3. mrjayviper

    WhatEverGreen Support Topic

    currently using High Sierra 10.13.6 with latest security patch. I'm also using built-in Nvidia (GTX770) drivers. I'm currently using lilu.kext (version 1.2.3) + NvidiaGraphicsFixup.kext (1.2.6) and this is working fine. When I decided to use the latest lilu.kext (1.2.8) +WhateverGreen.kext (1.2.4), I get boot loop. Any ideas on how to debug/fix this? Currently the only fix that I know that works is to revert to using the older version of lilu.kext and using NvidiaGraphicsFixup. Thanks
  4. mrjayviper

    Clover General discussion

    what would be the recommended clover version for those still in High Sierra. Recent discussions seems specific to Mojave so it's possible those clover versions are not suitable for <10.14? Thanks
  5. For me, black screen often happens after verbose portion (boot flag -v in clover config.plist) of boot and before the Apple logo with horizontal progress bar shows up. The display would go to sleep (says entering entering sleep mode) on it "own". Things I've tried: 1. MacPro6,1 + DP cable: permanent black screen unless I use Lilu+NvidiaGraphicsFix. Even then, I still often get black screen. 2. MacPro5,1 + DP cable: No need to use Lilu+NvidiaGraphicsFix but still intermittent black screen. I've also tried using an injected GFX1 SSDT file(see attachment) . same results. 3. MacPro5,1 + DVI cable: no black screen so far but I've only been using it for the last 4 hours! I've also tried using an injected GFX1 SSDT file. But it seems it doesn't matter if I'm using one or not for DVI. In saying that, it would be great if I can use a display cable that can carry audio signal as well. I've been using a cheap USB audio card but it produces an annoying pop during startup and shutdown. setup in my sig. Thanks! Note: I haven't tried MacPro6,1 + DVI. I have yet to try HDMI on any SMBIOS configuration. I'll be doing that tomorrow. SSDT(GFX).zip
  6. mrjayviper

    Clover General discussion

    another question please. If I don't need something to show up (or scanned), I can delete the EFI driver. correct? example: I don't want the Windows OS/data partitions to be shown/scanned so I can delete and NTFS driver. Or in Linux case, I can delete any of the extX drivers. Thanks
  7. mrjayviper

    Clover General discussion

    How can I disable scanning of entries during clover boot? I've tried the settings on the screenshot and Auto=Yes (which disables all the checkboxes inside the scan section) but it's still happening. Thanks
  8. mrjayviper

    Clover General discussion

    edited.....
  9. mrjayviper

    Clover General discussion

    Is this the right place to talk about compiling and other developer talk? Seems it's more appropriate to talk about that in the clover development section. And leave the "normal" clover users to this thread?
  10. mrjayviper

    Clover General discussion

    TLDR: (10.13.x) HFSplus can't detect any drives (including the USB stick OSX installer) on UEFI booting when I installed an older firmware on motherboard. VboxHFS+ works on UEFI boot. But I have experienced bootloop issues when I use VboxHFs + 4+TB HFS+ raid array but on legacy boot. No issues with HFSplus when using legacy booting. I can use a legacy boot USB installer to install OSX but the HDD have the same issues when using UEFI boot. --------------------- A month ago I updated the firmware (2018 version) on my Intel board and I got UEFI booting working. Clover+HFSplus.efi can detect my USB and the single HDD. I also have no bootloop issues when it comes to using a 4+TB HFS+ raid array. Because of other weird boot issues which I thought we're due to OSX, I moved back to Windows. But the weird boot issues area still present so I put back an older version (2017) of the firmware and from what I can see, my boot issues on Windows have disappeared. I decided to try OSX again last night. The problem is that when UEFi booting, HFSplus.efi can't detect any drives including the USB stick. I used VboxHFS just several hours ago, no issues with detecting drives. But when I was testing OSX last month and was using VBoxHFS on legacy boot, I get bootloop issues when I have 4+TB HFS+ raid array. I tried smaller raid array like 2x 80GB and I don't get any bootloop with that. My educated guess is that VboxHFS starts to get issues with raid arrays as the size increases. Any ideas on how to: 1. Continue using HFSplus but using UEFI 2. OR use VbosHFS but no bootloop on raid arrays Thanks
  11. mrjayviper

    Clover problems report & features request

    I created a UEFI USB installer and my UEFI setup cannot boot using it. I tried a UEFI Ubuntu USB installer and that works fine. I inspected both sticks using the motherboard EFI shell and I can see that the EFI folder created by clover doesn't have the attribute of D (D for directory) hence the motherboard firmware cannot see the bootloader. The fix I had to do is to run these commands inside motherboard EFI shell: 1. fsX: (change to correct location of the USB stick) 2. attrib * (to display all the attributes of files/folders. The EFI folder has no D attribute at this point. It does does the archive attribute set. The other OSX system folders like .FSxxx have one) 3. attrib -a EFI (strips the EFI of its attributes. for some reason this also creates a new file called EFI) 4. del EFI (deletes the EFI file) 5. attrib * (to display the attributes again and this time the EFI folder has a D attribute) Can this be fix by Clover? Thanks!
  12. mrjayviper

    Clover General discussion

    Removed
  13. mrjayviper

    Clover General discussion

    Perhaps those without UEFI will care?
  14. Just a question: Seems this guide is for creating a legacy booting not UEFI? I asked since: 1. I downloaded the clover install.zip and it contains a driver64 folder 2. It doesn't tell what options to select during Clover installation. Some installation options are disabled once i select UEFI. Basically I'm trying to get UEFI to boot using a USB installer and somehow it's not working. I believe my board (see sig) supports UEFI since I run the Ubuntu USB installer using the UEFI bootable device option. Plus after installing Ubuntu, I get a "UEFI:ubuntu" in my bootable devices list. Thanks
  15. mrjayviper

    Clover General discussion

    I followed whatever is in the guide that I linked. I've only tried high Sierra and using GPT. After installing clover with UEFI option, I have an EFI volume. I followed whatever is in the guide that I linked. I've only tried high Sierra and using GPT. After installing clover with UEFI option, I have an EFI volume. ----- I think this is not allowed but I also created an UEFI USB installer using uni_beast for high Sierra.
×