Hi everyone Hi everyone After Stora, I'm now trying to install Debian on a GoFlexNet and then install OMV. I followed the same process that led me to install Stora https://forum.doozan.com/read.php?2,12096 but the installation stops here: U-Boot 1.1.4 Cloud Engines 1.1.2 (3.4.22) SATA PHYADDR=0 U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00691750 Soc: 88F6281 A1 (DDR2)by diappollo - Debian
Great!!!! Thanks bodhi! It's all working, I sincerely thank you for your help. I hope my noob story can help other people ;)by diappollo - Debian
Hi bodhi, Thanks for your help (and your patience) in PM but since "it's progressing" we might as well come back to the forum. Uboot is (it seems to me) correctly flashed but I now have a new blockage U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:38:05 -0700) Netgear Stora MS2110 SoC: Kirkwood 88F6281_A1 DRAM: 128 MiB WARNING: Caches not enabled NAND: 256 MiB In:by diappollo - Debian
ok or are the envs not in fw-env.config? In any case, since I can't get the assets via fw_printenv mtdparts fw_printenv ethaddr I don't see how I'm going to be able to provide information : fw_setenv mtdparts 'xxxxxxxxx' fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx' Obviously something is eluding me...by diappollo - Debian
Bodhi, The internet connection is good, I don't understand ... I got around the problem by transferring via SFTP. What bothers me more is to always have this message: root@debian:/tmp# fw_printenv Cannot read environment, using default Cannot read default environment from file While : Quotebodhi > root@debian:~# fw_printenv ethaddr > > Cannot read environment, usby diappollo - Debian
bodhi, Thanks but under the terminal with wget, it does not workby diappollo - Debian
Hi, Well, following a crash, I restarted the Stora, and although step 8. was not completed, it seems to work. A priori, the latest Uboot 2017 has been loaded if I am the beginning of the return. Bienvenue dans minicom 2.9 OPTIONS: I18n Port /dev/ttyUSB0, 10:49:51 Tapez CTRL-A Z pour voir l'aide concernant les touches spéciales U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:3by diappollo - Debian
Hi bodhi, I stopped at step 8. Since I am flashing with uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb, if I understand correctly, I must now flash the environment variables by using the one present here: uboot.2016.05-tld-1.environment.bodhi.tar... I imagine that at this stage, I must avoid rebooting. Except, beginner's question, how do I retrieve the uboot.2016.05-tld-1 on dropbox otherby diappollo - Debian
bodhi, Ok, thank you, so I started the procedure but I (still) have problems: 1- when I run this command, I get this response? root@debian:~# fw_printenv ethaddr Cannot read environment, using default Cannot read default environment from file 2- and with this : dmesg et grep -i 'bad'by diappollo - Debian
bodhi, Finally! It works! It's probably a stupid mistake, I was launching the kwoot in a terminal while another was connected to the NAS via minicom... Then, I told myself that it must disrupt the transfer/return of data, I had not understood that I would have the detail in the terminal where Kboot was launched, so I did not see how to control the smooth running of the operations. Sby diappollo - Debian
Try the later version of kwboot here: https://forum.doozan.com/read.php?3,27280 I tried with uboot.2017.07-tld-1.netgear_ms2110.bodhi.tar and kwboot_2024.04-rc3 but no change... what's the difference between kwboot_2024.04-rc3 and the "static" version ? root@MINI-GURU-LINUX:/home/mini-guru/Bureau/kwboot-tool# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.netby diappollo - Debian
root@:/# kwboot -t -B 115200 /dev/ttyUSB0 -b uboot.2017.07-tld-1.netgear_ms2110.mtd0.kwb -p kwboot version 2024.01 Detected kwbimage v0 with NAND boot signature Patching image boot signature to UART Sending boot message. Please reboot the target.../ 1 - I ran the above command. 2 - Immediately plugged in the NAS power after running the command to start the image transfer via UART. theby diappollo - Debian
bodhi, Yes thanks for the advice, I had indeed already checked this point, I forgot to mention it, it is version 1.21. Therefore, it should not be a problem? Marvell>> md ff00003c ff00003c: 00000121 e3a00000 e59f222c e5921000 !.......,"...... ff00004c: e2013008 e3530000 1a000002 e3811008 .0....S..by diappollo - Debian
bodhi, > Sorry for all these questions Not at all. It will help others when installing new u-boot the 1st time, too Thank you for taking it that way, I try to be as exhaustive as possible in my research questions so that it can actually be useful to others! But, having done my first installation of Linux Ubuntu barely a month ago, I am really a beginner and I think that my questionsby diappollo - Debian
bodhi, > If you see it again, please post the serial boot log. Here it is at every startup __ __ _ _ | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |by diappollo - Debian
perfect, it's good, the network works. Really thanks for the help! I must have done something wrong because I was sure I had modified the DTB as specified... my bad! Otherwise, I still have this "dual boot" problem before it works but I think it's due to my USB key without really knowing why? Just to share my experience, I also had to change the power supply because tby diappollo - Debian
Thanks again for this quick response, Ok, I'll leave "saveenv" aside, but I have the manipulation mentioned above by modifying like this: Generate the uImage with DTB embedded inside: cd /media/sdb1/boot cp -a zImage-6.5.7-kirkwood-tld-1 zImage.fdt cat dts/kirkwood-goflexnet.dtb >> zImage.fdt mv uImage uImage.orig mkimage -A arm -O linux -T kernel -C none -a 0x00008by diappollo - Debian
bodhi, Top! Thanks a lot! The boot remains uncertain, I often have to re-enter the environment variables, despite this, a first boot does not succeed then after restarting it works? It's surprising because the sequence is a priori always the same: Hit any key to stop autoboot: 0 (Re)start USB...by diappollo - Debian
Thanks for the quick response. Here's what it looks like using method 1: | \/ | __ _ _ ____ _____| | | | |\/| |/ _` | '__\ \ / / _ \ | | | | | | (_| | | \ V / __/ | | |_| |_|\__,_|_| \_/ \___|_|_| _ _ ____ _ | | | | | __ ) ___ ___ | |_ | | | |___| _ \ / _ \ / _ \| __| | |_| |___| |_) | (_) | (_) | |_by diappollo - Debian
Hello everyone, I’m facing several issues while installing Debian on a STORA MS2000 NAS using a USB stick. I'm new to this type of installation and I've been on it for a good week, skimming Doozan's topics. I even tried booting via ttl but nothing works. I'm getting used to the idea that I'm not going to manage it without help! Here's the context and theby diappollo - Debian