Thanks Richard, but that did not work either. I downloaded he zip file and followed the instructions to do a manual install. However I then got an error message telling me that my driver was already up to date and the installation did not proceed!
Well, I think I'm out of ideas, then. Any further experiment - like removing the old driver and installing the new one 'clean' (which might be the obvious next step) - run the risk of leaving you with an unusable machine, and I can't advise that. Running Einstein on a GPU is cool, but not that important.
Thanks anyway Richard. I agree uninstalling video driver is not something I would want to do so I will just keep crunching Collatz and keep an eye on he Dell driver web site for when a new one is available.
Your CPU & GPU are from the Ivy Bridge generation and Richard's is a new Haswell, that's why he got the current driver installed. Knowing DELL he's probably never going to get an update, though.
I'd definitely ask DELL support for a current driver, specifically with OpenCL 1.02 support. If they decline I'd poke them a bit harder and demand to be actually be able to use the product they sold me. If that won't help.. well, there may not be much to do except never buying from them again.
For mobile nVidia chips the driver get "hacked" regularly, so people can update their PCs with the regular driver, instead of waiting for updates from the manufacturers which never appear anyway. That hack is simply adding the card's IDs to some ini file. Could be that this is available for Intel too.
Dell plus Intel : my commiserations. I did crunch for E@H with one of them and when the driver requirements changed, I proceeded to much the same impasse. Took that unit off crunching.
[Aside : When developing with OpenGL, I found Intel's driver adherence to standards appalling. This lead me to coin the phrase 'lying driver' meaning that upon runtime inquiry ( under Windows ) of the driver, a certain OpenGL version would be claimed. However upon further inquiry ( to obtain the function entry points ) many calls were simply not available that should have been as per the stated version! Of the very many machines I could lay my hands on to test ( bar one with an obtuse card maker ) only Intel graphics on Dells had this problem. So what's with that ? ]
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
So it sounds like Dell would indeed cut some transistors off their Intel GPUs to make them incompatible with OpenGL and regular drivers. Hurray! :p
It must be expensive to treat all those CPUs. And they probably put huge efforts into not damaging other parts of the chips while sabotaging the GPUs..
So it sounds like Dell would indeed cut some transistors off their Intel GPUs to make them incompatible with OpenGL and regular drivers. Hurray! :p
It must be expensive to treat all those CPUs. And they probably put huge efforts into not damaging other parts of the chips while sabotaging the GPUs..
Well, in over about 60 machines, I didn't find any problems with Intel graphics outside of Dell laptops to be exact. As I didn't know anyone with a Dell desktop box, I can't speak of them.
IIRC the OpenGL functionality claimed, but then denied, was related to server-side ( ie. typically implemented on the graphics card ) memory stuff like buffer objects etc. So that suggests a design choice related to memory, but IIRC some of them have a shared memory arrangement between GPU and CPU ? Something like that. So maybe the Intel driver wasn't written for such sharing - and why would it be - so maybe Dell couldn't/wouldn't be bothered to factorise that and Intel didn't want to rewrite the driver ( as that wasn't in the supply deal ). Easier to just block/not-expose certain software functions, 'on the quiet' so to speak. But I speculate excessively here .... :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Isn't possible to manually force a Driver onto the System ?
I used that technique to get a Vista64 System to accept a Trinity AMD APU Driver for a more modern but compatible Richland AMD APU. Dirty workaround, but so far it works for lots of hardware-compatible but DEVICE_ID-incompatible devices.
In short, if the hardware is compatible, Windows should accept any driver manually selected from an existing Driver package via the Device Manager.
The only small hassle is to locate the .inf File for the proper OS in the Driver package, otherwise Windows naturally won't install it (either look into its unpack location which usually remains in place or use a tool like 7Zip to manually extract the entire package onto HD)
For all I know, that is basically what driver "hacks" do (albeit in a more user-friendly, elegant manner), they include the proper lines for unlisted DEVICE_IDs in the Driver .inf file that they know are hardware compatible (so called .inf hack, that with sufficient time/experience isn't actually very difficuly to do - if you know exactly what you're doing that is).
That technique dates way back into 3dfx times and continued to work through Notebook drivers, Peripherials like scanners or printers and was used to "tweak" NVidia and ATI Drivers many years ago.
Anyway, manually doing it would be how I do it if need be... Maybe worth a shot.
(and I wouldn't count too much on manufacturer support, they usually lock features out for a reason due to marketing decisions - which normally aren't in the best interests for the customer ;) )
In short, if the hardware is compatible, Windows should accept any driver manually
Yes, but the thing here is that you're not battling Windows, but battling Dell. Dell has always had a thing built into their systems, that allows only Dell approved drivers to be loaded. Try anything else and it'll just be ignored or denied.
Dell wants to make it easy for its end-user. No need to think about compatibility, just install drivers and be done with it. Want to be the boss over your computer? Don't buy a Dell!
Thanks Richard, but that did
)
Thanks Richard, but that did not work either. I downloaded he zip file and followed the instructions to do a manual install. However I then got an error message telling me that my driver was already up to date and the installation did not proceed!
Well, I think I'm out of
)
Well, I think I'm out of ideas, then. Any further experiment - like removing the old driver and installing the new one 'clean' (which might be the obvious next step) - run the risk of leaving you with an unusable machine, and I can't advise that. Running Einstein on a GPU is cool, but not that important.
Thanks anyway Richard. I
)
Thanks anyway Richard. I agree uninstalling video driver is not something I would want to do so I will just keep crunching Collatz and keep an eye on he Dell driver web site for when a new one is available.
Your CPU & GPU are from the
)
Your CPU & GPU are from the Ivy Bridge generation and Richard's is a new Haswell, that's why he got the current driver installed. Knowing DELL he's probably never going to get an update, though.
I'd definitely ask DELL support for a current driver, specifically with OpenCL 1.02 support. If they decline I'd poke them a bit harder and demand to be actually be able to use the product they sold me. If that won't help.. well, there may not be much to do except never buying from them again.
For mobile nVidia chips the driver get "hacked" regularly, so people can update their PCs with the regular driver, instead of waiting for updates from the manufacturers which never appear anyway. That hack is simply adding the card's IDs to some ini file. Could be that this is available for Intel too.
MrS
Scanning for our furry friends since Jan 2002
Dell plus Intel : my
)
Dell plus Intel : my commiserations. I did crunch for E@H with one of them and when the driver requirements changed, I proceeded to much the same impasse. Took that unit off crunching.
[Aside : When developing with OpenGL, I found Intel's driver adherence to standards appalling. This lead me to coin the phrase 'lying driver' meaning that upon runtime inquiry ( under Windows ) of the driver, a certain OpenGL version would be claimed. However upon further inquiry ( to obtain the function entry points ) many calls were simply not available that should have been as per the stated version! Of the very many machines I could lay my hands on to test ( bar one with an obtuse card maker ) only Intel graphics on Dells had this problem. So what's with that ? ]
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
So it sounds like Dell would
)
So it sounds like Dell would indeed cut some transistors off their Intel GPUs to make them incompatible with OpenGL and regular drivers. Hurray! :p
It must be expensive to treat all those CPUs. And they probably put huge efforts into not damaging other parts of the chips while sabotaging the GPUs..
MrS
Scanning for our furry friends since Jan 2002
RE: So it sounds like Dell
)
Well, in over about 60 machines, I didn't find any problems with Intel graphics outside of Dell laptops to be exact. As I didn't know anyone with a Dell desktop box, I can't speak of them.
IIRC the OpenGL functionality claimed, but then denied, was related to server-side ( ie. typically implemented on the graphics card ) memory stuff like buffer objects etc. So that suggests a design choice related to memory, but IIRC some of them have a shared memory arrangement between GPU and CPU ? Something like that. So maybe the Intel driver wasn't written for such sharing - and why would it be - so maybe Dell couldn't/wouldn't be bothered to factorise that and Intel didn't want to rewrite the driver ( as that wasn't in the supply deal ). Easier to just block/not-expose certain software functions, 'on the quiet' so to speak. But I speculate excessively here .... :-)
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Isn't possible to manually
)
Isn't possible to manually force a Driver onto the System ?
I used that technique to get a Vista64 System to accept a Trinity AMD APU Driver for a more modern but compatible Richland AMD APU. Dirty workaround, but so far it works for lots of hardware-compatible but DEVICE_ID-incompatible devices.
In short, if the hardware is compatible, Windows should accept any driver manually selected from an existing Driver package via the Device Manager.
The only small hassle is to locate the .inf File for the proper OS in the Driver package, otherwise Windows naturally won't install it (either look into its unpack location which usually remains in place or use a tool like 7Zip to manually extract the entire package onto HD)
For all I know, that is basically what driver "hacks" do (albeit in a more user-friendly, elegant manner), they include the proper lines for unlisted DEVICE_IDs in the Driver .inf file that they know are hardware compatible (so called .inf hack, that with sufficient time/experience isn't actually very difficuly to do - if you know exactly what you're doing that is).
That technique dates way back into 3dfx times and continued to work through Notebook drivers, Peripherials like scanners or printers and was used to "tweak" NVidia and ATI Drivers many years ago.
Anyway, manually doing it would be how I do it if need be... Maybe worth a shot.
(and I wouldn't count too much on manufacturer support, they usually lock features out for a reason due to marketing decisions - which normally aren't in the best interests for the customer ;) )
To make explicit my other
)
To make explicit my other assumption here : if Dell/Intel can't be bothered with OpenGL driver compliance then maybe the same applies for OpenCL.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: In short, if the
)
Yes, but the thing here is that you're not battling Windows, but battling Dell. Dell has always had a thing built into their systems, that allows only Dell approved drivers to be loaded. Try anything else and it'll just be ignored or denied.
Dell wants to make it easy for its end-user. No need to think about compatibility, just install drivers and be done with it. Want to be the boss over your computer? Don't buy a Dell!