Quantcast
Channel: Debian on NSA325 V1/V2
Viewing all 359 articles
Browse latest View live

Re: NSA 325 V2 Debian Is Possible!

$
0
0
everything goes ok
Now i have updated with ubout 2016 and i have run debian 4.4.0
Also i managed to install omv 3.0.86
But.... when i insert sata hdd the boot proccess stop
What is going wrong?

Re: NSA 325 V2 Debian Is Possible!

$
0
0
cratsil1979,

Because you have multiple drives during boot, and the default envs on uboot-2014.07 did not take care of that automatically. So the kernel does not know which drive is the system drive.

Try again with this newer script uboot.2016.05-tld-1.environment.scr in this post:

http://forum.doozan.com/read.php?3,29362,29390#msg-29390

Even though it was for u-boot-2016.05, it should work the same way for your current installed u-boot-2014.07.

------

By the way, once you booted into Debian, you should install the latest u-boot

Quote

Last Updated 19 June 2016

I've uploaded 2016.05-tld-1 U-Boot images for Pogo E02, GoFlexNet, GoFlex Home, Dockstar, Pogo V4/Mobile, iConnect, Netgear Stora, Sheevaplug, NSA320, NSA325, NSA310S/320S, NSA310, and HP-T5325.

Re: NSA 325 V2 Debian Is Possible!

$
0
0
bodhi Wrote:
-------------------------------------------------------
> lille,
>
> >
> > BTW, I am not willing to install your U-boot, be
> ca
> > use I want to boot to stock rootfs and your U-bo
> ot
> > version doesn't allow this until today afaik.
>
> That's OK. No need to install new u-boot if you st
> ill want to boot stock.
>
> This booting problem is simple. Your rootfs uImage
> needs to have the DTB appended to it (because you
> are booting with stock u-boot). Use the kirkwood-
> nsa325.dtb insteadt of kirkwood-goflexnet.dtb in t
> he instruction quoted below.
>
>
Quote

4. Create uImage and uInitrd and setup for
> booting.
>
> ....
>
> 4b. Boot with DTB file embedded in the kernel imag
> e (no U-Boot envs changes are needed if your syste
> m already booting on USB or HDD)
>
> Again, please replace kirkwood-goflexnet.dtb below
> with the correct DTB name for your box.
>
> Generate the uImage and uInitrd:
>
> cd /boot
> mv uImage uImage.orig
> cp -a zImage-4.8.0-kirkwood-tld-1  zImage.fdt
> cat dts/kirkwood-goflexnet.dtb  >> zImage.fdt
> mkimage -A arm -O linux -T kernel -C none -a 0x000
> 08000 -e 0x00008000 -n Linux-4.8.0-kirkwood-tld-1
> -d zImage.fdt  uImage
> mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00
> 000000 -e 0x00000000 -n initramfs-4.8.0-kirkwood-t
> ld-1 -d initrd.img-4.8.0-kirkwood-tld-1 uInitrd
> 

sorted this out already by reading the http://forum.doozan.com/read.php?2,12096 thread properly, sorry my fault.

but how to boot to stock rootfs when usb stick with your debian rootfs is not inserted?

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lille,

> sorted this out already by reading the http://foru
> m.doozan.com/read.php?2,12096 thread properly, sor
> ry my fault.

Cool!

>
> but how to boot to stock rootfs when usb stick wit
> h your debian rootfs is not inserted?

Interrupt serial console and

setenv bootcmd 'if run bootcmd_linux; then; else bootcmd_stock; fi; reset'
boot

Try 2 tests:

1. If it boots all the way into Debian successfully, and then
2. if it boots to stok successfully, when the stick is not inserted.

then you can come back to serial console and save it.

Re: NSA 325 V2 Debian Is Possible!

$
0
0
There was a typo and I've corrected it above.

Re: NSA 325 V2 Debian Is Possible!

$
0
0
bodhi Wrote:
-------------------------------------------------------
> There was a typo and I've corrected it above.

Thank you for your tremendous support!

First of all I had to set the environment variable 'enaMonExt' to 'yes' because if, then & else could not be interpreted

Marvell>> setenv bootcmd 'if run bootcmd_linux; then; else bootcmd_stock; fi; re set'
Marvell>> boot
Unknown command 'if' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'else' - try 'help'
This command can be used only if enaMonExt is set!

The examination passed afterwards but the next issue arises

Marvell>> setenv enaMonExt yes
Marvell>> setenv bootcmd 'if run bootcmd_linux; then; else bootcmd_stock; fi; reset'
Marvell>> boot
Unknown command 'FSrun' - try 'help'
Unknown command 'FSrun' - try 'help'
Unknown command 'FSrun' - try 'help'
Usage:
fi - Find value in the memory.

