Jump to content
30963 posts in this topic

Recommended Posts

On 10/5/2024 at 10:38 PM, chris1111 said:

Try boot args mem=2 arch=i386

 

@chris1111, I needed to change ISA Enable bit=disabled and PCI Latency Timer bigger then 32. Now I can boot legacy Clover with dual channel RAM. Thank you for your help!

  • Like 3
  • Thanks 1

Hi @Slice

I can't start clover after updating sequoia on my Z390 machine. It's not the first time: every time I update, I get a black screen and an underscore at the top left. So Clover doesn't start.


What can I do? Do you have a solution, please?

16 hours ago, Matgen84 said:

Hi @Slice

I can't start clover after updating sequoia on my Z390 machine. It's not the first time: every time I update, I get a black screen and an underscore at the top left. So Clover doesn't start.


What can I do? Do you have a solution, please?

 

Same Mobo as you, latest Clover.

 

Spoiler

1.png

 

config.plist

Edited by Stefanalmare
  • Like 1
  • Thanks 1
9 hours ago, Stefanalmare said:

 

Same Mobo as you, latest Clover.

 

  Reveal hidden contents

 

 

config.plist 11 kB · 5 downloads

 

Thanks a lot @Stefanalmare Do you have unlocked CFG setting in BIOS as I make on my Z390 Aorus Master ?

Edited by Matgen84
On 10/16/2024 at 10:59 AM, Matgen84 said:

Hi @Slice

I can't start clover after updating sequoia on my Z390 machine. It's not the first time: every time I update, I get a black screen and an underscore at the top left. So Clover doesn't start.


What can I do? Do you have a solution, please?

Underscore in the left corner means you booted by legacy. But why? Z390 can be booted by UEFI. 🤔

  • Like 2
18 hours ago, Slice said:

Underscore in the left corner means you booted by legacy. But why? Z390 can be booted by UEFI. 🤔

 

It's strange. CSM disable in BIOS since almost 6 years: how is it possible to boot by legacy ! I don't understand. Could you explain to me, please.

Since few years now,  I boot Clover  via BootloaderChoser 1.4.0. And I only copy/paste each CloverX64.efi update into EFI/CLOVER folder. Of cause I rename CLOVERX64 to CLOVERX64_5160_XXX (XXX = commit). Each time, I have this issue, I boot OC from a rescue USB, Reset NVRAM to solve the problem. CLOVER work fine after.

Edited by Matgen84
14 hours ago, Alpha22 said:

@Matgen84 

I also use this method, but I don't rename anything

@Alpha22 I rename CLOVERX64 to CLOVERX64_5160_XXX (XXX for comitt) because  I keep several Clover version into EFI/CLOVER folder, for testing. 

  • Like 1
  • 3 weeks later...

@Jief_Machak @Slice @chris1111

hello team
 

How to apply this code in Clover's config.plist to activate Intel Bluetooth

I tried successfully with Hackintool but I can't apply it permanently 

every proposal is welcome 
 

Thanks

"bluetoothExternalDongleFailed DATA 00"
"bluetoothInternalControllerInfo DATA 0000000000000000000000000000"

 



 

Spoiler

image.thumb.png.97f09d84b17654eb4dfc76b86083a5d0.png

 

  • Sad 1

Hi my friend. We can’t apply this on Clover. Need run Opencore once and them in Nvram Will be fix that until you reset (clean) again. 

Edited by Max.1974
  • Thanks 1
6 hours ago, PG7 said:

@Jief_Machak @Slice @chris1111

hello team
 

How to apply this code in Clover's config.plist to activate Intel Bluetooth
 

  Reveal hidden contents

image.thumb.png.97f09d84b17654eb4dfc76b86083a5d0.png

nvram bluetoothExternalDongleFailed="%00"
nvram bluetoothInternalControllerInfo="%00%00%00%00%00%00%00%00%00%00%00%00%00%00"

Edited by LockDown
  • Like 1
  • Thanks 1
4 hours ago, LockDown said:

nvram bluetoothExternalDongleFailed="%00"
nvram bluetoothInternalControllerInfo="%00%00%00%00%00%00%00%00%00%00%00%00%00%00"

@chris1111 

Chris1111, you who have a lot of experience in scripts, would it be possible to create a

thank you everyone

 

 

sudo nvram bluetoothExternalDongleFailed="%00"

sudo nvram bluetoothInternalControllerInfo="%00%00%00%00%00%00%00%00%00%00%00%00%00%00"

 

this command works 

Would it be possible to create a script to activate it at system launch?

*in boot-args I had already tested but it doesn't work
 

Edited by PG7
8 hours ago, PG7 said:

@chris1111 

Chris1111, you who have a lot of experience in scripts, would it be possible to create a

thank you everyone

 

 

sudo nvram bluetoothExternalDongleFailed="%00"

sudo nvram bluetoothInternalControllerInfo="%00%00%00%00%00%00%00%00%00%00%00%00%00%00"

 

this command works 

Would it be possible to create a script to activate it at system launch?

*in boot-args I had already tested but it doesn't work
 

Hi @PG7

 

Ask Slice, only he can do it.

 

Edited by chris1111
  • Like 1
  • Confused 1
8 minutes ago, PG7 said:

@MaLd0n
Daniel with this script I was unable to activate

THis script just run 

sudo nvram bluetoothExternalDongleFailed="%00"

sudo nvram bluetoothInternalControllerInfo="%00%00%00%00%00%00%00%00%00%00%00%00%00%00"

I tested and just work fine with clover

  • Like 1
  • Thanks 2
49 minutes ago, MaLd0n said:

THis script just run 

sudo nvram bluetoothExternalDongleFailed="%00"

sudo nvram bluetoothInternalControllerInfo="%00%00%00%00%00%00%00%00%00%00%00%00%00%00"

I tested and just work fine with clover

Works for UEFI system but not Legacy Duet

Edited by chris1111
  • Like 2
6 hours ago, PG7 said:


Hello, here on my HP DV6 2140ef 1gen i5-M430 Legacy Laptop, Nvram.tool applies normally, which means it works correctly

  Hide contents

image.thumb.png.89986446e97da10ec3f566cf3f8fe933.png

 

of course with the CLOVER64.efi from Slice

 

 Hey man You said here  command not work in live system, the script is the same command

 

 

Edited by chris1111
  • Like 2
26 minutes ago, chris1111 said:

of course with the CLOVER64.efi from Slice

Nop

NVRAM.tool

 

no, in this case I was just using the Clover 5160f and not the new Slice Clover

in the next post, yes, I only used Clover from Slice

Edited by PG7
  • Like 1
×
×
  • Create New...