just noticed Die0 on asic 2 has really low power?
same as my! how to patch? Tuning suit doesnt work it out.
Topic: Swedish ASIC miner company kncminer.com - page 856. (Read 3050071 times)
same as my! how to patch? Tuning suit doesnt work it out.
just noticed Die0 on asic 2 has really low power?
Finally. The good news is "only" 1200 mBTC lost. I need a drink now.
To anyone suffering the red & green lights of death follow KNC flash instructions up thread plus:
a) make sure controller board ground screws are tight.
b) make sure the sd card is formatted FAT16 (not FAT32).
Not off topic I think if we're talking about sdcard formatting - but for android cellphone that kept disconnecting the sdcard this worked, told it needed FAT32. On advice read in a forum I tried formatting on a linux machine tho I didn't use fdisk I used cfdisk. ran cfdisk /dev/sdx, deleted the FAT32 partition, created a WIN95 FAT32 type 0C then after writing the partition to the sdcard and quitting, I ran mkfs.vfat /dev/sdx1. Running mkfs.vfat made all the difference.
Any october orders tried using the tuning feature? my knc works quite well but thought i would have a look anyway, as one of my boards never gets as hot as the others.
So Asic2 has different volts from the others, this is an upgrade module, are these boards different from the original?
Asic 5 is the one that never gets up to temperature, when i loaded the tuning software, that asic contained no voltage values until i hit factory reset.
any ideas? has anyone got any better performance making adjustments to these values?
https://i.imgur.com/tZbT16U.png
https://i.imgur.com/hZGVO6g.png
https://i.imgur.com/aeWuMS1.png
http://imgur.com/17ciHiM,tZbT16U,hZGVO6g,aeWuMS1#0
So Asic2 has different volts from the others, this is an upgrade module, are these boards different from the original?
Asic 5 is the one that never gets up to temperature, when i loaded the tuning software, that asic contained no voltage values until i hit factory reset.
any ideas? has anyone got any better performance making adjustments to these values?
https://i.imgur.com/tZbT16U.png
https://i.imgur.com/hZGVO6g.png
https://i.imgur.com/aeWuMS1.png
http://imgur.com/17ciHiM,tZbT16U,hZGVO6g,aeWuMS1#0
Finally. The good news is "only" 1200 mBTC lost. I need a drink now.
To anyone suffering the red & green lights of death follow KNC flash instructions up thread plus:
a) make sure controller board ground screws are tight.
b) make sure the sd card is formatted FAT16 (not FAT32).
Thanks for the advice.
I gave it a go to no success, then powered it on with no boards attached and it detected the IP.. Weird!
When i then add the boards gradually it then freaks out and turns off.
I gave it a go to no success, then powered it on with no boards attached and it detected the IP.. Weird!
When i then add the boards gradually it then freaks out and turns off.
Try cooling the controller board. Some call it voodoo but some (me for instance) say it sometimes works.
All my machines from knc were unresponsive upon arrival... every one.
They were all fine, and just needed a bit of configuring...
If your miner seems unresponsive upon arrival....
one or more of these tips may help:
check your proxy.
1. no Http:// on stratum addresses.
2. Check your pool sign on credentials.
Make sure no space if you use the copy & paste... an empty character field can be hard to catch.
3. Make sure you turn DHCP OFF the first time you get into the GUI,
and...... assign an address before restarting, or you will have to sniff all over again.
good luck
They were all fine, and just needed a bit of configuring...
If your miner seems unresponsive upon arrival....
one or more of these tips may help:
check your proxy.
1. no Http:// on stratum addresses.
2. Check your pool sign on credentials.
Make sure no space if you use the copy & paste... an empty character field can be hard to catch.
3. Make sure you turn DHCP OFF the first time you get into the GUI,
and...... assign an address before restarting, or you will have to sniff all over again.
good luck
I know you are trying to help but please try to read the problem first.
None of that troubleshooting is any use. When I (and others with the same problem) say non-responsive I mean non-responsive as in a completely bricked rig. If you can get to the mining config or status page the rig isn't non-responsive.
As an example. My unit has IP address of 192.168.0.190.
Going to http://192.168.0.190 gets "connection refused".
SSH to 192.168.0.190 gets "connection refused".
The unit never completes booting (red & green lights remain on).
So how exactly would I make sure the mining address is correct if the webpage is unresponsive? In this case unresponsive isn't an exaguration. The rig does ABSOLUTELY NOTHING as delivered. It doesn't even finish booting (red or green light turn off).
Now if I (and others with the red & green lights of death) disconnect all ASIC boards, the rig can be accessed by the IP address (192.168.0.190 in this case). So this isn't some user error not sure of what the IP address is. Of course it doesn't matter.
a) any settings entered are erased when you reboot (yes all mining config info is replaced with an "X" after reboot)
and
b) connecting any mining board (tried each of the 4 individually) returns to same red & green lights of death.
Simple version:
ASIC boards connected = a complete brick, no GUI, no SSH, no completed boot cycle (red & green lights of death).
ASIC boards disconnected = GUI & SSH accessible, all settings lost when power cycled, connecting any ASIC board returns to the status above.
After ascertaining the BBB and controller do connect on their own, when you test an ASIC module to the controller board, do you plug that single module into the same port it had been in earlier or do you try hooking it up to a port normally used by one of the other modules. I found changing the destination of an ASIC module ribbon cable to a different port on an October miner, works while when hung up that way reconnecting to the same port as before is much less likely to work.
When you are in cgminer using ssh access... do not save the settings to the default directory...
instead, save to /config/cgminer.conf
thats where it's kept.
if you save to the default, it will have no effect after restart
Sry, missed that before
So I got something. Not sure if these matter or not but for those with similar issues. I believe the SD card needs to be formatted FAT16 & my rig might have had a loose ground screw.
On FAT16:
It looks like windows by default formats to Fat32. Even selecting "FAT" on a 4GB card wasn't FAT16. I used the command line DISKPART tool to manually create a small 512MB partition and was able to get the flash to complete. Will post step by step if someone needs it. If you have a 2GB or smaller SD card it shouldn't be an issue.
On ground screw:
Also it looks like one of the screws holding the control board in place was loose (ground?). I didn't get red & green lights while flashing until after I tightened it. Yeah at this point I might be chasing ghosts but even with FAT16 formatted card I couldn't get the flash "light sequence" to match KNC instructions until after tightening down the screw.
Still (4 days later shame on your knc), the unit now boots with an ASIC connected, web admin works, and SSH login is possible. It also keeps settings (SSH checked, pool config) between reboots. I have it running with only a single ASIC board connected but this is more life than this brick has shown so far. Next step is to power down, do an invocation to the machine god and connect the other four modules.
On FAT16:
It looks like windows by default formats to Fat32. Even selecting "FAT" on a 4GB card wasn't FAT16. I used the command line DISKPART tool to manually create a small 512MB partition and was able to get the flash to complete. Will post step by step if someone needs it. If you have a 2GB or smaller SD card it shouldn't be an issue.
On ground screw:
Also it looks like one of the screws holding the control board in place was loose (ground?). I didn't get red & green lights while flashing until after I tightened it. Yeah at this point I might be chasing ghosts but even with FAT16 formatted card I couldn't get the flash "light sequence" to match KNC instructions until after tightening down the screw.
Still (4 days later shame on your knc), the unit now boots with an ASIC connected, web admin works, and SSH login is possible. It also keeps settings (SSH checked, pool config) between reboots. I have it running with only a single ASIC board connected but this is more life than this brick has shown so far. Next step is to power down, do an invocation to the machine god and connect the other four modules.
FWIW:
https://www.sdcard.org/downloads/formatter_4
For those who have to format a SD card.
So I got something. Not sure if these matter or not but for those with similar issues. It looks like windows by default formats to Fat32. Even selecting "FAT" on a 4GB card wasn't FAT16. I used diskpart tool to manually create a 512MB partition and was able to get the flash to complete. Also it looks like one of the screws holding the control board in place was loose (gound?). I didn't get red & green lights while flashing until after I tightened it.
Still (4 days later shame on your knc), the unit now boots with an ASIC connected and also remembers settings (SSH checked, pool config) between reboots. I have it running with only a single ASIC board connected but this is more life than this brick has shown so far. Next step is to power down, do an invocation to the machine god and connect the other four modules.
Still (4 days later shame on your knc), the unit now boots with an ASIC connected and also remembers settings (SSH checked, pool config) between reboots. I have it running with only a single ASIC board connected but this is more life than this brick has shown so far. Next step is to power down, do an invocation to the machine god and connect the other four modules.
Good luck! I think you're finally over the hump.
After ascertaining the BBB and controller do connect on their own, when you test an ASIC module to the controller board, do you plug that single module into the same port it had been in earlier or do you try hooking it up to a port normally used by one of the other modules. I found changing the destination of an ASIC module ribbon cable to a different port on an October miner, works while when hung up that way reconnecting to the same port as before is much less likely to work.
See above. I got some life now. Single ASIC using its original port. Going to try the other 3 modules.
All my machines from knc were unresponsive upon arrival... every one.
They were all fine, and just needed a bit of configuring...
If your miner seems unresponsive upon arrival....
one or more of these tips may help:
check your proxy.
1. no Http:// on stratum addresses.
2. Check your pool sign on credentials.
Make sure no space if you use the copy & paste... an empty character field can be hard to catch.
3. Make sure you turn DHCP OFF the first time you get into the GUI,
and...... assign an address before restarting, or you will have to sniff all over again.
good luck
They were all fine, and just needed a bit of configuring...
If your miner seems unresponsive upon arrival....
one or more of these tips may help:
check your proxy.
1. no Http:// on stratum addresses.
2. Check your pool sign on credentials.
Make sure no space if you use the copy & paste... an empty character field can be hard to catch.
3. Make sure you turn DHCP OFF the first time you get into the GUI,
and...... assign an address before restarting, or you will have to sniff all over again.
good luck
I know you are trying to help but please try to read the problem first.
None of that troubleshooting is any use. When I (and others with the same problem) say non-responsive I mean non-responsive as in a completely bricked rig. If you can get to the mining config or status page the rig isn't non-responsive.
As an example. My unit has IP address of 192.168.0.190.
Going to http://192.168.0.190 gets "connection refused".
SSH to 192.168.0.190 gets "connection refused".
The unit never completes booting (red & green lights remain on).
So how exactly would I make sure the mining address is correct if the webpage is unresponsive? In this case unresponsive isn't an exaguration. The rig does ABSOLUTELY NOTHING as delivered. It doesn't even finish booting (red or green light turn off).
Now if I (and others with the red & green lights of death) disconnect all ASIC boards, the rig can be accessed by the IP address (192.168.0.190 in this case). So this isn't some user error not sure of what the IP address is. Of course it doesn't matter.
a) any settings entered are erased when you reboot (yes all mining config info is replaced with an "X" after reboot)
and
b) connecting any mining board (tried each of the 4 individually) returns to same red & green lights of death.
Simple version:
ASIC boards connected = a complete brick, no GUI, no SSH, no completed boot cycle (red & green lights of death).
ASIC boards disconnected = GUI & SSH accessible, all settings lost when power cycled, connecting any ASIC board returns to the status above.
After ascertaining the BBB and controller do connect on their own, when you test an ASIC module to the controller board, do you plug that single module into the same port it had been in earlier or do you try hooking it up to a port normally used by one of the other modules. I found changing the destination of an ASIC module ribbon cable to a different port on an October miner, works while when hung up that way reconnecting to the same port as before is much less likely to work.
So I got something. Not sure if these matter or not but for those with similar issues. I believe the SD card needs to be formatted FAT16 & my rig might have had a loose ground screw.
On FAT16:
It looks like windows by default formats to Fat32. Even selecting "FAT" on a 4GB card wasn't FAT16. I used the command line DISKPART tool to manually create a small 512MB partition and was able to get the flash to complete. Will post step by step if someone needs it. If you have a 2GB or smaller SD card it shouldn't be an issue.
On ground screw:
Also it looks like one of the screws holding the control board in place was loose (ground?). I didn't get red & green lights while flashing until after I tightened it. Yeah at this point I might be chasing ghosts but even with FAT16 formatted card I couldn't get the flash "light sequence" to match KNC instructions until after tightening down the screw.
Still (4 days later shame on your knc), the unit now boots with an ASIC connected, web admin works, and SSH login is possible. It also keeps settings (SSH checked, pool config) between reboots. I have it running with only a single ASIC board connected but this is more life than this brick has shown so far. Next step is to power down, do an invocation to the machine god and connect the other four modules.
On FAT16:
It looks like windows by default formats to Fat32. Even selecting "FAT" on a 4GB card wasn't FAT16. I used the command line DISKPART tool to manually create a small 512MB partition and was able to get the flash to complete. Will post step by step if someone needs it. If you have a 2GB or smaller SD card it shouldn't be an issue.
On ground screw:
Also it looks like one of the screws holding the control board in place was loose (ground?). I didn't get red & green lights while flashing until after I tightened it. Yeah at this point I might be chasing ghosts but even with FAT16 formatted card I couldn't get the flash "light sequence" to match KNC instructions until after tightening down the screw.
Still (4 days later shame on your knc), the unit now boots with an ASIC connected, web admin works, and SSH login is possible. It also keeps settings (SSH checked, pool config) between reboots. I have it running with only a single ASIC board connected but this is more life than this brick has shown so far. Next step is to power down, do an invocation to the machine god and connect the other four modules.
Neptunes are down to 787/1500
KNC details say only 1200 will be sold this batch.
Leaving 487 units up for grabs.
KNC details say only 1200 will be sold this batch.
Leaving 487 units up for grabs.
Don't forget kncminer.cn they seem to still have Jupiters for sale
Just looked and all sold out.
Welp, I'm in for a Neptune. My sons' inheritance on the line with the Neptune. Sure hope it gets here ahead of schedule.
Wonder if it was bitpay fees or slow updating of current btc value but the Neptune cost me $13714.46.
It does seem like I get more hw errors while running eligius, but my overall payouts seem larger. I set up a p2pool node and I don't think I have the patience for it. BTC guild had lower payouts on the jupiters than eligius as well. Maybe I'll try ghash next....
I think your having the same issue as me. This is what I was told. I just woke up and have not tested it yet though.
https://www.dropbox.com/s/6yk2eu62lmna0dq/SD_image_0.99-E.zip
1) Copy the ZIP file to an SD card and unzip the content of the archive on to the micro SD card formatted with FAT file system.
2) Turn the miner off via the power supply off switch and disconnect from the wall.
3) Open the case of the miner.
4) Insert the micro SD with the recovery files on it in to the SD card slot on the controller board
5) Reconnect the power supply and turn the power on.
6) Please wait while internal MMC flash memory is reprogrammed there will be a sequence of LED as follows:
1,2,3,4 blue LEDs on the BeagleBone will turn on, then bright white LED inside the case turns on for several seconds and then the red + green LEDs on the control board are on this means that the programming is in progress. When only the green LED is on for 5 seconds this means that the recovery was successful then all LEDs should go off and it means that the procedure completed.
7) Turn the miner off again and disconnect from the wall.
Eject the micro SD card from the controller board.
9) Plug in all the cables that were unplugged and ensure that they are secured.
10) Reconnect the power supply and power on. The miner should then start from the on-board MMC flash with the software revision 0.9.9-E
https://www.dropbox.com/s/6yk2eu62lmna0dq/SD_image_0.99-E.zip
1) Copy the ZIP file to an SD card and unzip the content of the archive on to the micro SD card formatted with FAT file system.
2) Turn the miner off via the power supply off switch and disconnect from the wall.
3) Open the case of the miner.
4) Insert the micro SD with the recovery files on it in to the SD card slot on the controller board
5) Reconnect the power supply and turn the power on.
6) Please wait while internal MMC flash memory is reprogrammed there will be a sequence of LED as follows:
1,2,3,4 blue LEDs on the BeagleBone will turn on, then bright white LED inside the case turns on for several seconds and then the red + green LEDs on the control board are on this means that the programming is in progress. When only the green LED is on for 5 seconds this means that the recovery was successful then all LEDs should go off and it means that the procedure completed.
7) Turn the miner off again and disconnect from the wall.
Eject the micro SD card from the controller board.9) Plug in all the cables that were unplugged and ensure that they are secured.
10) Reconnect the power supply and power on. The miner should then start from the on-board MMC flash with the software revision 0.9.9-E
I received the same email from KNC. The issue is that even after a flash at least in my case the same symptoms occur. Also the light sequence wasn't exactly as described. Of course the board was 0.99e and the zip/email are for flashing it to 0.99e so there is no definitive way to verify the board has been reflashed. Would be nice if the recovery version was labeled 0.99f (exactly the same as "e" but could verify the version after reboot).
When you try this out let me know what happens in step 6 for you. I get 1,2,3,4 blue led, then "bright white LED on and off" and then nothing. No flashing red & green, no green only. At that point I can remove the sd card and reboot but have the same "brick" already described. Is that because the flash failed? Or did the flash complete but that wasn't the real problem? Who knows but for me there is no change, still bricked. Hopefully you have better luck.
Doesn't seem to be working for me. You can boot it directly from a sd card, are so it seems with these instructions.
http://forum.kncminer.com/forum/main-category/hardware/23664-how-to-restore-a-broken-beaglebone-without-the-need-to-rma
That didn't help me either though. Everything seemed to happen as described though. I don't think the issue has anything to do with the beagle unfortunately.
Update Holy Crap, it worked. It just changed the units Ip for some reason the ip of the unit changed so I didn't think it worked. Thank god, this was getting really depressing.
I got ~10% hardware errors and ~10% lower hashrate mining at Eligius overnight, and switched to Btcguild this morning and the problems went away (my hashrate for November Jupiters went up by ~10% and the hardware errors went away at Btcguild).
October Jupiters using the .99 firmware don't appear to be impacted, but some November Jupiters running the .99e most definitely are.
I prefer to mine at Eligius versus Btcguild to support pool decentralization, but won't do so if it means a 10% hashrate hit.
I am not the only person having this issue. Check out the Eligius thread for more examples.
https://bitcointalk.org/index.php?topic=23768.2980
October Jupiters using the .99 firmware don't appear to be impacted, but some November Jupiters running the .99e most definitely are.
I prefer to mine at Eligius versus Btcguild to support pool decentralization, but won't do so if it means a 10% hashrate hit.
I am not the only person having this issue. Check out the Eligius thread for more examples.
https://bitcointalk.org/index.php?topic=23768.2980
I suspect it had more to do with the restart of the KNC miner than anything else.
Don't like your hash rate or error rate? Restart!
Is there anything I can do to get these cores to work? On board 3 none of the cores work, and on board 2 about 24 out of the 192 cores seem to stay off.
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
https://i.imgur.com/OipHElT.png
I just got the miner today and when I initially started it up the hashrate climbed up to about 660/670, but later i checked and noticed it was running at about 480GH/s.
https://i.imgur.com/OipHElT.png
I also have the same issue. 2 Nov Jupiters, both have their own 1200w PSU.
Both started off at 660+ GH but after 12 hours one unit is at 500GH with all cores disabled on one ASIC board
Tried hard reset, checked connections
Has anybody managed to salvage such a board ?
Thanks
try change pool
eligius have problems witch kncminer
I don't believe this to be true. Mine are working fine on Eligius.
I'll check it out I still have accounts on BTCG and Slush as well and BitMinter.
i start hash ghash.io
eligius continues with problems
eligius continues with problems
Neptunes are down to 787/1500
KNC details say only 1200 will be sold this batch.
Leaving 487 units up for grabs.
KNC details say only 1200 will be sold this batch.
Leaving 487 units up for grabs.
Don't forget kncminer.cn they seem to still have Jupiters for sale
Just looked and all sold out.
Welp, I'm in for a Neptune. My sons' inheritance on the line with the Neptune. Sure hope it gets here ahead of schedule.
I also refuse to use BFGminer because of Kano's antics 
Kano has no active role in BFGminer development; Kano develops for CGminer along with ckolivas.Oh wow really? I guess I am misinformed! Thanks for the headsup...
Jump to: