Hi Andreas, They are one and the same and it was the same card at both times. Any other ideas?
Ray On Sun, Dec 27, 2009 at 5:19 PM, Andreas Klöckner <[email protected]>wrote: > On Donnerstag 24 Dezember 2009, Raymond Tay wrote: > > another comparison by running the CUDA 2.3 SDK samples deviceQueryDrv > > (which used *cuDeviceGetAttribute *and looked for > > *CU_DEVICE_ATTRIBUTE_CLOCK_RATE*) and that ran fine.... > > > > I don't know why its failing for CLOCK_RATE in PyCuda, anyone has ideas? > > This is truly strange. Have you checked (using "otool -L") if they both > link > against the same CUDA library? That's the only explanation that makes sense > to > me. Were you querying the same card both times? > > Andreas > > _______________________________________________ > PyCUDA mailing list > [email protected] > http://tiker.net/mailman/listinfo/pycuda_tiker.net > >
_______________________________________________ PyCUDA mailing list [email protected] http://tiker.net/mailman/listinfo/pycuda_tiker.net
