Jump to content
30960 posts in this topic

Recommended Posts

11 minutes ago, mifjpn said:

Thank you everyone.

I'm sick and the doctor banned my computer and internet.

We sincerely apologize for any inconvenience.

The rest was left to Alpha999, who lives with me.

Thank you very much.

 

take care of you and your health to come back and continue this adventure with us

Strength and courage

  • Like 1
  • Thanks 1
15 minutes ago, mifjpn said:

Thank you everyone.

I'm sick and the doctor banned my computer and internet.

We sincerely apologize for any inconvenience.

The rest was left to Alpha999, who lives with me.

Thank you very much.

Take care of yourself and get back in shape :angel:

  • Like 2
  • Thanks 2

Hi @Slice
 

I'm back at home. When I try to build latest commit 830cc59, I can't:
 

Thanks for your effort.

[GENFW] BdsDxe
/Users/mathieu/src/Cloverbootloader/rEFIt_UEFI/entry_scan/loader.cpp:1620:210: error: expected ')'
        if (!AddLoaderEntry(SWPrintf("\\%s\\boot.efi", Volume->ApfsTargetUUIDArray[i].c_str()), NullXString8Array, FullTitleRecovery, L""_XSW, Volume, Volume->ApfsTargetUUIDArray[i], NULL, OSTYPE_RECOVERY, 0) {
                                                                                                                                                                                                                 ^
/Users/mathieu/src/Cloverbootloader/rEFIt_UEFI/entry_scan/loader.cpp:1620:12: note: to match this '('
        if (!AddLoaderEntry(SWPrintf("\\%s\\boot.efi", Volume->ApfsTargetUUIDArray[i].c_str()), NullXString8Array, FullTitleRecovery, L""_XSW, Volume, Volume->ApfsTargetUUIDArray[i], NULL, OSTYPE_RECOVERY, 0) {
           ^
1 error generated.
make: *** [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit/OUTPUT/entry_scan/loader.obj] Error 1


build.py...
 : error 7000: Failed to execute command
	make tbuild [/Users/mathieu/src/Cloverbootloader/Build/Clover/RELEASE_XCODE8/X64/rEFIt_UEFI/refit]


build.py...
 : error F002: Failed to build module
	/Users/mathieu/src/Cloverbootloader/rEFIt_UEFI/refit.inf [X64, XCODE8, RELEASE]

- Failed -

 

  • Thanks 1
  • Confused 3
10 minutes ago, Matgen84 said:

Hi @Slice
 

I'm back at home. When I try to build latest commit 830cc59, I can't:
 

Thanks for your effort.

idem

same

tried even with
 

git -f -f -d -x
./buildme XCODE8

 

  • Confused 1
  • Sad 2

Errors at compilation and may somes  explicit messages

 

/Desktop/CloverBootloader/rEFIt_UEFI/entry_scan/loader.cpp: In function 'void ScanLoader()':
/Desktop/CloverBootloader/rEFIt_UEFI/entry_scan/loader.cpp:1620:13: error: init-statement in selection statements only available with '-std=c++17' or '-std=gnu++17' [-Werror]
 1620 |         if (!AddLoaderEntry(SWPrintf("\\%s\\boot.efi", Volume->ApfsTargetUUIDArray.c_str()), NullXString8Array, FullTitleRecovery, L""_XSW, Volume, Volume->ApfsTargetUUIDArray, NULL, OSTYPE_RECOVERY, 0) {
      |             ^
/Desktop/CloverBootloader/rEFIt_UEFI/entry_scan/loader.cpp:1620:209: error: expected ';' before '{' token
 1620 |         if (!AddLoaderEntry(SWPrintf("\\%s\\boot.efi", Volume->ApfsTargetUUIDArray.c_str()), NullXString8Array, FullTitleRecovery, L""_XSW, Volume, Volume->ApfsTargetUUIDArray, NULL, OSTYPE_RECOVERY, 0) {
      |                                                                                                                                                                                                                 ^~
      |                                                                                                                                                                                                                 ;
/Desktop/CloverBootloader/rEFIt_UEFI/entry_scan/loader.cpp:1620:13: error: value computed is not used [-Werror=unused-value]
 1620 |         if (!AddLoaderEntry(SWPrintf("\\%s\\boot.efi", Volume->ApfsTargetUUIDArray.c_str()), NullXString8Array, FullTitleRecovery, L""_XSW, Volume, Volume->ApfsTargetUUIDArray, NULL, OSTYPE_RECOVERY, 0) {
      |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/Desktop/CloverBootloader/rEFIt_UEFI/entry_scan/loader.cpp:1625:244: error: expected ')' before ';' token
 1625 |         AddLoaderEntry(SWPrintf("\\%s\\com.apple.installer\\boot.efi", Volume->ApfsTargetUUIDArray.c_str()), NullXString8Array, FullTitleInstaller, LoaderTitleInstaller, Volume, Volume->ApfsTargetUUIDArray, NULL, OSTYPE_OSX_INSTALLER, 0);
      |                                                                                                                                                                                                                                                    ^
      |                                                                                                                                                                                                                                                    )
/Desktop/CloverBootloader/rEFIt_UEFI/entry_scan/loader.cpp:1620:12: note: to match this '('
 1620 |         if (!AddLoaderEntry(SWPrintf("\\%s\\boot.efi", Volume->ApfsTargetUUIDArray.c_str()), NullXString8Array, FullTitleRecovery, L""_XSW, Volume, Volume->ApfsTargetUUIDArray, NULL, OSTYPE_RECOVERY, 0) {
      |            ^
cc1plus: all warnings being treated as errors
make: *** [/Desktop/CloverBootloader/Build/Clover/RELEASE_GCC53/X64/rEFIt_UEFI/refit/OUTPUT/entry_scan/loader.obj] Error 1

 

  • Like 1
  • Thanks 1
45 minutes ago, Slice said:

Fixed

 

@Slice

Thanks for the fix :) I can't boot at all with the latest commit dc4a2617: Clover stuck at GUI when I select BS 11.1 HDD or BS 11.0.1 RC USB (no keyboard, no mouse) :cry: Maybe I mistaken somewhere !

Other test: can't boot  any macOS -->Black screen or BIOS boot select (because I use F12) 


 

2020-11-27_16-43-45_BOOTX64.EFI.log

2020-11-27_16-43-45_BOOTX64.EFI(1).log

Edited by Matgen84
  • Confused 1

When I boot with 5119 (pre-OC), I got the text mode back when I do shutdown or restart. If I boot with 5127, I don't have that.

The only difference is that 5119 use AptioMemoryFix and 5127 uses quirks.

Anyone has an idea on which quirks I forgot that has the effect of not having the text mode back ?

  • Like 1
  • Confused 1

@Jief_Machak When I boot to the recovery HD BS with latest commit 5127 I have Halting on critical error AptioMemorifix

no issue booting the Big Sur system

Spoiler

IMG_2365.thumb.JPG.08d95a7acf70984617f1415ecffb257d.JPG

 

Edited by chris1111
4 hours ago, Jief_Machak said:

When I boot with 5119 (pre-OC), I got the text mode back when I do shutdown or restart. If I boot with 5127, I don't have that.

The only difference is that 5119 use AptioMemoryFix and 5127 uses quirks.

Anyone has an idea on which quirks I forgot that has the effect of not having the text mode back ?

are you asking in Verbose mode?

@Jief_Machak

 

confirm that the order to load the Kext is good for Wifi Atheros! I tested it here and it works normal in all the tests you did

 

Spoiler

 

I did tests with this laptop on BigSur but it has HD3000 which is not possible to activate the graphics so this is the dock without transparency ...

 

"I just leave this clarification so that other members are not wasting time and signing this ...."

 

Spoiler

ar9285.png

 

 

Spoiler

ar9565.png

 

 

Spoiler

Intel Centrino Wireless-N 1000.png

 

 

Spoiler

ar9485 - 1.png

 

 

Spoiler

ar9485 - 2.png

 

 

Spoiler

Intel Centrino Advanced-N 6205 .png

 

 

Spoiler

Intel  Centrino Advanced-N 6200.png

 

  • Like 1
On 11/27/2020 at 2:47 PM, Jief_Machak said:

Also, check AirPortAtheros40.kext/Contents/Info.plist and you'll see :


	<key>OSBundleLibraries</key>
	<dict>
		<key>as.acidanthera.voodoo.driver.PS2Controller</key>
		<string>2.1.0</string>
		<key>com.apple.iokit.IOHIDFamily</key>
		<string>1.0.0b1</string>
		<key>com.apple.kpi.bsd</key>
		<string>8.0.0</string>
		<key>com.apple.kpi.iokit</key>
		<string>8.0.0</string>
		<key>com.apple.kpi.libkern</key>
		<string>8.0.0</string>
		<key>com.apple.kpi.mach</key>
		<string>8.0.0</string>
		<key>com.apple.kpi.unsupported</key>
		<string>8.0.0</string>
	</dict>

Pretty easy to spot dependencies, right ?

Ignore com.apple.*

 

@Jief_Machak @Slice

 

I have problems with this kext that I will leave on the post!

 

- ALPS touchpad I built the "VoodooPS2Trackpad.kext" Plugin from "VoodooPS2Controller-R6RC2" inside the Kext of Slice ALPS Here because the VoodooPS2Controller-R6RC2 I was using was giving Kernel panic on BigSur!

 

- I tested the kext on Mojave, Catalina and it loads and works without problems but ... it's not the case on BigSur because this Dell Latitude E6330 doesn't work "I have another Dell Vostro 2520 I'm using this same kext and it works on BigSur without problems "

 

- I saw that Jief talked about dependencies and that it would be easy to repair but ... not for me because I don't know how to solve it!

 

- I am using another kext that I found on the internet and it is working only that in the options of the trackpad it is only empty ....

 

- a little help or a resolution indication would be great. even Slice could maybe also insert support for this trackpad in your Kext ALPS (if you need information from him you can only do what you need here)

 

thank you all in advance

 

Spoiler

269641397_Capturedecran2020-11-29a01_55_22.thumb.png.11600176bb6c8a9da98619325eb12957.png

 

Log boot Mojave Fonctionne touchpad.zip

Log boot BigSur ne fonctionne pas le touchpad.zip

VoodooPS2Controller.kext.zip

 

Capture d’écran 2020-11-29 à 01.55.22.png

Edited by PG7
13 hours ago, Slice said:

You have to boot from Preboot.

@Slice :thumbsup_anim:Thank you! Enter the system successfully as you said. :thumbsup_anim:

 

But there is another question, I can choose normal system partition to enter with OC, can I

 

only choose preboot to enter with Clover?:(

2 hours ago, fryysyd said:

I can choose normal system partition to enter with OC

Nope, you can't. OC only boot through Preboot.

4 hours ago, PG7 said:

are you asking in Verbose mode?

Yes, I have verbose mode at boot, but not anymore at shutdown.

 

In the end, the question is what is the quirks configuration that mimics AptioMemoryFix ?

9 hours ago, Jief_Machak said:

When I boot with 5119 (pre-OC), I got the text mode back when I do shutdown or restart. If I boot with 5127, I don't have that.

The only difference is that 5119 use AptioMemoryFix and 5127 uses quirks.

Anyone has an idea on which quirks I forgot that has the effect of not having the text mode back ?

ProvideConsoleGop?

 

45 minutes ago, Jief_Machak said:

Nope, you can't. OC only boot through Preboot.

Yes, I have verbose mode at boot, but not anymore at shutdown.

 

In the end, the question is what is the quirks configuration that mimics AptioMemoryFix ?

It is config-sample.plist. But I didn't analyze quirk by quirk. I just found a configuration when it works as before.

As well I have to remind that apfs.efi driver from system has huge text output while ApfsDriverLoader no.

11 hours ago, Matgen84 said:

 

@Slice

Thanks for the fix :) I can't boot at all with the latest commit dc4a2617: Clover stuck at GUI when I select BS 11.1 HDD or BS 11.0.1 RC USB (no keyboard, no mouse) :cry: Maybe I mistaken somewhere !

Other test: can't boot  any macOS -->Black screen or BIOS boot select (because I use F12) 


 

2020-11-27_16-43-45_BOOTX64.EFI.log

2020-11-27_16-43-45_BOOTX64.EFI(1).log

The log tells me that you are trying to boot BigSur Recovery. Wait please, it is not supported yet.

Mojave Recovery boot fine.

  • Like 1
11 hours ago, Matgen84 said:

 

@Slice

Thanks for the fix :) I can't boot at all with the latest commit dc4a2617: Clover stuck at GUI when I select BS 11.1 HDD or BS 11.0.1 RC USB (no keyboard, no mouse) :cry: Maybe I mistaken somewhere !

Other test: can't boot  any macOS -->Black screen or BIOS boot select (because I use F12) 


 

2020-11-27_16-43-45_BOOTX64.EFI.log

2020-11-27_16-43-45_BOOTX64.EFI(1).log

What is the kext CtlnaAHCIPort.kext? What is the origin of the kext?

  • Like 1
51 minutes ago, Slice said:

What is the kext CtlnaAHCIPort.kext? What is the origin of the kext?

It is a kext driver About SATA HDD or SSD

Especially if you don't use this one No HDD or SSD will be seen in the GUIclover menu.

Edited by naiclub
1 hour ago, Slice said:

What is the kext CtlnaAHCIPort.kext? What is the origin of the kext?

 

@Slice This CtlnaACHIPort.kext is Big Sur version, to print 11th Intel Series instead of generic SATA. It works fine before, with previous Clover revision.
 

It come from here: CtlnaAHCI 

4 minutes ago, Matgen84 said:

 

@Slice This CtlnaACHIPort.kext is Big Sur version, to print 11th Intel Series instead of generic SATA. It works fine before, with previous Clover revision.
 

It come from here: CtlnaAHCI 

Does it comes from sources or it is just ordinary AHCIPort.kext with edited Info.plist?

 

12 minutes ago, Slice said:

Does it comes from sources or it is just ordinary AHCIPort.kext with edited Info.plist?

 

 

In fact, I don't really know, but I think so, is only ordinary kext with edited Info.plist. CFBundleVersion is 341.0.2. 

Edited by Matgen84
49 minutes ago, Slice said:

In this case codeless kext will be preferable.

 

How to do ? I am not expert enough. It would be this kext which prevents me from booting ...

@Slice Remember that with latest commit, I also can't boot BS Preboot.

Edited by Matgen84
2 hours ago, Slice said:

What is the kext CtlnaAHCIPort.kext? What is the origin of the kext?

In my case I need this kext for my notebook 1's Intel 100 series internal HDD, SSD. If I don't use this system doesn't recognise my drives and stall with AppleAHCIPort (or smth like that). Before Catalina it was SATA-100-series-unsupported.kext. it's simply injecting some pciids into AppleAHCI I think

  • Like 2
2 minutes ago, kushwavez said:

In my case I need this kext for my notebook 1's Intel 100 series internal HDD, SSD. If I don't use this system doesn't recognise my drives and stall with AppleAHCIPort (or smth like that). Before Catalina it was SATA-100-series-unsupported.kext. it's simply injecting some pciids into AppleAHCI I think

And it still works as well as the mountain lions.

×
×
  • Create New...