Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

Zenith432
Zenith432
Posted
Posted

Is it possible That new efi driver like Optiofix3 or Aptiofixmemory changed this behavior?

Or it is unrelated?

E2H 226 MSR_PKG_CST_CONFIG_ CONTROL C-State Configuration Control (R/W)

15 CFG Lock (R/WO) When set, lock bits 15:0 of this register until next reset.

Make macOS great again!

Steve Jobs in response: macOS is already great!

Bill Gates in response: macOS was never great!

  • Like 7
maxb2000
maxb2000
Posted
Posted

I know that this isn't the right thread but I can't post into UEFI section so please forgive me :D


These Gigabyte guys made a BIOS file that's rubbish to say at least. If I want to unlock secret menus I can't because the program crashes (AMIBCP) if I want to patch it using UEFIPatch says nothing to patch.


What's wrong ?


Here is the BIOS file:


http://download.gigabyte.eu/FileList/BIOS/mb_bios_ga-b85m-d2v_f4.zip


It's a gigabyte board GA-B85M-D2V.


Guest
Guest
Posted
Posted

this clover log answer clearly at my previous answer:

 

0:104  0:000  BrandString = Intel® Xeon® CPU E5-2696 v4 @ 2.20GHz

0:104  0:000   The CPU supported turbo
0:104  0:000  MSR 0x35              16002C
0:104  0:000  MSR 0xE2 before patch 00008402
0:104  0:000  MSR 0xE2 is locked, PM patches will be turned on
0:104  0:000  MSR 0xCE              20080C3B_F2811600
0:104  0:000  MSR 0x1B0             00000000
 
My sub sequential question is:
Which PM Patches are automatically turned on by clover for mine Broadwell EP Cpu?
Pavo
Pavo
Posted
Posted

 

I know that this isn't the right thread but I can't post into UEFI section so please forgive me :D

These Gigabyte guys made a BIOS file that's rubbish to say at least. If I want to unlock secret menus I can't because the program crashes (AMIBCP) if I want to patch it using UEFIPatch says nothing to patch.

What's wrong ?

Here is the BIOS file:

http://download.gigabyte.eu/FileList/BIOS/mb_bios_ga-b85m-d2v_f4.zip

It's a gigabyte board GA-B85M-D2V.

 

UEFIPatch only patches MSR 0xE2 lock (also known as Cpu CFG Lock) older GA boards afaik do not have this.

bronxteck
bronxteck
Posted
Posted

does latest clover 4394 installer install properly to 10.13.4? it seems to put it on the root of my "High Sierra" volume now.

 

I have to install to my first partition "Sierra" (shared drive for both os) for it to install to EFI. this issue was corrected a while back in clover. was there a code regression?

  • Like 1
Pavo
Pavo
Posted
Posted

does latest clover 4394 installer install properly to 10.13.4? it seems to put it on the root of my "High Sierra" volume now.

 

I have to install to my first partition "Sierra" (shared drive for both os) for it to install to EFI. this issue was corrected a while back in clover. was there a code regression?

Clover installer package has issues with installing into ESP right now for 10.13.4 beta 1. Its a known issue.

  • Like 1
ccphuc2016
ccphuc2016
Posted
Posted

does latest clover 4394 installer install properly to 10.13.4? it seems to put it on the root of my "High Sierra" volume now.

 

I have to install to my first partition "Sierra" (shared drive for both os) for it to install to EFI. this issue was corrected a while back in clover. was there a code regression?

WHERE THE LINK DOWNLOAD CLOVER 4394 ?

 

THANK

maoyeye
maoyeye
Posted
Posted
2018-02-04 00:21:25.516374+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.516375+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.517554+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.517555+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.517956+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.517956+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569454+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569454+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569479+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569479+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569521+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569521+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569542+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.569542+0800  localhost kernel[0]: (AppleACPIPlatform) <AppleACPIPlatform`AcpiOsVprintf> ACPI Error:

2018-02-04 00:21:25.578514+0800  localhost kernel[0]: (AppleACPIEC) <AppleACPIEC`AppleACPIEC::fetchNamespaceECResources(IOACPIPlatformDevice*, acpi_generic_address*, unsigned int*, unsigned int*, bool*)> ACPI: EC device memory error 0x0 0x0
chris1111
chris1111
Posted
Posted

