ZyXEL NSA320 booted from USB...once!

[lulo]

orginal automaticaly created /etc/network.d/wired-eth0
$this->bbcode_second_pass_code('', '
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
INTERFACE='eth0'
IP='dhcp'
## for DHCPv6
#IP6='dhcp'
## for IPv6 autoconfiguration
#IP6='stateless'

## Example of static eth0
#CONNECTION='ethernet'
#DESCRIPTION='A basic static ethernet connection using iproute'
#INTERFACE='eth0'
#IP='static'
#ADDR='192.168.1.23'
#ROUTES=('192.168.0.0/24 via 192.168.1.2')
#GATEWAY='192.168.1.1'
#DNS=('192.168.1.1')

## For IPv6 autoconfiguration
#IP6=stateless

## For IPv6 static address configuration
#IP6='static'
#ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#ROUTES6=('abcd::1234')
#GATEWAY6='1234:0:123::abcd'
[root@alarm ~]#
')

Your suggestions - add this line and actual config :
$this->bbcode_second_pass_code('', '
CONNECTION='ethernet'
DESCRIPTION='A basic dhcp ethernet connection using iproute'
PRE_UP="/sbin/ifconfig eth1 hw ether 00:19:cb:00:51:81"
INTERFACE='eth0'
IP='dhcp'
## for DHCPv6
#IP6='dhcp'
## for IPv6 autoconfiguration
#IP6='stateless'

## Example of static eth0
#CONNECTION='ethernet'
#DESCRIPTION='A basic static ethernet connection using iproute'
#INTERFACE='eth0'
#IP='static'
#ADDR='192.168.1.23'
#ROUTES=('192.168.0.0/24 via 192.168.1.2')
#GATEWAY='192.168.1.1'
#DNS=('192.168.1.1')

## For IPv6 autoconfiguration
#IP6=stateless

## For IPv6 static address configuration
#IP6='static'
#ADDR6=('1234:5678:9abc:def::1/64' '1234:3456::123/96')
#ROUTES6=('abcd::1234')
#GATEWAY6='1234:0:123::abcd'
[root@alarm ~]#
')

00:19:cb:00:51:81 = printenv ( ...ethaddr=00:19:CB:00:51:81...)
Im not find any other address MAC - reset printenv and start oryginal FW = ethaddr=00:19:CB:00:51:81 => nsa-310 working perfectly for this MAC and wol working.
If use this MAC for archlinux ( PRE_UP="/sbin/ifconfig eth1 hw ether 00:19:cb:00:51:81" ) wol not working and actually internet not working.
eth0 and eth1 its the same address MAC from archlinux:
$this->bbcode_second_pass_code('', '
[root@alarm ~]# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::219:cbff:fe00:5181 prefixlen 64 scopeid 0x20<link>
ether 00:19:cb:00:51:81 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 10 bytes 1348 (1.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 11

eth1: flags=4098<BROADCAST,MULTICAST> mtu 1500
ether 00:19:cb:00:51:81 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 68 bytes 4804 (4.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 68 bytes 4804 (4.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@alarm ~]#
')

boot (netcfg.service) not produce any ethernet address, only if manually "dhcp eth1":
$this->bbcode_second_pass_code('', '
[root@alarm ~]# dhcpcd eth0
dhcpcd[179]: version 5.6.8 starting
dhcpcd[179]: eth0: sending IPv6 Router Solicitation
dhcpcd[179]: eth0: broadcasting for a lease
dhcpcd[179]: eth0: sending IPv6 Router Solicitation
dhcpcd[179]: eth0: sending IPv6 Router Solicitation
dhcpcd[179]: eth0: sending IPv6 Router Solicitation
dhcpcd[179]: eth0: no IPv6 Routers available
dhcpcd[179]: timed out
[root@alarm ~]# [ 217.518701] usb 1-1.2: USB disconnect, device number 3

[root@alarm ~]# dhcpcd eth1
dhcpcd[197]: version 5.6.8 starting
[ 239.231033] r8169 0000:00:01.0 eth1: link down
[ 239.235516] r8169 0000:00:01.0 eth1: link down
[ 239.243215] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
dhcpcd[197]: eth1: waiting for carrier
[ 241.241322] r8169 0000:00:01.0 eth1: link up
[ 241.245632] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
dhcpcd[197]: eth1: carrier acquired
dhcpcd[197]: eth1: sending IPv6 Router Solicitation
dhcpcd[197]: eth1: sendmsg: Cannot assign requested address
dhcpcd[197]: eth1: broadcasting for a lease
dhcpcd[197]: eth1: offered xxx.xxx.1.206 from xxx.xxx.1.1
dhcpcd[197]: eth1: acknowledged xxx.xxx.1.206 from xxx.xxx.1.1
dhcpcd[197]: eth1: checking for xxx.xxx.1.206
dhcpcd[197]: eth1: sending IPv6 Router Solicitation
dhcpcd[197]: eth1: leased xxx.xxx.1.206 for 43200 seconds
dhcpcd[197]: forked to background, child pid 228
[root@alarm ~]# ping google.com
PING google.com (208.117.224.103) 56(84) bytes of data.
64 bytes from cache.google.com (208.117.224.103): icmp_seq=1 ttl=57 time=8.24 ms
64 bytes from cache.google.com (208.117.224.103): icmp_seq=2 ttl=57 time=6.96 ms
64 bytes from cache.google.com (208.117.224.103): icmp_seq=3 ttl=57 time=7.87 ms
64 bytes from cache.google.com (208.117.224.103): icmp_seq=4 ttl=57 time=8.78 ms
64 bytes from cache.google.com (208.117.224.103): icmp_seq=5 ttl=57 time=7.95 ms
64 bytes from cache.google.com (208.117.224.103): icmp_seq=6 ttl=57 time=7.59 ms
64 bytes from cache.google.com (208.117.224.103): icmp_seq=7 ttl=57 time=9.71 ms

--- google.com ping statistics ---
7 packets transmitted, 7 received, 0% packet loss, time 6009ms
rtt min/avg/max/mdev = 6.968/8.160/9.713/0.825 ms
[root@alarm ~]#
')

after ifconfig:
$this->bbcode_second_pass_code('', '
[root@alarm ~]# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80::219:cbff:fe00:5181 prefixlen 64 scopeid 0x20<link>
ether 00:19:cb:00:51:81 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18 bytes 3108 (3.0 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 11

eth1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet xxx.xxx.1.206 netmask 255.255.255.0 broadcast 113.114.1.255
inet6 fe80::219:cbff:fe00:5181 prefixlen 64 scopeid 0x20<link>
ether 00:19:cb:00:51:81 txqueuelen 1000 (Ethernet)
RX packets 9511 bytes 657058 (641.6 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 24963 bytes 35543503 (33.8 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 0 (Local Loopback)
RX packets 100 bytes 7044 (6.8 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 100 bytes 7044 (6.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[root@alarm ~]#
')

after wol (from router, computer, etc.) not working

can use "stupid" method:
$this->bbcode_second_pass_code('', '
systemctl enable dhcpcd
')
internet not working at boot, only if use manually:
$this->bbcode_second_pass_code('', '
systemctl restart dhcpcd
')

[moonman]

https://wiki.archlinux.org/index.php/MA ... s_Spoofing

I believe it has to be dhcpcd@ethX not just dhcpcd

[lulo]

ok...this solution fix problem ethernet (internet) start at boot system:
$this->bbcode_second_pass_code('', 'systemctl enable dhcpcd@eth1')

When new properly http://os.archlinuxarm.org/os/ArchLinux ... est.tar.gz ?

[moonman]

Lulo, can you test 3.1 kernel? (pacman -Sy linux) and post lspci, sensors, dmesg here. Also about errors on the internal memory, i dont think we can do anything, but it doesn't affect usability.

[lulo]

uname, lm_sensors (ec. sensors-detect working can load ec. modules), lspci:
$this->bbcode_second_pass_code('', '
[root@alarm ~]# date
wto, 21 maj 2013, 09:27:28 CEST
[root@alarm ~]# uname -a
Linux alarm 3.1.10-20-ARCH #1 PREEMPT Sat May 18 14:37:07 UTC 2013 armv5tel GNU/Linux
[root@alarm ~]# modprobe lm85
[root@alarm ~]# modprobe i2c-mv64xxx
[root@alarm ~]# lsmod
Module Size Used by
rtc_pcf8563 2187 0
i2c_mv64xxx 4121 0
lm85 14856 0
hwmon_vid 1366 1 lm85
hwmon 1187 1 lm85
i2c_core 15344 3 lm85,i2c_mv64xxx,rtc_pcf8563
mv_cesa 9128 0
ipv6 259694 14
autofs4 22074 2
[root@alarm ~]# sensors-detect
# sensors-detect revision 6085 (2012-10-30 18:18:45 +0100)
# DMI data unavailable, please consider installing dmidecode 2.7
# or later for better results.

This program will help you determine which kernel modules you need
to load to use lm_sensors most effectively. It is generally safe
and recommended to accept the default answers to all questions,
unless you know what you're doing.

Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
modprobe: FATAL: Module cpuid not found.
Failed to load module cpuid.
Silicon Integrated Systems SIS5595... No
VIA VT82C686 Integrated Sensors... No
VIA VT8231 Integrated Sensors... No
AMD K8 thermal sensors... No
AMD Family 10h thermal sensors... No
AMD Family 11h thermal sensors... No
AMD Family 12h and 14h thermal sensors... No
AMD Family 15h thermal sensors... No
AMD Family 15h power sensors... No
Intel digital thermal sensor... No
Intel AMB FB-DIMM thermal sensor... No
VIA C7 thermal sensor... No
VIA Nano thermal sensor... No

Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'... No
Trying family `SMSC'... No
Trying family `VIA/Winbond/Nuvoton/Fintek'... No
Trying family `ITE'... No

Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0... No
Probing for `IPMI BMC SMIC' at 0xca8... No

Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
Probing for `National Semiconductor LM78' at 0x290... No
Probing for `National Semiconductor LM79' at 0x290... No
Probing for `Winbond W83781D' at 0x290... No
Probing for `Winbond W83782D' at 0x290... No

Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Sorry, no supported PCI bus adapters found.
Module i2c-dev loaded successfully.

Next adapter: mv64xxx_i2c adapter (i2c-0)
Do you want to scan it? (YES/no/selectively):
Client found at address 0x2e
Handled by driver `lm85' (already loaded), chip type `lm85'
Client found at address 0x51
Handled by driver `rtc_pcf8563' (already loaded), chip type `pcf8563'
(note: this is probably NOT a sensor chip!)

Now follows a summary of the probes I have just done.
Just press ENTER to continue:

Driver `lm85':
* Bus `mv64xxx_i2c adapter'
Busdriver `i2c_mv64xxx', I2C address 0x2e
Chip `lm85' (confidence: 6)

Do you want to generate /etc/conf.d/lm_sensors? (YES/no):
ln -s '/usr/lib/systemd/system/lm_sensors.service' '/etc/systemd/system/multi-user.target.wants/lm_sensors.service'
Unloading i2c-dev... OK

[root@alarm ~]# sensors
lm85-i2c-0-2e
Adapter: mv64xxx_i2c adapter
in0: +1.80 V (min = +0.00 V, max = +3.32 V)
Vcore: +1.09 V (min = +0.00 V, max = +2.99 V)
+3.3V: +3.23 V (min = +2.97 V, max = +3.63 V)
+5V: +5.10 V (min = +4.50 V, max = +5.50 V)
+12V: +12.25 V (min = +0.00 V, max = +15.94 V)
fan1: 4963 RPM (min = 0 RPM)
fan2: 0 RPM (min = 0 RPM)
fan3: 0 RPM (min = 0 RPM)
fan4: 0 RPM (min = 0 RPM)
temp1: +31.0°C (low = -127.0°C, high = +127.0°C)
M/B Temp: +32.0°C (low = -127.0°C, high = +127.0°C)
temp3: +35.0°C (low = -127.0°C, high = -19.0°C)
cpu0_vid: +0.000 V

[root@alarm ~]# lspci -vv
00:00.0 Host bridge: Marvell Technology Group Ltd. 88F6281 [Kirkwood] ARM SoC (rev 03)
Subsystem: Marvell Technology Group Ltd. Device 11ab
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 9
Region 0: Memory at <ignored> (64-bit, prefetchable)
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [60] Express (v1) Root Port (Slot-), MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <256ns, L1 <1us
ExtTag- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 512 bytes
DevSta: CorrErr- UncorrErr- FatalErr- UnsuppReq- AuxPwr- TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <256ns, L1 unlimited
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 128 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
RootCtl: ErrCorrectable- ErrNon-Fatal- ErrFatal- PMEIntEna- CRSVisible-
RootCap: CRSVisible-
RootSta: PME ReqID 0000, PMEStatus- PMEPending-
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr-
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap- CGenEn- ChkCap- ChkEn-

00:01.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 03)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 9
Region 0: I/O ports at 1000 [size=256]
Region 2: Memory at e0014000 (64-bit, prefetchable) [size=4K]
Region 4: Memory at e0010000 (64-bit, prefetchable) [size=16K]
[virtual] Expansion ROM at e0000000 [disabled] [size=64K]
Capabilities: [40] Power Management version 3
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=375mA PME(D0+,D1+,D2+,D3hot+,D3cold+)
Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
Address: 0000000000000000 Data: 0000
Capabilities: [70] Express (v2) Endpoint, MSI 01
DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s <512ns, L1 <64us
ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset-
DevCtl: Report errors: Correctable- Non-Fatal- Fatal- Unsupported-
RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 4096 bytes
DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr+ TransPend-
LnkCap: Port #0, Speed 2.5GT/s, Width x1, ASPM L0s L1, Latency L0 <512ns, L1 <64us
ClockPM+ Surprise- LLActRep- BwNot-
LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk-
ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
DevCap2: Completion Timeout: Not Supported, TimeoutDis+, LTR-, OBFF Not Supported
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, OBFF Disabled
LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete-, EqualizationPhase1-
EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
Capabilities: [ac] MSI-X: Enable- Count=4 Masked-
Vector table: BAR=4 offset=00000000
PBA: BAR=4 offset=00000800
Capabilities: [cc] Vital Product Data
Unknown small resource type 00, will not decode more.
Capabilities: [100 v1] Advanced Error Reporting
UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
AERCap: First Error Pointer: 00, GenCap+ CGenEn- ChkCap+ ChkEn-
Capabilities: [140 v1] Virtual Channel
Caps: LPEVC=0 RefClk=100ns PATEntryBits=1
Arb: Fixed- WRR32- WRR64- WRR128-
Ctrl: ArbSelect=Fixed
Status: InProgress-
VC0: Caps: PATOffset=00 MaxTimeSlots=1 RejSnoopTrans-
Arb: Fixed- WRR32- WRR64- WRR128- TWRR128- WRR256-
Ctrl: Enable+ ID=0 ArbSelect=Fixed TC/VC=ff
Status: NegoPending- InProgress-
Capabilities: [160 v1] Device Serial Number 00-00-00-00-00-00-00-00
Kernel driver in use: r8169

[root@alarm ~]#
')

and dmesg:
http://pastebin.com/mPtkj5qX

and full boot process and above (from RS232):
http://pastebin.com/3pQFFMPm
1) fw_printenv not working
2) use "trick" to netcfg

Question:
Not loaded and detect from boot kernel (driver r8169 ?) sleep MAC adrdress from my ethernet, embeded card (can firmware orginal): 00:00:00:00:00:30 ???

Generally working...only bad mapping DDR, NAND, PCIe (????) or bad sectors from disk (using external and internal e2fsck - no any bad block,sectors,etc. and all for disk ok - any change - this is the same situations). Using generally new installation (hackable telnet,ssh,etc.) from my modified script (oryginal script = http://os.archlinuxarm.org/os/nsa3x0/ns ... arm.tar.gz ).

my modified usb_key_func.sh.2
$this->bbcode_second_pass_code('', '
#!/bin/sh

#####
# Created By: Jason Plum <jplum@archlinuxarm.org>
# Prepared for: Arch Linux ARM
# ----------
# Automation to convert NSA-310 to Arch Linux ARM on /dev/sda
# : /dev/sda is sata port 1, left side of enclosure.
#####
echo "Automatic Installation of Arch Linux ARM"

###
# setup u-boot environment
echo "- set bootloader"
fw_setenv arcNumber 4022
fw_setenv mainlineLinux yes
fw_setenv 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'
fw_setenv 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 rw rootwait loglevel=8'
fw_setenv bootcmd_linux 'setenv bootargs $(bootargs_linux); ide reset; ext2load ide 0:1 $(loadaddr) /uImage; bootm $(loadaddr)'
fw_setenv bootcmd_stock 'setenv bootargs $(bootargs_stock); nand read.e $(loadaddr) $(kernel_addr) 0xA00000; bootm $(loadadr)'
fw_setenv to_stock "setenv mainlineLinux no; setenv bootcmd \'run bootcmd_stock\'; saveenv; reset"
fw_setenv to_linux "setenv mainlineLinux yes; setenv bootcmd \'run bootcmd_linux\'; saveenv; reset"

###
# setup the partitions on the disk (sda)
# : 16M 1st partition, ext2/3
echo "- parition sda"
fdisk /dev/sda <<EOF
o
n
p
1

+16M

n
p
2


p
w

EOF
echo " * pause for ioctl to re-sync partitions"
sleep 5
###
# make filesystems
echo "- make filesystems"
# ext2 makes u-boot happy.
mkfs.ext2 -L "boot" /dev/sda1
# stock does not know how to make ext4!
mkfs.ext4 -L "rootfs" /dev/sda2

###
# make dirs & mount
echo "- mount destination"
mkdir -p /tmp/boot
mount -t ext2 /dev/sda1 /tmp/boot
mkdir -p /tmp/rootfs
mount -t ext4 /dev/sda2 /tmp/rootfs

###
# prepare the system
# extract the rootfs
echo "- extract rootfs"
#tar xzf /mnt/parnerkey/rootfs.tgz -C /tmp/rootfs/
tar xzf /e-data/C96D-6C40/rootfs.tgz -C /tmp/rootfs/

# copy the uImage to the boot partition
echo "- prepare boot partition"
cp -aR /tmp/rootfs/boot/* /tmp/boot/

# always make sure you're sync'd!
sync

###
# prepare for first boot
# set the bootcmd to run the steps to convert.
fw_setenv bootcmd 'run to_linux'
###
# we're done here
echo "- REBOOTING!"
sync
reboot
')

1) Installations from pendrive only working from this path: /e-data
2) /mnt and other path - no any info data to pendrive
3) md5sum its bad (salted_md5sum_3x0)
4) C96D-6C40 = my uuid pendrive (from label - not working).
Generally automatic installation not working - using only manualy installation can exec this modified script usb_key_func.sh.2.
(My oryginal FW is last - 5.1 - can use <= 4.4 - identical situation).

#########################################################################################################
I don't know:
Can use oryginal fw and archlinux ( <=linux-3.1.10-19 and <=linux-kirkwood-3.9.1-1) its the same error from boot:
$this->bbcode_second_pass_code('', '
...
...
[ 16.909633] Bad eraseblock 693 at 0x0000056a0000
[ 16.937938] Bad eraseblock 919 at 0x0000072e0000
[ 16.945573] Bad eraseblock 948 at 0x000007680000
...
...
')

Maybe and probably NAND its bad from this address or any other data write and not cleanly read,write,delete, etc.

Core my question:
How to permanently erase all data from NAND and cleanly installations oryginal FW ???
- please step by step - can my children.

After planed install archlinux. Not clean read NAND = other problems from investigation and analizes boot process to developers from planed properly patch to kernel (NSA-310) and probably my automatic installation (without bad arcNumber from oryginal script) => success ??? (salted_md5sum_3x0...maybe).

[WarheadsSE]

In uboot:
$this->bbcode_second_pass_code('', '
run to_stock
')

I've never altered the NAND. The number for the 310 matches the registered devices.

[lulo]

run to_stock from uboot:

http://pastebin.com/mC8nQr7A

[WarheadsSE]

That is stock. What of it? That's what you wanted, yes?

[lulo]

No, I wanted full properly working (boot clear, working all driver properly, etc.) archlinux .

[moonman]

1. messages about bad blocks. One of the developers would probably require a device to fix this. But really, these messages are harmless and don't affect anything and you can just ignore them.
2. MAC address for r8169. I've seen a patch where the MAC is hardcoded. That's the only fix I've seen so far for this problem. Again, this can easily be fixed with mac spoofing.

Are there any other things that don't work?

https://github.com/peeter123/NSA310-320 ... /README.md
Read through this for leds, power button etc... Also note Known bugs: All mtd blocks read as bad. The chip is somehow not supported by kernel.