Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
29,866 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted

Unchecking "UEFI only" is absolutely safe operation. You will get more options and nothing dangerous among them.

UEFI boot will work the same way. 

 

 

Yes, I checked the "Install Clover in the ESP" if that what you mean. Or maybe I missed something?

 

 

1. I set the FakeID in boot option on Clover boot screen. 

2. Can guide me to the correct method?

 

Googled "Sound assertion..." and "IOConsoleUsers..." doesn't really help me. Is it a good choice to set the Fake ID for each boot? But this will lead me to the next question; how to make set Fake ID with configurator, and how to enable HD4000 after that because it's already "true" in the config.plist.

I don't understand why do you ask about FakeID. What is the problem that you want change it? What is hte hardware?

Enter Clover GUI and press "Options".

Then navigate to Graphics and change here *-platform-id to the value 1660003.

Try to boot.

If not success then do it again with other value.

  • Like 1
Link to comment
Share on other sites
rock.n.rollyn
rock.n.rollyn
Posted
Posted

Unchecking "UEFI only" is absolutely safe operation. You will get more options and nothing dangerous among them.

UEFI boot will work the same way. 

 

I don't understand why do you ask about FakeID. What is the problem that you want change it? What is hte hardware?

Enter Clover GUI and press "Options".

Then navigate to Graphics and change here *-platform-id to the value 1660003.

Try to boot.

If not success then do it again with other value.

Thank you for the reply. Ah, I'll try again after this and check the "UEFI".

 

The reason I ask because:

-Changed the FakeID, I able to boot into OS with low resolution.

-Changing 3 different -ig-platform-id doesn't work, unless I change the FakeID in Clover option. 0x01620005, 0x0166000a, 0x0166000b are the option for HD4000 in configurator. 

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Thank you for the reply. Ah, I'll try again after this and check the "UEFI".

 

The reason I ask because:

-Changed the FakeID, I able to boot into OS with low resolution.

-Changing 3 different -ig-platform-id doesn't work, unless I change the FakeID in Clover option. 0x01620005, 0x0166000a, 0x0166000b are the option for HD4000 in configurator.

1. Write your system information. Hardware spec.

2. Upload your config.plist and clover preboot.log files.

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Thank you for the reply. Ah, I'll try again after this and check the "UEFI".

 

The reason I ask because:

-Changed the FakeID, I able to boot into OS with low resolution.

-Changing 3 different -ig-platform-id doesn't work, unless I change the FakeID in Clover option. 0x01620005, 0x0166000a, 0x0166000b are the option for HD4000 in configurator. 

If you set FakeID for abstract value then it will be VESA graphics and no other efforts change anything.

ig-platform-id should be tested without changing FakeID.

  • Like 1
Link to comment
Share on other sites
rock.n.rollyn
rock.n.rollyn
Posted
Posted

If you set FakeID for abstract value then it will be VESA graphics and no other efforts change anything.

ig-platform-id should be tested without changing FakeID.

Yep, tested all three however no luck. Lilu and IntelGraphicFixup updated, no luck too. Also "UEFI only" checked but no success. 

 

1. Write your system information. Hardware spec.

2. Upload your config.plist and clover preboot.log files.

 

나의 LG-F800S 의 Tapatalk에서 보냄

1. Spec as per in sig; Sierra |  Gigabyte GA-H77M-D3H |  i5 3570K |  HD 4000 |  8GB RAM.

2. Here you are; Clover debug and config.plist; Config_debug.zip 

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Yep, tested all three however no luck. Lilu and IntelGraphicFixup updated, no luck too. Also "UEFI only" checked but no success. 

 

1. Spec as per in sig; Sierra |  Gigabyte GA-H77M-D3H |  i5 3570K |  HD 4000 |  8GB RAM.

2. Here you are; Clover debug and config.plist; attachicon.gifConfig_debug.zip

 

exactly tell me your problem.

black screen? 

try cases

1.

Fake ID intel = 0x01668086

ig-platform-id = 0x0166000A

 

2.

Fake ID intel = 0x01668086

ig-platform-id = 0x01660001 or 0x01660002 or 0x01660003 or 0x01660004

 

3.

Fake ID intel = 0x01628086

ig-platform-id = 0x01620005 or 0x01620006 or 0x01620007

Link to comment
Share on other sites
rock.n.rollyn
rock.n.rollyn
Posted
Posted

exactly tell me your problem.

black screen? 

try cases

1.

Fake ID intel = 0x01668086

ig-platform-id = 0x0166000A

 

2.

Fake ID intel = 0x01668086

ig-platform-id = 0x01660001 or 0x01660002 or 0x01660003 or 0x01660004

 

3.

Fake ID intel = 0x01628086

ig-platform-id = 0x01620005 or 0x01620006 or 0x01620007

The problem is I'm unable to boot into my OS after I updated to the latest Clover. Booting froze at "IOConsoleUsers: time (0) 0->0, lin 0, llk. So I google for weeks but still no luck.

 

