Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

Slice
Slice
Posted
Posted
9 hours ago, brousseau6933 said:

Hello,

 

I'm able to boot Big Sur on a Dell XPS 8930, i7 8700, 32 Gb RAM, without problems with 5148.

 

5150: only black screen, not even verbose starts?

 

Thanks,

 

Patrice

Provide please preboot.log and config.plist.

  • Like 2
  • Thanks 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
7 hours ago, brousseau6933 said:

Thanks for your answer. You mean the actual files with 5148 or with 5150. It doesn’t even try to boot…

I mean with 5150. Something wrong at your side.

Link to comment
Share on other sites
brousseau6933
brousseau6933
Posted
Posted (edited)
19 hours ago, Slice said:

I mean with 5150. Something wrong at your side.

Ok here are two folders:

 

- 5148, boot fine Big Sur on Dell XPS 8930.

- 5150 shows OS menu then when selecting Big Sur, stays on a black screen, even when checking verbose...

 

OneDrive link: https://1drv.ms/u/s!AsCftN_jdRMFhc8Dcrj6BK02w8raaw?e=EJHJ4c

 

**Surely a mistake on my side, a file that doesn't belong there or one missing. Quirks not ok, I don't know!

 

**This time, I updated manually, replacing one file at a time and removing what was not present in the 5150 PKG.

 

Thanks and Happy New Year!

Edited by brousseau6933
Link to comment
Share on other sites
Allan
Allan
Posted
Posted
12 minutes ago, brousseau6933 said:

It had probably too much stuff and some mistakes in the config?

Not too much, I've just removed the unnecessary entries. 

 

As I always do to myself 😁

  • Like 2
Link to comment
Share on other sites
  • 2 weeks later...
brousseau6933
brousseau6933
Posted
Posted (edited)

