Jump to content
1961 posts in this topic

Recommended Posts

22 minutes ago, cankiulascmnfye said:

 

Well that's not an issue of the app, that's a layer 8 problem… ;)

True, what I meant was it would have been great to incorporate two modes: basic/advanced where basic has some sort of limiter, so newbies won't damage their equipment. I personally love it, that's why I installed it on my gf laptop. I'm just trying to warn others what could happen if not careful.

But we're going way off-topic here 🤓 

Edited by ivak4eto
  • Like 1

For those who need multiple displays in Sequoia, I have started conducting dual-GPU tests for my hack here.  This is the first that I am testing Radeon graphics in Big Sur or later (my last Radeon experience was with Catalina) and I must say - Sequoia handles dual-GPU (Intel and Radeon) beautifully and seamlessly.  Based on my limited testing, those who need multiple displays do not need to feel limited or constrained by the number of graphics ports on their Radeon dGPU.

 

EDIT: I'm a newbie when it comes to Radeon graphics, so I apologize for what may be a remedial question: Are there any use cases that necessitate configuration of the Intel iGPU as headless when installing a Radeon dGPU?  If so, what breaks if the Intel iGPU is not configured as headless when a Radeon dGPU is installed?

 

I ask only because the hackintosh Radeon guides that I have read specify a headless iGPU configuration when installing a Radeon graphics card.  I never questioned this until I found myself limited by a single dGPU-connected graphics port on my hack.  Now, I am finding that the iGPU can be fully enabled/configured (not headless) and all graphics ports (dGPU-connected and iGPU-connected video ports) benefit from Radeon graphics acceleration.

Edited by deeveedee
  • Like 3
2 hours ago, deeveedee said:

I ask only because the hackintosh Radeon guides that I have read specify a headless iGPU configuration when installing a Radeon graphics card.  I never questioned this until I found myself limited by a single dGPU-connected graphics port on my hack.  Now, I am finding that the iGPU can be fully enabled/configured (not headless) and all graphics ports (dGPU-connected and iGPU-connected video ports) benefit from Radeon graphics acceleration.

 

There's a reason for configuring the iGPU headless - at least when using an iMac SMBIOS: the iGPU is utilized for Intel Quick Sync Video and HEVC encoding/decoding in the case. My RX580 has 4 ports. Why would I use the iGPUs output in this case while sacrificing iQSV and HEVC capabilities, when I could connect 4 displays to the GPU directly?

Edited by cankiulascmnfye

@cankiulascmnfye I didn't question your need for additional graphics ports.  My dGPU has a single DP port, so I can't use headless iGPU if I want multiple displays. 

 

Have you tested your iMac with a non-headless iGPU to demonstrate that  Intel Quick Sync Video and HEVC encoding/decoding does not work (so it only works with iGPU headless configuration)?

 

EDIT: My VideoProc Hardware Info (with non-headless Intel iGPU and Radeon RX 560x):

Spoiler

Screenshot2024-07-02at1_59_45PM.png.7066ab4baf1199cb13a06f78dc471c8e.png

 

EDIT2: My question could quickly go beyond the scope of this Sequoia thread.  If you have constructive comments / responses, please post them in my hack-specific thread here.  Thank you.

Edited by deeveedee
On 6/30/2024 at 1:39 AM, CloverLeaf said:

 

Yea, I am familiar with the commands but I think that -igfxbrs should be -igfxbls. Correct me if I am wrong.

Yes master! You are right. I was using this command incorrectly. Thank you for the correction.

 

 

  • Like 2
20 hours ago, deeveedee said:

@cankiulascmnfye I didn't question your need for additional graphics ports.  My dGPU has a single DP port, so I can't use headless iGPU if I want multiple displays. 

 

Have you tested your iMac with a non-headless iGPU to demonstrate that  Intel Quick Sync Video and HEVC encoding/decoding does not work (so it only works with iGPU headless configuration)?

 

EDIT: My VideoProc Hardware Info (with non-headless Intel iGPU and Radeon RX 560x):

  Reveal hidden contents

Screenshot2024-07-02at1_59_45PM.png.7066ab4baf1199cb13a06f78dc471c8e.png

 

EDIT2: My question could quickly go beyond the scope of this Sequoia thread.  If you have constructive comments / responses, please post them in my hack-specific thread here.  Thank you.

 

