Jump to content

Clover General discussion


ErmaC
29,866 posts in this topic

Recommended Posts

Hey guys just found a bug on the latest Clover 4149 and up, for some odd reason Clover doesn't read/patch Kext sections from plist, eg. NVME patch doesn't work. Rolling back the clover does.

 

Check all the logs found nothing so far to indicate why is it doing it.

Yes. I have the same problem. System won't boot from Plextor M2. 

debug.log.zip

Link to comment
Share on other sites

I can't see any nvidia info on your system log.

 

나의 LG-F800S 의 Tapatalk에서 보냄

Its not this?

 

0:100  0:000   - GFX: Model=Gigabyte GeForce GTX 750 Ti family 117 (Nvidia)

0:100  0:000  PCI (00|01:00.01) : 10DE 0FBC class=040300
0:100  0:000   - HDMI Audio: 
0:100  0:000  PCI (00|00:16.00) : 8086 1C3A class=078000
0:100  0:000  PCI (00|00:16.01) : FFFF FFFF class=FFFFFF
0:100  0:000  PCI (00|00:1A.00) : 8086 1C2D class=0C0320
0:100  0:000  PCI (00|00:1B.00) : 8086 1C20 class=040300
0:100  0:000  PCI (00|00:1C.00) : 8086 1C10 class=060400
0:100  0:000  PCI (00|00:1C.01) : 8086 1C12 class=060400
0:100  0:000  PCI (00|03:00.00) : 168C 002B class=028000
 
0:210  0:000  Video driver loaded: disconnect Success
0:287  0:076  Searching for invalid DiskIo BY_DRIVER connects: not found, all ok
0:287  0:000  VideoBiosPatchNativeFromEdid:
0:287  0:000   Bios: nVidia, nv_data_table_offset: 0x28B, nv_data_table: 0xC028D, std_vesa: 0xC438E, nv_mode_table: 0xC4393, mode_table_size: 0x10
0:287  0:000   VideoBiosPatchInit(LegacyRegion = Success) = Success
0:287  0:000   VideoBiosUnlock:  unlocked
0:288  0:001   Patching: BT_NVDA
0:288  0:000   Parse Edid: descriptor block 0 is timing descriptor (h_active: 1366, v_active: 768, h_sync_offset: 70, h_sync_width: 143, h_blanking: 426, v_blanking: 30, pixel_clock: 8550, v_sync_offset: 3, v_sync_width: 3)
0:288  0:000  the patch is not ready for the desired resolution
0:288  0:000   VideoBiosLock: Success
0:305  0:016  CsmVideoDriverBindingStart
0:305  0:000  mixed support=40010
0:305  0:000  Controller is [030000]
0:305  0:000  Check for VBE
0:349  0:044   found Detail Timing 1366x768
0:349  0:000   found Detail Timing 1360x768
0:357  0:008    0 640x480 attr=3BF - ok, edid+, 640x480, working, highest, pref=0
0:358  0:001    1 800x600 attr=3BF - ok, edid+, 800x600, working, highest, pref=1
0:360  0:001    2 1024x768 attr=3BF - ok, edid+, 1024x768, working, highest, pref=2
0:361  0:001    3 1280x1024 attr=3BF - ok, edid-
0:369  0:008    4 1600x1200 attr=3BF - ok, edid-
0:369  0:000  CsmVideo: New mode: 2 1024x768 - set
0:538  0:168   - SetMode pref 2 (2) = Success
0:538  0:000  CsmVideoCheckForVbe - Success
0:538  0:000  CsmVideoDriverBindingStart end Success
0:538  0:000  CsmVideo: New mode: 1 800x600 - blocking that switch
0:538  0:000  CsmVideo: New mode: 1 800x600 - blocking that switch
 
