Koinin, > I'm installing the latest Debian rootfs > (Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2) > on my GoFlex Home, and everything seems to boot > successfully from USB > sudo tar -xjf > Debian-6.5.7-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > -C /mnt/usb You must be root, sudo won't work. https://forum.doozan.com/read.php?2,12096 QuoteNote: alby bodhi - Debian
And remember to do this so the USB rootfs will not wear out prematurely. https://forum.doozan.com/read.php?2,13702,13704#msg-13704by bodhi - Debian
Hi Navi, Welcome back, hope all is well too! > 2) This time I plan to keep booting from USB pen > drive and use the new HDD just for DATA. I will > also make a clone copy of the USB pen drive for > emergency use. That's how I run my GF Homes for many years. > Therefore the Questions I have are: > > (1) Since I already have your UBoot (2017-07) > inby bodhi - Debian
BayPanard, > > # GPIO for internal HDD power on > #################################### > static void > KW_6282_112_GPIO_init(SYNO_KW_GENERIC_GPIO > *global_gpio) > { > KW_6282_211_GPIO_init(global_gpio); > global_gpio->hdd_pm.hdd1_pm = 30; > } > > > # Global GPIO > ##################### > static void > KW_6282_211_GPIO_iby bodhi - Debian
BayPanard, In case you want to look in the GPL source, the board ID is SYNO_DS212_ID. u-boot-mv-3.5.9/board/mv_feroceon/mv_kw/kw_family/boardEnv/mvBoardEnvSpec.h: #define BOARD_ID_BASE 0x0 #define SYNO_DS212_ID (BOARD_ID_BASE+0x1B) Your stock dmesg [ 0.000000] Synology Board ID: 27by bodhi - Debian
> Btw I just use a generic initrd, as it seems you > don't even need an initrd? What do people use the > initrd for? As long as the ext4 module is > built-in, everything should work, no? It's true, as long as the kernel config includes all necessary drivers (eg. linux-6.14.6-mvebu-tld-1), you don't need it. However, you need Initrd if: - you want to load some modby bodhi - Debian
BayPanard, Thanks for testing. Looks like there is no power to the USB 3.0 port.by bodhi - Debian
Man. > After a few tries I came to the conclusion that > the max size of the uImage can't go above about > 3510-3515ish kb. (I haven't yet got serial access > so I can't see what excatly is the problem, and I > don't have any deeper knowledge or understanding > of this soc, so this is just meant as face value) Original stock u-boot for this box limby bodhi - Debian
Man, I was looking into rolling new u-boot for this and the Synology 215j. However, this Armada 375 SoC only has minimal support in mainline u-boot and Linux. It will be quite time consuming to write a lot of new code, also there is no publicly available datasheet for this SoC, so I am hesitate to start the effort. The Armada 385/388 based NAS are much easier to deal with since I've roby bodhi - Debian
Man, > Thanks for answering. I have not soldered a serial > connector to it. I have not messed with any uboot > envs. (I thought any envs weren't persistent > anyways?) It's now running pretty much bog > standard Debian Trixie, standard uboot/envs. I > would agreee root=LABEL=rootfs is more idiot > proof, but I guess this is good enough for me. OK. &by bodhi - Debian
Man, > So i cloned the rootfs partition to a new drive > and now it works, so probably there might be a > fault with the original drive or something else > (there were som IO errors when I moved things > around with Gparted so I might have to redo it > from scratch, just have to backup about 2.5TB data > first). > You did not post the boot log so it's noby bodhi - Debian
Hi Ivan, Here is the new May 21 build. Let's see if the 2nd HDD will work! uboot.2024.10-tld-1.ds211.bodhi.250521.tar md5: a6c370cd210a0099bc3fc2535f31be5f sha256: 13b0720eb4c7a7c2bcc63d16b1b9eb3d76d365aa707cf1bd6bebab1db53c0fb3 This tarball contains 5 files. uboot.2024.10-tld-1.ds211.kwb uboot.2024.10-tld-1.ds211.environment.img uboot.2024.10-tld-1.ds211.environment uby bodhi - uBoot
Attached here is the new u-boot build for Synology DS112. uboot.2024.10-tld-1.ds112.bodhi.250521.tar md5: 0486eeb249ac3f9382074f3df9d6b804 sha256: c7953a9b2e6ed8aa64666c237b0c22420e995d011989c577d18f0ba19704a6ec This tarball includes 5 files uboot.2024.10-tld-1.ds112.kwb uboot.2024.10-tld-1.ds112.environment.img uboot.2024.10-tld-1.ds112.environment uboot.2024.10-tld-1.ds112.bootby bodhi - Debian
Hold on. It seems was a bad build. I will reupload!by bodhi - Debian
@shermbug, Not sure why. I've PMed joerg.by bodhi - uBoot
adrien60, Thanks for the feedback!by bodhi - Debian
Kernel linux-6.14.6-mvebu-370xp-tld-1-bodhi.tar.bz2 package has been uploaded. Please see 1st post for download link.by bodhi - Debian
BayPanard, > I was thinking debian would work its way to > activate USB ports. Right! > I will test again Give it a try, but don't spend too much time. I'll have a new build soon!by bodhi - Debian
shermbug, Please post in joerg's thread for Pogo E02.by bodhi - uBoot
Kernel 6.14.6-mvebu-tld-1 package has been uploaded. See 1st post for download link. Please create a new thread for any installation problem or questions.by bodhi - Debian
@ConcentratedCancer, In the kernel 6.14.6-kirkwood-tld-1 release, I've changed the name of the DTB to kirkwood-wd-mycloud-ex4.dtb.by bodhi - Debian
Kernel linux-6.14.6-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or question.by bodhi - Debian
BayPanard, > This time with dtb file placed on rootfs : it > booted straight to debian ! Cool! > 2. USB3 ports on the back are not working So the new u-boot actually messed up the USB 3.0 ports! that's quite strange. Because it should not. Did you try removing the USB drive and reattach it?by bodhi - Debian
ZooMoo, > How do I compile a kernel from source and use it > within a Debian Debootstrap install. I guess I'll > need some of Synologies custom libraries, but I'm > not sure > > I've searched online and I could not find anything > for this use-case. > > I'd need to cross-compile it, but I hope there is > some advice or a guide that mby bodhi - Debian
I've built kernel 6.14.6-kirkwood and running it on a few boxes. Since 6.15 will be out in a couple week, I think I'll release this 6.14.6 stable version (if there is nothing significant comming on 6.14.6+ stable in the next couple days).by bodhi - Debian
sudos, I don't think it's bad RAM. > Interestingly this is the one that's running > Owntone. I haven't connected anything to it yet > since then and it's just been sitting there. Both > the tester box and the remote box are completely > unaffected. Do you have swap on? ===== FWIW, one of my several M300 is used in my kernel distributed buby bodhi - Debian
Attached here is the kwbimage.cfg for the Pogo V4. This should be adapted to the Pogo 02 tutorial in the 1st post.by bodhi - uBoot
shermbug Wrote: ------------------------------------------------------- > Just a quick status update... (no 'real' news on > the recovery effort): > > I setup a Pi400 with OpenOCD and I am able to run > the binary. I haven't gotten to the point of > connecting the hardware, so that will be in > another update. This was not straight forward, > thougby bodhi - uBoot
shermbug, > Any other ideas (low hanging fruit)? I'm guessing > that t would also have nuked any tftp server or > client functions and/or other network > boot/recovery options... > but I can easily try some > stuff on that end if you have any relevant > info/ideas (like the address of the device and/or > the expected sever address, file name to put or &gby bodhi - uBoot
Try 1. Start kwboot 2. Power up the Pogo Mobile. and 1. Power up the Pogo Mobile. 2. Start kwboot immediately. And make sure the serial wires are away from the power cord. Sometime the power interference could cause noise if the wires are not shielded. > Also, FWIW, I'm using the OpenWrt u-boot.kwb file > for this device (from OpenWrt 24.10.1). Is there > anotherby bodhi - uBoot