Setup & Software Discussions
automate-eGPU EFI - eGPU boot manager for macOS and Windows
 

[Solved] automate-eGPU EFI - eGPU boot manager for macOS and Windows  

 of  26
  RSS

nu_ninja
(@nu_ninja)
Estimable Member
Joined: 2 years ago
 

Looks like I have NvidiaWeb YES from the script install even though I choose AMD. Removing fixes the problem.

Mid-2012 13" Macbook Pro (MacBookPro9,2) TB1 -> RX 460/560 (AKiTiO Node/Thunder2)
+ macOS 10.15+Win10 + Linux Mint 19.1


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 
Posted by: nu_ninja

@mac_editor

Yes, the script installed EFI causes a frozen login screen if I startup with egpu connected and my manual installation works normally. Hot-plug and log-out doesn't get egpu recognized but unload and reload the thunderbolt kext and egpu is recognized and the icon stays in the menubar

Thank you for testing. Could you share the config.plist files of your working vs. the script-created file?

Update: Ok I saw your post and yes I thought that wasn't making a difference. Bad me. An update to the script will remove that when choosing AMD.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


nu_ninja liked
ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@nu_ninja script has been updated. Could you try again?

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
OliverB
(@oliverb)
Noble Member
Joined: 1 year ago
 
Posted by: mac_editor

@goalque Right, @itsage is on the 2016 model. I was under the assumption that the EFI muxing (power-prefs variable) is functional on the 2018 MBPs without testing this myself. My bad.

Yes, I do have Windows. Doesn't need any mods to get eGPUs working though.

I can confirm this. No mods, no patch, no bootloader and eGPU is running perfectly in Windows 1803 on 2018 MPB 15.

But: You get the interal display running by the Microsoft Basic Display Adapter and you can't change the resolution or do anything more than display:

HWiNFO 2018MPB15
DisplayResolutFix

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 

the UHD available as a compute unit while using the accelerated external display (if you are using one). Maybe mention your config. in your signature.

Before today, I never tried getting the iGPU to work in Windows so I don't have much experience with this. While I was running on the eGPU-display, the UHD 630 was available for compute as in your case.

Thanks. I don't have an eGPU chassis.
My aim here was to have a universal dev machine I could use on the go. My desktop has both a Vega 64 and 1080ti, I can always do my work there if needed. Unfortunately, my desktop is about 17kg, so it makes it difficult to carry in a backpack 🙂
Having the Intel has a compute unit is unfortunately not possible. When using the hardware decoders, you get a GPU based frame (a texture really). You can only render such texture if you have a D3D11/DXVA HW accelerated display adapter.
But when the Intel is active, you always end up using the Microsoft Basic Graphic adapter, which is software only.

I work on video players (Firefox Web browser), ability to use HW decoder is a must for both performance and battery life.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@jya Roger that, forgive my ignorance on the matter. Sadly it seems on the 2018 MBP it may not be possible at this time.

@oliverb If using an NVIDIA eGPU, you can get the internal display to function fully accelerated as well, if the eGPU is hot-plugged at the right time and no other peripherals are present.

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
nu_ninja
(@nu_ninja)
Estimable Member
Joined: 2 years ago
 

@mac_editor

Script works perfectly now  🙂

Mid-2012 13" Macbook Pro (MacBookPro9,2) TB1 -> RX 460/560 (AKiTiO Node/Thunder2)
+ macOS 10.15+Win10 + Linux Mint 19.1


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@nu_ninja Appreciate you testing this quickly 🙂 Thanks a bunch!

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
OliverB
(@oliverb)
Noble Member
Joined: 1 year ago
 
Posted by: mac_editor

@oliverb If using an NVIDIA eGPU, you can get the internal display to function fully accelerated as well, if the eGPU is hot-plugged at the right time and no other peripherals are present.

I actually have my internal display fully accelerated, only that I cannot start DirectX Applications there, it got an error (see below). Workaround: I can start on the external display and drag it into the internal or I can start without DirectX (e.g. OpenGL).

Anyway, external display works perfectly and no need to hot-plug at the right time.

NoDirectXStartOnInterlDisplay

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
OliverB
(@oliverb)
Noble Member
Joined: 1 year ago
 

@mac_editor, perhaps you know what this strange artifact like a little window with disables scrowbars mean on my internal display (left side):

InternalDisplayLeft

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@oliverb By accelerated I meant that the GPU driving the display is not a basic adapter. Hence you see the error while launching apps. Basically the internal AMD GPU can function alongside NVIDIA eGPU.

That artifact is just a glitch. 

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@oliverb We are talking about activating the Intel iGPU for internal display, do you have the same problem?

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
OliverB
(@oliverb)
Noble Member
Joined: 1 year ago
 
Posted by: mac_editor

@oliverb By accelerated I meant that the GPU driving the display is not a basic adapter. Hence you see the error while launching apps. Basically the internal AMD GPU can function alongside NVIDIA eGPU.

That artifact is just a glitch. 

Ah, this nasty little glitch remains stubbornly.
@goalque: Sorry, If I got little Off-Topic.. This is all very faszinating.

2018 15" MBP & 2015 13" MBP connected to RTX2080Ti GTX1080Ti GTX1080 Vega56 RX580 R9-290 GTX680


ReplyQuote
(@egpu_freak)
Active Member
Joined: 1 year ago
 

my external display is able to detect my egpu, how can I use the egpu to accelerate my internal display and choose the app to be accelerated?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque

Then hold down the Option key and select "EFI Boot".

Type "devtree -b" to see which GPU is driving the internal display.

Our last chance is to access the gmux through IO address space:

mm -io 7D0 10 -n

mm -io 7C2 -n

What's the output?

Ok, this is what I've tried.

1- Shell_Full.efi on separate USB

devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

1- Shell_Full.efi on separate USB, after running

sudo nvram fa4ce28d-b62f-4c99-9cc3-6815686e30f9:gpu-power-prefs=%01%00%00%00

Identical to step 1.
devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

3- Install refind, run apple_set_os.efi then Full-Shell.efi
Identical to step 1.
devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

4- Install refind, run nvram command, run apple_set_os.efi then Full-Shell.efi
Identical to step 1.
devtree -b shows both the AMD and the Skylake EG2 graphic device. I can't tell which one is active from that screen, this is just the PCI tree
mm -io 7D0 10 -n -> nothing output
nm -io 7C2 -n -> 0xFF

So the gmux doesn't seem to be impacted by any of those commands.

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

Ok, thanks. I have never seen value 0xFF before (you have a typo there, should be mm not nm). I suppose the AMD appears first in the device tree and has ”Primary Console Output Device” item?

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque

Ok, thanks. I have never seen value 0xFF before (you have a typo there, should be mm not nm). I suppose the AMD appears first in the device tree and has ”Primary Console Output Device” item?

That is correct.
Primary Console Output Device is attached to AMD Radeon Baffin Video Adapter.

Could it be that the gmux device is now attached at a different address on those models?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@jya yes, it is very possible that the gmux device is located at the different offset. Current Linux drivers define it at 0x700.

To find out the correct IO offset, you need to look at ACPI tables and search for the minimum range value for this device. In Linux, you should be able to read registered port regions from the /proc/ioports file.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
(@yuanming_wang)
New Member
Joined: 1 year ago
 

Same problem here with MacBook Pro 2017 NTB using Mojave 10.14.1,
Have you figure this out ?

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 
Posted by: Yuanming Wang

Same problem here with MacBook Pro 2017 NTB using Mojave 10.14.1,
Have you figure this out ?

What problem exactly?

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 
Posted by: goalque
Posted by: NavilleZhang

Hi:
I've tried using this instead of the traditional step-by-step guide.
I'm able to execute the automate-eGPU.efi in refined when eGPU is not plugged in, however it just stucks at ``Using Configuration ''``.

automate-eGPU.efi cannot be used with rEFInd or alone, it's designed to be used with the boot screen efi (bootx64.efi).

I used a new USB disk and tried the install script bash <(curl -s  https://egpu.io/wp-content/uploads/2018/11/automate-eGPU-EFI-install.txt)
 However, if I boot up with the eGPU plugged in, I just have a blackscreen, if I plug it in anypoint after the system has started, for example the EFI menu, the whole system just freezes. Attempting to choose "Load Windows" or "Load macOS" without eGPU also results in a frozen system

EDIT: I've already changed muxsettings

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

Sorry, I have not looked into what @mac_editor's script does. According to log something went wrong since Clover couldn't find any volumes with Block IO protocol. I can only confirm that MS-DOS (FAT) + MBR works.

2016 15" MBP should not be the problem:

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/17/#post-43433

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
Inotna
(@inotna)
Eminent Member
Joined: 3 years ago
 

I have been around here for while and I got the Akitio Node 1.5 year ago I think hadn't really played around it much since I got it. First I got the 13" MBP MBP. I purchased the Nvidia 1060 6GB, wasn't really impressed with the performance for gaming. Last year I upgraded to the mid 2017 15" inch model.

Anyway. today I received my RTX 2070. I have Windows 10 installed on a Seagate 256GB SSD drive. Plugin the card Akitio Node, boot windows up. Connect the Akitio when windows is fully booted up. let it find drivers and install the latest from Nvidia. Reboot unplug the akin node. Hold option to select the windows drive (windows to go) Count to 2 connect the Akitio and I works flawlessly internal screen/external when running BF1. Anyway do I need this automate boot manager? Is there anyway the Akitio node can be already plugged when I do cold boot as I remember for now I get a little flashing windows logo

hope you can help I have been reading up the last week but still confused little out of loop, so much has happened! Keep up the good work

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
(@reinhard1004)
Eminent Member
Joined: 2 years ago
 
Posted by: goalque
Posted by: nu_ninja

@goalque
So my egpu is now working on 10.14.1 with the EFI. I re-upgraded to see if mac_editor's method would do anything and before even trying that, it just worked. The only thing I can think of that would make a difference is, the first time I upgraded, I had booted with the EFI and left the egpu plugged in. Whereas this time I upgraded without any patches applied and the egpu disconnected.

If you are going to do any macOS/software updates, please always boot normally (no patches, eGPU disconnected).

And it is worth to mention again:

https://egpu.io/forums/mac-setup/automate-egpu-efi-egpu-boot-manager-for-macos-and-windows/paged/3/#post-45725

1) If you have to force power-off or a kernel panic occurs, please do one normal boot into macOS and login, shut down (without USB stick). Otherwise, the "EFI Boot" does not work on the next startup.

Yess - avoiding a force power-off and kernel panic for one clean boot and shutdown fixed my problem. After that booting via EFI 1.0.5 works great as it used to with 1.0.4. Also using a less crappy USB stick now (could also have fixed it :)).
@goalque: Thanks for the tool & support!
@mac_editor: Thanks for the neat installer script. =)
Hope the Mojave drivers will be out any time soon.

Late 2016 15" MBP w/ Radeon Pro 460, 2m CalDigit TB3 cable, Mantiz Venus eGPU case, NVidia GTX 1080ti.


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 
Posted by: goalque

Sorry, I have not looked into what @mac_editor's script does. According to log something went wrong since Clover couldn't find any volumes with Block IO protocol. I can only confirm that MS-DOS (FAT) + MBR works.

2016 15" MBP should not be the problem:

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/17/#post-43433

I formatted and reinstalled both the USB disk as well as the whole internal SSD and restarted (yet again) from scratch and the issue still persists. This time I copied the folder over without using the script. The log seems to be a little bit different though.  Below is my current disk list info as well as the log

