Atonus

I connected the eGPU with the 6.9 sec delay and it worked, partly, the eGPU was detected, but there was no output to the external monitor I had connected to the eGPU. And when the GTX 770 drivers finished installing and the laptop rebootet Win was loading and for a split second it even showed the login screen, then it went black again. It isn't the rebooting process because I tested that one before and there were no problems, so it must have something to do with the dGPU drivers...

Ohhhh right, yeah. Thanks

Is this the reset slider?

I got the screen running again. I'm not quite fond of having to hotplug the eGPU everytime I want to use it. Would you please go into further detail about how to set up the pci reset delay. Alright, after I disable the dGPU for better cooling, just for you Nando, I will OC the CPU for the sake of research, however I probably won't leave it that way, unless of course it's stable and cool enough to run daily.

Nice, looks like we really made some progress today! However I'm still stuck with a 6440 that will boot up and load Win only to turn the screen black. I still couldn't figure it out. My theory would be that the Laptop on first boot with the eGPU attached somehow changed its default video output to the eGPU or something, and now it's neither responsive to the Intel HD 4600 or the AMD 8690M. But how can I resolve this..? Advice needed When I figure the afore mentioned problem out, I will then test whether the eGPU also works in Gen2 on A.07 and A.08. And I'll probably try to disable the dGPU. Until then, I need help for my "blackscreen"

It turns out that Dell did indeed turn of any RAID settings and hid it from the common user. Or rather didn't make it visible. What you have to do to enable RAID on the Dell Latitude E6440 is: - Download https://www.sendspace.com/<wbr>file/bouk3i It's a flash toolkit by Intel with additional batch scripts mostly for Asus boards. You can use fptw to dump your current or flash a new BIOS. - Extract it to C:\. The new path should be "C:\FTK8_0.11\Windows" You can extract it, where you want. However, it will be easier to handle the next steps, if it is C:\. - Start > type "cmd" > right click > Open as Administrator. You need full rights to run fptw.exe - Type "cd C:\FTK8_0.11\Windows" to change your current directory to the toolkit folder - Type "fptw.exe -D backup.rom -BIOS" This command will create a dump (-D) of the BIOS section (-BIOS) to the file backup.rom. The Management Engine section for example is read/write protected, so it won't be possible to do a full dump. Then you can open the dump with "UEFITool" (just search for it on Google), then search for and extract the module SetupPrep, when you find it, run it trough the "Universal IFR extractor" which will generate a text document of the input. I attached my text document down below so that you can compare. SetupPrep IFR.txt The interesting part is in my case in line 2030. It tells us the name of the setting ("RAID0"), the hexadecimal address in the NVRAM (0x19D) and its possible values (0 - Disabled/ 1 - Enabled). In my 6440 the NVRAM 0x19D was 0, so disabled. To change the NVRAM download the following programm: http://brains.by/posts/<wbr>bootx64.7z An easy way to run the app, would be to place it on a FAT32 formatted thumb drive in a folder named EFI, so the path looks like this: "EFI\Boot\bootx64.efi". On each boot your notebook looks for this file and if it is found, it is started. If not, go to the boot menu (F12 if I remember correctly) and select your thumb drive at the UEFI boot section. You should then see a GRUB boot loader and possibly you will need to confirm that you want to continue. The command prompt, which you will reach, will be the place, where you can flip the RAID0 setting - amongst others. To make sure this tool finds the correct values, read out some settings first. To read out a value you need to write "setup_var <address>", to store values "setup_var <address><value>". - "setup_var 0x19D" should show you 0x0, which would mean the RAID0 option at address 0x19D is disabled. For most addresses you will see 0x0, so let's check for a more unique value .. - "setup_var 0x1AF" should display a value ranging from 0x69 to 0x7F, which is the value for the "Critical Trip Point" at line 1659 If not, you should abort and not use it. Otherwise you can enter "setup_var 0x19D 0x1" to store 0x1 at address 0x19D and activate RAID0. Then you can reboot and see what happens. If something went wrong, or you simple want to change the setting back to its default state, boot again from your thumb drive and enter: "setup_var 0x19D 0x0". I actually did this procedure on a A.07 BIOS by accident, however it turns out that I was able to downgrade to A.02 afterwards and my RAID config was still working. I don't know about any other BIOS versions though. So I set up the Laptop, final specs: i-7 4810MQ 2,8 Ghz (no overcl), 16Gb 1866Mhz, AMD 8690M, 2x250Gb Samsung EVO RAID 0, Win 8.1 Pro 64bit, BIOS A.02 Mods: EC Retrofit, ODD SSD, eGPU: EVGA GTX770 SC, Corsair ATX, PE4L-EC060A, DIY BOX V1.1, dual monitor 1080p ******, I read your eGPU post for the 6440 and you said its simply a matter of plug and boot in order for the TOLUD to lower, which I did. And the Laptop recognized the 770, but when I rebootet the laptop screen just went black (but still bg</value>-illuminated) I was able to see the mouse cursor, but nothing else. Even if I unplug the eGPU there's only a black screen. Please help me if you can. I'm not sure what I've done wrong.</address><address><value> Regards!</value></address></address>

Soooo, hello again, got some big news. I managed to enable the RAID 0 option in the BIOS again. So this is my setup until I get the eGPU working: i7 4810MQ 16 Gb 1866Mhz 2x250 Gb Samsung EVO RAID 0 And the eGPU will be a EVGA GTX770 SC

Hi, so I followed your advice, Nando, and got myself a 6440. It is indeed a very nice, well built laptop. Still, I did encounter a problem even before attempting the eGPU mod. I was trying to set up a RAID 0 with 2x250Gb SSDs however Intel's RST only gives me the option to create a recovery array. No raid 0, no raid 1, nothing. I tried it on the A.02 and on the A.07 version, updated to the latest drivers and still can't get it to work. Do you guys have any idea what it could be? I'd be very grateful for any advice. If you need further information just ask. Benjamin

Did anyone actually attempt to retrofit the dGPU cooler? Because on these pictures it looks like the screwholes are in different spots than the iGPU cooler ones....