24:080  0:000  EdidDiscovered size=128
24:080  0:000  ------- EDID Table
24:080  0:000  000  |  00  FF  FF  FF  FF  FF  FF  00  05  E3
24:080  0:000  010  |  00  19  01  01  01  01  00  13  01  03
24:080  0:000  020  |  68  29  17  78  2A  EE  D1  A5  55  48
24:080  0:000  030  |  9B  26  12  50  54  BF  EE  00  31  0A
24:080  0:000  040  |  61  4C  01  01  01  01  01  01  01  01
24:080  0:000  050  |  01  01  01  01  66  21  56  AA  51  00
24:080  0:000  060  |  1E  30  46  8F  33  00  9D  EA  10  00
24:080  0:000  070  |  00  1E  66  21  50  B0  51  00  1B  30
24:080  0:000  080  |  40  70  36  00  22  13  00  00  00  1E
24:080  0:000  090  |  00  00  00  FD  00  37  4B  1E  51  09
24:080  0:000  100  |  00  0A  20  20  20  20  20  20  00  00
24:080  0:000  110  |  00  FC  00  46  31  39  0A  20  20  20
24:080  0:000  120  |  20  20  20  20  20  20  00  B1
24:081  0:001  read_nVidia_ROM
24:081  0:000  Using PRAMIN fixups
24:215  0:133  PROM
24:439  0:223  version 82.07.25.00.6B
24:439  0:000  nVidia Gigabyte GeForce GTX 750 Ti  2048MB NV117 [10DE:1380] :: PciRoot(0x0)\Pci(0x1,0x0)\Pci(0x0,0x0) => device #1
24:439  0:000  Nvidia: VideoPorts: user defined from config.plist: 4
24:439  0:000  Nvidia: BootDisplay: 2
24:439  0:000  default NVCAP: 04000000-00000600-19000000-00000007-00000000
24:439  0:000   setting specified layout-id=1 (0x1)
24:440  0:000  stringlength = 3820
24:440  0:000  CurrentMode: Width=1024 Height=768
24:440  0:000  Beginning FSInjection
FSInjectionInstall ...
 
24:686  0:054    Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext
24:698  0:011    Extra kext: EFI\CLOVER\kexts\Other\NvidiaGraphicsFixup.kext
24:707  0:009    Extra kext: EFI\CLOVER\kexts\Other\NVWebDriverLibValFix.kext
 
25:075  0:009    Extra kext: EFI\CLOVER\kexts\10.12\Lilu.kext
25:086  0:010    Extra kext: EFI\CLOVER\kexts\10.12\NvidiaGraphicsFixup.kext
Link to comment
Share on other sites

May I change my current version Clover_v2.4k_r4104 ?

 

After upgrade to 10.13 17A344b 

 

Can't see my existing recovery partition when i boot in Clover :

 

dev/disk3 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +119.2 GB   disk3
                                 Physical Store disk0s2
   1:                APFS Volume Macintosh-HD            33.0 GB    disk3s1
   2:                APFS Volume Preboot                 29.4 MB    disk3s2
   3:                APFS Volume Recovery                519.6 MB   disk3s3
   4:                APFS Volume VM                      2.1 GB     disk3s4

 
I use 
Link to comment
Share on other sites

Its not this?

 

0:100 0:000 - GFX: Model=Gigabyte GeForce GTX 750 Ti family 117 (Nvidia)

0:100 0:000 PCI (00|01:00.01) : 10DE 0FBC class=040300

0:100 0:000 - HDMI Audio:

0:100 0:000 PCI (00|00:16.00) : 8086 1C3A class=078000

0:100 0:000 PCI (00|00:16.01) : FFFF FFFF class=FFFFFF

0:100 0:000 PCI (00|00:1A.00) : 8086 1C2D class=0C0320

0:100 0:000 PCI (00|00:1B.00) : 8086 1C20 class=040300

0:100 0:000 PCI (00|00:1C.00) : 8086 1C10 class=060400

0:100 0:000 PCI (00|00:1C.01) : 8086 1C12 class=060400

0:100 0:000 PCI (00|03:00.00) : 168C 002B class=028000

 

0:210 0:000 Video driver loaded: disconnect Success

0:287 0:076 Searching for invalid DiskIo BY_DRIVER connects: not found, all ok

