Thank you sym0 for your contribution! Unless you already tested it I'll run the fan and led binaries on the debian system tonight to see what results I get! Thanks :)by ConcentratedCancer - Debian
I've been away on vacation so I haven't had a chance to run the fan and led control binaries on the debian system. I am back now though so I will give that a try and report back!by ConcentratedCancer - Debian
They are dynamically linked fan_control: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.16, stripped led: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.16, strippedby ConcentratedCancer - Debian
Sadly the fan control and led tools are supplied in their binary form even in the GPL, there are no other references to led's or fan control anywhere else in the GPL so that may be a no go unfortunately.by ConcentratedCancer - Debian
Hello again, I had a bit of a boost in energy this evening and thought I would do some digging into the firmware, I found two binaries of interest, /usr/sbin/fan_control and /usr/sbin/led, "fan_control" controls the fan as you would expect you can turn it on and off and set speed and get the fan RPM, "led" allows me to set the power led status (on, off, blinking, red or bluby ConcentratedCancer - Debian
Hey, Yep, my mistake, actually there was more than one mistake, I forgot to copy the kernel before appending the device tree onto it so the "kernel" I was trying to load was just the device tree, as well as I extracted the dts instead of the dtb. I am still sick so my brain isn't working quite right haha, regardless that new device tree does show the correct size/layout and hasby ConcentratedCancer - Debian
Hello, I have been away the last few days but I have gotten the chance now to test the new DTS you provided. Upon loading the kernel and initrd, but instantly crashes with "data abort" and resets the CPU. I have attached the log. Thanks!by ConcentratedCancer - Debian
Hello, I was sick the last few days, is this what you are needing? Marvell>> printenv baudrate=115200 loads_echo=0 ipaddr=2.66.66.200 serverip=2.66.66.32 rootpath=/srv/ubuntu netmask=255.255.255.0 run_diag=yes stdin=serial stdout=serial stderr=serial console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0xff00000@0x100000(root) mainlineLinux=no enaMonExt=noby ConcentratedCancer - Debian
Hello, I've been away the last couple days but I'll be back home this evening and will be able to get those for you. Thanks!by ConcentratedCancer - Debian
Hello, I just realized I linked the firmware binary and not the GPL, my mistake. I edited my previous post with the correct link. I tried again with a dumb switch connected directly to the router and directly to the router it's self and got the exact same messages repeating in the log [ 260.744801][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex,by ConcentratedCancer - Debian
Hey, So I am not home at the moment so I can't tinker with the machine, however before I left I did test four drives in the machine at once and indeed all the sata ports do work! As for the kernel command line not using a label instead of a UUID, that was me messing about before I was able to get the machine to boot at all, to keep it as consistent as possible I will use a roots labelby ConcentratedCancer - Debian
Hello once again, Running that ethtool command did quiet the log whilst keeping the connection stable, amazing! It's been awhile since I have used systemd with more than one interface so I completely forgot it won't bring up the interface or DHCP it unless it's configured in the interfaces file. Either way doing that it works as expected. I have attached a log with the reqby ConcentratedCancer - Debian
Alright so we are getting closer, it now boots up and also shows eth0 and eth1. However there are some oddities. When the ethernet cable is attached, the console gets spammed with messages of the link going up and going down. I've attached the bootlog however to make it more clear on what is going on I have edited the log and added comments which I will preface and end using "##by ConcentratedCancer - Debian
Hello once again, With using the early printk argument I now get some useful information. I have attached the bootlog to the post. It appears to get to the part in the initramfs where it mounts the real rootfs, but then kernel panics. I am not sure how a device tree could cause that to happen but you know more than me. Thanks again!by ConcentratedCancer - Debian
Bodhi, Thank you for making that DTS for this machine. It's past midnight where I live but I wanted to provide a update/some feedback on using the DTB before I call it a night. Regenerating the uImage using the new .dtb caused it to hang at "starting kernel". I am not sure how to get any more debugging information out of it as I am pretty sure that message is technically bby ConcentratedCancer - Debian
Hey bodhi, Thank you for taking the time to reply, I have gathered the requested log files and will attach them to the post, they are all named accordingly to make it easier to differentiate between the logs. The logs I got from within Debian were made with the kirkwood-db-88f6282 dtb this time, however as you said, I don't think it makes a big difference. Some of the Linux bootargsby ConcentratedCancer - Debian
Hello, I also have a WD EX4, I have been working the past two weeks on getting a newer kernel running on it (the stock WD OS3 ships with Linux 3.2.40). This forum was extremely helpful in getting me further in this process. The U-Boot that is on the EX4 does not support USB booting or booting from a SATA drive. However TFTP booting does work. I was able to use the linux-6.13.8-kirkwood-tld-1-bby ConcentratedCancer - Debian