log☇︎
1100+ entries in 0.311s
trinque: you could give the buildroot instructions a whirl for the pogo
trinque: I need to re-image my pogo
shinohai: Yeah, I'm gonna try the pogo, I got it running *sorta* in sl4a
mod6: you're gonna get a pogo going? i still need to get a chance to get mine fired up.
shinohai: So I found this http://danielpbarron.com/pogo-howto.txt on your site danielpbarron, and I just so happen to have a few spare drives already.
mircea_popescu: pete_dushenski pogo.
assbot: 491 results for 'pogo' : http://s.b-a.link/?q=pogo
davout: !s pogo
mircea_popescu: http://log.bitcoin-assets.com/?date=31-05-2015#1149136 << the latter point is correct, for now. but, much like us being here makes live marginally harder for now, yet the presence of punishment for idiots provides them an incentive to either get killed or get fixed, just so putting that in there pre-pogo provides an avenue for the network to purge itself of idiocy. ☝︎
asciilifeform: it is necessary for, e.g., pogo
assbot: Logged on 30-05-2015 01:44:59; danielpbarron: http://log.bitcoin-assets.com/?date=30-05-2015#1147922 << i noticed this on my two nodes; my pogo has been lagging behind by at least a few blocks and my bigger machine was also getting its memory pool jammed up
danielpbarron: http://log.bitcoin-assets.com/?date=30-05-2015#1147922 << i noticed this on my two nodes; my pogo has been lagging behind by at least a few blocks and my bigger machine was also getting its memory pool jammed up ☝︎☟︎
decimation: so that it fits more comfortably in the pogo?
mod6 reminds himself to setup that pogo
mod6: What's the memory cap that you wanna use on a pogo? 256Mb?
asciilifeform: and in the case of 'pogo', the door is not in your house, but in... your car.
asciilifeform: ben_vulpes, mod6, mircea_popescu, et al: incidentally, even though 'transaction orphanage amputator' may not be a magical pill against oom-on-pogo (my preliminary investigation suggests that it is -not-) it still rips out the idiotic ddos vector that every unbounded cache of anything whatsoever is.
danielpbarron: yes my pogo uses 2 gigs of swap
asciilifeform: ben_vulpes, mod6, mircea_popescu, et al: incidentally, now that we have a bounded memory footprint, it may be time to try running pogo with swap space again
mod6: my full sync's (non-pogo) with v0.5.3.1 are about the same 44-45Gb
danielpbarron: it's about the same size on my non-pogo node; how big is it for the "core" implementation
assbot: Logged on 27-05-2015 14:44:35; jurov: danielpbarron: how big is .bitcoin on pogo?
jurov: danielpbarron: how big is .bitcoin on pogo? ☟︎
jurov: also you forget that you have to buy ssd for the pogo
jurov: no here it's same as pogo
asciilifeform: 2-3x the cost of pogo.
asciilifeform: thestringpuller: the trick with pogo, incidentally, is that its price is a rather artificial thing. my understanding is that they were sold 'at cost' and presently sold at liquidation price.
thestringpuller: 6 times more than a pogo tho
davout: danielpbarron asciilifeform re mircea_popescu's comments earlier regarding bitcoind's pogo, is there any way that i can get it running on the buildroot install before we actually manage to pull-off a static build?
cazalla: remidns me, i need to get my pogo up and going
davout: if there's a way to get bitcoind running on the buildroot install i'm interested, my pogo, is waiting, with it's SSD plugged in and all
mircea_popescu: davout did you manage to get that pogo going btw ?
assbot: Logged on 25-05-2015 20:17:06; danielpbarron: on a related note, my pogo running 0.5.3.x is now a full node
danielpbarron: on a related note, my pogo running 0.5.3.x is now a full node ☟︎
assbot: 461 results for 'pogo' : http://s.b-a.link/?q=pogo
mircea_popescu: !s pogo
mircea_popescu: Jautenim or you could order a pogo and help that effort along ?
mircea_popescu: Jautenim atm it's practically running on a pogo, so very low.
asciilifeform: decimation: that dongle is just the thing for, e.g., pogo - but the rng is not a rs232 device...
danielpbarron: and while checking numbers, my pogo is at height=352796
ascii_field: for those who did not watch the 'elbrus' youtube (did anyone ?) - if the screenshots are genuine , we now know that one core of 'elbrus' has approximately same benchmark performance as 'pogo.'
mod6: but anyway, yeah if it's still too large for the pogo, i guess that doesn't help us exactly.
asciilifeform: thing appears to run in approximately constant memory footprint, but far too large for 'pogo' etc. and very suggestive of fragging
ascii_field: (the only reason we don't build bitcoind on pogo is the ram-poverty)
davout: and i was confused because i didn't remember that danielpbarron's pogo runs a debian thing, hence able to run bitcoind
davout: asciilifeform: so i managed to get "busybox mkfs.ext2 /dev/sda1" working on the pogo by using buildroot-2015.05-rc1 instead of 2015.02, applying your patches (which do apply cleanly), apply my WIP-patch, and boot on that
asciilifeform: davout: kinda problematic if we can't initialize a blank drive from the pogo itself << yes, this will -have- to be fixed. but either a) later or b) someone not me
davout: kinda problematic if we can't initialize a blank drive from the pogo itself
assbot: Blade Servers, Linux Workstations, 1u Servers, Computer Server, Server Hardware | Pogo Linux, Inc. ... ( http://bit.ly/1ALJwvH )
mircea_popescu: !rate davout 4 X.EUR, apparently working on the proper French pronounciation of "pogo"
asciilifeform: ^ goes with the pogo serial thing
mod6: got my pogo today :]
danielpbarron: http://danielpbarron.com/pogo/spec.html
davout: danielpbarron: because other than the attached SATA the pogo has no other storage than the eeprom, right?
davout: oh and also there was something else, maybe asciilifeform can help with that, probably very noobish question, but i have nfi how to setup the pogo so that i'm able to put the compiled kernel on it without needing it to use tftp to load it on each boot
assbot: Logged on 07-05-2015 09:53:33; davout: danielpbarron: you created the filesystem of your pogo on your local station amirite? messed a bit with fdisk but it looks like the pogo doesn't have any mkfs binary :/
davout: danielpbarron: you created the filesystem of your pogo on your local station amirite? messed a bit with fdisk but it looks like the pogo doesn't have any mkfs binary :/ ☟︎
decimation: ben_vulpes: are you soldering the serial lines to the pogo?
decimation: asciilifeform: re: valgrind < are you running valgrind on the poor little pogo or on an x86?
davout: ok, i'm off for now, i'll get on cross-compiling bitcoind and getting it running on the pogo later
davout: ah, so ultimately the procedure would be "acquire pogo, burn image on USB stick, insert SATA drive, insert flashed USB stick, power unit on" right?
davout: but from my understanding a stock pogo won't let you simply boot from an arbitrary usb stick
davout: and since you mention the final product, what would the target procedure look like to configure a new pogo?
danielpbarron: i was able to compile bitcoind for a pogo from my gentoo laptop using crossdev
davout: ok, where would i find directions to compile it properly for the pogo?
danielpbarron: it'll take forever on the pogo i think
davout: so now i guess i just need to build the bitcoind release and put it on the pogo
davout: aha, i'm the new pogo
davout: the pogo seems to have a half green half red light
assbot: pogo [bitcoin assets wiki] ... ( http://bit.ly/1P0CnDy )
danielpbarron: http://wiki.bitcoin-assets.com/pogo
davout: danielpbarron: but i'm slightly confused at this whole thing, say i manage to flash the new uboot on the pogo, and set the correct variables with the new fw_printenv command that comes with the improved u-boot, and that with the correct settings the pogo will look for a kernel on the network at boot time, what's netcat for?
davout: i assume i can use the steps relevant to u-boot from there to get the correct version on the pogo and resume your instructions when that's done
mod6: oh cool, i guess my pogo will be delivered tomorrow
davout: from what i understand i need to replace u-boot on the pogo so that it'll load this new kernel over the network by using tftp
davout: danielpbarron: looking at your pogo docs, not sure how to perform step 4.1 u-boot compilation
ascii_field: in other news, pogo blew oom at 129647.
ascii_field: 120309 (pogo, fired up ~2hr ago, currently ~50% ram used)
mod6: I should re-iterate that I'm still waiting on a pogo to come to me...so this v0.5.3.1+OrphanageNuke test is running on AWS deb6 (amd64)
danielpbarron: mod6> the correct pogo to order is the Series 4 with the maroon/red colored logo on the front right? << http://www.amazon.com/gp/product/B006I5MKZY/
mod6: the correct pogo to order is the Series 4 with the maroon/red colored logo on the front right?
danielpbarron: seems as though the stock pogo is configured to look for a TFTP server without any modification -> bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
davout: so i'm currently connected to the Pogo through SSH, pretty easy so far
ascii_field: danielpbarron: on stock pogo you need fw_printenv (or serial cable) to get into uboot console
danielpbarron: and can also be used from the OS, but they don't come standard with an unmodified pogo
danielpbarron: stock pogo does not come with this tool, but it does come with nandwrite, flash_erase, and flash_eraseall
danielpbarron: http://log.bitcoin-assets.com/?date=29-03-2015#1078941 << how to initially get fw_printenv to tell pogo to boot kernel over TFTP in the future? ☝︎
davout: danielpbarron: which i'm not (doing the serial thing), so it's not very clear to me how to build the kernel and software that'll actually run on the pogo once it's ready
danielpbarron: all you need is to install some sort of TFTP server on your workstation, and use the built in flashing tools of pogo to set some parameters to connect to your workstation when it boots
danielpbarron: davout, yeah that's why i'm rewriting; it's about the workstation connecting to pogo
davout: (referring to http://danielpbarron.com/pogo/howto.txt)
davout: danielpbarron: in your docs, 2.2.2 refer to building a kernel for the workstation talking to the pogo, not building a kernel for the pogo itself, or am i heavily confused?
ascii_field: so pogo node lives or dies by the actual speed of the drive.
ascii_field: <danielpbarron> on a related note, my 5400 rpm pogo cannot sync << i spoke of this briefly at c3. the almost deadly-certain explanation is that there is no ram to spare for the customary disk cache
danielpbarron: on a related note, my 5400 rpm pogo cannot sync
davout: ascii_field: i have the physical pogos you gave me, an ethernet cable, a power adapter, an internet connection, a few usb sticks, a working debian, and a 120gb sata disk that fits in the pogo. what's the easiest way to set it up as a bitcoin node
assbot: Logged on 01-05-2015 16:14:34; davout: hrm.. i was under the impression it was possible to somehow re-flash the pogo from a simple USB stick without soldering anything
davout: haha, ok nice, guess i'm going to put the pogo back together then :-)
davout: hrm.. i was under the impression it was possible to somehow re-flash the pogo from a simple USB stick without soldering anything ☟︎
ben_vulpes: davout: danielpbarron.com/pogo/howto.txt