@bodhi That worked :-) Booted with usb envs setenv ipaddr 192.168.1.19 setenv serverip 192.168.1.1 setenv usb_setup 'setenv usbActive 1; setenv usbType 3; usb start;' setenv load_initrd_addr 0x3000000 setenv load_image_addr 0x02000000 setenv load_image 'echo loading uImage from tftpserver ...; tftpboot $load_image_addr uImage' setenv load_initrdby richjn - Debian
@bodhi Memory refreshed So zImage with dtb embedded avoiding the need to load the dtb separately. I will have a go at this tomorrow. Richardby richjn - Debian
@bodhi Ah, I had missed that bit, basically I didn't read any of the post I just grabbed the rootfs. I hadn't had any issues with my own setup because my kernel is stripped back to bare essentials and still quite small, hence I didn't stop to think something may have changed. I'm a bit confused though I thought uImage was an initramfs plus a u-boot header and hence woulby richjn - Debian
@bodhi I will try to get this done over the weekend but I have just downloaded linux-5.1.7-mvebu-tld-1 and note from the config file that raid1 is compiled as a module. CONFIG_MD_RAID1=m This will not work for the raid installation with zImage in flash we need raid1 built in to bring the rootfs up. We could use my kernel then sed the appropriate changes for the tutorial or skip the rby richjn - Debian
@bodhi Thanks for the update on your holiday movements and trust you are having a great break :) I think you may have missed from my post that at this time I only have one unit, the other went missing from my desk on the first week of my holiday and no one knows where it went. It now looks like I will need to press the unit back into service prior to your return and once deployed it mayby richjn - Debian
@bodhi I have been bribed to forego my long term leave and am back in my office. I am under some pressure to get the RS816 back into service for a project and the whereabouts of the second unit is still unknown, I know you were also holidaying but I wasn't sure of your return date ? If it works for you and we can get to the tutorials before our agreed mid August date that would helpby richjn - Debian
@bodhi I'm embarrassed!! Having just slated a work colleague for a stupid mistake on our firewall I then notice I have doubled up on mtdparts=!!! setenv mtdparts 'mtdparts=mtdparts=spi0.0:4m(boot),-(spi-rootfs)' I will now try to squeeze down the crack in the floorboardsby richjn - Debian
@bodhi Just posting on the off chance you haven't started your own holiday yet. I will be returning to my holiday tomorrow. I got called back for an "emergency" with our firewall (the converted RS816) which irritatingly, for my holiday, proved to be nothing more serious than a miss-configured firewall rule by someone who shouldn't have been meddling with it in the firstby richjn - Debian
@bodhi My last 'working' day today before I start packing for my extended leave so just wanted to sign out and say I will post on my return. One thing I forgot to comment on in my previous email was the use of Ext3. In recent kernels Ext3 is no longer present as a standalone item with Ext3 filesystems being handled by the Ext4 kernel module simply to provide backwards compatibilitby richjn - Debian
@bodhi Very happy to go any route you like and certainly for a single HDD install we don't need to do any of the other stuff. I suspect though that most users will have this unit running as a 4 HDD setup with DSM and just want to convert it to native Debian. In all cases I was assuming we would boot from rootfs on a USB and install to HDD from there. What I have been doing regardless oby richjn - Debian
@bodhi I think we might need to get our hands a bit dirty on this particular unit when it comes to tutorial III for a raid setup simply because we need to make sure all the Synology raid super blocks are blown away and making sure /boot is sat on the correct raid meta etc. I hear what you are saying re: users should look things up themselves but it wouldn't add many steps if in the raid tby richjn - Debian
@bodhi >> Basically the installation has 3 parts. Sounds good :) >> So to prepare, we'd want to check the following tools in stock (mtd-utils, u-boot-tools). None of those are in stock if by stock you meant Synology DSM ? u-boot-tools was in your previous rootfs but not mtd-utils. The other thing I was thinking about in my last post was a decent partitioning tool for gby richjn - Debian
@bodhi Env's worked fine and the box is now effectively "stock" I have 4 x 2TB drives with the latest DSM-6.2.2 installed all ready for mid August when we both get back from our respective holidays. I am completely at your disposal for how you want to configure things but as a rack server I suspect most users would want to setup raid. Was also wondering what level of userby richjn - Debian
@bodhi Thanks for the env's I'm out at the moment but will post once I get back and apply them. Yes, I was looking to get it back to stock so we can do the tutorial on it. Once the tutorial is done I will probably re-configure it to be the same as my other rs816 i.e zImage on flash.by richjn - Debian
@bodhi >Will be back tomorrow to look at restoring stock envs. Thanks I will wait till you are back then rather than risk messing it up. Info you probably need From Marvel>> printenv Marvell>> 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=by richjn - Debian
@bodhi > Debian Buster release is slated for July 6th: I'm away from 1st July to 15th August so any time after that would be good for me. I was just about to pack away the bricked rs816 and decided to have one last try before I did and to my utter disbelief it booted to Marvel>> using the rs816.stock.uboot.kwb we had taken from the other rs816 conversion. If you recall thisby richjn - Debian
@bodhi I think your advise is sound as usual and if I were running a mainline Linux OS where a couple of apt-get's would see me up and running I would probably go that route but compiling / installing everything required to run a Ubuntu KVM is to add more packages to my own system than I want to and generally would mess with my zen. I did compile a bare minimum Qemu for the armhf VM but wby richjn - Debian
@bodhi I suspect I am in the minority but I prefer not to cross compile if I can avoid it. I did setup a native armhf qemu a while back but it was dog slow :(by richjn - Debian
@bodhi The top level script uses git to download updates to all of the components for the firmware build and then checks to see if you have the appropriate development files installed, missing items are ignored till the end of the checks before exiting as I don't have them installed. Because I'm building on an in-production server I don't want to install all of the requirementsby richjn - Debian
@bodhi I have downloaded two tarballs from Lynksys published gpl specifically for the WRT32X 1) WRT32X_gpl_v1.0.180130.36-HK.tar.gz 2) WRT32X_v1.0.180404.58.tar.gz Both contain two u-boot tarballs 1) u-boot-2014.10.tar.bz2 2) u-boot-2015.10.tar.bz2 There are a number of patches relating to u-boot which are held outside of the u-boot tarballs, I have not spent much time with it yeby richjn - Debian
@bodhi > U-Boot 2013.01 (May 18 2017 - 16:37:44) Marvell > version: 2015_T1.QA.0p16 Good catch I later found another u-boot which apparently was lifted from Lynksys GPL (I haven't verified this) it was labelled as uboot-wrt3200acm_wrt32x.bin and ran to the same result. Now that you have highlighted the discrepancy I have rerun it and note that this one also has the same u-bootby richjn - Debian
@bodhi I think this is the correct fork HERE I will check it out and update if I have the wrong one (lots of interruptions today making it hard to focus)by richjn - Debian
@bodhi Just a bit of an update on attempts to recover the bricked rs816 After a LOT of communications with Synology they sent me their boot images, I'm not 100% sure if they are even intended for uart booting because their developer told me they just take the ram chips out and re-flash them in a "flasher" they have for the job when they need to do one. Suffice to say I had no jby richjn - Debian
@bodhi > So how do we solve this? use a journal file system such as Ext3 or Ext4 for rootfs (where the kernel files are) Yes, for uInitrd / initrd.img but not for zImage / uImage where we are still stuck with flash or raw hdd sector for these. I think the choice between raw hdd sectors and flash is probably a personal preference thing but currently I favour flash although I readily accept thby richjn - Debian
@bodhi > Chasing GKH really hard I do chase on my main box :) but will not try with my rs816 due to zImage being on flash with consequent wear concerns. I'm currently on linux-5.17 with the kernel stripped down to only the bits I need but even with this minimal setup zImage with uInitrd in flash would not be possible. From here I will update on a 6 monthly schedule or before if a rby richjn - Debian
@bodhi If not too late maybe go with linux-5.1.7 it has a an extra nic fix in it commit 67a3fa2fd0e0df42af99aa0174672c5ee4588b3a Author: Jisheng Zhang <Jisheng.Zhang@synaptics.com> Date: Mon May 27 11:04:17 2019 +0000 net: mvneta: Fix err code path of probe [ Upstream commit d484e06e25ebb937d841dac02ac1fe76ec7d4ddd ] Fix below issues in err code path oby richjn - Debian
@bodhi I'm parking the rescue for now but will pick it back up at some point, I may write to Synology and ask them if they are prepared to send me a rescue uart image of their own, I presume they must have one. Even though I'm down to one rs816 which is in production I owe its successful conversion to this forum and in particular to you for all of your help and guidance getting it dby richjn - Debian
@bodhi kwboot test from above ended the same way with no further output. 98 % [......................................................................] 99 % [........................] I fetched and installed my new serial pcie card and on the face of it things are worse, download-serial.sh doesn't get a nack and kwboot is even more tricky to start. I will get on with trying sby richjn - Debian
@bodhi The fall back patch was one I had already applied to my kwboot which regrettably seems to make no difference on this box. I had also tried multiple variations of -s & -q. I am re-running with kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot-a38x-2015T1_p18_Thecus-tld-4-spi-uart.bin -s 0 -q 1 -f The upload is taking place in a similar manner to last time where the first 9% happens qby richjn - Debian
@bodhi All arrays synced and rs816 back in rack. The download-serial.sh.orig works fine. u-boot-a38x-2015T1_p18_Thecus-tld-4-spi-uart.bin $ ./download-serial.sh /dev/ttyUSB0 u-boot-a38x-2015T1_p18_Thecus-tld-4-spi-uart.bin send-stop-pattern.c: In function ‘main’: send-stop-pattern.c:24:2: warning: implicit declaration of function ‘sleep’ [-Wimplicit-function-declaration]by richjn - Debian