Author

Topic: [Antminer S1 Sales open] Price changes daily, now 0.414 BTC for 180GH/s - page 236. (Read 346285 times)

hero member
Activity: 560
Merit: 500
Bitmain is a amazing company, ship on 25 and i already have 27 here in the Netherlands. Thanks for the fast delivery. Will order again!

+1
hero member
Activity: 728
Merit: 500
Bitmain is a amazing company, ship on 25 and i already have 27 here in the Netherlands. Thanks for the fast delivery. Will order again!
sr. member
Activity: 388
Merit: 250
BITMAIN, any updates on shipping/tracking?
full member
Activity: 158
Merit: 100
entered the 8.8.8.8 for the DNS.   Restarted the machine.  Hits save and apply on miner config page again....wont start....the corresponding sys log for this last attempt

I was having issues with mine and the google DNS last night so I added the OpenDNS (208.67.222.222) as the first entry.

I saved, then went to network and clicked the "connect" so the interface would restart.  On one, this caused the Ant to start.  The other, I selected "restart" from the menu.  But you need to find the "Diagnostics" tab and ensure you can "ping" to ensure your DNS settings are working.
full member
Activity: 158
Merit: 100
Guys, an information please

Is it possible to have ssh access with antminer and "view" cgminer with "screen -r" command ?

Thanks  Smiley

Just enable network access via cgminer config ( /etc/config/cgminer ??) and query it for the status.
full member
Activity: 158
Merit: 100
edit 2 : interested if you removed the heat sink whether it is noticeable that the paste has run from top to bottom

No I haven't removed the heat sink.  I cleaned up the huge mess after making a trip for some cotton balls and alcohol and then fired it up.  So far, it's working but bonus, the fan isn't quiet either.  I have screens of the pre-configured mining panel, one of the entries leads me to believe it was part of a mine cause it was something like Antminer_13_43, which is something I would add for a shelf -> miner setup.  The sysdate was also Dec 23rd before I sync'd it even if the PCB listed 2014/1/4.
legendary
Activity: 1946
Merit: 1035
what should the poll address for slush's pool look like (in the antminer settings) ?

http://api.bitcoin.cz:8332 ?
stratum.bitcoin.cz:3333  ?

Use stratum for antminers.

stratum+tcp://stratum.bitcoin.cz:3333

Eligius.st is also a good pool.

I have been using http://stratum.bitcoin.cz:3333

This has been working.

Is there a difference in using stratum+tcp://stratum.bitcoin.cz:3333

Basically, http://stratum.bitcoin.cz:3333 will redirect to stratum+tcp://stratum.bitcoin.cz:3333
hero member
Activity: 1582
Merit: 502
Check if you can ping google.com
hero member
Activity: 543
Merit: 502
what should the poll address for slush's pool look like (in the antminer settings) ?

http://api.bitcoin.cz:8332 ?
stratum.bitcoin.cz:3333  ?

Use stratum for antminers.

stratum+tcp://stratum.bitcoin.cz:3333

Eligius.st is also a good pool.

I have been using http://stratum.bitcoin.cz:3333

This has been working.

Is there a difference in using stratum+tcp://stratum.bitcoin.cz:3333
hero member
Activity: 560
Merit: 500
try stratum.mining.eligius.st:3334 no http and no stratum+tcp just stratum.mining.eligius.st
as user set your minning address and whatever password


right
full member
Activity: 126
Merit: 100
try stratum.mining.eligius.st:3334 no http and no stratum+tcp just stratum.mining.eligius.st
as user set your minning address and whatever password
full member
Activity: 127
Merit: 100
entered the 8.8.8.8 for the DNS.   Restarted the machine.  Hits save and apply on miner config page again....wont start....the corresponding sys log for this last attempt

thanks guys