λ : >>> diskutil list

/dev/disk0 (internal):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      GUID_partition_scheme                         500.3 GB   disk0

   1:                        EFI EFI                     314.6 MB   disk0s1

   2:                 Apple_APFS Container disk1         411.0 GB   disk0s2

   3:       Microsoft Basic Data BOOTCAMP                89.0 GB    disk0s3

/dev/disk1 (synthesized):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:      APFS Container Scheme -                      +411.0 GB   disk1

                                 Physical Store disk0s2

   1:                APFS Volume Reimu                   312.8 GB   disk1s1

   2:                APFS Volume Preboot                 45.3 MB    disk1s2

   3:                APFS Volume Recovery                512.8 MB   disk1s3

   4:                APFS Volume VM                      1.1 GB     disk1s4

/dev/disk2 (external, physical):

   #:                       TYPE NAME                    SIZE       IDENTIFIER

   0:     FDisk_partition_scheme                        *30.8 GB    disk2

   1:                 DOS_FAT_32 EGPUBOOT                30.8 GB    disk2s1

0:100 0:100 MemLog inited, TSC freq: 2906728220
0:100 0:000 CPU was calibrated with RTC
0:100 0:000 start
0:100 0:000
0:100 0:000 Now is 5.11.2018, 21:35:8 (GMT)
0:100 0:000 Starting Clover revision: 4513 on Apple EFI
0:100 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/goalque/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 9.4.1]
0:100 0:000 SelfDevicePath=PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x3,0x0)\HD(1,MBR,0x00000000,0x800,0x3947800) @79487B18
0:100 0:000 SelfDirPath = \EFI\BOOT
0:188 0:087 Running on: '' with board ''
0:188 0:000 === [ GetCPUProperties ] ==================================
0:188 0:000 CPU Vendor = 756E6547 Model=506E3
0:188 0:000 The CPU supported SSE4.1
0:188 0:000 BrandString = Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
0:188 0:000 The CPU supported turbo
0:188 0:000 MSR 0x35 40008
0:188 0:000 TSC/CCC Information Leaf:
0:188 0:000 numerator : 242
0:188 0:000 denominator : 2
0:188 0:000 Calibrated ARTFrequency: 0
0:188 0:000 MSR 0xE2 before patch 60000008
0:188 0:000 MSR 0xCE 0008083B_F1011D00
0:188 0:000 corrected FLEX_RATIO = 1C0000
0:188 0:000 MSR 0x1B0 00000000
0:188 0:000 FSBFrequency = 0 MHz, DMI FSBFrequency = 0 MHz, Corrected FSBFrequency = 0 MHz
0:188 0:000 MaxDiv/MinDiv: 29.0/8
0:188 0:000 Turbo: 34/35/36/38
0:188 0:000 Features: 0xBFEBFBFF
0:188 0:000 Threads: 8
0:188 0:000 Cores: 4
0:188 0:000 FSB: 0 MHz
0:188 0:000 CPU: 0 MHz
0:188 0:000 TSC: 0 MHz
0:188 0:000 PIS: 0 MHz
0:188 0:000 ExternalClock: 0 MHz
0:188 0:000 === [ GetDevices ] ========================================
0:188 0:000 PCI (00|00:00.00) : 8086 1910 class=060000
0:188 0:000 PCI (00|00:01.00) : 8086 1901 class=060400
0:188 0:000 PCI (00|01:00.00) : 1002 67EF class=030000
0:188 0:000 - GFX: Model=AMD Radeon Pro 555 (ATI/AMD)
0:188 0:000 PCI (00|01:00.01) : 1002 AAE0 class=040300
0:188 0:000 - HDMI Audio:
0:188 0:000 PCI (00|00:02.00) : 8086 191B class=030000
0:188 0:000 - GFX: Model=Intel HD Graphics 530 (Intel)
0:188 0:000 PCI (00|00:14.00) : 8086 A12F class=0C0330
0:188 0:000 PCI (00|00:15.00) : 8086 A160 class=118000
0:188 0:000 PCI (00|00:16.00) : 8086 A13A class=078000
0:188 0:000 PCI (00|00:19.00) : 8086 A166 class=118000
0:188 0:000 PCI (00|00:1B.00) : 8086 A167 class=060400
0:188 0:000 PCI (00|02:00.00) : 144D A804 class=010802
0:188 0:000 PCI (00|00:1C.00) : 8086 A110 class=060400
0:188 0:000 PCI (00|03:00.00) : 14E4 43BA class=028000
0:188 0:000 - WIFI: Vendor=Broadcom
0:188 0:000 PCI (00|00:1E.00) : 8086 A127 class=118000
0:188 0:000 PCI (00|00:1E.01) : 8086 A128 class=118000
0:188 0:000 PCI (00|00:1E.02) : 8086 A129 class=118000
0:188 0:000 PCI (00|00:1E.03) : 8086 A12A class=118000
0:188 0:000 PCI (00|00:1F.00) : 8086 A151 class=060100
0:188 0:000 PCI (00|00:1F.02) : 8086 A121 class=058000
0:188 0:000 PCI (00|00:1F.03) : 8086 A170 class=040300
0:188 0:000 PCI (00|00:1F.04) : 8086 A123 class=0C0500
0:188 0:000 PCI (00|00:01.01) : 8086 1905 class=060400
0:188 0:000 PCI (00|04:00.00) : 8086 1578 class=060400
0:188 0:000 PCI (00|05:00.00) : 8086 15D3 class=060400
0:188 0:000 PCI (00|06:00.00) : 8086 15D2 class=088000
0:188 0:000 PCI (00|05:01.00) : 8086 15D3 class=060400
0:189 0:000 PCI (00|05:02.00) : 8086 15D3 class=060400
0:189 0:000 PCI (00|07:00.00) : 8086 15D4 class=0C0330
0:189 0:000 PCI (00|05:04.00) : 8086 15D3 class=060400
0:189 0:000 PCI (00|00:01.02) : 8086 1909 class=060400
0:189 0:000 PCI (00|7A:00.00) : 8086 1578 class=060400
0:189 0:000 PCI (00|7B:00.00) : 8086 15D3 class=060400
0:189 0:000 PCI (00|7C:00.00) : 8086 15D2 class=088000
0:189 0:000 PCI (00|7B:01.00) : 8086 15D3 class=060400
0:189 0:000 PCI (00|7B:02.00) : 8086 15D3 class=060400
0:189 0:000 PCI (00|7D:00.00) : 8086 15D4 class=0C0330
0:189 0:000 PCI (00|7B:04.00) : 8086 15D3 class=060400
0:189 0:000 === [ GetDefaultSettings ] ================================
0:189 0:000 Clover load options size = 0 bytes
0:195 0:006 EFI\CLOVER\config.plist loaded: Success
0:195 0:000 === [ GetListOfThemes ] ===================================
0:195 0:000 === [ Found config plists ] ===============================
0:195 0:000 - config.plist
0:195 0:000 === [ GetEarlyUserSettings ] ==============================
0:195 0:000 timeout set to 0
0:195 0:000 Custom boot CUSTOM_BOOT_DISABLED (0x0)
0:383 0:187 KextsToPatch: 3 requested
0:461 0:078 - [00]: IOGraphicsFamily (IOGraphicsFamily Patch (c) egpu.io [goalque])Data: 71DE8218, Len: 14 = Data: 71DE8198, Len: 14 = :: BinPatch :: data len: 14
0:940 0:478 - [01]: AppleGPUWrangler (AppleGPUWrangler Discrete Patch (c) egpu.io [goalque])Data: 71DE8198, Len: 14 = Data: 71DE8218, Len: 14 = :: BinPatch :: data len: 14
1:440 0:500 === [ LoadDrivers ] =======================================
5:640 4:199 Loading apple_set_os.efi status=Success
6:044 0:404 === [ InitScreen ] ========================================
10:277 4:232 reinit: self device path=PciRoot(0x0)\Pci(0x1,0x1)\Pci(0x0,0x0)\Pci(0x2,0x0)\Pci(0x0,0x0)\USB(0x3,0x0)\HD(1,MBR,0x00000000,0x800,0x3947800)
10:370 0:092 === [ GetDefaultSettings ] ================================
13:313 2:943 === [ GetAcpiTablesList ] =================================
16:390 3:076 Get Acpi Tables List from RSDT:
16:552 0:162 - [00]: FACP Apple00 len=244
16:635 0:082 - [01]: UEFI EDK2 len=66
16:712 0:077 - [02]: ECDT Apple00 len=83
16:789 0:076 - [03]: HPET Apple00 len=56
16:874 0:084 - [04]: APIC Apple00 len=188
16:993 0:119 - [05]: MCFG Apple00 len=60
17:088 0:095 - [06]: SBST Apple00 len=48
17:235 0:146 - [07]: SSDT SmcDppt len=36
17:322 0:087 - [08]: SSDT PEG0GFX0 len=2045
17:409 0:087 - [09]: SSDT PEG0SSD0 len=36
17:490 0:080 - [10]: SSDT SsdtS3 len=49
17:576 0:085 - [11]: SSDT SataAhci len=221
17:663 0:087 - [12]: SSDT Sdxc len=184
17:749 0:085 - [13]: SSDT TbtPEG12 len=39278
17:825 0:075 - [14]: SSDT Xhci len=3122
17:900 0:075 - [15]: SSDT Cpu0Ist len=1554
17:977 0:076 - [16]: SSDT ApIst len=1450
18:049 0:071 - [17]: SSDT Cpu0Cst len=661
18:125 0:075 - [18]: SSDT ApCst len=281
18:210 0:085 - [19]: SSDT CpuSsdt len=3823
18:288 0:077 - [20]: DMAR SKL len=352
18:368 0:080 - [21]: VFCT Apple00 len=59524

