nms Posted December 17, 2016 Share Posted December 17, 2016 I don't know if this helps you guys, but the device that Clover was started from is available from the Clover bootlog. The Clover bootlog is available from ioreg. Note: SPEEDY-NUC:~ rehabman$ bdmesg|grep SelfDevicePath 0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1D,0x0)\Pci(0x0,0x0)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,720CCE1B-927B-4261-9ED9-4126654A36CA,0x28,0x64000) @84486018 Is not it a device where clover found config.plist? Link to comment Share on other sites More sharing options...
joevt Posted December 17, 2016 Share Posted December 17, 2016 So I'm pretty sure that we need to do something before SIGTERM as joevt is saying in #11984. What I found is that we can't actually mount on SIGTERM, which is why it's bugging out.rEFItBlesser is a solution for rEFIt that does a similar thing - mount the EFI partition at shutdown. It is a Startup Item as described at: https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/StartupItems.html#//apple_ref/doc/uid/10000172i-SW9-CJBBHDII I made some changes for rEFInd which seemed to work when I used it but I haven't used it recently. Startup Items are deprecated but I think they still work. Anyway, if the rEFItBlesser script works, then maybe it can help with this save_nvram_plist problem. You'll probably want to remove any part that uses the bless command, and just test the disk mounting feature (the if statement after the "mounted=0" line). Note that it uses "mount" instead of "df" to get a list of mount points. It also doesn't use diskutil. It uses /Users/Shared because other folders may not have permission? The difference between a Startup Item and a Daemon is that a Startup Item defines dependencies. I think this is all handled by launchd, which you can look at the source code. Maybe the relevant parts could be converted to a Daemon. rEFItBlesser.zip 1 Link to comment Share on other sites More sharing options...
RehabMan Posted December 17, 2016 Share Posted December 17, 2016 Is not it a device where clover found config.plist? It indicates the partition from which Clover was started by BIOS. And, yes... also the location of config.plist (Clover always loads the configuration from the same partition it was booted from). Link to comment Share on other sites More sharing options...
joevt Posted December 17, 2016 Share Posted December 17, 2016 Is not it a device where clover found config.plist?I haven't checked. It doesn't matter. The take away here is that Clover can put any information we want there. If the information does not include the location of Clover, than Clover can be changed to add that. If device path is not usable by Mac OS X, Clover could add the partition GUID (either from GPT or from the filesystem). To learn if device path is useable in Mac OS X, we should learn what kind of device paths the bless command creates, and how it does that. We should make a routines that can be used in Mac OS X that can convert a device path between hex and text like GfxUtil but which can handle all cases as defined by EFI_DEVICE_PATH_TO_TEXT_PROTOCOL and EFI_DEVICE_PATH_FROM_TEXT_PROTOCOL. I think all the source code for this is in the UefiDevicePathLib folder of EDK2. GfxUtil only implements 2 device path node types, pci and acpi. UefiDevicePathLib has 44 others. Link to comment Share on other sites More sharing options...
PMheart Posted December 18, 2016 Share Posted December 18, 2016 Hi. Could Clover support reading EFI String info except config.plist?... In some cases it's so inconvenient that the long data is existing in config.plist... Thanks. PMheart Link to comment Share on other sites More sharing options...
Slice Posted December 18, 2016 Share Posted December 18, 2016 It indicates the partition from which Clover was started by BIOS. And, yes... also the location of config.plist (Clover always loads the configuration from the same partition it was booted from). In the case of legacy boot there are two different partitions: 1. Where MBR, PBR and file BOOT are located. 2. Where CloverX64.efi and config.plist are located. They can be different. 1 Link to comment Share on other sites More sharing options...
RehabMan Posted December 18, 2016 Share Posted December 18, 2016 In the case of legacy boot there are two different partitions: 1. Where MBR, PBR and file BOOT are located. 2. Where CloverX64.efi and config.plist are located. They can be different. Yes, I don't use legacy boot, so my comments apply to UEFI only. Even in the legacy scenario, it is best if #1 and #2 are the same (ESP). I'm not a fan of a "legacy root" install of Clover, I would assume in the "legacy root" scenario you would still store nvram.plist in partition indicated by SelfDevicePath (likely the only possibility). Link to comment Share on other sites More sharing options...
Sherlocks Posted December 18, 2016 Share Posted December 18, 2016 i added old models in platformdata.c. Some have changed to the correct data. platform data add models.zip added list MacBookPro1,2 MacBookPro5,2 MacBookPro5,4 MacBookPro11,4 MacBookAir3,2 MacMini5,2 MacMini5,3 iMac4,2 iMac5,2 No more models are missing. Clover has all the information from Apple to models using Intel cpu to the current model now. if you don't trust, search board-id, you can see added info in web site(geekbench, apple site, kernel panic log) tested build in latest r3964. test report nvram from r3964 brightness load is good after reboot. nvram save in efi partition root. 2nd boot, nvram save in mac hdd root. but unhide. i see unhide code in rc script. will it be hide? and already report, not include christmas theme in pkg. when install clover pkg, remove christmas install option(automately) or need to add christmas theme in pkg. thank you. 1 Link to comment Share on other sites More sharing options...
joevt Posted December 20, 2016 Share Posted December 20, 2016 To learn if device path is useable in Mac OS X, we should learn what kind of device paths the bless command creates, and how it does that. The file /src/edk2/Clover/rEFIt_UEFI/Platform/Nvram.c seems to suggest that there could be some differences between the device paths created by bless (or Startup Disk Preferences panel) and by EFI. There are special compare functions in that file to compare these device paths. This might not be as easy as I thought. Maybe it's possible for Clover to add a device property to the device that contained Clover, then a script in macOS can search for that property in the entire IO Registry without having to compare device paths. Link to comment Share on other sites More sharing options...
Sherlocks Posted December 20, 2016 Share Posted December 20, 2016 @Slice. i updated Chassis Information. it's not clear since long time ago. here is my research result. =======================MacBook=========================== MacBook1,1 Chassis Information (Type 3) Raw Data: Header and Data: 03 15 03 00 01 0A 02 03 04 03 03 01 01 00 00 00 00 00 00 00 00 Strings: Apple Computer, Inc. Mac-F4208CC8 Asset Tag Manufacturer: Apple Computer, Inc. Type: Notebook Lock: Not Present Version: Mac-F4208CC8 Serial Number: Asset Tag: Asset Tag Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBook8,1 Chassis Information Manufacturer: Apple Inc. Type: Laptop Lock: Not Present Version: Mac-BE0E8AC46FE800CC Serial Number: Asset Tag: Chassis Board Asset Tag# Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 SKU Number: Not Specified MacBook1,1~7,1 are old models. type use Notebook. since MacBook8,1use broadwell and renew models, type use Laptop. skylake model too. ============================================================== ======================MacBook Pro============================= MacBookPro5,2 Chassis Information (Type 3) Raw Data: Header and Data: 03 15 11 00 01 08 02 03 04 03 03 01 01 00 00 00 00 00 00 00 00 Strings: Apple Inc. Mac-F2268EC8 Asset Tag# Manufacturer: Apple Inc. Type: Portable Lock: Not Present Version: Mac-F2268EC8 Serial Number: Asset Tag: Asset Tag# Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookPro8,1 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-94245B3640C91C81 Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookPro9,1 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-4B7AC7E43945597E Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookPro10,1 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-C3EC7CD22292981F Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookPro11,2 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-3CBD00234E554E41 Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookPro1,1 ~ MacBookPro7,1 use Board-ID 8 numbers. Mac-XXXXXXXX, Type is Portable MacBookPro8,1 ~ MacBookPro11,1 use Board-ID 12 numbers. Mac-XXXXXXXX Type is Notebook MacBookPro12,1 Chassis Information Manufacturer: Apple Inc. Type: Laptop Lock: Not Present Version: Mac-E43C1C25D4880AD6 Serial Number: Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 SKU Number: Not Specified MacBookPro12,1 ~ use broadwell cpu. we can see imac17,1 type. it uses type laptop too. as result, macbookpro13,x use type “Laptop” ============================================================== ======================MacBook Air============================= MacBookAir2,1 Chassis Information (Type 3) Raw Data: Header and Data: 03 15 11 00 01 0A 02 03 04 03 03 01 01 00 00 00 00 00 00 00 00 Strings: Apple Inc. Mac-F42D88C8 Asset Tag# Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-F42D88C8 Serial Number: Asset Tag: Asset Tag# Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookAir3,1 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-942452F5819B1C1B Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookAir4,1 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-C08A6BB70A942AC2 Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 MacBookAir5,2 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-2E6FAB96566FE58C Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 we can’t smbios file after MacBookAir6,1 but we can find fact. both MacBook8,1 and MacBookPro12,1 use Broadwell and used Type “Laptop”. MacBookAir6,1 has Haswell. Haswell model use Type “Notebook”, and MacBookAir7,1 use Broardwell. as result, we can enough guess MacBookAir7,1 type is “Laptop”. ============================================================== ======================Mac mini============================= Macmini1,1 Chassis Information (Type 3) Raw Data: Header and Data: 03 15 03 00 01 04 02 03 04 03 03 01 01 00 00 00 00 00 00 00 00 Strings: Apple Computer, Inc. Mac-F4208EC8 Asset Tag Manufacturer: Apple Computer, Inc. Type: Low Profile Desktop Lock: Not Present Version: Mac-F4208EC8 Serial Number: Asset Tag: Asset Tag Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 we don’t know Macmini2,1 type. but can guess enough. because board-id is very similar “Mac-F408EXX”. so Macmini2,1 type is “Low Profile Desktop” Macmini3,1 Chassis Information Manufacturer: Apple Inc. Type: Lunch Box Lock: Not Present Version: Mac-F22C86C8 Serial Number: Asset Tag: Asset Tag# Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 Macmini5,1 Chassis Information Manufacturer: Apple Inc. Type: Lunch Box Lock: Not Present Version: Mac-8ED6AF5B48C039E1 Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 we don’t know use Macmini6,1 type. but can guess enough. because both 5,1 and 6,1 use “SandyBridge CPU”. so Macmini6,1 type is “Lunch Box” Macmini7,1 Chassis Information Manufacturer: Apple Inc. Type: Notebook Lock: Not Present Version: Mac-35C5E08120C7EEAF Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 ============================================================== ======================iMac============================= iMac5,1 Chassis Information (Type 3) Raw Data: Header and Data: 03 15 03 00 01 0D 02 03 04 03 03 01 01 00 00 00 00 00 00 00 00 Strings: Apple Computer, Inc. Mac-F42786A9 Asset Tag Manufacturer: Apple Computer, Inc. Type: All In One Lock: Not Present Version: Mac-F42786A9 Serial Number: Asset Tag: Asset Tag Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 iMac10,1 Chassis Information (Type 3) Raw Data: Header and Data: 03 15 13 00 01 0D 02 03 04 03 03 01 01 00 00 00 00 00 00 00 00 Strings: Apple Inc. Mac-F2268DC8 Asset Tag# Manufacturer: Apple Inc. Type: All In One Lock: Not Present Version: Mac-F2268DC8 Serial Number: Asset Tag: Asset Tag# Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 iMac13,1 Handle 0x001D, DMI type 3, 21 bytes Chassis Information Manufacturer: Apple Inc. Type: All In One Lock: Not Present Version: Mac-00BE6ED71E35EB86 Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 iMac14,1 Chassis Information Manufacturer: Apple Inc. Type: All In One Lock: Not Present Version: Mac-031B6874CF7F642A Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 iMac17,1 Chassis Information Manufacturer: Apple Inc. Type: Laptop Lock: Not Present Version: Mac-DB15BD556843C820 Serial Number: Asset Tag: Boot-up State: Safe Power Supply State: Safe Thermal State: Safe Security Status: None OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 SKU Number: Not Specified iMac17,1 use Skylake cpu. iMac16,1 use broadwell cpu. according to apple used type pattern above, both 17,1 and 16,1 have type. as result, Type “Laptop” 15,1 use Haswell. We can get fact from Macbookpro and Macbookair. haswell and under cpu, use same type. as result, we can get Type “All In One” ============================================================== ======================MacPro============================= MacPro3,1 Chassis Information Manufacturer: Apple Inc. Type: Unknown Lock: Not Present Version: Mac-F42C88C8 Serial Number: Asset Tag: Asset Tag# Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 we don’t know 1,1 and 2,1’s type. but we guess type “Unknown”. because 1,1 ~ 3,1 use same board-id pattern “Mac-F42XXXXX” MacPro5,1 Chassis Information Manufacturer: Apple Inc. Type: Tower Lock: Not Present Version: Mac-F221BEC8 Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 we don’t know 4,1’s type. but we know board-id. 4,1 and 5,1 use same board-id. as result, 4,1’s type “Tower” MacPro6,1 Chassis Information Manufacturer: Apple Inc. Type: Unknown Lock: Not Present Version: Mac-F60DEB81FF30ACF6 Serial Number: Asset Tag: Not Specified Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: Unspecified Contained Elements: 0 ============================================================== we get Chassis Information clearly now. i can't get some information. but can guess it enough from apple's Chassis pattern. tested build in r3966. here is smbios dump. Base Board Information Manufacturer: Apple Inc. Product Name: Mac-A5C67F76ED83108C Version: MacBookPro13,3 Serial Number: Asset Tag: Base Board Asset Tag Features: Board is a hosting board Board is replaceable Location In Chassis: Part Component Chassis Handle: 0x0010 Type: Motherboard Contained Object Handles: 0 Handle 0x0010, DMI type 3, 22 bytes 0000: 03 16 10 00 01 09 02 03 04 03 03 01 01 00 00 00 0010: 00 00 01 00 00 00 Chassis Information Manufacturer: Apple Inc. Type: Laptop Lock: Not Present Version: Mac-A5C67F76ED83108C Serial Number: Asset Tag: MacBook-Aluminum Boot-up State: Safe Power Supply State: Safe Thermal State: Other Security Status: Other OEM Information: 0x00000000 Height: Unspecified Number Of Power Cords: 1 Contained Elements: 0 SKU Number: Not Specified you can see case MacBookPro114: case MacBookPro115: case MacMini71: gSettings.ChassisType = MiscChassisTypeNotebook; //10; gSettings.Mobile = TRUE; break; about case MacMini71. mobile is true. i saw macmini7,1 use haswell mobile cpu "i5-4278U". because of this reason, i did "gSettings.Mobile = TRUE;" imac16,1 imac16,2 imac17,1 gSettings.Mobile = False;. because it not use mobile cpu. you can see what i did. Clover Configurator and Clover CCE have wrong information of Chassis. We need to support them from Apple's smbios data. i really appreciate this thread https://applelife.ru/threads/darwindumper-dampy-nastojaschix-macov.39174/ i checked christmas theme in latest commit. thanks. platformdata.c-Chassis Information.zip Link to comment Share on other sites More sharing options...
bronxteck Posted December 20, 2016 Share Posted December 20, 2016 for me christmas theme was missing sierra icons Link to comment Share on other sites More sharing options...
Slice Posted December 21, 2016 Share Posted December 21, 2016 @Slice. i updated Chassis Information. it's not clear since long time ago. here is my research result. we get Chassis Information clearly now. i can't get some information. but can guess it enough from apple's Chassis pattern. tested build in r3966. here is smbios dump. you can see about case MacMini71. mobile is true. i saw macmini7,1 use haswell mobile cpu "i5-4278U". because of this reason, i did "gSettings.Mobile = TRUE;" imac16,1 imac16,2 imac17,1 gSettings.Mobile = False;. because it not use mobile cpu. you can see what i did. Clover Configurator and Clover CCE have wrong information of Chassis. We need to support them from Apple's smbios data. i really appreciate this thread https://applelife.ru/threads/darwindumper-dampy-nastojaschix-macov.39174/ i checked christmas theme in latest commit. thanks. OK, committed. Link to comment Share on other sites More sharing options...
PMheart Posted December 21, 2016 Share Posted December 21, 2016 @Sherlocks You are missing MacBook8,2 SMBios data LOL. So not full. I can get a little like board-id etc. But not all. Anyway hope this may help you? ProductName: MacBook8,2 board-id: Mac-473D31EABEB93F9B Others like BoardManufacturer should be absolutely Apple. Don't want to tell. Link to comment Share on other sites More sharing options...
Sherlocks Posted December 21, 2016 Share Posted December 21, 2016 @Sherlocks You are missing MacBook8,2 SMBios data LOL. So not full. I can get a little like board-id etc. But not all. Anyway hope this may help you? ProductName: MacBook8,2 board-id: Mac-473D31EABEB93F9B Others like BoardManufacturer should be absolutely Apple. Don't want to tell. where is MacBook8,2? i never see MacBook8,2 model. here is MacBook Series. http://www.everymac.com/systems/apple/macbook/index-macbook.html board-id: Mac-473D31EABEB93F9B -> MacBookPro13,1 model board-id here is fact https://browser.primatelabs.com/v4/cpu/compare/875361?baseline=875361 Link to comment Share on other sites More sharing options...
PMheart Posted December 21, 2016 Share Posted December 21, 2016 where is MacBook8,2? i never see MacBook8,2 model. here is MacBook Series. http://www.everymac.com/systems/apple/macbook/index-macbook.html board-id: Mac-473D31EABEB93F9B -> MacBookPro13,1 model board-id here is fact https://browser.primatelabs.com/v4/cpu/compare/875361?baseline=875361 Oops. Why... But here it's MB82 with the board-id above. https://github.com/syscl/XPS9350-macOS/blob/master/CLOVER/config.plist#L738 Edit: Ah no. I think syscl is wrong. But in Pike's ssdtPRGen.sh, there's still MacBook8,2 but with a different board-id. (https://github.com/Piker-Alpha/ssdtPRGen.sh/blob/Beta/Data/Models.cfg#L95) It's Mac-F305150B0C7DEEEF.plist And yes. Mac-473D31EABEB93F9B is MBP13,1. Sorry my error. Link to comment Share on other sites More sharing options...
Sherlocks Posted December 21, 2016 Share Posted December 21, 2016 Oops. Why... But here it's MB82 with the board-id above. https://github.com/syscl/XPS9350-macOS/blob/master/CLOVER/config.plist#L738 it's wrong. did you search board-id? you just tell me syscl's smbios. he used combined smbios data. syscl smbios combination list bios version - macbook9,1 data familiy - macbook productname - macbook8,2 board-id - macbookpro13,1 already not match. give me official macbook8,2 information. Link to comment Share on other sites More sharing options...
PMheart Posted December 21, 2016 Share Posted December 21, 2016 it's wrong. did you search board-id? you just tell me syscl's smbios. he used combined smbios data. syscl smbios combination list bios version - macbook9,1 data familiy - macbook productname - macbook8,2 board-id - macbookpro13,1 already not match. give me official macbook8,2 information. Ah no... Yes I see syscl uses a combined SMBios data. But Pike mentioned MB82 and here is one more. (https://gist.github.com/rtrouton/e6cf0f4064aea52fac2e5116c4b05f2e#file-gistfile1-txt-L9) Strangely. I cannot get any info about MB82 but it seems to exist. 1 Link to comment Share on other sites More sharing options...
Sherlocks Posted December 21, 2016 Share Posted December 21, 2016 Ah no... Yes I see syscl uses a combined SMBios data. But Pike mentioned MB82 and here is one more. (https://gist.github.com/rtrouton/e6cf0f4064aea52fac2e5116c4b05f2e#file-gistfile1-txt-L9) Strangely. I cannot get any info about MB82 but it seems to exist. thank you for information. we never see Mac-F305150B0C7DEEEF information in web, geekbench, everymac, etc. apple just add this board-id. they not use this board-id when release macbook8,x. if any information is exist, It should of course be added. but exist only board-id. at least, have to exist bios version or official specs in everymac. have a nice day 1 Link to comment Share on other sites More sharing options...
PMheart Posted December 21, 2016 Share Posted December 21, 2016 thank you for information. we never see Mac-F305150B0C7DEEEF information in web, geekbench, everymac, etc. apple just add this board-id. they not use this board-id when release macbook8,x. if any information is exist, It should of course be added. but exist only board-id. at least, have to exist bios version or official specs in everymac. have a nice day Thanks. Yes. Some board-ids are existing but they may not be released. You can check /S*/L*/E*/IOPlatformPluginFamily.kext/C*/PlugIns/X86PlatformPlugin.kext/C*/Resources. But... Why Pike and rtrouton said it's MB8,2... 1 Link to comment Share on other sites More sharing options...
liujianwei Posted December 21, 2016 Share Posted December 21, 2016 Why lost respond from keyboard and mouse random on clover and sierra?config.plistdelete all option exceptSSDT:GenerateKernelAndKextPatches:AppleRTCSystemParameters:InjectKextsseems fix this problem with dsdt <?xml version="1.0" encoding="UTF-8"?><!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>ACPI</key> <dict> <key>SSDT</key> <dict> <key>Generate</key> <dict> <key>CStates</key> <true/> <key>PStates</key> <true/> </dict> </dict> </dict> <key>KernelAndKextPatches</key> <dict> <key>AppleRTC</key> <true/> </dict> <key>SystemParameters</key> <dict> <key>InjectKexts</key> <string>Yes</string> </dict> </dict> </plist> Link to comment Share on other sites More sharing options...
PMheart Posted December 22, 2016 Share Posted December 22, 2016 @Sherlocks Hi. I found iMac13,3 SMBios data from Pike's Revoboot Fork. It's a special-designed model for education early 2013. The data can be found at https://github.com/Piker-Alpha/RevoBoot/blob/clang/i386/libsaio/smbios/model_data.h#L82 And also. It seems that there's multiple board-id for iMac17,1. They are divided by different configurations. One more... Why use 'iMac17,1' here instead of 'iMac'... Apple's specifications? ( https://sourceforge.net/p/cloverefiboot/code/3967/tree//rEFIt_UEFI/Platform/platformdata.c#l494 ) Thanks in advance. PMheart Link to comment Share on other sites More sharing options...
Sherlocks Posted December 22, 2016 Share Posted December 22, 2016 @Sherlocks Hi. I found iMac13,3 SMBios data from Pike's Revoboot Fork. It's a special-designed model for education early 2013. The data can be found at https://github.com/Piker-Alpha/RevoBoot/blob/clang/i386/libsaio/smbios/model_data.h#L82 And also. It seems that there's multiple board-id for iMac17,1. They are divided by different configurations. One more... Why use 'iMac17,1' here instead of 'iMac'... Apple's specifications? ( https://sourceforge.net/p/cloverefiboot/code/3967/tree//rEFIt_UEFI/Platform/platformdata.c#l494 ) Thanks in advance. PMheart I made it based on everymac site. thank you for imac13,3 and other models info from revoboot. i will search more details. yeah. imac17,1 has multiple board-id also exist only model name imac17,1. we can choose one. i don't touch board-id that clover use 17,1 board-id select long time ago. family name reason here System Information Manufacturer: Apple Inc. Product Name: iMac17,1 Version: 1.0 Serial Number: XXXXXXXXXXXX UUID: XXXXXXX-XXXX-XXXX-XXXXX-XXXXXXXXXXXX Wake-up Type: Power Switch SKU Number: Family: iMac17,1 some models don't use Family name any Mac names. ex macbookpro model. it causes many confusion. you can check what i said by checking smbios data of apple models. 1 Link to comment Share on other sites More sharing options...
PMheart Posted December 22, 2016 Share Posted December 22, 2016 I made it based on everymac site. thank you for imac13,3 and other models info from revoboot. i will search more details. yeah. imac17,1 has multiple board-id also exist only model name imac17,1. we can choose one. i don't touch board-id that clover use 17,1 board-id select long time ago. family name reason here some models don't use Family name any Mac names. ex macbookpro model. it causes many confusion. you can check what i said by checking smbios data of apple models. Thanks. But the Family should be 'iMac' instead of 'iMac17,1'? Clover now using 'iMac17,1'... The 'Product Name' should be 'iMac17,1' but Family should be 'iMac'... Just like other iMac models? Anyway. I'd like to know why Clover specially set the 'Family' of iMac17,1 to 'iMac17,1' but not iMac... Link to comment Share on other sites More sharing options...
Sherlocks Posted December 22, 2016 Share Posted December 22, 2016 Thanks. But the Family should be 'iMac' instead of 'iMac17,1'? Clover now using 'iMac17,1'... The 'Product Name' should be 'iMac17,1' but Family should be 'iMac'... Just like other iMac models? Anyway. I'd like to know why Clover specially set the 'Family' of iMac17,1 to 'iMac17,1' but not iMac... At first I thought iMac was the name of the family. However, when I checked the smbios data, the familiy name was iMac17,1. On top of that I wrote the facts. Some macbookpro models had strange names without the word mac at all. So, I suggested some degree of unification. If we do not unify, we need to check the smbios data for all models, and we can not get the data from the internet. Link to comment Share on other sites More sharing options...
PMheart Posted December 22, 2016 Share Posted December 22, 2016 At first I thought iMac was the name of the family. However, when I checked the smbios data, the familiy name was iMac17,1. On top of that I wrote the facts. Some macbookpro models had strange names without the word mac at all. So, I suggested some degree of unification. If we do not unify, we need to check the smbios data for all models, and we can not get the data from the internet. Your code above on iMac17,1 is 'Product Name', not 'Family'. I think the 'Product Name' should be 'iMac17,1' (This is correct.) and 'Family' should be 'iMac'. (Not 'iMac17,1') Also. I saw in Clover Configurator, the 'Family' is 'iMac'. May be not correct. Link to comment Share on other sites More sharing options...
Recommended Posts