naquaada Posted Wednesday at 09:00 AM Share Posted Wednesday at 09:00 AM ... but it's difficult. I'm still stuck with Mavericks. I can't complain about it, but there are some problems. I know these from my long past, here's my story. Everything is repeating... 1. Tiger My first system was an Athlon 64 3400+ Socket 754 without SSE3 and an AGP ATI Radeon X1600 Pro on an Asus K8N-E Deluxe with an nForce 3 chipset. In Tiger 10.4.4 there was not much support, but with 10.4.5 everything was working. I used the installation images from Myzar, they were working fine up to 10.4.7. But then the 10.4.8 image from JaS contained a critical flaw which made the Disk Utility unuseable. I explained this very often in InsanelyMac, but the error was kept up to the last 10.4.11 images. At this time every version required a new kernel, that's why Apple released so many updates updates which was overwriting the patched kernel. So I stayed with 10.4.7 to have a fully working OS. 2. Leopard My second system was an Athlon 64 3700+ Socket 939 with SSE3 and an PCI-E ATI Radeon X1600 Pro on an Asus A8N-SLI Premium with an nForce 4 chipset. I waited some time until Leopard worked stable. I used the Leo4All V3 image for Leopard 10.5.3. Now everything was working again. My main video player was Quicktime 7.4.5 with the Perian plugin. But after the update to Quicktime 7.5 a simple AVI used 90% CPU time. After some tests I found out that it was the graphics card. So I bought for four computers ATI Radeon HD2600XT and everything was fine again. Even better. With Natit.kext I could 'overlock' my TFT from 1600x1200 to up to 2048x1536. Leopard worked flawless up to 10.5.8 using the AnV kernel. 3. Snow Leopard It took a long time until the first AMD Snow Leopard images appeared. But I had the luck that the Radeon HD2600XT was not supported anymore. I didn't want to buy new graphics cards again, so I stayed with Leopard. In this time people always wanted to do 'Vanilla' installations, so Chameleon 2 appeared. I now also had a Thinkpad x61t, but I never got OSx86 to work on it. It wouldn't be great anyway because the Intel GMA X3100 graphics wasn't supported. So I installed Windows 7 on the ThinkPad, on my desktop I still stayed with Leopard. 4. Mavericks I completely skipped Lion and Mountain Lion, probably because my graphics card wasn't supported. In February 2012 I bought two new systems: a Gigabyte GA-Z77-DS3H with a Core i7 3770K and an ITX Gigabyte GA-Z77N-WiFi with an Core i7 3770S. And a Sapphire Radeon HD6870. I don't know why, but I still stayed with Leopard. The time of playing with hardware was gone. I had still the Asus A8N-SLI Premium with the HD2600XT. The processor had changed to an Dual-Core AMD Opteron 185, overclocked to 3 GHz. At the time Mavericks was relased I was interesting in doing some experimenting again. With Clover I got it working. The fun of computer hacks had come back. It was possible to modify socket 775 boards to use socket 771 Xeons. With the Xeon L5420 it was possible to upgrade to a 2,5 GHz Quad-Core for just 10 Euro. I used for them with the same Mavericks installation and just had to modify some kexts. 5. Yosemite As Yosemite was out I quickly got it working. But I noticed it was very slow, especcially in the UI. On the Core i7 with an Radeon HD6870 was slower than a Xeon with a Radeon HD4870. The problem was also in El Capitan. So I stayed with Mavericks - till today. 6. Mojave As I had some time again, I tried a Mojave installation. Because Metal required a new graphics card, I bought a Radeon HD7770 and a Radeon HD7870. For my Mini-ITX systems I got a Sapphire GPRO 4200. This is a low-profile, single-slot graphics card, but with 4 GB GDDR5 and four Mini-DisplayPort outputs. I also have the GPRO 6200, this is basically the same, but full height with six Mini-DisplayPort outputs. These are based on the Cape Verde chipsets, so also R7 250 / HD7000 series. I never needed heavy equipment, low power consumption is more important to me. Mavericks and Mojave are working fine with these cards. But Mojave had a big problem. It is a nice installation, but without no appearent reason randomly the iconservicesagent kicks in and uses more than 100 GB memory. I have 32 GB RAM, but this means it uses lots of swap. The system is quickly so unresponsive that I can only get out with a hardware reset. I tried mixing the iconserviceagent files from 10.13, 10.14 and 10.15, no success. There seems to be no solution. Somebody wrote that it could work to remove all custom icons, but on my system nearly all files have custom icons, so I don't want to do this. So I'm still working with Mavericks. 7. Sonoma I got for not much money a MacBook11,5 with a 2.5 GHz Core i7 4870HQ and a Radeon R9 M370X. I upgraded it to a 4 TB SSD. I installed Monterey and Sonoma using OpenCore Legacy Patcher. But it's no fun. It feels very slow. CPU and GPU are getting so hot, the CPU oft more than 100 °C. So quickly the fans spin up and get loud. My systems are all built to be very silent, so this is annyoing. I also noticed that I'm not a laptop guy, a desktop system with a large screen is always better for me. I also have not much better software on Sonoma, so I using the MacBook only for a few things and go back to my Mavericks system. It is still the same installation, it only works so good because it's good maintained. If I have nothing better to do, clean it up, defragment it (yes, this also is useful on an HFS+ SSD) and make a backup as .dmg. But because my Mavericks installation works so well, I never had to restore it. But I used this image to clone my system to other mainboards. 8. Actual state In 2024 the audio chip of my GA-Z77-DS3H suddenly died. I got a Gigabyte Q77M-DS2H because I want to reduce space. My actual case is a huge Coolermaster Cosmos. Because I have enough Core i7 3rd generation laying around, I found an interesting use for them: An AsRock Z67M-GE. It has an additional Eltron E168A USB 3.0 chip which is fully supported by OSx86. The interesting features are two IR ports, serial port, printer port and even a floppy port. As retro computer user this is useful. I squeezed everything in a small desktop case which is smaller than a VCR. I had to use Low Profile RAM and angled SATA cables. Now I have a completely silent system with 32 GB RAM, 5 TB harddrives, 1,5 TB SSD and a Slimline DVD. So I can use this board for OSx86 or writing custom floppy formats from Windows XP. I also got two never boards: An Asus Prime Z270-K with a Sapphire RX560 and an ITX Gigabyte GA-H270N-WiFi, both with a Core i7 7700. The ITX board should bet either the GPRO 4200 oder a GPRO 4300. There were also some problems, the battery of the ITX board has a battery on a cable, and it is empty. So I have to solder a battery adapter, and I don't have much time actually. So I'm still using my GA-Z77-DS3H with Mavericks. It is like the years ago with Leopard: The system is working well, but the problem is the software support. Firefox 78esr is the last version. Now I got an ALogic 32" touchscreen monitor. I know the UPDD touchscreen driver from my Iiyama touchscreen monitor. Version 6 is working with Mavericks, but the company only has version 7 to download, which requires Mojave. This isn't useable because of the iconservicesagent. Mavericks also doesn't recognize the 4K resolution of this monitor. The maximum is 2560x1440. I created a monitor override with custom resolutions, but these are not shown in the list, also not when using the option key on 'scaled'. With the tool Resolutionator I got it working. I'm actually using 3008x1692. But the native resolution is still 2560x1440, so it's this kind of 'overclocking' like on my HP L2035. Everything is returning... I made attempts to upgrade, but it is difficult. The most OSx86 tools are requiring a newer version as Mavericks. Mojave isn't reliable. I also don't know about the actual kexts. I see no difference if Lilu and Whatevergreen is installed because my systems are working so well. Firefox 78 was often crashing on embedded videos, but I got used to it. After I disabled the hardware acceleration in about:config this problem was solved. This was a few days ago in April. I don't know anything about the topic ACPI and dsdt.aml patching, because I never needed this on my computers. Even an ITX board with GeForce 9300 chipset is working fine. So, my plans are to set up my systems from scratch. I want to install one system perfect, then transfer the data a newer version. I want to keep these: 1. Mavericks - it is the last macOS I have nothing to complain about 2. Mojave - the last macOS with 32bit support 3. Monterey - the last macOS for Ivy Bridge 4. Sonoma/Sequoia on the i7 7700 as actual versions The new Mavericks installation is so far finished, I even had time to configure software like SIDplay, a player for Commodore 64 music. So, porting to Mojave is close. But I have these problems: The GA-Q77M-DS2H won't sleep. I played a long time with pmset, it has the same configuration as my GA-Z77-DS3H. Still no sleep. SleepEnabler.kext is loaded, I don't use NullPowerManagement.kext. Even the AsRock Z67M-GE can sleep. Maybe it's because I have a Core i5 3570 (Intel HD2500 graphics) on the GA-Q77M-DS2H. I already have a Core i7 3770S here, but my thermal paste was 8 years old, so I have to get new one. I also would like to delid the processors and change the thermal paste on the die. It is at least 13 years old. On a laptop the thermal paste on the CPU/GPU dies also would be replaced. Graphics: The card was detected as Radeon 8830M. I managed to display the correct graphics card with Clover Settings, but I have the feeling that the system boot is not so smooth anymore. The CPU is still shown wrong as 600 MHz Core i5. Getting the hardware acceleration and DRM two work will be problematic. I also have no idea which kexts are working. I see no difference between Lilu and plugins are installed or not. The kexts are loaded, but there's no difference. I'm using FakeSMC.kext and place them in /Library. I made one change: On my GA-Z77-DS3H I'm using Legacy BIOS and MBR. The most computers I owned had no UEFI, so porting a BIOS/MBR system was easier. On the GA-Q77M-DS2H I'm using GPT, but still with Legacy BIOS. UEFI mode wasn't working well. The Broadcom wireless Mini-PCI-E to PCI-E card is working, but Bluetooth is missing. But probably I have the cable not connected. So there are the major problems I want to fix before I migrate the system to Mojave. So if anybody could help me with this, it would be great. Greets, naquaada. Link to comment Share on other sites More sharing options...
Supervisor fabiosun Posted Wednesday at 09:37 AM Supervisor Share Posted Wednesday at 09:37 AM (edited) hi @naquaadawelcome here if you like you can create a thread in English international area of this forum, and i think you could receive help for your problem (in this area is fine, only the title could be more specific, and if you like you could add in your signature hardware you have ) Broadcom wireless is supported from sonoma and greater OS only using OCLP app to patch OSX to use old system kext (blocking new one) your problem in supported osx (if you have connected usb part of you PCIE card) could be related to a wrong or a not exixtant USB port mapping. It is (for me) a too much old system and i have zero experience on that platform, but some users could help 🙂 Edited Wednesday at 09:39 AM by fabiosun Link to comment Share on other sites More sharing options...
naquaada Posted Wednesday at 11:47 AM Author Share Posted Wednesday at 11:47 AM (edited) I have lots of similar systems, so I'm listing them first and give them a number. All systems are using Clover without DSDT or other ACPI patches. S1: Gigabyte GA-Z77-DS3H, Core i7 3770K, HD 7870, 32 GB DDR3, BIOS, MBR, 1 TB SSD, 9 TB HD Video Connection: DisplayPort 4K, Audio: TI Burr Brown USB, M-Audio USB Transit, LAN: Atheros Mavericks: Graphics hardware acceleration and DRM not working Mojave using HFS+: Graphics hardware acceleration and DRM not working, iconservicesagent problem S2: Gigabyte GA-Z77N-WiFi, Core i7 3770S, GPRO 4200, 16 GB DDR3, BIOS, GPT, 2 TB SSD, 5 TB HD Video Connection: HDMI 4K, Audio: VoodooHDA ALC 892, LAN: RTL 8111E, WLAN: Broadcom 43224 Mavericks: Graphics hardware acceleration and DRM are not working S3: Gigabyte GA-Q77M-DS2H, Core i7 3770S, GPRO 6200, 32 GB DDR3-LP, BIOS, GPT, 1 TB SSD, 5 TB HD Video Connection: DisplayPort FHD, Audio: VoodooHDA ALC 887, LAN: Intel, WLAN: Broadcom 43xx Mavericks: Sleep and graphics hardware acceleration and DRM are not working S4: AsRock H67M-GE, Core i7 3770S, GPRO 4200, 32 GB DDR3-LP, BIOS, GPT, 1.5 TB SSD, 1 TB HD Video Connection: HDMI FHD, Audio: VoodooHDA ALC 892, LAN: RTL 8111E, WLAN: Broadcom 4352, USB3: Etron EJ168 Mavericks: Graphics hardware acceleration and DRM are not working S5: Asus Prime Z270-K, Core i7 7700, RX 560, 64 GB DDR4, UEFI, GPT, 2 TB NVME SSD Audio: Realtek ALC 887, LAN: Intel I219-V Not installed yet S6: Asus Prime Z270-K, Core i5 7500, Radeon HD 7770, 16 GB DDR4 SODIMM, UEFI, GPT, 500 GB Apple NVME SSD Audio: Realtek ALC 887, LAN: Intel I219-V Not installed yet S7: Gigabyte H270N-WiFi, Core i7 7700, GPRO 4200, 64 GB DDR4, UEFI, GPT, 2 TB NVME SSD, 5 TB HD Audio: Realtek ALC 1220, LAN: Intel I219-V, Wireless: Intel Not installed yet L1: MacBook11.5, Core i7 4790HQ, Radeon R9 M370X, 16 GB DDR3, OCLP, 4 TB NVME SSD Monterey and Sonoma are fully working, but slow and hot CPU/GPU L2: Dell XPS 15 9570, Core i9 8950HK, 4K UHD Touchscreen, GTX 1050 Ti Max-Q, 64 GB DDR4, UEFI, GPT, 500 GB NVME SSD Audio: Realtek ALC3266-CG with Waves MaxxAudio Pro Not installed yet L3: Dell XPS 15 9560, Core i7 7700HQ, 4K UHD Touchscreen, GTX 1050, 16 GB DDR4, UEFI, GPT, 500 GB NVME SSD Audio: Realtek ALC3266-CG with Waves MaxxAudio Pro Not installed yet Some special systems. The Zotac boards were socket 775, but are modified for socket 771 Xeons. X1: Zotac GeForce 9300 ITX, Xeon L5408, GeForce graphics, 8 GB DDR2, BIOS, MBR, 1 TB SSD, 2 TB HD Video Connection: DVI or HDMI, Audio: VoodooHDA ALC 662, LAN: GeForce, WLAN: Old Bradcom Mavericks, Snow Leopard Server and Leopard are working fine. Mavericks has no WLAN. X2: Zotac G41ITX-A-E, Xeon L5420, Intel GMA X4500, 8 GB DDR2, ALC 662, BIOS Not built yet X3: Supermicro X7-DVL-i, 2x Xeon L5408, Radeon HD 5xxx, 48 GB DDR2-Reg, BIOS Not built yet Edited 17 hours ago by naquaada Link to comment Share on other sites More sharing options...
naquaada Posted Wednesday at 06:13 PM Author Share Posted Wednesday at 06:13 PM (edited) Systems 1 to 4 are all based on the Mavericks vom System 1, with some kext changes. My new installations are created on System 3. I want to install Mavericks first, then migrate to Mojave on a HFS+ drive. The third system should be Monterey, the last version which should work on Ivy Bridge without too many patches. It doesn't require the AVX2 command set. System 2 is in a tight Mini-ITX-case, with Mini-PCI-Express WLAN/Bluetooth working. In System 3 and 4 have a Broadcom WLAN connected Mini PCI-E adapter. Wireless is working in Mavericks, Bluetooth not, but is probably not connected. The USB plug uses two ports, this could be the reason. System 4 is stuffed in a very small 36x36x10 cm desktop case. But it has a Core i7, 32 GB RAM and 6 drives: 1 TB SSD, 500 GB SSD, 4 TB 3,5" HD, 1 TB 2,5" HD. And a slimline DVD drive and a floppy with cardreader. Has anyone managed to make a real floppy working in macOS ? 😉 Making use of the 8 bit LPT port for controlling external devices would be nice. The board has two infrared ports, but it seems it is no eHome compatible receiver for the Apple Remote. Despite the age it has a very big graphical BIOS/UEFI. There is also an AsRock H67M-GE/HT wich has VGA, DVI, HDMI and DisplayPort for the Intel HD 4000 graphics as well as an second front USB 3.0 controller. Whoever is searching a board which is fully OS X compatible, can use Windows XP or boot DOS from floppy, this is it. The serial ports are always turned on in my systems. Many are disabling them, but I've used them for cheap Wacom serial graphics tablets. I managed to get the touchscreen function on two monitors with different controllers working. Mavericks with UPDD version 6 and in Mojave with version 6 or 7. Edited Wednesday at 07:07 PM by naquaada Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Wednesday at 07:05 PM Moderators Share Posted Wednesday at 07:05 PM let's do one at a time, tell me exactly which one you want to update and if the bios is legacy or uefi, you see I have systems with bios and x58 and 775 cob on big sur, Ventura and Sonoma, do you have usb and hard disk available for testing? let's start from one of your hardware without mixing, we use opencore not clover so download a newer system than toi, i would start with BigSur or Monterey Link to comment Share on other sites More sharing options...
naquaada Posted Wednesday at 07:15 PM Author Share Posted Wednesday at 07:15 PM (edited) Actually, System 3 (Gigabyte GA-Q77M-DS2H) is the system on which I'm working now. I have everything working except graphics hardware acceleration and Sleep. Maybe it's because I have a Core i5 3570 in the system. The Intel HD2500 graphics unit seems to be problematic and I can't fully disable it in BIOS. I'm updating to an Core i7 3770S in a few days. I'm actually using Clover, installed in the EFI partition. I actually use Legacy BIOS because I didn't see advantages in UEFI. But because I'm not using multiboot and rarely boot from USB, switching to UEFI would be no problem if OpenCore requires it. Only System 4 has to remain BIOS for installing legacy operating systems like Windows XP. I hope that some of the last problems can be solved by switching to OpenCore. But I have no experience with it and it is difficult to configure it because I don't have a system new enough to run the neccessary tools. That's why I want to finish all systems (Mavericks, Mojave and Monterey) and then try the transition to OpenCore. Of course I found some DSDT.aml and whatever for my boards, but after installing them the system was worse or didn't even start. So I'm using on no system ACPI patches. That's why I absolutely have no clue of hardware patching, simply because I never needed it since I started with OSx86 nineteen years ago. If my graphics card requires some framebuffer patching to get hardware acceleration working, I wouldn't be able to do this. But I can use Darwin Dumper to get the Video ROM and more information. Because I've installed different operating system versions, Ive installed additional kexts in System/Library/Extensions on Leopard and Snow Leopard, and in /Library/Extensions on Mavericks and Mojave. Simply because it works. It is neccessary to copy some files to the Clover folder? I guess in OpenCore it is neccessary. I'm also using FakeSMC, also because it works. I tried VirtualSMC, but I think I had problems, so I switched back to FakeSMC. I have read somewhere that video decoding and DRM is usually done with the IGPU. Is this correct? I'm usually removing all kexts which are not neccessary. I think the System 3 wasn't even booting with the Intel HD4000 kexts installed. Edited Wednesday at 07:40 PM by naquaada Link to comment Share on other sites More sharing options...
naquaada Posted Wednesday at 07:57 PM Author Share Posted Wednesday at 07:57 PM (edited) Here is my Clover config file and an export of the System Profiler. I also attached a screenshot from Terminal with pmset. Even if i kill mds, the system won't sleep. The most important option is to change the CPU. Then all systems are better comparable. The ability to recover a system is always available. On my MBR systems I'm using a 256 MB FAT32 partition, so it is possible from a Linux live system to restore Clover. I also have for every system a bootable USB drive with Clover installed. The only reason why a board wasn't booting anymore was a wrong BIOS setting. Since I'm using the EFI partition now, I've written a small AppleScript file which is mounting the partition automatically. It has the hidden flag set so it doesn't appear in the Finder. For more advanced file operations I'm using Path Finder. This is another reason why I'm not often using the MacBook: Path Finder is taking a lot of CPU time, which results in loud fans. I have no idea why this program works so badly on Sonoma. config.plist.zip GA-Q77M-DS2H.zip Edited Wednesday at 08:18 PM by naquaada Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Wednesday at 08:15 PM Moderators Share Posted Wednesday at 08:15 PM I think that from opencore you can still disable the igpu and try to run the ati 6200 with OCLP Link to comment Share on other sites More sharing options...
naquaada Posted Wednesday at 08:21 PM Author Share Posted Wednesday at 08:21 PM (edited) Actually I can't configure OpenCore because it requires at least Mojave. Let's check if changing the CPU helps. The i5 was on the board as I got it. The i7 3770S has an Intel HD 4000, and a lower TDP (65 instead of 77). And I have a bigger cooler for it, the i5 has the stock Intel cooler. There are slight differences in the graphics cards: The GPRO 4200 uses Cape Verde PRO2, the GPRO 6200 uses Cape Verde PRO GL. But both are having the same ID 0x682b. Edited Wednesday at 08:26 PM by naquaada Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Wednesday at 08:22 PM Moderators Share Posted Wednesday at 08:22 PM 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 Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Wednesday at 08:55 PM Moderators Share Posted Wednesday at 08:55 PM 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 Link to comment Share on other sites More sharing options...
naquaada Posted Wednesday at 09:28 PM Author Share Posted Wednesday at 09:28 PM (edited) I found an 128 GB USB drive containing Monterey, probably a clone from my MacBook. It was prepared for my Asus Prime Z270-K because it had the Mac ID 'iMacPro1,1' in Opencore. With iMacPro1,1 iMac19,1 and actually MacPro6,2 it boots on my GA-Q77M-DS2H, but ends with a black screen. But the system is active, I can hear lots of hard disk activity. I can't boot in Mavericks, 'Mac OS version: Not yet set' Any ideas? I can edit the files on Mojave. There is only the simple bootloader. Can I do a safe boot without graphic drivers? I can't boot from the Monterey Recovery image. Edited Wednesday at 09:49 PM by naquaada Link to comment Share on other sites More sharing options...
naquaada Posted Thursday at 10:59 AM Author Share Posted Thursday at 10:59 AM @carlo_67 With your EFI folder I'm getting the message 'OC: Configuration requires vault but no vault provided!' I made some experiments and noticed I can boot from my old Mavericks installation, but not from the one I installed fresh. I changed in my OpenCore.plist the macmodel back to iMac13,2 and added the boot argument -no_compat_check and radpg=15. I can still boot Monterey, but get a black screen. What else can I do? Link to comment Share on other sites More sharing options...
naquaada Posted Thursday at 01:13 PM Author Share Posted Thursday at 01:13 PM (edited) Good news: My delidded Core i7 3770S works. The remaining on-die thermal paste were some hard crumbles, so it wasn't a bad idea. Before this I made a backup of my old installation, and during compressing the disk image the Core i5 was more than 100°C ! I've never seen something like this on my Ivy Bridge CPUs. As I removed the cooler, there was not much thermal paste on the Core i5. The mainboard must have been in an preinstalled system, instead of the 'Gigabyte' BIOS logo an OEM 'Hyrican' logo is shown. The BIOS is UEFI, but in pure text mode, no fancy graphics. But the original BIOS looked the same if I check the manual. But it will take a while because I can rebuild it. Because I added a huge cooler, I can't insert a 3,5" HD without removing the cooler or the mainboard. So I want to prepare a HD first, and I have to clone the 4 TB HDD from my main system. This will take some time. Edited Thursday at 01:52 PM by naquaada 1 Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Thursday at 04:59 PM Moderators Share Posted Thursday at 04:59 PM add inside the driver folder, it is already declared in the config.plist HfsPlus.efi.zip Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Thursday at 05:15 PM Moderators Share Posted Thursday at 05:15 PM 6 ore fa, naquaada ha scritto: With your EFI folder I'm getting the message 'OC: Configuration requires vault but no vault provided!' Open config.plist with OpenCore Configurator or ProperTree and set: Misc -> Security -> Vault = Optional Link to comment Share on other sites More sharing options...
naquaada Posted Thursday at 06:30 PM Author Share Posted Thursday at 06:30 PM I've changed it. Manually, because OpenCore configuratiorator doesn't work on Mavericks. But why is a new OpenCore configuration neccessary? The one on my Monterey USB drive is working, even with MacModel 13,2 like an Ivy Bridge system should have. I only have no graphics output. What is neccessary to get the graphics card working? The GPRO 4200/6200 are based on the Radeon R7 250X. I often read that it requires radpg=15. I guess this is a WhateverGreen option. On Monterey the AMD7000Controller.kext and AMDRadeonX4000.kext both are containing the device ID of my graphics card. In the attachment is the EFI folder of the Monterey USB drive. EFI_naquaada.zip Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Thursday at 08:09 PM Moderators Share Posted Thursday at 08:09 PM @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 Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted Thursday at 08:52 PM Moderators Share Posted Thursday at 08:52 PM 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 Link to comment Share on other sites More sharing options...
naquaada Posted Thursday at 10:35 PM Author Share Posted Thursday at 10:35 PM Sounds good. Is this plist based on my EFI folder's configuration? But this won't fix hardware acceleration in Mavericks and Mojave I guess. My 7000/X4000 kexts are somewhat modified, but I don't know anymore what I changed. I'm also having AMDVerde.kext and ATY_init.kext in System/Library/Extensions. My HD 7870 has device ID 6818 and uses Pitcairn XT. It is using Chutoro as Framebuffer. On the GPRO 4200 and 6200 Dashimaki and Futomaki are working. Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted yesterday at 05:04 AM Moderators Share Posted yesterday at 05:04 AM 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 Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted yesterday at 05:51 AM Moderators Share Posted yesterday at 05:51 AM 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 Link to comment Share on other sites More sharing options...
naquaada Posted yesterday at 07:26 AM Author Share Posted yesterday at 07:26 AM (edited) This really sounds good. But I'm still not finished with the hard disk. There is an unexpected problem. I'm using a 7200 rpm WD Black, and it gets very hot in my Sharkoon Quickport, I had more than 53°C. So after every cloned partition I have to shut down the computer, take the HD out and let it cool down for a long time. This makes the cloning process even longer. Can you give me links to an actual OpenCore installer and Configurator? As I tinkered last year with the Asus Prime, and there were two incompatible configuration files for OpenCore, is this problem solved? I can't check the contents of this installation, because I used the old Apple NVME SSD for experimenting. It is in an adapter which is 110 mm long, so I can't use it in my external case. But maybe there are some files on the SATA M.2 SSD. Edited yesterday at 07:27 AM by naquaada Link to comment Share on other sites More sharing options...
Moderators carlo_67 Posted yesterday at 07:43 AM Moderators Share Posted yesterday at 07:43 AM 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/ Link to comment Share on other sites More sharing options...
naquaada Posted yesterday at 07:54 AM Author Share Posted yesterday at 07:54 AM Wow, you are replying quickly 👍 After I used the EFI partition, it was a bit annyoing to mount it every time. So I wrote three AppleScript files which can mount the EFI partition on drive 0, 1 or 2. I just need to add them in the startup objects. I also wrote a tool to kill the disk cache. This can get very large, I had values over 10 GB. Using the terminal command 'sudo purge' this cache can be cleared and frees lots of memory. I wrote an AppleScript file for this. Can you use these tools? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now