Koen, QuoteBodhi it really amazes me how you can troubleshoot these devices remotely based on just some short log. Below the boot log of booting with the dove-dove-db.dtb file. Cool! we got pretty far for a first boot :) The console boot log has a lot of information even though sometime it seems too cryptic. [ 0.000000] Division by zero in kernel. [ 0.000000] CPU: 0 PID: 0 Comm:by bodhi - Debian
Try setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x3000000 /boot/uImage; ext2load usb 0:1 0x4000000 /boot/uInitrd' setenv bootcmd_exec 'run set_bootargs; run bootcmd_usb; bootm 0x3000000 0x4000000' run bootcmd_execby bodhi - Debian
Koen, It does not look like the DTB. Your serial console show that something went wrong after the uImage was loaded. MIC>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial' MIC>> setenv bootcmd_usb 'usb start; ext2load usb 0:1 0x2000000 /boot/uImage; ext2load usb 0:1 0x3000000 /boot/uInitrd&by bodhi - Debian
This is an over-the-top article. I smell something not rigth is going happen to Linux. Perhaps Gravelrash was right :) https://www.newyorker.com/science/elements/after-years-of-abusive-e-mails-the-creator-of-linux-steps-asideby bodhi - Off-Topic
buec65, > but no access to USB, IDE or tftboot > > U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 > -0700) > ZyXEL NSA325 2-Bay Power Media Server > > SoC: Kirkwood 88F6282_A1 > DRAM: 512 MiB > WARNING: Caches not enabled > NAND: 128 MiB > In: serial > Out: serial > Err: serial > Net: egiga0 > MV88E1318 PHY initialized onby bodhi - uBoot
Koen Wrote: ------------------------------------------------------- > Stock OS doesn't offer a terminal or anything > useful to explore the system with. So I've taken > the USB stick from the T50 and used the following > commands from the HP T5335 topic. It starts > loading the kernel but hangs. > > > MIC>> setenv set_bootargs 'setenv bootarby bodhi - Debian
Nicely done Koen! This box has a different u-boot U-Boot 2009.08-svn7881 (Jan 23 2013 - 13:55:26) version: dove-5.3.4 The HP T5335z: U-Boot 2009.08 (Aug 24 2011 - 15:11:17)HP version: 5.4.2-V28 Basically the same u-boot envs can set up to boot Debian USB rootfs. The DTS will be based on the same reference Dove dts, but slightly different, though. They might or might not use the samby bodhi - Debian
cdlenfert, > Thanks for finding that. I'm not sure what to do > with it however. My EO2 is running stock OS, so > shouldn't these stock envs already be set? No, these envs are from Jeff's old u-boot setup. > I don't > have serial console hooked up (though I could if I > had to, but would rather not disasemble if I don't > need to). &gby bodhi - Debian
jasper, > Attached is the session log. The log text file has > been re-formatted for Windows. Pogoplug OS has > been damaged as explained earlier. Please let me > know how I should proceed next. There are 2 things you need to do here. 1. You need to get flash new u-boot and its envs image after you logged into Debian. This is to make permanent. https://forum.doozan.com/rby bodhi - uBoot
sebr Wrote: ------------------------------------------------------- > I can confirm that if I disable WOL the system > shuts down properly. > Just strange that it appears after later kernel > update. WOL has been enabled like forever (never > used tho). It is actually invoked in the kernel behind the sceen to check if you have WOL enable. Even though you never use it expliby bodhi - Debian
Gravelrash Wrote: ------------------------------------------------------- > Read more to me that the Linux Foundation that pay > his wages, have told him to play nice or they will > fork the project and stop paying his wages..... > have you seen who is on and runs the Linux > Foundation. I hope that's not what really happened. I think it is hard to threaten Linusby bodhi - Off-Topic
If you read the flame war in the comment section, very entertaining :)) The flame war is even more entertaining at Phoronix: https://www.phoronix.com/scan.php?page=news_item&px=Linux-Kernel-Code-of-Conductby bodhi - Off-Topic
sebr, > Thank for sorting this out bodhi. What WOL bug you > talk about / will it be fixed in next kernel? > I remember only the NAS326 had some trouble with > the WOL. Never used the WOL function on NSA325 > tho. It is not related to the kernel. It seems that systemd has some problem dealing with WOL. To turn it on/off you'd use ethtool. So run that and check if youby bodhi - Debian
https://lwn.net/Articles/764902/by bodhi - Off-Topic
megal0maniac, I've just booted up the EA4500. I have no problem with the switch at all. root@EA4500:/boot# lst uImage -rw-r--r-- 1 root root 4170563 Aug 26 02:31 uImage root@EA4500:/boot# lst /boot/dts/kirkwood-ea4500.dtb -rw-r--r-- 1 root root 12419 Aug 25 12:11 /boot/dts/kirkwood-ea4500.dtb root@EA4500:/boot# uname -a Linux EA4500 4.18.4-kirkwood-tld-1 #1 PREEMPT Friby bodhi - Debian
> but I have all 5 > interfaces and can do fancy thinks like > > ip link set ethernet1 down > That's the beauty of the DSA switch! And the DSA design is really cool how it works internally.by bodhi - Debian
Yes, it was systemd problem dealing with WOL. My NSA310S (which is identical to the NSA325 in most aspects regarding network and WOL) running sysvinit does a reboot or shutdown without problem.by bodhi - Debian
Here it is. ethact=egiga0 bootdelay=3 baudrate=115200 mainlineLinux=yes console=ttyS0,115200 led_init=green blinking led_exit=green off led_error=orange blinking mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data) mtdids=nand0=orion_nand partition=nand0,2 stdin=serial stdout=serial stderr=serial rescue_installed=0 rescue_set_bootargs=setenv bootargs console=by bodhi - Debian
cdlenfert Wrote: ------------------------------------------------------- > Will the same chainloading approach > (post > 1 with updated boot command in > this > post) I did on the pogoplug mobile work for > the pogoplug E-02 model? I'm ready to make the > leap on that device over to Debian, but still want > the stock OS as a fallback recovery system. >by bodhi - Debian
Hi megal0maniac, > Interestingly, the dtb from your previous post > (https://forum.doozan.com/read.php?2,26854,36051#msg-36051) > works. Good to hear there is a work around! > Not sure of the difference between that one and > the one in the latest kernel There might have been a change in mainline DTS that were brought in without us knowing about (through include statby bodhi - Debian
sebr, This might be a systemd problem. Or the WOL bug. I'll see if I can repeat it only NSA310S booting with sysvinit. In the mean time, you could turn off WOL using ethtool, and see if you can shutdown cleanly.by bodhi - Debian
sebr, > I see exactly the same error on my NSA325v2 > > > [ 160.603907] __nand_correct_data: uncorrectable > ECC error > [ 160.609263] __nand_correct_data: uncorrectable > ECC error > [ 160.623771] print_req_error: I/O error, dev > mtdblock5, sector 0 > [ 160.634636] __nand_correct_data: uncorrectable > ECC error > [ 160.639977] __nand_corrby bodhi - Debian
Hi Koen, Thanks for trying! > HP>> setenv set_bootargs 'setenv bootargs > console=ttyS0,115200 root=LABEL=rootfs > rootdelay=10 ${mtdparts} video=armada-drm splash > quiet earlyprintk=serial' > HP>> saveenv BTW, you should not do saveenv while testing. That way, the new setting will be applicable only for this boot, and after reboot the box willby bodhi - Debian
Koen, Your boot log above indicated that both u-boot and the envs are OK: U-Boot 2017.07-tld-1 (Nov 01 2017 - 00:58:19 -0700) HP Thin Client T5325 SoC: Kirkwood 88F6281_A0 SPI: ready DRAM: 512 MiB WARNING: Caches not enabled MMC: SF: Detected mx25l8005 with page size 256 Bytes, erase size 64 KiB, total 1 MiB In: serial Out: serial Err: serial Net: egiga0 88Eby bodhi - Debian
QuoteCopy of large files to/from external HDD with NTFS format via network (SMB) This also a big factor: SMB. Compare your smb.conf with ones in Wiki thread: https://forum.doozan.com/read.php?2,23630 QuoteSamba Samba smb.conf for a simple set up HowTo setup Samba/CIFS sharesby bodhi - Debian
sebr, > How to find out what cost so much performance and > tweak it? - See which version ntfs-3g that is used by the stock FW. And which is used by Debian. - Compare the mount options after the disk is mounted in both cases. Also try remount with big_writes option. This should bump the performance quite a bit. Assuming it is mounted at /media/sdb1. mount -o remount,noatby bodhi - Debian
Koen, > I'm not sure what is going on. Should I try to > reflash the 2 uboot files? I think you did not install u-boot and the envs correctly. But let's try this first. Your envs are located in mtd2 now. root@debian:~# cat /etc/fw_env.config /dev/mtd2 0x00000 0x10000 0x10000by bodhi - Debian
Let's try this new DTB. And probably we need the video to be precisely what we want. However I am not quite sure what the correct parameter is (could not find anybody using the Armada DRM). Let's try armada-drm (it's the name of the module). I don't think we need resolution or device. set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtby bodhi - Debian
Koen, 1. You are trying to ping the router T5325> ping 192.168.1.1 But your U-boot env is not in the same subnet ipaddr=192.168.0.41 2. In Debian, your envs probably were not in the right place. Warning: Bad CRC, using default environment ... eth1addr=00:00:11:22:33:45 Check cat /etc/fv_env.configby bodhi - Debian