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

Re: NSA 325 V2 Debian Is Possible!

May 22, 2017, 5:48 am
$
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
↧
Search

Re: NSA 325 V2 Debian Is Possible!

May 22, 2017, 6:15 am
$
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!

May 22, 2017, 6:44 am
$
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!

May 22, 2017, 7:30 am
$
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!

May 22, 2017, 8:22 am
$
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!

May 22, 2017, 9:58 pm
$
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!

May 23, 2017, 2:36 am
$
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!

May 23, 2017, 11:29 am
$
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
↧
Search

Re: NSA 325 V2 Debian Is Possible!

May 26, 2017, 1:53 am
$
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!

May 26, 2017, 4:32 am
$
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.
↧

Re: NSA 325 V2 Debian Is Possible!

May 26, 2017, 7:52 am
$
0
0
I'd be very happy if you could do that.
Don't forget that there are countries with very high energy prices.
↧

Re: NSA 325 V2 Debian Is Possible!

May 26, 2017, 7:28 pm
$
0
0
lolinger,

> Don't forget that there are countries with very hi
> gh energy prices.

Indeed! I will add that to the kernel.
↧

Re: NSA 325 V2 Debian Is Possible!

July 9, 2017, 12:16 am
$
0
0
Well,

uBoot is stuck after loading the Kernel with linux-4.11.3-kirkwood-tld-2. The kernel does not boot up after loading. I am still using linux-4.10.9-kirkwood-tld-1 which works fine for me but without cpufreq of course.
I boot with DTB files included in the kernel and EXT2 for boot partition.
↧
↧

Re: NSA 325 V2 Debian Is Possible!

July 9, 2017, 1:30 am
$
0
0
lolinger,

> uBoot is stuck after loading the Kernel with linux
> -4.11.3-kirkwood-tld-2. The kernel does not boot u
> p after loading. I am still using linux-4.10.9-kir
> kwood-tld-1 which works fine for me but without cp
> ufreq of course.
> I boot with DTB files included in the kernel and E
> XT2 for boot partition.

Do you have serial console? and what did you try to set in Debian before rebooting?
↧

Re: NSA 325 V2 Debian Is Possible!

July 9, 2017, 3:20 am
$
0
0
Yeah, I have a serial console.
After U-Boot is done with loading the kernel and ramdisk, nothing happens.
↧
Search

Re: NSA 325 V2 Debian Is Possible!

July 9, 2017, 3:39 am
$
0
0
lolinger,

The cpufreq is working on a few of my boxes with linux-4.11.3-kirkwood-tld-2.

If you don't post your serial console boot log then I have no idea what's wrong with your NSA325 :)

If you'd like me to help figure out, then power up, interrupt serial console and 
printenv
boot
↧

Re: NSA 325 V2 Debian Is Possible!

July 12, 2017, 1:47 pm
$
0
0
Same problem here with fresh install on NSA325v2 with rootfs Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2. After installing linux-4.11.3-kirkwood-tld-2-bodhi.tar.bz2 and reboot the NSA is stuck in Loading Kernel. With 4.10.9 its working.
↧
↧

Re: NSA 325 V2 Debian Is Possible!

July 12, 2017, 3:56 pm
$
0
0
andreasnsa & lolinger,

I'm running my NSA325v2 with this latest kernel linux-4.11.3-kirkwood-tld-2 for a while. And just rebooted it a couple days ago. So not sure what is the problem in your box.

1. Which u-boot are you running in your box? my latest release, or stock?
2. If running my u-boot image, do you have netconsole? Please post that log.
3. Do you have serial console, and if yes, please post the serial boot log.
↧

Re: NSA 325 V2 Debian Is Possible!

July 22, 2017, 4:52 am
$
0
0
hello... i would like to update my uboot... i.m confused, what have to do now?
i haven't managed to run debian....
my bootenv is mess
i'm in this point.......



U-Boot 2014.07-tld-4 (Aug 02 2015 - 00:40:12)
ZyXEL NSA325 2-Bay Power Media Server

SoC: Kirkwood 88F6282_??
DRAM: 512 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0 [PRIME]
MV88E1318 PHY initialized on egiga0
Unknown command 'button' - try 'help'
Unknown command 'button' - try 'help'
Unknown command 'button' - try 'help'
Hit any key to stop autoboot: 0

NAND read: invalid mtd device 'nand_mtd'
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
NSA325>
↧

Re: NSA 325 V2 Debian Is Possible!

July 22, 2017, 2:43 pm
$
0
0
crstil1979,

Quote

U-Boot 2014.07-tld-4 (Aug 02 2015 - 00:40:12)

This is relatively new version. So to set the envs correctly and boot into Debian :

1. Create the Debian rootfs if you have not done so, using Debian-4.4.0-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (or use your existing rootfs if you already have one before that boots OK):

http://forum.doozan.com/read.php?2,12096

2. And then follow the instruciton in this post to create the default envs file uEnv.txt:

http://forum.doozan.com/read.php?2,14351,23556#msg-23556

3. Boot and watch serial console. Post the bootlog here if you have problem booting completely into Debian.
↧
Viewing all 359 articles
Browse latest View live
Search