Jump to content
3338 posts in this topic

Recommended Posts

11 minutes ago, surenmunoo said:

What did you use to map usb? I use Hackintool 

image.thumb.png.b8e7d41f66647054167982c051b30c1a.png

 

 

Hackintool does not work, or it has not worked for me, I have currently mapped them in windows...

My b660 motherboard is a bit weird and has several internal Asmedia 107x USB HUBs and I've had quite a bit of trouble on MacOS getting everything to work just fine.

  • Like 1
14 minutes ago, PoMpIs said:

 

Hackintool does not work, or it has not worked for me, I have currently mapped them in windows...

My b660 motherboard is a bit weird and has several internal Asmedia 107x USB HUBs and I've had quite a bit of trouble on MacOS getting everything to work just fine.

I tried in windows as well using usbmap but I failed to do it or just did not understand how to do it properly. 

Edited by surenmunoo

@meaganmargaret

 

As far as we have read, Vega 56 / 64 is the lower Metal 3 capable AMD dGPU. Intel Iris Plus Graphics series and Intel UHD Graphics 630 iGPU also. 
Do you have enable-metal for your AMD? This can get Metal 3 in the AMD system profiler although it’s not true. 

Edited by miliuco
  • Like 3
2 hours ago, PoMpIs said:

 

In this beta 3, I can't use the variable frequency in mine... it makes playing videos have image corruption, and on certain occasions everything freezes for a few seconds... and it only happens to me in this beta 3, in the previouss and monterey if I could use variable frequency without problem

 

1049511522_Capturadepantalla2022-07-08alas20_54_33.png.22493fab1f5d578e9c5790eb24a29d17.png

 

But if I can have the 165Hz 

I don't even have that option, in my config.plist for device properties is this

 

PciRoot(0x0)/Pci(0x2,0x0)

AAPL,ig-platform-id = 00001259

  • Like 1
Guest ricoc90
1 hour ago, meaganmargaret said:

So, that sounds like you mean to say a Vega GPU (56 .r 64)would not be Metal 3 compatible, right?


No, I meant to say that Metal 3 drops support for older cards except for Vega. It does support Vega, but Polaris has been competely dropped.

The reason why System Information reports the RX 590 as being Metal 3 is because your iGPU is supported by Metal 3. I am not sure how this affects actual computing though. It Might be that macOS switches to the iGPU for Metal computing/rendering if it finds that the dGPU lacks certain capabilities, but I could be completely wrong

34 minutes ago, Donw35 said:

I don't even have that option, in my config.plist for device properties is this

 

PciRoot(0x0)/Pci(0x2,0x0)

AAPL,ig-platform-id = 00001259

 

Already...

That's what happens to me on the i5.

 

I have a Lenovo with an HD620 iGPU and officially according to the user manual in the HDMI output it only supports 1920x1080p@60Hz, forcing it with SwitchResX I have reached 3440x1440p, but only at 55Hz... and the same thing happens in windows... but I think that the HD630 can go up to 1080p 144Hz or 4K 60Hz

22 minutes ago, PoMpIs said:

 

Already...

That's what happens to me on the i5.

 

I have a Lenovo with an HD620 iGPU and officially according to the user manual in the HDMI output it only supports 1920x1080p@60Hz, forcing it with SwitchResX I have reached 3440x1440p, but only at 55Hz... and the same thing happens in windows... but I think that the HD630 can go up to 1080p 144Hz or 4K 60Hz

Yeah, in works @ 2560X1440 @ 144hz in Monterey 

  • Like 1
6 minutes ago, Donw35 said:

Yeah, in works @ 2560X1440 @ 144hz in Monterey 

 

Well, it should work the same in Ventura...

 

But, you know, it's a beta... -_-

 

I in this beta 3 in the Alder Laker, I have quite a few graphical errors when I use SVP+iiNA if I have the monitor in variable frequency, it even gave me a kernel panic (AMDRadeonX6000....) a while ago and this in beta 1 and 2 never did.

 

apple fix one thing and another breaks. :lol:

Can anyone see why i get a black screen when i try installing Ventura B1?

