Quote2. I started out with a 3.14 rootfs and did a manual upgrade to Debian Jessie. Are there any known caveats in doing so (as opposed to using a 3.18 rootfs package)? I can you give only information on the above question. When using rootfs 3.17 or smaller then this is Debian Wheezy, if you then upgrade to the kernel 3.18 or higher it doesn't turn into jessie. It stays Debian Wheezy linby ziggy - Debian
Hi Thanks for the quick reply. I've noticed that my usb_root was set to "/dev/db1" instead of "LABEL=rootfs". root@RXkeNAS:~# fw_printenv arcNumber=4495 baudrate=115200 bootcmd=run bootcmd_usb; run bootcmd_sata; run bootcmd_mmc; reset bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_bootby ziggy - Debian
Hi When I wan't to shutdown my machine via ssh or via terminal the result is the same. It won't shutdown and is going in maintenance mode. When pushing control-D like asked in this maintenance mode it boots right up in debian and can ssh into it, but when entering root password ssh isn't allowed and only terminal works. For shutting down I used the command: shutdown nowby ziggy - Debian
OMV (Openmediavault) wasn't working on 3.18.x not even after upgrading to newest kernel 4.2.0 After doing some research it was the incompatibility of OMV with the new debian (jessie) rootfs starting from 3.18.x I created then my own uImage for 3.17 (debian wheezy) on the working debian I made with the 3.18.5 that bodhi created for me. So that I could install the old debian (wheezy) 3.17by ziggy - Debian
w00t now it is working! Many thx to everyone that helped me. Now finding the login and pwd for getting logged in via serial connection or ssh as root for further manipulation... Because like in the log I tried root as login and root as pasword, but then the connection via ssh is closed and with serial he keeps asking login even if I type root. edit: Ok found it the reason why I couldnby ziggy - Debian
Hi bodhi your uImage doesn't work either... Strange I don't know what is wrong with my setup anymore. It complains about machid not correct. Doest the env need machid filled in? Because I notice that in my printenv machid isn't set. Or can it maybe be that my usb stick and hdd is formatted in ext4 even if I adjusted env settings accordingly? To sum up the logs of my sysby ziggy - Debian
Sorry for the clutter in the kernel forum, that you had to move it to here. Thanks for the uImage! I'll try it right away. Another question. Would it be possible to flash /boot to NAND or other internal memory instead of USB stick or HDD on my NSA325v2?by ziggy - Debian
Hi andsol The boot folder you gave is not 3.18.5 but 4.1 Are you sure you've upload te correct boot folder? If you want can you make a boot folder with kernel 3.18.5 for NSA325v2 with uboot 2014.7-tld-4 installed in NAND. For quick testing I now boot from USB stick, but plan to install it on internal hdd. Many thanks already for thanks for the help!by ziggy - Debian
bodhi Wrote: ------------------------------------------------------- > Thanks andsol. > > I think for the 3.18.5 rootfs, ziggy only needs > the uImage file that has the NSA325 DTB appended > to it. It looks like the rest are OK. Thanks andsol for your boot folder, but this doesn't seems to work... :-( It gives me the same message when booting with your boot foldeby ziggy - Debian
andsol Wrote: ------------------------------------------------------- > @Ziggy, 3.18.5 image should work fine for you. Let > me know if you need properly generated kernel > files I can send them to you. Can you please generate for me the correct uImage? With the wheezy virtual machine it also doesn't work uname -a Linux debian 3.2.0-4-486 #1 Debian 3.2.68-1+deb7u3 i6by ziggy - Debian
Hi Bodhi Ah ok, no problem! I'm happy enough that you can help me with this in your spare time. Unfortunately I don't have another ARM box around. I'm now preparing a Wheezy virtual machine to try creating the uImage. But if this fails, can somebody be so kindly to already create the uImage for me and upload it?by ziggy - Debian
bodhi Wrote: ------------------------------------------------------- > @ziggy, > > Your execution of the steps are all correct, I did > not see any thing wrong. So that points to the > mkimage command, which might be not working > correctly in that Debian 3.16.0-4-586 system. > > To make matter simpler, instead of using the > 3.18.5 rootfs, use the > Debby ziggy - Debian
Sorry about the little information I gave, I updated my previous post to be more complete. If something is still missing, please let me know and I'll update it. Thanks in advance for taking a look into this.by ziggy - Debian
When I want to follow step 4 in the instructions: QuoteUpdated 24 Feb 2015: This rootfs is the first Debian jessie rootfs in my Kirkwood kernel/rootfs release series, and to keep in sync with kernel Linux-3.18.5-kirkwood-tld-1. I get an error when creating the uImage. All the information I can give you is the following: - ZyXEL NSA325v2 with latest uBoot 2014.7-tld-4 flashed on NAND - Tby ziggy - Debian
I proceeded but now I'm stuck on section B at sub d: Flash u-boot envs to NAND location 0xC0000. The first step succeeded: /i-data/fe8bf781/admin # ./flash_erase /dev/mtd0 0xc0000 1 Erase Total 1 Units Performing Flash Erase of length 131072 at offset 0xc0000 done But the second I receive the following output when doing this command: /i-data/fe8bf781/admin/tmp # nandwrite -s 78643by ziggy - uBoot
Bodhi ok, because in setp 7 the expected output should look like this: Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x60000 In my output I don't see an offset.by ziggy - uBoot
Bodhi Many thx for your help! I performed step 6 again and get a correct output: /i-data/fe8bf781/admin # ./flash_erase /dev/mtd0 0 4 Erase Total 4 Units Performing Flash Erase of length 131072 at offset 0x60000 done but after performing step 7 I don't receive a correct output: /i-data/fe8bf781/admin/tmp # nandwrite /dev/mtd0 uboot.2014.07-tld-4.nsa325.mtd0.kwb Writing databy ziggy - uBoot
Bodhi Thanks for this clear explanation. Like asked the outpot uname -a Linux NSA325-v2 2.6.31.8 #2 Fri May 15 12:20:01 CST 2015 armv5tel GNU/Linux cat /proc/mtd dev: size erasesize name mtd0: 00100000 00020000 "uboot" mtd1: 00080000 00020000 "uboot_env" mtd2: 00080000 00020000 "key_store" mtd3: 00080000 00020000 "info" mtd4: 00a00by ziggy - uBoot