works 4386, and 4398 this doesn't work. all working. iron in the signature. :hysterical:

manual transfer works in the folder EFI

Package not working in 10.13 Beta 4

its a know issue

Needy
Needy
Posted
Posted (edited)

Package not working in 10.13 Beta 4

 

works 4386, and 4398 this doesn't work. all working. iron in the signature. :hysterical:

manual transfer works in the folder EFI, works 4398.cd21dc00a0a7.jpg

 

 

works 4386, and 4398 this doesn't work. all working. iron in the signature. :hysterical:

manual transfer works in the folder EFI, works 4398.cd21dc00a0a7.jpg

 

 

I see, guess it's related to the EFI mount script. Not sure tho.

Check the installer log, should be in ur boot volume or EFI. 

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2584363
Edited by Needy
  • Like 1
chris1111
chris1111
Posted
Posted

Clover EFI installer log - Sun Feb  4 13:22:42 CET 2018

Installer version: v2.4k r4398 EFI bootloader

 319.1 GB   disk4s3

 

ERROR: /dev/disk2s1 use an unsupported partition scheme: EF57347C-0000-11AA-AA11-00306543ECAC

 

 

 

/dev/disk0 (internal, physical):

here the translation isn't necessary.

Edit ***

If you are in macOS High Sierra  (17E139j ) Clover package not working, its a know issue APFS Volume

  • Like 1
Badruzeus
Badruzeus
Posted
Posted

Hi @Slice,

Thanks for r4399 commit, but on my Legacy-GPT scheme it seems I have little bit installation problem; it uses my (selected) MacHD Root as target instead of the EFI Partition (Install Clover in the ESP checked though). Also, I see no r4398 backup files (that previously installed) from my /EFI-Backups. Sorry for reporting this issue.

 

 

soD0FUU.jpg

 

 

#EDIT: Using 10.11.6 with HFS+ when installing.

chris1111
chris1111
Posted
Posted

@Rehabman

i first saw clover ESP installation issue in 10.13.4 beta1. 

 

1. in 10.13.3, i didn't have install issue like this.

thanks in advance

Clover r4399 works here APFS 10.13.4 Beta1

  • Like 4
dgsga
dgsga
Posted
Posted

Here's an alternative and simpler mountESP script for 10.13.4 Beta 1, it wouldn't work on earlier macOS versions with APFS though :(. It would be possible to add the changes as an 'if OS ver > 10.13.3' clause...

#!/bin/bash

DEST_VOL="${1}"
EFI_ROOT_DIR="${2:-${DEST_VOL%*/}/EFIROOTDIR}"
partutil="./partutil"

DiskDevice=$(LC_ALL=C diskutil info "${DEST_VOL}" 2>/dev/null | \
                              sed -n 's/.*Part [oO]f Whole: *//p')

if [[ -z "$DiskDevice" ]]; then
    echo "Can't find volume with the name ${DEST_VOL}"
    exit 1
fi

# check if target volume is a logical Volume instead of physical
if [[ "$(echo $(LC_ALL=C diskutil list | grep -i 'Logical Volume' | \
          awk '{print tolower($0)}'))" == *"logical volume"* ]]; then
    # ok, we have a logical volume somewhere.. so that can assume that we can use "diskutil cs"
    LC_ALL=C diskutil cs info $DiskDevice > /dev/null 2>&1
    if [[ $? -eq 0 ]] ; then
        # logical volumes does not have an EFI partition (or not suitable for us?)
        echo "$DiskDevice is a logical volume"
        # find the partition uuid
        UUID=$(LC_ALL=C diskutil info "${DiskDevice}" 2>/dev/null | \
                                      sed -n 's/.*artition UUID: *//p')
        # with the partition uuid we can find the real disk in in diskutil list output
        if [[ -n "$UUID" ]]; then
            realDisk=$(LC_ALL=C diskutil list | \
                grep -B 1 "$UUID" | \
                grep -i 'logical volume' | awk '{print $4}' | \
                sed -e 's/,//g' | sed -e 's/ //g')
            if [[ -n "$realDisk" ]]; then
                DiskDevice=$(LC_ALL=C diskutil info "${realDisk}" 2>/dev/null | \
                                             sed -n 's/.*Part [oO]f Whole: *//p')
            fi
        fi
    fi
fi

# check if target volume is APFS, and therefore part of an APFS container
if [[ "$(echo $(LC_ALL=C diskutil list "$DiskDevice" | grep -i 'EF57347C-0000-11AA-AA11-00306543ECAC' | \
          awk '{print tolower($0)}'))" == *"ef57347c-0000-11aa-aa11-00306543ecac"* ]]; then
    # ok, this disk is an APFS partition, extract physical store device
    realDisk=$(LC_ALL=C diskutil list 2>/dev/null | \
        sed -n "s/.*Container $DiskDevice *//p" | \
        cut -d' ' -f5)
    echo Target volume "$1" on "$DiskDevice" is APFS on physical store "$realDisk"
    DiskDevice=$(LC_ALL=C diskutil info "$realDisk" 2>/dev/null | \
        sed -n 's/.*Part [oO]f Whole: *//p')
fi

# echo "realDisk = $realDisk"
# echo "UUID = $UUID"
# echo "DiskDevice = $DiskDevice"

# Check if the disk is a GPT disk
disk_partition_scheme=$("$partutil" --show-partitionscheme "$DiskDevice")

if [[ "$disk_partition_scheme" = "GUID_partition_scheme" ]]; then

    plistbuddy='/usr/libexec/PlistBuddy'

    # Get the index of the ESP device
    index=$(LC_ALL=C /usr/sbin/gpt -r show "/dev/$DiskDevice" 2>/dev/null | \
     awk 'toupper($7) == "C12A7328-F81F-11D2-BA4B-00A0C93EC93B" {print $3; exit}')
    [[ -z "$index" ]] && index=1 # if not found use the index 1

    # Define the ESPDevice
    ESPDevice="${DiskDevice}s${index}"

    # Get the ESP mount point if the partition is currently mounted
    ESPMountPoint=$("$partutil" --show-mountpoint "$ESPDevice")

    if [[ -n "$ESPMountPoint" ]]; then
        # If already mounted it's okay
        exitcode=0
    else
        # Else try to mount the ESP partition
        ESPMountPoint="/Volumes/ESP"
        exitcode=1
        fstype=$($partutil --show-fstype $ESPDevice)
        if [[ -n "$fstype" ]]; then
            [[ ! -d "${ESPMountPoint}" ]] && mkdir -p "${ESPMountPoint}"
            mount -t $fstype /dev/$ESPDevice "${ESPMountPoint}" 2>&1
            exitcode=$?
        fi
    fi

    if [[ $exitcode -ne 0 ]]; then
        echo
        echo "ERROR: can't mount ESP partition ($ESPDevice) !"
        echo "Check that the partition is well formated in HFS or Fat32."
        echo
        echo "To format as HFS use command like:"
        echo "sudo newfs_hfs -v EFI /dev/r$ESPDevice"
        echo
        echo "For format as Fat32 use command like:"
        echo "sudo newfs_msdos -v EFI -F 32 /dev/r$ESPDevice"
    else
        ln -sf "$ESPMountPoint" "$EFI_ROOT_DIR"
    fi
else
    # Disk is not GPT use the DEST_VOL as EFI_ROOT_DIR
    ln -sf "${DEST_VOL}" "$EFI_ROOT_DIR"
    exitcode=0
fi

exit $exitcode
  • Like 1
 Share
Go to topic listing
×
×
  • Create New...