Some people seem to think you can disable enduro with a bios update.
Let me show you why not:
![]()
Take out the IGP in the clevo machine and the chain is broken.
-
Meaker@Sager Company Representative
-
That makes sense
Thanks!
-
Is it yet known whether you can disable Optimus if you have an Nvidia card in a clevo EM series? I'm contemplating buying a 680m and selling my 7970m.
-
If the 7970 goes through the IGP as shown, the nVidia will do the same.
-
Thanks
My question: WHY?
Is there a reason they would do it like this? -
From my point of view it would be to cut cost. Would be nice to hear from Clevo why, but that will never happen.
-
Meaker@Sager Company Representative
There is also a slight power penalty.
Cost on multiple factors, more chips, more traces, more complexity in the bios (more bug testing). -
so basically what we need is a solution (im assuming a driver) that shuts off the igpu leaving only the channels open that the dgpu needs to run through in order to operate?
-
Meaker@Sager Company Representative
What you are describing is enduro. Since the integrated is the only chip wired its the integrated chip that has to output the rendered frame.
-
and the iGPU has no issue keeping up with what's being outputted by the GPU?
-
It makes a bit of sense, but where did you get those diagrams/information?
-
Id also like to know the for source those diagrams.
I do know that Nvidia's Optimus works by attaching the dGPU to the iGP's Framebuffer for the video output.
It would be odd for AMD/ATI to do anything different than that. Even more odd to have Dell design a different method, that is not the standard method that the device manufacturers support in their reference documents. -
so we have to wait for better drivers then...?
-
Meaker made them himself. We just have to wait for mature drivers. optimis sucked when it first came out as well. patience!
-
DeutschPantherV Notebook Consultant
-
it shouldnt, as it doesnt have a problem keeping up with Optimus.
-
Meaker you are correct that you cannot "disable" enduro or completely bypass the iGPU completely. Having said that, you could design a "switch" that forces the dGPU to be used exclusively and always.
Enduro does some sort of check based on program running, what is being requested, or some other criteria by which to judge whether to use the iGPU or the dGPU. If we could force the dGPU to be used for everything then that check would never occur and never choose wrong and presumably that check incurs some sort of performance hit even if it is extremely minimal and only for the very start of any new program.
So calling it "disabling Enduro" is inaccurate but I think what we're interested in is being able to force Enduro's choice. -
-
@erikk
I think that would be the best case if there is no true way to disable the iGPU which sounds like there is not. The actual iGPU or HD 4000 is actually on the processor in any case. So I am guessing that the AMD/nVidia is actually going through the frame buffer or external component that is controlled by the iGPU.
Not really an expert in that area anymore. -
Having said all this, I don't have my laptop yet so I'm not very familiar with all the ins and outs yet and I'm only speaking from second hand knowledge but I believe that my comments are accurate. -
*sigh*.......
-
I'll be the first to admit that I don't know if it will help but having multiple programs configured differently and a check for every running program sure seems like a recipe for problems and performance issues and personally I don't see why giving the "forced" functionality to us the end user is in any way hard to do or something they should keep us from being able to do. Ideally at some point in the future (sooner would be better) the AMD drivers will be mature enough to actually do what they're supposed to without any performance problems but would having a force dGPU option even then be a problem? At that point we'd all just recommend don't bother using it, Enduro is great and there's no reason not to use it now. -
im only sighing because i think i need to take a break from stressing out about the 7970m driver issues all day
im just going to wait till my machine actually comes in then ill start worrying again -
I know the feeling. When XoticPC offered to put "expedited" on my order with Sager I almost told them not to because I didn't want anyone doing anything with my pc to be rushing.
-
All I know is in my HP DV6z when there was finally a way (with hax) to set fixed dGPU, performance went up a measurable amount and there were no hiccups. It was still muxed through the iGPU, but there was no software to fuss with when the dGPU should engage or not. It was just ON.
I know in that case it's AMD GPU to AMD CPU, but the concept is the same. -
So can we assume the Clevo HM series is identical to the diagram on the right? i.e. the dell/AW one?
-
-
Hey sager! We want optimus! We want optimus!
Oh !
We don't want optimus! We don't want optimus! -
Thus explaining why the hell the Clevo's cant be used without a GPU.
-
Personally I never wanted Optimus or any kind of software switching. I always wanted a hard switch.
-
yes, ideally, a hardswitch would be the best. perhaps on the next gen they will have a standard mxm slot that connects to a mux and an igpu that connects to a mux with a spdt switch haha.
-
-
-
Start a petition.
-
Awesome illustration, thanks! One question—I read on another forum that the external video ports are wired directly to the discrete card, while the internal LCD follows the architecture you describe. Do you know if this is true, and if so, what the implications would be? If this is true (and I honestly have no idea), would it be possible to bypass the integrated card by running the system in clamshell mode?
-
-
I think the iGPU may have been holding the dGPU back too even on Optimus, the followings are the screenshots I took between the P150EM with i7-3610QM + GTX 675M and the G73JW with i7-940XM + GTX 460M. The program I used is FFXIV benchmark, both pictures are taken during loading screen (Glossy screen = G73JW, Matte screen = P150EM):
G73JW i7-940XM@ 2.4GHz (to match the 3610QM) and GTX 460M @ stock clock, GPU usage 99%, 425.0 FPS:
P150EM i7-3610QM@ 2.3GHz and GTX 675M @ stock clock, GPU usage 82%,226.8 FPS:
-
Why did Clevo go for this design?
Was it thrown onto them from AMD or did they choose this path for igpu/dgpu piggyback? -
There must be a way to get full usage on our 7970M.
I can't actually monitor my frequencies !!!
I do the overclock using MSI AfterBurner (done the tutorial for unlocking OC), but I can't monitor my real frequencies, GPU-Z only show me the Intel 4000 Integrated Graphics.... Help ? -
Meaker@Sager Company Representative
Afterburner shows your frequency lol.
Also Yes the design will hold back FPS..... when you get over 200fps and the bus can't handle any more frames being sent over it. -
When I run at 720P I can get roughly 1000FPS at loading screen on the G73JW, and only 550FPS on the P150EM.
-
Try firing up GPU-z AFTER you're running a 3D app.
But if it's limiting FPS then that's crazy. What does this mean for high bandwidth games, AA enabled, etc? Will this cause issues? -
-
If iGPU does not limit FPS or bandwidth on 680m / Optimus, there should be no reason it limits with AMD. So I am really hoping the issue lies in the way AMD card handles the throughput and can actually be resolved via driver update. I also have another test that points toward a software cause / solution: - if I run Kombustor burn in test in DX9 / OpenGL mode, I get around 80fps / 75% usage; with DX10 / DX11 mode I get 99% usage and 125 fps. This kinda proves that the card is capable of doing 100% usage and performance but certain software functions are bottlenecking rendering process.
-
As soon as I alt+tab, I can see my running AfterBurner showing me that frequencies are droping (going on iGPU ?). Gpu-Z still shows me Integrated Frequencies in any situation... -
-
-
Meaker@Sager Company Representative
Yes initially PCI-E 2.0 was a bottleneck for 120hz 1080p.
However now we are on PCI-E 3.0 it should be ok.
Why you can't disable enduro.
Discussion in 'Sager and Clevo' started by Meaker@Sager, Jun 27, 2012.