Actually, I tried using the iGPU to drive a display AND using it for actual rendering in DaVinci Resolve when my previous GPU died. And it wasn't an experience I would recommend. 

  • Like 1

@cankiulascmnfye My experience is very different from yours.  See my observations here.

 

Maybe Sequoia has improved dual-GPU support or you experienced a Layer-8 problem?

 

EDIT: I haven't tested DaVinci Resolve with dual-GPU and I don't use it.  Hopefully others can test.

 

EDIT2: @cankiulascmnfye I just re-read your last post and believe you are claiming that DaVinci Resolve rendering performance is not good with iGPU-only.  I'm not surprised, but as you know, I believe that is already widely known and that is not at all what I am claiming.  Seems like we have a communication issue - that is definitely Layer-8.  Could be me - not sure.

Edited by deeveedee
On 6/28/2024 at 8:07 AM, URBANsUNITED said:

Hi!

 

Does anybody else have problems with iCloud Drive?

I can't connect from Finder to it, even I am using my iCloud account

I am on the Beta 2  - 24A5279h

Haswell with MacPro7,1 SMBios

 

image.png.ddb373982edf273912a47f0dae6ef7d4.png

image.png.f0d91eedf314d599c7472caf0516250e.png

 

image.png.278d851ca2adfa616d91004ba750c42c.png

 

 

Thanks

 

URBANsUNITED

 

 

 

 

Found the reason for my iCloud Drive problems:

 

If the Home dir is not on the main HDD aka you move your home dir -  the desktop, download etc folders to a different HDD/partition on macOS Sequoia, you'll loose the iCloud Drive sync feature!

I did some tests and you can sync iCloud Drive only with the original location of home dir.

It's a shame as on previous systems this feature was given and suffered no issues. Maybe it is a beta bug, but I believe not.

But it is strange, that the function still officially exists...

image.png.852f777e0450f3a0d8a6779481a81060.png

 

Cheers

 

URBANsUNITED

 

 

 

  • Like 3
4 hours ago, deeveedee said:

@cankiulascmnfye My experience is very different from yours.  See my observations here.

 

Maybe Sequoia has improved dual-GPU support or you experienced a Layer-8 problem?

 

EDIT: I haven't tested DaVinci Resolve with dual-GPU and I don't use it.  Hopefully others can test.

 

EDIT2: @cankiulascmnfye I just re-read your last post and believe you are claiming that DaVinci Resolve rendering performance is not good with iGPU-only.  I'm not surprised, but as you know, I believe that is already widely known and that is not at all what I am claiming.  Seems like we have a communication issue - that is definitely Layer-8.  Could be me - not sure.

 

Well, you are claiming that you have a dual-gpu setup now. To me, a dual GPU-setup consist of 2 physical, dedicated, identical graphics cards. What you have configured is a GPU/iGPU combo. Whatever works for you, but I doubt that anybody will test this simply because a) it's uncommon to have a GPU with only one output. And b) if I recall correctly, running the iGPU to display a picture alongside a GPU requires additional tweaks to the framebuffer patch to make it work.

@cankiulascmnfye Please forgive me - I didn't realize there was a proper name for what I was calling dual-GPU.  I'll defer to your naming expertise.  

 

My EFI is public and readily available for inspection if you want to see my additional tweaks.  You'll see that they are all normal WEG DeviceProperties - nothing special.

 

Based on my findings, those who have a dGPU with suitable graphics acceleration but an insufficient number of graphics ports can extend their port-count by using iGPU ports to supplement.  There is no need to buy a new dGPU with more ports.  For example, someone with a 2-port dGPU who needs 3 displays could augment the dGPU with an iGPU port with no performance degradation and no loss of dGPU or iGPU acceleration.  I posted here in this thread since I've never seen anyone post about it before and was hoping for some valuable / constructive feedback.  Maybe my observations are unique to Sequoia, or maybe they're unique to my hack, but I don't know because I have never tested.

 

Thank you for your feedback. The pleasure was all mine.

 

EDIT: I have added a note here for any readers who are confused by my use of the term "dual-GPUs."

Edited by deeveedee
  • Like 4

It would be much more important than WiFi if the nVidia GeForce GTX780M and other nVidia graphics cards

were supported by OCLP 1.6 or higher for Sequoia.

 

There are enough USB alternatives for WiFi, so you don't necessarily need patches for Broadcom things.

  • Like 2
