I've noticed that myself primarily with cgminer, that if cgminer crashes/exits the unit will sometime hang. We're looking into where that might be happening and hope to have a fix in for the next firmware release.
Thanks. If it helps, I noticed that killing bfgminer with "pkill -9 bfgminer" *seems* to cause this behavior more often than with "pkill bfgminer" which lets it exit a bit more gracefully. 
Topic: The Chili – 30+GH/s BFL based Bitcoin Miner Assembly - page 20. (Read 137904 times)
I've got like 3 or 4 cards that all of the sudden are showing 250GH/100% hardware errors?
I have them off now and will let them cool completely down before turning them back on.. But reading on here that some people solved this with firmware reflash's.
Do these cards get in situations where they need to be re-flashed? Or can a reboot always get them "back"
I am currently running the 14e flash that has the 1.1v limit.
What were those cards achieving before they went to 250GH/100%HW ?I have them off now and will let them cool completely down before turning them back on.. But reading on here that some people solved this with firmware reflash's.
Do these cards get in situations where they need to be re-flashed? Or can a reboot always get them "back"
I am currently running the 14e flash that has the 1.1v limit.
Mr Teal or anyone "in the know",
I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
and now a few minutes later when I started bfgminer again, it CAME BACK! It's never come back from a hangup before, so maybe that did it? Or was this just a fluke?
Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
I've noticed that myself primarily with cgminer, that if cgminer crashes/exits the unit will sometime hang. We're looking into where that might be happening and hope to have a fix in for the next firmware release. I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
Code:
echo "reset" >/dev/ttyUSB1
and now a few minutes later when I started bfgminer again, it CAME BACK! It's never come back from a hangup before, so maybe that did it? Or was this just a fluke?
Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
Question -
What is the max amperage provided by the 3 pin fan power ports on these? I've got a pretty hefty fan I'd like to point along the edge to keep the FETs stuff cool. It is however a 2A fan and I don't want to overdraw anything. Thanks!
The PFET is rated at -4.2A at 25C (-3.4A @ 70C) so you should be fine. It's had no problem running a Thermaltake Water 2.0 Extreme CLC that draws 20-30W, so I think you'll be fine. What is the max amperage provided by the 3 pin fan power ports on these? I've got a pretty hefty fan I'd like to point along the edge to keep the FETs stuff cool. It is however a 2A fan and I don't want to overdraw anything. Thanks!
Not really. I have a 4 chip board that I play with that is similarly limited, even if I only run 2 chips on it. It's more a function of the BFL chips being broken, the highest clock divisor doesn't work so you reach a maximum frequency setpoint and then can only vary the frequency using the voltage. There's a limit to how far you can push the voltage though.
Do you played with external clock injenction to the test clock pin? I mean I saw in documentation the internal clock can be overridden by setting external clock on this pin. Also it is described as an test pin.Cheers...
Not really. I have a 4 chip board that I play with that is similarly limited, even if I only run 2 chips on it. It's more a function of the BFL chips being broken, the highest clock divisor doesn't work so you reach a maximum frequency setpoint and then can only vary the frequency using the voltage. There's a limit to how far you can push the voltage though.
Do you played with external clock injenction to the test clock pin? I mean I saw in documentation the internal clock can be overridden by setting external clock on this pin. Also it is described as an test pin.Cheers...
Question -
What is the max amperage provided by the 3 pin fan power ports on these? I've got a pretty hefty fan I'd like to point along the edge to keep the FETs stuff cool. It is however a 2A fan and I don't want to overdraw anything. Thanks!
What is the max amperage provided by the 3 pin fan power ports on these? I've got a pretty hefty fan I'd like to point along the edge to keep the FETs stuff cool. It is however a 2A fan and I don't want to overdraw anything. Thanks!
So, in anticipation of that, what is the exact part number of the FTDI chip that I should order, and possibly from where? I do have a hot air station, so that part will be easy, but what temperature should I set it at so as not to melt the chip body?
Thanks in advance!
For chips with legs, I'd go with 400c for 30 seconds tippy tops. See how long it takes to get them off, then use a bit less than that to get the new one on.Thanks in advance!
You don't need anywhere near as long heat for the chips with legs.
Perfect - thanks! I actually just ordered that just in case, but good to know I was on the right track!
So, in anticipation of that, what is the exact part number of the FTDI chip that I should order, and possibly from where? I do have a hot air station, so that part will be easy, but what temperature should I set it at so as not to melt the chip body?
Thanks in advance!
For chips with legs, I'd go with 400c for 30 seconds tippy tops. See how long it takes to get them off, then use a bit less than that to get the new one on.Thanks in advance!
You don't need anywhere near as long heat for the chips with legs.
So, in anticipation of that, what is the exact part number of the FTDI chip that I should order, and possibly from where? I do have a hot air station, so that part will be easy, but what temperature should I set it at so as not to melt the chip body?
Thanks in advance!
For chips with legs, I'd go with 400c for 30 seconds tippy tops. See how long it takes to get them off, then use a bit less than that to get the new one on.Thanks in advance!
You don't need anywhere near as long heat for the chips with legs.
Thanks much! Part number?
So, in anticipation of that, what is the exact part number of the FTDI chip that I should order, and possibly from where? I do have a hot air station, so that part will be easy, but what temperature should I set it at so as not to melt the chip body?
Thanks in advance!
For chips with legs, I'd go with 400c for 30 seconds tippy tops. See how long it takes to get them off, then use a bit less than that to get the new one on.Thanks in advance!
You don't need anywhere near as long heat for the chips with legs.
i may just try and replace the ftdi chip
Before doing that, try shorting the center two pins on the unpopulated 0.1" connector labeled PROG. Pin 5 is MCU reset and pin 6 is ground, so it will hold the microcontroller in reset. If it's an MCU issue holding it in reset should cause the device to pop up on your computer as the FTDI chip will be able to connect. If it doesn't show up, it likely is the FTDI.
How did you do it on the Chili? And what is with those chips?
C
So, in anticipation of that, what is the exact part number of the FTDI chip that I should order, and possibly from where? I do have a hot air station, so that part will be easy, but what temperature should I set it at so as not to melt the chip body?
Thanks in advance!
where did you get your U1?
Mr Teal or anyone "in the know",
I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
I have also been wanting a solution to this very same problem although I have been restarting bfgminer less often lately. the only reason I am restarting now is if there is a a power faliure or something else like that. I have also wondered if there was a way of making the miners come up on the same /dev/xxxx every time they or the computer is rebooted.I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
Code:
echo "reset" >/dev/ttyUSB1
and now a few minutes later when I started bfgminer again, it CAME BACK! It's never come back from a hangup before, so maybe that did it? Or was this just a fluke?Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
+1
As for the same /dev/xxxx, I hava short line that just picks out the ones that have certain devices on them. For example, to pick out the antminer ones:
Code:
usb="1:"$(./antminer -n | grep -e ea60 | sort -k 8 | cut -d ' ' -f 7 | tr '\n' ',1:' | sed 's/,$/\n/g' | sed 's/,/,1:/g')
puts the the devs that antminer (cgminer modded for antminer U1s) recognizes that are indeed U1s in a format that the --usb switch can recognize. I set that up when I invoke antminer and that way whatever /dev/xxxx they are in I don't have to worry about and since I automatically tell it the right ones. Fun stuff!
Mr Teal or anyone "in the know",
I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
I have also been wanting a solution to this very same problem although I have been restarting bfgminer less often lately. the only reason I am restarting now is if there is a a power faliure or something else like that. I have also wondered if there was a way of making the miners come up on the same /dev/xxxx every time they or the computer is rebooted.I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
Code:
echo "reset" >/dev/ttyUSB1
and now a few minutes later when I started bfgminer again, it CAME BACK! It's never come back from a hangup before, so maybe that did it? Or was this just a fluke?Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
+1
Mr Teal or anyone "in the know",
I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
and now a few minutes later when I started bfgminer again, it CAME BACK! It's never come back from a hangup before, so maybe that did it? Or was this just a fluke?
Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
I start and stop my bfgminer quite a bit, but often one or the other of my Chilis doesn't come up again and I can't add it manually. I have to do a hard reset or power on/off to get it to reboot and get seen again. Restarting bfgminer or invoking it with --force-dev-init doesn't seem to do the trick.
My question is there any way I can force it to reset via a commandline so I don't have to wait until I get home from work or whatever? I know the devices are on /dev/ttyUSB0 or /dev/ttyUSB1 and when they're working, I can see some output if I cat them directly, but I get nothing if it's hung. Any ideas to force a reset remotely?
Hmm, on a whim I just did:
Code:
echo "reset" >/dev/ttyUSB1
and now a few minutes later when I started bfgminer again, it CAME BACK! It's never come back from a hangup before, so maybe that did it? Or was this just a fluke?
Anyone? Bueler?
edit: spoke too soon - it was recognized for a bit, but NOT hashing. then trying to restart from within bfgminer just made it disappear again. Argh.
Weird stuff. I added small heat sinks on the FETs and my performance went *down*. Tightened the water block a bit and temps spiked and performance *crashed*
Removed little sinks, loosened up block and snugged down gently and all normal. But man this thing is sensitive to fiddling; my guess is tightening caused the board to flex a hair enough to lift the sink off a chip. Result instant fail.
Back to 38gh. If I bolt a water block to the back of the board and run it with the one on the front I could probably get 40, but another thing I noticed is if you turn the block upside down the pump must cavitate or something, total fail.
Wow.
Removed little sinks, loosened up block and snugged down gently and all normal. But man this thing is sensitive to fiddling; my guess is tightening caused the board to flex a hair enough to lift the sink off a chip. Result instant fail.
Back to 38gh. If I bolt a water block to the back of the board and run it with the one on the front I could probably get 40, but another thing I noticed is if you turn the block upside down the pump must cavitate or something, total fail.
Wow.
out of the 18 i have had here the only ones that have been below 32gh have always had bad contact for the cooler or no cooling on the backside of the board under the FETs. i have basically the whole backside of the board under the FETs covered with small heatsinks and a fan blowing on them. all my units run above 32gh. most of them are ~35gh
thanks. I thought if the temp was under 70 it would hash faster until it hits 70 and maintain that speed. Since my temp is 64, it isnt running as fast as it can.
Yeah, sounds like your asics are cool, but your FETs are hot. Get some cooling on them and your hashrate and asic temp will both rise.
ah. ok thanks.
out of the 18 i have had here the only ones that have been below 32gh have always had bad contact for the cooler or no cooling on the backside of the board under the FETs. i have basically the whole backside of the board under the FETs covered with small heatsinks and a fan blowing on them. all my units run above 32gh. most of them are ~35gh
thanks. I thought if the temp was under 70 it would hash faster until it hits 70 and maintain that speed. Since my temp is 64, it isnt running as fast as it can.
Yeah, sounds like your asics are cool, but your FETs are hot. Get some cooling on them and your hashrate and asic temp will both rise.
Jump to: