Jump to content
142 posts in this topic

Recommended Posts

https://github.com/laobamac/SimpleRTK5

 

RTL8126 driver porting has been completed. ( RSS is being implemented, and support will be added later)

 

125ab56a689dd795ff6a9dfb4559feba.thumb.png.3ced47ea68621372e2af71626052d641.png

 

 

Edited by laobamac_yyds
  • Like 5
  • Thanks 3
On 1/27/2026 at 11:25 PM, kaoskinkae said:

The three computers are perfect; two of them are New and OLD1 with Radeon RX570 and RX560 graphics cards, and the third, OLD2, has a counterfeit Intel graphics card (see my specs). Everything works perfectly with the modified, unofficial Lilu.kext kext instead of WhateverGreen.kext, but I've noticed a graphics error, which I've included along with the screenshots. I don't know if it's a beta issue or a bug in Lilu.kext.

 

 

 

 

 

 

I went back to the last beta and no artifact so I think I'll stick with 25D5101c for now. Those small things bug me lol.

I don't use WEG.

For the record OCLP 3 daily is fine with my broadcom wifi but I revert the patch for upgrades then just patch again. And for cloning with superduper.

 

Off topic, I need to do this (picked it up somewhere ages ago) to get the patch AND the revert patch done otherwise I get a pending update error.

 

In Terminal type:

diskutil info / | grep "Device Node"

Which gave me this for my EFI partition, change the rest of the steps to match your setup: Device Node: /dev/disk2s10s1

Then to fix the EFI partition so root patches can be applied:

sudo mount -o nobrowse -t apfs /dev/disk2s10 /System/Volumes/Update/mnt1

sudo bless --folder /System/Volumes/Update/mnt1/System/Library/CoreServices --bootefi --create-snapshot

 

 

  • Like 1

A couple of good news items to report about macOS Tahoe:

  • Lilu.kext 1.7.2 Beta fixes the Tahoe update problem.  With Lilu.kext 1.7.2, I no longer need to add boot-arg -wegnoegpu to update Tahoe.  Note that I still need to temporarily disable BluetoolFixup.kext to allow incremental updates.
  • Tahoe 26.3 Beta 3 has fixed the poor Polaris GeekBench 6 Metal performance that I was seeing.  With earlier versions of Tahoe 26.3, my RX 560x GB6 Metal scores had dropped from ~24K to ~19K.  With Tahoe 26.3 Beta 3, GB 6 Metal Scores are back to ~24K.
    Spoiler

    Screenshot2026-01-28at10_55_53PM.png.0d10dee19b700e5d439b5a6357394068.png

     

  • Like 9
On 12/29/2025 at 2:19 AM, MakAsrock said:

Try OCLP 3.0.0 Nightly 😊

Any suggestions?macOS 26.2

Screenshot 2026-01-28 at 1.15.28 am.png

  • Sad 1
50 minutes ago, HurricaneX said:

Any suggestions?macOS 26.2

Screenshot 2026-01-28 at 1.15.28 am.png

If a root patch has already been applied, that's how it should be. You need to revert it. In another wise, wait for an official solutions.
For me, everything looks different:

Снимок экрана 2026-01-29 в 15.39.38.jpg

Edited by MakAsrock
  • Like 1
1 hour ago, HurricaneX said:

Any suggestions?macOS 26.2

That is exactly what you would expect to see if you attempt to apply OCLP patches to Tahoe with the "official" OCLP 3.0.0 "Nightly."  The OCLP Devs have not yet released OCLP for Tahoe.  You would need to use one of the unofficial OCLP forks to patch Tahoe.

Edited by deeveedee
  • Like 2
1 hour ago, deeveedee said:

That is exactly what you would expect to see if you attempt to apply OCLP patches to Tahoe with the "official" OCLP 3.0.0 "Nightly."  The OCLP Devs have not yet released OCLP for Tahoe.  You would need to use one of the unofficial OCLP forks to patch Tahoe.

Solved!!! Just back to Hackintosh after few months,my bad for the information gap

Screenshot 2026-01-29 at 11.29.57 pm.png

  • Like 2
22 hours ago, laobamac_yyds said:

https://github.com/laobamac/SimpleRTK5

 

RTL8126 driver porting has been completed. ( RSS is being implemented, and support will be added later)

Dear @laobamac_yyds,

 

I appreciate any work derived from my macOS ethernet drivers and the GPL gives you the right to modify and redistribute the derived work, but it also requirers to respect copyrights of the original authors. Unfortunately, I noticed that you don't comply with this requirement because you copied large portions of the code from LucyRTL8125Ethernet to your project without even mentioning my original work. Instead of that you took great effort to remove any copyright notice from the copied code. I expect you to comply with the GPL and copyright law and therefore ask you to take action that your project will be fixed to respect my work.

 

Regards

 

Laura Müller aka Mieze 😺

  • Like 7
  • Thanks 1
14 minutes ago, Mieze said:

Dear @laobamac_yyds,

 