Wed Dec 31 16:00:11 1969 kern.warn kernel: [    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Wed Dec 31 16:00:11 1969 kern.debug kernel: [    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
Wed Dec 31 16:00:11 1969 kern.debug kernel: [    0.000000] pcpu-alloc:
  • 0
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 16256
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.000000] Kernel command line:  board=TL-WR741ND-v4 console=ttyATH0,115200 rootfstype=squashfs,jffs2 noinitrd
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] PID hash table entries: 256 (order: -2, 1024 bytes)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] Writing ErrCtl register=00000000
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] Readback ErrCtl register=00000000
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] Memory: 61336k/65536k available (2187k kernel code, 4200k reserved, 588k data, 232k init, 0k highmem)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.000000] NR_IRQS:51
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.080000] Calibrating delay loop... 265.42 BogoMIPS (lpj=1327104)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.080000] pid_max: default: 32768 minimum: 301
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.080000] Mount-cache hash table entries: 512
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.090000] NET: Registered protocol family 16
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.100000] MIPS: machine is TP-LINK TL-WR741ND v4
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.550000] bio: create slab at 0
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.560000] Switching to clocksource MIPS
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.560000] NET: Registered protocol family 2
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.570000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.570000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.570000] TCP: Hash tables configured (established 512 bind 512)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.580000] TCP: reno registered
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.580000] UDP hash table entries: 256 (order: 0, 4096 bytes)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.590000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.600000] NET: Registered protocol family 1
Wed Dec 31 16:00:11 1969 kern.debug kernel: [    0.600000] PCI: CLS 0 bytes, default 32
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.620000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.620000] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.630000] msgmni has been set to 119
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.640000] io scheduler noop registered
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.640000] io scheduler deadline registered (default)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.640000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.650000] ar933x-uart: ttyATH0 at MMIO 0x18020000 (irq = 11) is a AR933X UART
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.660000] console [ttyATH0] enabled, bootconsole disabled
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.670000] ath79-spi ath79-spi: master is unqueued, this is deprecated
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    0.680000] m25p80 spi0.0: found s25fl064k, expected m25p80
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.680000] m25p80 spi0.0: s25fl064k (8192 Kbytes)
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.690000] 5 tp-link partitions found on MTD device spi0.0
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.690000] Creating 5 MTD partitions on "spi0.0":
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.700000] 0x000000000000-0x000000020000 : "u-boot"
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.700000] 0x000000020000-0x000000117d80 : "kernel"
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    0.710000] mtd: partition "kernel" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.720000] 0x000000117d80-0x0000007f0000 : "rootfs"
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    0.730000] mtd: partition "rootfs" must either start or end on erase block boundary or be smaller than an erase block -- forcing read-only
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.740000] mtd: partition "rootfs" set to be root filesystem
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.740000] mtd: partition "rootfs_data" created automatically, ofs=0x370000, len=0x480000
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.750000] 0x000000370000-0x0000007f0000 : "rootfs_data"
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.760000] 0x000000020000-0x0000007f0000 : "firmware"
Wed Dec 31 16:00:11 1969 kern.notice kernel: [    0.770000] 0x0000007f0000-0x000000800000 : "art"
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.790000] libphy: ag71xx_mdio: probed
Wed Dec 31 16:00:11 1969 kern.info kernel: [    0.790000] eth0: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
Wed Dec 31 16:00:11 1969 kern.info kernel: [    1.340000] eth0: Found an AR7240/AR9330 built-in switch
Wed Dec 31 16:00:11 1969 kern.info kernel: [    2.380000] eth1: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
Wed Dec 31 16:00:11 1969 kern.info kernel: [    2.930000] ag71xx ag71xx.0 eth1: connected to PHY at ag71xx-mdio.1:04 [uid=004dd041, driver=Generic PHY]
Wed Dec 31 16:00:11 1969 kern.info kernel: [    2.940000] TCP: cubic registered
Wed Dec 31 16:00:11 1969 kern.info kernel: [    2.940000] NET: Registered protocol family 17
Wed Dec 31 16:00:11 1969 kern.info kernel: [    2.950000] 8021q: 802.1Q VLAN Support v1.8
Wed Dec 31 16:00:11 1969 kern.info kernel: [    2.960000] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Wed Dec 31 16:00:11 1969 kern.info kernel: [    2.970000] Freeing unused kernel memory: 232K (80316000 - 80350000)
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.790000] usbcore: registered new interface driver usbfs
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.800000] usbcore: registered new interface driver hub
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.800000] usbcore: registered new device driver usb
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.810000] usbcore: registered new interface driver bitmain
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    5.820000] hash ok
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    5.820000] hashtest OK
Wed Dec 31 16:00:11 1969 kern.err kernel: [    5.820000] bitmain-asic: success to register device
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.830000] usbcore: registered new interface driver bitmainbl
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.840000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.840000] ehci-platform: EHCI generic platform driver
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.850000] ehci-platform ehci-platform: EHCI Host Controller
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.850000] ehci-platform ehci-platform: new USB bus registered, assigned bus number 1
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.860000] ehci-platform ehci-platform: irq 3, io mem 0x1b000000
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.890000] ehci-platform ehci-platform: USB 2.0 started, EHCI 1.00
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.890000] hub 1-0:1.0: USB hub found
Wed Dec 31 16:00:11 1969 kern.info kernel: [    5.890000] hub 1-0:1.0: 1 port detected
Wed Dec 31 16:00:11 1969 kern.info kernel: [    6.230000] usb 1-1: new high-speed USB device number 2 using ehci-platform
Wed Dec 31 16:00:11 1969 kern.info kernel: [    6.380000] hub 1-1:1.0: USB hub found
Wed Dec 31 16:00:11 1969 kern.info kernel: [    6.380000] hub 1-1:1.0: 2 ports detected
Wed Dec 31 16:00:11 1969 kern.info kernel: [    6.670000] usb 1-1.1: new full-speed USB device number 3 using ehci-platform
Wed Dec 31 16:00:11 1969 kern.info kernel: [    6.800000] bitmainbl 1-1.1:1.0: USB Bitmain bootloader device now attached to USB Bitmain bootloader-0
Wed Dec 31 16:00:11 1969 kern.warn kernel: [    6.810000] PIC microchip bootloader usb OK
Wed Dec 31 16:00:11 1969 kern.notice kernel: [   10.560000] jffs2: notice: (328) jffs2_build_xattr_subsystem: complete building xattr subsystem, 25 of xdatum (0 unchecked, 24 orphan) a
legendary
Activity: 1405
Merit: 1001
Did you check the Network -> Diagnostics?
Do they work?
full member
Activity: 127
Merit: 100
so ive gone through the setup process, seems everything was successful.  

