Topic: CGminer v3.8.5 on Broadcom based DD-WRT / OpenWRT - page 18. (Read 77138 times)

do you have a small tutorial for both usb storage and using it with cgminer and ztex?

Well, you should be able to fit the one bitstream you are actually using without problems, but if you want the full bitstream directory or you have multiple ztex boards with different versions running at the same time, you'll need to set up usb storage. That is what I do.

yes I have, but I don't get my ztex working (libusb 1.0.18 is installed so I think the bitstream is missing)

have u seen this?

http://en.qi-hardware.com/wiki/Icarus#Using_TP-LINK_TL-WR703N_as_host

it uses cgminer 2.4.1 though, and theres a bug, right now you cant use privileged API.

hi,

and what is with the ztex bitstream? My tp-link 703n says there is not enough space for it? Or can you give me your compiled cgminer and it do not need it?

Well, I grabbed openwrt sources and compiled it with the needed kernel modules (so I didn't have to load them afterwards which could fail due to lack of space). I then cross compiled cgminer and presto.

Ok, I skipped the step of getting ztex worker going on the cross compiled environment, but that has already been done and does not need to be done again.

thanks

try to get one from ebay now....

is it hard for a non linux noob like me to get cg miner running on that hardware (i know how to do the openwork DDwrt part )

TP-Link MR3220 (also tried the MR3420 which is basically the same thing only with better wifi range, so I'm using that one as originally designed )

Oh thats nice since i want to get rid of my mac mini, what router do u use ?

It works just fine in my experience. I have the router dedicated to cgminer, mining to p2pool and it has no difference that I can perceive from the same setup with a full linux desktop.

Does it work great, without stales etc. I heard something about offloading problems on Ztex Boards?

I'm using ztex in OpenWRT, in fact I did much of the development with that as target (as it is the hardest to debug, might as well make it work there to start with). Can't speak of DD-WRT.

I can compile a version with it in, but I don't know that anyone has got it working. Look back through this thread and see if you can get any info from those who have attempted it.

And thanks Ned

Thanks, P_Shep.  Doughnation sent.

Any updates on Ztex support?

Updated for cgminer 2.4.2:

https://github.com/downloads/pshep/cgminer/cgminer-2.4.2-mipsel.tar.gz

Updated version:
https://github.com/downloads/pshep/cgminer/cgminer-2.4.1-1-mipsel.tar.gz

Still the same binary, but a few tweaks to the scripts and an all-new serial driver.

I discovered there was a problem with the FTDI drivers. The existing one wasn't quite compatible with the FTDI chip used in the BFL (hence having to add product and vendor IDs when loading the driver). I found newer drivers which had the chip included (FT232H), but these drivers were for later versions of linux kernel than DD-WRT uses, so wouldn't compile.
In the end I had to hack together a driver from the old one as a base and adding in the bits of code needed to get the new chip working. Seems to be working for me so far, but it is quite experimental (read: a hack) so be aware.

The specific issue I found was that when more than 64 bytes were sent by the BFL, the 65th and 66th byte would be lost. This meant that when 6 or more valid nonces were returned by the BFL, the 6th would be corrupted, leading to the 7th and onward being read incorrectly. What was happening was the driver was expecting a packet of only 64 bytes and reading the next two bytes as controls. In fact the packet being sent was much larger and the driver was discarding valid data.

The driver fix does two things:
1. Adds native support for the FT232H (and that's the only device I added)
2. Scans the device for the max packet size, which previously was hard-set to 64 bytes.

At some point I'll put my ftdi_sio.ko code changes on github.

Thanks for keeping this up to date.  Will send some btc later.

They recommend a partition of 512MB for Optware
http://www.dd-wrt.com/wiki/index.php/How_to_-_Format_and_Partition_External_Storage_Device

You can always make another partition for NAS

and you absolutely need a powered hub. Each of those devices may only use a small amount of power, but if they are all getting that power through the router then you're going to stress the router. At least have the hub attached to the router powered.

I am going to try to install DD-WRT/OptWare/CGminer on a E3000 this weekend. How big of a USB key is necessary, I only have a 256MB and >8GB keys, which seem like under and overkill.

I'll definitely send a donation out if this works out!

PS. Speaking of power, how important is it to power the USB hub? I know powered USB hubs are generally built better, but is powering necessary for 12(+4 hubs) devices?