just a little hint, if you may run into some strange behavior... you've installed spl with 850MHz on NAND right now. Medion came with 750MHz by default. I noticed that commands like "agt-get update && apt-get upgrade" lead to segmentation fault when trying to create cache. With 800MHz it worked quite acceptable for me. Also our device doesn't have active cooling (no faby alexinc - Debian
It's getting more and more wired. Although java -version states a running headless environment, starting an java based application leads to DEBUG MESSAGE: Atomic load(jlong) unsupported on this platform with Oracle Java8. Running openjdk11-headless is working, but pretty slow and CPU hungry! Running Debian 11 now, so going back to an older version and trying again will be my task for tomoby alexinc - Rescue System
So it's kernel related! Since 5.x Java is crashing with root@debian:~# /home/ejdk1.8.0_211/linux_arm_sflt/jre/bin/java -version [ 569.830438][ T419] 8<--- cut here --- [ 569.834188][ T419] Unhandled fault: page domain fault (0x81b) at 0xb67b6000 [ 569.841203][ T419] pgd = 2cb67a2d [ 569.844587][ T419] *pgd=649e5831, *pte=631bb59f, *ppte=631bbe6e [ 569.851527][ T419]by alexinc - Rescue System
Exactly this is my plan for tomorrow. ;-) Will let you know then.by alexinc - Rescue System
I'm not in a hurry. Just noticed today, that on rescue disk (800MHz SPL and Debian Wheezy) Oracle Java headless embedded was starting just fine, no segmentation fault (which i get at self compiled OpenWRT right now too, btw.). Now i need to find out, if segmentation fault was caused by upgraded Debian or the last kernel update. Once again quite a few setups to check...by alexinc - Rescue System
Quote Perhaps the 2013 SPL and u-boot combo would work It's also 800MHz SPL...by alexinc - Rescue System
is there any easy way to convert nand spl to disk spl first? would love to test sata boot with 750/725MHz first...by alexinc - Rescue System
> The Pogoplug V3 can run at 850Mhz without problem. > We have not seen report that this box might not > work with the overclock SPL. That's why I wanted > to see it running Debian. I found some postings in here, that mentioned instability and temperature issues with higher CPU speed, but all were like going back to stock or keeping the device out of its case (what I'mby alexinc - Rescue System
just some short news: - ext4 partition not read by uboot seems to be related to mkfs.ext4 ^64, so it gets formatted 32 bit. - segmentation faults and apt cache errors are related to spl being 850MHz! using dirty spl from "rescue disk" is running 800MHz and a bit more stable, but not enough, as stock spl is 725MHz. now i'm having the trouble that no one ever created spl with 725by alexinc - Rescue System
so mkfs.ext4 -E lazy_itable_init=0 -L rootfs /dev/sda1 didn't work out... OX820> ide reset Reset IDE: Bus 0: OK Device 0: Model: Crucial_CT275MX300SSD1 Firm: M0CR070 Ser#: 17251799E2D8 Type: Hard Disk Supports 48-bit addressing Capacity: 262321.6 MB = 256.1 GB (537234768 x 512) OX820> ext4ls ide 0:1 / <DIR> 4096 . <by alexinc - Rescue System
QuoteExt4 should work. Probably you did not format the Ext4 file system with "lazy_itable_init=0" option. Ext4 rootfs must be finalized before it can be used for booting. You're right of course. Didn't know that and will try asap. QuoteTry apt-get clean dpkg --clear-avail apt-get update I tried already almost everything, also reinstalling apt-get, etc... it was alwby alexinc - Rescue System
i notice loosing network connection quite often [ 5434.888911][ T3749] oxnas-dwmac 40400000.ethernet eth0: Link is Down [ 5438.009594][ T3749] oxnas-dwmac 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off also apt-get update often needs to be started, as apt cache quite often fails with segmentation fault or cache crc error!?by alexinc - Rescue System
just for references... :-) Stage1 (SPL) + U-Boot from "uboot.2015.10-tld-2.ox820.bodhi.tar" on NAND U-Boot SPL 2013.10-tld-4 (Sep 07 2014 - 14:10:12) Boot device: NAND Attempting to set PLLA to 850 MHz ... plla_ctrl0 : 0000020a plla_ctrl1 : 00330000 plla_ctrl2 : 0065008b plla_ctrl3 : 000000f1 PLLA Set U-Boot 2015.10-tld-2 (Oct 21 2017 - 22:00:02 -0700) OXNby alexinc - Rescue System
ok, got it! ;-) [ 9.325304] Please append a correct "root=" boot option; here are the available partitions: setenv bootargs "console=ttyS0,115200n8 root=/dev/sda2 rootdelay=3 rootfstype=ext2"by alexinc - Rescue System
without appending DTM should be like: OX820 # ext2load ide 0:2 60000000 /boot/uImage 4600448 bytes read in 611 ms (7.2 MiB/s) OX820 # bootm 60000000 ## Booting kernel from Legacy Image at 60000000 ... Image Name: Linux-4.14.180-oxnas-tld-1 Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 4600384 Bytes = 4.4 MiB Load Address: 60008000 Entry Point: 600by alexinc - Rescue System
thats what i instantly did already this afternoon. i got this even before posting my last posts, but as results were the same, i thought it wouldn't be that essential. ;-) the question is now, where is the difference between Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 and Debian-4.14.180-oxnas-tld-1-rootfs-bodhi.tar.bz2 when both just got decompressed to rootfs partition with almost saby alexinc - Rescue System
whatever i'm doing now, it always ends in loading ## Flattened Device Tree blob at 61000000 with OX820 # printenv SET_dtb=fdt addr ${fdtaddr} ; fdt header autoload=no baudrate=115200 bootcmd=run ideboot bootdelay=3 bootnew=bootm 60000000 - 61000000 bootold=bootm 60000000 console=console=ttyS0,115200n8 ethact=mii0 ethaddr=06:05:C2:E8:D1:88 ext2_dtb=ext2load ide 0:2 61000000 /by alexinc - Rescue System
here we go with 3.17 for now. have to flash newer u-boot later for running latest rootfs + kernel. U-Boot SPL 2013.10-ga72eb8f-dirty (Feb 19 2014 - 15:21:12) Boot device: SATA Attempting to set PLLA to 800 MHz ... plla_ctrl0 : 0000030a plla_ctrl1 : 00400000 plla_ctrl2 : 007f0068 plla_ctrl3 : 00000193 PLLA Set Bus 0: OK Device 0: reading bootargs.bin reading u-boot.imgby alexinc - Rescue System
Alright, i owe you something... ;-) here is, what i didn't expect. booting from sata with "schnee's rescue disk". 3 partitions "BOOT" (vfat), "rootfs" (ext2), "home" (ext2) and stock u-boot. deleted all files on "rootfs" after successful first boot (Debian 3.17.0) which then crashed after automatic upgrade to kernel 4.1.0! extractedby alexinc - Rescue System
Since 2018 (OpenWRT 18.06) there is no more OpenWRT u-boot, it's booting with vendor u-boot.by alexinc - Rescue System
The last dance - as expected, complete nand dump from new box with openwrt written to old box without any problems, but: Stage-1 Bootloader Tue Aug 9 16:44:00 CST 2011 Attempting to set PLLA to 750MHz ... plla_ctrl0 : 0x0000000A plla_ctrl1 : 0x000F0000 plla_ctrl2 : 0x001D01A0 plla_ctrl3 : 0x00000017 PLLA Set Setup memory, testing Reading NAND, Image 0 Hdr len: 0x0001A94Cby alexinc - Rescue System
did you read, that i copied the file to nand (/usr/sbin) too for testing purpose? ;-) i checked around and found a post that explained you cannot use a "random" compiled binary on openwrt. nand-utils have to be compiled for openwrt... i'm just to tired to search for it again. ;-) just for the record: root@OpenWrt:# cat /proc/mtd dev: size erasesize name mtd0: 0004000by alexinc - Rescue System
your welcome! ;-) glad if i can give back just a little bit of what i learned the last weeks. hopefully i'm not forgetting everything throughout the coming months/years again. will report back, what the openwrt dumps are doing to the old device. there's a little, little hope as partition layout is completely different and booting works with stock u-boot nowdays. let's keep fingeby alexinc - Rescue System
i found out that i had to install nand-utils from openwrt, not the ones provided in this forum. everything worked as expected. just have to get home to nandwrite on old device - not that i'm expecting miracles, but afterwards i've tried every possible combination i could imagine. ;-)by alexinc - Rescue System
for now i already installed openwrt. wanted to make nanddump too (for nandwriting on old box as a last attempt), but there it says: root@OpenWrt:/tmp/sda1/tools# ls -l -rwxr-xr-x 1 root root 1616492 Nov 15 2010 busybox -rwxr-xr-x 1 root root 787036 Jun 20 2011 e2fsck -rwxr-xr-x 1 root root 25632 Jun 30 2014 flash_erase -rw-r--r-- 1 root rby alexinc - Rescue System
Latest news: got my new P89625 today and as it came with latest/last firmware i first started nanddump everything with some little differences in mtd file size afterwards, compered to the dumps i used earlier. then i started nandwriting mtd1 till mtd7 from scratch (after nand erase.chip) on my old device. everything went smooth so far and environment included ethaddr from my newly aquired deviby alexinc - Rescue System
Just caught a new unused one at eBay for a few bucks, as Ctera isn't available over here in Germany and price range is not attractive when importing. So after getting it and doing the official firmware upgrade, I'm up for everything... Should backup the whole system then and still not sure if going with Debian or OpenWRT. Any hints what i should try before flashing it in regards of usinby alexinc - Rescue System
There are still some things i could try after vacation. First of all it would be interesting to find out how and what to create in ubi partition. I know there were some volumes like rootfs, kernel, uboot_env and uboot_env2... That's what uboot stage 2 is missing right now - possibility to write to uboot_env volumes. The other option is unsquashing openwrt--ubifs-sysupgrade.tar, which leavby alexinc - Rescue System
I will! :-) Maybe I'll try the one or other thing from time to time. But everything I've read about decompression error leads to faulty RAM. :-/by alexinc - Rescue System
I'll have a look, but first one week vacation after all this mess and intensive learnings at late nights... :-Dby alexinc - Rescue System