I read some IOConsoleUsers able to be solved with FakeID and ig-platform-i, thus I tried for my machine. Editing FakeID in the options of Clover help me to boot my OS however in low resolution.

 

May I know how do you suggest me to change FakeID? I changed my FakeID in Clover options before booting into OS. However the changes disappear after each boot, isn't permanent in my case. Or I missed some tool or option etc in the Clover Configurator?

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

The problem is I'm unable to boot into my OS after I updated to the latest Clover. Booting froze at "IOConsoleUsers: time (0) 0->0, lin 0, llk. So I google for weeks but still no luck.

 

I read some IOConsoleUsers able to be solved with FakeID and ig-platform-i, thus I tried for my machine. Editing FakeID in the options of Clover help me to boot my OS however in low resolution.

 

May I know how do you suggest me to change FakeID? I changed my FakeID in Clover options before booting into OS. However the changes disappear after each boot, isn't permanent in my case. Or I missed some tool or option etc in the Clover Configurator?

Okay.

In GUI, temp value for testing.

In config, permanent value if you setted any value.

 

It is your choice for testing..

 

Test and please report.

 

Also if you can boot with hd 4000 and old clover version, upload ioreg.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites
RehabMan
RehabMan
Posted
Posted

Rev 4250

XCPM patch will no more be unconditional.

		<key>KernelXCPM</key>
		<true/>
Default value is <false/>. 

It can arise some problems because old revision has default to true.

But many users can't boot at all because of this. Let it be conditional setting from config or from Clover GUI.

 

Why add "BOOLEAN KernelXCPMAllowed;" to Platform.h when it is not accessed anywhere?

And KernelXCPM is just a synonym for KernelIvyXCPM?

  • Like 1
Link to comment
Share on other sites
syscl
syscl
Posted
Posted

Hi, is there something changed in r4250? I have tried to build r4250 and give me "Thinning failed". I have to force archCpuType=CPU_TYPE_X86_64 to make it boot, otherwise the archCpuType is corrupted?

 

Here's the log from r4251(same with r4250 when I reverted).

 

 

 

preboot.log.zip

Link to comment
Share on other sites
Guest ricoc90
Guest ricoc90
Posted
Posted

Hi, is there something changed in r4250? I have tried to build r4250 and give me "Thinning failed". I have to force archCpuType=CPU_TYPE_X86_64 to make it boot, otherwise the archCpuType is corrupted?

 

Here's the log from r4251(same with r4250 when I reverted).

 

 

 

attachicon.gifpreboot.log.zip

 

 

Had the same issue some revisions ago and it turned out it was due to a messed up working copy

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Why add "BOOLEAN KernelXCPMAllowed;" to Platform.h when it is not accessed anywhere?

And KernelXCPM is just a synonym for KernelIvyXCPM?

Yes, KernelXCPMAllowed is not needed, I made this but use KernelIvyXCPM because it can be easy extended on other CPU. Should be renamed to common KernelXCPM

but we have to support backward compatibility.

Hi, is there something changed in r4250? I have tried to build r4250 and give me "Thinning failed". I have to force archCpuType=CPU_TYPE_X86_64 to make it boot, otherwise the archCpuType is corrupted?

 

Here's the log from r4251(same with r4250 when I reverted).

 

 

 

attachicon.gifpreboot.log.zip

check "svn diff"

The message

10:397  0:004  Preparing kexts injection for arch= from EFI\CLOVER\kexts\Other

can't be in official Clover

 

 

 
This section should also be selected depending on the options of KernelXCPM.
 
 

 

Already depending

&& Entry->KernelAndKextPatches->KPIvyXCPM
  • Like 1
Link to comment
Share on other sites
syscl
syscl
Posted
Posted

Slice, I svn diff, and terminal give me nothing. I build r4251 with ./ebuild.sh, still give me log like this on Dell Precision M3800.

 

preboot.log.zip

 

You said Official Clover cannot have "Preparing for kext injection...", what that mean sorry? Am I doing something wrong? Or miss something?

 

syscl

Link to comment
Share on other sites
PMheart
PMheart
Posted
Posted

Slice, I svn diff, and terminal give me nothing. I build r4251 with ./ebuild.sh, still give me log like this on Dell Precision M3800.

 

attachicon.gifpreboot.log.zip

 

You said Official Clover cannot have "Preparing for kext injection...", what that mean sorry? Am I doing something wrong? Or miss something?

 

syscl

Looks like something is broken here: https://sourceforge.net/p/cloverefiboot/code/4251/tree/rEFIt_UEFI/Platform/kext_inject.c#l332

So, on your build, "archCpuType" is neither "x86_64", nor "i386"...

What's up? I guess you've messed up something in kext_inject.c, have you tried `svn cleanup` ?

  • Like 1
Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

Sad but true Slice, even more strange. Here the log from our friends Matgen84:
arch was correctly detect while loading 'Other' folder, but gone afterwhile.

46:146  0:000  OSVesion: 10.13.1, ShortOSVersion=10.13, uni-vers=10.13,
46:146  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
...
46:146  0:000  Preparing kexts injection for arch= from EFI\CLOVER\kexts\10.13
  • Like 1
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted

 

