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
DTBs for Asus_m25, Netgear_Stora, Qizhitong_501m_v2.by bodhi - Debian
Sash, Try using the kernel 4.6 DTB with kernel 4.8: http://forum.doozan.com/read.php?2,12096,30563#msg-30563by bodhi - Debian
Looks like PCI is broken in kernel 4.8 due to the difference in DTS. So if you have the NSA325 v1/v2, the Pogo V4, and the Iomega ix4 200d, please replace the DTB with the kernel 4.6 DTB (attached in this post). mv /boot/dts/kirkwood-nsa325.dtb /boot/dts/kirkwood-nsa325.dtb.v4.8 cp -a kirkwood-nsa325.dtb /boot/dts/ mv /boot/dts/kirkwood-pogoplug_v4.dtb /boot/dts/kirkwood-pogoplug_v4by bodhi - Debian
Sash, Kernel 4.6 PCI is OK. Try install that version and let me know. QuoteUpdated 20 May 2016: Kernel linux-4.6.0-kirkwood-tld-1 package has been uploaded. The following features were added/updated:by bodhi - Debian
It's been a long time. So I'm not sure if this will work, try: ip route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.2.1 dev wlan0 where 192.168.2.1 is your router.by bodhi - Debian
Problem with PCI (i.e. USB 3.0 and other PCIe interfaces) in kernel 4.8. Fixed in the following 3 posts.by bodhi - Debian
Sash Wrote: ------------------------------------------------------- > yep there seems to be a problem with the bus, else > there should be an output when calling lspci, > right!? > i have posted the dmesg above. PCI seems broken. I'm investigating this.by bodhi - Debian
Hold on to installing this kernel, possibly the USB 3.0 interface is broken.by bodhi - Debian