feas, That's not the cause. - Remove this uEnvt.txt file - Power up, interrupt serial console - And then setenv bootcmd 'run bootcmd_uenv; run scan_disk; run set_bootargs; printenv; printenv bootargs; run bootcmd_exec' boot Please post the entire serial console log.by bodhi - Debian
feas, Your kernel files looks fine, as comparing with ones on my Pogo E02! I have a feeling that it might be something to do with bootargs. But they look OK, too. However, this indicates there is something in the uEnv.txt: loading envs from usb 0 ... 87 bytes read in 366 ms (0 Bytes/s) See what's in this file, could be that it has redefined some envs that caused this freeze? cby bodhi - Debian
feas, Even though you said you've used method 4a, let's check the kernel files on /boot. Assuming you mount it at /media/sdb1 on your laptop. Pls post the output of: ls -lart /media/sdb1/boot 1. See if the uImage is indeed the one generated by mkimage, or if by accident it was one with embedded DTB? 2. Does this USB drive have more than one partition?by bodhi - Debian
jason Wrote: ------------------------------------------------------- > Here are the results from the netconsole output of > a new rootfs 4.4. The device appear to boot (LED > is solid green). However, the device only has an > IP address while in uboot. After starting the > kernel, the device does not connect to the network > (confirmed by router connected device list). &by bodhi - uBoot
Preacher, I'll find my original Pogo E02 mtd0 for you. But first, boot into Debian and check for bad blocks, see if there is any: dmesg | grep -i badby bodhi - uBoot
Kernel linux-4.8.3-kirkwood-tld-1 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
1. You should have saved this Pogo E02 mtd0 as the original uboot! It is always better to use the uboot on the same box (unless you already flashed new uboot and did not backup mtd0). 2. How did you copy this file uboot.mtd0.dockstar.original.kwb to / ? Log into stock OS?by bodhi - uBoot
desmond Wrote: ------------------------------------------------------- > Hi, Bodhi. > > I installed uboot using your guide but debian > jessie works too slow for me. I decided to return > to original firmware using environment from here: > http://www.openstora.com/wiki/index.php?title=Defa > ult_environment_of_U-Boot > > > U-Boot 2015.10-tld-1 (Nov 06 2by bodhi - uBoot
jason, > U-Boot 2015.10-tld-1 (Nov 06 2015 - 15:56:21 > -0800) > Seagate FreeAgent DockStar > gcc (Debian 4.9.2-10) 4.9.2 > GNU ld (GNU Binutils for Debian) 2.25 > Hit any key to stop autoboot: 0 > starting USB... > USB0: USB EHCI 1.00 > scanning bus 0 for devices... 2 USB Device(s) > found > scanning usb for storage devices... 0 Storage >by bodhi - uBoot
Of course. However, if your box is not facing the internet, no need to worry. Just be careful, as always: don't run any software that you cant tell whether it is from a reputable repo (such as Debian distribution).by bodhi - Debian
Try using fdisk to wipe and create an MBR partition table, and then using ntfs-3g to format this partition as NTFS. I think it is possible that the Seagte enclosure has something to do with this (they don't expect people to reuse the HDD inside or install another HDD in it).by bodhi - Off-Topic
Seong O Wrote: ------------------------------------------------------- > Dear Bodhi, > > As I got similar problem with my Pogo series V4, I > connected with USB-serial and tried like above. > > But I got result like next, > > root@ubuntu:/home/tmp# ./kwboot -t -B 115200 > /dev/ttyUSB0 -b > uboot.2016.05-tld-1.pogo_v4.mtd0.kwb –p > Sending boot mesby bodhi - uBoot
SiliCAT, > Maybe It's time for me to give up on finding a > perfect approach. I know, been there :) being somewhat a perfectionist myself, sometime it took me hours to debug a problem while I know it would take me a few minutes to implement a sensible solution for it.by bodhi - Debian
Ancient Abysswalker Wrote: ------------------------------------------------------- > Been having issues with the pogoplug native > on-board SATA... When I try to mount a drive that > has a partition on it, it sees no partition, just > the drive (checked using lsblk). However if I try > to plug the drive in by USB it works just fine... > I've been told it might be a cby bodhi - Off-Topic
SiliCAT, > So I use udev rules and scripts. > The scripts works well when I plug in the disk > driver or unplug it from the usb port. But when > the system reboot, the scripts do not work during > the boot time. > I took several hours to test the rules and > scripts, and found it seems the only command that > can be executed in the udev rules at the boot time &gby bodhi - Debian
SiliCAT Wrote: ------------------------------------------------------- > Hi bodhi, > Sorry for report late. > These two days, I have done reboot for nearly 20 > times, but only 1 time, It couldn't find the usb > device, and just at the same time, the sd card > corrupted. > I'm confused, because the day before, it lost usb > device almost every time. Tby bodhi - Debian
You have not done these steps when you installed new u-boot: Flashing Instruction: ..... 9. Erase 1 block starting 0x00100000 /usr/sbin/flash_erase /dev/mtd0 0x00100000 1 Expected output Erasing 128 Kibyte @ 100000 -- 100 % complete 10. Flash uboot environment to 0x00100000 /usr/sbin/nandwrite -s 1048576 /dev/mtd0 uboot.2013.10-tld-5.ox820.environment.img Expected outputby bodhi - uBoot
JoeyPogoPlugE02 Wrote: ------------------------------------------------------- > Up until recently didn't realize you couldn't just > plug a SATA hard drive into a Seagate device. > That's because I didn't have one to realize that. > But as there are USB plugs on the unit so that's > one workaround in the meantime. > > For that matter, do aby bodhi - Off-Topic
If this is a USB hard drive then it is a common issue. If you have serial console or net console, reboot, interrupt console and, ver printenv usb start boot and post the entire log here.by bodhi - Debian
Ancient Abysswalker Wrote: ------------------------------------------------------- > Odd. I am using the files from > uboot.2015.10-tld-1.ox820.bodhi.tar so yes I think > I'm using new uBoot. I'm also using the files from > Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 and > I'm guessing that's where the issue is arising > from? In this case, do I jusby bodhi - uBoot
Ancient Abysswalker, Advise: never post captured images for troubleshooting. If it is a simple problem, then a small screen capture is OK, but text log is always the best way (we can not search for a string in images). Please post text log only. --------- Your problem is because the u-boot envs are old, not uboot.2013.10-tld-5.ox820.environment version. Did you install the new u-boot ?by bodhi - uBoot
Boot with USB rootfs only. And get these outputs: fw_printenv cat /proc/cmdline fdisk -l ls -l /dev/disk/by-label mount Plug the Sata drive in, mount it. Assuming it is mounted at /media/sdb1. Get these outputs: fdisk -l ls -l /dev/disk/by-label ls -l /media/sdb1/by bodhi - uBoot
Ancient Abysswalker Wrote: ------------------------------------------------------- > Sorry. Just to clarify, am I copying the scanning > code bits from section A and the mounting bits > from B into the uEnv.txt file? Or is this a > different method of approaching the boot order > problem? I'm just not sure what bits I'm actually > using here :) hahaha The defby bodhi - uBoot
Sash Wrote: ------------------------------------------------------- > he bodhi. > > i'm using zram on all my small ram devices to > "enlarge" RAM before using slow swap. Have you > tought about updating the rootfs with the zram > option by default? > > its just adding this script to startup: > ZRAM on > Debian I have zswap enabled in thby bodhi - Debian
Here is the general explanation: http://forum.doozan.com/read.php?3,19093 And read section 11 in the installation procedure for this uboot: http://forum.doozan.com/read.php?3,16017by bodhi - uBoot
Sash, Check your /boot/uImage. Was it appended with the ix4 DTB?by bodhi - Debian
See this: http://forum.doozan.com/read.php?2,12096,30563#msg-30563by bodhi - Debian
Sash Wrote: ------------------------------------------------------- > hi > > so 1st tried the k4.6 dtb with k4.8, but no 2nd > sata chip not any lspci output. Please post dmesg output for this.by bodhi - Debian
Reserved 2.by bodhi - Debian
DTBs for Nsa310s and Nsa320s.by bodhi - Debian