NSA 320

Install Arch Linux ARM on other devices.

Re: NSA 320

Postby Tonkiplis2 » Wed Feb 20, 2013 10:02 pm

Thx WarheadsSE that works :)

Now I have the next problem, I have no result when I ping the device, and I don't know wheter the ssh deamon is on...

is anybody experiencing the same issue? Is there anything wrong in the boot log repoorted above? :)

I am sorry for all these questions, but I am lost... :(((

Cheers,

Tonkiplis
Tonkiplis2
 
Posts: 19
Joined: Wed Jan 09, 2013 7:01 am

Re: NSA 320

Postby prokrypt » Fri Feb 22, 2013 6:08 am

$this->bbcode_second_pass_quote('Tonkiplis2', 'I')s there anything wrong in the boot log repoorted above? :)

$this->bbcode_second_pass_code('', '[FAILED] Failed to start Netcfg multi-profile daemon.
See 'systemctl status netcfg.service' for details.')

SSH daemon is started. You just need to figure out why netcfg fails. Try to boot into stock, then reboot back to archlinux and see if network still notwork :]
prokrypt
 
Posts: 31
Joined: Thu Dec 27, 2012 4:45 am

Re: NSA 320

Postby Tonkiplis2 » Sat Feb 23, 2013 6:08 pm

Now the ssh deamon starts and I can ping the device:

$this->bbcode_second_pass_code('', '[ OK ] Started Periodic Command Scheduler.
[ 23.321820] systemd[1]: Started Periodic Command Scheduler.
[ 23.331661] systemd[1]: Starting OpenSSH Daemon...
Starting OpenSSH Daemon...
[ OK ] Started OpenSSH Daemon.
[ 23.411770] systemd[1]: Started OpenSSH Daemon.
[ 23.416496] systemd[1]: Starting Login Service...
Starting Login Service...
[ 23.472241] systemd[1]: Starting D-Bus System Message Bus...
Starting D-Bus System Message Bus...
[ OK ] Started D-Bus System Message Bus.
[ 23.561726] systemd[1]: Started D-Bus System Message Bus.
[ 23.572642] systemd[1]: Starting System Logger Daemon...
Starting System Logger Daemon...
[ OK ] Started System Logger Daemon.
[ 23.671739] systemd[1]: Started System Logger Daemon.
[ 23.681176] systemd[1]: Starting Permit User Sessions...
Starting Permit User Sessions...
[ OK ] Started Permit User Sessions.')

ping :

$this->bbcode_second_pass_code('', 'ping 192.168.1.51
PING 192.168.1.51 (192.168.1.51): 56 data bytes
64 bytes from 192.168.1.51: icmp_seq=0 ttl=64 time=1.877 ms
64 bytes from 192.168.1.51: icmp_seq=1 ttl=64 time=2.136 ms
64 bytes from 192.168.1.51: icmp_seq=2 ttl=64 time=4.230 ms
64 bytes from 192.168.1.51: icmp_seq=3 ttl=64 time=2.194 ms
64 bytes from 192.168.1.51: icmp_seq=4 ttl=64 time=2.724 ms
64 bytes from 192.168.1.51: icmp_seq=5 ttl=64 time=3.257 ms
^X^C
--- 192.168.1.51 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.877/2.736/4.230/0.806 ms
')

when i try to ssh the ip:

$this->bbcode_second_pass_code('', 'ssh root@192.168.1.51
root@192.168.1.51's password:

')

it never ends. Does anyone has a solution? =))
Tonkiplis2
 
Posts: 19
Joined: Wed Jan 09, 2013 7:01 am

Re: NSA 320

Postby WarheadsSE » Sat Feb 23, 2013 7:27 pm

Check the mount options of /
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: NSA 320

Postby va1210 » Thu Feb 28, 2013 10:13 pm

I'm having trouble enabling Arch Linux on my NSA 320. I tried to run the USB installer, but the installation failed in a similar fashion as others here. I partitioned and installed the HD according to the usb_key_func_sh.2 script, and to the best of my abilities tried to fix the environment variables on the NSA, also according to the script. Now when I try to boot up the machine I get the following on the serial:

$this->bbcode_second_pass_code('', 'NSA320>> run to_linux
Saving Environment to NAND...
Erasing Nand...Writing to Nand... done

__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** MARVELL BOARD: RD-88F6281A LE

U-Boot 1.1.4 (Mar 23 2011 - 16:09:39) Marvell version: 3.4.19

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 006CFEE0

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 256MB
DRAM CS[1] base 0x10000000 size 256MB
DRAM Total size 512MB 16bit width
Addresses 10M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (10M - 7M): Done
NAND:128 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
//--- stateButtonBit = 3, recovery ---//
Kernel address is 0xc80000.

Streaming disabled
Write allocate disabled

Module 0 is RGMII
Module 1 is TDM

USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0, egiga1 [PRIME]
Hit any key to stop autoboot: 0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found

** Bad partition 1 **
## Booting image at 02000000 ...
Bad Magic Number
')

Printenv shows the following:

$this->bbcode_second_pass_code('', 'NSA320>> printenv
bootdelay=2
baudrate=115200
loads_echo=0
eth1addr=00:19:CB:00:51:82
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
nandEcc=1bit
MODEL_ID=DD01
PRODUCT_NAME=NSA-320
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=ZyXEL Communications Corp.
run_diag=yes
ethaddr=B0:B2:DC:EE:D7:7F
console=100000
=ttyS0,115200 mtdparts=nand_mtd:0xc0000@0(uboot)ro,0x7f00000@0x100000(root)
CASset=min
ethprime=egiga1
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;
ethmtu=1500
eth1mtu=1500
mvPhoneConfig=mv_phone_config=dev0:fxs,dev1:fxs
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
MALLOC_len=3
arcNumber=3956
to_stock=setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset
to_linux=setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset
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=/dev/sda2 ro rootwait loglevel=8
bootcmd_linux=setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr) /uImage; bootm $(loadaddr)
bootcmd_stock=setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)
bootcmd='run bootcmd_linux'
stdin=serial
stdout=serial
stderr=serial
nandEnvBase=100000
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
hddPowerCtrl=no
enaAutoRecovery=yes
kernel_addr=0xc80000
pcieTune=no
ethact=egiga1
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/sda2 ro rootwait loglevel=8

Environment size: 2464/131068 bytes
')

Any idea what I'm doing wrong? All help would be much appreciated..

Ville
va1210
 
Posts: 9
Joined: Thu Feb 28, 2013 10:03 pm

Re: NSA 320

Postby WarheadsSE » Thu Feb 28, 2013 10:32 pm

Is your disk partitioned with MBR or GPT?
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: NSA 320

Postby va1210 » Thu Feb 28, 2013 11:05 pm

I would expect MBR (I did the partitioning with fdisk exactly like the script, starting with the 'o' option), but I'm not completely 100% sure. But I'll check first thing tomorrow.
va1210
 
Posts: 9
Joined: Thu Feb 28, 2013 10:03 pm

Re: NSA 320

Postby va1210 » Fri Mar 01, 2013 4:01 pm

Yes, the drive was definitely partitioned as MBR. Another interesting observation: when I boot into stock, fdisk is unable detect both /dev/sda and /dev/sdb even when they're plugged in normally (on bootup there is even a message stating that both drives are disconnected). However, at the same time, the web ui is able to format the disk just fine. Are the sata devices perhaps called something different than /dev/sdx? The hardware is very fresh and came preflashed with 4.50, so perhaps the hardware is incompatible with the standard drivers..
va1210
 
Posts: 9
Joined: Thu Feb 28, 2013 10:03 pm

Re: NSA 320

Postby WarheadsSE » Fri Mar 01, 2013 4:24 pm

That would be.. odd. But I would not put ZyXEL past doing something interesting. If the webui is indeed seeing them, then there is a chance that the power line has not been enabled, and thus, it is not showing until that is flipped up.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: NSA 320

Postby va1210 » Fri Mar 01, 2013 6:17 pm

Are you referring to the power resume script? Tried that too, but I can't even find gpio under /sys:

$this->bbcode_second_pass_code('', '/ # ls /sys
block class devices fs module
bus dev firmware kernel')

Regarding the harddrive, this is what fdisk tells me:

$this->bbcode_second_pass_code('', '/ # fdisk /dev/sda

Unable to open /dev/sda')

However, dmesg does show some sda action:

$this->bbcode_second_pass_code('', '/ # dmesg|grep sda
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/465 GiB)
sd 0:0:0:0: [sda] 0-byte physical blocks
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 23 00 10 00
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sda:
sda1 sda2
sd 0:0:0:0: [sda] Sector size 0 reported, assuming 512.
sd 0:0:0:0: [sda] Attached SCSI disk
sd 0:0:0:0: [sda] Synchronizing SCSI cache
sd 0:0:0:0: [sda] Result: hostbyte=0x01 driverbyte=0x00')

Dev looks like this:

$this->bbcode_second_pass_code('', '/ # ls /dev/sda*
/dev/sda /dev/sda11 /dev/sda14 /dev/sda3 /dev/sda6 /dev/sda9
/dev/sda1 /dev/sda12 /dev/sda15 /dev/sda4 /dev/sda7
/dev/sda10 /dev/sda13 /dev/sda2 /dev/sda5 /dev/sda8')

Another annoyance, every 10 seconds I get the following on my console:

$this->bbcode_second_pass_code('', '/ # Traceback (most recent call last):
File "./cdsdaemon.py", line 472, in <module>
File "./cdsdaemon.py", line 440, in createDB
sqlite3.OperationalError: unable to open database file')
va1210
 
Posts: 9
Joined: Thu Feb 28, 2013 10:03 pm

PreviousNext

Return to [Please read announcement] Community-Supported Devices

Who is online

Users browsing this forum: No registered users and 5 guests