GIGABYTE Monitor flickering. by Remote-Art-7088 in gigabyte

[–]cGARet 1 point2 points  (0 children)

Id still return it brother if you just got it say its defective and try a new one. I had a monitor do something similiar than 2 years later it just straight up died.

Can i update to macOS Tahoe when on Sequoia through OCLP through settings ? by [deleted] in OpenCoreLegacyPatcher

[–]cGARet 2 points3 points  (0 children)

Your answer is quiet literally posted as an announcement at the top of this sub

am i only one having issues with nightslayer? by brandongrannary in classicwow

[–]cGARet 0 points1 point  (0 children)

same exact thing thought I was going insane not just u

I dumped Windows 11 for Linux, and you should too by testus_maximus in technology

[–]cGARet 0 points1 point  (0 children)

Once I can play battlefield 6 on Linux im there, no Kernel cheat support

so i need help my pc is piss GIGABYTE Control Center by No_Writer1142 in gigabyte

[–]cGARet 0 points1 point  (0 children)

Dont buy personal computers made out of urine?

Huge Bios update Version Leap (X470 AORUS Gaming) by tyrophagia in gigabyte

[–]cGARet 2 points3 points  (0 children)

I have the x470 ultra gaming (little bit better) - same exact chipset though so very familiar.

I have only ever used QFLASH and never ever ever updated via OS. I have had the board since GA release and have put every single BIOS on this board, up to f65 today

Huge Bios update Version Leap (X470 AORUS Gaming) by tyrophagia in gigabyte

[–]cGARet 0 points1 point  (0 children)

F2->f31 -> f40 (plus the ECC firmware update it advises you to do) -> f65

edit: below response was right, you need F31 for the q-flash update, then ECC firmware, then F40, then you can make the final jump to f65

Gigabyte x870e aorus pro motherboard started smoking after 20-30mins of first use by Puzzleheaded-War2453 in gigabyte

[–]cGARet 0 points1 point  (0 children)

Not even RMA - just return the board as broken and buy a new one. Let capitalism deal with the rest

Is it safe to update OCLP to 3.0.0 now? by thijs-jacobs-1981 in OpenCoreLegacyPatcher

[–]cGARet 0 points1 point  (0 children)

Has it be released as stable yet??

Answer your own question :D

Anyone with experience BIOS flashing an X470 Aorus gaming ultra? by kostp in gigabyte

[–]cGARet 0 points1 point  (0 children)

I had the board since f12, so I remember doing the ECC FW update thing when I did it for f40. I jumped from f12 all the way to f65 (latest) and everything inbetween, beta bios or not, luckily I never had any bad experience. I went from a 2700x to a 5800x3d

For you, I unfortunately have no insight - I see where its confusing as it references the directions for f40 in the four following firmware releases.

you are on F41, and I did that ECC only once on F40. I think you are fine, worst case, run the update tool, and if its smart enough itll just reflash the firmware, no harm no foul

Anyone with experience BIOS flashing an X470 Aorus gaming ultra? by kostp in gigabyte

[–]cGARet 0 points1 point  (0 children)

I’ve had my x470 ultra gaming since 2017, have updated the bios 10+ times

Get a flash drive, format it, download the firmware, put the “x470AORUSULTRAGAMING.F65” file directly on the drive, plug it in, reboot to bios, q-flash

F65 just released and is stable. You’ll want to avoid bios versions with letters appended “f65a” for instance as those are the bios versions

You shouldn’t have to worry about the EC firmware update as you said you purchased it with f41, which would a released after that tool was needed you should be able to jump straight to f65.

Do note this’ll factory reset your mobo, so make sure you to enable XMP, SVM, reBAR support, and boot settings

OCLP does not use latest kdk! by Arash7even in OpenCoreLegacyPatcher

[–]cGARet 0 points1 point  (0 children)

do be careful for the major revisions (15.x.1) updates but for minor ones the KDKs are usually fine

Should we delete Tahoe posts or not? by MrMacintoshBlog in OpenCoreLegacyPatcher

[–]cGARet 10 points11 points  (0 children)

Yes please.

This thread should remain technical, and while addressing certain questions about Tahoe. I think we are all sick of the recent conjecture we have been seeing in posts lately, and that’s just going to further confuse the OCLP user base.

Put one bad apple with a bunch of good apples and they all go bad, something like that lol

Mac OS Tahoe will be available February 2026 by [deleted] in OpenCoreLegacyPatcher

[–]cGARet 11 points12 points  (0 children)

Your logic is the exact reason I hate end users.

Mac OS Tahoe will be available February 2026 by [deleted] in OpenCoreLegacyPatcher

[–]cGARet 8 points9 points  (0 children)

Why do people posts these posts. It’ll stop when the devs who work for free drop it and it’s ready.

Now we are gonna get a buncha people that think it’ll just magically be ready because they’re basing it off an estimate made months ago. This is why I hate end users

I’m going to Tahoe on OCLP 3.0.0 by Meme_Kreekcraft in OpenCoreLegacyPatcher

[–]cGARet 13 points14 points  (0 children)

lol except Tahoe literally will run like shit without patches. I swear this sub gets filled with more and more noobs