Bitcoin Forum
May 12, 2024, 05:46:34 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: CCMINER tpruvot cuda8 branch on nvda 367.57 Cuda error in func 'neoscrypt_hash_k  (Read 1107 times)
aurigae (OP)
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile WWW
November 07, 2016, 12:55:20 AM
Last edit: November 07, 2016, 01:10:58 AM by aurigae
 #1

CCMINER tpruvot cuda8 branch on nvda 367.57 Cuda error in func 'neoscrypt_hash_k on xubuntu 16.10
The error occured after upgrading from the previous nvda prop driver.

Rebuild error:

1. Default installation of Xubuntu 16.10
2. install nvidia prop driver 367.57
3. Clone and compile CCminer tpruvot cuda 8 branch with gcc 4.8 (http://askubuntu.com/questions/724872/downgrade-gcc-from-5-2-1-to-4-9-ubuntu-15-10) and the Cflags / symlinks for the prop driver https://github.com/tpruvot/ccminer/blob/linux/INSTALL.
4. run ./build.sh from the git repository directory
5. Run ./ccminer -a neoscrypt

Code:
[2016-11-07 01:52:42] Starting on stratum+tcp://MININGPOOLADDRESS:PORT
[2016-11-07 01:52:42] NVML GPU monitoring enabled.
[2016-11-07 01:52:42] 1 miner thread started, using 'neoscrypt' algorithm.
[2016-11-07 01:52:42] Stratum difficulty set to 256
[2016-11-07 01:52:43] GPU #0: Using x cuda threads
Cuda error in func 'neoscrypt_hash_k4' at line 1517 : misaligned address.


Any idea how to fix that without downgrading to the previous nvda driver?

¯\_(ツ)_/¯
1715535994
Hero Member
*
Offline Offline

Posts: 1715535994

View Profile Personal Message (Offline)

Ignore
1715535994
Reply with quote  #2

1715535994
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715535994
Hero Member
*
Offline Offline

Posts: 1715535994

View Profile Personal Message (Offline)

Ignore
1715535994
Reply with quote  #2

1715535994
Report to moderator
aurigae (OP)
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile WWW
November 07, 2016, 02:12:41 AM
 #2

This is wired, error remains after downgrading back to 367.48 where it previously did work.

¯\_(ツ)_/¯
aurigae (OP)
Member
**
Offline Offline

Activity: 112
Merit: 10


View Profile WWW
November 07, 2016, 02:31:04 AM
 #3

Wrong algo mined - if you receive this error check the -a option or port ....

explain: CUDA_SAFE_CALL(cudaMemcpy(resNonces, d_NNonce[thr_id], 2 * sizeof(uint32_t), cudaMemcpyDeviceToHost));
reference was correct so i had to assume i made a mistake....

CLOSED

¯\_(ツ)_/¯
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!