Jump to content
30960 posts in this topic

Recommended Posts

Just now, Matgen84 said:

Hi @chris1111

I noticed that submodule commits here (reported in your post) is not present, despite a fresh clone 🤔

Yea I dont know Why the build module not clone the latest  e288a05cb05511a5b86d1677b43b0f0304fe4326

 

:blink:

33 minutes ago, chris1111 said:

Yea I dont know Why the build module not clone the latest  e288a05cb05511a5b86d1677b43b0f0304fe4326

 

:blink:

 

Maybe there is something strange into OpencorePKG sub-module (see commit number on GitHub) in CloverHackyColor/CloverBootloader directory. The latest  e288a05cb05511a5b86d1677b43b0f0304fe4326 exists into CloverHackyColor/OpencorePKG. But I can't find more recent July 7th for example I don't quite understand 😔

I try : cd src/Cloverbootloader/opencorepkg and type git checkout origin/master to have e288a05 commit. 

On 7/8/2022 at 8:02 PM, mnfesq said:

First off, thanks Slice for you quick revision of Clover to make Ventura Beta 3 boot.

 

Now, a nagging problem that I cannot seem to resolve.  I cannot get HEVC hardware acceleration using Clover but I do get it using OC.

 

Compare these screenshots:

 

Booting with OC

475175131_WithOC.thumb.jpg.7a36489e3b2b4e432459d8dd5d79573e.jpg

Booting with Clover

913796557_WithClover.thumb.jpg.4538350843f01fcefca944475a94e66a.jpg

Here's my config.plist.  I would appreciate it if someone could take a look and see if there is anything you see that I could change to resolve this issue. Thanks.

 

mnfesq config.plist.zip 3.04 kB · 6 downloads



test 

config.plist

  • Thanks 1
4 hours ago, Matgen84 said:

 

Maybe there is something strange into OpencorePKG sub-module (see commit number on GitHub) in CloverHackyColor/CloverBootloader directory. The latest  e288a05cb05511a5b86d1677b43b0f0304fe4326 exists into CloverHackyColor/OpencorePKG. But I can't find more recent July 7th for example I don't quite understand 😔

I try : cd src/Cloverbootloader/opencorepkg and type git checkout origin/master to have e288a05 commit. 

I made new commit. Hope it will fix async issue.

sergey@iMac-Pro CloverBootloader % cd OpenCorePkg 
sergey@iMac-Pro OpenCorePkg % git branch
* master
sergey@iMac-Pro OpenCorePkg % git describe head --tags
0.8.3
sergey@iMac-Pro OpenCorePkg % 

 

  • Like 1
  • Thanks 1

@SliceI Made A Small ChangeTo buildme

Now Clones/Updates OpenCore

Now Compiles With No Error

Enjoy

buildme.zip

Edited by STLVNUB
  • Like 1
12 hours ago, PG7 said:

 

Thanks @PG7.  I now have HEVC capability with Clover using your config.plist.1962671103_BootwithClover-PG7Config.thumb.jpg.bfece87fdad473aeaf3a3e23958f5448.jpgHowever, although it may only be cosmetic, I wonder why, with OC, my IGPU is recognized by VideoProc but, with Clover, it is not recognized.  Any ideas?

Edited by mnfesq
2 hours ago, mnfesq said:

 

Thanks @PG7.  I now have HEVC capability with Clover using your config.plist.1962671103_BootwithClover-PG7Config.thumb.jpg.bfece87fdad473aeaf3a3e23958f5448.jpgHowever, although it may only be cosmetic, I wonder why, with OC, my IGPU is recognized by VideoProc but, with Clover, it is not recognized.  Any ideas?

I have an idea.

Graphics = N/A when model name is not beginning with "Intel" or "AMD".

Check your card name. Is it the name from config? Or from old version of WhateverGreen?

  • Like 1
  • Thanks 1
10 hours ago, Slice said:

I have an idea.

Graphics = N/A when model name is not beginning with "Intel" or "AMD".

Check your card name. Is it the name from config? Or from old version of WhateverGreen?

 

Yes, that was the issue.  In device properties for IGPU, @PG7 added model=UHD 620.  Adding "Intel" to the name made it appear in VideoProc.  I suspect that if I remove the model entry, WEG will select it correctly.

 

Edited by mnfesq
  • Like 2
19 hours ago, STLVNUB said:

@SliceI Made A Small ChangeTo buildme

Now Clones/Updates OpenCore

Now Compiles With No Error

Enjoy

buildme.zip 5.42 kB · 14 downloads

I committed your small change although I don't understand why our --recurse-submodules don't do the same thing.

  • Like 2
5 minutes ago, 5T33Z0 said:

Anyone else thinking that boot times got slower after the change to gcc12 was made? Clover r5137 booted incredibly fast. SInce then it got slower again.

It is rather because of OC integration.

Anyway boot process occurs once per day or once per week in my case. I can wait few seconds.

  • Like 2

Hello everyone, thanks for your tireless efforts to get Ventura working, as with Monterey last year, it's very appreciated.

 

For us that wish to remain a little conservative and won't update so fast, macOS or Clover, is the new release r5148 destined to replace a good working r5146 ? @Slice ? I use it for both Catalina and Monterey on 2 different hackintoshes. I know they say if it works, don't upgrade but... 😂 🤣

 

Thank you again everyone.

  1. @Slice
  2. Have Made Another Little Change To Building Clover 
  3. Now Own Folder Named Clover, Inside Is runme.command
  4. Execute This And It Will clone CloverBootloader If Not There
  5. And cd to CloverBootloader And git pulls If There
  6. Then it runs buildme 

          Reason For Doing This Is So There Is No Conflics  With Local Changes

          Resulting In Having To Do A git stash Depending On What Was Changed

       

         i.e Make Change to buildme, And when It git pull,  it Asks To Stash It

         Clover.zip

Edited by STLVNUB

Hi all

I noticed something strange under Ventura Beta 2 : despite sound and startup disk settings correctly, Clover GUI (r5147 c7789dc) don't select macOS automatically.

Few minutes ago, I update successfully Ventura Beta 3 (22A5295i) ( Clover r5148 a5e78463a). I select Startup disk on Ventura. After turning off, I turn on again my config, same problem : Clover don't select macOS disk automatically !

 

On the other hand, Ventura seems to keep the sound parameter for the moment.

What do you think about that (z390 config). 🤔

25 minutes ago, 5T33Z0 said:

@Matgen84 What happens if you select "LastBootedVolume"? Did you reset NVRAM already?

 

@5T33Z0 I don't try 'LastBootedVolume". Since Big Sur, I use Volume UUID. I don't reset NVRAM.

×
×
  • Create New...