2 hours ago, eSaF said:

My observations so far after applying this stand alone patch.

As mentioned, WiFi indicates it is connected and working as all nearby Networks are shown.

AirDrop is now working wirelessly in both directions.

HandOff to iPhone wirelessly does not work and causes the p/c to lockup forcing a hard reset although it does work wired.

Maybe when OCLP becomes available for Sequoia that glitch will be solved.

Not sure why can't you apply the path using Nightly.

Have you tried different SMBIOS?

After I applied the patch, WiFi/BT is working.

Airdrop working both ways.

HandOff working fine wirelessly and wired.

 

Someone mentioned 5G. It's working fine: 5G/80MHz, Tx Rate 867Mbps

  • Like 2
{"bug_type":"210","timestamp":"2024-07-04 08:17:59.00 +0200","os_version":"macOS 15.0 (24A5279h)","roots_installed":0,"incident_id":"2A488B58-A1B5-47D4-9BA1-11022304DB81"}
{"macOSProcessedStackshotData":"bm8gb24gZGlzayBvciBzbGVlcC93YWtlIGZhaWx1cmUgcGFuaWMgc3RhY2tzaG90IGZvdW5k","macOSPanicString":"panic(cpu 2 caller 0xffffff80160bbc7e): Kernel trap at 0xffffff80165ab814, type 14=page fault, registers:\nCR0: 0x0000000080010033, CR2: 0x0000000000000150, CR3: 0x0000002ea6edf000, CR4: 0x00000000003406e0\nRAX: 0xffffff91cf508260, RBX: 0xffffff91cf508260, RCX: 0xffffffd2194c7e78, RDX: 0x0000000000000000\nRSP: 0xffffffd2194c7df0, RBP: 0xffffffd2194c7df0, RSI: 0xffffff96986beb00, RDI: 0x0000000000000000\nR8:  0xffffffd2194c7e70, R9:  0xffffffd2194c7e74, R10: 0xffffffd7cde63050, R11: 0x0000000000000000\nR12: 0xffffff9b62005800, R13: 0xffffff8d067a93d0, R14: 0x00000000194c7e78, R15: 0x0000000000000000\nRFL: 0x0000000000010283, RIP: 0xffffff80165ab814, CS:  0x0000000000000008, SS:  0x0000000000000010\nFault CR2: 0x0000000000000150, Error code: 0x0000000000000000, Fault CPU: 0x2, PL: 0, VF: 0\n\nPanicked task 0xffffff969b4529b0: 24 threads: pid 500: ContinuityCaptur\nBacktrace (CPU 2), panicked thread: 0xffffff9697ab9598, Frame : Return Address\n0xffffffd2194c76d0 : 0xffffff8015f5f581 \n0xffffffd2194c7720 : 0xffffff80160cbeac \n0xffffffd2194c7760 : 0xffffff80160bb52b \n0xffffffd2194c7820 : 0xffffff8015ef5971 \n0xffffffd2194c7840 : 0xffffff8015f5f877 \n0xffffffd2194c7940 : 0xffffff8015f5ef12 \n0xffffffd2194c79b0 : 0xffffff80167d44d8 \n0xffffffd2194c7aa0 : 0xffffff80160bbc7e \n0xffffffd2194c7c20 : 0xffffff80160bb97d \n0xffffffd2194c7ce0 : 0xffffff8015ef5971 \n0xffffffd2194c7d00 : 0xffffff80165ab814 \n0xffffffd2194c7df0 : 0xffffff8019b40029 \n0xffffffd2194c7e20 : 0xffffff801661c015 \n0xffffffd2194c7eb0 : 0xffffff80165b0687 \n0xffffffd2194c7f40 : 0xffffff801663b162 \n0xffffffd2194c7fa0 : 0xffffff8015ef5db6 \n      Kernel Extensions in backtrace:\n         com.apple.iokit.IOSkywalkFamily(1.0)[035A9AD9-6CDE-362F-8DEC-B664BC6431EC]@0xffffff8019b3d000->0xffffff8019bfbfff\n            dependency: com.apple.driver.mDNSOffloadUserClient(1.0.1b8)[0A313F93-C7BD-349E-A87E-51700E341780]@0xffffff80183c7000->0xffffff80183cbfff\n            dependency: com.apple.iokit.IONetworkingFamily(3.4)[FCB9BFDD-93F0-3784-8274-3D4DB73BF90E]@0xffffff801816c000->0xffffff8018181fff\n\nProcess name corresponding to current thread (0xffffff9697ab9598): ContinuityCaptureAgent\nBoot args: revpatch=cpuname,sbvmm \n\nMac OS version:\n24A5279h\n\nKernel version:\nDarwin Kernel Version 24.0.0: Thu Jun 20 20:36:19 PDT 2024; root:xnu-11215.0.115.501.3~1\/RELEASE_X86_64\nKernel UUID: DABA6728-61F5-3F9E-A198-C49749A456CA\nroots installed: 0\nKernelCache slide: 0x0000000015c00000\nKernelCache base:  0xffffff8015e00000\nKernel slide:      0x0000000015ce4000\nKernel text base:  0xffffff8015ee4000\n__HIB  text base: 0xffffff8015d00000\nSystem model name: MacPro7,1 (Mac-27AD2F918AE68F61)\nSystem shutdown begun: NO\nPanic diags file available: YES (0x0)\nHibernation exit count: 0\n\nSystem uptime in nanoseconds: 187081208341\nLast Sleep:           absolute           base_tsc          base_nano\n  Uptime  : 0x0000002b8ee8b3c4\n  Sleep   : 0x0000000000000000 0x0000000000000000 0x0000000000000000\n  Wake    : 0x0000000000000000 0x0000001c132dda8c 0x0000000000000000\nCompressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space\nZone info:\n  Zone map: 0xffffff81c3d9a000 - 0xffffffa1c3d9a000\n  . PGZ   : 0xffffff81c3d9a000 - 0xffffff81dbd9b000\n  . VM    : 0xffffff81dbd9b000 - 0xffffff86a50ce000\n  . RO    : 0xffffff86a50ce000 - 0xffffff883d734000\n  . GEN0  : 0xffffff883d734000 - 0xffffff8d06a67000\n  . GEN1  : 0xffffff8d06a67000 - 0xffffff91cfd9a000\n  . GEN2  : 0xffffff91cfd9a000 - 0xffffff96990cd000\n  . GEN3  : 0xffffff96990cd000 - 0xffffff9b62400000\n  . DATA  : 0xffffff9b62400000 - 0xffffffa1c3d9a000\n  Metadata: 0xffffffd1e8d34000 - 0xffffffd208d34000\n  Bitmaps : 0xffffffd208d34000 - 0xffffffd218d34000\n  Extra   : 0 - 0\n\n\n\n"}