0:287 0:000 VideoBiosPatchNativeFromEdid:

0:287 0:000 Bios: nVidia, nv_data_table_offset: 0x28B, nv_data_table: 0xC028D, std_vesa: 0xC438E, nv_mode_table: 0xC4393, mode_table_size: 0x10

0:287 0:000 VideoBiosPatchInit(LegacyRegion = Success) = Success

0:287 0:000 VideoBiosUnlock: unlocked

0:288 0:001 Patching: BT_NVDA

0:288 0:000 Parse Edid: descriptor block 0 is timing descriptor (h_active: 1366, v_active: 768, h_sync_offset: 70, h_sync_width: 143, h_blanking: 426, v_blanking: 30, pixel_clock: 8550, v_sync_offset: 3, v_sync_width: 3)

0:288 0:000 the patch is not ready for the desired resolution

0:288 0:000 VideoBiosLock: Success

0:305 0:016 CsmVideoDriverBindingStart

0:305 0:000 mixed support=40010

0:305 0:000 Controller is [030000]

0:305 0:000 Check for VBE

0:349 0:044 found Detail Timing 1366x768

0:349 0:000 found Detail Timing 1360x768

0:357 0:008 0 640x480 attr=3BF - ok, edid+, 640x480, working, highest, pref=0

0:358 0:001 1 800x600 attr=3BF - ok, edid+, 800x600, working, highest, pref=1

0:360 0:001 2 1024x768 attr=3BF - ok, edid+, 1024x768, working, highest, pref=2

0:361 0:001 3 1280x1024 attr=3BF - ok, edid-

0:369 0:008 4 1600x1200 attr=3BF - ok, edid-

0:369 0:000 CsmVideo: New mode: 2 1024x768 - set

0:538 0:168 - SetMode pref 2 (2) = Success

0:538 0:000 CsmVideoCheckForVbe - Success

0:538 0:000 CsmVideoDriverBindingStart end Success

0:538 0:000 CsmVideo: New mode: 1 800x600 - blocking that switch

0:538 0:000 CsmVideo: New mode: 1 800x600 - blocking that switch

 

24:080 0:000 EdidDiscovered size=128

24:080 0:000 ------- EDID Table

24:080 0:000 000 | 00 FF FF FF FF FF FF 00 05 E3

24:080 0:000 010 | 00 19 01 01 01 01 00 13 01 03

24:080 0:000 020 | 68 29 17 78 2A EE D1 A5 55 48

24:080 0:000 030 | 9B 26 12 50 54 BF EE 00 31 0A

24:080 0:000 040 | 61 4C 01 01 01 01 01 01 01 01

24:080 0:000 050 | 01 01 01 01 66 21 56 AA 51 00

24:080 0:000 060 | 1E 30 46 8F 33 00 9D EA 10 00

24:080 0:000 070 | 00 1E 66 21 50 B0 51 00 1B 30

24:080 0:000 080 | 40 70 36 00 22 13 00 00 00 1E

24:080 0:000 090 | 00 00 00 FD 00 37 4B 1E 51 09

24:080 0:000 100 | 00 0A 20 20 20 20 20 20 00 00

24:080 0:000 110 | 00 FC 00 46 31 39 0A 20 20 20

24:080 0:000 120 | 20 20 20 20 20 20 00 B1

24:081 0:001 read_nVidia_ROM

24:081 0:000 Using PRAMIN fixups

24:215 0:133 PROM

24:439 0:223 version 82.07.25.00.6B

24:439 0:000 nVidia Gigabyte GeForce GTX 750 Ti 2048MB NV117 [10DE:1380] :: PciRoot(0x0)\Pci(0x1,0x0)\Pci(0x0,0x0) => device #1

24:439 0:000 Nvidia: VideoPorts: user defined from config.plist: 4

24:439 0:000 Nvidia: BootDisplay: 2

24:439 0:000 default NVCAP: 04000000-00000600-19000000-00000007-00000000

24:439 0:000 setting specified layout-id=1 (0x1)

