daver160

What? A BIOS doesn't work right? I've never heard of such a thing! Wait I got that wrong, it's the other way around...

Well nando can help you best with getting the reallocation to work. Like I said before, to me it looks like it thinks your TOLUD is 3.5GB instead of 3GB.

Strange, because Device Manager says otherwise (or so I am led to believe):

If all else fails (which it shouldn't) you could always just pull the 540m. That'll make sure it doesn't take up resources

heh now there's some good advice. I guess I'll also have to invest in a pretty good hammer crowbar. Also, a new laptop

Poor BIOS writing rant continued:

It's possible to write a single BIOS that can run almost any 6 and 7 series platform (virtually identical chipsets, same voltage regulators, KBC's accept the same commands), but BIOS writers throw in tons of unnecessary proprietary code that does unnecessary hardware checks with a complete lack of failsafes. Ex. This one laptop I've been messing with will refuse to POST with 1866MHz memory. Could the BIOS run default clocks and timings if it doesn't like the SPD? Of course. Does it? Nope. Black screen. And that's the least of the BIOS's issues... with the biggest being that although overclocking and voltage increases are locked out for hardware "safety", there is a bug which allows you to disable the CPU fan, thermal throttling, and thermal shutdown... Also read yesterday how 680m 6 series clevo users system's will refuse to POST with certain video BIOS's. The system has optimus with an IGP, so there is no reason for the system to not boot with the 680m malfunctioning. Does it disable the 680m and boot? Nope, 680m must be pulled. I can go on and on and on and on... If I could learn a bit more machine code and get the memory libraries required to enable CPU features, maybe I'll write my own BIOS from scratch.

Yipes, point taken. I always thought that BIOS software was written with at least a minimum amount of confidence, since it deals directly at the hardware level, controlling such things as memory speeds, thermals, sensors, etc.

You can manually lower your TOLUD? That isn't needed, but it will make things simpler. Lower it by 256MB or more. That will allow the eGPU to be allocated on boot, then all you need the setup program for is to disable the 540m. Otherwise you'll need to run the reallocation script in addition.

Maybe nando changed things, but you used to need to build devcon.txt from windows using the command window. Not having a proper devcon file usually made compaction freeze the system.

Update: Yes you still need to run a command to build devcon.txt:

http://forum.techinferno.com/diy-e-gpu-projects/2123-diy-egpu-setup-1-x.html

But your system isn't crashing, so it looks like you don't need to make a new one. If you really can select your TOLUD in BIOS, lower it and you can forget about compaction.

So my BIOS made me lie. Turns out that "Max TOLUD" selector in my BIOS doesn't do anything.

I tried setting it to 2.5 GB, 2.75 GB, 3.5 GB, and Dynamic. None of these settings change my PCI Bus value in my Win7 Device Manager: it read BFA00000 regardless of what I set in the BIOS.

So boot in Setup (menu-based), ensure the eGPU is detected (F5), disabled the dGPU with Video cards->dGPU[off] , perform a 32-bit PCI compaction on the iGPU+eGPU and proceed to then manually add the I/O address per T10. Even after successful 32-bit compaction I still get a error 12 in Windows if you still get an error 12.

I have a problem with 32-bit compaction: it always tells me that

"No Solution found. Set another method then try another PCI compaction"

This happens when I try 32-bit against iGPU, eGPU, and iGPU+eGPU, as well as 32-bitA against the same 3 GPU options.

Is there any specific reason why I would be getting that "No solution found" error message when running 32-bit and 32-bitA compaction methods?

Thanks both!

I might be reading it wrong but it looks like the pci.bat thinks your TOLUD is 3.5GB (0xe000000c), not 3GB.(0xc0000000). I'm thinking that the TOLUD really isn't 3.5GB, since if it was it would be very difficult for your system to run the iGPU and dGPU with other devices as well (only 32MB would be left). I'm not sure if pci.bat gets the TOLUD from devcon.txt or if it looks it up. I suggest rebuilding the devcon.txt file, then rebuilding setpci.bat.

DSDT override is unnecessary though since unless you're using thunderbolt, you need to disable the dGPU anyway for optimus compression to work. This will make room for the 650. You'll then need to allocate the 650 since the BIOS failed to on boot.

You did try cold booting with the eGPU on right? BIOS's that aren't poorly written (which is the minority) will adjust the TOLUD to allocate everything it sees on startup. I don't know what your laptop is, so I don't know if yours does this or not.

Hi Khenglish,

Thanks f or the help. I will try this out tonight when I'm home from work.

My question now is: how do I rebuild my devcon.txt file? Do I literally just delete its contents and then Setup 1.x will rebuild it the next time I run compaction? Or do I need to do something else?

My notebook is the Dell XPS 15 L502x, practically same one as wicked20 who has successfully pulled off eGPU with Opt1.1 (he has results in the table on first page). I've added my laptop and eGPU specs to my signature, which will hopefully be useful in the future.

It's good to know that I wasn't crazy in thinking that I did not have to perform a DSDT override. As I mentioned before, here is my startup.bat

call speedup lbacache
call iport g1 1 
call iport dGPU off
call vidwait 60 10de:11c6
call vidinit -d 10de:11c6 
call pci 
call grub4dos win7

As I am using the PE4H+PM3N (soon to hopefully be PE4H+PM060a or something similar for Gen2 speeds, working out those details with HIT), I am indeed disabling my dGPU prior to running compaction.

I am only cold booting with the eGPU powered on. In my case, I power on the eGPU (via SWEX switch) a couple seconds before I power on my notebook. I've not had any problems with Windows not detecting my eGPU, just the Error 12. My BIOS allows me to change my TOLUD value as well, for example, I can lower it to 2.5GB if necessary. I don't know if that would help things or not.

Thanks again

No one has any advice on getting rid of an Error code 12?

My understanding of the Error 12 is that it is initially related to your TOLUD value; mine is 3GB so I thought I wouldn't need to perform a DSDT override. As well, running a Setup 1.x 36-bit compaction against my eGPU (and selecting iGPU for 32-bit) did not resolve my Error 12.

I tried to follow the DIY eGPU Troubleshooting steps, particularly Error 12 #2, but I was having trouble figuring out exactly how and what values to use. My pci.bat looks like this

REM r:/core/compact.exe pciend 310000000 useonly 8086:0126 import devcon.txt makebatch R:\config\pci.bat
REM created Wed Jan 16 23:28:51 2013
echo Performing PCI write (compact@Wed Jan 16 23:28:51 2013)

@echo -s 1:0.0 COMMAND=0 BASE_ADDRESS_1=c BASE_ADDRESS_2=3 COMMAND=0 BASE_ADDRESS_3=fe00000c BASE_ADDRESS_4=2 > setpci.arg
@echo -s 0:2.0 COMMAND=5 BASE_ADDRESS_2=e000000c BASE_ADDRESS_3=2 >> setpci.arg
@echo -s 1:0.0 COMMAND=0 BASE_ADDRESS_0=fd000000 >> setpci.arg
@echo -s 1:0.1 COMMAND=0 BASE_ADDRESS_0=febfc000 >> setpci.arg
@echo -s 0:2.0 COMMAND=5 BASE_ADDRESS_0=fcc00004 BASE_ADDRESS_1=0 >> setpci.arg
@echo -s 0:1c.0 MEMORY_BASE=fd00 MEMORY_LIMIT=feb0 PREF_MEMORY_BASE=fe01 PREF_BASE_UPPER32=2 PREF_MEMORY_LIMIT=ff1 PREF_LIMIT_UPPER32=3 >> setpci.arg
@echo -s 0:1c.1 MEMORY_BASE=f1b0 MEMORY_LIMIT=f1b0 PREF_MEMORY_BASE=fff1 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=1 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1c.3 MEMORY_BASE=f1a0 MEMORY_LIMIT=f1a0 PREF_MEMORY_BASE=fff1 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=1 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1c.4 MEMORY_BASE=f190 MEMORY_LIMIT=f190 PREF_MEMORY_BASE=fff1 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=1 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1c.5 MEMORY_BASE=fff0 MEMORY_LIMIT=0 PREF_MEMORY_BASE=f181 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=f181 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1.0 MEMORY_BASE=f190 MEMORY_LIMIT=feb0 PREF_MEMORY_BASE=f181 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=ff1 PREF_LIMIT_UPPER32=3 >> setpci.arg
@echo -s 1:0.0 COMMAND=0 COMMAND=0 >> setpci.arg
@echo -s 0:2.0 COMMAND=7 >> setpci.arg
@echo -s 1:0.0 COMMAND=0 >> setpci.arg
@echo -s 1:0.1 COMMAND=0 >> setpci.arg
@echo -s 0:2.0 COMMAND=7 >> setpci.arg

setpci @setpci.arg
set pci_written=yes

My last two echo lines contain nothing like what nando's troubleshooting demo provides, hence why I'm stuck.

Regarding the different ways of compaction, I've tried them all:

• 32-bit, against iGPU, eGPU, iGPU+eGPU (all 3 will fail, giving me the "set another method and try again" message).
  
• 32-bitA, against iGPU, eGPU, iGPU + eGPU (all 3 will also fail, same error as above)
  
• 36-bit, against iGPU (then 32-bit against None, iGPU, eGPU, iGPU+eGPU), eGPU (tried same 32-bit settings), and finally iGPU+eGPU (tried same 32-bit settings).
  

I decided to stick with the 36-bit iGPU+eGPU and the 32-bit "None". None of the 32-bit methods worked, but all 36-bit selections result in Device Manager giving me the Error 12. Am I making the wrong choices for compaction?

My specs are:

i7-2760QM

8GB RAM

dGPU: Nvidia GT 540M

eGPU: GTX 650 Ti

PSU: 625W, 12V1 and 12V2 @24A, 5V @22A

I've confirmed that the GPU is not faulty, but using it in another desktop system.

I'd really appreciate if someone could please help me out here.

Hi all,

I'm having trouble getting my Setup 1.x startup.bat to run.

I ran it in Setup 1.x to check that it is OK, and it didn't give me any problems. Here is what I have in it:

call speedup lbacache (1)
call iport g1 1 
call iport dGPU off
call vidwait 60 10de:11c6
call vidinit -d 10de:11c6 
call pci  (2)
call grub4dos win7

I have tried removing (1) and (2) individually, and together as nando recommended to another user here before. It did not make any difference.

Here is my pci.bat

REM r:/core/compact.exe pciend 310000000 useonly 8086:0126 import devcon.txt makebatch R:\config\pci.bat
REM created Wed Jan 16 23:28:51 2013
echo Performing PCI write (compact@Wed Jan 16 23:28:51 2013)

@echo -s 1:0.0 COMMAND=0 BASE_ADDRESS_1=c BASE_ADDRESS_2=3 COMMAND=0 BASE_ADDRESS_3=fe00000c BASE_ADDRESS_4=2 > setpci.arg
@echo -s 0:2.0 COMMAND=5 BASE_ADDRESS_2=e000000c BASE_ADDRESS_3=2 >> setpci.arg
@echo -s 1:0.0 COMMAND=0 BASE_ADDRESS_0=fd000000 >> setpci.arg
@echo -s 1:0.1 COMMAND=0 BASE_ADDRESS_0=febfc000 >> setpci.arg
@echo -s 0:2.0 COMMAND=5 BASE_ADDRESS_0=fcc00004 BASE_ADDRESS_1=0 >> setpci.arg
@echo -s 0:1c.0 MEMORY_BASE=fd00 MEMORY_LIMIT=feb0 PREF_MEMORY_BASE=fe01 PREF_BASE_UPPER32=2 PREF_MEMORY_LIMIT=ff1 PREF_LIMIT_UPPER32=3 >> setpci.arg
@echo -s 0:1c.1 MEMORY_BASE=f1b0 MEMORY_LIMIT=f1b0 PREF_MEMORY_BASE=fff1 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=1 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1c.3 MEMORY_BASE=f1a0 MEMORY_LIMIT=f1a0 PREF_MEMORY_BASE=fff1 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=1 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1c.4 MEMORY_BASE=f190 MEMORY_LIMIT=f190 PREF_MEMORY_BASE=fff1 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=1 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1c.5 MEMORY_BASE=fff0 MEMORY_LIMIT=0 PREF_MEMORY_BASE=f181 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=f181 PREF_LIMIT_UPPER32=0 >> setpci.arg
@echo -s 0:1.0 MEMORY_BASE=f190 MEMORY_LIMIT=feb0 PREF_MEMORY_BASE=f181 PREF_BASE_UPPER32=0 PREF_MEMORY_LIMIT=ff1 PREF_LIMIT_UPPER32=3 >> setpci.arg
@echo -s 1:0.0 COMMAND=0 COMMAND=0 >> setpci.arg
@echo -s 0:2.0 COMMAND=7 >> setpci.arg
@echo -s 1:0.0 COMMAND=0 >> setpci.arg
@echo -s 1:0.1 COMMAND=0 >> setpci.arg
@echo -s 0:2.0 COMMAND=7 >> setpci.arg

setpci @setpci.arg
set pci_written=yes

My Device Manager sees the GTX 650 Ti, and displays an error 12.

The steps I took to get here:

1. Boot into Windows 7 with eGPU plugged in

2. Let the standard Windows 7 VGA driver install

3. Restart Windows

4. Uninstalled notebook Nvidia drivers

5. Restart Windows

6. Install the newest 310.x Nvidia drivers

7. Restarted Windows

8. Device Manager Error code 12 for the GTX 650 Ti

9. Boot into Setup 1.x

10. Video cards > Initialize > eGPU

11. Video Cards > Hybrid GFX > dGPU off

12. PCIe Ports > Link Speed > G1 > port 1 (eGPU)

13. PCI compaction > method 36-bit > iGPU (none when asked for 32-bit)

14. Set the Chainloader to win7

15. Chainload win7.

Even after that last step, Windows 7 boots up but the eGPU is not displaying anything on my external monitor. So I reboot and tried those steps again, same result. Finally, I boot up Setup 1.x and selected the "Automatically run startup.bat" option. I watched the screen run through the script very quickly, and then boot up WIndows 7... same result as is now: I can see my GTX 650 Ti in device manager, but it's giving me an error 12. I shouldn't have to do a DSDT override because my TOLUD is 2.99GB (3GB), meaning I have enough space for the eGPU.

Am I missing something? I've been at this for hours, and I know that I must be doing something wrong... but it's escaping me and I'll bet it's the littlest thing too!

Hi all,

I'm still working with HIT on my PE4H package exchange, and I must say that they're doing an absolutely bang up job with it. I'm really very impressed by their effort. Considering that it was my own mistake for ordering the PE4H kit instead of the PE4L from the get go, HIT has been really accommodating to me. The included Setup 1.x software hasn't gone amiss either.

My sales rep has mentioned that they now recognise that the PE4H board is PCI-e 2.0 compatible, and that this particular part does not require replacement. So rather than exchanging my entire PE4H+PM3N package for a PE4L+PM060a which has the disadvantage of being one large component, my sales rep is attempting to work with their engineers and inventory guys to see about only exchanging my current PM3N + mini-HDMI cable for the "newer" PM3N+cable.

My best guess is that he is implying the very same thing that BPlus has mentioned, that the PE4H + L060a + PM3N is the next best thing available given my situation.

In the meantime, he has said that this particular exchange may take a little while, and that I should go ahead and start using my current components until all these details get straightened out. I'll use this opportunity to setup my laptop then. Hopefully things will go swimmingly here

Other than the PE4H being a larger, sturdier base board with a detachable cable, is there any other benefit over the PE4L? I'm just asking out of curiosity more than anything else.

HIT has authorised a complete refund of my PE4H package and is shipping me a PE4L. I don't mind at all if the PE4L is smaller and not as sturdy, so long as end result is that I get better performance with the PE4L+PM060a. I have an old Shuttle PC case coming my way, and I'll likely jerry rig that to hold the GPU, PSU and PE4L package, and then stack my monitor on top of it.

Are you sure? From the first page:

"NVIDIA's Optimus can engate on your your eGPU setup if you have:

• Intel IGP: Intel GMA 4500MHD, HD, HD3000 or x3150 (Pine Trail)
  
• NVIDIA Fermi desktop card: GT4xx, GTS4xx, GTX4xx, GTX5xx, or GTS240. A GTS250 or older will not work."
  

If I remember correctly what is important is that you have an ACTIVE intel gpu (which I have), but I thought it's not required a notebook with a dedicated nVidia gpu (there's no mention of it).

To my knowledge, the point is if the SB Pentium HD graphics is among the chips that support Optimus. It should, since it's similar to the HD2000, but I hope someone will confirm...

Perhaps you're right. As I stated, it was my understanding that your system had to have Optimus already in order for it to engage...

Edit: my notebook has a sandy bridge pentium cpu (b960) and no dedicated graphics. Will Optimus engage with the integrated HDgraphics (it's very similar to the HD2000, just with a few minor features deactivated)??

No, My understanding of Optimus and Opt1.2 is that your system had to have Optimus prior to installing the eGPU.

Hi Tech Inferno Fan,

So if I got this right, that means that you can pair a PE4H with a PM060a for PCI-e 2.0 performance, thus Opt 1.2?

I'm in the process of working out with HIT an exchange for the PE4H+PM3N (just received it in the mail yesterday) for a PE4L+PM060a**. Is there confirmation/proof anywhere else about this? If this is the case, it would simply mine and HIT's effort in my situation. The guys at HIT have been more than accommodating with me, and I'm over the moon with their support so far. Granted they are a little bit slow to respond via email, but that's not a concern for me.

Hopefully this great news about the PE4H is true. That would be really great to be able to just return the PM3N board in exchange for the PM060a (if HIT carries just the PM060a boards that aren't soldered to the PE4x).

** No confirmation yet from HIT, but my salesperson has said that they will try to work out an exchange such that I can return my entire PE4H+PM3N for credit towards the PE4L+PM060a and receive any left over funds as a refund (since the PE4L is cheaper than the PE4H).

PE4H 2.4 supports pci-e 2.0

Good news for PE4H 2.4 owners. According to a new update at PE4H (PCIe passive adapter ver2.4) where they've soldered the EC2C/PM3N end but left the other end detachable, PE4H 2.4 owners can now get pci-e 2.0 performance if attached to expresscard/mPCIe 2.0. PE4H 2.4 has a nice and study base so was my favorite as an open, free standing device.

Hi all,

Here are some screens in the modded BIOS for my laptop

Primary Display Selection: options are

IGD (guessing is Intel)

PEG

PCI

Auto

It appears that one can set the graphics to any of these, though IGD is default. Selecting PEG and PCI don't appear to make any difference, at least on a "software" level where Windows 7 is concerned. I haven't noticed any particular changes within Windows when using one of the non-IGD selections. (I've since returned it to IGD).

I am assuming here that "Primary Device Selection" really just means "what graphics device to boot from". This doesn't appear to disable anything. I will likely have to disable dGPU from Setup 1.x, as recommended from tondy, quoted below:

I would personally try disabling dGPU via setup 1.x before flashing bios. You can run setup 1.x via usb for temporary testing until you've settled on a working setup. Since you bought the PE4H from HIT you should be getting setup 1.x for free included.

Self-explanatory: "Max TOLUD". I forgot to take a photo of the these screens (borrowing an NBR user's here), but I can confirm in my Device Manager that my TOLUD is already 3GB (value is BFA00000 = C0000000 = 3GB) so should be plenty of room for eGPU.

Can't wait to sort out this PE4H/PE4L issue with HIT, and to finally get a chance to play with the eGPU.

Compare x1.1Opt vs x1.2Opt results at http://forum.techinferno.com/diy-e-gpu-projects/2109-diy-egpu-experiences-%5Bversion-2-0%5D-20.html#post30509 and http://forum.techinferno.com/diy-e-gpu-projects/2158-diy-egpu-guide-sony-vaio-vpc-z2-svz13.html#post27918 . The doubling of bandwidth b/w pci-e 1.x and pci-e 2.x adds a considerable amount of extra real-game FPS.

There's supposedly a modded bios that can switch the dGPU off on your L502x so with the PE4L 2.1b it may not even need to boot via Setup 1.1x. The PE4H 2.4 woud require booting via Setup 1.1x to downgrade the mPCIe port link from pci-e 2.x to pci-e 1.1x speed. The extra performance and easier installation are reason why I'd recommend offloading/returning the unopened pci-e 1.x capable PE4H-2.4 and getting a pci-e 2.0 capable PE4L 2.1b instead.

The stupid thing is, after reading all those pages on NBR, I knew that one was "better" than the other (PE4L vs PE4H), but when I was ordering the parts on HIT I had it the other way around: I thought that PE4H was the better board, which allowd 1.2Opt whereas PE4L allowed 1.1Opt.

I'll work with HIT to see what kind of return/exchange I can work out. It wasn't until I came here to register and post a thank you that I read that PE4L is the better board. Quite the "duh" moment, isn't it.

And yes, the user capitankasar at NBR has a modded BIOS for the L502x wherein there is an option to set the primary video adapter; this may or may not actually disable the dGPU, but I'll find out once I flash the new BIOS.

Thanks again!

First and foremost I want to thank Tech Inferno Fan for all his dedication to this DIY project, and the many threads he maintains. It's not easy maintaining your composure across so many threads on the internet. That pretty much makes him a demi-god. I had been following the thread on NBR for a while (not sure about the whole banning debacle, but I don't delve into that)and came here when I saw the links.

Now on to the flesh of the matter. My notebook is the Dell XPS 15 L502x, i7-2760qm, 8GB mem, GT540M gpu (Optimus), and has a free mPCI-e port. The GPU that I bought is the Gigabyte GTX 650 Ti OC 2GB ($120), and a Cooler Master Extreme 2 Power Plus 625W (12V1 @ 24A) ($40) [both were on sale].

I currently have a PE4H-PM3N (from HIT) in the mail. I had read many, many, many pages on the NBR forum before finding out that the PE4L gives better performance due to PCI-e 2.0. But by that time, it was too late: I had already ordered the PE4H package.

In realistic numbers (say, in-game FPS), how much of a performance drop is PCI 2.0 vs 1.0? I understand that I will be able to do, at max, Opt 1.1, with the PE4H and I'm fine with that. I just wanted to upgrade my GPU from the GT540M to something capable of running games at framerates higher than just 30 fps at med settings. I've also inquired with HIT if I can exchange the PE4H for the PE4L, but I have yet to hear back from them (I only just inquired today).

I've been assembling my own gaming rigs for years. That said, I'm actually not too well versed in the differences in performance between stuff like PCI-e generations; I've only just gone with what's standard for the time.

Thanks in advance! And hope everybody had a happy new year!