from u-boot (saved before changed, see above): MIC>> printenv bootdelay=0 baudrate=115200 loads_echo=0 in_mfg=no ub_mfgphase=0000000 mb_sn=00000000 mtdids=nand0=dove-mtd arcNumber=1789 CASset=min MALLOC_len=5 ethprime=egiga0 bootargs_root=root=/dev/nfs rw bootargs_end=:::dove:eth0:none image_name=uImage sataargs=root=/dev/sda1 rw init=/init video=dovefb:lcd0:1024x768-2by pengu - Debian
After playing around with some other devices ... let's boot this ... | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_ \___/ |____/ \___/ \___/ \__| ** LOADER ** U-Boot 2009.08-svn7881 (Jan 23 2013 - 13:55:26) version: dove-5.3.4 BootROM: Version on chip: 2.33 Sby pengu - Debian
I've got a similar device (LXD8541). It's nearly the same ... CPU is running at 800 MHz. As there is some time in the near future, and I'm working again on other devices.. this is a nice thing too.. I have a working Serial Console .. USB Stick and a SD Card .. what could possibly go wrong ? ;-)by pengu - Debian
same with updated DTB (ex2100) and patches.. so linux-4.17.19 is the last "working" kernel for this box ..by pengu - Debian
sorry for the confusion. mtd layout is working with the provided DTB, chip select isn't working (kernel 4.16) with both. Now, I'm running kernel 4.16.8 with the provided DTB by your patch. [ 0.000000] Linux version 4.16.8 (root@WDebian) (gcc version 7.3.0 (Debian 7.3.0-17)) #1 SMP Thu May 10 13:40:53 CEST 2018 [ 0.000000] CPU: ARMv7 Processor [414fc091] revision 1 (ARMv7)by pengu - Debian
yes .. same here except the flash partitions taken from the EX4100 firmware SDK It's working fine in 4.14x and 4.15x kernel and perhaps 4.16 RC kernels.by pengu - Debian
The EX2100 NAND partition layout is wrong. Please see attached file for the correct one. I hope that the network issues with unpatched kernel 4.16 were fixed ... the values were taken from the EX4100 firmware SDK no network issues but now NAND issues ... [ 5.211797] marvell-nfc f10d0000.flash: too many NAND chips: 8 (max = 4 CS) [ 5.218816] marvell-nfc: probe of f10d0000by pengu - Debian
it's not the uImage...by pengu - Debian
sorry for the late response .. I'm running tvheadend on Debian Jessie or Stretch. When running on Stock WD OS, then the following things has to be done: - depending on the TV Stick you want to use, we need a driver which isn't included in the kernel used by WD - we need all the programs and libs used by Tvheadend on Debian - we have to make shure that its running on startup.by pengu - Debian
The mentioned patch for "mvneta" seems to be in mainline now: commit a59e386c4f4fce346161c0a62a5e1fbc1f435d6f Author: Simon Guinot <simon.guinot@sequanux.org> Date: Mon Nov 13 16:27:02 2017 +0100 net: mvneta: fix handling of the Tx descriptor counter commit 0d63785c6b94b5d2f095f90755825f90eea791f5 upstream. The mvneta controller provides a 8by pengu - Debian
yes, it's running for a fiew months now but I don't use bodhi's rootfs because someone reported problems with systemd I'm using a jessie based rootfs (the one for MCMGen2) which I've updated to stretch.by pengu - Debian
without serial I cannot say more about this but I'll do if I have the time for it. First I need a working box (now, the two ex2u boxes were up and running) and I also got e raspberry pi 3 for serial connection. So let's se whats happening on the EX4100 and EX2100 which also doesn't working at the moment. The last flashed kernel doesn't boot.by pengu - Debian
yes it is!. It's working on the following (tested) devices with Debian Stretch: - Iomega iConnect - ZyXEL NSA325 - ZyXEL NAS326 - WD MyCloud EX2 Ultra - WD MyCloud EX2100 - WD MyCloud EX4100by pengu - Debian
first I have to say thank you to all who makes it possible to use Debian on this box. I'm trying to use debian on this box and also on the EX2100 but I see some differences: The EX2100 is booting fine from NAND but the EX4100 doesn't (for the first time end now). It resulted in the recovery console and SSH on Port 2222. It doesn't matter if I use the stock U-Boot or the ubootby pengu - Debian
I've seen that during several updates from Debian Jessie to Stretch and later "/var/cache/man" isn't accessible so the following should be done before "apt(-get) upgrade": rm -fr /var/cache/man The man page db gets recreated /rebuilt during update so there is no harmby pengu - Debian
I am running into probmehs when not using the default sshd config while updating Debian Jessie to Stretch. There were some unsupported options. It doesn't matter allowing root to login or not.by pengu - Debian
This device is similar to some ZyXEL devices (NSA325v2 / NSA310s / NSA320s) so it has similar issues (power off) This is why I gave away my first device last year. A view months ago I noticed that this issue is gone since Kernel 4.8 on other devices, let's try on this device too. I also noticed that there was introduced a new DTB in Kernel 4.10 for the, I think similar device "Lenby pengu - Debian
@cde, I've done this now on several boxes and no problems (kirkwood, oxnas armhf, x86) - changed the /etc/apt/sources.list (replaced "jessie" with "stretch" - apt update && apt upgrade && apt dist-upgrade && apt autoremove perhaps "mandb" complains about somthing going wrong in /var/cache/man ... the following boxes were suby pengu - Debian
yes, this seems the only working "envs" other than gives gives me a pc : [<0064c700>] lr : [<00620da0>] sp : 005fb1d0 ip : 00000003 fp : 00000002 r10: 00690c80 r9 : 00000001by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > So using the Wiki simple smb.conf, the xfer speed > for 10GB file is 85MB/s and 92MB/s? this were the rates without the mentiond line. I cannot do more on this atm because my NAS326 is gone ... After changing the Stick and successfully booting Debian again, I decided to upgrade the kernel as usual. All good Iby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > Then pengu should post his smb.conf. as I said .. it only needs that line in the smb.conf: min receivefile size = 128k All other stuff makes it worseby pengu - Debian
SAMBA performance .. it needs some tweaking on Kirkwood boxes ... here .. one line is enough ... min receivefile size = 128k 103 mb/s read ... 98 mb/s write ... (windows 10) a little more on my Gentoo Linux box samba --version Version 4.5.8-Debian lsb_release -a No LSB modules are available. Distributor ID: Debian Description: Debian GNU/Linux 9.0 (stretch) Release:by pengu - Debian
bodhi Wrote: ------------------------------------------------------- > pengu, > > > > [1598111.263448] mvneta: mvneta_ethtool_set_wol > ph > > y_id = 0x0 > > This meant you have missed some configs. yeah .. now it's working [ 389.958644] m88e1318_get_wol: phy_id = 0x1410dd1 OK [ 389.963557] mvneta: mvneta_ethtool_set_wol phy_id = 0x1410dby pengu - Debian
no new ext4 partition and the rootfs partition is fine it also cannot be usb stick related .. tested with different USB Sticks (Intenso Basic Line, Sandisk Cruizer Fit, Verbatim Store 'n' Go, Transcend JetFlash 510) and I've seen this on boxes with slightly differend MD numbersby pengu - Debian
Patches applied ... but see here .. [1598111.263448] mvneta: mvneta_ethtool_set_wol phy_id = 0x0 [1598111.268973] mvneta f1070000.ethernet eth0: The PHY does not support set_wol, was CONFIG_MARVELL_PHY enabled? but CONFIG_MARVELL_PHY is enabled. cat .config | grep CONFIG_MARVELL_PHY CONFIG_MARVELL_PHY=yby pengu - Debian
bodhi Wrote: ------------------------------------------------------- > @everybody, > > I need someone to test the new kernel WOL patches > in 4.10.9-mvebu-tld-1 on your box. Please try: > > > ethtool -s eth0 wol g > ethtool -s eth0 wol g Cannot set new wake-on-lan settings: Operation not supported not setting wol but this new kernel and patch fixesby pengu - Debian
a fiew months ago (with Kernel 4.4.2x and OpenWrt patches), I noticed that there were issues while running "locale-gen" (gzip was messed up and "localedef" two or segfaults) Now tried with kernel 4.4.61 and patches from here but same thing ... Perhaps it depends on the exact version of the device, it differs sometimes ... "memtester" is running fine so thisby pengu - Debian
ok .. same as before .. nothing more .. (tested with linux-3.16.42 and linux-4.4.6)by pengu - Debian
same as before.. ... USB 0: host mode PEX 0: PCI Express Root Complex Interface PEX interface detected Link X1 Net: egiga0 Hit any key to stop autoboot: 0 (Re)start USB... USB: scanning bus for devices... 2 USB Device(s) found Waiting for storage device(s) to settle before scanning... 1 Storage Device(s) found reading /uImage .............................................by pengu - Debian