Jump to content
3338 posts in this topic

Recommended Posts

To AMD users: Is your CPU brand string patch broken by using the latest version of Lilu and RestrictEvents from the master branch? In other words, can you reproduce https://github.com/acidanthera/bugtracker/issues/2065?

 

Any feedback is greatly appreciated.

  • Like 2
Guest ricoc90
3 hours ago, Stefanalmare said:

Guys, the saga continues! I understand that I can not use standalone IGPU from CometLake and I put a RX570 inside the case. I tried to use CometLake UHD 630 as headless IGPU (all CML and CFL framebuffers) but I can't get H264 acceleration, only HEVC. Anybody with CometLake CPU and 500 series mobo here? I need some help!


You are correct. I Couldn't get the iGPU working either on my 500 series motherboard, so I'm running it headless as well.
I had to force metal on my iGPU. Not sure why. Either add enable-metal to your device properties or use bootflag igfxmetal=1.

platform-id: 0300913E
 

Spoiler

534245437_Schermafbeelding2022-07-03om20_47_45.thumb.png.ecdc7f35f241417551934520138bc6d0.png

Edited by ricoc90
additional info

Good night. I've noticed that, when ejecting the Ventura EFI partition (Desktop icon), immediately afterwards I see 3 successive warnings regarding that the Preboot, Update and VM disks can't be ejected.

By pressing Cancel, dialogs disappear. 
macOS 13 beta 2.
Is it happening to anyone else?

 

Spoiler

 

11 hours ago, antuneddu said:

Hi , How did you get here? Kernel > Quirks > PowerTimeoutKernelPanic

In my case if disabled ... it restarts when wake up from sleep

Ciao e Grazie @antuneddu

That's a very good observation. PowerTimeoutKernelPanic is always enabled but:

 

- Without the AppleXcpmCfgLock Monterey gives me a KP upon wake from sleep but does not restart.

- The KP on Ventura is always generating an automatic restart upon wake from sleep. 

 

I compared both Kernel panic logs and they're quite different. 

 

Still investigating other venues ( GPU-WTG / Nvme Controller ). I'll post my findings/results.

 

Monterey Kernel-2022-07-03-130643.panic

Ventura Kernel-2022-07-02-205548.panic

Guest ricoc90
7 minutes ago, Stefanalmare said:

How?

You can use the boot flag as well, it’s the same thing. 
 

using the device properties method add key enable-metal with data value of 01 I believe it was. I’ll have to check in a bit I am not home at the moment
 

16 minutes ago, miliuco said:

Good night. I've noticed that, when ejecting the Ventura EFI partition (Desktop icon), immediately afterwards I see 3 successive warnings regarding that the Preboot, Update and VM disks can't be ejected.

By pressing Cancel, dialogs disappear. 
macOS 13 beta 2.
Is it happening to anyone else?

 

  Reveal hidden contents

 

 Yep happens on my hack as well 

Edited by ricoc90
2 hours ago, ricoc90 said:


You are correct. I Couldn't get the iGPU working either on my 500 series motherboard, so I'm running it headless as well.
I had to force metal on my iGPU. Not sure why. Either add enable-metal to your device properties or use bootflag igfxmetal=1.

platform-id: 0300913E
 

  Reveal hidden contents

534245437_Schermafbeelding2022-07-03om20_47_45.thumb.png.ecdc7f35f241417551934520138bc6d0.png

Yep it works! Thank you! I don't need to fake platform-id. My IGPU is native supported.

Guest ricoc90
32 minutes ago, miliuco said:

@Stefanalmare

I think RX 580 doesn't support Metal 3. How did you get this? enable-metal=01 in deviceProperties of the dGPU?

No, iGPU. With enable-metal the headless iGPU will be used for computing, since the iGPU does support Metal 3 it will get reported as such :)

See WEG's readme:

 

Quote

igfxmetal=1 boot argument (and enable-metal property) to force enable Metal support on Intel for offline rendering.



 

Edited by ricoc90
26 minutes ago, ricoc90 said:

You can use the boot flag as well, it’s the same thing. 
 

using the device properties method add key enable-metal with data value of 01 I believe it was. I’ll have to check in a bit I am not home at the moment
 

 Yep happens on my hack as well 

It works with both methods:

1. boot-arg -> "igfxmetal=1"

2. device properties -> "enable-metal       01000000        DATA"

11 minutes ago, miliuco said:

@Stefanalmare

I think RX 580 doesn't support Metal 3. How did you get this? enable-metal=01 in deviceProperties of the dGPU?

We speak about enabling IGPU UHD 630 Comet Lake on series 500 mobos.

  • Like 2
Guest ricoc90
24 minutes ago, Stefanalmare said:

Yep it works! Thank you! I don't need to fake platform-id. My IGPU is native supported.


So is mine :) with ig-platform-id you can define which framebuffer your iGPU will use:
https://github.com/acidanthera/WhateverGreen/blob/master/Manual/FAQ.IntelHD.en.md#intel-uhd-graphics-610-655-coffee-lake-and-comet-lake-processors
 

 

10 minutes ago, eSaF said:

Bro - I just tried the boot-arg -> "igfxmetal=1" entry and it works (see the attached) don't know if it is just cosmetic but will know soon enough in one way or another.

  Hide contents

