carlo_67

fsck_apfs -y /dev/diskXsX metti in numeri del disco e invia

terminale/diskutil list e mostra il disco da riparare

@audiomanhttps://macos86.it/topic/367-bios-settings-asus-asrock-gigabyte-msi/ setta bene il bios

pero strano dovrebbe andare senza niente a meno che ha l'integrata abilitata nel bios

non ho più idee, prova a staccare e riattaccare il cavo dopo lo schermo nero, provalo anche su un altro monitor

riprova ho cambiato i framebuffer non avevo visto la porta dvi, una cosa devi fare attacca solo il cavo hdmi config.plist.zip i kext Lilu e web sono aggiornati?

tieni una copia del tuo e prova questo config.plist.zip

mi ripassi il confi con le device proprieties

strano la 580 non ha bisogno di tante stranezze, comunque riabilita il web dal config. e lascia il boot arg agdpmod=pikera

WhateverGreen.kext disabilitali sul config e riprova ma fallo da una usb seno rischi di non avviare

prova a avviare senza weg pero fallo da una usb

apri il config con opencore configurator, aggiungi a bootarg agdpmod=Pikera poi recati su device proprieties e aggiungi il controller vga come da foto

quale hack, passa il config

in Download you will find many useful things, also take a look at useful links, you will find guides and much more, in short this forum is very well made and by people crazier than insanelymac 🤣

if you go up to download here you will also find very useful things, for example this https://macos86.it/files/file/91-powertool/ 😜

I use this OCAT, very accurate, you can mount EFI, and update Kext and Driver and you can update the OC bootloader to the latest version, follow the guide (in IT) easy to use. Or there is OpeCore Configurator not always stable but does its job https://mackie100projects.altervista.org/download-opencore-configurator/

I forced the loading of the 4000controller.kext only on monterey with a max and min kernel and put in devices proprerties the framebuffer suitable for OlandXT you could also try on other systems, it will not force the patch to load, or you can use Clover and Opencore so you can boot the systems you want separately

yes this is your modified config, I repeat your video card is based on another framebuffer and the r7.250 does not have the same as the r9 what you are now trying to make believe

Ahh there! Yes, it all makes sense then: seeing "Pitcairn" as the framebuffer is a sure sign that macOS is not using AMDRadeonX4000.kext, but something else — probably a broken fallback or a bad match from AMDRadeonX5000Controller. Monterey sees your device-id 0x682B, but it doesn't load the right kext (X4000) because of the policy. Instead it tries to handle it with a wrong framebuffer, like Pitcairn, which is not compatible. Result: no acceleration, black screens, or only VESA mode. config.plist2 we force the kext 7000 and 4000controller and patch them try config 2.plist.zip

@naquaada macOS Monterey disables GCN 1.0 support via policy, even if the ID is present. Some IDs (like 0x682B) remain in the plist for historical reasons or internal backwards compatibility, but: AMDRadeonX4000.kext drivers are not loaded. Even if the kext is present, matching fails at runtime. This also applies to 7000Controller.kext, which does not contain Oland-compatible framebuffers, so even if it "sees" the ID, it is of no use. Great point! Yes, it's true: the ID 0x682B (i.e. your RX 250) is present in both: AMDRadeonX4000.kext ➜ legacy GCN 1.0 drivers (Oland, Cape Verde) AMDRadeonX5000.kext / X7000Controller.kext - used for newer models, but sometimes with leftover support - But be careful: being listed in kexts does not mean they are actually loaded! Check with gpuid if your card has Uefi support or if it needs to be flashed, try my config.plist, I put a more compatible framebuffer in the devices proprierties "Futomaki", but you can also try Hamachi, remove the no_comact_check from the boot arg and still keep your config working configOlandXT.plist.zip

Open config.plist with OpenCore Configurator or ProperTree and set: Misc -> Security -> Vault = Optional

add inside the driver folder, it is already declared in the config.plist HfsPlus.efi.zip

this is a base to work on, IGPU is disabled and ATI too, then after you will work to make it work, create an installer with BIG or Monterey, mount the efi partition and insert the EFI. I advise you to disconnect the disks where you have the system working with Clover it could conflict, so either use OC or clover EFI 2.zip

I repeat, try to make a BigSur USB, and put OpenCore as boot loader, using only basic kext lilu, virtualSMC AppleALC and WhateverGreen, do not use DSDT, in the ACPI folder put only SSDT-Basic that you find in Download, you will see that with some care and patience we will install it, of course we use an independent HDisk without compromising your working one

I think that from opencore you can still disable the igpu and try to run the ati 6200 with OCLP