EDIT: Just to confirm:
If I only need Bootcamp Windows Internal Screen with eGPU, I don't need to run those sudo pm*** commands?
My issue is not related to Windows 10 build number?
NVIDIA card version doesn't affect the issue?

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: goalque

@jya yes, it is very possible that the gmux device is located at the different offset. Current Linux drivers define it at 0x700.

To find out the correct IO offset, you need to look at ACPI tables and search for the minimum range value for this device. In Linux, you should be able to read registered port regions from the /proc/ioports file.

I haven't been able to natively boot linux on this laptop yet, there are no drivers for the T2 SSD controller.
And none of the linux installer I've played with manage to get the graphic card going, so can't even play with a live session yet.

If I was to dump the ACPI tables for this laptop, would that help? I have them somewhere...

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


goalque liked
ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 
Posted by: goalque

Sorry, I have not looked into what @mac_editor's script does. According to log something went wrong since Clover couldn't find any volumes with Block IO protocol. I can only confirm that MS-DOS (FAT) + MBR works.

2016 15" MBP should not be the problem:

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/17/#post-43433

I read the log again, judging by the timestamp it seems like it contains log for two different attempts. The first one stopped at scanning volumes. Should I wait longer despite the app seems to be stuck? And is the black screen when cold boot with eGPU plugged in supposed behaviour?

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 
Posted by: goalque

