I'm not sure why the forum kept rejecting when I attached the environment img file.by bodhi - uBoot
Here is the u-boot image.by bodhi - uBoot
Wes, Plug in the SD card, power up, and interrupt serial console, and then execute these commands (copy/paste each one to the u-boot prompt). setenv set_bootargs_mmc 'setenv bootargs console=$console root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params' setenv mmc_load_uimage 'load mmc 0:1 0x800000 /boot/uImage setenv mmc_load_uinitrd 'load mmc 0:1 0x1100000 /booby bodhi - Debian
runner3735 Wrote: ------------------------------------------------------- > Test is done. I tried the backdoor curl method on > a brand new v4 mobile attached to a LAN with no > internet access. The connection was denied, so it > was a no go. I did not try using regular http or > other ports, but it seems that port 443 is > blocked. > > Thanks bodhi, so if I mby bodhi - Off-Topic
runner3735, Certainly, after connecting serial console, enable SSH so that it's easier to install. However installing u-boot is quick, so it is OK to use serial too. > Could someone familiar with the stock os on the v4 > mobile tell me what command(s) I should use to > enable ssh once I have successfully connected over > serial? > Log in to stock, and edit thisby bodhi - Off-Topic
Wes Wrote: ------------------------------------------------------- > Bodhi, > > Now, when I plug the SD card into my live linux > machine, I'm getting the errorUnable to > mount rootfs Here is a screenshot of the > message: http://imgur.com/a/nIYfu > > -Wes Wes, The trouble you have is that you don't have a real Linux box, and the Live CD Ubuntuby bodhi - Debian
Wes, 1. > I'm pretty sure all of the commands worked in the > live linux machine (I wish there was a better way > to get feedback from entering each command), here > is the full pastebin log of that: > http://pastebin.com/spvjf5hv You need to be root user while doing this. That's the permission error when you can't extract or copy files. 2. >by bodhi - Debian
If not then I will upload the individual files.by bodhi - uBoot
Here are the 2 tarballs. See if you can extract them. wget http://forum.doozan.com/file.php?3,file=1233,filename=uboot.2016.05-tld-1.pogo_v4.bodhi.tar,download=1 wget http://forum.doozan.com/file.php?3,file=1234,filename=uboot.2016.05-tld-1.environment.bodhi.tar,download=1by bodhi - uBoot
Wes, On Ubuntu, go ahead and change directory to the SD card /boot folder cd /media/mmcblk0p1/boot Get the tarball wget --no-check-certificate https://bitly.com/1sMwD7b -O uboot.2016.05-tld-1.environment.bodhi.tar Extract the tarball tar -xf uboot.2016.05-tld-1.environment.bodhi.tar See if the files are all there: ls -l | grep uboot.2016.05-tld-1 expected output: -rw-r--by bodhi - Debian
Wes Wrote: ------------------------------------------------------- > Bodhi, > > I've ran into another problem at the next command. > Pastebin: http://pastebin.com/egfmvaxm That environment file is in the uboot environment tarball that you have downloaded: uboot.2016.05-tld-1.environment.bodhi.tarby bodhi - Debian
november17 Wrote: ------------------------------------------------------- > > > /tmp # uname -a > Linux PogoplugMobile 2.6.31.8 #4 Tue Aug 23 > 13:00:50 PDT 2011 armv5tel GNU/Linux > /tmp # ping 8.8.8.8 > PING 8.8.8.8 (8.8.8.8): 56 data bytes > 64 bytes from 8.8.8.8: seq=0 ttl=46 time=15.129 > ms > 64 bytes from 8.8.8.8: seq=1 ttl=46 time=13.657 > msby bodhi - uBoot
xddy Wrote: ------------------------------------------------------- > Hi bodhi, it's booted now after I switched to an > oooooooold usb drive (I was using a sandisk cruzer > blade on my pogoplug), phew~~~ > > I did have the idea to try another drive but would > take it as the last way coz I've been using the > sandisk cruzer blade on both E02 and dockstar fby bodhi - Debian
Wes Wrote: ------------------------------------------------------- > Bodhi, > > I think I got the drive letter, if I am reading > correct, it is p1? > > I am still running into problems at cd > /media/sdb1/bootHere is a pastebin of me > running all of the commands: > http://pastebin.com/ng57mgar > > > QuoteCopy the env text file in the new u-boby bodhi - Debian
Wes, The USB drive letter is assigned by the system. So when I wrote "/dev/sdb1" or "/media/sdb1" I meant: I assume that is what Ubuntu has assigned it. The drive letter will be different, depending on how many drives/partitions you already have in this box. So do this: Take out the stick, plug it back in, and then find out which drive letter was assigned: dmesby bodhi - Debian
november17, > > Now getting the above error. I'm not sure exactly > what I did wrong. I do think what happened was I > was unsuccessful in getting the proper file over > to the Pogo but I have no clue how to do it with > terminal. From your post, I assume that you are inside Pogo OS at /tmp ? Try: uname -a ping 8.8.8.8 If you can get to the net fromby bodhi - uBoot
habibie, > it does not say is internally it is a 5 TB SATA > HDD. Can anyone confirm this? Otherwise, I would > get one for my other GoFLEX Home unit which > currently has no HDD but only enclosure case. They always have internal SATA disk plugged into USB controller. Exactly the same way as if we put them together from parts with a USB 3.0 enclosure and a barebone HDD. Justby bodhi - Off-Topic
Wes, Try: mkdir -p /media/sdb1 mount /dev/sdb1 /media/sdb1by bodhi - Debian
xddy , Regarding the Debian netconsole setup: http://forum.doozan.com/read.php?2,9522. Not really, you can't simply regenerate the initrd on Ubuntu at terminal (different architecture), you would have to qemu/chroot to generate it correctly. > The box stuck somewhere > and cannot get ip, front led stays green, This means the kernel has started successfully but could not mountby bodhi - Debian
haarwurm Wrote: ------------------------------------------------------- > bodhi, are you ever sleeping? Again, you answered > my question almost instantly, thank you - and by > the way, thank you for your indispensable work. > > Concerning the DTS part, I used the nsa325 file, > but forgot to alter the pasted text, sorry. > > The correct envs did the trick, my Nby bodhi - Debian
xddy, As I mentioned, netconsole output stops here. So it might have booted. Did you try: 1. Ping the box. If it is online, it will responds: ping debian.local or 2. Find the box IP address in the network router.by bodhi - Debian
haarwurm, 2 things. 1. This step should be done with the NSA325v2 DTB Wrong command: cat dts/kirkwood-goflexnet.dtb >> zImage.fdt This is the correct command: cat dts/kirkwood-nsa325.dtb >> zImage.fdt 2. Since you are booting with stock u-boot, and a new Debian rootfs, the envs must be adjusted. Wrong command: bootcmd_linux=setenv bootargs $(bootargs_linux)by bodhi - Debian
Hi Wes, It happens to all of us, yours truly included :) Recovering from this is not hard. You have not bricked it at all! You have flashed the new u-boot successfully. But now your envs are all messed up (because of the error while flashing that). Now it's time to use the uEnv.txt to boot. This file will be read by u-boot during boot phase, and whatever envs in there will be used tby bodhi - Debian
xddy, > Starting kernel ... netconsole only outputs this much. So what happen after this is not known unless you've aleady done this set up to see the kernel booting progress: Use netconsole to troubleshoot Debian kernel booting Try these 1. Check the USB drive for errors using another LInux box and fix it. If the drive is assigned the drive letter sdb1: e2fsck /dev/sdb1 2.by bodhi - Debian
Wes, - Kernel upgraded (4.8.3 is already latest) - Debian upgrade - u-boot uprade.by bodhi - Debian
Wes Wrote: ------------------------------------------------------- > The SD card commands worked! You are a magician, > haha. I guess I should try to either update Uboot > and the Debian kernal at this stage? My final goal > for the system, is as mentioned briefly, a NAS > that can stream media and store files on a 750gb > external HDD. Your kernel is the latest now. Sby bodhi - Debian
Boot with SD card: setenv mmc_load_dtb 'ext2load mmc $device 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb' setenv mmc_boot 'mw 0x800000 0 1; run mmc_load_uimage; run mmc_load_dtb; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi' bootby bodhi - Debian
Wes Wrote: ------------------------------------------------------- > Haha, makes it extra hard with my $5 iron and > ruined tips. I would like to return the thanks, as > I've never had someone be so dedicated and so > helpful to a project, so thank you very much for > supporting me and all the other noobs out there. No need to, but here is something that might interesby bodhi - Debian
Wes Wrote: ------------------------------------------------------- > Well, I thought I had exhausted all of my skill in > debugging, turns out I haven't. I had two issues, > both my own fault, first off one of my solder > points must have broke after I hot glued all of > them down, so after re-soldering that, and then > after switching what I thought were the correctby bodhi - Debian
Wes, Power up, interrupt serial console and then setenv usb_load_dtb 'ext2load usb $device 0x1c00000 /boot/dts/kirkwood-pogoplug_v4.dtb' setenv usb_boot 'mw 0x800000 0 1; run usb_load_uimage; run usb_load_dtb; if run usb_load_uinitrd; then bootm 0x800000 0x1100000 0x1c00000; else bootm 0x800000 - 0x1c00000; fi' boot After booting into Debian, either 1. Set themby bodhi - Debian