Jump to content
30960 posts in this topic

Recommended Posts

3 hours ago, Jief_Machak said:

Not sure what you mean. You're not obliged to create folders you don't need. So why "empty folders" ?

Sorry but you got it well, and the point is just the same:

--> Question: why the installer did not create these new directories?

3 hours ago, Jief_Machak said:

Just create the one you need

agreed.

--> inplicit answere: There is no need to create any folder because nor the package nor the app knows what you need. Create ones you need manually!

 

We just have the same opinion, and my post was just to let understand that create them by the installer is not possible.... unless you create hundreds of directories to cover any supported OSes.

Edited by vector sigma
  • Like 2
4 hours ago, vector sigma said:

Sorry but you got it well, and the point is just the same:

--> Question: why the installer did not create these new directories?

agreed.

--> inplicit answere: There is no need to create any folder because nor the package nor the app knows what you need. Create ones you need manually!

 

We just have the same opinion, and my post was just to let understand that create them by the installer is not possible.... unless you create hundreds of directories to cover any supported OSes.

Ah ok. I didn't realise it was about the installer. I must have missed a post.

 

NOTE Ideally, these directory wouldn't be used. For few years, I had the same clover for install recovery and normal boot. VoodooI2C.kext doesn't work for install, that's why I made that possibility.

  • Like 1

43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0_normal

10.5.8.0 seems wrong 

On 12/21/2019 at 10:22 AM, Florin9doi said:


43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5_normal
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0
43:194  0:000  Preparing kexts injection for arch=i386 from EFI\CLOVER\OEM\VMware7,1\kexts\10.5.8.0_normal

10.5.8.0 seems wrong 

Sure it is. I'll have a look soon.

2 hours ago, luky35 said:

I like the name of this theme in the picture, or where I find it

 

Thanks,

 

It's a @Badruzeus  theme called: Mojave. You can find it via CloverThemeManager (I think) or Badruzeus repo on GitHub ('MyCloverThemes'). I only customize the logo :)

Did we still need "FSInject.efi" in CLOVER?? When i install Clover, i read the description of FSInject.efi and it's written "Provide injection of kernel extensions from Clover folder.". Honestly, i can boot without this driver,, So when i must use it???

 

image.png.d3e8b3a3bc9b43c5bab13f41c09ffab6.png

 

I just use this driver right now


image.png.c454f587e8a46badb08f1ab7b961365a.png

  • Like 1
11 hours ago, Andres ZeroCross said:

Did we still need "FSInject.efi" in CLOVER?? When i install Clover, i read the description of FSInject.efi and it's written "Provide injection of kernel extensions from Clover folder.". Honestly, i can boot without this driver,, So when i must use it???

 

 

 

I just use this driver right now


 

The description is not correct.

Actually FSInject allows you to ForceLoad kexts form /S/L/E

  • Like 1
  • Thanks 2
21 hours ago, Slice said:

The description is not correct.

Actually FSInject allows you to ForceLoad kexts form /S/L/E

What does ForceLoad mean? Does it load them like the kexts in the Clover folder? Does it force load all the kexts in /S/L/E? None from /L/E?

2 hours ago, joevt said:

What does ForceLoad mean? Does it load them like the kexts in the Clover folder? Does it force load all the kexts in /S/L/E? None from /L/E?

Original comment from Dmazar is here Post#30 Using extra kexts and skipping kernelcache

But OS changed and rules changed.

We can write

	<key>KernelAndKextPatches</key>
	<dict>
		<key>ForceKextsToLoad</key>
		<array>
			<string>\System\Library\Extensions\AMDRadeonX4000.kext</string>
		</array>

to patch the kext on the fly. Same for /L/E. Volume assumed same as boot.efi used to load cache.

It is needed because some system kexts are not present in kernelcache because they are not loaded by default.

  • Like 2

I didn't see any new kext structure folder  on Clover_v2.5k_r5101

second issue I have 

my VoodoI2C touchpad don't work during installation but with Opencore work my touchpad during installation

my touch was working earlier version of clover boot loader I think this is kext injection bug

when I install VoodoI2C.kext in system L/E then work fine

anyone can tell me about that

  • Like 1

The installer doesn’t create these folders. Create some if you need.

VoodooI2c is one of the reason I’ve created these folder possibility. So I confirm the voodooI2c not working in installer is NOT because of these new folder name.

just create a 10_install folder and put the complete version of voodoops2controller in it and you’ll be able to install.

5 hours ago, Jief_Machak said:

The installer doesn’t create these folders. Create some if you need.

VoodooI2c is one of the reason I’ve created these folder possibility. So I confirm the voodooI2c not working in installer is NOT because of these new folder name.

just create a 10_install folder and put the complete version of voodoops2controller in it and you’ll be able to install.

I didn't understand please tell me clearly 

Where can i create 10_install folder

Just now, anmool said:

I didn't understand please tell me clearly 

Where can i create 10_install folder

