Thanks a lot! I'm in finish! :) The machine booted up successfuly and it is working fast and stable. Awesome!by Mr Dini - Debian
Okay, now I loaded the uInitrd too. But it says this about two minutes: Marvell>> ext2load usb 0:1 0x800000 /boot/uImage .... . ......by Mr Dini - Debian
Hard work! Now, I Can boot up the kernel, but how Can I specify the rootfs path? At my pendrive, I have only one partition (ext2) with rootfs and a /boot directory with my edited uImage. Thanks! Here is a pastebin (sorry, the text's end is invisible, because I used mini terminal window).by Mr Dini - Debian
Okay, now it's saying an another interesting error: Marvell>> mw.l f1010100 1361c000 Marvell>> usb reset (Re)start USB... USB: scanning bus for devices...by Mr Dini - Debian
Yes, I found that command: mw.l f1010100 1361c000 Will try it tomorrow! Regarding the two partitions... Okay, but in case, when I just have a rootfs, where the u-boot look for the uImage (kernel). I haven't got a non stop tftp server to download it every boot and my HDD is full of data... Edit: Ah sorry, I had to read Your comment three times to understand, how did You thought tby Mr Dini - Debian
Hi! I tried to boot up from USB, but it doesn't works... Here is an output: Marvell>> usb reset (Re)start USB... USB: scanning bus for devices... 1 USB Device(s) found Waiting for storage device(s) to settle before scanning... 0 Storage Device(s) found Marvell>> It is a pendrive with two partitions. Yes, You said, I just have one, but I have very old u-boot wby Mr Dini - Debian
Okay! Summa-summarum: I have an uImage generated with Your description, from the 4.6 tld archive (bz2). And an uInitrd from madadmin's article. I will place theese two files to a pendrive's FAT16 part with boot label? And I will extract the rootfs to the second, rootfs labelled partition? After it, I think, I just have to test a boot up with serial console and if everything isby Mr Dini - Debian
Many-many thanks! I am very thankful! :) Certainly, I have serial cable and I Can use it. I will try it tomorrow.by Mr Dini - Debian
And the 4.4.0 rootfs will work with 4.6.0 kernel? Because, as You read, the 320S ethernet fix is just come with the future releases... Ps.: I don't want to upgrade u-boot from the stock, because the original fw will not work if I update it.by Mr Dini - Debian
Okay, but I Can't install deb packages at my nas's stock fw, because I haven't got dpkg package manager... So I decided to build the uImage on a PC ubuntu 14.04 (x64). But when I try to install the linux-image-4.6.0-kirkwood-tld-1_1.0_armel.deb package, it says compatibility error... (x64 and armel) I successfully created the uImage, but I Can't create the uInitrd with tby Mr Dini - Debian
Hi! Thanks for the detailed answer and sorry for my late reply... One thing is not clear for me. If my u-boot not supports fdt and tld, I have to make an uImage manualy for the nas. That's okay, but how Can I do that? Where Can I download a kernel source tree, which compatible with my nas?by Mr Dini - Debian
Hi! I have an NSA320S too and I am interested to install Debian on it. But I want to install the whole system to pendrive(s). I found at @bodhi's nice forum some compatible kernels, but they are fdt based and we have got old u-boot binary on this nas, and I don't want to change that if it isn't important. So I think the manualy configure of the uImage is a better solution inby Mr Dini - Debian