Hey, I can have a look how I get WOL working within my "old 4.13" build, this weekend. As it is working fine, after you activated WOL with ethtools. Cheers Carlby Peacemaker - Debian
user1231 Wrote: ------------------------------------------------------- > Also, I've thrown together a script that downloads > binaries from debian.org and replaces the ones in > Carl's initrd, in case you're paranoid about > running binaries from unknown sources. Not that I > don't trust Carl, Martin and Fox_exe, but my > employer doesn't... ohby Peacemaker - Debian
Have you looked at the sources of the mcm-daemon for the mcm2 / ex2u? Its doing same things: setting the baudrate of ttyS1 Sendung hex commands for e.g fan, temp, powercontrol.by Peacemaker - Debian
Is someone now using kernel 4.13 or 4.12 on mcm2 or ex2u and got wol working? I tried to upgrade from kernel 4.9. to 4.13 my initrd is not loading any more.by Peacemaker - Debian
mcmg2 Wrote: ------------------------------------------------------- > yes, I bought my cloud mirror gen2, it is on the w > ay. > > any advice would be great or detailed how to...^^ You can find a good HowTo here: https://themm.net/public/ex2u/start @bodhi QuoteI've not started on new u-boot, just gathering info to pacth stock u-boot and modify kernel DTB first. Weby Peacemaker - Debian
Hey bodhi, I've seen the work on the Ex4100, and waiting for a new uboot there. It should be compatible with the ex2 ultra / mcm gen2. But still you need to flash the nand to get it working. uboot or initrd/kernel and initrd+kernel option is working very good, new uboot is still in work, or am I wrong?by Peacemaker - Debian
Hey, what device do you have in mind? the ex2 ultra or the ex2. For the Ex2 Ultra ( or mycloud mirror gen2) its possible, but you need to flash the nand, for percistence. As I don't have the ex2 with I don't know.by Peacemaker - Debian
Good to see, you making progress with the kwboot / Uboot via UART. :-) Maybe we'll get a better / newer Uboot for the WD Devices, and can get a full debian (with "stock"-initrd) working.by Peacemaker - Debian
hmartin Wrote: ------------------------------------------------------- > QuotePeacemaker > Just a small guess, maybe you can try booting my i > nitrd via tftp https://themm.net/public/ex2u/start > > > Yup, this boots to busybox for me. Nice! > > I will need to compile this kernel with a new DTS > to enable the second Gigabit interface on the EX21 > 00...by Peacemaker - Debian
Hey guys, Just a small guess, maybe you can try booting my initrd via tftp https://themm.net/public/ex2u/start With the smaller Ex2u this will drop you into a small busybox, and there is everythink working, even without powerreg. With a standard uInitrd I did'nt got it running. Cheersby Peacemaker - Debian
I'm not sure that this *.dtb file realy exists. As the uBoot has only slight changes from a dev uBoot from Marvel, and for the boot the dtb file is not realy nessesary. And I did not get what you expect from that *.dtb, as I'm sure it won't work with the mainline kernel.by Peacemaker - Debian
Just a short question: can you save env's permanent in the uboot? As on my ex2u it's not possible. But to be honest, the main problem could be that the dtb file is the wrong one. And without saving the env's you have to flash at least something on the nand.by Peacemaker - Debian
Hey saschadd, Both files came out of the vendors gpl package, and I modified the dts to the mainline kernel. Cheers Carlby Peacemaker - Debian
Okay,..I'll fix this. And great work with the HowTo, BTW for the dts: blue-sata1-led { label = "wd385:blue:hdd1"; gpios = <&gpio1 21 GPIO_ACTIVE_LOW>; }; blue-sata2-led { label = "wd385:blue:hdd2"; gpios = <&by Peacemaker - Debian
@ bodhi Not working,... if you are nevertheless interested in the sources, its form the mcm-gpl package form wd.by Peacemaker - Debian
@bodhi kwboot is not working, either the version from the nas326 nor compiled from 2013.0.1-20014_T3.0p2 kwboot -d -b ./u-boot-a38x-RangerPeak_2014T3_PQ-nand-uart_1G.bin -B 115200 /dev/ttyUSB0 Sending debug message. Please reboot the target...\ Sending boot image... M - 1.73 Booting from NAND flashl General initialization - Version: 1.0.0 Detected Device ID 6820 High speed PHY - Vby Peacemaker - Debian
You might be right, but as I'm forced to use a custom initrd(due to the locked uboot), update-initramfs -u is not working for me. Just to make it clear the root partition is mount correct by initrd. The "systemd-boot-process" does not find partitons on the lvm, partition direct on disk or raid are no problem. cheers Carlby Peacemaker - Debian
Hey, I know many of you are not realy a friends of systemd, but may be you can help as well. I checked some things, but I'm stucked with lvm and systemd: At boot process systemd did not find partitons on the lvm. As soon as debian is booted i can just mount them normal,..of cause a walk around is easy but I like to fix this. On my desktop this config works perfect.by Peacemaker - Debian
It's not working, so the address might be wrong: root@wdebian:~# cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0x00080000 0x20000 0x20000 root@wdebian:~# fw_printenv Warning: Bad CRC, using default environment bootargs= bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=$by Peacemaker - Debian
@Bodhi I know this, but the stock-os has no /etc/fw_env.config. So I have no idea where the env's are located in the mtd0. and so fw_printenv does not work.by Peacemaker - Debian
@bodhi I'd try your way some time ago, but as stock OS don't has fw_env, I didn't get access the env's from debian. @MM Thanks for the push to bashrc :-) QuoteMM Yes, but how would you solve it? I would just put a too high default value into the config and let the user fix it for himself. What better solution do we have? Maybe implemet in the config.ini an auto opby Peacemaker - Debian
hey bodhi, Env's and I guess every promp from the uboot are already posted from JanN (first post as well), and of cause I can stop the boot process (with key "1"). Yes, I think the uboots are very similar, but in the wd uboot version you can't save env's as there is no saveenv command. So I guess the only way is to flash a free uboot, but with a own initrd, there isby Peacemaker - Debian
@ Martin, So with my "worse case"-HDD (old-wd-black) your last build works quite well, as you said it takes a while to settle, but it does. The problem with "fixed"(-even in config) start values is that the fan does not start every time and on every device with the same value: so my fan starts turning with 55-65 and ~2000rpm; 80 value is about 3500 rpm and i "can"by Peacemaker - Debian
Hey martin, really nice work ! & Big Thanks ! Few things: - 80 for min speed is quite high and why hardcode this value: What about check on first start the "fanstart" value and add for safety 5 or so for smaller thinks I'll just do commitsby Peacemaker - Debian
Hey Martin, The PID-controller sounds really interresting and would be a "nice to have" feature. ( besides I think it is not needed as rapid tempreture increase and decrease does not happen) I merge your mcm-daemon on github and reworked the fan-control, in my opinion it is working better, with lower noise. Maybe you can have a look at these lines and maybe it helps with the pid.by Peacemaker - Debian
MM Wrote: ------------------------------------------------------- > i made the first changes to the mcm-daemon and > added the ability to show the fanrpms. Great work! > What doesn't work for me with your initrd is > getting a shell by pressing a key on the serial > console, but pressing the reset button works for > me. Hm,.. strange, did you pressed only "by Peacemaker - Debian
@bodhi Thanks, but the stock uboot of the WD-Devices are locked as no saveenv command is integrated, so we have to stay at stock env's :-/ @MM, Updated the Initrd, and fixed this: - you check for /sbin/init as a symlink which didn't work for me as /sbin/init is an executable - when the passphrase in /mnt/config/initrd/luks.key is wrong (trailing newline) no shell is started toby Peacemaker - Debian
MM Wrote: > After switching to the "real" init on the rootfs, > no output from the boot scripts > is sent. I see only kernel messages and after a > while the serial login prompt. I'm not missing anything, and will post a bootlog later. > Well, I won't implement this since it's awful. > Either everything the mcm-daemon/control script >by Peacemaker - Debian
MM Wrote: ------------------------------------------------------- > - you check for /sbin/init as a symlink which > didn't work for me as /sbin/init is an executable > - when the passphrase in > /mnt/config/initrd/luks.key is wrong (trailing > newline) no shell is started to fix it Thanks for your reply, I'll fix this > - the console is lost after the firstby Peacemaker - Debian
Updated the initrd in my github: I add resetbutton support: with pressing resetbutton you can enter rescue-shell now without uart. Somehow shutdown is not working any more; the device is rebooting every time :-/ and have no idea why. To keep it simple I reworked the fancontrol script from Lorenzo Martignoni with more fan-states. I will upload the sources and an patched rootfs when its tesby Peacemaker - Debian