brightbulb

DSDT override is possible under Windows 8.1 via the registry if driver signing enforcement is turned off. You may find Windows will auto-allocated the eGPU into the extra space created. If not, then use of Setup 1.30 will require a change from UEFI to MBR. If your system is delivered with a UEFI Win8.x install then can use a non-destructive GPT to MBR conversion process as explained at How to Convert GPT to MBR or Convert MBR to GPT without Losing Data? .

Yes, I answer any specific questions about Setup 1.30.

Is this a recent change? I thought the only way to do a DSDT override was to apply it from within setup 1.30?

I would like to give this another go because I can't run my eGPU and iGPU simultaneously at this stage which means I can't hot-plug.

Has the method to do a DSDT override changed/improved at all since those guides were posted?

Thanks

Windows works just fine if I don't enter Setup 1.x. But when I chainload (even without doing anything), I just gives me that error...

You may be chainloading the wrong partition (I got that error when I did that). Although since you're coming from GRUB that seems unlikely.

Or GRUB is configured incorrectly.

Or you are making your Windows partition inaccessible with your compaction. What compaction do you run?

In setup1.x, after compaction, go into grub4dos and type 'ls hd(' and press tab. Pick one of the options and repeat e.g. 'ls hd(0,' followed by tab. That will allow you to see what is available.

You can then even boot into Windows from grub4dos by finding the small NTFS partition windows uses to boot ( hd(1,0) for me) and running:

chainloader (hd1,0)/bootmgr && boot

Let me know how you get on.

I actually got it to boot directly to my GRUB2 boot menu, but the problem is, after that when I try to boot into Windows 7 (From Grub), I get this. https://dl.dropboxusercontent.com/u/19991857/eGPU/2014-06-23%2000.38.58.jpg.

Would be very interested in hearing how to fix this..

Does windows work if you don't go into setup1.x? Does it work if you go into setup1.x and chainload (without compaction)?

Have you tried other graphics cards?

I found myself unable to chainload after installing Ubuntu in a separate partition. I have completed setup-disk-image-linux.bat and added the entry to GRUB2 as instructed, however none of the chainloading options are able to get me back to GRUB or either OS.

Using the first MBR entry of the chainloader brings up a promising-looking dark-purple tinted background, which may indicates that this partly works, however it quickly disappears as my machine resets.

Is there anything I can try to remedy this?

Did you solve your problem. I have same. .....please tell what I do...

What GPU are you using?

I ended up using a different GPU, although you could try the hijacking trick with setup 1.x (36-bit compaction on igpu, force egpu to 32-bit). Hopefully this will cause dwm to load into the egpu at boot, but I haven't tried.

All working

This is a little messy at the moment, but at least shows that a cheap 12V power supply combined with a 5V regulator module works fine (as long as you trim them well).

The hijack trick works. Internal display still comes on but only in non-functional 4-bit grayscale. Hope that doesn't damage anything, it's definitely a bit unsettling.

Interesting result when using this method to make space for the eGPU in Windows 8:

After a few days/reboots Windows seemed to accept the 36-bit allocation of the iGPU, so it now runs flawlessly without needing a DSDT override.

You'd have to plug away at the DSDT override till you get it going. Not much advice that I can offer there.

As you are running Win8, the way you'd get the eGPU to use the iGPU PCI config space is to perform a iGPU+eGPU 36-bit compaction, but force the eGPU to 32-bit. That way it will hijaak the iGPU PCI config (or any other available in 32-bit space). Win8 should honor the Setup 1.x allocation and flag the iGPU with an error 12. Having a error12 on the primary iGPU device isn't as catastrophic in Win7 as it is under Win7 as described in http://forum.techinferno.com/diy-e-gpu-projects/6392-win8-x-more-flexible-egpu-platform-than-win7.html . I believe that even with a non-functional iGPU, the NVidia x1 pci-e compression will still engage. Only thing you'd miss out on would be of course the eGPU-accelerated internal LCD mode.

The hijack trick works. Internal display still comes on but only in non-functional 4-bit grayscale. Hope that doesn't damage anything, it's definitely a bit unsettling.

You'd have to plug away at the DSDT override till you get it going. Not much advice that I can offer there.

As you are running Win8, the way you'd get the eGPU to use the iGPU PCI config space is to perform a iGPU+eGPU 36-bit compaction, but force the eGPU to 32-bit. That way it will hijaak the iGPU PCI config (or any other available in 32-bit space). Win8 should honor the Setup 1.x allocation and flag the iGPU with an error 12. Having a error12 on the primary iGPU device isn't as catastrophic in Win7 as it is under Win7 as described in http://forum.techinferno.com/diy-e-gpu-projects/6392-win8-x-more-flexible-egpu-platform-than-win7.html . I believe that even with a non-functional iGPU, the NVidia x1 pci-e compression will still engage. Only thing you'd miss out on would be of course the eGPU-accelerated internal LCD mode.

Alright, I will keep playing with the DSDT, maybe the windows logs or dumps will give me more info on what's going wrong. I am using win8, so the second option sounds like it would suffice for the time being. With 3 HD screens running off the GTX660 I wouldn't exactly miss the handful of pixels of the internal display.

Is it possible to use conditional statements in the startup.bat?

Something like

if eGPU (

hijack

)

chainload

Thanks for the tips. Indeed the built quality of the x230 has been a let-down, but it's been good on other fronts. I don't think I'll be able to get a refund at this point, but I'll definitely bear your suggestion in mind when an opportunity comes up.

As for the issue at hand: I have tried to override the memory as suggested in your Win8 DSDT override guide. I was able to make all the changes and eradicate any compilation errors with only some warnings remaining, but always got a blue screen when loaded. I'm fairly certain the size of the recompiled .aml is smaller than the .dat, it's quite close though. I removed all references to other OS's but not sure what else can be removed. Could there be other reasons for the BSOD?

Disabling the iGPU is definitely also an option. How would this be done?

I'm having a problem I haven't yet seen on here: My x230 won't POST with a GTX660 (2gb) as eGPU, but works fine with a GTS250 (1gb).

Due to what I assume is the dynamic TOLUD, neither card fits on the bus if it's being hot plugged.

I just found a solution to this problem, which is to boot with the GTS250, swap cards at boot menu, followed by compaction and chainload.

While this works flawlessly once in Windows, it's very tedious, not to mention the wear on the PCIe1x slot.

Does anyone have any idea what could be preventing the computer from POSTing with the GTX660?

I have tested multiple PSU's and also stress tested the GPU in a different system.

Anyone had any success using an x230 with windows 8? At the moment mine crashes dwm.exe (desktop window manager), which means you can't log in or use anything metro.

I'm using a gts250 until my gtx660 shows up. Could that be the issue maybe?

EDIT: This seems relevant to running egpu on windows 8: http://superuser.com/a/558907... TLDR; DWM must run on primary video card

I still don't fully understand this what makes the PE4H 3.2 worth more than the PE4L 2.1b.

On the PE4H 2.4, there were 4 HDMI sockets to allow PCIE up to x4.

On version 3.2, the cable is soldered onto the board, no additional PCIE connections can be made. Doesn't that limit it to a x1 connection?

What's the point of having a longer socket and all those extra components on the PE4H PCB?

I have an x230 with up to date BIOS. I get an error code 12 when I have my eGPU plugged in.

Root bridge override gives a blue screen at boot.

Is there a specific BIOS version I should be using?