Closed GoogleCodeExporter closed 9 years ago
The NVS 135M is just too slow. The call by Pyrit is interrupted by X to prevent
the
screen from locking up completely. There is no solution :-)
Please see the FAQ regarding the number of cores.
Original comment by lukas.l...@gmail.com
on 6 Apr 2010 at 5:09
OK I checked FAQ ;) Thanks!
Is it really that slow? It runs with 1400PMK/s for a onboard card still fast in
TTY
;)
So it is too slow to handle both X and Pyrit and the X-Server does recognize
this?!
I did not know that XServer ist that intelligent ;)
Might there be any workaround?
Thanks for the fast answer ;)
Best regards,
Flow
Original comment by flow.off...@googlemail.com
on 7 Apr 2010 at 12:23
its actually not the X server but the driver itself. The driver detects the
running
X-Server and enforces a five-second-timeout.
You can edit cpyrit/cpyrit.py, modify the line "self.buffersize = 4096" in
CUDACore.__init__ and set it to a lower value (e.g. 2048)
Original comment by lukas.l...@gmail.com
on 7 Apr 2010 at 4:59
are you really getting 1400 PMK/s with that card?
i have that card and im not even getting a quarter of that amount...similiar
spec cpu
as well
Original comment by psychona...@gmail.com
on 24 Apr 2010 at 7:20
Original issue reported on code.google.com by
flow.off...@googlemail.com
on 6 Apr 2010 at 4:52