I have the updated OC and Lilu for B3.

This is for the AMD system in my signature.

Current EFI attached that works with Monterey as well. 

EFI.zip

Edited by SavageAUS

@bisdak4920 Thank you very mutch for your kindness and shearing your wonderful EFI FOLDER. I have my z97 hack running  Venture beta 3.

Thank again

I do have a resolution problem but I think that's down to my OLD Gpu (7970) 

UPDATE

it was the old gpu . just fitted a and radeon 580. its all good 

Screenshot 2022-07-09 at 08.50.55.png

Edited by BALDY_MAN
  • Like 4

@aben @jsl2000 Could you please try this: https://github.com/acidanthera/WhateverGreen/actions/runs/2640401875? I did some code simplification again; hopefully I managed to have the kp addressed.

 

If it still kp, please attach a screenshot with -v debug=0x100 keepsyms=1.

Thanks!

  • Like 3
1 hour ago, PMheart said:

@aben @jsl2000 Could you please try this: https://github.com/acidanthera/WhateverGreen/actions/runs/2640401875? I did some code simplification again; hopefully I managed to have the kp addressed.

 

If it still kp, please attach a screenshot with -v debug=0x100 keepsyms=1.

Thanks!

Thanks and this version worked at Big Sur 11.6.6, Monterey 12.5 & Ventura 13.0 beta3 without KP.

as.vit9696.WhateverGreen (1.6.1) F469F034-B4B3-3E1E-8092-90C2153AF21B <55 17 9 7 6 3 2 1>

Screenshot 2022-07-09 at 6.37.00 PM.png

Screenshot 2022-07-09 at 6.36.15 PM.png

Edited by jsl2000
  • Like 3
1 hour ago, 5T33Z0 said:

 

Well then you better start using it. It fixes black screen issues in multi monitor configurations.

I think he use MacPro7,1 smbios with AMD rig...so, WEG is not needed at all. Maybe sometimes system is more powerful w/o this kext...... Black screen issues in multi screen is only on iMac and iMacPro with some old dgpu... with WEG you NEED to use agdpmod pikera and you multimonitor work... without weg and MP7,1 (Ryzen etc, need to use this smbios to work correctly...) ALL port are recognized and work like expected with Navi dgpu (drm and fairplay 3.x too)...

 

weg is good but definitely not  "must needed"... 

1 hour ago, jsl2000 said:

Thanks and this version worked at Big Sur 11.6.6, Monterey 12.5 & Ventura 13.0 beta3 without KP.

as.vit9696.WhateverGreen (1.6.1) F469F034-B4B3-3E1E-8092-90C2153AF21B <55 17 9 7 6 3 2 1>

Screenshot 2022-07-09 at 6.37.00 PM.png

Screenshot 2022-07-09 at 6.36.15 PM.png

Could you please try playing HEVC encoded videos? You can try https://filesamples.com/formats/hevc.

 

Also, if possible, please compare my version against the official release 1.6.0. The anticipated result is that you will have green screen with 1.6.0, while it’s fixed with mine.

  • Like 3
Guest 5T33Z0

It seems that the Device Property for selecting specific AMD Frambuffers (@0,name) no longer works in macOS Ventura.

 

Here are the Dev Propertries for my RX 580:

 

569589625_Bildschirmfoto2022-07-09um13_54_42.thumb.png.c3d713fa5d4a66a0f8213dd6d276ec8d.png

 

If I check for Orinoco in IO Reg when running Big Sur/Monterey I get result:

 

325292611_Bildschirmfoto2022-07-09um13_48_56.thumb.png.9834c5a177c9b31cef7266026cf3ee5a.png

 

In Ventura, nothing:

 

1051188443_Bildschirmfoto2022-07-09um13_59_16.thumb.png.1cdb4967e1837cdc4b7b56d20b8a9940.png

 

But the Framebuffer still exist in AMD9500Controller.kext:

 

274374157_Bildschirmfoto2022-07-09um14_01_39.png.57dcd41f3636f28af6cfd428cf8215db.png

 

Looks exactly the same as previous versions.

 

Any idea why this is?

 

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