Sorry, I have not looked into what @mac_editor's script does. According to log something went wrong since Clover couldn't find any volumes with Block IO protocol. I can only confirm that MS-DOS (FAT) + MBR works.

2016 15" MBP should not be the problem:

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/17/#post-43433

Progress! I waited quite a while and I'm finally able to see the Windows booting up white circle! After a while I can see my touchbar lighting up so I guess windows is properly booted. However the internal screen is just black, the backlit is on but there is absolutely nothing displayed? Is there anything I'm supposed do on Windows? I'm using the very first version of Windows 10 dated back to 2015.

EDIT: To be clear, the only thing I can see past the EFI screen is just the Windows Booting white spinning dot circle, nothing else. TouchBar is fully interactive, just no display. Plug-in eGPU at this stage doesn't help

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

If the debug flag is set to true and the USB stick is slow, the boot process may take a few minutes.

The most important is to download/install Boot Camp drivers.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 

Did that. Windows works fine when booting normally. Strange, software issue I guess?

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 
Posted by: goalque

If the debug flag is set to true and the USB stick is slow, the boot process may take a few minutes.

The most important is to download/install Boot Camp drivers.

Am I supposed to delete the Bootcamp dGPU drivers first or can I just leave them as is? I cant think of other possibilities atm

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
jya
 jya
