NSA325V2 booting problem

@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.


---------------------
Moderator EDIT: I've split this topic to this new thread so it will not clutter the main kernel/rootfs thread.



Edited 2 time(s). Last edit at 08/29/2015 01:47PM by bodhi.

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 i686 GNU/Linux

mkimage -V

mkimage version 2012.04.01

same error

mkimage: Can't map uImage: Invalid argument

----
Friendly regards


Ziggy



Edited 1 time(s). Last edit at 08/29/2015 01:36AM by ziggy.

ziggy Wrote:
-------------------------------------------------------

> Can you please generate for me the correct
> uImage?
> With the wheezy virtual machine it also doesn't
> work
>

Ziggy, as I said earlier, Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 should work for you. Its my initital image where im starting from.

Which debian release you need?
Check attachment, there is boot folder for jessie.
Kernel files

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.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/29/2015 03:09AM by bodhi.

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 folder as with the boot folder untouched.

see attach

Would it be possible to make the uImage for 3.18.5 rootfs with NSA325 dtb appended like bodhi stated?
Then I can upgrade further with the steps on the forum, so I can learn how to upgrade the system for future purpose.

----
Friendly regards


Ziggy



Edited 1 time(s). Last edit at 08/29/2015 04:40AM by ziggy.

ziggy Wrote:
>
> Would it be possible to make the uImage for 3.18.5
> rootfs with NSA325 dtb appended like bodhi
> stated?
> Then I can upgrade further with the steps on the
> forum, so I can learn how to upgrade the system
> for future purpose.

I think, your problem in something else. 3.18.5 it's my emergency point. When you have it set on USB and there is no issues with uboot dtb environment settings, system should load. I have nsa325v2.

Let me know which exact version you need I will make you an USB image



Edited 1 time(s). Last edit at 08/29/2015 05:34AM by andsol.

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!

----
Friendly regards


Ziggy

ziggy Wrote:
-------------------------------------------------------
> 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!

Hmm, i've tried to set clean image Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 on my NSA325v2 with uboot 2014.7-tld-4 on usb. But its not loading. Since im jumped to 2014.7-tld-4 uBoot, Debian-3.18.5-kirkwood-tld-1-rootfs-bodhi.tar.bz2 doesent work anymore.
Unfortunately I can't give you whole image of my system, it has some private info.
Any other ideas how may I help you?

@andsol,

What you should do is creating a new uImage on a 3.18.5 rootfs (you could do this on your 4.1 rootfs too, with the right command). If you don't have this rootfs, let me create this file for ziggy.

@ziggy,

There is no need to do anything extra, just use your newly created 3.18.5 rootfs. Dowload the new uImage, replace the existing /boot/uImage file with this new one.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

@ziggy, I gonna send you 3.18.5 boot folder later. I have to go now ).

@ziggy,

Here is Dropbox link for the uImage file.

uImage.3.18.5-kirkwood-tld-1.tar
md5
dca3dc0027b848c6f7255c6963c8e0a8

Assuming /media/sdxx is where the USB drive mounted on your Intel box. Extract the 3.18.5 rootfs to it. And then

cd /media/sdxx/boot
mv uImage uImage.orig
tar -xf uImage.3.18.5-kirkwood-tld-1.tar

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 2 time(s). Last edit at 08/30/2015 03:32AM by bodhi.

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?

----
Friendly regards


Ziggy

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 system.
- ZyXEL NSA325v2 with latest uBoot 2014.7-tld-4 flashed on NAND
- The following printenv

arcNumber=4495
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; reset
bootcmd_mmc=run mmc_init; run set_bootargs_mmc; run mmc_boot
bootcmd_sata=run sata_init; run set_bootargs_sata; run sata_boot;
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootcmd_usb=run usb_init; run set_bootargs_usb; run usb_boot;
bootdelay=3
console=ttyS0,115200
device=0:1
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mmc_boot=mw 0x800000 0 1; run mmc_load_uimage; if run mmc_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
mmc_init=mmc rescan
mmc_load_uimage=ext2load mmc $device 0x800000 /boot/uImage
mmc_load_uinitrd=ext2load mmc $device 0x1100000 /boot/uInitrd
mmc_root=/dev/mmcblk0p1
mtddevname=rootfs
mtddevnum=2
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
rootdelay=5
rootfstype=ext4
sata_boot=mw 0x800000 0 1; run sata_load_uimage; if run sata_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
sata_init=ide reset
sata_load_uimage=ext4load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext4load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
serverip=192.168.0.220
set_bootargs_mmc=setenv bootargs console=$console root=$mmc_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_sata=setenv bootargs console=$console root=$sata_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; mmc rescan; ide reset; setenv uenv_loaded 0; for devtype in usb mmc ide; do for disknum in 0; do run uenv_read_disk; done; done
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x810000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_boot=mw 0x800000 0 1; run usb_load_uimage; if run usb_load_uinitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
usb_init=usb start
usb_load_uimage=ext4load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext4load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1

Environment size: 2844/131068 bytes

----
Friendly regards


Ziggy

ziggy,

There is nothing wrong with your u-boot envs. machid should be undefined.

Try download the uImage again. I've just re-uploaded it. Perhaps I've used the wrong file the last time!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 08/30/2015 03:36AM by bodhi.

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 couldn't login with the default root/root settings was because in some weird way my USB stick was corrupted but still gave me a debian login screen via serial connection.

I then cleaned it up and installed everything on the internal HDD like bodhi instructed with the created uImage and did everything again.
Now I'm booted on debian the latest 4.1.0 kirkwood.

Going to the next chapter -> installing OMV on my NSA325v2!

Many thx to bodhi and andsol for the aid!

----
Friendly regards


Ziggy



Edited 2 time(s). Last edit at 09/07/2015 10:59AM by ziggy.

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.17 and update it like any debian distro.

After doing that you can install the new kernel 4.2.0 like you could do when upgrading the kernel on 3.18.x.

Then installing OMV like described in the forum:
http://forums.openmediavault.org/index.php/Thread/5302-Howto-install-OpenMediaVault-on-Debian-7-x-Wheezy/

----
Friendly regards


Ziggy



Edited 1 time(s). Last edit at 09/07/2015 11:05AM by ziggy.