• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Linux VM A3s

Intelman34

Limp Gawd
Joined
Mar 5, 2003
Messages
467
Has anyone else had their VM -bigadv machines start pulling A3 units?

My log shows the last bigadv unit I pulled could be sent (could not transmit to collection server) and eventually it downloaded the new core and started rolling with that.
 
I was getting nothing but A3's, but at the time I was experimenting with SMP7 vs SMP8 (this was a couple of days ago). As long as I had SMP7 set, I was getting A3's. As soon as I went back to SMP8, I got a Big WU.
 
I was getting nothing but A3's, but at the time I was experimenting with SMP7 vs SMP8 (this was a couple of days ago). As long as I had SMP7 set, I was getting A3's. As soon as I went back to SMP8, I got a Big WU.
That's interesting. First time I heard this occurring. Now that SMP2 is available and it has its own bonus scheme, Stanford might see a need to differentiate between its different SMP WUs, and maybe enforcing a minimum of 8 threads to run -bigadv now.
 
Mine finished a -bigadv this morning (roughly 4 hours ago), I checked the client through logmein like always and was shocked stupid to see it say the new unit was 73% done....*then* I realized it was a GRO-A3 so obviously you can add me to the list of *nix VM's grabbing an A3. Oh well, could be worse...could be an A1. [gulp] Hope I didn't just jinx myself... :eek:

Using linuxrouter's VM, my flag is the default ./fah6 -bigadv -smp 8 so it's not just something for clients running the -smp 7 flag. :(
 
Using linuxrouter's VM, my flag is the default ./fah6 -bigadv -smp 8 so it's not just something for clients running the -smp 7 flag. :(
Then they were probably out of -bigadv WUs. Recently, when that happened they either sent A1 or A2 WUs, so I guess this time they are sending A3s.
 
Not only did mine grab an a3 but my last bigadv unit wont send :(
 
No problems with Nexus.

If it is the flags, -smp 16 probably means I'm safe.
 
On my 3rd bigadv unit now, if the timing is right I'll switch over to the Linux disk after the next one finishes and that should help, seeing almost 33 min TPFs, should get around 32 with the native Linux

Havnt had anything else tho. When I was trying A3's I did get a bunch if A1s, but not since going big!
Posted via [H] Mobile Device
 
I just checked my logs and it did slide a 6021 WU through and I did have a problem sending a bigadv as well. Crud.
 
Just got a 6015 on my big adv rig, that should out me nearly 100k fir the day because they will all submit today
Posted via [H] Mobile Device
 
Back
Top