(@jya)
Trusted Member
Joined: 2 years ago
 
Posted by: NavilleZhang
Posted by: goalque

Sorry, I have not looked into what @mac_editor's script does. According to log something went wrong since Clover couldn't find any volumes with Block IO protocol. I can only confirm that MS-DOS (FAT) + MBR works.

2016 15" MBP should not be the problem:

https://egpu.io/forums/mac-setup/two-new-egpu-solutions-on-macos-10-13-4-pure-efi-and-hybrid/paged/17/#post-43433

Progress! I waited quite a while and I'm finally able to see the Windows booting up white circle! After a while I can see my touchbar lighting up so I guess windows is properly booted. However the internal screen is just black, the backlit is on but there is absolutely nothing displayed? Is there anything I'm supposed do on Windows? I'm using the very first version of Windows 10 dated back to 2015.

EDIT: To be clear, the only thing I can see past the EFI screen is just the Windows Booting white spinning dot circle, nothing else. TouchBar is fully interactive, just no display. Plug-in eGPU at this stage doesn't help

This problem is what we've been attempting to solve for several pages now 🙁

Pending: Add my system information and expected eGPU configuration to my signature to give context to my posts


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 

And when exactly should I plug in the eGPU? The original post says do so after logged in (Which I assume only applies when using eGPU from macOS), other users' screenshots says the EFI is able to detect the eGPU so those seems like cold boot with eGPU/plug in at EFI selection

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
mac_editor
(@mac_editor)
Famed Member Moderator
Joined: 3 years ago
 

@jya I believe @navillezhang is on a 2016 MBP, not 2018. The 2016 has worked fine before with apple_set_os.efi@navillezhang could you add your config. to your signature?

purge-wrangler.shpurge-nvda.shset-eGPU.shautomate-eGPU EFI Installer
2018 MacBook Pro 15" RP560X + RX 5700 XT (Mantiz Venus)


ReplyQuote
NavilleZhang
(@navillezhang)
Trusted Member
Joined: 1 year ago
 
Posted by: mac_editor

@jya I believe @navillezhang is on a 2016 MBP, not 2018. The 2016 has worked fine before with apple_set_os.efi@navillezhang could you add your config. to your signature?

If you mean the forum signature, done and done  🙂

BTW just tried coldboot/ plug-in at EFI again and it still freezes the machine

RTX 2080Ti
2016 15' Macbook Pro with RP460
Akitio Node Pro


ReplyQuote
goalque
(@goalque)
Noble Member Admin
Joined: 3 years ago
 

@navillezhang The first thing is to get iGPU visible in device manager. HD Graphics 530? MuxSetting=1 + apple_set_os.efi should do the trick. Older versions of Win10 may not have iGPU drivers built in - if Apple does not provide them, you have to download from Intel.

Then you probably need DSDT.aml as @itsage advised.

automate-eGPU EFIapple_set_os.efi
--
2018 13" MacBook Pro + Radeon [email protected] + Win10 1809


ReplyQuote
 of  26