Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.11.0 - page 142. (Read 5805527 times)

Quote from: erk on January 20, 2014, 08:37:37 PM

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.

Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.

I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

How strange, I even tried editing the driver and reducing the number of bits in case it was being overclocked too much by default.
I have tried Ubuntu 13.10 (on two machines) and Scientific Linux 6.4 and they all do it, my Nanofury is an NF1 as designed by vs3

Which particular problem are you talking about now? The slowdown with erupters (chek2fire confirmed it worked better by running the erupter on a separate hub). Or the crashing at random intervals (which as I said is due to a bug in 3.10.0 from effectively unplugging of the device when conditions are flaky which is fixed in git post 3.10.0).

chek2fire

legendary

Activity: 3416

Merit: 1142

Ιntergalactic Conciliator

Quote from: chek2fire on January 20, 2014, 08:20:07 PM

Quote from: chek2fire on January 20, 2014, 08:20:07 PM

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.

Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.

I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

How strange, I even tried editing the driver and reducing the number of bits in case it was being overclocked too much by default.
I have tried Ubuntu 13.10 (on two machines) and Scientific Linux 6.4 and they all do it, my Nanofury is an NF1 as designed by vs3

Maybe is the hub you are using?

erk

hero member

Activity: 826

Merit: 500

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.

Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.

I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

How strange, I even tried editing the driver and reducing the number of bits in case it was being overclocked too much by default.
I have tried Ubuntu 13.10 (on two machines) and Scientific Linux 6.4 and they all do it, my Nanofury is an NF1 as designed by vs3

chek2fire

legendary

Activity: 3416

Merit: 1142

Ιntergalactic Conciliator

Quote from: HellDiverUK on January 20, 2014, 04:56:17 PM

I have a Ubuntu Linux server with all the current updates, running a variety of miners plugged into it on cgminer 3.10.0

I plugged a nanofury NF1 into a usb hub that has a few block erupters in it and the NF1 would only mine at just less than1GH/s.

I removed the block erupters and the NF1 started mining at full speed. Even if I add just one block erupter the NF1 instantly halves it's speed. The block erupter mines at full speed only the NF1 is effected, neither reports any errors that I can see.The power pack for the hub is 2.1Amps so it should be able to handle that, so I think it might be a conflict of some sort.

Erupters run at usb1.1 speed and protocol and perhaps are having some communication interaction making everything work in the same crap manner - depends greatly on how usb hubs manage different speed devices. Try them on separate hubs.

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.

I run cgminer in xubuntu 13.10 and with 1 in usb of laptop and the other nanofury in a anker usb hub and i have no crashing problems. In the same hub i have a bifury and a redfury and all run perfect.

-ck

legendary

Activity: 4088

Merit: 1631

Ruu \o/

Quote from: -ck on January 16, 2014, 11:47:15 PM

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected.

I'm seeing the same. 2xNanofury and 1xBitburner Fury. cgminer 3.10.0 just quits at random intervals. Running on Debian Wheezy on BeagleBone Black, and same issue on Debian Wheezy on PC. cgminer runs for days on the same machine when not running the Nanofurys.

You see this comment earlier: ?

There's a bug in the 3.10.0 release that crashes when a device is (effectively) unplugged that was fixed immediately after in git, so grab a git tarball from master or build from git.

jedimstr

hero member

Activity: 798

Merit: 1000

Quote from: ipoomyself on January 20, 2014, 05:09:30 PM

bfgminer wont overclock antminer u1 to 2.2gh/s

it works at 2gh/s using freq 0981

however

when i use freq 0A81 it defaults to 1.6gh/s WTF?

is it because i used a letter and the program doth not recognise it?

currently using bfg 3.10.0 software and antminer 1.6 (overclock 2.2) hardware.

should i invest more money into this or is this just another long term ponzi pyramid scheme that will be the death of us all i nee d input

Well first things first, maybe you should ask this in the BFGMiner thread instead of the CGMiner thread.

It's like walking into a Church and asking where the Satanic Ritual is being held tonight. Or vice versa. Wink

ipoomyself

newbie

Activity: 50

Merit: 0

bfgminer wont overclock antminer u1 to 2.2gh/s

it works at 2gh/s using freq 0981

however

when i use freq 0A81 it defaults to 1.6gh/s WTF?

is it because i used a letter and the program doth not recognise it?

currently using bfg 3.10.0 software and antminer 1.6 (overclock 2.2) hardware.

should i invest more money into this or is this just another long term ponzi pyramid scheme that will be the death of us all i nee d input

HellDiverUK

hero member

Activity: 1246

Merit: 501

Turns out that 3.10.0 is crashing on the nanofury after a random period of time. Even on a separate linux box with nothing else connected. Same setup runs bfgminer fine.

I'm seeing the same. 2xNanofury and 1xBitburner Fury. cgminer 3.10.0 just quits at random intervals. Running on Debian Wheezy on BeagleBone Black, and same issue on Debian Wheezy on PC. cgminer runs for days on the same machine when not running the Nanofurys.

erk

hero member

Activity: 826

Merit: 500