Jump to content
286 posts in this topic

Recommended Posts

I analyzed the attached EFI, and I think it's more correct to use desktop id since the flags and index have the same values in the patch. I'm attaching a screenshot of the patch for you to test. If you try this patch, try logging in.

image.png.8544ce1c47b3cb3cca8a017204276432.png

 

To use AAPL,ig-platform-id Desktop you need to add the spoof device-id.

As you can see below, this way you avoid adding unnecessary patches. Force Online might fix random black screens on startup.

Screenshot 2026-01-04 alle 01.06.10.png

 

I3 9100 https://www.intel.com/content/www/us/en/products/sku/134870/intel-core-i39100-processor-6m-cache-up-to-4-20-ghz/specifications.html

 

 

 

Screenshot 2026-01-04 alle 01.13.39.png

Edited by Baio77
  • Like 1

@Baio77 Your suggestion may work.  Acidanthera says here that CPUs with device-id 0x3e91 should be "spoofed" as device-id 0x3e92.  See my post here where I recommended that brumas2025 try device-id 0x3e92.  device-id 0x3e92 is a Desktop ID (same as i5-9600).

 

brumas2025 tested framebuffer platform-id 0x3e9b0007.   it worked for him after we modified the busIDs.  See here.  It appears that once the busIDs are properly patched, both mobile and desktop framebuffers can be used.  Note that he started this thread with framebuffer platform ID 0x3e9b0007 when only a single display was working.  That's why we tried other framebuffer Platform IDs.  Now that we have more test results, it appears that as long as the busIDs are patched, he can use mobile and desktop framebuffers.  See his test results here.

Edited by deeveedee
  • Like 1

@Baio77  I'm not sure what you're trying to say, but I trust you know what you're talking about.  I have a feeling there is more than one right answer. 

 

EDIT: I think you're saying that with ig-platform-id 0x3e9b0007, we don't need to patch the indices and flags because the framebuffer already defines them. If that's what you're saying, then yes, we already know that. Review the EFIs posted earlier in this thread.

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

EDIT2: @Asural I'm not confident that the problem has anything to do with ACPI patching (I doubt it).  I think the fact that displays "worked" after new ACPI patches were included in the EFI was just a timing glitch.  Don't give up on the ACPI patches, since they'll only improve his hack, but I'd continue to think about settings / configuration that would affect display initiation timing.

 

@brumas2025 In your BIOS, do you have an option for "Fast Boot" or something similar?  If so, please make sure that this setting is "Disabled" in BIOS.

 

I removed the arguments as you advised, but nothing has changed...

Quote

4.png.d41033b120d37b449cb6c5ede547f730.png

Quote

5.png.528eb51a2839509a77c4c6c05ef094a1.png

Quote

3.png.f50115fc63533b4fda64e1f2ac06ad38.png8.png.810abeb47790a3d6f2df2abd08034ee4.png

6.png.914e5b7f811f6fb6f2988f0d81e29767.png7.png.95ac604c09e02dfe15b9ff0f18b116f0.png

2.png.96b702e457e645a5375118e58bd05e3c.png1.png.1f3a865b61ab7c98c0e809de817ef347.png

 

37 minutes ago, brumas2025 said:

I removed the arguments as you advised, but nothing has changed...

 

Regarding BIOS

LegasyUSBSaport = Disable
XHCI Hand-off = Enable

PCI Expless Nateve Controll = Enable

 

The following are power saving settings, so I think it's fine to disable them.
PCIE APSM Suport
PCH PCIE APSM Suport
DMI APSM Suport
 PCH DMI APSM Suport
 

I think the kext requires USBMap.kext, so I'm writing down how to create it.
 

