I've been trying to get about $500 I had at Mt.GOX now since May.  First it was the 'DWOLLA' problem... that never got fixed.  Then it was 'we changed banking methods'.  Then it was for 5% we'll do a 'manual withdrawl' that'll take 7-10 business days.  That was September 10th.  It's now October 1st.  I think I've been patient enough to not scream RIP OFF.

 Thanx for the info.

For small amounts of btc (1~5btc) how else can I turn that into USD?  I've always xfer'd the btc to mtGOX, sold it there and xfer'd it to DWOLLA and from DWOLLA to my US bank.  Looking for something a bit faster than what that has become.

I submitted a USD transfer from mtGOX at 00:45 on June 28th to my VERIFIED DWolla account.  It still has not shown up at DWOLLA.  Dwolla says it's not be sent to them.  mtGOX says:

We sincerely regret for the inconvenience. We are currently experiencing delays with Dwolla transactions and we apologize for the delay in this progress. Dwolla changed their terms of service and they do not want to deal with virtual currency anymore but they did not terminate their relations with us but there is no way to guarantee that, so we requested for a written consent from Dwolla which allow us to continue to use them, but till today we have not received any reply from Dwolla regarding this concern. So, until we we receive a clear statement from Dwolla we do not want to keep to much money with them and that is why dwolla withdrawals are processing slowly . We will keep you updated once the funds are processed. Please let us know if you wish to cancel this transaction and withdraw by other methods.

The way I read it mtGOX is creating an artificial slowdown and is just spoon feeding to DWOLLA.

I guess I should look at some other way of getting my mitts on my USD.

Actually I think I did.  As soon as I get a chance I'll go redo it again.

I uninstalled 11.2, installed 12.3, installed the 3/11 DM and gives me the original Java error I posted originally.  Back to the Jan 23rd DM and 11.2 for now.  I have the error file if you want it.

Trial & Error to find "the right one"?

Is there a way to get rid of one of the SDKs instead?

Would this be an "ATI" and an "AMD" one someplace?

I used the Catalyst 11.2 .run and have diablo running again however it "Added Cypress (#x)" with x being 1 thru 4 of 14 CU each.  there are 2 HD5830s in this machine.  I've never seen this before.  The driver installed was ati-driver-installer-11-2-x86.x86_64.run that I restored from a backup.  

If I don't use the .run scripts from AMD/ATI then I'm not sure how to install the proprietary drivers.  However it's mining and at a touch over 553 which is where this machine has always been.

My /etc/X11/Xorg.conf file is as it's always been since 6 of 2011 so it didn't add devices 3 & 4.  

PS:   Diablo that is running now has a .jar file dated Jan 23rd of this year.  I tried the 11 March one with same results but it is reporting around 537 mhash

Next idiot who broke his miner after months of no problems...

I updated to Catalyst 12-3, and 3/11/12 version of the miner.  Reverted back to Catalyst 12-2 but no help.  Thinking I forgot to reinstall something maybe... Xubuntu 64b.  ati-opencl-runtime_2.1_amd64.deb maybe?

PS:  I had been running 11.2 drivers
PPS:  It's something to do with drivers... AMDOverdriveCtl isn't reading fan, temp or much of anything.  Card is a HD5830.  Think I'll try to go back to an 11.2 driver.

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f01af3f7139, pid=2274, tid=139645544691456
#
# JRE version: 6.0_26-b03
# Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C  [libaticaldd.so+0x15e139]  __isnanf+0x15e139
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

---------------  T H R E A D  ---------------

Current thread (0x00000000404c6800):  JavaThread "main" [_thread_in_native, id=2279, stack(0x00007f01c305f000,0x00007f01c3160000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000dd4

Registers:
RAX=0x0000000000000000, RBX=0x00007f01b8290bd0, RCX=0x00007f01c40d1007, RDX=0x00007f01b8000078
RSP=0x00007f01c315bb70, RBP=0x00007f01c315d530, RSI=0x00007f01c315bec0, RDI=0x00007f01b8290bd0
R8 =0x00007f01b8293720, R9 =0x00007f01c3e7cff0, R10=0x00007f01c3e80e58, R11=0x0000000000000206
R12=0x00007f01c315bec0, R13=0x00007f01b8290bd0, R14=0x00007f01c315bec0, R15=0x00007f01b828f3f8
RIP=0x00007f01af3f7139, EFLAGS=0x0000000000010202, CSGSFS=0x0000000000000033, ERR=0x0000000000000004
  TRAPNO=0x000000000000000e

Deepbit Admins:  Can news list on left side of account page be updated to show the most recent difficulty increase?  Still shows 7/7/2011.
Thanx, Skip

How 'bout just downclocking it via aticonfig --odsc=gpu,mem
or for a wider range (often) use AMDOverdriveCtl.

  Yea, go borrow the code from Hashkill ;-)

I have one mobo that does this with it's 2 x 5830's.  One boot only card 2 and only video on card 2 (even boot up bios screen).  One or two reboots and video moves to card 1 where it should be and Diablo can then use both cards.  Seems that something gets messed up on a soft reset.  Power off for 3 mins and it always comes up right.

I have another very similar machine, same OS, same drivers, same config files, both i7-87x 1156 sockets, different mobos and it never does this.  The one that gives me the problem is a MSI H55-GD65 (H55) the one that doesn't is a BioStar T5 XE (P55) mobo.

Sent you PM with my IP and userid.

Lost connection to central about 3:30am and still couldn't connect at noon today (CDT).  I can't tell the reason as I can ping central up in Dallas from down here in Austin.  1 machine connected to east didn't have any problems.   I've moved the others to east for now.

Slept in today so didn't catch this for about 8 hours :-(

Skip

UPDATE:  9pm CDT, still no connections to central server but east working fine.

Just like I told my tek team the other day... "I need you guys to come up with a list of all unknown issues and prioritize them immediately."  They figured out (after a bit) that I was BS'ing 'em to make a point to the big dogs.  Unfortunately I think my bosses boss like the idea :-(

Skip

About 3:30am CDT all my miners when belly up except 1.  The triggering event was something between me and btcguild's central server.  The reason one remained up was it was connected to the east server.  Anyway, here's best I could pen and paper copy from the ones that went down.... all the same major message.

what came after that varied a bit from nothing to

either
at java.util.Formatter.parse(Formatter.java:2480)
at java.util.Formatter.parse(Formatter.java:2414)
at java.util.Formatter.parse(Formatter.java:2367)

or it referred to Getwork Parser.

I suspect this was triggered by the long not able to connect to btcguild central but I suppose it could be coincidental.

Installed the version with the .jar file dated 7/2/11 yesterday around 8pm CDT

PS:  btw, they were disconnected from central for about 8 hours because I decided to sleep in today :-(

Ditto

from my desktop...

skip@c17-desktop:~$ traceroute uscentral.btcguild.com
traceroute to uscentral.btcguild.com (69.147.241.114), 30 hops max, 60 byte packets
  
 4  Gi0-2-4-0.austtxrdcsc-rtr2.austin.rr.com (24.27.13.38)  20.863 ms  25.198 ms  25.361 ms
 5  agg20.austtxa-cr01.texas.rr.com (66.68.2.236)  34.327 ms  34.966 ms  35.115 ms
 6  te0-12-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.56)  44.035 ms  21.949 ms  19.852 ms
 7  ae-4-0.cr0.dfw10.tbone.rr.com (66.109.6.88)  19.020 ms  21.198 ms  21.403 ms
 8  ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209)  25.402 ms ae-1-0.pr0.dfw10.tbone.rr.com (66.109.6.179)  25.553 ms  29.158 ms
 9  ip65-47-204-137.z204-47-65.customer.algx.net (65.47.204.137)  29.319 ms te1-2-0d0.cir1.dallas2-tx.us.xo.net (65.47.204.5)  34.630 ms ip65-47-204-105.z204-47-65.customer.algx.net (65.47.204.105)  62.978 ms
10  207.88.15.46.ptr.us.xo.net (207.88.15.46)  33.945 ms  34.108 ms  38.790 ms
11  65.106.4.234.ptr.us.xo.net (65.106.4.234)  39.003 ms  43.816 ms  43.444 ms
12  edge1.dal.ubiquityservers.com (207.88.185.110)  24.686 ms  16.657 ms  25.423 ms
13  69.147.241.114.rdns.ubiquityservers.com (69.147.241.114)  19.190 ms  23.139 ms  23.294 ms

Lemme go hook a miner back to it.

EDIT: Strange.  Miner(Diablo) still not connecting to it but connects to deep and east.  Dang thing is practically next door isn't it?  Maybe I should just run some cat6 to it.

a few min later:

4  Gi0-2-4-0.austtxrdcsc-rtr2.austin.rr.com (24.27.13.38)  23.987 ms  24.148 ms  26.744 ms
 5  agg20.austtxa-cr01.texas.rr.com (66.68.2.236)  29.486 ms  40.763 ms  40.927 ms
 6  te0-12-0-2.dllatxl3-cr01.texas.rr.com (72.179.205.56)  40.567 ms  23.721 ms  25.457 ms
 7  ae-4-0.cr0.dfw10.tbone.rr.com (66.109.6.88)  18.275 ms  22.275 ms  26.334 ms
 8  ae-3-0.pr0.dfw10.tbone.rr.com (66.109.6.209)  26.508 ms  30.784 ms  30.942 ms
 9  ge5-0-2d0.cir1.dallas2-tx.us.xo.net (65.47.204.29)  31.101 ms ip65-47-204-105.z204-47-65.customer.algx.net (65.47.204.105)  35.063 ms ip65-47-204-141.z204-47-65.customer.algx.net (65.47.204.141)  35.234 ms
10  207.88.15.46.ptr.us.xo.net (207.88.15.46)  35.396 ms  38.586 ms  38.742 ms
11  65.106.4.234.ptr.us.xo.net (65.106.4.234)  42.684 ms  42.848 ms  42.993 ms
12  edge1.dal.ubiquityservers.com (207.88.185.110)  28.384 ms  39.366 ms  13.234 ms
13  69.147.241.114.rdns.ubiquityservers.com (69.147.241.114)  13.336 ms  17.540 ms  23.253 ms

ping summary...

--- uscentral.btcguild.com ping statistics ---
39 packets transmitted, 30 received, 23% packet loss, time 38070ms
rtt min/avg/max/mdev = 18.410/25.881/41.100/5.130 ms

went from 37% loss to 23% to now 4%...

64 bytes from 69.147.241.114.rdns.ubiquityservers.com (69.147.241.114): icmp_req=50 ttl=52 time=15.9 ms
^C
--- uscentral.btcguild.com ping statistics ---
50 packets transmitted, 48 received, 4% packet loss, time 49101ms
rtt min/avg/max/mdev = 12.755/15.516/28.078/2.900 ms


BTW, these are from a machine that is 1 switch closer to the router than all the miners are except 1 which is on the same switch as this machine.

lost route to uscentral server about 2 hours ago... just outside of Austin, TX here.

Just installed the one with June 27th .jar file on the machines out in the 'server oven'.
Great stuff!  Pretty much got +10 MegaHootzels per card.

Mostly running #! Linux AMD64, drivers v11.2 / 11.3, OpenCL 2.1, BOINC running 100% on all CPU cores/threads:

1x5850@775/875 went from 304 to 314   
2x5830x@875/900 went from 533 to 553
1x5830@875/900 went from 266 to 276
6970@885/800 + 6870@995/910 went from 670 to 694.  driver v11.6, OpenCL 2.4.

Curious... haven't seen a compare between HashKill and the Diablo miner here.