Topic: OLD: BFGMiner 3.10.0: modular ASIC+FPGA, GBT+Strtm, RPC, Mac/Lnx/W64, AntU1, DRB - page 6. (Read 1193208 times)
April 30, 2014, 09:29:41 PM
Luke I have a question. I am using BFGminer 3.10.0 and when I am running my GPUs on scrypt. Some times when I start them they are starting wrong showing GHS instead of KHS. Looks like SHA256 instead of scrypt. Any way to fix this other them watching it start and if it breaks restart the miner. Thanks
April 27, 2014, 02:28:19 PM
Hi Luke,
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
I believe we've identified all the compatibility issues. Assuming the fixed firmware is released in time, it should be supported in 4.0.Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
is there a branch that can be viewed?
or is it a mainline commit?
April 27, 2014, 02:24:13 PM
Hi Luke,
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
I believe we've identified all the compatibility issues. Assuming the fixed firmware is released in time, it should be supported in 4.0.Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
is there a branch that can be viewed?
or is it a mainline commit?
plx <3
April 27, 2014, 02:14:43 PM
Hi Luke,
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
I believe we've identified all the compatibility issues. Assuming the fixed firmware is released in time, it should be supported in 4.0.Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
is there a branch that can be viewed?
or is it a mainline commit?
April 27, 2014, 02:10:01 PM
Hi Luke,
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
I believe we've identified all the compatibility issues. Assuming the fixed firmware is released in time, it should be supported in 4.0.Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
is there a branch that can be viewed?
or is it a mainline commit?
April 27, 2014, 12:44:47 PM
It does see it but I only get half the hash rate on the 30 gh/s boards. The HexFury USB miner based on the one string design works fine as the effective rate is dead on but the current reported is only half. That works fine for the HeXfury though.
I will try again as I am using the latest pre-release of 4.0 for my gridseeds.
Thanks for the link I had not been in that thread for a while.
I will try again as I am using the latest pre-release of 4.0 for my gridseeds.
Thanks for the link I had not been in that thread for a while.
I used BFG for long time with GPUs, thanks a lot Luke for your work !
here https://bitcointalksearch.org/topic/m.3987613
they say it should work ...
godspeed !
here https://bitcointalksearch.org/topic/m.3987613
they say it should work ...
godspeed !
April 27, 2014, 12:41:24 PM
That sounds great.
Thanks for the update and the work on it.
Thanks for the update and the work on it.
Hi Luke,
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
I believe we've identified all the compatibility issues. Assuming the fixed firmware is released in time, it should be supported in 4.0.Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
April 27, 2014, 12:40:12 PM
I used BFG for long time with GPUs, thanks a lot Luke for your work !
here https://bitcointalksearch.org/topic/m.3987613
they say it should work ...
godspeed !
here https://bitcointalksearch.org/topic/m.3987613
they say it should work ...
godspeed !
April 27, 2014, 12:32:51 PM
Hi Luke,
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
I believe we've identified all the compatibility issues. Assuming the fixed firmware is released in time, it should be supported in 4.0. Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
April 27, 2014, 12:27:08 PM
Hi Luke,
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
Any news on OneString Miner support? It is the last piece of the puzzle for me so I do not have to use cgminer anymore.
I hope you are having a great weekend and thanks again.
April 27, 2014, 08:14:48 AM
How to solo mine with gridseed?
April 26, 2014, 02:27:46 PM
This may be a silly request, but, is there a way to have bfgminer reset after a given period of time?
Because of my location, I'm have some issues with pool access and it would be handy to have bfg reset itself to ensure connectivity.
I'm scratching my head after reading through all the readme's and searching online.
Any thoughts? Something I've missed?
bfgminer-rpc restartBecause of my location, I'm have some issues with pool access and it would be handy to have bfg reset itself to ensure connectivity.
I'm scratching my head after reading through all the readme's and searching online.
Any thoughts? Something I've missed?
April 26, 2014, 02:23:17 PM
This may be a silly request, but, is there a way to have bfgminer reset after a given period of time?
Because of my location, I'm have some issues with pool access and it would be handy to have bfg reset itself to ensure connectivity.
I'm scratching my head after reading through all the readme's and searching online.
Any thoughts? Something I've missed?
Because of my location, I'm have some issues with pool access and it would be handy to have bfg reset itself to ensure connectivity.
I'm scratching my head after reading through all the readme's and searching online.
Any thoughts? Something I've missed?
April 26, 2014, 01:08:47 PM
Just ensure dev_serial gets set to the correct value before add_cgpu is called.
When I list devices with the GridSeed plugged in, I see BFGMiner report the device twice:
Code:
[2014-04-26 13:01:10] lowlevel_scan: Found usb device at usb:093:002 (path=(null), vid=0483, pid=5740, manuf=STMicroelectronics, prod=STM32 Virtual COM Port , serial=8D801F885551)
And then later:
Code:
[2014-04-26 13:06:39] lowlevel_scan: Found vcom device at dev_t:23000012 (path=/dev/cu.usbmodem3a21, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
The problem I am having is that the first instance, via USB, has the serial number. The second instance does not, and the second instance (vcom) is what is being used for mining. So when the device is probed, the value for detectone_meta_info.serial is NULL.
April 26, 2014, 12:07:34 PM
Just ensure dev_serial gets set to the correct value before add_cgpu is called.
When I list devices with the GridSeed plugged in, I see BFGMiner report the device twice:
Code:
[2014-04-26 13:01:10] lowlevel_scan: Found usb device at usb:093:002 (path=(null), vid=0483, pid=5740, manuf=STMicroelectronics, prod=STM32 Virtual COM Port , serial=8D801F885551)
And then later:
Code:
[2014-04-26 13:06:39] lowlevel_scan: Found vcom device at dev_t:23000012 (path=/dev/cu.usbmodem3a21, vid=0000, pid=0000, manuf=(null), prod=(null), serial=(null))
The problem I am having is that the first instance, via USB, has the serial number. The second instance does not, and the second instance (vcom) is what is being used for mining. So when the device is probed, the value for detectone_meta_info.serial is NULL.
April 26, 2014, 11:36:48 AM
BFGMiner will accept serial numbers after @ too, but I'm not sure if the gridseed driver supports this.
How is supporting this different than supporting --set-device other fashions? Any code / docs to reference? I assumed providing set_device was enough and the miner proper was what targeted the devices. April 26, 2014, 11:34:34 AM
BFGMiner will accept serial numbers after @ too, but I'm not sure if the gridseed driver supports this.
How is supporting this different than supporting --set-device other fashions? Any code / docs to reference? I assumed providing set_device was enough and the miner proper was what targeted the devices.
April 26, 2014, 10:14:33 AM
Great! Thanks for the quick answers. Thanks also for your involvement in this community. I've seen your blog, of course.
One last question though. Is the list of devices consistent? For example, if I remove or add a device and reboot, do the device "something" values get reassigned?
I ask because with cgminer you specify the device by serial number, which is always independent of USB device discovery.
One last question though. Is the list of devices consistent? For example, if I remove or add a device and reboot, do the device "something" values get reassigned?
I ask because with cgminer you specify the device by serial number, which is always independent of USB device discovery.
To answer my own question, it looks like you have to map the Linux dev node to the GSD physical unit. I guess this approach is general in that it potentially allows any device, including GPUs, to be able to be addressable in bfgminer.
But it sounds like in the case of USB devices this feature could be pretty difficult to use. Especially if moving a USB device around means that the assigned Linux "dev" nodes change. That would potentially mean that you'd have to remap the frequency to USB devices every time you change your rig configuration.
Compare that to the girnyau cgminer where you can specify a device by serial number, regardless of what Linux "dev" node it's assigned.
We're seeing GridSeeds pop up in an increasing number of USB products (DualMiners, 5-chip "cupcakes", blades). It strikes me that having a per USB serial number (and possibly per chip) frequency feature in bfgminer would be very useful.
April 26, 2014, 10:00:23 AM
Great! Thanks for the quick answers. Thanks also for your involvement in this community. I've seen your blog, of course.
One last question though. Is the list of devices consistent? For example, if I remove or add a device and reboot, do the device "something" values get reassigned?
I ask because with cgminer you specify the device by serial number, which is always independent of USB device discovery.
One last question though. Is the list of devices consistent? For example, if I remove or add a device and reboot, do the device "something" values get reassigned?
I ask because with cgminer you specify the device by serial number, which is always independent of USB device discovery.
To answer my own question, it looks like you have to map the Linux dev node to the GSD physical unit. I guess this approach is general in that it potentially allows any device, including GPUs, to be able to be addressable in bfgminer.
But it sounds like in the case of USB devices this feature could be pretty difficult to use. Especially if moving a USB device around means that the assigned Linux "dev" nodes change. That would potentially mean that you'd have to remap the frequency to USB devices every time you change your rig configuration.
Compare that to the girnyau cgminer where you can specify a device by serial number, regardless of what Linux "dev" node it's assigned.
We're seeing GridSeeds pop up in an increasing number of USB products (DualMiners, 5-chip "cupcakes", blades). It strikes me that having a per USB serial number (and possibly per chip) frequency feature in bfgminer would be very useful.
April 26, 2014, 06:57:57 AM
I used this miner for weeks and i had no problem with it!
Really liked this and i will buy a bigger miner to use with it!
Really liked this and i will buy a bigger miner to use with it!
Jump to: