pandastruck
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by pandastruck
-
-
I found a way that the eGPU works!
Boot into Setup 1.3, Menu Based
64bit address room for the iGPU
Force 32bit room to the eGPU
chainload windows and VOILA! The eGPU works. Now my iGPU has error 12 but who cares?
I'm gonna test it some further
Thx everyone, especially Tech Inferno Fan!
-
"pt MEM writefromfile 1 0xDAFE9000 dsdt.aml" 'works', but Windows won't start - only a BSoD...
Maybe the mistake is in my dsdt_....dsl File. Like described here: http://forum.techinferno.com/diy-e-gpu-projects/2109-diy-egpu-experiences-%5Bversion-2-0%5D-264.html#post82012
If I use your iasl.exe from that howto-package, my dsl compiles. If i use a newer iasl.exe Version from 2013 oder 2014 I get the error messages like in my post above. Is there a chance to fix this error? Or is there another opportunity to create an error-free dsl file that I can compile to this needed .aml file?
Edit: Even a non-edited dsl File won't compile... Same error.
-
OMG. I can't be so damn stupid Must be a hard week.. ;D I'll give it try...
Edit: @Tech Inferno Fan
The first five steps cant be executed in DOS mode. The 'pt MEM writefromfile ...' command was executed in the Setup DOS prompt.
- 1
-
It did it like 10 times now here are some Screenshots.
edit: sorry, i dont know how to make thumbnail views for the screenshots
edit2: now i used a newer version of iasl from this site: https://acpica.org/downloads/binary-tools
Now, it won't compile.
edit3: The line where the error shows up is (7160):
Name (_IRC, 0x00) // _IRC: Inrush CurrentMicrosoft Windows [Version 6.3.9600]© 2013 Microsoft Corporation. All rights reserved.C:\Windows\system32>cd ..
C:\Windows>cd ..
C:\>cd tool_new
C:\tool_new>iasl -g
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140114-32 [Jan 14 2014]
Copyright © 2000 - 2014 Intel Corporation
Table [RSDT] obtained from registry, 196 bytes
Table [RSDT] written to "RSDT_TP-G4.dat"
There are 20 tables defined in the XSDT
Table [FACP] obtained from registry, 268 bytes
Table [FACP] written to "FACP_TP-G4.dat"
Table [DSDT] obtained from registry, 65365 bytes
Table [DSDT] written to "DSDT_TP-G4.dat"
Disassembly of DSDT
Pass 1 parse of [DSDT]
Pass 2 parse of [DSDT]
Parsing Deferred Opcodes (Methods/Buffers/Packages/Regions)
Parsing completed
Disassembly completed
ASL Output: dsdt_TP-G4.dsl - 561971 bytes
C:\tool_new>iasl.exe dsdt_TP-G4.dsl
Intel ACPI Component Architecture
ASL Optimizing Compiler version 20140114-32 [Jan 14 2014]
Copyright © 2000 - 2014 Intel Corporation
dsdt_TP-G4.dsl 2503: Method (_DOD, 0, NotSerialized)
Remark 2120 - ^ Control Method should be made
Serialized (due to creation of named objects within)
dsdt_TP-G4.dsl 3912: Method (_CRS, 0, NotSerialized)
Remark 2120 - ^ Control Method should be
made Serialized (due to creation of named objects within)
dsdt_TP-G4.dsl 5393: Method (_Q16, 0, NotSerialized)
Warning 3115 - Not all control paths return a value ^ (_Q16)
dsdt_TP-G4.dsl 5891: Method (GBIF, 3, NotSerialized)
Remark 2120 - ^ Control Method should be
made Serialized (due to creation of named objects within)
dsdt_TP-G4.dsl 7037: Method (MHGI, 1, NotSerialized)
Remark 2120 - Control Method should be made Serialized ^ (due to creation of
named objects within)
dsdt_TP-G4.dsl 7610: Name (_IRC, 0x00)
Error 6103 - ^ Reserved name must be a con
trol method (with zero arguments)
dsdt_TP-G4.dsl 8305: Method (NBCI, 4, NotSerialized)
Remark 2120 - ^ Control Method should be
made Serialized (due to creation of named objects within)
dsdt_TP-G4.dsl 8307: Name (_T_0, Zero)
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt_TP-G4.dsl 8577: Method (NVSB, 1, NotSerialized)
Remark 2120 - ^ Control Method should be
made Serialized (due to creation of named objects within)
dsdt_TP-G4.dsl 9467: Method (_PLD, 0, Serialized)
Warning 3115 - Not all control paths return a value ^ (_PLD)
dsdt_TP-G4.dsl 9467: Method (_PLD, 0, Serialized)
Warning 3107 - Reserved method must return a value ^ (Package require
d for _PLD)
dsdt_TP-G4.dsl 12334: Method (SCMP, 3, NotSerialized)
Remark 2120 - ^ Control Method should be made Ser
ialized (due to creation of named objects within)
dsdt_TP-G4.dsl 13429: Method (MHPF, 1, NotSerialized)
Remark 2120 - ^ Control Method should be made Ser
ialized (due to creation of named objects within)
dsdt_TP-G4.dsl 13449: Method (MHIF, 1, NotSerialized)
Remark 2120 - ^ Control Method should be made Ser
ialized (due to creation of named objects within)
dsdt_TP-G4.dsl 13618: Method (GOBT, 1, NotSerialized)
Remark 2120 - ^ Control Method should be made Ser
ialized (due to creation of named objects within)
dsdt_TP-G4.dsl 13666: Method (NVOP, 4, NotSerialized)
Remark 2120 - ^ Control Method should be made Ser
ialized (due to creation of named objects within)
dsdt_TP-G4.dsl 13668: Name (_T_0, Zero)
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt_TP-G4.dsl 13803: Method (NVPS, 4, NotSerialized)
Remark 2120 - ^ Control Method should be made Ser
ialized (due to creation of named objects within)
dsdt_TP-G4.dsl 13805: Name (_T_1, Zero)
Remark 2011 - Use of compiler reserved name ^ (_T_1)
dsdt_TP-G4.dsl 13806: Name (_T_0, Zero)
Remark 2011 - Use of compiler reserved name ^ (_T_0)
dsdt_TP-G4.dsl 15298: Method (PMON, 2, NotSerialized)
Remark 2120 - ^ Control Method should be made Serialized
(due to creation of named objects within)
dsdt_TP-G4.dsl 15614: Method (SCMP, 2, NotSerialized)
Remark 2120 - ^ Control Method should be made Serialized
(due to creation of named objects within)
ASL Input: dsdt_TP-G4.dsl - 15664 lines, 523393 bytes, 6707 keywords
Compilation complete. 1 Errors, 3 Warnings, 18 Remarks, 2951 Optimizations
C:\tool_new>
-
It doesn't I did exactly as you said. DSDT substitution, chainload mbr. Then i can choose Boot Win 8.1 or Setup. If I choose Windows and the Expresscard with the eGPU is plugged in, BSoD. if it's not connected, Windows starts up, as soon as i plug in the Expresscard, BSoD with the Error "BAD_POOL_HEADER". And there's no 'Large Memory'...Boot Setup 1.30 -> DOS prompt, type 'pt MEM writefromfile 1 0xDAFE9000 dsdt.aml' to do the DSDT substitution, then type 'chainload mbr'. Confirm that you have a Large Memory area in your device manager. If this worksthen that eliminates the DSDT substitution being the cause of the BSOD. Proceed then to add that line to your startup.bat, run 'setup', set PCI compaction->endpoint=56.25GB and then PCI compaction->Run compact, setting the scope to eGPU only, select Startup.bat->Test run then Chainloader->Test run. -
Thank you for your reply. I'll test it, when I'm at home later in the evening (CET).Boot Setup 1.30 -> DOS prompt, type 'pt MEM writefromfile 1 0xDAFE9000 dsdt.aml' to do the DSDT substitution, then type 'chainload mbr'. Confirm that you have a Large Memory area in your device manager. If this works then that eliminates the DSDT substitution being the cause of the BSOD. Proceed then to add that line to your startup.bat, run 'setup', set PCI compaction->endpoint=56.25GB and then PCI compaction->Run compact, setting the scope to eGPU only, select Startup.bat->Test run then Chainloader->Test run. -
Ok, then I'll pass on that. Maybe even help more information about the systems.
One is a Lenovo T530:
i7-3520M
HD4000, no dGPU
8GB RAM
Windows 8.1 64bit
I know that Lenovo shloud have no problems with TOLUD.
Hey guys, i'm the one with the T530 and TOLUD problems.
My latest try:
I used this howto (http://forum.techinferno.com/diy-e-gpu-projects/2109-diy-egpu-experiences-%5Bversion-2-0%5D-28.html#post31421). My TOLUD value is 0xFED40000 ~ 4GB.
My DSDT table starts at 0xDAFE9000. I installed Setup 1.3a. With 'iasl -g' I created the dsl file and edited it with the QWordMemory entry. 'iasl file.dsl' complied without errors and i got the dsdt.aml file. I rebooted into Setup 1.3 selected 'Start Setup 1.x with command prompt' and executed "pt MEM writefromfile 1 0xDAFE9000 dsdt.aml" - no errors. After that, with F10 I started the menu-based Setup and selected the "PCI 36-bit PCI compaction" on the eGPU and the "Force 32bit" on the iGPU. Till here it worked flawlessly. With a chainboot into Win8.1, I get a BSoD or my notebook just restarts.
Any further ideas? :/
eGPU experiences [version 2.0]
in DIY e-GPU Projects
Posted
Indeed! It works!