All Activity
- Yesterday
-
Phew. Finally finished the new version of the Q77M-DS2H. It now has a dellidded i7 3770S with fresh Arctic MX-6. I use a Scythe Ninja Mini with two 92mm CPU fans and two 120 mm case fans. In normal use and with closed case the cpu is about 40°C, but the cooler fans are actually limited to 5V to be quieter. A stresstest was creating a disk image using bzip2 compression. Disk Utility uses 780% CPU time, the rest ist used by the system, so this is a really good method to max out the CPU. 55°C was the highest temperature. I'm using a Sharkoon Quickport Internal removeable drive bay for a 5 1/4" slot. It has one 2,5" drive and one 3,5" drive, as well as two USB 3.0 ports. I also added a DVD drive, but I know I have somewhere a BluRay drive. The 4 TB HD I prepared didn't fit in the case, so it got a Seagate 5 TB 2,5" HD. It is 15 mm high and rather fast for its size. I still have one PCI port and one PCI-E x 16 port (4x speed) free. That's how I like it. Everything squeezed into a compact, silent case and still expandable.
-
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/ 😜
-
macOS Sonoma 14.7.6 (23H616 ) 👍 ci ha messo un po ma alla fine è riuscito ad installarsi- alla prossima
-
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?
-
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/
-
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.
-
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
- Last week
-
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.
-
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
-
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
-
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
-
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.
-
-
@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?
-
sonicman66 joined the community
-
SheldonCoop joined the community
-
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.
-
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
-
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.
-
I think that from opencore you can still disable the igpu and try to run the ati 6200 with OCLP
-
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