Sad but true Slice, even more strange. Here the log from our friends Matgen84:

arch was correctly detect while loading 'Other' folder, but gone afterwhile.

.....

But, I think It works properly here with Legacy Clover r4251. Or if below is wrong, how it should to be..?

.....  .....
2:604  0:000  Now is 18.10.2017,  6:59:33 (GMT)
2:604  0:000  Starting Clover revision: 4251 on CLOVER EFI
2:604  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.11.6 | XCODE: 8.2]
.....  .....

27:788  0:000  === [ StartLoader ] =======================================
27:788  0:000  Finally: ExternalClock=24MHz BusSpeed=99773kHz CPUFreq=2195MHz PIS: hw.busfrequency=96000000Hz
27:788  0:000  Loading boot.efi  status=Success
28:194  0:406  GetOSVersion: 10.13.1 (17B35a)
..... .....

28:233  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
28:233  0:000  Extra kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext
28:270  0:036    |-- PlugIn kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext
28:284  0:014    |-- PlugIn kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext
28:288  0:004  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
.....  .....
28:306  0:017  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
28:567  0:006  Extra kext: EFI\CLOVER\kexts\10.13\AppleALC.kext
28:591  0:024    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
28:867  0:275  SetStartupDiskVolume:
28:867  0:000    * Volume: 'macOS High Sierra'
..... .....

preboot_a43sj_r4251_legacy.log.zip

EFI_r4251.zip

Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

Yosh Badruzeus I can see Clover work as it should be on your machine. I believe Matgen84 currently boot on UEFI. Maybe he will give more infos later.. here :)

Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.12.6 | XCODE: 8.3.3]
  • Like 1
Link to comment
Share on other sites
Badruzeus
Badruzeus
Posted
Posted

Just another report, so far.. I also got no issue with r4251, even with GCC53 built (Ubuntu 16.04). Thanks.  :)

 

 

 

.....  .....  ...
2:794  0:000  Now is 18.10.2017,  9:15:56 (GMT)
2:794  0:000  Starting Clover revision: 4251 on CLOVER EFI
2:794  0:000  Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t GCC53 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t GCC53 -n 5 | OS: Ubuntu 16.04]
.....  .....  ...

17:257  0:000  Loading boot.efi  status=Success
17:348  0:090  GetOSVersion: 10.13.1 (17B35a)
.....  .....  ...

17:391  0:000  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\Other
17:391  0:000  Extra kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext
17:422  0:031    |-- PlugIn kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Keyboard.kext
17:431  0:008    |-- PlugIn kext: EFI\CLOVER\kexts\Other\ApplePS2SmartTouchPad.kext\Contents\PlugIns\ApplePS2Controller.kext
17:434  0:003  Extra kext: EFI\CLOVER\kexts\Other\FakeSMC.kext
.....  .....  ...

17:452  0:018  Preparing kexts injection for arch=x86_64 from EFI\CLOVER\kexts\10.13
17:662  0:004  Extra kext: EFI\CLOVER\kexts\10.13\Lilu.kext
17:716  0:017  Extra kext: EFI\CLOVER\kexts\10.13\AppleALC.kext
17:734  0:017    |-- PlugIn kext: EFI\CLOVER\kexts\10.13\AppleALC.kext\Contents\PlugIns\PinConfigs.kext
17:936  0:201  SetStartupDiskVolume:
17:936  0:000    * Volume: 'macOS High Sierra'
.....  .....  ...
 

 

 

preboot_a43sj_r4251_gcc53.log.zip

EFI_r4251_GCC53.zip

Link to comment
Share on other sites
rock.n.rollyn
rock.n.rollyn
Posted
Posted

Okay.

In GUI, temp value for testing.

In config, permanent value if you setted any value.

 

It is your choice for testing..

 

Test and please report.

 

Also if you can boot with hd 4000 and old clover version, upload ioreg.

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

Old config.plist: config_old_clover.plist.zip

Current bootlog, booted with old clover. config_old_clover.plist.zip

 

Just in case these two are useful. 

 

I'll upload the IOReg later. Still googling how to make IOReg. 

Link to comment
Share on other sites
rock.n.rollyn
rock.n.rollyn
Posted
Posted

what is your working clover revision? upload ioreg that you got boot with graphic

 

and test blow with latest clover

http://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?p=2517556

Working is 3763. Latest is 4243.

 

I'll test later since I don't really get the instruction. Take time to explore the configurator. 

 

 

 

Okay.

In GUI, temp value for testing. 

In config, permanent value if you setted any value.

 

It is your choice for testing..

 

Test and please report.

 

Also if you can boot with hd 4000 and old clover version, upload ioreg.

Link to comment
Share on other sites
Sherlocks
Sherlocks
Posted
Posted

Working is 3763. Latest is 4243.

 

I'll test later since I don't really get the instruction. Take time to explore the configurator.

Take ioreg after boot with clover r3763. And please upload ioreg file.

 

나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...