@bodhi I'm booted in with the following; setenv ipaddr 192.168.1.250 setenv serverip 192.168.1.2 setenv load_dtb_addr 0x1000000 setenv load_image_addr 0x02000000 setenv load_image 'echo loading zImage from tftpserver ...; tftpboot $load_image_addr zImage' setenv load_dtb 'echo loading DTB from tftpserver ...; tftpboot $load_dtb_addr armada-385-synology-rs816-v12.dtby richjn - Debian
@bodhi WIN :) Guys arrived will post more ina minuteby richjn - Debian
@bodhi If I am just adding the bootarg I can do that but give me 15 mins I have someone arriving to pick up some gear in a second. If it needs more (for the delay etc) then yes, please can you post an example.by richjn - Debian
@bodhi QuotezImage is built in ./arch/arm/boot/ uInitrd is the initramfs with a u-boot header uImage is vmlinuz with a u-boot header. Thank youby richjn - Debian
@bodhi OK, so that didn't work! and I think I got myself mixed up in my post above. Maybe I need a u-boot component terminology guide based on the results I'm seeing. For u-boot zImage is the equivalent of vmlinuz ? uInitrd is the equvilent of initrd is the equivalent of initramfs ? uImage is ? EDIT I meant my "small build" didn't workby richjn - Debian
@bodhi I think I mentioned I am running my own fork of Arch Linux. The "Arch Way" is to compile anything that can be as a loadable module then on initrd creation they use hooks to probe only for the modules required to boot thereafter udev / kmod deal with the rest as the system comes up. The Arch mkinitcpio utility allows the user to add modules they might want during boot via a confiby richjn - Debian
@bodhi QuoteMy goal always has been to make it possible to run a full blown Debian system on disk. Very happy to test anything you ask me to in the interest of achieving your goal and generally helping others get this box up and running. I will see how "close to the wire" I am with my attempts to reduce size if too close I will drop my preferred option.by richjn - Debian
RS816 fan speed control The fans are all pre-configured in @bodhi upcoming 5.1.x rootfs To control the fan speed on this box you can install Debian fancontrol. To install # apt-get install fancontrol To configure # pwmconfig Or if you prefer download the attached fancontrol config file and install it to /etc Then start the fan control daemon # service fancontrol startby richjn - Debian
@bodhi I will try to reduce zImage, uInitrd and DTS to below 7mb first as its my preferred option to boot from flash. Even if I succeed I am happy to test an HDD raw sector boot as others may prefer to go that way especially if you are unable to rebuild stock u-boot.by richjn - Debian
@bodhi Hi I think we were both trying to do too many things at once and on my side with the final post in sight I was guilty of being just too keen to get it done...... lesson learnt! I haven't tried reducing the zImage / uInitrd size as yet because although its an option it is probably a less desirable solution as it would be an RS816 specific one. My other thought is can we load zIby richjn - Debian
@bodhi QuoteThe SPI flash size is 8MB. At minimum 1MB must be reserved for u-boot. And the kernel files size are: And I missed this post from you altogether!! Everything you said consequently now falls into place and hopefully now you know I missed the post you don't think I've not been listening.by richjn - Debian
@bodhi QuoteNot sure what you meant by SP1? Yeah I meant SPI it's been a long day. I will leave you in peace to think it all through. Meanwhile just out of curiosity I will see if I can reduce the zImage size by knocking out as many built in modules as I can.by richjn - Debian
@bodhi Bummer! this stock u-boot is really too limited. I have to think what should be the best way forward I'm typing whilst you are posting, sorry about that, if this is a dead line I'm ready to try again with Sp1 flash if its ok with you ?by richjn - Debian
@bodhi Marvell>> help diskboot diskboot - diskboot- boot from IDE device Usage: diskboot loadAddr dev:part Marvell>> help usbboot usbboot - boot from USB device Usage: usbboot loadAddr dev:part Same for scsiboot Marvell>> help scsiboot scsiboot - boot from SCSI device Usage: scsiboot loadAddr dev:partby richjn - Debian
@bodhi Just ran help from u-boot and there appears to be a boot from usb option (bottom of list) and a diskboot (mid list) Marvell>> help ? - alias for 'help' Creset - Creset - Run 'reset' or boot command in a loop, while counting. SatR - Sample At Reset sub-system WOLTest - WOLTest - Wake On Lan u-boot testing active_units- printby richjn - Debian
@bodhi I thought stock u-boot was unable to load zImage from USB due to lack of ext2ls or ext2load ? I have reduced the "setenv bootcmd" From setenv bootcmd 'mw 0xf10a2620 0x251;mw 0xf10a2e20 0x251;usb xhciinit; run bootcmd_exec; run bootspi' To setenv bootcmd 'run bootcmd_exec; run bootspi' And we boot no problem from HDD (with zImage, uInitrd, DTBby richjn - Debian
@bodhi Two ports available but I confess I'm not sure at the moment if it is needed or not. When I moved over to a HDD install I deleted the following from the env variables you had supplied originally to zifxify setenv usb_setup 'setenv usbActive 1; setenv usbType 3; usb start;' And then from the setenv bootcmd_exec run usb_setup; In the setenv bootcmd I left the xhcby richjn - Debian
@bodhi I have mentioned it several times actually but as I said these things happen so we press on :) Quoterichjn I use rootfs LABEL but actual device is /dev/md0by richjn - Debian
@bodhi No, not bootargs I'm afraid. Booting into stock deleted my rootfs which was /dev/md0 I'm only speculating but stock uses /dev/md0 as its boot device so maybe it was trying to recover it. I have recovered the raid device but was unable to rescue the file system. I will need to start over. These things happen when you are breaking new ground :) Will post back when I'mby richjn - Debian
@bodhi All went well until after the run bootspi This booted to stock but on returning to try and boot Debian I am getting dropped to an intramfs prompt. i.e. rootfs not found. I will boot back in via a usb drive and see if stock has overwritten something. Back when I have got to the answer.by richjn - Debian
@bodhi I interupt u-boot and enter the following, just to note I dropped starting usb once I had gone over to an HDD install. Also my 20 second rootfs delay was just from testing not actually needed. I use rootfs LABEL but actual device is /dev/md0, lastly my rootfs is ext4 in case it make any difference. setenv ipaddr 192.168.1.250 setenv serverip 192.168.1.2 setenv load_dtb_addr 0x10000by richjn - Debian
@bodhi fw_printenv CASset=max MALLOC_len=5 MPmode=SMP ata_hdd_detect=syno_hdd_detect=39,39,39,39 ata_hdd_enable=syno_hdd_enable=37,37,37,37 autoload=no baudrate=115200 boot_order=hd_scr usb_scr mmc_scr hd_img usb_img mmc_img pxe net_img net_scr bootargs= bootargs_dflt=$console $nandEcc $mtdparts_lgcy $bootargs_root nfsroot=$serverip:$rootpath ip=$ipaddr:$serverip$bootargs_end $mvNetCby richjn - Debian
@bodhi Missed one of the fan speeds of the v11 DTS v12 and final attached.by richjn - Debian
@100001101000 Interesting I will take a look! I'm currently stopping the power led blinking in rc.local echo 4 > /dev/ttyS1 And turning the status light On > Green echo 8 > /dev/ttyS1 Later I will add a script to change those to Orange > blinking based on smartd & mdmon errorsby richjn - Debian
@bodhi QuotePlease put every thing below in 1 new post in this thread cat /proc/mtd dev: size erasesize name mtd0: 00400000 00001000 "boot" mtd1: 00400000 00001000 "spi-rootfs" cat /etc/fw_env.config # MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd1 0x0000 0x80000 0x2by richjn - Debian
@bodhi Echo your sentiments, thanks to everyone for contributing in being able to add the RS816 to the supported list!by richjn - Debian
@bodhi Other than any last thoughts you may have on the fan the only thing I can think of that is currently not addressed is the NIC led's. To recap, the nic's and hdd's leds are powered up via gpio 6 as a group and our current ide-disk1 trigger flashes all of them on hdd activity which is not the desired action for the nic leds which we want to flash on network activity. Inby richjn - Debian
@bodhi QuoteI think we shoudl try the DS116 definition one more time to make sure. Good call! Not sure if something has changed (extra kernel config) or I just missed it before but with the DS116 config we now have more control. I have redone the map to reflect the actual speed change points noted by echoing in 50 increments to fan1_target and utilizing my wife's hearing, she can hear aby richjn - Debian
@bodhi With no new triggers showing up (from the config addition) are we going to leave switching fans from low to high to users to implement via a script ? Once I have done mine I could share it here for others to use / base theirs on. If we are leaving it to end users I think we should clean up the fan section of v9 DTS which still contains 7 speeds in the form of an rpm map. As we now knowby richjn - Debian