Pages:
Author

Topic: Connection problems. (Read 2166 times)

hero member
Activity: 770
Merit: 502
August 27, 2011, 12:12:14 AM
#23
I guess whatever it was, worked itself out. :S Mining away for about 12 hours straight, without a hiccup.
hero member
Activity: 770
Merit: 502
August 26, 2011, 10:40:12 AM
#22
Sounds like you're fine outside of slush I suggest asking on their main thread or pming the pool operator for assistance.

Will do, reason I left deepbit, on deepbit if I nail down say like a 17min block, I receive 0.00528057, If I nailed down something similar to the time limit, well take a look

Slush's
Code:
7588 2011-08-26 07:02:48 0:34:28 832816 0.01892028

Deepbit
Code:
25.08 17:34:38 0h 32m 162 2525767  0.00311074

Odd ain't it? This is why I left deepbit, I feel I am not receiving the shares I've earned.

Edit:
Not shares but BTC.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
August 26, 2011, 10:31:10 AM
#21
Sounds like you're fine outside of slush I suggest asking on their main thread or pming the pool operator for assistance.
hero member
Activity: 770
Merit: 502
August 26, 2011, 10:20:16 AM
#20
I removed CCC 11.6, installed 11.8.
Went back to Slush's.
Mined all night, from 9PM to sometime this morning too, I am guessing 8 am, or so, cannot really tell yet, "Processing..." on two blocks. But when I came to the pc, you know how a caution yellow street light blinks , well, card 1 would blink connection problems, then mine, then card 2 would take the connection problems place, back and forth, each card would take turns having connection problems.
I stopped both miners and started them, they have since, been mining just fine in front of my eyes. I've taken the OC off of them both at 9pm last night to see how they would do.

I don't know what to think anymore. It's got me so rotted atm.

Edit:
I've installed 11.8 to see if it had anything to do with the dummy plug, so, I've got the dummy plug removed. That eliminates that variable.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
August 25, 2011, 03:17:02 PM
#19
That is a likely cause.
hero member
Activity: 770
Merit: 502
August 25, 2011, 03:03:11 PM
#18
Well, I ran out and trimmed my lawn, knock an hour off, seems to be ok, but last time i said seems to be ok, it shot me the error. If it happens again, i'll post back.

Wonder if it had to do something with my machine and slush's pool?

what PSU are you running?

http://www.pcpower.com/power-supply/silencer-750-quad-black.html

Edit:
Dunno if that had to do with any of it, slush just posted about migration.

https://bitcointalksearch.org/topic/m.480310

Edit 2:

Hmm, I just took a peak at what address the new "v2001-08-24" guiminer was using for slush's, it was set with http://api2.bitcoin.cz
I just changed both miners "card 1 and 2" for slush's address too api2.bitcoin.cz and it connected. My head is spinning.

edit 3:
Immediately, connection problems with my machine and slush's after I appointed the miners to api2.bitcoin.cz. There is no problem with deepbit atm at all, guess I am sticking with deepbit now.

hero member
Activity: 956
Merit: 1001
August 25, 2011, 02:55:20 PM
#17
what PSU are you running?
hero member
Activity: 770
Merit: 502
August 25, 2011, 01:47:38 PM
#16
No poclbm seems more stable. Try another pool for am hour as a sanity check (deep would be good)

My thoughts as well. Had the account already made, just created two miners. On starting the xfx 5830, it paused for one second on connection problems then connected, the sapphire connected right away.

Edit:
There are so many variables, new card, new driver & sdk, new guiminer, dummy plug.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
August 25, 2011, 01:43:05 PM
#15
No poclbm seems more stable. Try another pool for am hour as a sanity check (deep would be good)
hero member
Activity: 770
Merit: 502
August 25, 2011, 01:40:17 PM
#14
You didn't switch to Phoenix did you? Odds are against the CPU being an issue I have a athlon 64 that keeps up with a multi card configuration.

m nope, I haven't, think I should jump on the phoenix then? atm I am on the opencl.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
August 25, 2011, 01:34:35 PM
#13
You didn't switch to Phoenix did you? Odds are against the CPU being an issue I have a athlon 64 that keeps up with a multi card configuration.
hero member
Activity: 770
Merit: 502
August 25, 2011, 01:25:10 PM
#12
Could it be the motherboard? Maybe using one core for utilization?
hero member
Activity: 770
Merit: 502
August 25, 2011, 01:23:40 PM
#11
lol, yea, i edited my post before you posted your suggestion.

I tried, I get the same results.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
August 25, 2011, 01:21:45 PM
#10
Try separating then into two workers.
hero member
Activity: 770
Merit: 502
August 25, 2011, 01:19:32 PM
#9
Ok that takes out a lot of variables. Are both cards on slush or are they different pools?

They both are on slush's. On one worker account.

Edit:

But I have tried two separate worker accounts and receive same results.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
August 25, 2011, 01:19:02 PM
#8
Ok that takes out a lot of variables. Are both cards on slush or are they different pools?
hero member
Activity: 770
Merit: 502
August 25, 2011, 01:17:07 PM
#7
Ethernet. cat6.

PC > 8 port switch hub > router > modem. None of this connection problem started until I got this second card in.
sr. member
Activity: 462
Merit: 250
It's all about the game, and how you play it
August 25, 2011, 01:07:19 PM
#6
Wired or  wireless?
hero member
Activity: 770
Merit: 502
August 25, 2011, 01:05:26 PM
#5
Its back.

Even without overclocks.

hero member
Activity: 770
Merit: 502
August 25, 2011, 11:13:28 AM
#4
Back off the clock a bit and give the memory a bump

done, I've dropped it from 1038c/300m to 1020c/300m . Seems like it is good now.

I would figure, guiminer would throw a hardware failure error if it was oc'd to high. Odd enough it stop sending connection problems after your suggestion.

Temps were good @ 1038c/300m connection problems
DispIO 68c
MemIO 74c
Shader 69

Temps now @ 1020c/300m connection problems gone
DispIO 66c
MemIO 72c
Shader 69c

Thanks deslok,  dunno why I didn't try lower clocks to see if that was the problem *facepalm*.

Pages:
Jump to: