I am trying to get folding at home gpu client working. The issue we are having now is that it detects the driver version and says it is not right, and it won't proceed. I've searched through the lines of a WINEDEBUG=+trace and I think the issue is:
0009:trace:d3d:init_driver_info OS version 5.1. 0009:trace:d3d_caps:init_driver_info Found card 10de:05e2 in driver DB. 0009:trace:d3d_caps:init_driver_info Reporting (fake) driver version 0x0006000f-0x000b21aa.
It could also be from: 0009:trace:reg:NtSetValueKey (0x14,L"Driver",1,0xff883b94,20) 0009: set_key_value( hkey=0014, type=1, namelen=12, name=L"Driver", data={57,00,49,00,4e,00,45,00,20,00,53,00,43,00,53,00,49,00,00,00} )
But I think that is just trying to set a registry key, not get a registry key (i.e. the driver version from the registry).
What I can't figure out is what version this is reporting. I've searched but I can't find this driver DB, so I don't know what 0x0006000f-0x000b21aa corespondent too. Can someone point me in the right directions?
Thanks,
Seth Shelnutt
On Wed, 2 Jun 2010 03:14:34 +0000, Seth Shelnutt shelnutt2@gmail.com wrote:
I am trying to get folding at home gpu client working. The issue we are having now is that it detects the driver version and says it is not right, and it won't proceed. I've searched through the lines of a WINEDEBUG=+trace and I think the issue is:
0009:trace:d3d:init_driver_info OS version 5.1. 0009:trace:d3d_caps:init_driver_info Found card 10de:05e2 in driver DB. 0009:trace:d3d_caps:init_driver_info Reporting (fake) driver version 0x0006000f-0x000b21aa.
It could also be from: 0009:trace:reg:NtSetValueKey (0x14,L"Driver",1,0xff883b94,20) 0009: set_key_value( hkey=0014, type=1, namelen=12, name=L"Driver", data={57,00,49,00,4e,00,45,00,20,00,53,00,43,00,53,00,49,00,00,00} )
But I think that is just trying to set a registry key, not get a
registry
key (i.e. the driver version from the registry).
What I can't figure out is what version this is reporting. I've searched but I can't find this driver DB, so I don't know what 0x0006000f-0x000b21aa corespondent too. Can someone point me in the
right
directions?
Thanks,
Seth Shelnutt
It's a table at: http://source.winehq.org/source/dlls/wined3d/directx.c#L983
-Albert
On Wed, Jun 2, 2010 at 5:20 AM, Albert Lee trisk@forkgnu.org wrote:
On Wed, 2 Jun 2010 03:14:34 +0000, Seth Shelnutt shelnutt2@gmail.com wrote:
I am trying to get folding at home gpu client working. The issue we are having now is that it detects the driver version and says it is not right, and it won't proceed. I've searched through the lines of a WINEDEBUG=+trace and I think the issue is:
0009:trace:d3d:init_driver_info OS version 5.1. 0009:trace:d3d_caps:init_driver_info Found card 10de:05e2 in driver DB. 0009:trace:d3d_caps:init_driver_info Reporting (fake) driver version 0x0006000f-0x000b21aa.
It could also be from: 0009:trace:reg:NtSetValueKey (0x14,L"Driver",1,0xff883b94,20) 0009: set_key_value( hkey=0014, type=1, namelen=12, name=L"Driver", data={57,00,49,00,4e,00,45,00,20,00,53,00,43,00,53,00,49,00,00,00} )
But I think that is just trying to set a registry key, not get a
registry
key (i.e. the driver version from the registry).
What I can't figure out is what version this is reporting. I've searched but I can't find this driver DB, so I don't know what 0x0006000f-0x000b21aa corespondent too. Can someone point me in the
right
directions?
Thanks,
Seth Shelnutt
It's a table at: http://source.winehq.org/source/dlls/wined3d/directx.c#L983
Sure the code is in directx.c but the I suspect the issue Seth is seeing is that different parts of Wine expose different version numbers. Some games also have this issue (I believe they use some user32 code which just returns the display driver name reported by winex11.drv which is different from what wined3d mentions). It can be that real windows also stores it somewhere in the registry which we don't.
Roderick
Is there any reason that across all files we don't report the same driver version? Does windows not do this? Maybe it'd be easier to keep the code in wined3d and just have user32 and such call for the driver details? I haven't looked at how windows does it yet, but I'm just wondering if you guys have any idea of the top of you head.
Thanks,
Seth Shelnutt
On Wed, Jun 2, 2010 at 8:06 AM, Roderick Colenbrander < thunderbird2k@gmail.com> wrote:
Sure the code is in directx.c but the I suspect the issue Seth is seeing is that different parts of Wine expose different version numbers. Some games also have this issue (I believe they use some user32 code which just returns the display driver name reported by winex11.drv which is different from what wined3d mentions). It can be that real windows also stores it somewhere in the registry which we don't.
Roderick
On Wed, Jun 2, 2010 at 5:03 PM, Seth Shelnutt shelnutt2@gmail.com wrote:
Is there any reason that across all files we don't report the same driver version? Does windows not do this? Maybe it'd be easier to keep the code in wined3d and just have user32 and such call for the driver details? I haven't looked at how windows does it yet, but I'm just wondering if you guys have any idea of the top of you head.
We should behave the same way as Windows and also work as similar as possible. Calling wined3d from user32 is not the right way. In the end we likely have to move all the gpu detection stuff to winex11.drv and somehow let wined3d retrieve the info from there. Other sources like user32 (and perhaps registry keys) should also use this info.
Roderick
-
Albert Lee -
Roderick Colenbrander -
Seth Shelnutt