So no, that didn´t help because FSrun command doesn´t work here on my machine with stock U-boot (U-Boot 1.1.4 (Jul 18 2013 - 10:47:29) Marvell version: 3.5.9).

Any further ideas?
.

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lille,

Interrupt serial console and

setenv bootcmd 'bootcmd_linux; bootcmd_stock; reset'
boot

Re: NSA 325 V2 Debian Is Possible!

$
0
0
bodhi Wrote:
-------------------------------------------------------
> lille,
>
> Interrupt serial console and
>
>
> setenv bootcmd 'bootcmd_linux; bootcmd_stock; rese
> t'
> boot
>

does also nothing

Hit any key to stop autoboot: 0
Marvell>> setenv bootcmd 'bootcmd_linux; bootcmd_stock; reset'
Marvell>> boot
Unknown command 'bootcmd_linux' - try 'help'
Unknown command 'bootcmd_stock' - try 'help'

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lille,

Sorry that was a typo!

setenv bootcmd 'run bootcmd_linux; run bootcmd_stock; reset'
boot

Re: NSA 325 V2 Debian Is Possible!

$
0
0
bodhi Wrote:
-------------------------------------------------------
> lille,
>
> Sorry that was a typo!
>
>
> setenv bootcmd 'run bootcmd_linux; run bootcmd_sto
> ck; reset'
> boot
>

thanks, I´m too stupid to see this immediately ;)

now it tries to boot the kernel, but it stops, no ramfs is loaded afterwards

Marvell>> setenv bootcmd 'run bootcmd_linux; run bootcmd_stock; reset'
Marvell>> boot
(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
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number

NAND read: device 0 offset 0xc80000, size 0xa00000

Bad block at 0xc80000 in erase block from 0xc80000 will be skipped
Reading data from 0x169f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8
Created: 2013-12-19 6:31:22 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5756136 Bytes = 5.5 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................................................................................................................................................................................................................................. done, booting the kernel.

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lille,

Try the revised envs:

setenv bootcmd_stock 'setenv mainlineLinux no; setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)'
setenv bootcmd 'run bootcmd_linux; run bootcmd_stock; reset'
boot

Re: NSA 325 V2 Debian Is Possible!

$
0
0
bodhi Wrote:
-------------------------------------------------------
> lille,
>
> Try the revised envs:
>
>
> setenv bootcmd_stock 'setenv mainlineLinux no; set
> env bootargs $(bootargs_stock); nand read.e $(load
> addr) $(kernel_addr) 0xA00000; bootm $(loadadr)'
> setenv bootcmd 'run bootcmd_linux; run bootcmd_sto
> ck; reset'
> boot
>

still stopping after 'done, booting the kernel' with no usb stick inserted

Hit any key to stop autoboot: 0
Marvell>> setenv bootcmd_stock 'setenv mainlineLinux no; setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)'
Marvell>> setenv bootcmd 'run bootcmd_linux; run bootcmd_stock; reset'
Marvell>> boot
(Re)start USB...
USB: scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number

NAND read: device 0 offset 0xc80000, size 0xa00000

Bad block at 0xc80000 in erase block from 0xc80000 will be skipped
Reading data from 0x169f800 -- 100% complete.
10485760 bytes read: OK
## Booting image at 02000000 ...
Image Name: Linux-2.6.31.8
Created: 2013-12-19 6:31:22 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5756136 Bytes = 5.5 MB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
OK

Starting kernel ...

Uncompressing Linux.............................................................................................................................................................................................................................................................................. done, booting the kernel.

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lille,

Has this box booted stock OS successfully right before you've started to set envs to boot both Debian and stock? If true, do you have the serial boot log for stock?

If not, was this bad block shown since begining or only recently?

Bad block at 0xc80000 in erase block from 0xc80000 will be skipped

Re: NSA 325 V2 Debian Is Possible!

$
0
0
bodhi Wrote:
-------------------------------------------------------
> lille,
>
> Has this box booted stock OS successfully right be
> fore you've started to set envs to boot both Debia
> n and stock? If true, do you have the serial boot
> log for stock?
>
> If not, was this bad block shown since begining or
> only recently?
>
>
> Bad block at 0xc80000 in erase block from 0xc80000
> will be skipped
>

yes , it booted to stock OS already before I have started to change the envs. I can´t remember if the bad block error occured the first time I´ve used the serial console. what exactly shoud be there at 0xc80000?

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lille,

Get a listing of envs in serial console

printenv

And post the output here, in code tags (it will get truncated if you dont use code tags).

Re: NSA 325 V2 Debian Is Possible!

$
0
0
bodhi Wrote:
-------------------------------------------------------
> lille,
>
> Get a listing of envs in serial console
>
>
> printenv
>
>
> And post the output here, in code tags (it will ge
> t truncated if you dont use code tags).

bodhi,

you´ll find 2 text files attached to this post. one is called booting (with this environment variables it is booting to stock OS), the other is called not_booting. please do a comparison and find out what is going on here. thank you in advance.

Re: NSA 325 V2 Debian Is Possible!

$
0
0
booting

Marvell>> printenv
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootcmd=nand read.e 0x2000000 $(kernel_addr) 0xA00000; bootm 0x2000000
bootdelay=2
baudrate=115200
loads_echo=0
ipaddr=10.4.52.165
serverip=10.4.52.7
rootpath=/srv/ubuntu
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=AE03
PRODUCT_NAME=NSA-325v2
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=MitraStar Technology Corp.
run_diag=yes
stdin=serial
stdout=serial
stderr=serial
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
mainlineLinux=no
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
ethprime=egiga0
netbsd_en=no
vxworks_en=no
bootargs_root=root=/dev/nfs rw
bootargs_end=:::DB88FXX81:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
disaMvPnp=no
ethaddr=00:50:43:xx:xx:xx
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
enaAutoRecovery=yes
kernel_addr=0x4640000
pcieTune=no
pcieTune1=no
ethact=egiga0

Environment size: 1565/131068 bytes
Marvell>>

Not booting

Marvell>> printenv
bootargs=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootdelay=2
baudrate=115200
loads_echo=0
ipaddr=10.4.52.165
serverip=10.4.52.7
rootpath=/srv/ubuntu
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=AE03
PRODUCT_NAME=NSA-325v2
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=MitraStar Technology Corp.
run_diag=yes
arcNumber=4495
bootargs_stock=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
bootargs_linux=console=ttyS0,115200 mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=LABEL=rootfs loglevel=8
bootcmd_linux=setenv bootargs $(bootargs_linux); mw.l f1010100 0020c000; usb reset; ext2load usb 0:1 $(loadaddr) /uImage; ext2load usb 0:1 0x01100000 /uInitrd; bootm $(loadaddr) 0x01100000
bootcmd_stock=setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)
to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset
to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset
console=console=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:::orion:eth0:none
image_name=uImage
standalone=fsload 0x2000000 $(image_name);setenv bootargs $(console) root=/dev/mtdblock0 rw ip=$(ipaddr):$(serverip)$(bootargs_end) $(mvPhoneConfig); bootm 0x2000000;
lcd0_enable=0
lcd0_params=640x480-16@60
ethaddr=00:50:43:xx:xx:xx
ethmtu=1500
mvPhoneConfig=mv_phone_config=dev[0]:fxs,dev[1]:fxo
mvNetConfig=mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500
usb0Mode=host
yuk_ethaddr=00:00:00:EE:51:81
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
image_multi=yes
ethact=egiga0
bootcmd='run bootcmd_linux'
stdin=serial
stdout=serial
stderr=serial
mainlineLinux=yes
enaMonExt=no
enaCpuStream=no
enaWrAllo=no
pexMode=RC
disL2Cache=no
setL2CacheWT=yes
disL2Prefetch=yes
enaICPref=yes
enaDCPref=yes
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
disaMvPnp=no
enaAutoRecovery=yes
kernel_addr=0x4640000
pcieTune=no
pcieTune1=no

Environment size: 2494/131068 bytes
Marvell>> boot
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
0 Storage Device(s) found
** Bad partition 1 **
** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number
Marvell>>

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lille,

Power up, interrupt serial console and try executing the stock boot command right away. See if you can boot to stock.

run bootcmd_stock

Re: NSA 325 V2 Debian Is Possible!

$
0
0
Noted that no cpufreq folder is created unter /sys/devices/system/cpu/cpu0. Therefore the CPU-clock is 1,6GHz all time. I am using latest rootfs and kernel image.
cpufreq-info gives the following error:
analyzing CPU 0:
no or unknown cpufreq-driver active

What's happening? The kirkwood cpufreq-driver is not supported by the kernel?

Re: NSA 325 V2 Debian Is Possible!

$
0
0
lolinger,

> Noted that no cpufreq folder is created unter /sys
> /devices/system/cpu/cpu0. Therefore the CPU-clock
> is 1,6GHz all time. I am using latest rootfs and k
> ernel image.
> cpufreq-info gives the following error:
> analyzing CPU 0:
> no or unknown cpufreq-driver active
>
> What's happening? The kirkwood cpufreq-driver is n
> ot supported by the kernel?

It is not supported by the kernel. Most of original Kirkwood plugs have very low power consumption at idle so that was never considered.

Since we have now several Kirkwood NAS that could use the feature, I will add it to the next release if so requested.
Viewing all 359 articles
Browse latest View live