@brumas2025. (It won't @ convert...)

 

Download USBMap-tahoe-test.zip and create USBMap.kext for Tahoe.
 

Creating the Original USBMap.kext

 

1. Launch Terminal and drag and drop USBMap.command into the terminal to execute it.
2. Select D. Discover Ports to begin selecting the USB port to use.
3. Insert a USB device (a mouse or gamepad will do) into the USB port you want to use on the H310. The port will become enabled and change color.
4. When the screen refreshes, the next USB will become discoverable, so continue to detect all USB devices.
5. When all are complete, exit the detection screen with Q.
6. Return to the menu screen; select the Edit & Create USBMap.kext menu with P.
7. Select A. Select All, then select K. Build USBMap.kext. USBMap.kext will be created in the Results folder.
8. Exit all menus with Q to exit USBMap.command.
The created USBMap.kext is for Sequioa only, so it needs to be converted for Thaoe.

 

Creating USBMap.kext for Tahoe

 

1. Drag and drop USBMapInjectorEdit.command into Terminal to execute it.
2. When prompted, drag and drop USBMap.kext into Terminal to execute it.
3. The menu screen will change, so select S to execute it.
4. The menu screen will change, so select C to execute it.
5. Creation is complete at this point, so select Q for all commands to exit USBMapInjectorEdit.command.

 

Add the created USBMap.kext to EFI, enable it in config.plist and check USB operation.
 

  • Like 1

I think @Baio77 and @deeveedee would like to test with device-id = <923E0000> and <913E0000>.
Please modify the device-id in the attached PciRoot(0x0)/Pci(0x2,0x0) file and test it.

 

The HackinTool display seems suspicious because it doesn't reflect the settings...
From the Patch menu bar, check Apply Current Patches, and click Goto Current in the Platform ID: drop-down menu before taking a screenshot.
image.png.fe8a5938fa6ccf9cb4a1110d12becb93.png

 

image.png.1276c4f72205472bf6fb3054df7760f3.png

 

ADD:

In my index3 display, BusID and pipe show 0x6 and 8 no matter what values I set.
 

 

Asural_test_1.plist

Edited by Asural
  • Like 1
3 hours ago, Asural said:

@brumas2025. (It won't @ convert...)

 

 

Add the created USBMap.kext to EFI, enable it in config.plist and check USB operation.
 

I'll try to do this, but it doesn't apply to graphics...

31 minutes ago, brumas2025 said:

I'll try to do this, but it doesn't apply to graphics...

This is done to ensure port isolation, as the USB port is also used for data communication.

In other words, USB communication does not interfere with the screen display.
In my case, without this I can't use the keyboard and mouse and Bluetooth gives me a warning.
 

Edited by Asural
  • Like 1
4 hours ago, Asural said:

Regarding BIOS
 

I changed the settings in the BIOS, booted with the configuration you suggested, black bars, and after twitching the monitor's power supply, the image returned to normal.

Quote

2026-01-0415_07_15.thumb.png.dbba901a01d183c86fc15f03f3ed6a7e.png

 

4 minutes ago, Asural said:

Please attach the ioreg file after enabling USBMap.kext.

Also, please test this post. I think it may be necessary to set the device ID.  - I don't understand what to test in this post....

iMac 040126.ioreg

16 minutes ago, brumas2025 said:

Also, please test this post. I think it may be necessary to set the device ID.  - I don't understand what to test in this post....

iMac 040126.ioreg 4.83 MB · 1 download

I checked USBMap.kext and ioleg, and it seems that only USB 2.0 is enabled.
I'll try again later, but in its current state, I don't think it will be recognized even if connected via USB 3.0.
This is sufficient for testing the screen, so let's test the display in this state.

 

@Baio77 and @deeveedee think that explicitly setting the device-id will "calibrate iGP using WEG."

In other words, this might work.

 

The attached configuration may instruct you to change some parameters, but I think it's fine to try anything and see if it works.
 

50 minutes ago, brumas2025 said:

I changed the settings in the BIOS, booted with the configuration you suggested, black bars, and after twitching the monitor's power supply, the image returned to normal.

 

Please narrow the HackinTool window width to make the text larger.

  • Like 1
7 minutes ago, Asural said:

I checked USBMap.kext and ioleg, and it seems that only USB 2.0 is enabled.
I'll try again later, but in its current state, I don't think it will be recognized even if connected via USB 3.0.

 

Please narrow the HackinTool window width to make the text larger.

during the removal of ioreg, I did not have usb 3 devices connected.

  • Like 1
17 minutes ago, brumas2025 said:

during the removal of ioreg, I did not have usb 3 devices connected.

When you insert a USB 2.0 port, USB 3.0 should be enabled automatically as well.
Since a maximum of 15 ports are assigned to USB 2.0 only, I assume you are not using the auto-detection function.
Well, for now, let's perform a display test in this state.

 

ADD:

A genius is someone who can follow simple instructions and do something easily.

Everyone makes mistakes, so don't worry about it and just move on.
 

Edited by Asural
  • Like 1
  • Thanks 1
Posted (edited)
43 minutes ago, Asural said:

Well, for now, let's perform a display test in this state.

I tried with the configurations that hackintool created, but again the black bars that go away when I turn off the NDMI display.

Quote

2026-01-0416_20_02.png.2ad4c9b7a6f93e114314b8791cd92e6d.png2026-01-0416_20_29.png.ade605a9e0e5462914fcc8e5f9b50c7b.png

 

config006.plist iMac 040126-1.ioreg

Edited by brumas2025
23 minutes ago, brumas2025 said:

I tried with the configurations that hackintool created, but again the black bars that go away when I turn off the NDMI display.

 

config006.plist 1.71 kB · 0 downloads iMac 040126-1.ioreg 4.83 MB · 0 downloads

In HackinTool's display, the BusID and Type are displayed differently for <923E0000> and <913E0000>.
Please attach the ioreg for <923E0000> and <913E0000>, clearly indicating which is which.
I think I'll get some feedback from @Baio77 and @deeveedee later, including my settings.
 

ADD:

If you performed the test using the settings in config006.plist, please test using the contents of Asural_test_1.plist.
This is because additional modifications to boot-arg are also included.
 

Edited by Asural
  • Like 1
Posted (edited)
20 minutes ago, Asural said:

In HackinTool's display, the BusID and Type are displayed differently for <923E0000> and <913E0000>.
Please attach the ioreg for <923E0000> and <913E0000>, clearly indicating which is which.
I think I'll get some feedback from @Baio77 and @deeveedee later, including my settings.
 

loaded from <913E0000> . the display has not changed...

And the previous pictures were when it was <923E0000>

Quote

2026-01-0416_39_37.png.a700c0ea1cd319bc56cfa63906fc8059.png2026-01-0416_52_26.png.a9a02300b08d1a7b1ca8e5b57f11b925.png

 

 

iMac 040126<913E0000> .ioreg

Edited by brumas2025
21 minutes ago, brumas2025 said:

loaded from <913E0000> . the display has not changed...

And the previous pictures were when it was <923E0000>

 

 

iMac 040126<913E0000> .ioreg 4.83 MB · 0 downloads

Sorry, IORegistryExplorer has been updated to Version 3.0.2 (14). Please use Version 3.0.2 for Tahoe because the settings are stored differently.

Edited by Asural
  • Like 1
Posted (edited)
14 minutes ago, Asural said:

Sorry, IORegistryExplorer has been updated to Version 3.0.2 (14). Please use Version 3.0.2 for Tahoe because the settings are stored differently.

<913E0000>

iMac v3.0.2.ioreg.zip

Edited by brumas2025
Posted (edited)
13 минут назад Асурал сказал:

Please also attach the test results for <923E0000>.
I'm probably going to bed now.
 

<923E0000>. Goodnight!

Расценки

2026-01-0417_17_36.png.650011e6d2af7891a7da8ced87163c1b.png

 

iMac 040126<923E0000> .ioreg.zip

Edited by brumas2025

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...