24:440 0:000 stringlength = 3820

24:440 0:000 CurrentMode: Width=1024 Height=768

24:440 0:000 Beginning FSInjection

FSInjectionInstall ...

 

24:686 0:054 Extra kext: EFI\CLOVER\kexts\Other\Lilu.kext

24:698 0:011 Extra kext: EFI\CLOVER\kexts\Other\NvidiaGraphicsFixup.kext

24:707 0:009 Extra kext: EFI\CLOVER\kexts\Other\NVWebDriverLibValFix.kext

 

25:075 0:009 Extra kext: EFI\CLOVER\kexts\10.12\Lilu.kext

25:086 0:010 Extra kext: EFI\CLOVER\kexts\10.12\NvidiaGraphicsFixup.kext

What is log with clover revision?

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites

What is log with clover revision?

 

나의 LG-F800S 의 Tapatalk에서 보냄

0:100  0:100  MemLog inited, TSC freq: 2892702838
0:100  0:000  
0:100  0:000  Now is 15.8.2017,  1:34:10 (GMT)
0:100  0:000  Starting Clover revision: 4166 on American Megatrends EFI
0:100  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.12.6 | XCODE: 8.0]

 

0:100  0:000  SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,644D2929-BCC3-429C-95DF-FE597AA3FE28,0x28,0x64000) @BD07318
Link to comment
Share on other sites

0:100 0:100 MemLog inited, TSC freq: 2892702838

0:100 0:000

0:100 0:000 Now is 15.8.2017, 1:34:10 (GMT)

0:100 0:000 Starting Clover revision: 4166 on American Megatrends EFI

0:100 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D CHECK_FLAGS -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.12.6 | XCODE: 8.0]

 

0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1F,0x2)\Sata(0x0,0xFFFF,0x0)\HD(1,GPT,644D2929-BCC3-429C-95DF-FE597AA3FE28,0x28,0x64000) @BD07318

Your original ram size 2048 right?

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites

Hi

new platformdata works, except platformfeatures

it auto set 0xffff although according to platformdata.c it should be 0x01 for iMac15,1

my config doesn't have any smbios settings except 

ProductName iMac15,1

 

Thanks for all the great work you guys doing.

post-221558-0-62542200-1502819376_thumb.png

  • Like 2
Link to comment
Share on other sites

Hi

new platformdata works, except platformfeatures

it auto set 0xffff although according to platformdata.c it should be 0x01 for iMac15,1

my config doesn't have any smbios settings except

ProductName iMac15,1

 

Thanks for all the great work you guys doing.

I disabled before to use in the future.

Right now, open time.

 

Thanks

 

나의 LG-F800S 의 Tapatalk에서 보냄

Link to comment
Share on other sites

One small bug to report, when selecting inject ATI=true for AMD RX Vega 64 it does not load proper name in about this Mac. The clover menu shows the correct info for video card but it doesn't appear to inject anything. It's just cosmetic but may be an issue if injection is needed for Framebuffer or port selections for some reason.

Link to comment
Share on other sites

Hi. Could you please share the link of X79PlatformPlugin.kext? I may check it further. And, if you prefer kext injection, then you could also use CPUFriend. (Sorry I'm on my mobile now)

 

 

http://www.insanelymac.com/forum/topic/312859-sandy-bridge-e-ivy-bridge-e-power-management-1012-beta/

 

You know what they say the way kexts are loaded in a certain order of things and the way ACPI management works but I don't have an issue placing this kext in Clover/Kexts.  I believe it can be in go in /L/E and not just /S/L/E.

Link to comment
Share on other sites

http://www.insanelymac.com/forum/topic/312859-sandy-bridge-e-ivy-bridge-e-power-management-1012-beta/

 

You know what they say the way kexts are loaded in a certain order of things and the way ACPI management works but I don't have an issue placing this kext in Clover/Kexts.  I believe it can be in go in /L/E and not just /S/L/E.

First of all thanks for the link.

If you put such dummy kext into Clover kext folder, it will simply be ignored by the kernel due to the existence of vanilla X86PlatformPlugin located in "/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext".

/L/E is basically the same as /S/L/E but according to some documents, 3rd-party kexts should be in the former and better to leave the latter untouched.

 

Also. I checked the kext, there was no "FrequencyVectors" entry and thus actually it was just dumb and did nothing. You are still being lack of FrequencyVectors, which is required by XCPM by default.

  • Like 1
Link to comment
Share on other sites

1. It is known. It is problem with installer and APFS, has not been updated, I don't use either so doesn't really come into my realm. IDK if anyone is really maintaining the installer anymore.... Someone needs to edit the installer scripts.

2. Thats just because apparently slice has a zip in his folder and hasn't cleaned it out. It's not really anything but an extra file, just remove it for now. Hopefully he removes it from his build for the next package installer.

3. Well that's not really a bug, the first is SMBIOS, the second is SPD, these are two different detections. You didn't actually show where it was injected later. If it still has changed then I would check to make sure you see "Trusting SMBIOS" in the log after where you selected your boot loader as that's where it is injected.

0:116  0:016  === [ Get Smbios ] ========================================
0:116  0:000  Type 16 Index = 0
0:116  0:000  Total Memory Slots Count = 2
0:116  0:000  Type 17 Index = 0
0:116  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:116  0:000  SmbiosTable.Type17->Size = 8192MB
0:116  0:000  SmbiosTable.Type17->Bank/Device = DIMM A DIMM A
0:116  0:000  SmbiosTable.Type17->Vendor = SK Hynix
0:116  0:000  SmbiosTable.Type17->SerialNumber = 12161215
0:116  0:000  SmbiosTable.Type17->PartNumber = HMA41GS6AFR8N-TF    
0:116  0:000  Type 17 Index = 1
0:116  0:000  SmbiosTable.Type17->Speed = 2133MHz
0:116  0:000  SmbiosTable.Type17->Size = 8192MB
0:116  0:000  SmbiosTable.Type17->Bank/Device = DIMM B DIMM B
0:116  0:000  SmbiosTable.Type17->Vendor = SK Hynix
0:116  0:000  SmbiosTable.Type17->SerialNumber = 12121212
0:116  0:000  SmbiosTable.Type17->PartNumber = HMA41GS6AFR8N-TF    
0:116  0:000  Boot status=0
0:116  0:000  Running on: 'XPS 15 9550' with board '0N7TVV'
0:866  0:000  === [ ScanSPD ] ===========================================
0:866  0:000  SMBus device : 8086 A123 class=0C0500 status=Success
0:866  0:000  SMBus CmdReg: 0x3
0:866  0:000  Scanning SMBus [8086:A123], mmio: 0xDD132004, ioport: 0xF040, hostc: 0x11
0:866  0:000  Slots to scan [8]...
0:866  0:000  SPD[0]: Type 12 @0x50
0:884  0:017  Unknown vendor bank=0x80 code=0xAD
0:884  0:000  Not using XMP because it is not present
0:884  0:000  DDR speed 2132MHz
0:884  0:000  Slot: 0 Type 26 8192MB 2132MHz Vendor=NoName PartNo=HMA41GS6AFR8N-TF SerialNo=0301070A0303080A
0:885  0:000  SPD[2]: Type 12 @0x52
0:903  0:017  Unknown vendor bank=0x80 code=0xAD
0:903  0:000  Not using XMP because it is not present
0:903  0:000  DDR speed 2132MHz
0:903  0:000  Slot: 2 Type 26 8192MB 2132MHz Vendor=NoName PartNo=HMA41GS6AFR8N-TF SerialNo=0301070A0403090D
10:715  0:000  === [ PatchSmbios ] =======================================
10:715  0:000  insert table 9 for dev 0:0
10:716  0:000  Trusting SMBIOS...
10:716  0:000  Detected alternating SMBIOS channel banks
10:716  0:000  Channels: 2
10:716  0:000  Interleave: 0 2 1 3 4 6 5 7 8 10 9 11 12 14 13 15 16 18 17 19 20 22 21 23
10:716  0:000   partNum=HMA41GS6AFR8N-TF    
10:716  0:000  SMBIOS Type 17 Index = 0 => 0 0:
10:716  0:000  BANK 0 DIMM0 2133MHz 8192MB
10:716  0:000   partNum=HMA41GS6AFR8N-TF    
10:716  0:000  SMBIOS Type 17 Index = 1 => 1 2:
10:716  0:000  BANK 1 DIMM0 2133MHz 8192MB
10:716  0:000  mTotalSystemMemory = 16384
10:716  0:000  NumberOfMemoryDevices = 2
10:716  0:000  Type20[0]->End = 0x7FFFFF, Type17[0] = 0x2000
10:716  0:000  Type20[1]->End = 0xFFFFFF, Type17[1] = 0x6000
10:716  0:000  Table 131 is present, CPUType=31
10:716  0:000  Change to: 705

post-1140626-0-44646200-1502860954_thumb.png

  • Like 1
Link to comment
Share on other sites

Hi @Slice

Is it possible to add a specific folder for config.plist because sometimes I find myself with 3 or 4 config in the Clover folder Thanks in advance

Hi chris1111,

Did you manage to use multiple configs with a single clover?

Link to comment
Share on other sites

First of all thanks for the link.

If you put such dummy kext into Clover kext folder, it will simply be ignored by the kernel due to the existence of vanilla X86PlatformPlugin located in "/System/Library/Extensions/IOPlatformPluginFamily.kext/Contents/PlugIns/X86PlatformPlugin.kext".

/L/E is basically the same as /S/L/E but according to some documents, 3rd-party kexts should be in the former and better to leave the latter untouched.

 

Also. I checked the kext, there was no "FrequencyVectors" entry and thus actually it was just dumb and did nothing. You are still being lack of FrequencyVectors, which is required by XCPM by default.

 

 

The modification in this kext has to do with something else I can't remember from the top of my head but I though it has something to do with the System Definition being MacMini frequencies/vectors.  I must have it in /L/E.  I will run with and without and get information and post it here.

Link to comment
Share on other sites

I Think I am not figure out how to use it

Thanks  :) I have been wondering about the same thing that to be able to boot from different configs for some time until I was your post. I will try it and see if I can figure out how to use it.

  • Like 1
