Quantcast DIY eGPU experiences - Page 35

+ Reply to Thread
Page 35 of 1167 FirstFirst ... 2531323334353637383945851355351035 ... LastLast
Results 341 to 350 of 11665
Like Tree18Likes

Thread: DIY eGPU experiences

  1. #341
    Notebook Consultant
    Join Date
    Feb 2010
    Posts
    170
    Rep Power
    8

    Default Re: DIY ViDock Experiences

    Has anyone found out if there's a driver or any way to make the graphics card + PE4x show video on the laptop display?

    Oh and also, would the Alienware m11x be able to use a high performance x2 1.0, x1 2.0 or x4 connection?
    Last edited by ruhtraeel; 22nd March 2010 at 11:45 PM.

  2. #342
    Elite Notebook User
    Join Date
    Aug 2007
    Location
    Lisbon, Portugal
    Posts
    2,495
    Rep Power
    23

    Default Re: DIY ViDock Experiences

    Quote Originally Posted by ruhtraeel View Post
    Has anyone found out if there's a driver or any way to make the graphics card + PE4x show video on the laptop display?
    Short version, no.

    If you want the long version, you can read the previous posts in this thread, this has been discussed already.
    Dell Latitude E6400 | P8600 2.40 GHz | Nvidia Quadro NVS 160M | 4GB RAM | 250 GB 7200 rpm | 1440x900 LED | Intel 5300 | Win 7 Pro 64 Bit
    Custom Desktop | i5 750 2.66 GHz | ATI HD5770 | 4 GB RAM | 1 TB 7200 rpm | Win 7 Pro 64 Bit | 1920x1080 22'' + 1680x1050 22''


    Please vote for the Alienware M11x R4!
    Live in Europe? Then vote for an European Alienware rep!

  3. #343
    Notebook Consultant
    Join Date
    Aug 2008
    Posts
    114
    Rep Power
    12

    Default Re: DIY ViDock Experiences

    Updated drivers for e1505 and made a nicer shoebox case for everything.
    Waiting for USB hub to come in to make the shoebox a usb hub as well =)

    e1505 has new 3dmark06 score, went up to 6848
    see:
    DIY eGPU experiences

  4. #344
    Banned
    Join Date
    Dec 2008
    Location
    YellowBrickRd.AU
    Posts
    7,931
    Rep Power
    0

    Default Re: DIY ViDock Experiences

    Update: while I was excited the following could be applied to Intel IGPs, I could only get it to work on a 4500MHD equipped Inspiron 1440. Neither the X3100 2510P nor the GMA950 DV2000 would allow me to locate their IGP's 256MB windows in PAE space. Thankfully those systems allowed PCI Reallocation, whereas the Inspiron 1440 would not, due to bios setting it's TOLUD too high. Good to have another option to try.

    IGP Reallocation: Easy > 3GB Win7 setup for Intel 4500MHD notebooks

    It was thought that Win7/64 would not require a 256MB window in < 4GB space, making PCI Reallocation redundant. However testing found the ATI 64-bit driver still needs a 256MB window in < 4GB space. Testing finding too that PAE (36-bit) addressing of Win7/32 works with the Intel IGP drivers. This gave a new solution where (1) the Intel IGP 256MB window could be relocated into 36-bit space (2) The ATI card could be allocated to use the 256MB window assigned by the bios for use by the Intel IGP. A simple solution demonstrated to work below for systems with a PAE-compatible CPU, which is pretty much any system since Pentium Pro. The main requirement now being the onboard graphics driver must support being relocated in > 4GB 36-bit PAE space which I only know 4500MHD does. ATI doesn't. Not sure on Nvidia.

    Solution

    1. Create USB DIY VIDock bootdisk
    2. Save igpreloc.bat below onto your USB bootdisk.
    3. Set the system-specific parameters.
    4. Boot DIY ViDock bootdisk and run 'igpreloc.bat'. It will chainload into Win7.

    igpreloc.bat
    Code:
    @echo off
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    :: Relocate IGP to 36-bit space (PAE). Designed for Intel chipset systems
    :: User defined system-specific parameters
    :: 
    :: port:    where 0=p1, 1=p2, 2=p3, 3=p4, 4=p5, 5=p6
    :: mem_win: the bios defined 256MB window used by IGP. 
    ::          Check it by running 'lspci -v -s 0:2.0' or in Device Manager.
    :: Inspiron 1440: expresscard slot is port5 (0/1c/4), IGP 256MB window@E0000000
    set port=4
    set mem_win=EFF1E001
    set io_win=2020
    ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
    :: Reallocate IGP at 300000000-30FFFFFFF (36-bit window - PAE compatible)
    :: That's at the > 12GB boundary, so is OK unless you have > 12GB of RAM
    :: Appears Win7 will do that upon detecting a conflict anyway, or DIY:
    echo [igpreloc.bat] Relocating Intel IGP... 
    setpci -s 0:2.0 18.l=0C
    setpci -s 0:2.0 1C.l=3
    
    echo [igpreloc.bat] Configuring underlying bridge's 256MB window.. 
    setpci -s 00:1c.%port% 1c.w=%io_win%
    setpci -s 00:1c.%port% 24.l=%mem_win%
    
    :: Chainload your OS, using whichever line works below
    grub 
    :: grub --config-file="menu.xp"
    :: grub --config-file="menu.w7"
    Test Results


    SystemRAMCPUGPUCommentsRelocated memmap
    Inspiron 14404GBT6600-2.24500MHD3GB requires no PCIscript. 4GB gives error 12: against the HD5750. The TOLUD of 3.5GB is too high to free 256MB using PCI Reallocation.
    After running igpreloc.bat on Win7/32 the 4500MHD will use resources in > 4GB space, even in Win7/32 by using PAE's 36-bit space. I can switch the internal LCD attached to the 4500MHD on no problem, AND use the desktop video card, so both the Intel and ATI drivers are active and work.
    here
    HP 2510P2GBU7600-1.2X3100IGP Relocation doesn't work. Might require the newer a series-4 (4500MHD) or newer gpu to do it. PCI Reallocation does however work OK-
    DV20003GBT2050-1.6GMA950


    So for systems which use a 64-bit CPU and chipset with Intel IGP graphics, this is a very easy solution to implement to allow a 4GB or more system configuration to work with ATI video cards.

    _____________________________________________________________________________________

    The technical description of what is being done in this solution and why is below.

    Microsoft's Win7 PCI enumerator isn't working to the ATI driver's requirements

    The Win7 PCI enumerator doesn't help clear things up either. It allocates the ATI card a 256MB window in > 4GB space when using a 64-bit CPU+chipset combo if there is no space to accomodate it in the < 4GB region. It does this even for Win7/32 since it supports PAE (36-bit addressing). So we have an ATI driver expecting a 256MB window in < 4GB space, with a Microsoft driver allocating the Window in > 4GB space.

    Symptoms

    When this occurs, the ATI desktop video card will have no errors against it in Device Manager. Checking Screen Resolution will even list the LCD attached to the desktop video card. The only way to know this is not a valid setup is by trying to extend the display to the LCD attached to the desktop video card. It will result in no image on the external LCD, and will simply revert back to the internal LCD. I would have liked to see the ATI driver flag an error here.

    Constraints based on test results

    * ATI's Win7 32-bit AND 64-bit driver require a 256MB window in 32-bit space (< 4GB).
    * Meaning ATI's 32-bit driver is not PAE compliant nor is the 64-bit driver fully 64-bit compliant
    * Win7 requiring the primary video card (IGP) to be active for the ATI card to work.
    * Intel IGP (x3100/4500MHD) drives are PAE/64-bit compatible.

    Within these constraints, can do the following as a workaround:
    * configure the underlying PCI bridge to use the IGP's bios defined 256MB window in 32-bit space
    * set the IGP to use a 256MB window in > 4GB space (PAE used for Win7/32-bit)
    Last edited by User Retired 2; 26th March 2010 at 04:13 PM.

  5. #345
    Notebook Geek
    Join Date
    Mar 2008
    Posts
    88
    Rep Power
    13

    Default Re: DIY ViDock Experiences

    Hi again,

    I've finally received my PEAH to connect my brand new Sapphire HD 5750 to my aging Asus F8SA/P. First bit of bad news is that my system has 5 enabled PCIe x1 ports (yay!) and the expresscard slot is port 5 (doh!). By tearing most of the laptop apart, I have only found a single mPCIe slot (2, taken by the WiFi card) so even though there are two slots free, my chances of getting a x2 link are looking slim... It looks like there might be another slot underneath the left palm rest (bluetooth? LAN?) but I couldn't reach it...will look into it further.

    The second bit of bad news is that I got the dreaded error 12 "cannot allocate resources". My laptop has 4GB RAM and runs Win7 x64. I've swapped a 2GB SODIMM with a 1GB one to get 3GB but didn't help. I can't follow nando4's latest recommendation since the laptop comes with a Mobility HD 3650, not an Intel IGP so I guess the PAE non-compliant driver issue remains.

    PCI address space editing is a bit out of my reach for now so perhaps someone would be so kind to have a look at my config and help me out with a possible reallocation bridge script?



    Here's my PCITOOL snapshot: http://www.mediafire.com/file/qrmzzzninzj/SNAPSHOT.BPD

    Any help would be appreciated

  6. #346
    Banned
    Join Date
    Dec 2008
    Location
    YellowBrickRd.AU
    Posts
    7,931
    Rep Power
    0

    Default Re: DIY ViDock Experiences

    Quote Originally Posted by ithildin View Post
    The second bit of bad news is that I got the dreaded error 12 "cannot allocate resources". My laptop has 4GB RAM and runs Win7 x64. I've swapped a 2GB SODIMM with a 1GB one to get 3GB but didn't help.
    ...
    PCI address space editing is a bit out of my reach for now so perhaps someone would be so kind to have a look at my config and help me out with a possible reallocation bridge script?
    ...
    Any help would be appreciated
    Based on your snapshot and Device Manager memory map, your system needs only a minimal PCI Reallocation to free up 256MB as shown below. Can then use that freed window to host the HD5750.

    F8SA.bat
    Code:
    :: Shrink 0/1/0 window from 512mb to 256mb starting at E0000000
    :: This will free up a 256MB window at D0000000. No idea why the bios
    :: made that window 512MB in size to begin with since it only needs 256MB
    setpci -s 0:1.0 24.l=EFF1E001
    
    :: 256MB free window at D0000000-DFFFFFFF, I/O window at 2000-2020.
    :: expresscard slot=port5 (0/1c/4)
    set port=4
    set io_win=2020
    set mem_win=DFF1D001
    
    @echo [bridge.bat] Configuring underlying bridge hosting desktop video card...
    setpci -s 0:1c.%port% 1c.w=%io_win%
    setpci -s 0:1c.%port% 24.l=%mem_win%
    
    @echo chainloading your OS with grub..
    :: Use whichever line works below:
    :: grub --config-file="menu.lst"
    :: grub --config-file="menu.xp"
    grub --config-file="menu.w7"
    Last edited by User Retired 2; 26th March 2010 at 04:53 PM.

  7. #347
    Notebook Geek
    Join Date
    Mar 2008
    Posts
    88
    Rep Power
    13

    Default Re: DIY ViDock Experiences

    Quote Originally Posted by nando4 View Post
    Based on your snapshot and Device Manager memory map, your system needs only a minimal PCI Reallocation to free up 256MB as shown below. Can then use that Window to host the HD5750. Correct also that IGP Reallocation would not work since you have ATI onboard and external graphics. ATI's drivers only want to work in a 32-bit space.
    Thanks nando4, that was quick

    The BIOS I am using is not exactly standard. My laptop was originally a F8SA with a Mobility Radeon HD 2600 512 MB. I've upgraded it to a Mob HD 3650 1GB but since the F8S chassis is not fully MXM compliant (it's the flipped design Asus tends to use) the VBIOS is actually merged with the main BIOS so I had to mix and match BIOS modules. I got the HD 3650 as a part for the higher specc'd model F8SP and replaced the F8SA VBIOS module with the one from the F8SP BIOS. It actually worked, mostly...! I lost some of the ACPI functions (fan control) probably because the vendor/part references don't match in the DSDT table in the BIOS anymore. The fan is now constantly on but the CPU and GPU are kept cool enough even under load so I chose not to press my luck any further. I am not sure if this has an impact on PCI memory allocation though. Still, your script should fix the issue.

    I tried it this morning before coming to work but I ran into trouble chainloading my Windows 7. I still had the recovery partition from my old Vista factory installation and grub kept booting that one instead of the W7 partition. After messing with the menu.w7 I managed to get it to root to the right partition but then I found that my W7 went bust. Between swapping RAM and remaping PCI devices, my W7 gets stuck at loading, even when I boot the machine directly without any bootdisk (so it's not a chainload problem per se). It's not a big loss since I had just made a fresh install last weekend just to mess around with my PEAH. I'll fix the partitions, install W7 on hd0,0 and start the process again.

    I'll keep you posted.
    Last edited by ithildin; 25th March 2010 at 10:38 AM. Reason: proof reading

  8. #348
    Notebook Evangelist
    Join Date
    Sep 2007
    Location
    Lolcation
    Posts
    651
    Rep Power
    16

    Default Re: DIY ViDock Experiences

    try to install a win xp driver to see if it'll work, you'll be limited to dx9 though
    Laptop: Inspiron 1505, 1.66 Core Duo, 3GB RAM, external XFX Radeon 5750 1GB + PE4L, 23" 1920x1080

  9. #349
    Notebook Geek
    Join Date
    Mar 2008
    Posts
    88
    Rep Power
    13

    Default Re: DIY ViDock Experiences

    Alright it works!

    After fixing the W7 partition, I could boot into Windows and run some tests. The HD 5750 is running just fine, no error 12 in sight! Since my first success in March, I've upgraded the CPU, implemented Nando's x1E tweaks (Everest screenshot here)and ran a series of additional benchmarks. Here are my current specs and benchmark results:

    Notebook
    Brand/Make: Asus F8SA/P
    CPU: Core 2 Duo T9300 2.4 GHz (was Core 2 Duo T7500 2.2 GHz)
    RAM: 4 GB DDR2 (667 MHz)
    Platform/Chipset: Santa Rosa/Intel PM965, ICH8M
    Laptop Graphics card: ATI Mobility Radeon HD 3650 1GB
    OS: Windows 7 Professional x64
    Drivers: Catalyst 10.3 (official)

    DIY Vidock
    Graphics card: Sapphire Vapor-X Radeon HD 5750 1GB
    Adapter: PE4H v1.0 + EC2C
    Connection: PCI-e 1.0 x1E (see notes here)
    Power supply: 90W 19V DC (notebook AC adapter) + 32W 12V DC (external DVD writer caddy)


    New results!
    3dmark Vantage
    Performance test - DirectX 10 - 1280x1024 - Default settings - Feature tests
    Setup Main score GPU score Texture fill rate Color fill rate Pixel shader Stream out GPU particles Perlin Noise
    E5400 + HD5750@x16 2.0 (desktop) P6898 7440 703.07 GTexels/s 3.67 GPixels/s 23.07 FPS 22.86 FPS 31.19 FPS 58.94 FPS
    T9300 HD5750@x1 P4999 4977 23.58 GTexels/s 3.7 GPixels/s 22.72 FPS 15.43 FPS 19.76 FPS 61.62 FPS
    T9300 HD5750@x1E P5318 5436 23.59 GTexels/s 3.71 GPixels/s 22.87 FPS 17.21 FPS 21.33 FPS 61.8 FPS
    T9300 HD5750@x1E (after resume) P4988 4961 23.55 GTexels/s 3.7 GPixels/s 22.77 FPS 15.44 FPS 20.59 FPS 61.56 FPS

    Notice the 30-fold difference in Texture fill rates between the desktop HD5750 and my DIY Vidock HD5750. It fits the idea that large texture handling is the major performance bottleneck here caused by the much narrower bandwidth of the Vidock setup (x1 1.0 vs x16 2.0 on the desktop). You can see that the x1E performance boost is lost after suspending+resuming the laptop. Apparently, the F8SA/P BIOS resets the port configuration back to normal x1 (confirmed by Everest).

    3dmark 06
    DirectX 9 - Fullscreen - 1280x1024 - Default settings - Feature tests
    Setup Main score SM2.0 score SM3.0 score
    E8400 + HD5750@x16 2.0 (desktop) 13439 5774 6642
    T7500 + HD5750@x1 8970 4456 4042
    T9300 + HD5750@x1 9704 4869 4063
    T9300 + HD5750@x1E 10499 5048 4885

    More detailed feature tests will follow.

    Resident Evil 5 Benchmark - DirectX 9
    Fullscreen - 1280x800 - High settings
    SetupAverage FPS (variable test)Avg FPS (fixed test)
    T7500 + HD5750@x151.3
    T9300 + HD5750@x153.825.9
    T9300 + HD5750@x1E66.137.3


    Resident Evil 5 Benchmark - DirectX 10
    Fullscreen - 1280x800 - High settings

    Coming soon...

    Crysis Demo Benchmark - DirectX 10 64 bit
    Avg of 3 runs - Fullscreen - 1280x1024 - High & medium settings

    Coming soon...

    Asus F8SA/P x1E Script (F8SAE.bat)
    Code:
    :: Shrink 0/1/0 window from 512mb to 256mb starting at E0000000
    :: This will free up a 256MB window at D0000000. No idea why the bios
    :: made that window 512MB in size to begin with since it only needs 256MB
    setpci -s 0:1.0 24.l=EFF1E001
    
    :: 256MB free window at D0000000-DFFFFFFF, I/O window at 2000-2020.
    :: expresscard slot=port5 (0/1c/4)
    set port=4
    set io_win=2020
    set mem_win=DFF1D001
    
    @echo [bridge.bat] Configuring underlying bridge hosting desktop video card...
    setpci -s 0:1c.%port% 1c.w=%io_win%
    setpci -s 0:1c.%port% 24.l=%mem_win%
    
    @echo Configuring port to x2 mode...
    :: Asus F8SA expresscard port 5. 'setpci -s0:1f.0 f0.l'=0xFED1C001
    pt MEM write 4 0xFED1C224 0xC4
    
    @echo chainloading your OS with grub..
    grub --config-file="menu.w7"
    Battlefield: Bad Company 2
    I've done some tests with BC2 to see if I could improve my fps with the DIY Vidock. Surprisingly, I got lower fps with HD 5750 than with the internal Mob HD 3650! The difference is roughly 30-50% lower performance compared to my OC HD 3650 (3dmark06=4189, less than half of my Vidock's HD5750). On both cases, GPU load is at 90-100% during play but while the HD3650 can manage 30-50 fps at 1280x800 on low settings, the HD5750 is choking at 18-30 fps on same settings. I tried dx10 vs dx9c, different resolutions, render ahead limits, etc.. My guess is that the HD 5750 is being starved for bandwidth, which has a big impact on performance in games like BC2. I will seriously look into upgrading it to a 2x 1.0 since I really want BC2 to run smoother!
    UPDATE: The x1E boost plus switching the game to DX9 resulted in impressive performance boosts! The game now plays steadily at 30-70 fps! More details coming soon...

    I'll keep this post up-to-date. Let me know if you would like me to run other benchmarks, etc.
    Thanks again for your help!

    Changelog:
    18-04-2010 - Updated specs, first result tables (with respective screeshots), x1E data.
    Last edited by ithildin; 4th May 2010 at 06:59 PM. Reason: Config and result updates

  10. #350
    Banned
    Join Date
    Dec 2008
    Location
    YellowBrickRd.AU
    Posts
    7,931
    Rep Power
    0

    Default Re: DIY ViDock Experiences

    Quote Originally Posted by ithildin View Post
    Battlefield: Bad Company 2

    My guess is that the HD 5750 is being starved for bandwidth, which has a big impact on performance in games like BC2. I will seriously look into upgrading it to a 2x 1.0 since I really want BC2 to run smoother!
    BC2: DIY ViDocked HD5750 30-50% slower than mobility HD3650 likely due to hypermemory and 1GB VRAM

    +1. A case where 3dmark06 synthetic benchmarks tells only half the story.

    The relatively poor HD5750 performance compared to the onboard HD3650 in BC2 is likely due to ATI's hypermemory setup, where system ram is being used as an extension to onboard VRAM to hold texture data. Means the video card needs to do transfers across the already limited PCI-e bus. Haven't found a way as yet to disable hypermemory. BC2 could do with a 1.5/2GB VRAM video card [eg: 1.5GB GTX480, 2GB Sapphire HD5850, 2GB HD4870]

    If you find an extra mPCIe socket or pads that is port1 to combine with your wifi port2, then you could do a port1+port2 x2 1.0 link, doubling bandwidth, which would definitely improve BC2 performance. Best performance would be from a 2GB VRAM video card AND a x2 1.0 link.
    Last edited by User Retired 2; 27th March 2010 at 07:48 AM.

 

 

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
All times are GMT -4. The time now is 05:37 PM.
Powered by vBulletin® Version 4.2.0
Copyright © 2013 vBulletin Solutions, Inc. All rights reserved.
SEO by vBSEO 3.6.0