a1 core and just 3g??
Printable View
a1 core and just 3g??
make sure to put -advmethods in... they used to grab more a2's that way..
-advmethods is on afaik, let me check, Darnit nope not on, thought notfred's put them on by default.. Now, I can edit the cfg directly and restart the vm's but I got no idea if that holds.. brb
Well it is on, running reconfigure.html says it is.. I thought it wasn't because it's not listed in client.cfg
you'll have to RR's input on what they are throwing down the linux pipeline now, and with what flags... I haven't run linux smp since I reformatted my mepis folder to make room for the 9600gso in Sept... back then I was getting about 50/50 mix of a1 and a2's.. at first we had to use the "flag that shall not be named" to get a2's.. but then later on in the summer, -advmethods did the trick..
It's a mistry to me, the config page says it's on but the log file says diffrent. Or does the linux client only logs if it flag is not used hehe.. don't think so but tbh their running and even with this low output you say for linux I'm up from 4k normally to 6k according to fahmon. Though that's also because I dropped that no name flag for the gpu and am back on the smaller one's :)
Yeah well I also just booted the vm's and run them, but I see that my checkpoints aren't being written to hdd so I think I better not close the vm to try and play with init ( I read somewhere that's the file I could do the most with ).
angra, I've cut down your lead from XX years to...
1 Angra 227.34 days
Quote:
Originally Posted by MikeB12
I set mine to advmethods in the advanced config, I had read awhile back that was what to do to acquire A2s :shrug:
Argh, one of my smp clients died. Came home and it was stuck. I closed it and tried it again and it just kept erroring out. Anyone know what this is:
Had to delete the whole work folder, queue.dat, and unitinfo.txt before it would start working again. Lost all my work on it.Code:[18:57:42] Completed 2250000 out of 5000000 steps (45 percent)
[19:12:19] Warning: long 1-4 interactions
[19:12:19] Gromacs cannot continue further.
[19:12:19] Going to send back what have done.
[19:12:19] logfile size: 0
[19:12:19] Warning: Core could not open logfile.
[19:12:19] - Writing 536 bytes of core data to disk...
[19:12:19] ... Done.
[19:12:19] No C.P. to delete.
[19:12:19] - Failed to delete work/wudata_04.sas
[19:12:19] - Failed to delete work/wudata_04.goe
[19:12:19] Warning: check for stray files
[19:12:19]
[19:12:19] Folding@home Core Shutdown: EARLY_UNIT_END
[19:12:19]
[19:12:19] Folding@home Core Shutdown: EARLY_UNIT_END
[19:12:22] CoreStatus = 7B (123)
[19:12:22] Client-core communications error: ERROR 0x7b
[19:12:22] This is a sign of more serious problems, shutting down.
[21:20:52] - Autosending finished units... [November 9 21:20:52 UTC]
[21:20:52] Trying to send all finished work units
[21:20:52] + No unsent completed units remaining.
[21:20:52] - Autosend completed
[23:45:39] Killing all core threads
[23:45:39] Killing 3 cores
[23:45:39] Killing core 0
[23:45:39] Killing core 1
[23:45:39] Killing core 2
That sux so much when you lose a WU...
Well drat. Fold6, my 9600GSO, is down. PSU developed a few leaky caps. Cheap thing. I can fix it but my soldering iron and spare capacitors are back at home and I'm at school :rolleyes: It'll be about a week before I get it going again :(
One of these days I'll have real PSUs powering my stuff.
Long interactions can be caused by many things. Bad WU, unstable PC, lunar cycles, etc...Quote:
Originally Posted by catawalks
And yeah, it really hurts to lose SMP WUs. :(
I have had like a dozen of those Long interactions in the past and it seemed they were a bad WU for me, however an unstable machine could do it also..Quote:
Originally Posted by coo-coo-clocker
well, ive got less than half of my hardware up and running, and its still not running at spec. my gx2 is still only pumping out 5kppd :( i really have no idea whats going on .....
i thought this was going to be an easy and fun race to play with for a few weeks,
it has been anything but easy, definatly not fun. and i would not have minded the expense to much, except that none of my new hardware that i bought, most of it is just lying around :(
stuff like that happens. Sometimes take a lot of effort to get the final push for everything to come together.Quote:
Originally Posted by skycrane
But don't get upset over it. Just relax.... leave it hang around for a few more days and when the energy levels are, get at it again.
I think it's because the vm's are limited to dual core's and you need proper quad's for the a2 core. Maybe native linux os, with a windows vm to do my daily buisiness :poke:Quote:
Originally Posted by road-runner
Don't know my way around linux though, so I doubt I'll do it :rofl:
The most important leason from that is this one, you're frustated now, butQuote:
Originally Posted by skycrane
for each frustration you have now a stronger feeling of accomplishment will take it's place when you do get it going :up:
Now excuse me. I'm on diaper duty :sofa: ( hides from the smell ;) )
Just like riptide says, just try & fix 1 thing at a time. It will all come together.Quote:
Originally Posted by [XC] riptide
Oh, snap! :eek:
~ 10 MIL points in just a little over 2 weeks. :wtf:
I was not contributing to the XS through the weekend ..
+ From 13th I won't contribute [ Wrath of the Lich King release ] I'm sorry for that but It's a must ... :hehe:
I decided to take a couple of days off , our office is running out of pencils I can chew
yea maybe thats my problem right there... ive got 3 different monitors hooked up to 4 different comps, and im trying to do all 4 comps at once :)Quote:
Originally Posted by DAK1640
maybe im multitasking a bit to much :shocked:
and im definatly not liking vista on my main rig, im thinking of going back to xp on it and forgetting about the smp on the cpu...
Do as I did, load a vm with notfreds ( 2 intances, can only assign two cores per vm ) and it's fire and forget :up:Quote:
Originally Posted by skycrane
Is this the meter I want to buy ???
We seem to be holding team whoopass at bay...:up:
The 5748's are killing our team production though.