>I think perhaps we should just keep the tools binaries on this site. It makes things a little simpler. And continue to keep the images at dropbox with bitly links? This is your call, I don't know what is better for your workflow and for the script calling a link here is the same as calling a link from dropbox.by bobafetthotmail - uBoot
> Actually, it is harder with the script to track download. bitly redirects to dropbox with browser. I'm not sure Google shorten links can be resolved in the script? I could put the md5 checksum file links there. AFAIK bitly redirects correctly wget (what is used in the script to fetch files), don't know about tracking but it should be dealt with server-side. I'm probablyby bobafetthotmail - uBoot
The UART port is clearly labeled as such on the manual http://dreamplug.googlecode.com/files/DreamPlug%20User%20Guide_US_v1.1.pdf and as the wiki says here, http://www.plugcomputer.org/Documentation/all-categories/categorydreamplug/dreamplug/ its pinout is the same as guruplug as the JTAG/UART thingy is the same. so you can get all info about it from the other page of the same wiki http://by bobafetthotmail - Debian
well, since the script is going to download both file and md5 checksum file, you may only need to keep the md5 checksum on a server that can track the downloads. Also, I could integrate basic telemetry in the script too, it would also help in gathering info about stock uboot md5s, having a database of stock uboots and their envs, and so on if I have a place I can send files into (an ftp accounby bobafetthotmail - uBoot
Hm, I started working on the script. Do we still need the part of the script that on start checks if stock uboot matches a md5? I don't know but I don't think most devices will have the same uboot md5. Also, jeff's script expects to check the md5 of tools too. I have a dropbox account already so I'm going to make all tests with that for the moment.by bobafetthotmail - uBoot
>The tower itself cruises at around 105 watts, sometimes 90 and sometimes 120, Well within the (true) spec of most crappy PSUs then, most are 250-300W units that can theoretically for 60 seconds reach 500-600W. It shouldn't be an issue, but if you can change to a better brand like Antec it is better.by bobafetthotmail - Off-Topic
bodhi Wrote: ------------------------------------------------------- > 3. rootfs file will be at my Dropbox folder and have generic name > debian-kirkwood-rootfs-bodhi-latest.tar.bz2 I have yet to test the busybox in your toolbox, does it have a tar that can decompress bz2 ? Because on Zyxel for example bz2 isn't decompressable by stock firmware. For the same reason I wasby bobafetthotmail - uBoot
Sure, I can modify that, expanding it to work for all other devices in the list and add some stuff for partitioning a drive.by bobafetthotmail - uBoot
newer Kirkwoods like yours cannot be bricked, as long as you have serial connection to the board's TTL pins you can reload a whole uboot over serial or fix the envs by using the uboot's own toolsby bobafetthotmail - uBoot
low-end hardware has higher failure rates, but that does not mean that they ALL fail horribly within 2 years. PSUs tend to kill hard drives and GPUs more than motherboards or devices over them (CPU/RAM). Are you sure you need a 600w unit? What hardware is in that PC? It is better to take a good quality PSU with less wattage than a crap PSU with more wattage, if your power needs are stillby bobafetthotmail - Off-Topic
uhh... what was this all about again? ... ah yes. The automated installer. :) So let's make sure we are still on the same page: I'm now going to make a script (most of this is already written for that discontinued project, if i can still find it anyway) that -checks the name of your flashable uboot binary and uses that to determine what box it is working on -checks that thby bobafetthotmail - Off-Topic
> If it is messy, let's clean it up, together. :) the approach of HP's t5325 u-boot is beyond stupid. The firmware rewrites envs each power off, the system then does not "power down" but reboots and the new envs bring it into a "ninja low-power mode" and it waits there, when receives a signal from the WoL it rewrites envs and reboots again into its normal fiby bobafetthotmail - Off-Topic
>there is no urgency for releasing a new u-boot, Yeah, as it is now it will probably be fine until kirkwoods are obsolete (considering their average role, that's at least a decade), any more work on it will be to add device support. I mean, it has all useful drivers, scripting, can read external config files, can figure out the file system in a partition on its own, does netconsole.by bobafetthotmail - Debian
Hmm, I see this load_dtb=echo loading DTB $dtb_file ...; ext2load $bootdev $device 0x1c00000 $dtb_file load_initrd=echo loading uInitrd ...; ext2load $bootdev $device 0x1100000 /boot/uInitrd load_uimage=echo loading uImage ...; ext2load $bootdev $device 0x800000 /boot/uImage This means that uboot looks for a ext2 partition (and will also read ext3 because it's similar). If you followby bobafetthotmail - Debian
>Makes 11,352,960,000 or over eleven billion spins on one lube job. But they got their money's worth! That's (relatively expensive) low-friction very hard metal bearings for you. You don't want even synthetic grease in a hdd, platters must stay VERY clean, grease goes everyhwere with heat.by bobafetthotmail - Off-Topic
I know that it isn't booting to stock, but kirkwoods are supported by openWRT, it can be flashed on NAND and is better than its original firmware by 3-4 orders of magnitude. here http://forum.doozan.com/read.php?8,25874 we talk about it and a more advanced system (UBIFS file system instead of stadnard openwrt image), but you can probably live well with standard instructions from openwrt pagby bobafetthotmail - uBoot
Umm, I got confused by the "ECC not enabled" message I see when booting Uboot then. I assumed that the "not enabled" meant that it was there but not.. well.. enabled. :) Is that message from stock uboot code? In the datasheet there is no reference about ECC. Nevermind then.by bobafetthotmail - uBoot
another useful post from bodhi about bad blocks http://forum.doozan.com/read.php?2,7806,13250#msg-13250 Might be a good idea to make a post you can add to the list of tutorialsby bobafetthotmail - uBoot
what SDcard to USB adapter you used? I suspect that the one used to connect it to the router isn't UHS I, while the SD card slot in the PC is UHS I or whatever. Can you use the same adapter you used for the router on the laptop too?by bobafetthotmail - Off-Topic
>1. You mentioned 1.5MB reserved for u-boot and envs. I made that with the stock uboot in mind, and the stock uboot+envs says that. I'm probably going to refine that a little into "just install bodhi's uboot first" because I'm sure that it works reliably anyway. >2. To accomodate bad blocks, you should make sure that you use a little more than needed. So perhaby bobafetthotmail - Off-Topic
Look for old NAS with disks. those with RAID. A vew years ago I've managed to get 4x 1.5 TB seagate drives and an old Intel NAS for 100 euros. These disks have been up for 3+ years before I received them, shut down less than 10 times, according to their SMART. Lately I got 2x 500 GB hitachi drives + a very crappy thecus NAS (that I'm probably cannibalizing for parts) for 25 euros,by bobafetthotmail - Off-Topic
Quick update, the buspirate can see and operate on the onboard flash, imaged the thing. I also discovered rare and powerful artifacts from modern china called "SOIC clips" or "<name of the chip package> clip" that simply clamp on the chip and let me connect cables to the programmer to work on the EEPROM. http://www.ebay.co.uk/itm/Programmer-Test-Clip-SOP8-SOP-SOIC-8-by bobafetthotmail - Off-Topic
I was wondering about the possibility to enable ECC for the RAM. The SoC supports it, and afaik the only difference in PC DIMMs is that they add a chip to compensate for the RAM space used by checksums. So, would it be possible to enable ECC in a kirkwood? RAM space will probably decrease so it may be worth it for 256+ RAM devices only. I'm asking in the uBoot section because I thinby bobafetthotmail - uBoot
> my Pogoplug Series 4. That's the guy with two USB 3.0 ports right? Assuming the two ports are not on a hub but on the average dual-port-to-pcie controller you have around 250 MB/s up and 250MB/s down (independent speeds), should be more than enough for two drives, just don't use SSDs. >Can I follow the above guide, making sure to create md0 and md1, one for each of theby bobafetthotmail - Debian
> Over my head! I only said to look for the parts where the cracking articles talk of the limits of their approach, they usually state in plain english what you need to do to stay safe against that. Like "password longer than X" or "use encryption Y" or "disable feature Z in router". You don't need to understand the ins and outs of pro wifi cracking (I&by bobafetthotmail - Off-Topic
%&£%"$)% Now that's cheep, and snapdragons might allow linux to run theoretically. But that's a major pain in the backside for little gain. But really.... 10 bucks. Too bad I'm not in the US.by bobafetthotmail - Off-Topic
> They reported the Intel NIC hung, but it did not freeze the LAN for other non-Intel boxes. I'm ready to bet that the Phoronix guy is using pro networking gear like say a pro switch for the very least (he has 20 or 30 PCs in his basement for tests and benches), while Fotex is likely using a consumer-grade device. It's not the first time a consumer-grade router or switch acts sby bobafetthotmail - Off-Topic
> In step 5, why do you keep 1 eraseblock between u-boot environment and root? That's for stock uboot, if you use bodhi's your mtdparts is fine.by bobafetthotmail - Off-Topic
Just chiming in: A char (single letter or number) is 8 bits, or one byte. One MB is 1024 bytes. That's 1024 letters/numbers per MB. You cannot realistically use passwords big enough to fill a single MB of RAM, and most routers have 16+ MB of RAM (usually around 8+ MB is free). > I've heard it said a nosy neighbor with Wireshark can get your WPA2 password in under 2 daysby bobafetthotmail - Off-Topic
From the logs, it seems you are using a motherboard with Intel e1000e ethernet chip. This chip is currently known for locking up for no reason with kernels 4.X, maybe you got hit by the same bug even with an older kernel (when it was rarer). http://www.phoronix.com/scan.php?page=news_item&px=E1000E-Crazy-Hangs Using another non-Intel chip will probably solve the current issue. Beingby bobafetthotmail - Off-Topic