Jump to content
30960 posts in this topic

Recommended Posts

Hi Sherlocks!

  "MacBook-Aluminum",   // MBP132
  "MacBook-Aluminum",   // MBP133

Not aluminum, but aluminium!

 

sorry. i don't really thinks this mistake.

old smbios has this name...

https://sourceforge.net/p/cloverefiboot/code/3917/tree//rEFIt_UEFI/Platform/platformdata.c

 

i just copy and paste. 

 

i will add imac 13,3 education model with fix.

education model has difference in other web site.

most of mac info sites has model name is imac13,1

http://www.everymac.com/systems/apple/imac/specs/imac-core-i3-3.3-21-inch-aluminum-early-2013-education-specs.html

 

but geekbench shown model name imac13,3

https://browser.primatelabs.com/geekbench3/2339913

you can see imac13,3 in motherboard entry

how do you think?

 

thank you:)

 

add. strange

everymac has "aluminum"

http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.9-15-late-2016-retina-display-touch-bar-specs.html

 

 

This notebook is offered in either silver colored aluminum or a darker "Space Gray" colored aluminum housing (but not other colors) and weighs just a bit more than 4 pounds (1.83 kg).

 

what is correct?

 

i saw both aluminum and aluminium are using in dictionary

sorry. i don't really thinks this mistake.

old smbios has this name...

https://sourceforge.net/p/cloverefiboot/code/3917/tree//rEFIt_UEFI/Platform/platformdata.c

 

i just copy and paste. 

 

i will add imac 13,3 education model with fix.

 

thank you:)

 

add. strange

everymac has "aluminum"

http://www.everymac.com/systems/apple/macbook_pro/specs/macbook-pro-core-i7-2.9-15-late-2016-retina-display-touch-bar-specs.html

 

what is correct?

 

i saw both aluminum and aluminium are using in dictionary

 

Aluminum is the correct spelling as per North American English.

Given the location of Apple headquarters in Cupertino, California, seems expected.

  • Like 3

added imac13,3 model.

 

many apple product info site inform imac13,3 is not exist, only shown imac13,1. so, i skipped this model.

http://www.everymac.com/systems/apple/imac/specs/imac-core-i3-3.3-21-inch-aluminum-early-2013-education-specs.html

 

like PMHeart mentioned, found this model's exist

first geekbench site

http://browser.primatelabs.com/geekbench3/search?utf8=%E2%9C%93&q=Mac-7DF2A3B5E5D671ED

 

more correct information in apple site

https://support.apple.com/ko-kr/HT201518

iMac (21.5-inch, Early 2013) iMac13,3 IM131.010A.B09 (2015-002)

 

as result, everymac and other sites has wrong information.

i added this model.

 

PMheart also Mentioned iMac15,2. but there is no iMac15,2 product name. only exist 15,1 name.

this is wrong in RevoBoot source

https://github.com/Piker-Alpha/RevoBoot/blob/clang/i386/libsaio/smbios/model_data.h#L133

 

board-id is Mac-FA842E06C61E91C5.

 

geekbench

http://browser.primatelabs.com/v4/cpu/1404453

it shown 15,1 in board entry.

 

kernel panic log in apple site. we sure it from this

https://discussions.apple.com/thread/6840233?start=0&tstart=0

 

other models are no problem.

 

also I changed the information by board ID. you can see what i said.

 

additionally, some imac models use mobile cpu.

here is list

 

  "Mac-81E3E92DD6088272",  // IM144   Intel Core i5-4260U @ 1.40 GHz 

  "Mac-A369DDC4E67F1C45",  // IM161   Intel Core i5-5250U @ 1.60 GHz 

 

because of this fact, i changed

 

      gSettings.ChassisType = MiscChassisTypeLapTop; //09;

      if((Model == iMac162) || (Model == iMac171)) {

          gSettings.Mobile      = FALSE;

          break;

      }

      gSettings.Mobile      = TRUE;

      break;

 

added

 

      gSettings.ChassisType = MiscChassisTypeAllInOne; //13;

      if(Model == iMac144) {

          gSettings.Mobile      = TRUE;

          break;

      }

 

tested build in latest r3968

 

 

you did this in r3963

 

chflags hidden "${mntpt}/${NVRAMFilename}"

 

changed

 

 

#chflags hidden "${mntpt}/${NVRAMFilename}"

 

we always see nvram file in EFI root and Mac HDD root.

 

i wonder that rc script is testing in latest commit?

 

i just wonder nvram file's hidden or not

 

thank you.

platformdata-update.zip

  • Like 1

added imac13,3 model.

 

many apple product info site inform imac13,3 is not exist, only shown imac13,1. so, i skipped this model.

http://www.everymac.com/systems/apple/imac/specs/imac-core-i3-3.3-21-inch-aluminum-early-2013-education-specs.html

 

like PMHeart mentioned, found this model's exist

first geekbench site

http://browser.primatelabs.com/geekbench3/search?utf8=%E2%9C%93&q=Mac-7DF2A3B5E5D671ED

 

more correct information in apple site

https://support.apple.com/ko-kr/HT201518

iMac (21.5-inch, Early 2013) iMac13,3 IM131.010A.B09 (2015-002)

 

as result, everymac and other sites has wrong information.

i added this model.

 

PMheart also Mentioned iMac15,2. but there is no iMac15,2 product name. only exist 15,1 name.

this is wrong in RevoBoot source

https://github.com/Piker-Alpha/RevoBoot/blob/clang/i386/libsaio/smbios/model_data.h#L133

 

board-id is Mac-FA842E06C61E91C5.

 

geekbench

http://browser.primatelabs.com/v4/cpu/1404453

it shown 15,1 in board entry.

 

kernel panic log in apple site. we sure it from this

https://discussions.apple.com/thread/6840233?start=0&tstart=0

 

other models are no problem.

 

also I changed the information by board ID. you can see what i said.

 

additionally, some imac models use mobile cpu.

here is list

 

because of this fact, i changed

 

added

 

tested build in latest r3968

 

 

you did this in r3963

 

changed

 

we always see nvram file in EFI root and Mac HDD root.

 

i wonder that rc script is testing in latest commit?

 

i just wonder nvram file's hidden or not

 

thank you.

Great job!

But I don't think we can rely on GeekBench etc.

Ah. Yes. Some iMac and Macmini models use mobile CPUs. But what else?

Cuz `#chflags hidden "${mntpt}/${NVRAMFilename}"` has been commented, and thus the /nvram.plist should be visible?

Great job!

But I don't think we can rely on GeekBench etc.

Ah. Yes. Some iMac and Macmini models use mobile CPUs. But what else?

Cuz `#chflags hidden "${mntpt}/${NVRAMFilename}"` has been commented, and thus the /nvram.plist should be visible?

Ofc. I dont want to rely on GeekBench. But we can get more correct data if we avoid hack build information.

 

I also wonder commented visible file like you said.

 

Now, we are still testing or not about nvram work? Rc script has problem in r3961. rc script is no problem for me in lastest commit. I wonder whether Rc script resolve or not.

 

나의 LG-F410S 의 Tapatalk에서 보냄

  • Like 1

Ofc. I dont want to rely on GeekBench. But we can get more correct data if we avoid hack build information.

 

I also wonder commented visible file like you said.

 

Now, we are still testing or not about nvram work? Rc script has problem in r3961. rc script is no problem for me in lastest commit. I wonder whether Rc script resolve or not.

 

나의 LG-F410S 의 Tapatalk에서 보냄

Some GeekBench results might be uploaded by hackintosh builds...

Ah sorry. I have no need for rc scpt and thus I can't test...

BTW. It seems that InjectKext and ForceKextsToLoad are attached... I want to use ForceKextsToLoad but don't want to inject Kexts in some cases. I just want to use ForceKextsToLoad. What should I do in this case?

iMac13,3 does exist, it's the 21.5-inch, Early 2013 education-only model (with an i3-3225, using HD 4000). iMac15,1 is the only model that does exist; however, iMac15,1 uses three different board IDs (depending on the GPU); same thing with iMac17,1.

  • Like 3

