Clover General discussion

[apianti]

If the intention is to build Clover without C99, perhaps it should be disabled when building with Xcode. Then you don't have to worry about devs adding code that depend on it.

 

IMHO, Seems ok to rely on tech (C99) that was ratified more than 17 years ago.

 

Not sure what you mean, Xcode uses clang which is forked from GCC 4.2 (earlier versions just use GCC)... It has way more messed up default rules than even GCC, neither actually follows the standard and decides to make a hybrid of C89/90 and C99, just differently. The C89/90 standard should be followed when writing C code, because that's standard C and what compilers should default to without being overridden. Also technically, C99 is dead and withdrawn from both ANSI and ISO in favor of C11. Not very many compilers actually have a full C99 implementation, I only know of GCC. And only like GCC and VS support C11, I know some versions don't support the full implementation but I'm pretty sure they both have full now. You should not be targeting anything but C89/90 unless you need a specific language feature, which is not needed, so should be using standard C here.

[Sherlocks]

Hello. I want to gather nvidia graphics information.

 

Anyone has "Kepler" or "Maxwell" or "Pascal" NVIDIA graphics card?

 

If has one of them, please check injection nvidia on graphic in config, then get clover fulllog and upload it.

 

Thanks in advance

 

나의 LG-F800S 의 Tapatalk에서 보냄

[RehabMan]

Not sure what you mean, Xcode uses clang which is forked from GCC 4.2 (earlier versions just use GCC)... It has way more messed up default rules than even GCC, neither actually follows the standard and decides to make a hybrid of C89/90 and C99, just differently. The C89/90 standard should be followed when writing C code, because that's standard C and what compilers should default to without being overridden. Also technically, C99 is dead and withdrawn from both ANSI and ISO in favor of C11. Not very many compilers actually have a full C99 implementation, I only know of GCC. And only like GCC and VS support C11, I know some versions don't support the full implementation but I'm pretty sure they both have full now. You should not be targeting anything but C89/90 unless you need a specific language feature, which is not needed, so should be using standard C here.

I'm pretty sure I've seen options inside the Xcode project manager to disable C99 (and probably other extensions).

But I'm not familiar enough with the Clover/edk2 build process to find the spot that needs to be changed to disable them.

Nor does it interest me much.

I was just suggesting that if you want devs to stick to a certain subset of the many C-standards, it should be enforced by the build process.

[apianti]

I'm pretty sure I've seen options inside the Xcode project manager to disable C99 (and probably other extensions).

But I'm not familiar enough with the Clover/edk2 build process to find the spot that needs to be changed to disable them.

Nor does it interest me much.

I was just suggesting that if you want devs to stick to a certain subset of the many C-standards, it should be enforced by the build process.

 

How can I enforce how they build something?? Even if I changed the build scripts, they could just not use them, that's part of the problem really. I think that maybe they should just use standard C. I don't think it's very useful if you start using C99 or C11, since that source cannot be built by every compiler but C89/90 can. Like if you take any C class in school they certainly aren't teaching you C99 or C11. When you change those options in Xcode, it doesn't change system wide, it just changes the arguments passed to clang/GCC when compiling. So maybe, probably, by default Xcode might use C99 by passing it as an argument. I have never used Xcode to directly build a C source though.... And the EDK2 build system uses a tools_def.txt file to define build rules, I'm sure that everyone uses different ones. There's a default from EDK2, one in clover, pretty sure that each tool to help build uses its own too...

[RehabMan]

How can I enforce how they build something?? Even if I changed the build scripts, they could just not use them, that's part of the problem really. I think that maybe they should just use standard C. I don't think it's very useful if you start using C99 or C11, since that source cannot be built by every compiler but C89/90 can. Like if you take any C class in school they certainly aren't teaching you C99 or C11. When you change those options in Xcode, it doesn't change system wide, it just changes the arguments passed to clang/GCC when compiling. So maybe, probably, by default Xcode might use C99 by passing it as an argument. I have never used Xcode to directly build a C source though.... And the EDK2 build system uses a tools_def.txt file to define build rules, I'm sure that everyone uses different ones. There's a default from EDK2, one in clover, pretty sure that each tool to help build uses its own too...

Hmm... I think most people using this to build Clover:

https://github.com/Micky1979/Build_Clover.git

[apianti]

Hmm... I think most people using this to build Clover:

https://github.com/Micky1979/Build_Clover.git

 

Yeah... That script I think uses the clover tools_def.txt but I'm not sure, I don't use that because I can just run all the stuff separately. Which means that changing the clover tools_def.txt does nothing in that case unless I specifically use it. I just need people contributing to the project to code in standard C, that's all. There's not really any way to "force" not using extensions because the person could just build without whatever was "forcing" in the build process, like by using a different tools_def.txt. I don't see why it's so hard to actually code in C the way that is expected. It's not like it's any harder, it's just putting declarations before any statements in any scope. But more importantly, use the correct types - that's a big problem with the extensions, automatic typecasting. Currently the patchers (and probably more), all have typecasting errors in various directions. That's how bugs can develop, when a type is promoted or truncated but still expected to be the original size...

[gujiangjiang]

I found 3 bugs in clover.

 

1.While we use apfs partition disk our disk will have disk0 and disk1 but clover cant recognize the real efi partition because when we use apfs partition the real efi partition is still disk0s1 but clover will recognize efi to disk1s1 this is an apfs partition so clover will always install failed and i had reported this bug in june but still cant be fixed till now so i mentioned again.

 

2.New clover version will create a CLOVERX64.EFI.ZIP file in EFI/Clover folder and still exist in Clover 4152.

 

3.I have a bug in recognize my menory vendor in system prefrence and all the memory vendor show NoName and it shows error SN number but i dont know how to fix this.

 

The clover log shows it recognized corrrectly first but when write into spd shows UnKnow.

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:841  0:016  === [ GetMacAddress ] =====================================
0:841  0:000  === [ ScanSPD ] ===========================================
0:841  0:000  SMBus device : 8086 A123 class=0C0500 status=Success
0:841  0:000  SMBus CmdReg: 0x3
0:841  0:000  Scanning SMBus [8086:A123], mmio: 0xDD132004, ioport: 0xF040, hostc: 0x11
0:841  0:000  Slots to scan [8]...
0:842  0:000  SPD[0]: Type 12 @0x50
0:859  0:017  Unknown vendor bank=0x80 code=0xAD
0:859  0:000  Not using XMP because it is not present
0:859  0:000  DDR speed 2132MHz
0:859  0:000  Slot: 0 Type 26 8192MB 2132MHz Vendor=NoName PartNo=HMA41GS6AFR8N-TF SerialNo=0301070A0303080A
0:860  0:000  SPD[2]: Type 12 @0x52
0:878  0:017  Unknown vendor bank=0x80 code=0xAD
0:878  0:000  Not using XMP because it is not present
0:878  0:000  DDR speed 2132MHz
0:878  0:000  Slot: 2 Type 26 8192MB 2132MHz Vendor=NoName PartNo=HMA41GS6AFR8N-TF SerialNo=0301070A0403090D

[apianti]

 

I found 3 bugs in clover.

 

1.While we use apfs partition disk our disk will have disk0 and disk1 but clover cant recognize the real efi partition because when we use apfs partition the real efi partition is still disk0s1 but clover will recognize efi to disk1s1 this is an apfs partition so clover will always install failed and i had reported this bug in june but still cant be fixed till now so i mentioned again.

 

2.New clover version will create a CLOVERX64.EFI.ZIP file in EFI/Clover folder and still exist in Clover 4152.

 

3.I have a bug in recognize my menory vendor in system prefrence and all the memory vendor show NoName and it shows error SN number but i dont know how to fix this.

 

The clover log shows it recognized corrrectly first but when write into spd shows UnKnow.

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:841  0:016  === [ GetMacAddress ] =====================================
0:841  0:000  === [ ScanSPD ] ===========================================
0:841  0:000  SMBus device : 8086 A123 class=0C0500 status=Success
0:841  0:000  SMBus CmdReg: 0x3
0:841  0:000  Scanning SMBus [8086:A123], mmio: 0xDD132004, ioport: 0xF040, hostc: 0x11
0:841  0:000  Slots to scan [8]...
0:842  0:000  SPD[0]: Type 12 @0x50
0:859  0:017  Unknown vendor bank=0x80 code=0xAD
0:859  0:000  Not using XMP because it is not present
0:859  0:000  DDR speed 2132MHz
0:859  0:000  Slot: 0 Type 26 8192MB 2132MHz Vendor=NoName PartNo=HMA41GS6AFR8N-TF SerialNo=0301070A0303080A
0:860  0:000  SPD[2]: Type 12 @0x52
0:878  0:017  Unknown vendor bank=0x80 code=0xAD
0:878  0:000  Not using XMP because it is not present
0:878  0:000  DDR speed 2132MHz
0:878  0:000  Slot: 2 Type 26 8192MB 2132MHz Vendor=NoName PartNo=HMA41GS6AFR8N-TF SerialNo=0301070A0403090D

 

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.

[gujiangjiang]

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.

 

Here are the full clover boot.log.

bootlog.log.txt.zip

[Badruzeus]

Hello. I want to gather nvidia graphics information.

 

Anyone has "Kepler" or "Maxwell" or "Pascal" NVIDIA graphics card?

Sorry, my 2nd Gen. laptop with SingleNvidia doesn't use such graphics, but since U've also committed this:

[4164] "Update id of NVIDIA Fermi/Kepler/Maxwell/Pascal families",

...so I give U some reports from another Nvidia Fermi variant: GT520M (10de:1050 aka GF119M).

 

Using 10.13 Beta 5 (17A330h) with Clover v2.4k r4166 all are still good. Some minor issues that I (actually) don't really care are:

1. with InjectNvidia=False & w/o @rehabman's GT520M DSDT patch, (Native) my Graphics on ATM shows only 1023MB VRam.

2. with InjectNvidia=True & w/o GT520M DSDT patch it shows "Asus GT520M" (NP, as seen on nvidia.c Platform; 0x1043 is detected as Asus, so the graphics injection is working well). VRam shown properly as it is: 1024MB.

3. with InjectNvidia=False and using GT520M DSDT patch, ATM shows my graphics as Nvidia and 1024MB VRam (it's just "cosmetics" for sure  )

 

Overall, is still good (for now) since my QE/CI works well. For El Capitan I stick with No. 3 but using Nvidia Web Driver. Minor issues are exactly same. Thanks.

 

#EDIT: Plz ignore my 3rd party kexts logs from EFI folder except FakeSMC & PS2, since some of them (maybe) obsolete or even not working under 10.13. 

#EDIT2: Sorry, forgot to mention: both on 10.13 Beta or 10.11.6 use MBP10,1 as SMBios. Cheers!

1. bootlog-NoInject-No_GFX0_DSDT.txt

2. bootlog-InjectNvidia.txt

3. bootlog.log-GFX0-DSDT_Patch.txt

[Cyberdevs]

Hello. I want to gather nvidia graphics information.

 

Anyone has "Kepler" or "Maxwell" or "Pascal" NVIDIA graphics card?

 

If has one of them, please check injection nvidia on graphic in config, then get clover fulllog and upload it.

 

Thanks in advance

Here is the bootlog for 1070 with and without injection

bootlog-Inject nVidia.txt.zip

Bootlog-No Injection.txt.zip

[Sherlocks]

Sorry, my 2nd Gen. laptop with SingleNvidia doesn't use such graphics, but since U've also committed this:

[4164] "Update id of NVIDIA Fermi/Kepler/Maxwell/Pascal families",

...so I give U some reports from another Nvidia Fermi variant: GT520M (10de:1050 aka GF119M).

 

Using 10.13 Beta 5 (17A330h) with Clover v2.4k r4166 all are still good. Some minor issues that I (actually) don't really care are:

1. with InjectNvidia=False & w/o @rehabman's GT520M DSDT patch, my Graphics on ATM shows only 1023MB VRam.

2. with InjectNvidia=True & w/o GT520M DSDT patch it shows "Asus GT520M" (NP, as seen on nvidia.c Platform; 0x1043 is detected as Asus, so the graphics injection is working well). VRam shown properly as it is: 1024MB.

3. with InjectNvidia=False and using GT520M DSDT patch, ATM shows my graphics as Nvidia and 1024MB VRam (it's just "cosmetics" for sure )

 

Overall, is still good (for now) since my QE/CI works well. For El Capitan I stick with No. 3 but using Nvidia Web Driver. Minor issues are exactly same. Thanks.

 

#EDIT: Plz ignore my 3rd party kexts logs from EFI folder except FakeSMC & PS2, since some of them (maybe) obsolete or even not working under 10.13.

First of all, thank you for detail test.

Ram size issue is just cosmetic.

I see your all log. Log fine that my think and theroy.

 

I don't know exactly El capitan issue.

I have a 525m model. I can success install and qc/ei on el capitan.

 

Thanks

 

나의 LG-F800S 의 Tapatalk에서 보냄

Here is the bootlog for 1070 with and without injection

I will send pm. Check please thanks.

 

나의 LG-F800S 의 Tapatalk에서 보냄

[Wppley2]

Hi all, hi Sherlocks! What you ask us is the log with 10.13 or 10.12.X too. I have an ssdt to inject my GTX 750 Ti. I need to take out my ssdt end inject Nvidia with Clover config or with ssdt is good to you?

[Sherlocks]

Hi all, hi Sherlocks! What you ask us is the log with 10.13 or 10.12.X too. I have an ssdt to inject my GTX 750 Ti. I need to take out my ssdt end inject Nvidia with Clover config or with ssdt is good to you?

For test

1. Without ssdt gfx injection

2. Just check nvidia injection on graphic in config.plist

3. Get full log

 

No related macos version. Test on you want

Thanks.

 

나의 LG-F800S 의 Tapatalk에서 보냄

[oSxFr33k]

No. Ivy-E is an XCPM unsupported model. AICPUPM should be the best solution I guess. (Note that there's even AICPUPM workaround mode for Ivy-E like they did for MacPro6,1, this is the only way to get a frequency lower than 1600Mhz with AICPUPM as far as I know) Although XCPM could also be enabled properly on Ivy-E in principle...

 

True.

Sigh... MP5,1 doesn't even have X86 support, so the data is missing undoubtedly. Maybe it's better to fill the data, for example something from MP6,1. (Remove pmspFile to prevent KP)

If you prefer Clover kext injection for that, I think CPUFriend might help you.

 

XCPM working fine here with MacPro6,1 model and X79PlatformPlugin kext.   So basically this is not something expected for Clover, there has to be a kext for this model CPU.

[PMheart]

XCPM working fine here with MacPro6,1 model and X79PlatformPlugin kext.   So basically this is not something expected for Clover, there has to be a kext for this model CPU.

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)

[xtddd]

Sorry, my 2nd Gen. laptop with SingleNvidia doesn't use such graphics, but since U've also committed this:

[4164] "Update id of NVIDIA Fermi/Kepler/Maxwell/Pascal families",

...so I give U some reports from another Nvidia Fermi variant: GT520M (10de:1050 aka GF119M).

 

Using 10.13 Beta 5 (17A330h) with Clover v2.4k r4166 all are still good. Some minor issues that I (actually) don't really care are:

1. with InjectNvidia=False & w/o @rehabman's GT520M DSDT patch, (Native) my Graphics on ATM shows only 1023MB VRam.

2. with InjectNvidia=True & w/o GT520M DSDT patch it shows "Asus GT520M" (NP, as seen on nvidia.c Platform; 0x1043 is detected as Asus, so the graphics injection is working well). VRam shown properly as it is: 1024MB.

3. with InjectNvidia=False and using GT520M DSDT patch, ATM shows my graphics as Nvidia and 1024MB VRam (it's just "cosmetics" for sure  )

 

Overall, is still good (for now) since my QE/CI works well. For El Capitan I stick with No. 3 but using Nvidia Web Driver. Minor issues are exactly same. Thanks.

 

#EDIT: Plz ignore my 3rd party kexts logs from EFI folder except FakeSMC & PS2, since some of them (maybe) obsolete or even not working under 10.13. 

#EDIT2: Sorry, forgot to mention: both on 10.13 Beta or 10.11.6 use MBP10,1 as SMBios. Cheers!

hi,,my laptop is also 2nd.thinkapd w520.... the graphic of nvidia quadro 1000m has no QE/CI on 10.13 beta1 but works well on 10.12.6 with dsdt patch.

[LockDown]

nvram.plist  has wrong timestamp...Why is it the time CREATED is 8hrs "behind" MODIFIED?

 

Also, it would be nice to hide /nvram.plist "if" its in the macos root

[Balamut]

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.

[Wppley2]

Hello. I want to gather nvidia graphics information.

 

Anyone has "Kepler" or "Maxwell" or "Pascal" NVIDIA graphics card?

 

If has one of them, please check injection nvidia on graphic in config, then get clover fulllog and upload it.

 

Thanks in advance

 

나의 LG-F800S 의 Tapatalk에서 보냄

Here is your request, sir 

bootlog.log.txt

[Sherlocks]

Here is your request, sir

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

 

나의 LG-F800S 의 Tapatalk에서 보냄

[xtddd]

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

 

나의 LG-F800S 의 Tapatalk에서 보냄

hi..my laptop's problem with nvidia quadro 1000m of high sierra can be resolved?

[Matthew82]

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

[Wppley2]

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

[Loloflat6]

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