Hang using continuity Cam with OCLP nightly

wifi and airdrop are working well

  • Like 3

Good morning, is Preview working fine after applying modern wireless root patch?

And does the system look as fluid as without the patch?

 

EDIt: answered here.

 

Xcode 16 beta 1 was pretty unusable but beta 2 works much better.

Edited by miliuco
Add link
  • Like 2
3 hours ago, eSaF said:

@Anto65 and @Irish_Man What boot-arg are you using also are these two kexts AMFIPass.kext and RestrictEvents.kext?

As I stated I can't install and get the latest nightly to patch Sequoia, in Sonoma everything works perfect so I don't think it has

anything to do with the SMBIOS as surely the problem would show there as well.

 

Sorry when I said Handoff not working, I meant it is working wirelessly for everything except to iPhone Camera

which only works wired, Mail, Messages, Web pages etc all work wired and wireless.

Use amfipass kext 1.4.1

Restrictevent I don't use it as I use iMac as smbios, I think that the latter is irrelevant anyway, I recommend those of lorys89 it doesn't need boot-args
Not having Apple devices I can't comment on 'Continuity Camera' etc. 🤷

For the rest it works

  • Like 2
1 hour ago, miliuco said:

Good morning, is Preview working fine after applying modern wireless root patch?

And does the system look as fluid as without the patch?

I answer myself. With AMFIPass.kext 1.4.1 and the latest OLCP sequoia development branch apparently everything works well:

  • information about wifi displayed in places where it was missing
  • good Internet connection
  • Preview works as it should
  • system works smoothly.

So far, I don't see anything different regarding the patch in Sonoma.
iMac20,2 without RestrictEvents.

 

@eSaF

Continuity camera only by USB, not wifi.

 

Edited by miliuco
Fix typo
  • Like 6
  • Thanks 1
Guest
This topic is now closed to further replies.
×
×
  • Create New...