iMac13,3 does exist, it's the 21.5-inch, Early 2013 education-only model (with an i3-3225, using HD 4000). iMac15,1 is the only model that does exist; however, iMac15,1 uses three different board IDs (depending on the GPU); same thing with iMac17,1.

Yes. And it seems that iMac13,3 is the only model which Apple uses Intel Core i3 Processor.

It is so wonderful what you have been doing and merry Christmas to All.

post-413859-0-45695600-1482606707_thumb.png

  • Like 4

I'm sorry, but the wiki for compiling clover seems outdated.

I'm getting following error with `ebuild.sh`, even though the new "mtoc.NEW" is installed:

TOOLCHAIN_DIR: <redacted>/clover/src/edk2/Clover/../../opt/local
Installing mtoc
Password:
Installing mtoc.NEW
NASM_PREFIX: <redacted>/clover/src/edk2/Clover/../../opt/local/bin/
NASM_VER: 2.12.02
./ebuild.sh: line 336: [: 2: integer expression expected
./ebuild.sh: line 337: [: 2: integer expression expected
./ebuild.sh: line 338: [: 2: integer expression expected
your nasm is not good to build Clover!

Any idea?

 

Edit: I solved my issue by changing all comparison operators respectively:

-ge - >=

-gt - >

-eq - ==

 

 

Edit2: Well, it still won't build:

[CC] ScanMem32Wrapper
Usage: /usr/local/bin/libtool [OPTION]... [MODE-ARG]...
Try 'libtool --help' for more information.
Usage: /usr/local/bin/libtool [OPTION]... [MODE-ARG]...
Try 'libtool --help' for more information.
[CC] PcdLib
libtool:   error: unrecognised option: '-static'

I'm using edk2@23520

 

Edit3:

I have "libtool 2.4.6". Is it too new? Is there a specific version to use with clover?

Edited by smolderas

@Slice

 

i found brightness load is not work after reboot. always hold on brightness after boot.

 

I mistook the brightness value for the change.

 

So in a recent rc script I tracked down the problem.

 

latest rc script code(hold on brightness value)

 

Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local

NVRAM saved on root of disk0s1

Supreme-MBP:~ supreme$ 

 

# echo "$rootDevice"

    # If NVRAMDevice is not specify use rootDevice
    #NVRAMDevice=${NVRAMDevice:-$rootDevice}
    NVRAMDevice=$(findFirstESP)
 
# echo "$NVRAMDevice"
    # Normalize NVRAMDevice (keep only the device name (remove /dev/)
    NVRAMDevice=${NVRAMDevice##*/}
 
# echo "normal $NVRAMDevice"
    if [[ ! "$NVRAMDevice" =~ ^disk[0-9]*s[0-9]*$ ]]; then
        # NVRAMDevice is a whole disk certainly a RAID device
        # try to save nvram.plist on the first Apple Boot Partition
 
        local AppleBootDevice=${rootDevice}
# echo "$AppleBootDevice"
        if [[ -n "$AppleBootDevice" ]]; then
            # Try to save nvram.plist on the Apple Boot device
            mountAndSaveNVRAM "$AppleBootDevice"
            [[ $? -eq 0 ]] && return
        fi
    fi
    

 

brightness work code

 

Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local

Password:

NVRAM saved to '/nvram.plist' [disk0s4]

Supreme-MBP:~ supreme$ 

 

# echo "$rootDevice"

    # If NVRAMDevice is not specify use rootDevice
    #NVRAMDevice=${NVRAMDevice:-$rootDevice}
    NVRAMDevice=${rootDevice}
 
# echo "$NVRAMDevice"
    # Normalize NVRAMDevice (keep only the device name (remove /dev/)
    NVRAMDevice=${NVRAMDevice##*/}
 
# echo "normal $NVRAMDevice"
    if [[ ! "$NVRAMDevice" =~ ^disk[0-9]*s[0-9]*$ ]]; then
        # NVRAMDevice is a whole disk certainly a RAID device
        # try to save nvram.plist on the first Apple Boot Partition
 
        local AppleBootDevice=$(findFirstESP)
# echo "$findFirstESP"
        if [[ -n "$AppleBootDevice" ]]; then
            # Try to save nvram.plist on the Apple Boot device
            mountAndSaveNVRAM "$AppleBootDevice"
            [[ $? -eq 0 ]] && return
        fi
    fi

 

i tried to change other method to hold on make nvram.plist in EFI root with bightness load work.

 

but i can't. according to this reslove, you need to find new method.

 

merry christmas.

 

thank you.

  • Like 3

Good afternoon, I own an EVGA X58 motherboard, and an X5660 xeon processor, and I wanted to use smbios for macpro 5.1, but the TyMCEDriver patch does not work. Does anyone have the correct patches?

Did you apply Patches_for_EDK2?

I am using system libtool as it set by default Xcode installation from 10.7 up to recent 10.12.3

With the default Apple built libtool I finally can compile clover again. The newest one of libtool lacks the option `-static`.

  • Like 1

Worked on el capitan, sierra still on black screen with parked mouse.

This could be not related to AppleTyMCEDriver. It seemed that AppleTyMCEDriver just caused KP on non-ECC memory. For further discussion, we may discuss at installation section?  :)

 

PMheart

Just tried to build latest Clover with CloverGrowerPro.

Had a couple of issues with setting up (not finding isl-0.12.2 ...Failed to connect to gcc.gnu.org port 21: Operation timed out) but found a mirrored site and manually downloaded).

 

After that first build went OK and I installed r3806 via pkg installer and system booted like before. All OK.

 

Then, I used "touch" on one of the .C files and ran Cloverpro again and it came back with:

..
..
..
bla bla bla.
..
..
Architecture(s)  = X64
Build target     = RELEASE
Toolchain        = GCC49

Active Platform          = /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Clover/Clover.dsc
Flash Image Definition   = /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Clover/Clover.fdf

Processing meta-data .... done!
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64]
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull.inf [X64]
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BaseMemoryLib/BaseMemoryLib.inf [X64]
make: *** No rule to make target `tbuild'.  Stop.
Building ... /Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BasePcdLibNull/BasePcdLibNull]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseDebugLibNull/BaseDebugLibNull]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseMemoryLib/BaseMemoryLib]


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/Build/Clover/RELEASE_GCC49/X64/MdePkg/Library/BaseLib/BaseLib]


build.py...
 : error F002: Failed to build module
	/Users/MacNB/Documents/CloverGrowerPro-master/CloverGrowerPro/edk2/MdePkg/Library/BasePcdLibNull/BasePcdLibNull.inf [X64, GCC49, RELEASE]

- Failed -
Build end time: 01:13:03, Oct.14 2016
Build total time: 00:00:08

Cloverx64  ERROR!!


Ejecting RAM disk
"disk2" unmounted.
"disk2" ejected.
SR-Mac-530:CloverGrowerPro MacNB$ 

Cannot do any more builds.

What wrong and how to fix ?

(I am running on macOS 10.12)

 

 

The same happened to me ... how can I fix this? Any clues? Which Makefile is complaining about 'No rule to make target tbuild' 

Thanks

 

Thanks, that script works beautifully ... just one thing somewhere there is a Clover.dsc for me (Mountain Lion used almost all defaults except MODE set to "R" ) I needed to remove -Wno-msvc-include at line 613 ... I suspect was the same issue with CloverGrowerPro except that gave me no clue what the problem was.

clover 3333 auto generate smbios iMac 2012 which caused i can not install lion 10.7.5 11G63,i have to create smbios mac pro 3.1 to install lion 10.7.5 11G63,what is the problem?if i change from i3-3240 to e3 1230,does clover 3333 auto generate smbios iMac 2011 that i can cause i can install 10.7.5 11G63?

clover 3333 auto generate smbios iMac 2012 which caused i can not install lion 10.7.5 11G63,i have to create smbios mac pro 3.1 to install lion 10.7.5 11G63,what is the problem?if i change from i3-3240 to e3 1230,does clover 3333 auto generate smbios iMac 2011 that i can cause i can install 10.7.5 11G63?

You can set SMBios manually. Anyway. I think iMac13,2 is more compatible with Ivy Bridge.

×
×
  • Create New...