in miner setup, I entered a p2pool address for pool1, and used my bitcoin address as the worke1 name, with some password.

how does do I actually initiate the mining process?


When you hit the SAVE&APPLY.  It will update your settings and restart the miner and start mining away.  If it does not, recheck your pool configuration.


there is no configuration to check,  just entered bitcoin mining address from p2pool.org, followed by my bitcoin address as the worker and password
only one pool info entered but when i click save and apply the browser-like-processing-circle keeps turning nonstop

Yes the configuration I was referring too was the pool URL, the pool port number, worker name, and password. I have seen it get stuck like that once.  I just rebooted and all was fine.  You could always try rebooting it too.

just rebooted no change, still same prob.  Sys log reports, bad address, could not be resolved.
im entering the pool address as reported by p2pool.org,  which is  http://p2pool.org:9332   im entering it as they have it,
full member
Activity: 182
Merit: 100
so ive gone through the setup process, seems everything was successful.  

in miner setup, I entered a p2pool address for pool1, and used my bitcoin address as the worke1 name, with some password.

how does do I actually initiate the mining process?


When you hit the SAVE&APPLY.  It will update your settings and restart the miner and start mining away.  If it does not, recheck your pool configuration.


there is no configuration to check,  just entered bitcoin mining address from p2pool.org, followed by my bitcoin address as the worker and password
only one pool info entered but when i click save and apply the browser-like-processing-circle keeps turning nonstop