Try to create it in EFI/CLOVER/ACPI or in EFI/CLOVER/themes <_<. Jokes aside, I would give it a chance in EFI/CLOVER/kexts :).

  • Like 1
On 12/20/2019 at 11:08 AM, n.d.k said:

You don't have to rename anything.  Ok to make it clear for someone not understand it well.

 

- Create a file name VolumeLabel.txt on Desktop

- Open it with text editor and write #EFI or any name you want with # in front on the first line, then save it.

- Mount the EFI partition (the one you install the clover on) and open up Finder click EFI on the left pane.

- Drag the VolumeLabel.txt file to it (the root, not into the EFI folder)

- Rename VolumeLabel.txt to .VolumeLabel.txt and it will disappear from the Finder since it's a hidden file name.

Done!

 In Finder, you can use Shift + Command + . to show/hide the hidden files. 

It still says Clover Boot from EFI when I do the following:

2013505507_ScreenShot2019-12-26at1_08_55PM.jpg.a14382691f9c434eb7e47b7b65127615.jpg

3 hours ago, anmool said:

I didn't understand please tell me clearly 

Where can i create 10_install folder

Снимок экрана 2019-12-26 в 21.31.12.png

22 minutes ago, pkdesign said:

It still says Clover Boot from EFI when I do the following:

2013505507_ScreenShot2019-12-26at1_08_55PM.jpg.a14382691f9c434eb7e47b7b65127615.jpg

Is it Clover version from latest github sources? Not from release.

  • Thanks 1

Originally I used Hackintool to download Clover 5101. not sure hwre they get it from. Then I checked https://github.com/CloverHackyColor/CloverBootloader  and downloaded from there. Both have the same result.

 

BTW, it also reverts to "Christmas" theme which is VERY annoying.

Edited by pkdesign
20 hours ago, Slice said:

Снимок экрана 2019-12-26 в 21.31.12.png

Is it Clover version from latest github sources? Not from release.

VoodoI2C.kext is not working during installation but with Opencore work 

VoodooI2C was working fine during installation earlier version of clover

i think that something has been changed in clover bootloader

Anyone have idea

5 hours ago, anmool said:

VoodoI2C.kext is not working during installation but with Opencore work 

VoodooI2C was working fine during installation earlier version of clover

i think that something has been changed in clover bootloader

Anyone have idea

You should modify VoodooI2C.kext/Contents/Info.plist to have this line

Снимок экрана 2019-12-27 в 23.28.36.png

2 hours ago, Slice said:

You should modify VoodooI2C.kext/Contents/Info.plist to have this line

Снимок экрана 2019-12-27 в 23.28.36.png

on latest VoodoI2C.kext v2.3  already have modified with OSBundleRequired Root

I tried already didn't get work during installation I think this is clover issue 

on OpenCore bootloader is working fine

 

On 11/11/2019 at 7:53 PM, Pene said:

 

Hi Slice,

 

Thank you for the response. But I think I didn't explain myself well.

0Bh is the location of of the "Attributes", not it's content.

The content is newSmbiosTable.Type17->Attributes = 1 in case of Single-Rank DIMMs and newSmbiosTable.Type17->Attributes = 2 in case of Dual-Rank DIMMs.

But this information is *already present* in SMBIOS, without us doing anything special in Clover.

 

He sent me two dmidecodes from a booted Mac, for each case, with the different DIMMs installed. Look:

 

This is the non-working case with the Single-Rank DIMMS: (notice the RANK: 1, it is present in smbios and read from the Attributes address at 0Bh):


Handle 0x1101, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 1
	Type: DDR4
	Type Detail: Synchronous Unbuffered (Unregistered)
	Speed: 2998 MT/s
	Manufacturer: Corsair
	Serial Number: 0000000000000000
	Asset Tag: Not Specified
	Part Number: CMW16GX4M2C3000C15
	Rank: 1
	Configured Clock Speed: 2133 MT/s
	Minimum Voltage: 1.2 V
	Maximum Voltage: 1.2 V
	Configured Voltage: 1.2 V

And this is the non-working case with the Dual-Rank DIMMS: (notice the RANK: 2, it is present in smbios and read from the Attributes address at 0Bh):


Handle 0x1100, DMI type 17, 40 bytes
Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 0
	Type: DDR4
	Type Detail: Synchronous Unbuffered (Unregistered)
	Speed: 3200 MT/s
	Manufacturer: G Skill Intl
	Serial Number: 0000000000000000
	Asset Tag: Not Specified
	Part Number: F4-3200C16-8GTZB
	Rank: 2
	Configured Clock Speed: 2133 MT/s
	Minimum Voltage: 1.2 V
	Maximum Voltage: 1.2 V
	Configured Voltage: 1.2 V

This is the only real difference between the chips.

He has two pairs of chips that it is working OK for install with them (one pair is 2x8GB - GSKILL the other is 2x16GB - CORSAIR). Both of these are working OK for install and both are with "Rank: 2".

He has only one pair with "Rank: 1" (they are more rare I think), but install keeps giving the error with them in all cases, also if using only a single DIMM, also when using both DIMMs.

 

I don't know what we should be doing with this information, I was mentioning it as maybe together we can understand what is going on here...

 

I tried, on my system, to add:

newSmbiosTable.Attributes = 1 

Just to see if it makes me also get the error (as my Rank also was 2) - but the error did not appear on my System (I don't actually have single-rank DIMMs to test with them, so I tried only to fake the rank).

 

There are many reports on the net (at other sites) about this issue, no one mentioned the Rank, but in most cases it was closed by using other DIMMs or moving the DIMMs in other slots (on boards that have more slots). So this is a memory issue, and in my opinion is is somehow related to the Rank. 

 

 

 

 

 

long time no see.

today i went home ofparents. and i checked desktop smbios type 17

Handle 0x1100, DMI type 17, 40 bytes
0000: 11 28 00 11 00 10 ff ff 40 00 40 00 00 20 09 01 
0010: 01 02 1a 80 00 55 08 03 04 00 06 01 00 00 00 00 
0020: 55 08 00 00 00 00 b0 04 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: 2133 MHz (0.5 ns)
	Manufacturer: Samsung
	Serial Number: 090903050F06080A
	Asset Tag: Not Specified
	Part Number: M378A1K43BB1-CPB
	Rank: 1
	Configured Clock Speed: 2133 MHz (0.5 ns)
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  1.200 V

Handle 0x1101, DMI type 17, 84 bytes
0000: 11 54 01 11 00 10 ff ff ff ff ff ff 00 00 09 02 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 2
	Locator: DIMM1
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1102, DMI type 17, 84 bytes
0000: 11 54 02 11 00 10 ff ff ff ff ff ff 00 00 09 03 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 3
	Locator: DIMM2
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1103, DMI type 17, 84 bytes
0000: 11 54 03 11 00 10 ff ff ff ff ff ff 00 00 09 04 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 4
	Locator: DIMM3
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

i can't install 10.14+ now from usb installer. only need to update mojave or catalina from high sierra.

i will test smbios version and memory rank

Edited by Sherlocks
  • Like 1
5 hours ago, Sherlocks said:

 

long time no see.

today i went home ofparents. and i checked desktop smbios type 17


Handle 0x1100, DMI type 17, 40 bytes
0000: 11 28 00 11 00 10 ff ff 40 00 40 00 00 20 09 01 
0010: 01 02 1a 80 00 55 08 03 04 00 06 01 00 00 00 00 
0020: 55 08 00 00 00 00 b0 04 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: 64 bits
	Data Width: 64 bits
	Size: 8192 MB
	Form Factor: DIMM
	Set: 1
	Locator: DIMM0
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: 2133 MHz (0.5 ns)
	Manufacturer: Samsung
	Serial Number: 090903050F06080A
	Asset Tag: Not Specified
	Part Number: M378A1K43BB1-CPB
	Rank: 1
	Configured Clock Speed: 2133 MHz (0.5 ns)
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  1.200 V

Handle 0x1101, DMI type 17, 84 bytes
0000: 11 54 01 11 00 10 ff ff ff ff ff ff 00 00 09 02 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 2
	Locator: DIMM1
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1102, DMI type 17, 84 bytes
0000: 11 54 02 11 00 10 ff ff ff ff ff ff 00 00 09 03 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 3
	Locator: DIMM2
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

Handle 0x1103, DMI type 17, 84 bytes
0000: 11 54 03 11 00 10 ff ff ff ff ff ff 00 00 09 04 
0010: 01 02 00 80 00 00 00 00 00 00 00 00 00 00 00 00 
0020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0030: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
0050: 00 00 00 00 

Memory Device
	Array Handle: 0x1000
	Error Information Handle: No Error
	Total Width: Unknown
	Data Width: Unknown
	Size: No Module Installed
	Form Factor: DIMM
	Set: 4
	Locator: DIMM3
	Bank Locator: BANK 0
	Type: <OUT OF SPEC>
	Type Detail: Synchronous
	Speed: Unknown
	Manufacturer: Not Specified
	Serial Number: Not Specified
	Asset Tag: Not Specified
	Part Number: Not Specified
	Rank: Unknown
	Configured Clock Speed: Unknown
	Minimum voltage:  Unknown
	Maximum voltage:  Unknown
	Configured voltage:  Unknown

i can't install 10.14+ now from usb installer. only need to update mojave or catalina from high sierra.

i will test smbios version and memory rank

 

info.

laptop: everything is okay

desktop: always data error when install macos from usb installer on 10.14+. 

 

okay. tested it.

no effect memory rank part.

i checked my laptop. my laptop single channel ram and needed to add memory info in smbios in config to avoid memory error.

 

i added memory info in config like my laptop.

there is no problem. finally i skipped data error message when install macos catalina from usb installer. i dont know and not sure exact problem.

Edited by Sherlocks
  • Like 2
×
×
  • Create New...