I appreciate any work derived from my macOS ethernet drivers and the GPL gives you the right to modify and redistribute the derived work, but it also requirers to respect copyrights of the original authors. Unfortunately, I noticed that you don't comply with this requirement because you copied large portions of the code from LucyRTL8125Ethernet to your project without even mentioning my original work. Instead of that you took great effort to remove any copyright notice from the copied code. I expect you to comply with the GPL and copyright law and therefore ask you to take action that your project will be fixed to respect my work.

 

Regards

 

Laura Müller aka Mieze 😺

I will add back the relevant copyright information as soon as possible.Don't misunderstand, deleting them was not my intention.During the process of optimizing code format, Gemini will indiscriminately remove all content marked with comments.

 

Best regards.

 

PS:If I have time, I hope to reply to my PM. This is just a small request, and it's okay if it's not convenient for some reason.

 

------EDITED AT 00:13-----

Copyright information has been added back to all files containing source code used in LucyRTL8125Ethernet

Edited by laobamac_yyds
  • Like 8
  • Thanks 1

Ok, so I updated.  But, Tahoe is still a problem on my system.  It still is running my system very hot.  I've tried to reduce transparency and even turned off indexing - no diff. I am regularly at 72 degrees on some parts of my motherboard and the fans (a water cooler) runs high all the time.

 

So, in doing research on this issue, I see that the usual methods to reduce transparency actually don't really work - reviews show that for many users, this option (in system settings) is pretty ineffective - lots of user complaints , but no action on Apple's part to address the issue.  The two dual programs, identityservicesd and transparencyd just are uncontrollable, apparently.  Too bad.

 

This does not happen on Windows, Sonoma, Sequoia, or Linux Mint - only Tahoe does this. They are all running on the same computer, just different drives. I keep hoping that Apple will address this but after four beta releases, and change, I just don't think so.

 

Screenshot2026-01-29at4_39_41PM.png.f59bae49a9f9a4cbad197a0d9ab940e9.png

Edited by meg2014
  • Sad 1

@meg2014 Tahoe 26.3 Beta 3 is working very well for me on 3 different Intel-based systems (10th Gen laptop with iGPU-only, 8th Gen desktop with iGPU-only and 8th Gen desktop with Polaris dGPU)  All have 32GB DDR4 RAM.  The settings I use are here.  72 degrees on a water-cooled system sounds high.  Try changing your temp scale from deg F to deg C :)

 

If you haven't figured it out, post your EFI and specify your CPU / Intel chipset / memory.

  • Like 2

@deeveedee and @eSaF:

 

Thanks for your responses.  I think, when I can download the full version of Tahoe 26.3 B4, I am going to do a complete reinstall.  I didn't hit this problem until 26.3.  26.2 was ok, so I am going to guess something in my system is causing this.

 

On my M1 mac, transparencyd and identityservicesd  don't continuously run like they do on my Intel Tahoe install.  (I just upgraded the M1 to 26.3 B4).  And the M1 Macbook is a good system, but it does not have the capabilities that my Intel system has.

 

Based on my research, I am not the only one who has experienced this - a lot of folks have experienced this and complained, mostly about the transparency fiasco.  The thing is my system is a very capable system, with a very fast CPU and GPU, so it has to be something else in the system, my system, that caused this.

 

My signature is not showing up, so my system is an Asus Z790 motherboard with a 14700K CPU, 32GB of DDR5 RAM, Sapphire 6800XT GPU.  it benchmarks very well, but the only issue is as I have discussed here.  Sequoia is great on this build.  Sonoma too, as are Linux Mint and Windows 11.

 

No worries about burning up the CPU.  I rarely use the Tahoe partition on this system.  I haven't booted up Tahoe in over two weeks, so not used very often. Mostly, when I want to use a Mac on this system, I'm either in Sequoia, or Sonoma.  This is a beta machine, all the Mac partitions are beta, only Windows and Linux are not beta.

Edited by meg2014
  • Like 1

It's not unusual for things to break (and then get fixed) with each beta update.  A walk through macOS release history will reveal many examples of this.  Sequoia works perfectly for me on all of my platforms and Tahoe 26.2 has no issues for me.  Tahoe 26.3 clearly isn't yet fully baked.

 

EDIT: I don't switch my production systems to the next major macOS until the new major macOS is required for continued Xcode upgrades.  This usually happens at version .4 or .5.  I'm optimistic that we'll have a solid new macOS by Tahoe 26.4.  Until then, Sequoia is outstanding.  For Intel-based Mac/Hack users, the wait will be worth it.

Edited by deeveedee
  • Like 4

So, I rebuilt Tahoe with B4 from scratch and the overheating problem I was having seems to be resolved.

 

The operative phrase there is "seems" 

 

So why do I say that?  Anyone who spends just a little time with Tahoe on an Intel platform will find so many bugs its really not worth the time - almost.  I am posting this from Sequoia because a new bug in Tahoe has shown up just recently - a graphical blurry square around my mouse cursor.  I'm not even going to bother trying to find out what it is and how to fix it. 

 

This is just one of so many bugs that I'm just done with Tahoe.  Like it has in the past, my Tahoe install on my Intel system is just going to sit, unused.  I will continue to upgrade it, but until Apple truly upgrades it and resolves all the bugs, I'm not going to use it, and its just going to sit.

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