1677368322_Screenshot2022-07-03at22_36_40.png.af4141fa8aa0af36879bff86ad50b5e8.png33937374_Screenshot2022-07-03at22_42_52.png.1729a64d84bd51ea296fee467673932c.png

 

Hahhahahahhahha! Funny! And true:

 

Spoiler

1.png

 

Edited by Stefanalmare
  • Like 2
  • Haha 3
Guest ricoc90
42 minutes ago, Stefanalmare said:

I don't know if this is the right explanation for this, but UHD 630 is Metal 3 in Ventura. So, even if RX580(570) is Metal 2, the system know that one gpu is Metal 3. Now throw with rocks!😄

As it's the default behaviour on genuine imac20,1. You can verify this by firing up Activity monitor and go to GPUs:

140245089_Schermafbeelding2022-07-04om00_49_40.png.01a5df71f21fdf2bf4a078ddd960177e.png

Edited by ricoc90

@eSaF @Stefanalmare

 

Curious thing! It can be as Stefanalmare says, maybe enabling Metal 3 in the iGPU macOS thinks dGPU is also Metal 3. But I doubt that it's a real change because of Apple comments about Ventura and Metal 3.

Anyway, we have learned a new thing. 

  • Like 3
9 hours ago, carlo_67 said:

 

so does it work? because I just copied the procedure here

 

https://www.macos86.it/topic/5792-wifi-lentoooo/?tab=comments#comment-131599 

 

thank you Lorys89 https://github.com/acidanthera/AirportBrcmFixup

I will hopefully check after work today if this helps or not.

  • Like 1

A few days ago someone posted the link to a command utility to get information about Metal (sorry, I don't remember who it was). It's metalgpu.

Download the ZIP or clone the repository, cd to the folder and run
swift run metalgpu.
But from the information obtained I don't know if it is possible to know if it is Metal 2 or Metal 3.

Spoiler
Index: 0
  Name: AMD Radeon RX 6600
  Registry ID: 4294968563
  Location: Built-in
  Characteristics: (None)
  Features:
    32-Bit Float Filtering: Supported
    32-Bit MSAA: Supported
    BC Texture Compression: Supported
    Barycentric Coordinates: Supported
    Depth 24 Stencil 8 Pixel Format: Supported
    Dynamic Libraries: Supported
    Function Pointers: Supported
    Primitive Motion Blur: Supported
    Programmable Sample Position: Supported
    Pull Model Interpolation: Supported
    Query Texture LOD: Supported
    Raster Order Groups: Supported
    Shader Barycentric Coordinates: Supported
  Recommended Maximum Memory Size: 7,98 GB
  Max Buffer Length: 3,5 GB
  Max Threads per Thread Group: (Width: 1024, Height: 1024, Depth: 1024)
  Max Thread Group Memory Size: 64 KB
  Sparse Tile Size: 16 KB

 

 

  • Like 1
Guest ricoc90
50 minutes ago, miliuco said:

A few days ago someone posted the link to a command utility to get information about Metal (sorry, I don't remember who it was). It's metalgpu.

Download the ZIP or clone the repository, cd to the folder and run
swift run metalgpu.
But from the information obtained I don't know if it is possible to know if it is Metal 2 or Metal 3.

  Hide contents
Index: 0
  Name: AMD Radeon RX 6600
  Registry ID: 4294968563
  Location: Built-in
  Characteristics: (None)
  Features:
    32-Bit Float Filtering: Supported
    32-Bit MSAA: Supported
    BC Texture Compression: Supported
    Barycentric Coordinates: Supported
    Depth 24 Stencil 8 Pixel Format: Supported
    Dynamic Libraries: Supported
    Function Pointers: Supported
    Primitive Motion Blur: Supported
    Programmable Sample Position: Supported
    Pull Model Interpolation: Supported
    Query Texture LOD: Supported
    Raster Order Groups: Supported
    Shader Barycentric Coordinates: Supported
  Recommended Maximum Memory Size: 7,98 GB
  Max Buffer Length: 3,5 GB
  Max Threads per Thread Group: (Width: 1024, Height: 1024, Depth: 1024)
  Max Thread Group Memory Size: 64 KB
  Sparse Tile Size: 16 KB

 

 


That was me, but it's pretty easy to write your own using SwiftUI's MTLDevice api:

 

1642312118_Schermafbeelding2022-07-04om02_13_51.png.20edc7ea42a86e19d72903b96094feec.png

Which shows you that the RX 580 indeed gets being reported as only being Metal 2, whereas the iGPU gets being reported as being Metal 3

Edited by ricoc90
Seriously, English....
2 hours ago, Stefanalmare said:

I don't know the reason, but I tested enable-metal on 2 rigs: 300 and 500 series with RX570/580 in Geekbench 4 and 5. I have improvement with around 7% on OpenGL and Metal.

Geekbench on +/-10% is not reliable at all... xD

 

image.thumb.png.df112870430812bded20ef7b74178d77.png

  • Like 3
Guest 5T33Z0
13 hours ago, Stefanalmare said:

Guys, the saga continues! I understand that I can not use standalone IGPU from CometLake and I put a RX570 inside the case. I tried to use CometLake UHD 630 as headless IGPU (all CML and CFL framebuffers) but I can't get H264 acceleration, only HEVC. Anybody with CometLake CPU and 500 series mobo here? I need some help!

 

  Reveal hidden contents

1.png

 

 

Which SMBIOS are you using?

Guest
This topic is now closed to further replies.
×
×
  • Create New...