It's me again, this time trying to update 5148 to 5151 and facing the same result I got with 5150, meaning no boot! Unsolved BTW as I had another fight with this Dell and OC and Clover vs AMD Polaris graphics. I can't provide bootlog as it simply doesn't go past a black screen after Clover boot menu!

 

 

 Here, very simple (but complicated ...):

 I have my Dell XPS 8930 who only wants to function properly with Clover, graphic lag question that OC does not manage, and I tried.

 

 Anyway, many attempts to go from Clover 5148 to 5150, with always the same result: Clover start menu - I choose "Preboot Big Sur" and ... Display lit but which remains black and it does not go further!

 

 This morning, same test, with 5151 and same result ???

 There is surely something that I forget (or that shouldn't be there in the files or config?). Anyone can take a look and try to understand what gets me stuck?

 

 Thank you,

 

 Patrice

 *** everything was done manually via Pacifist and I've deleted 5151 things that were not in the 5151 package (but present in my EFI 5148).

***Yes, I always clear NVRAM (F11) and reboot between each attempts!

***Just to be sure, I use the latest Clover Configurator to re-save the config.plist...

 

- Dell XPS 8930, i7 8700, 32 gb RAM, RX460 - Dual boot Win 11 and Big Sur. 5148 working really good, 5150 or 5151=no go!

 

 

 

 

Edited by brousseau6933
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted
16 hours ago, brousseau6933 said:

It's me again, this time trying to update 5148 to 5151 and facing the same result I got with 5150, meaning no boot! Unsolved BTW as I had another fight with this Dell and OC and Clover vs AMD Polaris graphics. I can't provide bootlog as it simply doesn't go past a black screen after Clover boot menu!

 

 

 Here, very simple (but complicated ...):

 I have my Dell XPS 8930 who only wants to function properly with Clover, graphic lag question that OC does not manage, and I tried.

 

 Anyway, many attempts to go from Clover 5148 to 5150, with always the same result: Clover start menu - I choose "Preboot Big Sur" and ... Display lit but which remains black and it does not go further!

 

 This morning, same test, with 5151 and same result ???

 There is surely something that I forget (or that shouldn't be there in the files or config?). Anyone can take a look and try to understand what gets me stuck?

 

 Thank you,

 

 Patrice

 *** everything was done manually via Pacifist and I've deleted 5151 things that were not in the 5151 package (but present in my EFI 5148).

***Yes, I always clear NVRAM (F11) and reboot between each attempts!

***Just to be sure, I use the latest Clover Configurator to re-save the config.plist...

 

- Dell XPS 8930, i7 8700, 32 gb RAM, RX460 - Dual boot Win 11 and Big Sur. 5148 working really good, 5150 or 5151=no go!

 

  Clover 5148 vs 5151

 

 

 

Your link redirect to the first page of thi thread ? 😉

1/ Don't use Clover configurator, it's not recommanded to edit/save config.plist

2/ To update Clover, do you try Clover PKG ? Don't use Pacifist to extract. On Githb, you have Clover V2

Link to comment
Share on other sites
brousseau6933
brousseau6933
Posted
Posted (edited)
On 1/15/2023 at 4:06 AM, Matgen84 said:

 

Your link redirect to the first page of thi thread ? 😉

1/ Don't use Clover configurator, it's not recommanded to edit/save config.plist

2/ To update Clover, do you try Clover PKG ? Don't use Pacifist to extract. On Githb, you have Clover V2

Fixed: Clover 5148 to 5151

*Deleted

 

I've tried manually and with the package, same result!

 

5149, 5150 and 5151 gave the same "no boot" situation.

 

Thanks for your reply!

Edited by brousseau6933
  • Like 1
Link to comment
Share on other sites
brousseau6933
brousseau6933
Posted
Posted (edited)

Solved with the help of a PM:

 

- too much stuff in UEFI drivers;

- moved kexts from "other" to "11".

 

**Looks like the move to « 11 » is a bad idea, like when you want to update the OS to another version!

 

***Moved back kexts to "Other". Still boot correctly except that all HWMonitorSMC2 settings were reset, probably due to the location change, weird!

Edited by brousseau6933
  • Like 2
Link to comment
Share on other sites
kushwavez
kushwavez
Posted
Posted (edited)

Hello all!
 

I doesn't seem to receive updates on Ventura, seems like the hwtarget isn't working. Is this known?

I have set it to J160AP, it worked on Monterey, but now is not. hwtarget is empty when I get it in Terminal 

11:06:46 > kushwavez@X1C6-Pro:~$ softwareupdate -l
Software Update Tool

Finding available software
No new software available.
11:06:55 > kushwavez@X1C6-Pro:~$ sysctl hw.target
hw.target:
11:06:58 > kushwavez@X1C6-Pro:~$ csrutil status
System Integrity Protection status: enabled.
<key>RtVariables</key>
	<dict>
		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x00</string>
		<key>HWTarget</key>
		<string>J160AP</string>
		<key>MLB</key>
		<string>C02032109R5DC771H</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>

SMBIOS I am using is: MacBookPro15,2 on Lenovo X1 Carbon 6th (i7-8650U)

Should I change anything?

Clover v5151

Edited by kushwavez
  • Confused 1
  • Sad 1
Link to comment
Share on other sites
Allan
Allan
Posted
Posted
On 1/15/2023 at 9:58 PM, brousseau6933 said:

Solved with the help of a PM:

 

- too much stuff in UEFI drivers;

- moved kexts from "other" to "11".

 

**Looks like the move to « 11 » is a bad idea, like when you want to update the OS to another version!

 

***Moved back kexts to "Other". Still boot correctly except that all HWMonitorSMC2 settings were reset, probably due to the location change, weird!

That's what I made for your EFI folder before 😄

  • Like 2
Link to comment
Share on other sites
Matgen84
Matgen84
Posted
Posted (edited)
6 hours ago, kushwavez said:

Hello all!
 

I doesn't seem to receive updates on Ventura, seems like the hwtarget isn't working. Is this known?

I have set it to J160AP, it worked on Monterey, but now is not. hwtarget is empty when I get it in Terminal 

11:06:46 > kushwavez@X1C6-Pro:~$ softwareupdate -l
Software Update Tool

Finding available software
No new software available.
11:06:55 > kushwavez@X1C6-Pro:~$ sysctl hw.target
hw.target:
11:06:58 > kushwavez@X1C6-Pro:~$ csrutil status
System Integrity Protection status: enabled.
<key>RtVariables</key>
	<dict>
		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x00</string>
		<key>HWTarget</key>
		<string>J160AP</string>
		<key>MLB</key>
		<string>C02032109R5DC771H</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>

SMBIOS I am using is: MacBookPro15,2 on Lenovo X1 Carbon 6th (i7-8650U)

Should I change anything?

Clover v5151

 

Hi @kushwavez Do you try J132AP for SMBIOS MacBookPro15,2 instead of J160AP. According to platform file in Clover Github repository, J160AP is for SMBIOS macPro7,1. If I am not mistaken.
 

Capture d’écran 2023-01-18 à 17.34.36.png

Edited by Matgen84
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
8 hours ago, kushwavez said:

Hello all!
 

I doesn't seem to receive updates on Ventura, seems like the hwtarget isn't working. Is this known?

I have set it to J160AP, it worked on Monterey, but now is not. hwtarget is empty when I get it in Terminal 

11:06:46 > kushwavez@X1C6-Pro:~$ softwareupdate -l
Software Update Tool

Finding available software
No new software available.
11:06:55 > kushwavez@X1C6-Pro:~$ sysctl hw.target
hw.target:
11:06:58 > kushwavez@X1C6-Pro:~$ csrutil status
System Integrity Protection status: enabled.
<key>RtVariables</key>
	<dict>
		<key>BooterConfig</key>
		<string>0x28</string>
		<key>CsrActiveConfig</key>
		<string>0x00</string>
		<key>HWTarget</key>
		<string>J160AP</string>
		<key>MLB</key>
		<string>C02032109R5DC771H</string>
		<key>ROM</key>
		<string>UseMacAddr0</string>
	</dict>

SMBIOS I am using is: MacBookPro15,2 on Lenovo X1 Carbon 6th (i7-8650U)

Should I change anything?

Clover v5151

I am sorry but HWTarget no more works in Ventura. So to get updates we have to set SMBIOS for models without T2.

  • Like 2
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
4 minutes ago, PG7 said:

@Slice  @Jief_Machak


LEGACY Boot

 

Too bad Clover couldn't do the complete installation or update of the latest system on a non-UEFI PC (Legacy)

would there be a solution?

 

 

thanks team

I don't know what is the issue but I know that since BigSur we need hardware NVRAM which is absent on legacy computers.

QEMU works with legacy Clover.

  • Like 1
Link to comment
Share on other sites
PG7
PG7
Posted
Posted
2 hours ago, Slice said:

know that since BigSur we need hardware NVRAM which is absent on legacy computers

and will it be possible to somehow emulate the NVRAM or are we without a solution?

  • Like 1
Link to comment
Share on other sites
Slice
Slice
Posted
Posted
21 hours ago, PG7 said:

and will it be possible to somehow emulate the NVRAM or are we without a solution?

Yes, legacy system is able to emulate NVRAM but when the system installed. The problem is during installation.

Link to comment
Share on other sites
PG7
PG7
Posted
Posted
16 hours ago, Slice said:

Yes, legacy system is able to emulate NVRAM but when the system installed. The problem is during installation.

yes I use Clover on Legacy machines with Ventura, Monterey and BigSur

I just can't even update or install these latest complete systems with Clover

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