Link to comment
Share on other sites

I Think I am not figure out how to use it

Ok here is what I found so far, the config will load according to what @apianti suggested, I created two folders inside OEM folder one is named P8H77-M LE and the other one is named Z170X-Gaming 5. upon boot clover will load the config.plist according to the system that I use my USB disk on. here is the log files:

 

If I use the USB disk to boot my Asus rig:

 

 

 

0:121  0:008  EFI\CLOVER\OEM\P8H77-M LE\config.plist loaded: Success

0:137  0:007  === [ Found config plists ] ===============================
0:137  0:000  - config.plist

 

 

 

and here is the log when I use it to boot my Z170X rig:

 

0:110  0:009  EFI\CLOVER\OEM\Z170X-Gaming 5\config.plist loaded: Success
0:124  0:008  === [ Found config plists ] ===============================

0:124  0:000  - config.plist 

 

 

 

I checked both systems after the OS is loaded and the serial numbers are correct which means clover loaded the correct config for each file.

 

I notices that the kext files were not loading at first so I renamed the kext folder inside /EFI/Clover/kext to something else and made a full copy of each system's clover folder inside the OEM and the folders I created. and It worked :)

  • Like 1
Link to comment
Share on other sites

The modification in this kext has to do with something else I can't remember from the top of my head but I though it has something to do with the System Definition being MacMini frequencies/vectors.  I must have it in /L/E.  I will run with and without and get information and post it here.

You claimed that you'd enabled XCPM. Correct?

I did see the purpose of that kext, that is, replacing Macmini6,2's StepContextDict, which is used by AICPUPM, with XCPM it's just useless. So. It makes no difference to install this kext or not.

  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...