Your u-boot even though it is old, it's fine. Don't try to mess with it for now. You can just download the latest Arch rootfs and create a new USB thumb drive, format it as Ext3 with it (on a different Linux box), and boot with it. If you're desperate to get anything working, temporarily use my rootfs (Updated 31 Oct 2014 Rootfs Debian-3.17.0-kirkwood-tld-1) and boot with it. Iby bodhi - Rescue System
@TheDoo, You are running the latest u-boot. Do this to recover: - Download the latest rootfs from this thread (Updated 31 Oct 2014 Rootfs Debian-3.17.0-kirkwood-tld-1). - Format a new USB thumb drive with Ext3 (or just use one you have and format it as new, wiping out all data, though) - Follow instruction to untar that rootfs to the drive - Take it to the Pogo and cold start. Fromby bodhi - uBoot
What a f' mess :)) where did you get this roofts? In your serial console please print the u-boot version: > version It you are running u-boot installed by Jeff's script or my u-boot build then the fw_config should look like mine showed above.by bodhi - Rescue System
Good idea, but while you are waiting for serial, - on server start pinging the pogo ping 192.168.1.76 - power up the pogo - if the pogo netconsole is running then you should see it responds to a few pings. If no response then either the network problem, or neconsole is not running at all.by bodhi - uBoot
purespin Wrote: ------------------------------------------------------- > I just upgraded to this kernel and rootfs with the > help from bodhi! Everything looks good except one > thing: > > > oxnas:~# mount -t iso9660 -o ro,loop keiso.iso > /mnt/temp > mount: Could not find any loop device. Maybe this > kernel does not know > about the loop deviceby bodhi - Debian
suo_jian Wrote: ------------------------------------------------------- > Hi bodhi, > Checked with new command, still no message shown, > is it possible the nc message is not sent to > 192.168.1.78, but somewhere else? Ah! it was reversed in u-boot envs :) serverip=192.168.1.78 ipaddr=192.168.1.76 if_netconsole=ping 192.168.1.78 start_netconsole=setenv ncip 192.168.1.7by bodhi - uBoot
purespin, Quote > fw_setenv ethaddr '00:25:31:00:ef:ed' > Can't overwrite "ethaddr" > > But I can change ipaddr and serverip env using the > same fw_setenv command! It should allow you to change ethaddr in Debian. You can also set it in u-boot console with setenv. What's your output of fw_printenv mtdparts uname -a Quote > - Do I stiby bodhi - uBoot
Neptune Wrote: ------------------------------------------------------- > Ok, I again reformatted the drive and installed > Archlinux again and this time its getting > IP(although I have set it as statis IP, it is > getting random IP, but this we can solve later). > I have 2 issues now, when I boot into Archlinux > and issue command > > What I did: > I interrby bodhi - Rescue System
Your roofts still has error. Have you tried to use a different Usb drive? Perhaps this drive is bad.by bodhi - Rescue System
suo_jian Wrote: ------------------------------------------------------- > Hi bodhi , > I run netcat-traditional, and listening at > 192.168.1.78, but there is no output. > > any other suggestion? Check your nc command. The correct command is: nc -lup 6666 192.168.1.78 6666by bodhi - uBoot
Purespin, Mount the new rootfs on the other Linux box and regenerate uImage: mkimage -A arm -O linux -T kernel -C none -a 0x60008000 -e 0x60008000 -n Linux-3.17.0-oxnas-tld-1 -d /boot/vmlinuz-3.17.0-oxnas-tld-1 /boot/uImage sync Take it to the Pogo and power up.by bodhi - uBoot
purespin, > ls -l /media/sdc1/boot > total 5488 > -rw------- 1 root root 2805560 Jun 6 2013 > uImage-3.1.10 > -rw------- 1 root root 2805496 Jun 6 2013 > zImage-3.1.10 > > Are you running Arch or Debian? there is no uInitrd in /boot. Is this a special build by Ingmar? I recall Ingmar_k does not use Initrd. > I haven't upgrade the kernel yet. Bby bodhi - uBoot
suo_jian, > This is nc from the netcat-openbsd package. An > alternative nc is available > in the netcat-traditional package. > Yes, you need to run netcat-traditional. > Btw, all rootfs/format are done in the ubuntu vm since mac can't write to ext3 easily.... This is fine, I do exactly this very often on a MacBook Pro. I'm sure your problem is easy toby bodhi - uBoot
purespin, > Thank you for the quick reply. Are you talking > about step 9 & 10 in 1st post? Yes step 9 and 10 > I didn't do these as I thought this is only for > FDT kernel. The new kernel is FDT. Stock kernel is not FDT (also some people are still running older non-FDT kernels). So if you plan to run new kernel then the new envs are needed if the DTB is not emby bodhi - uBoot
suo_jian, > I also create Linux Kernel 3.17 (FDT) on a usb > flash Did you upgrade the kernel on an existing rootfs, or create a brand new rootfs? > and plug to the usb, after reboot, I do not > see any message output from netconsole server. serverip=192.168.1.78 ipaddr=192.168.1.76 if_netconsole=ping 192.168.1.78 start_netconsole=setenv ncip 192.168.1.78; setenvby bodhi - uBoot
Your current env: usb_rootfstype=ext2 In serial console, change to ext3: setenv usb_rootfstype ext3 then let it boot boot After verifying everything is working OK, set it permanently in Linux: fw_setenv usb_rootfstype ext3by bodhi - Rescue System
purespin Wrote: ------------------------------------------------------- > Hi, > > I tried to upgrade from an old U-Boot (1.1.2 Jul > 29 2010) by following the first post. Everything > seems fine but I got the following error when > rebooting (using serial cable): > > > U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27) > Boot device: NAND > Attempting toby bodhi - uBoot
@Neptune, To really fix and prevent your rootfs corruption, you need to change u-boot env rootfs type to be consistent with what you have on the USB drive. If you're not sure how, please post your u-boot envs. In serial console, printenv Your dmesg showed that you're still having problem.by bodhi - Rescue System
Booting USB 3.0 is not supported by u-boot. But it is working fully as USB 3.0 after you've booted into Debian.by bodhi - Debian
Neptune Wrote: ------------------------------------------------------- > So yesterday I updated the system and I am back to > sqaure one, the GFN is not booting up. This time > the error is different, seems some kernel issue. > Here is the complete log, please have a look. > > http://pastebin.com/5AxLYun7 Looks like your rootfs was corrupted. Mount it on a different Lby bodhi - Rescue System
hyperlogos, Sound likes you need to do a fsck. The file system could have been corrupted already,by bodhi - Debian
hyperlogos, Was it a fresh rootfs download from the 1st post? or was it your existing rootfs? Try this: if your Pogo V4 is running with 3.17 FDT then copy your Pogo V4 uImage and uInitrd over to this USB rootfs, and boot with it.by bodhi - Debian
habibie, Quote> I want to setup my Seagate GoFLEX > NET with a single folder to install the debian ARM > distro so that any of my Seagate Dockstar units > will be able to boot off of this folder and leave > the original partitions intact on my Seagate > Dockstar units, except replacing its original > u-boot with the Doozan u-boot. Is it possible? Yes. You'rby bodhi - uBoot
joeykork Wrote: ------------------------------------------------------- > I have just gotten grub 2.02~beta2-17 to run on my > PogoPlug v4. I had to rebuild bodhi's 2014.07 > uboot with CONFIG_API enabled and had to rebuild > the grub2 debian package to change the loadaddr to > 0x0200000 - the uboot port still isn't a > relocatable ELF like the efi-arm one is. Iby bodhi - uBoot
hyperlogos, Quote> 10180 bytes read in 681 ms (13.7 KiB/s) > 2822232 bytes read in 405 ms (6.6 MiB/s) > 6114335 bytes read in 654 ms (8.9 MiB/s) > ## Booting kernel from Legacy Image at 00800000 > ... > Image Name: Linux-3.17.0-kirkwood-tld-1 > Created: 1970-01-01 0:00:40 UTC > Image Type: ARM Linux Kernel Image > (uncompressed) >by bodhi - Debian
Thanks twinclouds! Does the MK808 have WOL, or any sleep mode that will power down the stick?by bodhi - Allwinner A10
I've uploaded 2014.07-tld-1 U-Boot image for the Sheevaplug. Please see 1post for download link. Thanks to Wzl, who did all the testing for this Sheevaplug u-boot image!by bodhi - uBoot
> For some reason if you > install MySQL and right after install you reboot > then run apt-get check && apt-get update then > everything is working properly. Don't know if I'll ever reinstall mysql on my plugs, but it's good to know the workaround!by bodhi - Debian
Almaz, Yes, on rootfs 3.17, apt-get update did get stuck there at "Reading package lists... 0%". But the system is not hang. I have a different ssh connection, and everything else seems normal. No high CPU or anything peculiar. Apt-get update just not taking any CPU or doing anything, perhaps waiting for some event that never occured. After reboot, apt-get update is stuck again,by bodhi - Debian
Almaz Wrote: ------------------------------------------------------- > Yep, I tried 3.14 as well. If you do a clean > rootfs install with apt-get update && apt-get > upgrade && apt-get -y install mysql-server then > apt-get will crash. Once you restart Debian then > it'll be ok again. I'm not using mysql, but will try to repeat your problem to sby bodhi - Debian