Yes the configuration I was referring too was the pool URL, the pool port number, worker name, and password. I have seen it get stuck like that once.  I just rebooted and all was fine.  You could always try rebooting it too.

When I put save and apply to my mining details it did the same updating swirly doodahh so I just clicked on another tab then went back to the configuration page and the details were there .
sr. member
Activity: 588
Merit: 269
so ive gone through the setup process, seems everything was successful.  

in miner setup, I entered a p2pool address for pool1, and used my bitcoin address as the worke1 name, with some password.

how does do I actually initiate the mining process?


When you hit the SAVE&APPLY.  It will update your settings and restart the miner and start mining away.  If it does not, recheck your pool configuration.


there is no configuration to check,  just entered bitcoin mining address from p2pool.org, followed by my bitcoin address as the worker and password
only one pool info entered but when i click save and apply the browser-like-processing-circle keeps turning nonstop

You could post a screen shot of the miner screen to see stats.
sr. member
Activity: 336
Merit: 250
so ive gone through the setup process, seems everything was successful.  

in miner setup, I entered a p2pool address for pool1, and used my bitcoin address as the worke1 name, with some password.

how does do I actually initiate the mining process?


When you hit the SAVE&APPLY.  It will update your settings and restart the miner and start mining away.  If it does not, recheck your pool configuration.


there is no configuration to check,  just entered bitcoin mining address from p2pool.org, followed by my bitcoin address as the worker and password
only one pool info entered but when i click save and apply the browser-like-processing-circle keeps turning nonstop

Yes the configuration I was referring too was the pool URL, the pool port number, worker name, and password. I have seen it get stuck like that once.  I just rebooted and all was fine.  You could always try rebooting it too.
sr. member
Activity: 336
Merit: 250
pixl8tr, you scare me.....you could be my identical twin brother from another mother and father....weird

Hahaha

 Grin
full member
Activity: 127
Merit: 100
so ive gone through the setup process, seems everything was successful.  

in miner setup, I entered a p2pool address for pool1, and used my bitcoin address as the worke1 name, with some password.

how does do I actually initiate the mining process?


When you hit the SAVE&APPLY.  It will update your settings and restart the miner and start mining away.  If it does not, recheck your pool configuration.


there is no configuration to check,  just entered bitcoin mining address from p2pool.org, followed by my bitcoin address as the worker and password
only one pool info entered but when i click save and apply the browser-like-processing-circle keeps turning nonstop
sr. member
Activity: 336
Merit: 250
and is anyone dedicating their miners to work on alt coins,  then converting to bitcoins
considering difficulty of bitcoin, i thought that might be the best thing but no one here seems to be doing that.  Would appreciate the advise
that what i am dong
and i have been doing for the last 2 weeks



Hi pjcltd and thanks again for helping me out when I was setting up my miner Smiley

I also have this question as to if its better to mine altcoins rather than bitcoins directly.

I have tried mining UNO but had better results in 24 hours by mining btc directly.

I am currently mining btc but I would love to know if I could increase my daily earnings a bit Smiley

Care to share some thoughts?

Thanks Wink


just to throw my 2cents....and i haven't done hard cold figures...but am mining btc and peercoin and litecoin. obviously you are interested in a btc alternative...and a more profitable one at that....not sure if there is one...but peercoin seems like a logical bet only because in my non educated opinion it seems harder to go from $1000/btc to $3000/btc or 3 times the money than for peercoin to go from $6 do $18....and peercoin has the benefit of being the no. 2 sha256 coin so when all the ASICs that can't keep up with bitcoin will have to go somewhere, and I don't think it will be the trash....so they'll go mine another sha256 coin....I think it will be PEERCOIN.
Jump to: