blackdevil, The patch is large and looks pretty bad :) I don't think we should even attempt to retrofit it. If you can find the Linux SATA driver for this SoC that can be used in modern kernel, then I would say attempting to create a DTS for FDT kernel is feasible. If you can't find SATA driver then I would throw in the towel :)by bodhi - Debian
@Juan, This is a typical rootfs mounting problem. - Ensure your rootfs (/ partition) is formatted as Ext3, because your rootfstype env is: rootfstype=ext3 - Label your rootfs (sdxx is the partition letter for you rootfs /) \. In Linux: tune2fs -L rootfs /dev/sdxx - Set your rootfs label in bootargs in serial console setenv usb_root 'LABEL=rootfs' If you have 2 partitiby bodhi - uBoot
shv, Take alook at how the rescue system and the ubifs system is booted in the envs set by Jeff's script: bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run sata_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset force_rescue=0 force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0xby bodhi - uBoot
ingmar_k Wrote: ------------------------------------------------------- > Thank you very much for the hint! > > I just ran into a kernel oops with a Goflex-Net > and Kernel 3.16.3 and samba over eth0. > Seems this fixed it. At least I hope that it did. I've also pached the kernel to set it to default off (see the patch in the kernel release thread).by bodhi - Debian
Kernel linux-3.17.0-oxnas-tld-1 package was uploaded. Please see 1st post for download link.by bodhi - Debian
anto, > at last after 2 > years gathering dust I can finally use my pogo pro > to play music! Cool! glad to hear a success story :)by bodhi - Debian
Gravelrash, This is a nice writeup: http://forum.doozan.com/read.php?3,12261 I've been runing a cluster of Pogos with nfsroot on a GoFlex Net SATA for about a year now. All connected with Gbit Ethernet. It's best to run NFS V3 with these Pogos, easier to make it work.by bodhi - Debian
@blackdevil, Quote> U-Boot 2008.10-mpcore (Nov 11 2012 - 16:30:36) > Whitney model:(HALFDOME) release v1.2-beta2 > Whitney # boot > Unknown command 'boot' - try 'help' > Booting in uboot-console with "run bootcmd"-cmd > works fine. This u-boot is quite old and customized by Seagate. So I suspect that they have removed the boot command.by bodhi - Debian
@shv, If you've installed directly from stock to the new u-boot, you've missed this. To boot stock kernel from davygravy's or jeff's u-boot: pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi Jeff's script copies the orginal u-boot to NAND rootfs. The above pogo_bootmcd will load u-boot from mtd2 and that will boot uImage (mtd1). And then the mtd1by bodhi - uBoot
> > I successfully unbricked the Goflex Net device > using a J-link JTAG interface together with > OpenOCD. I read out the first 64 KB of the flash > and compared it to > uboot.2014.07-tld-1.goflexnet.mtd0.kwb. The > overall data structure was the same but some bytes > were different. After I flashed the file again > with the JTAG interface the device is workinby bodhi - uBoot
jan, I found my old backup mtds (from a couple years ago!). If you think your stock mtd2 is indeed messed up (after restoring the envs like I mentioned), and still need it then I will upload.by bodhi - Off-Topic
jst818 Wrote: ------------------------------------------------------- > After upgrading to kernel 3.17 ftd, 4a method, can > those file be deleted ? > > /boot/linux-headers-3.17.0-kirkwood-tld-1_1_armel. > deb > /boot/linux-image-3.17.0-kirkwood-tld-1_1_armel.de > b > /boot/zImage-3.17.0-kirkwood-tld-1 Yes, remove them. You can always redownload if needed, orby bodhi - Debian
jst818, Which rootfs are you running? If it is not in your current rootfs, install with: apt-get u-boot-toolsby bodhi - Debian
Kernel 3.17.0-kirkwood-tld-1 package was uploaded. Please see 1st post for download link. This is the first FDT kernel in my continuing release series for Debian Kirkwood boxex. So please read the new installation instruction even though you've installed these kernels before and familiar with the installation.by bodhi - Debian
Jan, This is stock kernel. But the envs look like have been changed (I could be wrong). It's best that you find the original envs or ALARM envs and see if you need restore them. If what you want is to run stock as original.by bodhi - Off-Topic
@addy75, Whatever software you have installed, do some research on this. It's not standard behavior. Perhaps what you've been seeing have something to do with this. [ 30.106761] softdog: Software Watchdog Timer: 0.08 initialized. soft_noboot=0 soft_margin=60 sec soft_panic=0 (nowayout=0)by bodhi - Debian
Hi Jan, Those pogoplugs were installed with Arch Linux ARM: /lib/modules/2.6.31.6_SMP_820 - MTD definition is done with u-boot envs. You can define them anyway you want and the kernel will pick it up as specified. The boot mtd is what need to be correctly specified, since that's where u-boot resides. The rest is up to us. Stock mtd2 contains rootfs because that's where the manuby bodhi - Off-Topic
Ah, I see. Well done :) And to start netconsole: setenv preboot 'run preboot_nc'by bodhi - uBoot
You are using old kernel? dt_sata_boot=ext2load ide 0:1 $uimage_addr /boot/uImage_2.6.31.14_OX820_1.2_shv.Pro; bootm $uimage_addrby bodhi - uBoot
Jan1973, I remember now. Your MTD layout is orginal or Arch (WarheadsSE version). We have new u-boot and kernel, which are most users in this forum use to install on Pogo V3 Pro/Classic: http://forum.doozan.com/read.php?2,16044 http://forum.doozan.com/read.php?3,16017,page=1 The MTD content is still basically the same, except that we've redefined it: from dev: size erasesizeby bodhi - Off-Topic
devinger, Remove the $ > setenv set_bootargs_usb 'setenv bootargs > console=$console root=$usb_root > rootdelay=$rootdelay rootfstype=$rootfstype > $mtdparts usb-storage.quirks=0x0bc2:0x3321:u' >by bodhi - uBoot
Cool! However, one more thing to keep in mind is: If you have multiple drives plugged in, then the boot drive is not guarantee to be 0: it could be 1:, because the way the Pogo E02 starts the drives, whichever come up first will be 0:, then 1:, … so on. A very good way (but not foolproof) is to plug that boot drive into the USB port right next to the Ethernet port. All things equal (speedby bodhi - Debian
BTW, I'm creating a new scan script that will be a little bit more resilient for multiple disks types. I was planning include it in the default envs for the next u-boot release.by bodhi - Debian
@Almaz, First, do you have 1 partition where your rootfs resides and no separate /boot partition? and do you have only one disk or multiple disks? What ever partition that contains /boot/uImage is the device being detected by usb_scan. If /boot is the 1st partition in the 1st disk then usb_device is 0:1 (if there is only one device). So if you change the /boot to sda2 then usb_device wilby bodhi - Debian
According to the above, you are running with 128M RAM, so it does look OK: KiB Mem: 121756 total, 119448 used, 2308 free, 16208 buffersby bodhi - uBoot
begrenzungsfaktor, As ingmar said, I did not include it in the kernel build for 3.16. So either you compile it or wait until 3.17 release, perhaps a week from now, time permitted.by bodhi - Debian
jan1973 Wrote: ------------------------------------------------------- > Hi, > > I have a bricked pogoplug pro. As far as I can > tell only the mtd2 rootfs has been corrupted, so > I'm looking for a nanddump with the orignal > pogoplug software on it. > > Thanks for your help! > > Jan It's been so long ago, I'm not sure I can find my mby bodhi - Off-Topic
addy75, See above: http://forum.doozan.com/read.php?2,14351,18279#msg-18279by bodhi - Debian
Almaz Wrote: ------------------------------------------------------- > I guess, it's impossible to boot from raid. > Before I start playing with uboot setting, is it > possible to boot from another partition such as > /dev/sda2? Yes, you can boot from any partition, providing the u-boot env is set correctly to boot that specific partition. The device in ext2load commandby bodhi - Debian
@Dale, > If I set any machid regardless of arcNumber it > will hang at uncompressing Kernel, I will see if > any machid's work, maybe this kernel doesn't > support or is not compiled to anything other than > OpenRD? Probably. If you can find the link to the source code to build VAMP, post here and I'll take a look. As right now, it is running fine, so thereby bodhi - uBoot