ggnfs not working

sega24 · 2016-03-02, 20:30

everything was okey before i change pc, after changes not working :/
i will start from begin

hi :)
3 years ago when i start fun with factorise, everything was okey
amd x4 cores winx64 gtx660
now, i buy new cpu amd x8 cores, new hdd and new gtx660tioc
and im still ... beginner :/
i cannot run it and i dont know why, what is missed

at the begining i install vs2015, but when i run python script i see "is cuda enabled?"
so...i install new nvidia card driver, vs2013, developers drivers for cuda/nvidia, toolkit7.5 where is nsight inside etc
and now... script running but i always to check is everything okey, take those 100digits from beginners guide
as i good remember, 3 years ago it takes me 1,5 hour ?
dont remember :/
but now i left my new pc for night, he work 10 hours and no results
also script show me like that.."0 gpu cores(gtx660ti) cuda arch. 3.0"

why 0 cores from gpu shows script?
what is missed ? dll or driver ?
maybe vs take lower like 2012 or 2010 ?
this method is still best for 154digits and higher ?
ggnfs+msieve

please help me :)
i was trying to find some answers but...nothing

pls

btw my new pc looks:

win7 x64
amd x8 oc to 4.2
x3 gtx 660ti oc - 3way sli
32gb memory

VBCurtis · 2016-03-02, 21:45

What version of msieve? Have you read the readme from msieve to see if your version supports the GPU code?

Have you learned what the various flags of msieve are used for, to determine which particular step is causing the problems?

The script's job is to call other programs at appropriate times. The script works, but the individual programs may not.

sega24 · 2016-03-07, 23:08

ggnfs-svn374-win64-opteron
msieve152_svn942_win64_cuda

from logs
...
using GPU 0 (GeForce GTX 660 Ti)
selected card has CUDA arch 3.0

i think 3 years ago i have the same files, so i think other parts are missed :/
yes i read readme from msieve, nothing about cuda, or i missed ? :/

VBCurtis · 2016-03-07, 23:35

You have twice mentioned the output of the log file, but you haven't told us what command you are issuing to msieve to produce this output. If we don't know what you are asking msieve to do, we have no way to tell you what might be happening.

What exact command are you issuing? You said "when I run the script"; I am not aware of a script that takes advantage of GPU-enabled msieve. Did you edit the script? I may just be unaware that the python script will invoke msieve in a way that uses GPU, but I haven't seen it.

If you're just running the python script, try using msieve directly to find a polynomial, then run the script with the polynomial in place (in the same folder as the rest of the exe's, with the name changed to _projectname_.fb from msieve.fb.

2016-03-02, 20:30	#1
sega24 May 2013 8₁₆ Posts	ggnfs not working everything was okey before i change pc, after changes not working :/ i will start from begin hi :) 3 years ago when i start fun with factorise, everything was okey amd x4 cores winx64 gtx660 now, i buy new cpu amd x8 cores, new hdd and new gtx660tioc and im still ... beginner :/ i cannot run it and i dont know why, what is missed at the begining i install vs2015, but when i run python script i see "is cuda enabled?" so...i install new nvidia card driver, vs2013, developers drivers for cuda/nvidia, toolkit7.5 where is nsight inside etc and now... script running but i always to check is everything okey, take those 100digits from beginners guide as i good remember, 3 years ago it takes me 1,5 hour ? dont remember :/ but now i left my new pc for night, he work 10 hours and no results also script show me like that.."0 gpu cores(gtx660ti) cuda arch. 3.0" why 0 cores from gpu shows script? what is missed ? dll or driver ? maybe vs take lower like 2012 or 2010 ? this method is still best for 154digits and higher ? ggnfs+msieve please help me :) i was trying to find some answers but...nothing pls btw my new pc looks: win7 x64 amd x8 oc to 4.2 x3 gtx 660ti oc - 3way sli 32gb memory

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
CPU working 24/7	BaptisteTesson	Information & Answers	5	2016-08-26 15:41
Log Out not working?	cheesehead	Forum Feedback	1	2012-03-19 17:13
DST not working?	Dubslow	Forum Feedback	2	2012-03-19 06:53
How is working on 44M-45M ?	hbock	Lone Mersenne Hunters	0	2005-04-06 17:16
Working on 525 for P-1	delta_t	Marin's Mersenne-aries	15	2004-09-13 15:27

2016-03-02, 21:45	#2
VBCurtis "Curtis" Feb 2005 Riverside, CA 11375₈ Posts	What version of msieve? Have you read the readme from msieve to see if your version supports the GPU code? Have you learned what the various flags of msieve are used for, to determine which particular step is causing the problems? The script's job is to call other programs at appropriate times. The script works, but the individual programs may not.

2016-03-07, 23:08	#3
sega24 May 2013 2³ Posts	ggnfs-svn374-win64-opteron msieve152_svn942_win64_cuda from logs ... using GPU 0 (GeForce GTX 660 Ti) selected card has CUDA arch 3.0 i think 3 years ago i have the same files, so i think other parts are missed :/ yes i read readme from msieve, nothing about cuda, or i missed ? :/

2016-03-07, 23:35	#4
VBCurtis "Curtis" Feb 2005 Riverside, CA 4,861 Posts	You have twice mentioned the output of the log file, but you haven't told us what command you are issuing to msieve to produce this output. If we don't know what you are asking msieve to do, we have no way to tell you what might be happening. What exact command are you issuing? You said "when I run the script"; I am not aware of a script that takes advantage of GPU-enabled msieve. Did you edit the script? I may just be unaware that the python script will invoke msieve in a way that uses GPU, but I haven't seen it. If you're just running the python script, try using msieve directly to find a polynomial, then run the script with the polynomial in place (in the same folder as the rest of the exe's, with the name changed to _projectname_.fb from msieve.fb.