bodhi, works like a charm! Thanks man, problem solved.by saschadd - Debian
> Regarding the uEnv.txt. No we cannot use that capability, it is not in stock u-boot. Okay, do you think there will be an updated uboot package like for the kirkwood boxes or are there too many different mvebu boxes around to make that? Or do we have to gather more infos about those boxes first? So by now i can only set the systemd in serial console. Do i have to add it to that lineby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Which box is it? the EX4100 > I am not sure what you meant. i meant the uEnv.txt file > But first, please post output of the envs listed in serial console Marvell>> printenv CASset=max MALLOC_len=5 MPmode=SMP autoload=no baudrate=115200 boot_order=hd_scr usb_scr mmc_scr hd_img usb_iby saschadd - Debian
bodhi, update to Kernel 4.13.2 worked well. Only issue, fw_printenv gives me a bad crc fw_printenv Warning: Bad CRC, using default environment bootargs= bootcmd= bootdelay=2 baudrate=115200 arch=sandbox cpu=sandbox board=sandbox board_name=sandbox stdin=serial,cros-ec-keyb,usbkbd stdout=serial,vidconsole stderr=serial,vidconsole ethaddr=00:00:11:22:33:44 eth1addr=00:00:11by saschadd - Debian
bodhi, update to Kernel 4.13.5 worked without problems! Thanks again for your great work.by saschadd - Debian
bodhi, debian stretch rootfs is up an running on the nsa325v2. thanks for your work man!by saschadd - Debian
bodhi, yes debian stretch is up an running. But still with fan running at full speed. How or where could i add that WDMyCloud_EX4100_GPL_v2.30.165_20170321/firmware/module/crfs/script/system_init you posted? or should we try to get this mcm daemon running? i should have some spare time for testing things.by saschadd - Debian
hmartin Wrote: ------------------------------------------------------- > Quotebodhi > I'll look into compiling this daemon and after > that you can test it on your box. > > > I compiled mcm-daemon, but it doesn't work on the > EX2100 yet (I am still investigating uP > communication problems). > > Perhaps you can try it on the EX4100. > >by saschadd - Debian
bodhi, i just tried to install your new Debian-4.12.4-mvebu-tld-1-rootfs-bodhi.tar.bz2 rootfs on the ex4100 I followed your instructions until cp -a zImage-4.12.4-mvebu-tld-1 zImage and then added copy armada-388-wd-ex4100.dtb and armada-388-wd-ex4100.dts to boot/dts (those files are not in the dts folder already) cat dts/armada-388-wd-ex4100.dtb >> zImage.fdt mkimage -A arm -Oby saschadd - Debian
bodhi, sorry for the delay, to much work to do. ;) > What is the EX4100 fan behavior in u-boot? does it spin at nomal speed? in u-boot it spins at full speed, at some point in booting the stock os it switches to slower speed. > And how about inside stock OS? does it spin slower, and is there a fan control tool that you can run in the Web interface or at command line? there isby saschadd - Debian
bodhi Wrote: > The DTS file right now is OK to use. It is not completed, because we would need the GPIOs defined to > control the LEDs. But other than that, You can start using the system. And as you are running it, you probably will find some minor stuff that we need to add. Thanks for the info. Well one major issue is the fan speed. For productive use i way to control the fan is needby saschadd - Debian
Thanks guys for the inputs. I got it copied with bodhis approach with 2 usb drives which worked very well. Now i only have to activate harddrive sleep as they are still always spinning. But thats another thing to do which is not part of this thread. ;)by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > I'm still exploring different approaches to shutdo > wn: > http://forum.doozan.com/read.php?2,35291,35538,pag > e=2#msg-35538 > > In the mean time, after you do "shutdown -h now", > wait for 30 seconds or a minute and it safe to tur > n off power. If you aby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > > cant find the up_send_ctl.c file but attached th > e > > /usr/local/modules/usrsbin/up_send_ctl for your > in > > formation. > > I've also found this binary in the GPL. Good. Have you found the up_send_ctl.c file?by saschadd - Debian
bodhi, cant find the up_send_ctl.c file but attached the /usr/local/modules/usrsbin/up_send_ctl for your information.by saschadd - Debian
bodhi, this search gives many results. so many things seem to be done by such scripts or binary. /usr/sbin/raid_config:up_send_ctl ErrStatus %d 0 /usr/sbin/raid_config:up_send_ctl VolClean /usr/sbin/raid_config:up_send_ctl VolStatus %d 6 %d 1 /usr/sbin/raid_config:up_send_ctl VolStatus %d 6 100 1 /usr/sbin/raid_config:up_send_ctl VolStatus %d 6 0 0 /usr/sbin/raid_config:up_send_ctlby saschadd - Debian
bodhi, here the script #!/bin/sh kill_program() { killall quotacheck killall lighttpd killall chk_hotplug killall system_daemon killall crond killall op_server killall fan_control killall temperature_monitor 2> /dev/null killall set_pwm 2> /dev/null killall sysinfod 2> /dev/null } one_bay_shutdown() {by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > saschadd, > > please log in stock OS, and search: > > > cd / > find . | xargs grep -i 'send cmd to micro-p to shu > tdown' -d skip > > gives the following ./usr/sbin/shutdown.sh: echo "send cmd to micro-p to shutdown"by saschadd - Debian
bodhi, here the shutdown log when i hold the front button. root@WDMyCloudEX4100 / # Push Power off key shutdown Push Power off key shutdown Push Power off key shutdown killall: quotacheck: no process killed killall: lighttpd: no process killed killall: op_server: no process killed dry_total_size:56022 dry_total_size:0 dry_total_size:11564 dry_total_size:30303 dry_total_size:5991by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > 2. Power off is hard to find in the GPL. So it wil > l take time. In the mean time, boot to stock, log > in as root, and shutdown with > > > poweroff > same thing as in debian happens, display stays on, fan is spinning BusyBox v1.20.2 (2014-10-30 15:28:01 CST) built-in shell (ash) Enter &by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > 1. Temporarily remove the MAC address from /etc/network/interfaces (to let the kernel generate random MAC as before). Shutdown. > - Connect serial console, and ethernet cable to port 1. > - Power up, interrupt serial console and > setenv ethact egiga1 > boot > > Please post the boot log. Marby saschadd - Debian
bodhi, i set the mac adresses i found in stock. strange that they are the same, only difference between egiga0 and egiga1 is the interrupt. well, i set it in debian /etc/network/interfaces and tried port 1 doesnt work port 2 works out of the box as eth0 poweroff doesnt work as wanted from ssh. so it is not an uart connection issue.by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Yes. That's why you need to specify the real ones > inside /etc/network/interfaces. This is a side eff > ect of our setup to protect the DTB from corrupti > on by stock u-boot. good to know ;) do i have to do it now or can i just leave it like that for now?by saschadd - Debian
bodhi, the mac adresses seem to be generated at boot. i noticed this already in stock firmware that the mac adresses seem to be different on every boot. after updating the debian system and rebooting ifconfig gives me the following eth0 Link encap:Ethernet HWaddr 9a:09:78:fd:ca:84 inet addr:192.168.178.46 Bcast:192.168.178.255 Mask:255.255.255.0 inet6 addr:by saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > And what is the output of > > > cat /etc/udev/rules.d/70-persistent-net.rules > cat /lib/udev/rules.d/75-persistent-net-generator. > rules | grep KERNEL > > > 70 and 75 might be diferent numbers (I forgot the > exact number in these names in this MVEBU rootfs : > ) following thby saschadd - Debian
bodhi Wrote: ------------------------------------------------------- > Does this box really have 2 Ethernet ports available? you might want to switch the cable to the other port. yes it has 2 gigabit ports available which could be set for Port-Trunking or Fail-Over-solution. interesting that switching to port 2 it works and gets an ip addressed. > Try these > > cat /etc/nby saschadd - Debian
No, network is not working. [ 16.072258] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.3.1 Copyright 2004-2014 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ Listening on LPF/eth0/de:a1:a8:5b:38:66 Sending on LPF/eth0/de:a1:a8:5b:38:6by saschadd - Debian
bodhi Wrote: > Did the fan turn off? fan stays on at full speed (like all the time when i boot to debian) > Was the light still on? light keeps blinking (like all the time when i boot to debian) > Or could it be that it is not working because i am connected to uart via picocom? > It is not very likely. But you can try that to see if it has any effect. cant try yetby saschadd - Debian
bodhi, is it possible that shutdown is not yet working correctly because we have not everything set correctly? Following the outputs from two different ways to shutdown. In the second try it seems to work but the box doesnt switch of. Or could it be that it is not working because i am connected to uart via picocom? shutdown now Broadcast message from an (ttyS0) (Sun Using makefile-by saschadd - Debian
bodhi, you were right. i was sure that it might be a "small" mistake i didnt see. following the bootlog, cat /proc/mtd and dmesg Booting from USB ... (Re)start USB... USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 4 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanby saschadd - Debian