americandesi
|
|
September 20, 2013, 02:55:06 PM |
|
6. Once you've found it, you should be in the root directory("cd /mnt/<devicename>/"). Do these commands: sudo sed -i 's/10.10.11.249/192.168.1.249/' etc/network/interfaces sudo sed -i '/s/255.0.0.0/255.255.255.0/' etc/network/interfaces sudo sed -i '/s/10.1.1.1/192.168.1.1/' etc/network/interfaces
1) I have a Windows PC. So if i boot from USB, will i be able to write to the SD card and modify the network config.? 2) I have a Macbook pro which has a SD card reader. Has anyone got an idea as to what steps i need to follow to make changes to the SD card in mac (if it is possible). Thanks, Q1: Step 6 from JaredR26 above is modifying the network config. Q2: If you have an sd card available, download the image, write it to the sd and put the sd card in your mac. Then check the Finder to see if it mounted the card. If it did, go to the etc/network directory. Is there an interfaces file ? Tutorial how to write the sd image to a card: http://www.embeddedarm.com/support/faqs.php?item=10Thank you very much. will try out and keep the group posted.
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
September 20, 2013, 02:59:55 PM |
|
CMIIW, I think he want to buy one with more "reasonable" price than the shop that he think will never break even.
Although I didn't require that when I initially asked them, I did the 2nd time I asked. Yes indeed I don't like the idea of paying someone for me to write a driver and do support for them ... Especially when that someone is making sizeable profits from what they are selling. I don't expect lots in return, but getting a mining device that pays for itself quickly is not unreasonable at all, even though they think it is. Others may be happy to lose BTC, but I'll simply avoid BitFury if the only way I can get hardware from them is to lose BTC. Doesn't make any sense at all for me to do that - yes I'm not an idiot. Side effect for you guys is you have a miner that sux - oh well As at today, if you get a 25GH/s device, it will make at the most 6.17BTC in 100 days (PPS assuming only 20% diff changes for the next 100 days) Of course that's if most of the companies saying they are going to deliver a lot of hashing power in the next month or so fail to do so. On the other hand, if they do all deliver, it's unlikely you'll make anywhere near that in the next 100days - possibly ever. My requirement was simply that they sell me hardware at a price that would appear to recover it's bitcoin cost in a month. That would of course cut a tiny bit into their sizeable profits, so they don't want that. They can indeed sell all the hardware they have - so it is a small loss for them. Oh well. Move along, nothing to see here
|
|
|
|
-Redacted-
|
|
September 20, 2013, 03:22:20 PM |
|
Kano, nobody really cares about your ROI bitching. Everyone is just so tired of hearing it from you. Really.
I seem to recall Dave saying he would send you some FREE hardware, after the paid orders went out. You might want to touch base back with him now that the August orders are out the door. It couldn't hurt.
|
|
|
|
kano
Legendary
Offline
Activity: 4592
Merit: 1851
Linux since 1997 RedHat 4
|
|
September 20, 2013, 03:35:07 PM |
|
Kano, nobody really cares about your ROI bitching. Everyone is just so tired of hearing it from you. Really.
I seem to recall Dave saying he would send you some FREE hardware, after the paid orders went out. You might want to touch base back with him now that the August orders are out the door. It couldn't hurt.
You forgot to read the last line.
|
|
|
|
americandesi
|
|
September 20, 2013, 03:54:13 PM |
|
Kano, nobody really cares about your ROI bitching. Everyone is just so tired of hearing it from you. Really.
I seem to recall Dave saying he would send you some FREE hardware, after the paid orders went out. You might want to touch base back with him now that the August orders are out the door. It couldn't hurt.
You forgot to read the last line. Kano - Am Sure he did. And we all did. But your initial comment below is nothing related to bitfury. It is more related to writing an image to SD card in the link here http://www.embeddedarm.com/support/faqs.php?item=10You just needed a reason to bitch about Dave and bitfury. If you think bitfury doesn't ROI, why are you even on this thread trolling. If bitfury has decided that they will go with some other miner software and not cgminer, then that is their business decision. Look at the latest post from JaredR26, they have mentioned that they are working on a better gui for rPI and integration with miner software for oct orders. Probably it might turnout better than what you have in mind. Heh that link doesn't know how to use dd properly - the bs= option is pretty much mandatory if you don't want to take hours doing it.
|
|
|
|
superduh
|
|
September 20, 2013, 03:57:38 PM |
|
Bitfurys won't Roi at current Fiat prices or bitcoins is a fact not an opinion anymore. Doesn't stop hardcore miners though
|
ok
|
|
|
greaterninja
|
|
September 20, 2013, 05:06:11 PM |
|
Dave, I do not have any +12V or Ground plugs like this with any of my 5 Starter Kits. I am running m-board version 2.2 Was I supposed to get some with the kits? It looks like I will need to make some plugs like that now. Problem is I am not sure if the plugs I make will be adequate. Below is a picture of the plugs I think I was supposed to get...but I did not get.
|
|
|
|
-Redacted-
|
|
September 20, 2013, 05:08:54 PM |
|
If you have the version 2 m-boards, there should be PCI-e connectors right on the m-board to plug into. This is a picture of my version 1 m-board.
|
|
|
|
greaterninja
|
|
September 20, 2013, 05:11:02 PM |
|
If you have the version 2 m-boards, there should be PCI-e connectors right on the m-board to plug into. This is a picture of my version 1 m-board.
The problem with my Version 2.2 boards is the board would not boot with just 2 x PCI-E connectors on the board. I had to still hookup a power cable to the +12V and Ground screws AND also hookup the 2x PCI-E power cables. Then the board booted. I tried to boot 2 different Rpis and 2 Different M-boards with 2 different h-boards only on 2 x PCI-E power cables to the PCI-E power connectors and they simply would not boot properly.
|
|
|
|
BenTuras
|
|
September 20, 2013, 06:05:54 PM |
|
Heh that link doesn't know how to use dd properly - the bs= option is pretty much mandatory if you don't want to take hours doing it.
I always use the -bs (buffer size) option without even thinking about it, so I didn't notice it was missing. Let MMMm be up to 25% of your internal memory in megabytes(for example 1024m), this is the complete command: dd if=ts-image.dd of=/dev/diskN bs=MMMm
|
|
|
|
Lloydimiller4
Full Member
Offline
Activity: 186
Merit: 100
Monero
|
|
September 20, 2013, 06:18:02 PM |
|
If you have the version 2 m-boards, there should be PCI-e connectors right on the m-board to plug into. This is a picture of my version 1 m-board.
The problem with my Version 2.2 boards is the board would not boot with just 2 x PCI-E connectors on the board. I had to still hookup a power cable to the +12V and Ground screws AND also hookup the 2x PCI-E power cables. Then the board booted. I tried to boot 2 different Rpis and 2 Different M-boards with 2 different h-boards only on 2 x PCI-E power cables to the PCI-E power connectors and they simply would not boot properly. I've got the same problem as ninja. I'm trying to figure out what I can do while I wait for the molex cables in the mail. Would it make sense to use another Pcie cable, and cut the ends off of it to use the bare wires for this? would I need 2 different PCIE cables or would 1 that splits into 2 be enough? Thanks
|
XMR: 43uAvbYL7z9NrKQig2DswM69XaeDug1Rf8v4Un1ndssb2To51Vojz2uZ21jFumWsCcgvqZ9hPuE3fEr xKoGCkHU8CzqHFiS
|
|
|
spiccioli
Legendary
Offline
Activity: 1378
Merit: 1003
nec sine labore
|
|
September 20, 2013, 06:22:23 PM |
|
Heh that link doesn't know how to use dd properly - the bs= option is pretty much mandatory if you don't want to take hours doing it.
I always use the -bs (buffer size) option without even thinking about it, so I didn't notice it was missing. Let MMMm be up to 25% of your internal memory in megabytes(for example 1024m), this is the complete command: dd if=ts-image.dd of=/dev/diskN bs=MMMm I'd say you can set bs to 128 or 256KB (maybe 1MB) and it should be enough. Bigger than this it does not speed things up a lot since you're constrained by the writing speed of the output file (of=...) in this case the SD disk. spiccioli
|
|
|
|
tom99
|
|
September 20, 2013, 06:27:31 PM |
|
Heh that link doesn't know how to use dd properly - the bs= option is pretty much mandatory if you don't want to take hours doing it.
Then why don't you post how to do it correctly? Sorry - I don't have a BitFury and they wont even sell me one. Ask the Bitfury team Are you sure that you cant buy it for Oct. delivery?
|
|
|
|
tom99
|
|
September 20, 2013, 06:28:44 PM |
|
If you have the version 2 m-boards, there should be PCI-e connectors right on the m-board to plug into. This is a picture of my version 1 m-board.
The problem with my Version 2.2 boards is the board would not boot with just 2 x PCI-E connectors on the board. I had to still hookup a power cable to the +12V and Ground screws AND also hookup the 2x PCI-E power cables. Then the board booted. I tried to boot 2 different Rpis and 2 Different M-boards with 2 different h-boards only on 2 x PCI-E power cables to the PCI-E power connectors and they simply would not boot properly. I've got the same problem as ninja. I'm trying to figure out what I can do while I wait for the molex cables in the mail. Would it make sense to use another Pcie cable, and cut the ends off of it to use the bare wires for this? would I need 2 different PCIE cables or would 1 that splits into 2 be enough? Thanks If you dont might post picture of new Mboard please? Thank you.
|
|
|
|
Xian01
Legendary
Offline
Activity: 1652
Merit: 1067
Christian Antkow
|
|
September 20, 2013, 06:46:25 PM Last edit: September 20, 2013, 07:21:03 PM by Xian01 |
|
Kano, nobody really cares about your ROI bitching. Everyone is just so tired of hearing it from you. Really.
... one of the reasons I have him on ignore =/ I feel bad for Con having such a polarizing teammate Even worse that it was Kano's attitude that drove me to use bfasjdhfgkahsdfghalkgMiner instead of CGminer over his constant crying over not getting free hardware in a timely manner. *additionally mentions something about bfasjdhfgkahsdfghalkgMiner having an uptime of over 8 days driving Erupter USB's on Windows vs CGMiner consistently crashing after 24-48 hours of use. Mumbles something about "gg libusb"*
|
|
|
|
gyverlb
|
|
September 20, 2013, 06:48:15 PM |
|
Heh that link doesn't know how to use dd properly - the bs= option is pretty much mandatory if you don't want to take hours doing it.
I always use the -bs (buffer size) option without even thinking about it, so I didn't notice it was missing. Let MMMm be up to 25% of your internal memory in megabytes(for example 1024m), this is the complete command: dd if=ts-image.dd of=/dev/diskN bs=MMMm bs is for block size. AFAIK dd doesn't buffer data and let the kernel cache handle buffering if needed. The bs value should be large enough to avoid inefficiencies (depends on the system, 4k probably is a minimum and most systems I know of have good/best results with 64k) but not too large to avoid wasting memory (and sometimes lower xfer speeds). Most of the time the ideal value is a power of 2 (to match kernel/hardware structure sizes) with some notable exceptions such as RAID arrays with a number of stripes not being a power of 2. To find out the best value you can test increasing block size values (starting at 4k and doubling size on each new try) by adding "bs=<block_size> count=<nb_blocks>" which will transfer <nb_blocks>*<block_size>: try limiting <nb_blocks> so that the transfer takes only a few seconds. dd should report the bandwidth, stop increasing bs when you reach a plateau and then remove the count=... parameter to get the command-line transferring the image at roughly the maximum speed possible.
|
|
|
|
-Redacted-
|
|
September 20, 2013, 07:25:03 PM |
|
OK - I've got a serious problem here. My main-board just smoked two Raspberry PI's. One will no longer come on at all, the other will turn the red light on connected to an external source away from the m-board, but a couple of the chips on the RPi get extremely hot very quickly, to the point where they burn your fingers if you touch them. I know that's not right.
The chip that now gets so hot on the RasPi is labelled RG2. I have one other m-board and a personal RasPi that I'll try, but I don't know for certain that the replacement board I received doesn't have the same problem - I've never tried it because I've been running both h-cards in one main board - the one that just smoked the RPis...
|
|
|
|
tom99
|
|
September 20, 2013, 07:27:22 PM |
|
OK - I've got a serious problem here. My main-board just smoked two Raspberry PI's. One will no longer come on at all, the other will turn the red light on connected to an external source away from the m-board, but a couple of the chips on the RPi get extremely hot very quickly, to the point where they burn your fingers if you touch them. I know that's not right.
The chip that now gets so hot on the RasPi is labelled RG2. I have one other m-board and a personal RasPi that I'll try, but I don't know for certain that the replacement board I received doesn't have the same problem - I've never tried it because I've been running both h-cards in one main board - the one that just smoked the RPis...
What was version of Mboard are you using?
|
|
|
|
Trongersoll
|
|
September 20, 2013, 07:28:45 PM |
|
OK - I've got a serious problem here. My main-board just smoked two Raspberry PI's. One will no longer come on at all, the other will turn the red light on connected to an external source away from the m-board, but a couple of the chips on the RPi get extremely hot very quickly, to the point where they burn your fingers if you touch them. I know that's not right.
The chip that now gets so hot on the RasPi is labelled RG2. I have one other m-board and a personal RasPi that I'll try, but I don't know for certain that the replacement board I received doesn't have the same problem - I've never tried it because I've been running both h-cards in one main board - the one that just smoked the RPis...
hmmm... I smoked Raspberry tobacco, it smelled nice.
|
|
|
|
superduh
|
|
September 20, 2013, 07:51:21 PM |
|
OK - I've got a serious problem here. My main-board just smoked two Raspberry PI's. One will no longer come on at all, the other will turn the red light on connected to an external source away from the m-board, but a couple of the chips on the RPi get extremely hot very quickly, to the point where they burn your fingers if you touch them. I know that's not right.
The chip that now gets so hot on the RasPi is labelled RG2. I have one other m-board and a personal RasPi that I'll try, but I don't know for certain that the replacement board I received doesn't have the same problem - I've never tried it because I've been running both h-cards in one main board - the one that just smoked the RPis...
did you "pencil mod it" wink once for yes two times for no
|
ok
|
|
|
|