Home
>
Rescue System
>
Topic
uboot NSA310 - probably erase uboot
Posted by kofec
|
uboot NSA310 - probably erase uboot January 25, 2017 02:53PM |
Registered: 9 years ago Posts: 38 |
Hi,
I think I kill my uboot when I try test latest changes in LEDE:
I follow the procedure:
https://github.com/lede-project/source/pull/656#issuecomment-274945142
I compile the uboot:
~/openwrt/LEDEnsa310 $ ls -alh bin/targets/kirkwood/generic/u-boot-nsa310/
total 1,5M
508K Jan 25 21:28 u-boot.bin
508K Jan 25 21:28 u-boot.img
508K Jan 25 21:28 u-boot.kwb
and take u-boot.bin
then on console:
nvironment size: 2960/131068 bytes
And then lost communication forever :-(
Is there anything I can do ?
---
Mod edit: use code tags
Edited 2 time(s). Last edit at 01/25/2017 03:56PM by bodhi.
I think I kill my uboot when I try test latest changes in LEDE:
I follow the procedure:
https://github.com/lede-project/source/pull/656#issuecomment-274945142
I compile the uboot:
~/openwrt/LEDEnsa310 $ ls -alh bin/targets/kirkwood/generic/u-boot-nsa310/
total 1,5M
508K Jan 25 21:28 u-boot.bin
508K Jan 25 21:28 u-boot.img
508K Jan 25 21:28 u-boot.kwb
and take u-boot.bin
then on console:
nvironment size: 2960/131068 bytes
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found
NSA310> fatload usb 0 0x1000000 uboot.bin
reading uboot.bin
519520 bytes read in 41 ms (12.1 MiB/s)
NSA310> nand write 0x1000000 0x00000 0x100000
NAND write: device 0 offset 0x0, size 0x100000
NAND write to offset 0 failed -5
0 bytes written: ERROR
NSA310>
SA310> mtdparts
device nand0 <orion_nand>, # parts = 9
#: name size offset mask_flags
0: uboot 0x00100000 0x00000000 0
1: uboot_env 0x00080000 0x00100000 0
2: key_store 0x00080000 0x00180000 0
3: info 0x00080000 0x00200000 0
4: etc 0x00a00000 0x00280000 0
5: kernel_1 0x00a00000 0x00c80000 0
6: rootfs1 0x02fc0000 0x01680000 0
7: kernel_2 0x00a00000 0x04640000 0
8: rootfs2 0x02fc0000 0x05040000 0
active partition: nand0,2 - (key_store) 0x00080000 @ 0x00180000
defaults:
mtdids : none
mtdparts: none
NSA310>
NSA310>
NSA310>
NSA310>
NSA310>
NSA310> reset
resetting ...
And then lost communication forever :-(
Is there anything I can do ?
---
Mod edit: use code tags
Edited 2 time(s). Last edit at 01/25/2017 03:56PM by bodhi.
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 03:27PM |
Registered: 10 years ago Posts: 298 |
It seems you did not erase the flash before writing, raw flash must be erased before writing.
Anyway, don't worry. NSA310 cannot be bricked. :-)
NSA310 is new enough so you can recover it easily with "kwboot" tool and serial (and a linux PC), see here.
http://forum.doozan.com/read.php?3,7852,7852
This is the command that should work in your case
./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot.kwb -p
Then you need to flash the uboot as you tried before.
kwboot only loads u-boot in RAM.
fatload usb 0 0x1000000 uboot.bin
nand erase 0x00000 0x100000
nand write 0x1000000 0x00000 0x100000
reset
Anyway, don't worry. NSA310 cannot be bricked. :-)
NSA310 is new enough so you can recover it easily with "kwboot" tool and serial (and a linux PC), see here.
http://forum.doozan.com/read.php?3,7852,7852
This is the command that should work in your case
./kwboot -t -B 115200 /dev/ttyUSB0 -b u-boot.kwb -p
Then you need to flash the uboot as you tried before.
kwboot only loads u-boot in RAM.
fatload usb 0 0x1000000 uboot.bin
nand erase 0x00000 0x100000
nand write 0x1000000 0x00000 0x100000
reset
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 03:33PM |
Registered: 9 years ago Posts: 38 |
I follow your steps:
But still the same
Edited 3 time(s). Last edit at 01/25/2017 04:09PM by kofec.
95 % [......................................................................]
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
NAND read from offset c0000 failed -74
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
NSA310>
NSA310>
NSA310>
NSA310> fatload usb 0 0x1000000 uboot.bin
** Bad device usb 0 **
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
NSA310> fatload usb 0 0x1000000 uboot.bin
reading uboot.bin
519520 bytes read in 42 ms (11.8 MiB/s)
NSA310> nand erase 0x00000 0x100000
NAND erase: device 0 offset 0x0, size 0x100000
Erasing at 0xe0000 -- 100% complete.
OK
NSA310> nand write 0x1000000 0x00000 0x100000
NAND write: device 0 offset 0x0, size 0x100000
1048576 bytes written: OK
NSA310> reset
resetting ...
But still the same
Edited 3 time(s). Last edit at 01/25/2017 04:09PM by kofec.
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 03:40PM |
Registered: 9 years ago Posts: 38 |
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 03:53PM |
Registered: 9 years ago Posts: 38 |
93 % [......................................................................]
94 % [......................................................................]
96 % [......................................................................]
98 % [......................................................................]
99 % [...]
[Type Ctrl-\ + c to quit]
U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.
PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: Bus 0: OK Bus 1: not available
Device 0: Model: HGST HTS545050A7E680 Firm: GG2OAH10 Ser#: TE85134N36SSKN
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Hit any key to stop autoboot: 0
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
NSA310> fatload usb 0 0x1000000 uboot.bin
** Bad device usb 0 **
NSA310> fatload usb 1 0x1000000 uboot.bin
** Bad device usb 1 **
NSA310> fatload usb 2 0x1000000 uboot.bin
** Bad device usb 2 **
NSA310> fatload usb 3 0x1000000 uboot.bin
** Bad device usb 3 **
NSA310> usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
| u-boot EHCI Host Controller
|
+-2 Hub (480 Mb/s, 100mA)
| USB2.0 Hub
|
+-3 Mass Storage (480 Mb/s, 500mA)
SMI Corporation USB DISK
NSA310> usb start
NSA310> usb info 3
config for device 3
3: Mass Storage, USB Revision 2.0
- SMI Corporation USB DISK
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x090c Product 0x1000 Version 17.0
Configuration: 1
- Interfaces: 1 Bus Powered 500mA
Interface: 0
- Alternate Setting 0, Endpoints: 2
- Class Mass Storage, Transp. SCSI, Bulk only
- Endpoint 1 In Bulk MaxPacket 512
- Endpoint 2 Out Bulk MaxPacket 512
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
NSA310> fatload usb 3 0x1000000 uboot.bin
** Bad device usb 3 **
Edited 1 time(s). Last edit at 01/25/2017 03:57PM by bodhi.
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 03:57PM |
Admin Registered: 14 years ago Posts: 19,977 |
@kofec,
Please use code tags.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Please use code tags.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 03:59PM |
Admin Registered: 14 years ago Posts: 19,977 |
Is the drive Ext2/3 or FAT?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
ext2load usb 0:3 0x1000000 uboot.bin
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:03PM |
Registered: 9 years ago Posts: 38 |
It is fat but - it looks like I should use u-boot.kwb
Edited 1 time(s). Last edit at 01/25/2017 04:08PM by kofec.
95 % [......................................................................]
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
NSA310>
NSA310>
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
NSA310> fatload usb 0 0x1000000 u-boot.kwb
reading u-boot.kwb
520036 bytes read in 41 ms (12.1 MiB/s)
NSA310> nand erase 0x00000 0x100000
NAND erase: device 0 offset 0x0, size 0x100000
Erasing at 0xe0000 -- 100% complete.
OK
NSA310> nand write 0x1000000 0x00000 0x100000
NAND write: device 0 offset 0x0, size 0x100000
1048576 bytes written: OK
NSA310>
NSA310> reset
resetting ...
�
U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.
PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: Bus 0: OK Bus 1: not available
Device 0: Model: HGST HTS545050A7E680 Firm: GG2OAH10 Ser#: TE85134N36SSKN
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Hit any key to stop autoboot: 0
ubi0: attaching mtd1
ubi0: scanning is finished
UBI init error 22
Error, no UBI device/partition selected!
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
NSA310>
NSA310>
Edited 1 time(s). Last edit at 01/25/2017 04:08PM by kofec.
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:11PM |
Registered: 9 years ago Posts: 38 |
Ok last issue:
Edited 1 time(s). Last edit at 01/25/2017 04:11PM by kofec.
U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.
PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: Bus 0: OK Bus 1: not available
Device 0: Model: HGST HTS545050A7E680 Firm: GG2OAH10 Ser#: TE85134N36SSKN
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Hit any key to stop autoboot: 0
ubi0: attaching mtd1
ubi0: scanning is finished
UBI init error 22
Error, no UBI device/partition selected!
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
NSA310> usb tree
USB device tree:
1 Hub (480 Mb/s, 0mA)
| u-boot EHCI Host Controller
|
+-2 Hub (480 Mb/s, 100mA)
| USB2.0 Hub
|
+-3 Mass Storage (480 Mb/s, 500mA)
SMI Corporation USB DISK
NSA310> fatload usb 3 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin
** Bad device usb 3 **
NSA310> fatload usb -3 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin
** Bad device specification usb -3 **
NSA310> usb info 3
config for device 3
3: Mass Storage, USB Revision 2.0
- SMI Corporation USB DISK
- Class: (from Interface) Mass Storage
- PacketSize: 64 Configurations: 1
- Vendor: 0x090c Product 0x1000 Version 17.0
Configuration: 1
- Interfaces: 1 Bus Powered 500mA
Interface: 0
- Alternate Setting 0, Endpoints: 2
- Class Mass Storage, Transp. SCSI, Bulk only
- Endpoint 1 In Bulk MaxPacket 512
- Endpoint 2 Out Bulk MaxPacket 512
NSA310>
Edited 1 time(s). Last edit at 01/25/2017 04:11PM by kofec.
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:15PM |
Admin Registered: 14 years ago Posts: 19,977 |
Try
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
usb start fatload usb 0:3 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:29PM |
Registered: 9 years ago Posts: 38 |
Bodhi,
I start your uboot - using kwboot - the write to flash. Thanks a lot for help. Maybe you can also fix 2nd boot stage in your uboot.
I start your uboot - using kwboot - the write to flash. Thanks a lot for help. Maybe you can also fix 2nd boot stage in your uboot.
97 % [......................................................................]
99 % [....................................]
[Type Ctrl-\ + c to quit]
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
NSA310> fatload usb 0 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin
reading lede-kirkwood-nsa310b-squashfs-factory.bin
4456448 bytes read in 145 ms (29.3 MiB/s)
NSA310> nand erase.part ubi
NAND erase.part: incorrect device type in ubi
NSA310> setenv mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x100000(second_stage_uboot),0x7b80000(ubi)
## Error: illegal character '='in variable name "mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x100000(second_stage_uboot),0x7b80000(ubi)"
NSA310> setenv mtdparts mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x100000(second_stage_uboot),0x7b80000(ubi)
NSA310> nand erase.part ubi
NAND erase.part: device 0 offset 0x280000, size 0x7b80000
Skipping bad block at 0x02b80000
Skipping bad block at 0x02c60000
Skipping bad block at 0x05520000
Skipping bad block at 0x057a0000
Skipping bad block at 0x06260000
Skipping bad block at 0x073e0000
Skipping bad block at 0x07c00000
Erasing at 0x7de0000 -- 100% complete.
OK
NSA310> nand write 0x2000000 ubi 0x600000
NAND write: device 0 offset 0x280000, size 0x600000
6291456 bytes written: OK
NSA310> setenv bootcmd "run setenv bootargs; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000"
NSA310> reset
resetting ...
�
U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: egiga0
Error: egiga0 address not set.
PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: Bus 0: OK Bus 1: not available
Device 0: Model: HGST HTS545050A7E680 Firm: GG2OAH10 Ser#: TE85134N36SSKN
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Hit any key to stop autoboot: 0
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: volume 2 ("rootfs_data") re-sized from 9 to 958 LEBs
ubi0: attached mtd1 (name "mtd=2", size 126 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1007, bad PEBs: 7, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1964526799
ubi0: available PEBs: 0, total reserved PEBs: 1007, PEBs reserved for bad PEB handling: 13
Read 0 bytes from volume kernel to 800000
No size specified -> Using max size (2064384)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: ARM LEDE Linux-4.4.42
Created: 2017-01-24 19:33:45 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1951826 Bytes = 1.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.4.42 (kofec@E5420Mint) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3114-1a83d4d) ) #0 Tue Jan 24 19:33:45 2017
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: ZyXEL NSA310b
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 253776K/262144K available (3978K kernel code, 138K rwdata, 1488K rodata, 172K init, 196K bss, 8368K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc055edb4 (5468 kB)
[ 0.000000] .init : 0xc055f000 - 0xc058a000 ( 172 kB)
[ 0.000000] .data : 0xc058a000 - 0xc05ac880 ( 139 kB)
[ 0.000000] .bss : 0xc05ac880 - 0xc05ddc0c ( 197 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000089] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[ 0.090081] pid_max: default: 32768 minimum: 301
[ 0.090192] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090211] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090744] CPU: Testing write buffer coherency: ok
[ 0.091109] Setting up static identity map for 0x81e0 - 0x821c
[ 0.091427] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.096505] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.096662] pinctrl core: initialized pinctrl subsystem
[ 0.097799] NET: Registered protocol family 16
[ 0.098145] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.099046] cpuidle: using governor ladder
[ 0.099398] Feroceon L2: Enabling L2
[ 0.099443] Feroceon L2: Cache support initialised.
[ 0.117653] SCSI subsystem initialized
[ 0.118414] usbcore: registered new interface driver usbfs
[ 0.118491] usbcore: registered new interface driver hub
[ 0.118550] usbcore: registered new device driver usb
[ 0.119474] clocksource: Switched to clocksource orion_clocksource
[ 0.120592] NET: Registered protocol family 2
[ 0.121125] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.121160] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.121190] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.121243] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.121268] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.121418] NET: Registered protocol family 1
[ 0.123209] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.123282] Crashlog allocated RAM at address 0x3f00000
[ 0.136289] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.136314] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.139000] io scheduler noop registered
[ 0.139017] io scheduler deadline registered (default)
[ 0.140250] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.140843] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[ 0.141194] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[ 0.141761] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[ 0.141779] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.141791] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.141804] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.142090] PCI: bus0: Fast back to back transfers disabled
[ 0.142105] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.142625] PCI: bus1: Fast back to back transfers disabled
[ 0.142723] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe00fffff]
[ 0.142738] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
[ 0.142756] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[ 0.142770] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
[ 0.142791] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
[ 0.142811] pci 0000:01:00.0: BAR 0: assigned [io 0x10000-0x100ff]
[ 0.142825] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.142836] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 0.142849] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 0.173748] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 0.174788] console [ttyS0] disabled
[ 0.174860] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 0.709421] console [ttyS0] enabled
[ 0.714112] sata_mv f1080000.sata: slots 32 ports 2
[ 0.722250] scsi host0: sata_mv
[ 0.726177] scsi host1: sata_mv
[ 0.729580] ata1: SATA max UDMA/133 irq 32
[ 0.733696] ata2: SATA max UDMA/133 irq 32
[ 0.738425] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 0.744841] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 0.749494] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 0.757108] Scanning device for bad blocks
[ 0.794565] Bad eraseblock 348 at 0x000002b80000
[ 0.799835] Bad eraseblock 355 at 0x000002c60000
[ 0.835590] Bad eraseblock 681 at 0x000005520000
[ 0.842102] Bad eraseblock 701 at 0x0000057a0000
[ 0.854921] Bad eraseblock 787 at 0x000006260000
[ 0.872908] Bad eraseblock 927 at 0x0000073e0000
[ 0.883713] Bad eraseblock 992 at 0x000007c00000
[ 0.891347] 3 ofpart partitions found on MTD device orion_nand
[ 0.897204] Creating 3 MTD partitions on "orion_nand":
[ 0.902386] 0x000000000000-0x0000000c0000 : "uboot"
[ 0.908800] 0x0000000c0000-0x000000140000 : "uboot_env"
[ 0.915157] 0x000000140000-0x000008000000 : "ubi"
[ 0.921795] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.928357] ehci-pci: EHCI PCI platform driver
[ 0.932915] ehci-orion: EHCI orion driver
[ 0.937105] orion-ehci f1050000.ehci: EHCI Host Controller
[ 0.942668] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 0.950508] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 0.969493] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 0.976204] hub 1-0:1.0: USB hub found
[ 0.980177] hub 1-0:1.0: 1 port detected
[ 0.984582] usbcore: registered new interface driver usb-storage
[ 0.991071] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 0.998033] i2c /dev entries driver
[ 1.002839] orion_wdt: Initial timeout 21 sec
[ 1.012565] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 1.020834] NET: Registered protocol family 10
[ 1.026689] NET: Registered protocol family 17
[ 1.031244] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 1.043936] 8021q: 802.1Q VLAN Support v1.8
[ 1.050490] UBI: auto-attach mtd2
[ 1.053656] ubi0: attaching mtd2
[ 1.273060] ubi0: scanning is finished
[ 1.288399] ubi0: attached mtd2 (name "ubi", size 126 MiB)
[ 1.293943] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[ 1.300862] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[ 1.307594] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[ 1.314426] ubi0: good PEBs: 1007, bad PEBs: 7, corrupted PEBs: 0
[ 1.320558] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[ 1.327807] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1964526799
[ 1.336994] ubi0: available PEBs: 0, total reserved PEBs: 1007, PEBs reserved for bad PEB handling: 13
[ 1.346663] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 1.353492] ubi0: background thread "ubi_bgt0d" started, PID 900
[ 1.360273] block ubiblock0_1: created from ubi0:1(rootfs)
[ 1.365783] ubiblock: device ubiblock0_1 (rootfs) set to be root filesystem
[ 1.373046] rtc-mv f1010300.rtc: setting system clock to 2017-01-25 23:23:10 UTC (1485386590)
[ 1.409507] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 1.429600] ata1.00: ATA-8: HGST HTS545050A7E680, GG2OAH10, max UDMA/100
[ 1.436330] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 1.479612] ata1.00: configured for UDMA/100
[ 1.484328] scsi 0:0:0:0: Direct-Access ATA HGST HTS545050A7 AH10 PQ: 0 ANSI: 5
[ 1.493545] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 1.501101] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 1.506900] sd 0:0:0:0: [sda] Write Protect is off
[ 1.511895] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.523169] hub 1-1:1.0: USB hub found
[ 1.527273] hub 1-1:1.0: 4 ports detected
[ 1.588275] sda: sda1
[ 1.591729] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.809489] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[ 1.839498] ata2: SATA link down (SStatus 0 SControl F300)
[ 1.849811] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[ 1.857503] Freeing unused kernel memory: 172K (c055f000 - c058a000)
[ 2.083764] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 2.119044] scsi host2: usb-storage 1-1.2:1.0
[ 2.359452] init: Console is alive
[ 2.363062] init: - watchdog -
[ 2.584871] init: - preinit -
[ 2.961971] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[ 3.034298] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
Cannot parse config file: No such file or directory
[ 3.133028] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[ 3.164767] random: jshn: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[ 3.192100] random: jshn: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[ 3.228092] random: procd: uninitialized urandom read (4 bytes read, 15 bits of entropy available)
[ 3.237506] scsi 2:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 4
[ 3.247195] sd 2:0:0:0: [sdb] 7866368 512-byte logical blocks: (4.03 GB/3.75 GiB)
[ 3.261997] sd 2:0:0:0: [sdb] Write Protect is off
[ 3.274268] sd 2:0:0:0: [sdb] No Caching mode page found
[ 3.279680] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 3.300093] sdb: sdb1
Press the [f] ke[ 3.306478] sd 2:0:0:0: [sdb] Attached SCSI removable disk
y and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 6.443426] mount_root: loading kmods from internal overlay
[ 7.339380] UBIFS (ubi0:2): default file-system created
[ 7.371378] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 1008
[ 7.433209] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[ 7.441108] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 7.451078] UBIFS (ubi0:2): FS size: 122185728 bytes (116 MiB, 947 LEBs), journal size 6064128 bytes (5 MiB, 47 LEBs)
[ 7.461747] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB)
[ 7.468393] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID 15A5D2FB-CD82-422B-BE80-B8FA9C6CA2A4, small LPT model
[ 7.480144] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 7.487257] block: unable to load configuration (fstab: Entry not found)
[ 7.494073] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
[ 7.500647] block: unable to load configuration (fstab: Entry not found)
[ 7.507437] block: attempting to load /etc/config/fstab
[ 7.512819] block: unable to load configuration (fstab: Entry not found)
[ 7.519606] block: no usable configuration
[ 7.528907] UBIFS (ubi0:2): un-mount UBI device 0
[ 7.533677] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" stops
[ 7.569863] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 1010
[ 7.631870] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[ 7.639775] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 7.649746] UBIFS (ubi0:2): FS size: 122185728 bytes (116 MiB, 947 LEBs), journal size 6064128 bytes (5 MiB, 47 LEBs)
[ 7.660414] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB)
[ 7.667061] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID 15A5D2FB-CD82-422B-BE80-B8FA9C6CA2A4, small LPT model
[ 8.347768] block: attempting to load /tmp/ubifs_cfg/upper/etc/config/fstab
[ 8.354908] block: unable to load configuration (fstab: Entry not found)
[ 8.361721] block: attempting to load /tmp/ubifs_cfg/etc/config/fstab
[ 8.368282] block: unable to load configuration (fstab: Entry not found)
[ 8.375096] block: attempting to load /etc/config/fstab
[ 8.380434] block: unable to load configuration (fstab: Entry not found)
[ 8.387201] block: no usable configuration
[ 8.392787] mount_root: overlay filesystem has not been fully initialized yet
[ 8.400564] mount_root: switching to ubifs overlay
[ 8.411237] urandom-seed: Seed file not found (/etc/urandom.seed)
[ 8.470294] procd: - early -
[ 8.473248] procd: - watchdog -
[ 9.288826] procd: - ubus -
[ 9.325800] random: ubusd: uninitialized urandom read (4 bytes read, 73 bits of entropy available)
[ 9.341403] random: ubusd: uninitialized urandom read (4 bytes read, 73 bits of entropy available)
[ 9.350730] random: ubusd: uninitialized urandom read (4 bytes read, 73 bits of entropy available)
[ 9.359792] random: ubusd: uninitialized urandom read (4 bytes read, 73 bits of entropy available)
[ 9.371630] procd: - init -
Please press Enter to activate this console.
[ 9.534190] zram: Added device: zram0
[ 9.549312] ip6_tables: (C) 2000-2006 Netfilter Core Team
[ 9.573535] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 9.583666] nf_conntrack version 0.5.0 (3967 buckets, 15868 max)
[ 9.601651] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 9.607290] pci 0000:00:01.0: enabling device (0140 -> 0143)
[ 9.613040] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[ 9.619928] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd0dce000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[ 9.629567] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
[ 9.684663] xt_time: kernel timezone is -0000
[ 9.696407] PPP generic driver version 2.4.2
[ 9.702442] NET: Registered protocol family 24
[ 12.479820] zram0: detected capacity change from 0 to 128974848
[ 12.552503] Adding 125948k swap on /dev/zram0. Priority:-1 extents:1 across:125948k SS
[ 14.484230] r8169 0000:01:00.0 eth0: link down
[ 14.490736] device eth0 entered promiscuous mode
[ 14.511422] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[ 15.519536] random: nonblocking pool is initialized
BusyBox v1.25.1 () built-in shell (ash)
_________
/ /\ _ ___ ___ ___
/ LE / \ | | | __| \| __|
/ DE / \ | |__| _|| |) | _|
/________/ LE \ |____|___|___/|___| lede-project.org
\ \ DE /
\ LE \ / -----------------------------------------------------------
\ DE \ / Reboot (SNAPSHOT, r3114-1a83d4d)
\________\/ -----------------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:36PM |
Registered: 9 years ago Posts: 38 |
When I want to start LEDE from USB using uImage (for bodhi uboot )
Starting kernel ... [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.4.42 (kofec@E5420Mint) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3060+2-533f73e) ) #0 Mon Jan 23 12:12:08 2017 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [ 0.000000] Machine model: ZyXEL NSA310b [ 0.000000] Memory policy: Data cache writeback [ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024 [ 0.000000] Kernel command line: console=ttyS0,115200 [ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes) [ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes) [ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes) [ 0.000000] Memory: 253776K/262144K available (3978K kernel code, 138K rwdata, 1488K rodata, 172K init, 196K bss, 8368K reserved, 0K cma-reserved) [ 0.000000] Virtual kernel memory layout: [ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB) [ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB) [ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB) [ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB) [ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB) [ 0.000000] .text : 0xc0008000 - 0xc055edb4 (5468 kB) [ 0.000000] .init : 0xc055f000 - 0xc058a000 ( 172 kB) [ 0.000000] .data : 0xc058a000 - 0xc05ac880 ( 139 kB) [ 0.000000] .bss : 0xc05ac880 - 0xc05ddc0c ( 197 kB) [ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1 [ 0.000000] NR_IRQS:16 nr_irqs:16 16 [ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns [ 0.000008] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns [ 0.000089] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256) [ 0.090081] pid_max: default: 32768 minimum: 301 [ 0.090192] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.090210] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [ 0.090747] CPU: Testing write buffer coherency: ok [ 0.091113] Setting up static identity map for 0x81e0 - 0x821c [ 0.091432] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3 [ 0.096515] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns [ 0.096673] pinctrl core: initialized pinctrl subsystem [ 0.097815] NET: Registered protocol family 16 [ 0.098162] DMA: preallocated 256 KiB pool for atomic coherent allocations [ 0.099059] cpuidle: using governor ladder [ 0.099412] Feroceon L2: Enabling L2 [ 0.099457] Feroceon L2: Cache support initialised. [ 0.117659] SCSI subsystem initialized [ 0.118421] usbcore: registered new interface driver usbfs [ 0.118497] usbcore: registered new interface driver hub [ 0.118562] usbcore: registered new device driver usb [ 0.119483] clocksource: Switched to clocksource orion_clocksource [ 0.120599] NET: Registered protocol family 2 [ 0.121135] TCP established hash table entries: 2048 (order: 1, 8192 bytes) [ 0.121169] TCP bind hash table entries: 2048 (order: 1, 8192 bytes) [ 0.121199] TCP: Hash tables configured (established 2048 bind 2048) [ 0.121253] UDP hash table entries: 256 (order: 0, 4096 bytes) [ 0.121278] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes) [ 0.121427] NET: Registered protocol family 1 [ 0.123217] futex hash table entries: 256 (order: -1, 3072 bytes) [ 0.123290] Crashlog allocated RAM at address 0x3f00000 [ 0.136433] squashfs: version 4.0 (2009/01/31) Phillip Lougher [ 0.136458] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc. [ 0.139139] io scheduler noop registered [ 0.139156] io scheduler deadline registered (default) [ 0.140392] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver [ 0.140976] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated [ 0.141327] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated [ 0.141902] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00 [ 0.141920] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff] [ 0.141932] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff] [ 0.141945] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.142222] PCI: bus0: Fast back to back transfers disabled [ 0.142237] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring [ 0.142756] PCI: bus1: Fast back to back transfers disabled [ 0.142854] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe00fffff] [ 0.142870] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff] [ 0.142888] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref] [ 0.142903] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref] [ 0.142924] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref] [ 0.142944] pci 0000:01:00.0: BAR 0: assigned [io 0x10000-0x100ff] [ 0.142958] pci 0000:00:01.0: PCI bridge to [bus 01] [ 0.142969] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff] [ 0.142982] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff] [ 0.173832] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled [ 0.174866] console [ttyS0] disabled [ 0.174938] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A [ 0.709535] console [ttyS0] enabled [ 0.714208] sata_mv f1080000.sata: slots 32 ports 2 [ 0.722349] scsi host0: sata_mv [ 0.726271] scsi host1: sata_mv [ 0.729671] ata1: SATA max UDMA/133 irq 32 [ 0.733783] ata2: SATA max UDMA/133 irq 32 [ 0.738506] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1 [ 0.744918] nand: Samsung NAND 128MiB 3,3V 8-bit [ 0.749573] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 0.757186] Scanning device for bad blocks [ 0.794611] Bad eraseblock 348 at 0x000002b80000 [ 0.799877] Bad eraseblock 355 at 0x000002c60000 [ 0.835604] Bad eraseblock 681 at 0x000005520000 [ 0.842110] Bad eraseblock 701 at 0x0000057a0000 [ 0.854921] Bad eraseblock 787 at 0x000006260000 [ 0.872895] Bad eraseblock 927 at 0x0000073e0000 [ 0.883700] Bad eraseblock 992 at 0x000007c00000 [ 0.891330] 4 ofpart partitions found on MTD device orion_nand [ 0.897186] Creating 4 MTD partitions on "orion_nand": [ 0.902368] 0x000000000000-0x000000100000 : "uboot" [ 0.908787] 0x000000100000-0x000000180000 : "uboot_env" [ 0.915144] 0x000000180000-0x000000280000 : "second stage u-boot" [ 0.922371] 0x000000280000-0x000007e00000 : "ubi" [ 0.928952] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [ 0.935550] ehci-pci: EHCI PCI platform driver [ 0.940097] ehci-orion: EHCI orion driver [ 0.944292] orion-ehci f1050000.ehci: EHCI Host Controller [ 0.949852] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1 [ 0.957675] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000 [ 0.979502] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00 [ 0.986220] hub 1-0:1.0: USB hub found [ 0.990184] hub 1-0:1.0: 1 port detected [ 0.994580] usbcore: registered new interface driver usb-storage [ 1.001074] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0 [ 1.008034] i2c /dev entries driver [ 1.012841] orion_wdt: Initial timeout 21 sec [ 1.022562] marvell-cesa f1030000.crypto: CESA device successfully registered [ 1.030842] NET: Registered protocol family 10 [ 1.036702] NET: Registered protocol family 17 [ 1.041261] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this. [ 1.053946] 8021q: 802.1Q VLAN Support v1.8 [ 1.060437] UBI error: no valid UBI magic found inside mtd3 [ 1.066095] rtc-mv f1010300.rtc: setting system clock to 2017-01-25 20:47:13 UTC (1485377233) [ 1.309498] usb 1-1: new high-speed USB device number 2 using orion-ehci [ 1.409507] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300) [ 1.429622] ata1.00: ATA-8: HGST HTS545050A7E680, GG2OAH10, max UDMA/100 [ 1.436376] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32) [ 1.461595] hub 1-1:1.0: USB hub found [ 1.465691] hub 1-1:1.0: 4 ports detected [ 1.479611] ata1.00: configured for UDMA/100 [ 1.484302] scsi 0:0:0:0: Direct-Access ATA HGST HTS545050A7 AH10 PQ: 0 ANSI: 5 [ 1.493468] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ 1.501019] sd 0:0:0:0: [sda] 4096-byte physical blocks [ 1.506815] sd 0:0:0:0: [sda] Write Protect is off [ 1.511781] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [ 1.749499] usb 1-1.3: new high-speed USB device number 3 using orion-ehci [ 1.839502] ata2: SATA link down (SStatus 0 SControl F300) [ 1.891783] usb-storage 1-1.3:1.0: USB Mass Storage device detected [ 1.898973] sda: sda1 [ 1.902490] sd 0:0:0:0: [sda] Attached SCSI disk [ 1.907323] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6 [ 1.914861] Please append a correct "root=" boot option; here are the available partitions: [ 1.923274] 1f00 1024 mtdblock0 (driver?) [ 1.928355] 1f01 512 mtdblock1 (driver?) [ 1.933458] 1f02 1024 mtdblock2 (driver?) [ 1.938539] 1f03 126464 mtdblock3 (driver?) [ 1.943643] 0800 488386584 sda driver: sd [ 1.948289] 0801 488385536 sda1 92cd7dbc-c022-49eb-8b19-13294cb9f612 [ 1.955387] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) [ 1.964498] Rebooting in 1 seconds..▒ U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700) ZyXEL NSA310 1-Bay Power Media Server SoC: Kirkwood 88F6281_A1 DRAM: 256 MiB
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:37PM |
Admin Registered: 14 years ago Posts: 19,977 |
Quote
I start your uboot - using kwboot - the write to flash. Thanks a lot for help. Maybe you can also fix 2nd boot stage in your uboot.
I am not sure what you meant by 2nd boot stage?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:43PM |
Admin Registered: 14 years ago Posts: 19,977 |
kofec,
> [ 1.955387] Kernel panic - not syncing: VFS:
> Unable to mount root fs on unknown-block(0,0)
You've missed the bootargs env, so the kernel does not know where the rootfs is.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> [ 1.955387] Kernel panic - not syncing: VFS:
> Unable to mount root fs on unknown-block(0,0)
You've missed the bootargs env, so the kernel does not know where the rootfs is.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 04:58PM |
Registered: 9 years ago Posts: 38 |
As it is writen :
https://github.com/lede-project/source/pull/732
https://github.com/lede-project/source/pull/732
this commit allows to make both a standalone and a second-stage u-boot for nsa310b, but only first-stage u-boot is added in the makefile and available in the build system. The reason is that while both work fine if installed to flash or loaded with kwboot, I could not get stock u-boot nor bodhi's u-boot to chainload any second stage u-boot (I also tried with dockstar's uboot that works fine on this device if loaded with kwboot).
|
Re: uboot NSA310 - probably erase uboot January 25, 2017 06:04PM |
Admin Registered: 14 years ago Posts: 19,977 |
kofec Wrote:
-------------------------------------------------------
> As it is writen :
>
> https://github.com/lede-project/source/pull/732
>
>
Ah! that LEDE 2nd stage. IMHO, it is a poor approach. So I will not support it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> As it is writen :
>
> https://github.com/lede-project/source/pull/732
>
>
> this commit allows to make both a standalone and > a second-stage u-boot for nsa310b, but only > first-stage u-boot is added in the makefile and > available in the build system. > > The reason is that while both work fine if > installed to flash > or loaded with kwboot, I could not get stock > u-boot nor > bodhi's u-boot to chainload any second stage > u-boot > (I also tried with dockstar's uboot that works > fine > on this device if loaded with kwboot). >
Ah! that LEDE 2nd stage. IMHO, it is a poor approach. So I will not support it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 06:13AM |
Registered: 9 years ago Posts: 38 |
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 06:32AM |
Admin Registered: 14 years ago Posts: 19,977 |
kofec,
It will not work with modern u-boot, i.e. it only works with much older u-boot. And LEDE doesn't need to do 2nd stage boot anyway. That's why I said it is not a good approach.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
It will not work with modern u-boot, i.e. it only works with much older u-boot. And LEDE doesn't need to do 2nd stage boot anyway. That's why I said it is not a good approach.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 07:27AM |
Registered: 9 years ago Posts: 38 |
OK understand. What is your proposal. All I need is to have LEDE in nand and have sysupgrade working (not always connect via serial cable).
After current sysupgrade I have below issue.
After current sysupgrade I have below issue.
NSA310> usb reset
resetting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
NSA310> fatload usb 0 0x2000000 lede-kirkwood-nsa310b-squashfs-factory.bin
reading lede-kirkwood-nsa310b-squashfs-factory.bin
4456448 bytes read in 146 ms (29.1 MiB/s)
NSA310> setenv mtdparts mtdparts=orion_nand:0x100000(uboot),0x80000(uboot_env),0x100000(second_stage_uboot),0x7b80000(ubi)
NSA310> mtdparts
device nand0 <orion_nand>, # parts = 4
#: name size offset mask_flags
0: uboot 0x00100000 0x00000000 0
1: uboot_env 0x00080000 0x00100000 0
2: second_stage_uboot 0x00100000 0x00180000 0
3: ubi 0x07b80000 0x00280000 0
active partition: nand0,2 - (second_stage_uboot) 0x00100000 @ 0x00180000
defaults:
mtdids : none
mtdparts: none
NSA310> nand erase.part ubi
NAND erase.part: device 0 offset 0x280000, size 0x7b80000
Skipping bad block at 0x02b80000
Skipping bad block at 0x02c60000
Skipping bad block at 0x05520000
Skipping bad block at 0x057a0000
Skipping bad block at 0x06260000
Skipping bad block at 0x073e0000
Skipping bad block at 0x07c00000
Erasing at 0x7de0000 -- 100% complete.
OK
NSA310> nand write 0x2000000 ubi 0x600000
NAND write: device 0 offset 0x280000, size 0x600000
6291456 bytes written: OK
NSA310> setenv bootcmd "run setenv bootargs; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000"
NSA310> save
save saveenv
NSA310> saveenv
Saving Environment to NAND...
Erasing NAND...
Erasing at 0xc0000 -- 100% complete.
Writing to NAND... OK
NSA310> reset
resetting ...
�
U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: ide_preinit failed
Hit any key to stop autoboot: 0
## Error: "setenv" not defined
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: volume 2 ("rootfs_data") re-sized from 9 to 932 LEBs
ubi0: attached mtd1 (name "mtd=3", size 123 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 981, bad PEBs: 7, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1964526799
ubi0: available PEBs: 0, total reserved PEBs: 981, PEBs reserved for bad PEB handling: 13
Read 0 bytes from volume kernel to 800000
No size specified -> Using max size (2064384)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: ARM LEDE Linux-4.4.42
Created: 2017-01-24 19:33:45 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1951826 Bytes = 1.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
�
U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: ide_preinit failed
Hit any key to stop autoboot: 0
NSA310>
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 07:28AM |
Registered: 9 years ago Posts: 38 |
The diffrence is:
when kernel load fine:
And Now fail:
Probably some env should be corrected
when correctly start from UBI (nand) saw below partitions:
I flash clean env but it didn't help
nand erase 0xc0000 0x20000
fatload usb 0 0x1000000 uboot.2016.05-tld-1.environment.img
nand write 0x1000000 0xc0000 se0x20000
Edited 4 time(s). Last edit at 01/26/2017 09:16AM by kofec.
when kernel load fine:
ubi0: volume 2 ("rootfs_data") re-sized from 9 to 932 LEBs
ubi0: attached mtd1 (name "mtd=3", size 123 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 981, bad PEBs: 7, corrupted PEBs: 0
And Now fail:
ubi0: volume 2 ("rootfs_data") re-sized from 9 to 958 LEBs
ubi0: attached mtd1 (name "mtd=2", size 126 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1007, bad PEBs: 7, corrupted PEBs: 0
Probably some env should be corrected
when correctly start from UBI (nand) saw below partitions:
[ 0.891347] 3 ofpart partitions found on MTD device orion_nand [ 0.897204] Creating 3 MTD partitions on "orion_nand": [ 0.902386] 0x000000000000-0x0000000c0000 : "uboot" [ 0.908800] 0x0000000c0000-0x000000140000 : "uboot_env" [ 0.915157] 0x000000140000-0x000008000000 : "ubi"
I flash clean env but it didn't help
nand erase 0xc0000 0x20000
fatload usb 0 0x1000000 uboot.2016.05-tld-1.environment.img
nand write 0x1000000 0xc0000 se0x20000
U-Boot 2016.09.01 (Jan 24 2017 - 19:33:45 +0000)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
IDE: Bus 0: OK Bus 1: not available
Device 0: Model: HGST HTS545050A7E680 Firm: GG2OAH10 Ser#: TE85134N36SSKN
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Hit any key to stop autoboot: 0
Unknown command 'for' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'done' - try 'help'
Unknown command 'for' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'done' - try 'help'
Unknown command 'done' - try 'help'
Unknown command 'if' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'fi' - try 'help'
running scan_disk ...
Unknown command 'scan_done=0' - try 'help'
Unknown command 'for' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'then' - try 'help'
## Error: "scan_$dev" not defined
Unknown command 'for' - try 'help'
Unknown command 'do' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'if' - try 'help'
Unknown command 'then' - try 'help'
Found bootable drive on $dev $disknum
Unknown command 'fi' - try 'help'
Unknown command 'fi' - try 'help'
Unknown command 'done' - try 'help'
Unknown command 'fi' - try 'help'
Unknown command 'done' - try 'help'
loading uImage ...
Unknown command 'load' - try 'help'
Unknown command 'if' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'else' - try 'help'
Unknown command 'fi' - try 'help'
Unknown command 'else' - try 'help'
Unknown command 'then' - try 'help'
Unknown command 'else' - try 'help'
Unknown command 'fi' - try 'help'
Unknown command 'fi' - try 'help'
Edited 4 time(s). Last edit at 01/26/2017 09:16AM by kofec.
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 10:44AM |
Registered: 9 years ago Posts: 38 |
After these all experiminets I'm not able to start LEDE from my old USB and power buttom not working - start via wake on lan. So this is some hadware issue? Or some environment issue ?
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
NSA310> printenv
arcNumber=4022
baudrate=115200
bootcmd=run bootcmd_uenv; run bootcmd_usb; usb stop; run bootcmd_sata; reset
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=10
console=ttyS0,115200
device=0:1
dtb_file=/boot/dts/kirkwood-nsa310a.dtb
ethact=egiga0
ethaddr=b6:d0:5e:0f:a1:17
led_error=orange blinking
led_exit=green off
led_init=green blinking
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
partition=nand0,2
rootdelay=10
rootfstype=ext2
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=ext2load ide $device 0x800000 /boot/uImage
sata_load_uinitrd=ext2load ide $device 0x1100000 /boot/uInitrd
sata_root=/dev/sda1
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
stderr=serial
stdin=serial
stdout=serial
uenv_import=echo importing envs ...; env import -t 0x810000
uenv_load=usb start; setenv uenv_loaded 0; for devtype in usb; 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 $devtype part $disknum; then run uenv_read; 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=ext2load usb $device 0x800000 /boot/uImage
usb_load_uinitrd=ext2load usb $device 0x1100000 /boot/uInitrd
usb_root=/dev/sda1
Environment size: 2114/131068 bytes
NSA310> sete
setenv setexpr
NSA310> setenv rootfstype=ext3
## Error: illegal character '='in variable name "rootfstype=ext3"
NSA310> setenv rootfstype ext3
NSA310>
NSA310>
NSA310> save
save saveenv
NSA310> saveenv
Saving Environment to NAND...
Erasing NAND...
Erasing at 0xc0000 -- 100% complete.
Writing to NAND... OK
NSA310>
NSA310>
NSA310>
NSA310>
NSA310> reset
resetting ...
�
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:59:20 -0700)
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 6809600 76da3475-01 83
2 6811648 1052672 76da3475-02 82
loading envs from usb 0 ...
2721 bytes read in 315 ms (7.8 KiB/s)
importing envs ...
## Warning: Input data exceeds 1048576 bytes - truncated
## Info: input data size = 1048578 = 0x100002
1765684 bytes read in 423 ms (4 MiB/s)
** File not found /boot/uInitrd **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: ARM LEDE Linux-4.4.15
Created: 2016-08-16 21:32:05 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1765620 Bytes = 1.7 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 01:05PM |
Registered: 10 years ago Posts: 298 |
I apologize with kofec, there is a sequence of bad luck here.
It seems nbd merged an older patch for the u-boot, it has wrong mtdparts and usb does not work. Will send again a patch for that later.
For now, install bodhi's uboot for nsa310 and its envs, then change or create envs to allow booting LEDE (it will work also in the future, no need to install LEDE's uboot when I fix it) with these commands
Then power off the nsa310 by disconnecting power connector. I needed to do that on mine too or I got errors like yours above. (uboot wasn't fully cleared from RAM)
LEDE needs NO "bootargs", no "root=" no nothing. It has these commands already in the firmware.
There is no second-stage uboot. You read that message wrong, I said that I could not make it, and that it is not needed.
Then you have bad blocks in the onboard flash,
Use LEDE initramfs (ramdisk) firmware image to install.
Then you will see LEDE start, this is all in RAM, when it is started you need to do a sysupgrade with the .tar file, and the LEDE firmware should format and write correctly to flash.
Then you can reboot and it should boot from flash.
Edited 1 time(s). Last edit at 01/26/2017 01:08PM by bobafetthotmail.
It seems nbd merged an older patch for the u-boot, it has wrong mtdparts and usb does not work. Will send again a patch for that later.
For now, install bodhi's uboot for nsa310 and its envs, then change or create envs to allow booting LEDE (it will work also in the future, no need to install LEDE's uboot when I fix it) with these commands
setenv bootargs_lede 'setenv bootargs' setenv bootcmd 'run scan_disk; run bootcmd_linux; run bootcmd_lede' setenv bootcmd_lede 'run bootargs_lede; ubi part ubi; ubi read 0x800000 kernel; bootm 0x800000' setenv mtdparts 'mtdparts=orion_nand:0x00c0000(uboot),0x80000(uboot_env),0x7ec0000(ubi)' saveenv
Then power off the nsa310 by disconnecting power connector. I needed to do that on mine too or I got errors like yours above. (uboot wasn't fully cleared from RAM)
[ 1.907323] VFS: Cannot open root device "(null)" or unknown-block(0,0): error -6
LEDE needs NO "bootargs", no "root=" no nothing. It has these commands already in the firmware.
There is no second-stage uboot. You read that message wrong, I said that I could not make it, and that it is not needed.
Then you have bad blocks in the onboard flash,
NAND erase.part: device 0 offset 0x280000, size 0x7b80000 Skipping bad block at 0x02b80000 Skipping bad block at 0x02c60000 Skipping bad block at 0x05520000 Skipping bad block at 0x057a0000 Skipping bad block at 0x06260000 Skipping bad block at 0x073e0000 Skipping bad block at 0x07c00000 Erasing at 0x7de0000 -- 100% complete.Flashing from uboot seems to fail because uboot isn't writing the firmware in a way that LEDE likes if there are bad blocks.
Use LEDE initramfs (ramdisk) firmware image to install.
usb reset fatload usb 0 0x800000 lede-kirkwood-nsa310b-initramfs-uImage bootm 0x800000
Then you will see LEDE start, this is all in RAM, when it is started you need to do a sysupgrade with the .tar file, and the LEDE firmware should format and write correctly to flash.
Then you can reboot and it should boot from flash.
Edited 1 time(s). Last edit at 01/26/2017 01:08PM by bobafetthotmail.
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 01:09PM |
Registered: 10 years ago Posts: 298 |
|
Re: uboot NSA310 - probably erase uboot January 26, 2017 03:04PM |
Admin Registered: 14 years ago Posts: 19,977 |
bobafetthotmail,
> @bodhi: thanks for taking the time to help kofec
> on this even if it was not an issue of your u-boot
> :)
No problem :) But I would suggest in the mean time this should be moved to Rescue subforum. And people can continue posting there with problem. I thought that kofec just want to build new u-boot :)
I'll ask Jeff if he can create another subforum for LEDE.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> @bodhi: thanks for taking the time to help kofec
> on this even if it was not an issue of your u-boot
> :)
No problem :) But I would suggest in the mean time this should be moved to Rescue subforum. And people can continue posting there with problem. I thought that kofec just want to build new u-boot :)
I'll ask Jeff if he can create another subforum for LEDE.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 27, 2017 12:00PM |
Registered: 9 years ago Posts: 38 |
Thank you @bobafetthotmail and @bodhi
Now almost everthing is fine. Two cosmetic issue:
2) it didn't read eth addr from uboot env but when i execute fw_printenv is see variable ethaddr
Now almost everthing is fine. Two cosmetic issue:
1) root@lede:/tmp# sysupgrade -d 5 lede-kirkwood-nsa310b-squashfs-sysupgrade.tar Image metadata not found - shows something like this Saving config files... Connection to 192.168.1.162 closed by remote host. Connection to 192.168.1.162 closed.
2) it didn't read eth addr from uboot env but when i execute fw_printenv is see variable ethaddr
br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 00:00:00:00:00:30 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.162/24 brd 192.168.1.255 scope global br-lan
valid_lft forever preferred_lft forever
inet6 fe80::200:ff:fe00:30/64 scope link
valid_lft forever preferred_lft forever
|
Re: uboot NSA310 - probably erase uboot January 28, 2017 05:15AM |
Registered: 10 years ago Posts: 298 |
> 2) it didn't read eth addr from uboot env but when i execute fw_printenv is see variable ethaddr
Ok, i'll have to fix it later using the function proposed by mkresin on github. For now you can set the right mac address with
How is Wake on Lan working with this firmware after you set mac address?
Does it still want 00:00:00:00:00:30 or it works with right mac address?
Ok, i'll have to fix it later using the function proposed by mkresin on github. For now you can set the right mac address with
uci set network.lan.macaddr='MAC-ADDRESS-HERE' uci commit service network restartThis is what mkresin's function also does. This configuration will be saved when you sysupgrade, but will not be needed after I sent the fix to LEDE.
How is Wake on Lan working with this firmware after you set mac address?
Does it still want 00:00:00:00:00:30 or it works with right mac address?
|
Re: uboot NSA310 - probably erase uboot January 28, 2017 09:36AM |
Registered: 10 years ago Posts: 298 |
bodhi said:
> I'll ask Jeff if he can create another subforum for LEDE.
Thanks, but it might not be necessary.
I have added support for the two devices I own (nsa310 and nsa325), and I'm going to try adding all other kirkwoods you support to LEDE, but I'll need a place for someone with the device to test it.
But apart from that it's not going to see much use, as I'm sending patches to LEDE, not making my own downstream project like you are doing with Debian.
So people should use LEDE download servers to get the firmwares and forums for any question.
I actually told kofec to use LEDE forums for his issues, not to come bother people here. :)
If you are ok with letting me make a "let's add support to LEDE/OpenWRT for kirkwood boxes" thread in the Debian section (even if it is not Debian, just for visibility), it's probably enough for me, and it will go dead and can be moved somewhere else after I'm done.
> I'll ask Jeff if he can create another subforum for LEDE.
Thanks, but it might not be necessary.
I have added support for the two devices I own (nsa310 and nsa325), and I'm going to try adding all other kirkwoods you support to LEDE, but I'll need a place for someone with the device to test it.
But apart from that it's not going to see much use, as I'm sending patches to LEDE, not making my own downstream project like you are doing with Debian.
So people should use LEDE download servers to get the firmwares and forums for any question.
I actually told kofec to use LEDE forums for his issues, not to come bother people here. :)
If you are ok with letting me make a "let's add support to LEDE/OpenWRT for kirkwood boxes" thread in the Debian section (even if it is not Debian, just for visibility), it's probably enough for me, and it will go dead and can be moved somewhere else after I'm done.
|
Re: uboot NSA310 - probably erase uboot January 28, 2017 04:12PM |
Admin Registered: 14 years ago Posts: 19,977 |
bobafetthotmai,
> If you are ok with letting me make a "let's add su
> pport to LEDE/OpenWRT for kirkwood boxes" thread i
> n the Debian section (even if it is not Debian, ju
> st for visibility), it's probably enough for me, a
> nd it will go dead and can be moved somewhere else
> after I'm done.
Please go ahead and make a thread for it in Debian section.
But have a description in the first post that describes the use cases for LEDE/OpenWrt. Things such as why would ones want to use LEDE. For example, embedded systems only, memory restriction, don't care much for latest security patches...etc. Things that emdebian used to exists for. Note that we have a sticky emdebian thread before: http://forum.doozan.com/read.php?2,72. So what you do is great, IMO. As long as we don't advocate people using it as a NAS (Debian is a better fit for that). I know you can make it a NAS with further modification, but that would be a distraction in a Debian forum.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> If you are ok with letting me make a "let's add su
> pport to LEDE/OpenWRT for kirkwood boxes" thread i
> n the Debian section (even if it is not Debian, ju
> st for visibility), it's probably enough for me, a
> nd it will go dead and can be moved somewhere else
> after I'm done.
Please go ahead and make a thread for it in Debian section.
But have a description in the first post that describes the use cases for LEDE/OpenWrt. Things such as why would ones want to use LEDE. For example, embedded systems only, memory restriction, don't care much for latest security patches...etc. Things that emdebian used to exists for. Note that we have a sticky emdebian thread before: http://forum.doozan.com/read.php?2,72. So what you do is great, IMO. As long as we don't advocate people using it as a NAS (Debian is a better fit for that). I know you can make it a NAS with further modification, but that would be a distraction in a Debian forum.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: uboot NSA310 - probably erase uboot January 29, 2017 03:49PM |
Registered: 9 years ago Posts: 38 |
bobafetthotmai,
It is not working but it is not critical. With the original Zyxel firmware it works this way that I'm able to wake on lan via eth addr provided with device till there is no power outage. But when there is no power on NSA310 I have to use 00:00:00:00:00:30 also.
It is not working but it is not critical. With the original Zyxel firmware it works this way that I'm able to wake on lan via eth addr provided with device till there is no power outage. But when there is no power on NSA310 I have to use 00:00:00:00:00:30 also.
Quote
bobafetthotmai
How is Wake on Lan working with this firmware after you set mac address?
Does it still want 00:00:00:00:00:30 or it works with right mac address?
|
Re: uboot NSA310 - probably erase uboot February 13, 2017 01:01PM |
Registered: 9 years ago Posts: 38 |
It was fine untill I want to upgrade to latest build:
(Linux version 4.4.47 (buildbot@builds) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3377-368cc8e) ) #0 Sun Feb 12 00:41:43 2017)
second attempt:
after that I flash manually factory build - there is issue with kernel modules:
(Linux version 4.4.47 (buildbot@builds) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3377-368cc8e) ) #0 Sun Feb 12 00:41:43 2017)
Issue with upgrade: root@lede:/tmp# sysupgrade -d 5 lede-kirkwood-nsa310b-squashfs-sysupgrade.tar Image metadata not found Saving config files... Watchdog handover: fd=3 - watchdog - killall: telnetd: no process killed
second attempt:
Sending TERM to remaining processes ... ubusd logd rpcd netifd odhcpd uhttpd collectd dnsmasq ntpd Sending KILL to remaining processes ... Switching to ramdisk... [ 129.214167] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" stops [ 129.235759] UBIFS (ubi0:2): un-mount UBI device 0 removing ubiblock0_1 [ 130.553158] block ubiblock0_1: released Volume ID 0, size 16 LEBs (2064384 bytes, 2.0 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "kernel", alignment 1 Volume ID 1, size 120 LEBs (15482880 bytes, 14.8 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs", alignment 1 Set volume size to 110186496 Volume ID 2, size 854 LEBs (110186496 bytes, 105.1 MiB), LEB size 129024 bytes (126.0 KiB), dynamic, name "rootfs_data", alignment 1 [ 137.296483] UBIFS (ubi0:2): default file-system created [ 137.328389] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 3055 [ 137.390538] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data" [ 137.398446] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes [ 137.408422] UBIFS (ubi0:2): FS size: 108767232 bytes (103 MiB, 843 LEBs), journal size 5419008 bytes (5 MiB, 42 LEBs) [ 137.419091] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB) [ 137.425736] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID A053A9E2-A9DD-4EDD-81A8-E8CD2EC098F7, small LPT model [ 137.456879] UBIFS (ubi0:2): un-mount UBI device 0 [ 137.461628] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" stops sysupgrade successful umount: can't unmount /dev: Resource busy umount: can't unmount /tmp: Resource busy [ 137.495697] sd 0:0:0:0: [sda] Synchronizing SCSI cache [ 137.516540] reboot: Restarting system
after that I flash manually factory build - there is issue with kernel modules:
ZyXEL NSA310 1-Bay Power Media Server
SoC: Kirkwood 88F6281_A1
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
PHY reset timed out
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 0
## Error: "scan_disk" not defined
## Error: "bootcmd_linux" not defined
ubi0: attaching mtd1
ubi0: scanning is finished
ubi0: volume 2 ("rootfs_data") re-sized from 9 to 964 LEBs
ubi0: attached mtd1 (name "mtd=2", size 126 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
ubi0: VID header offset: 512 (aligned 512), data offset: 2048
ubi0: good PEBs: 1007, bad PEBs: 7, corrupted PEBs: 0
ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 833779665
ubi0: available PEBs: 0, total reserved PEBs: 1007, PEBs reserved for bad PEB handling: 13
Read 0 bytes from volume kernel to 800000
No size specified -> Using max size (2064384)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: ARM LEDE Linux-4.4.47
Created: 2017-02-12 14:57:37 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 1994906 Bytes = 1.9 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.4.47 (buildbot@builds) (gcc version 5.4.0 (LEDE GCC 5.4.0 r3377-368cc8e) ) #0 Sun Feb 12 00:41:43 2017
[ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000] Machine model: ZyXEL NSA310b
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
[ 0.000000] Kernel command line: console=ttyS0,115200
[ 0.000000] PID hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.000000] Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
[ 0.000000] Memory: 253636K/262144K available (4078K kernel code, 142K rwdata, 1516K rodata, 172K init, 201K bss, 8508K reserved, 0K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xd0800000 - 0xff800000 ( 752 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xd0000000 ( 256 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc057edb4 (5596 kB)
[ 0.000000] .init : 0xc057f000 - 0xc05aa000 ( 172 kB)
[ 0.000000] .data : 0xc05aa000 - 0xc05cda60 ( 143 kB)
[ 0.000000] .bss : 0xc05cda60 - 0xc06000d4 ( 202 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] NR_IRQS:16 nr_irqs:16 16
[ 0.000000] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[ 0.000010] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[ 0.000092] Calibrating delay loop... 1196.85 BogoMIPS (lpj=5984256)
[ 0.090084] pid_max: default: 32768 minimum: 301
[ 0.090199] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090219] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.090768] CPU: Testing write buffer coherency: ok
[ 0.091137] Setting up static identity map for 0x81e0 - 0x821c
[ 0.091428] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.096643] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.096800] pinctrl core: initialized pinctrl subsystem
[ 0.097927] NET: Registered protocol family 16
[ 0.098278] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.099142] cpuidle: using governor ladder
[ 0.099495] Feroceon L2: Enabling L2
[ 0.099540] Feroceon L2: Cache support initialised.
[ 0.117833] SCSI subsystem initialized
[ 0.118585] usbcore: registered new interface driver usbfs
[ 0.118662] usbcore: registered new interface driver hub
[ 0.118722] usbcore: registered new device driver usb
[ 0.119632] clocksource: Switched to clocksource orion_clocksource
[ 0.120734] NET: Registered protocol family 2
[ 0.121328] TCP established hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.121364] TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.121394] TCP: Hash tables configured (established 2048 bind 2048)
[ 0.121450] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.121472] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.121631] NET: Registered protocol family 1
[ 0.123441] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.123514] Crashlog allocated RAM at address 0x3f00000
[ 0.137227] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[ 0.137246] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[ 0.139981] io scheduler noop registered
[ 0.140000] io scheduler deadline registered (default)
[ 0.141198] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 0.141784] irq: Cannot allocate irq_descs @ IRQ33, assuming pre-allocated
[ 0.142137] irq: Cannot allocate irq_descs @ IRQ65, assuming pre-allocated
[ 0.142712] mvebu-pcie mbus:pcie-controller: PCI host bridge to bus 0000:00
[ 0.142731] pci_bus 0000:00: root bus resource [io 0x1000-0xfffff]
[ 0.142743] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 0.142754] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 0.143033] PCI: bus0: Fast back to back transfers disabled
[ 0.143048] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.143570] PCI: bus1: Fast back to back transfers disabled
[ 0.143668] pci 0000:00:01.0: BAR 8: assigned [mem 0xe0000000-0xe00fffff]
[ 0.143684] pci 0000:00:01.0: BAR 7: assigned [io 0x10000-0x10fff]
[ 0.143701] pci 0000:01:00.0: BAR 6: assigned [mem 0xe0000000-0xe000ffff pref]
[ 0.143716] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0010000-0xe0013fff 64bit pref]
[ 0.143737] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0014000-0xe0014fff 64bit pref]
[ 0.143756] pci 0000:01:00.0: BAR 0: assigned [io 0x10000-0x100ff]
[ 0.143770] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 0.143781] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 0.143794] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 0.174416] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[ 0.177249] console [ttyS0] disabled
[ 0.177323] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[ 0.711663] console [ttyS0] enabled
[ 0.716324] sata_mv f1080000.sata: slots 32 ports 2
[ 0.724496] scsi host0: sata_mv
[ 0.728432] scsi host1: sata_mv
[ 0.731838] ata1: SATA max UDMA/133 irq 32
[ 0.735955] ata2: SATA max UDMA/133 irq 32
[ 0.740707] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[ 0.747090] nand: Samsung NAND 128MiB 3,3V 8-bit
[ 0.751756] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 0.759367] Scanning device for bad blocks
[ 0.796789] Bad eraseblock 348 at 0x000002b80000
[ 0.802059] Bad eraseblock 355 at 0x000002c60000
[ 0.837783] Bad eraseblock 681 at 0x000005520000
[ 0.844291] Bad eraseblock 701 at 0x0000057a0000
[ 0.857103] Bad eraseblock 787 at 0x000006260000
[ 0.875074] Bad eraseblock 927 at 0x0000073e0000
[ 0.885879] Bad eraseblock 992 at 0x000007c00000
[ 0.893508] 3 ofpart partitions found on MTD device orion_nand
[ 0.899367] Creating 3 MTD partitions on "orion_nand":
[ 0.904549] 0x000000000000-0x0000000c0000 : "uboot"
[ 0.911024] 0x0000000c0000-0x000000140000 : "uboot_env"
[ 0.917373] 0x000000140000-0x000008000000 : "ubi"
[ 0.924048] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 0.930652] ehci-pci: EHCI PCI platform driver
[ 0.935191] ehci-platform: EHCI generic platform driver
[ 0.940593] ehci-orion: EHCI orion driver
[ 0.944789] orion-ehci f1050000.ehci: EHCI Host Controller
[ 0.950353] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 0.958173] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[ 0.979652] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 0.986380] hub 1-0:1.0: USB hub found
[ 0.990356] hub 1-0:1.0: 1 port detected
[ 0.994766] usbcore: registered new interface driver usb-storage
[ 1.001265] rtc-mv f1010300.rtc: rtc core: registered f1010300.rtc as rtc0
[ 1.008226] i2c /dev entries driver
[ 1.013033] orion_wdt: Initial timeout 21 sec
[ 1.022755] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 1.030971] NET: Registered protocol family 10
[ 1.036841] NET: Registered protocol family 17
[ 1.041402] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[ 1.054087] 8021q: 802.1Q VLAN Support v1.8
[ 1.060600] UBI: auto-attach mtd2
[ 1.063763] ubi0: attaching mtd2
[ 1.283036] ubi0: scanning is finished
[ 1.298467] ubi0: attached mtd2 (name "ubi", size 126 MiB)
[ 1.304016] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 129024 bytes
[ 1.310936] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 512
[ 1.317665] ubi0: VID header offset: 512 (aligned 512), data offset: 2048
[ 1.324499] ubi0: good PEBs: 1007, bad PEBs: 7, corrupted PEBs: 0
[ 1.330627] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128
[ 1.337880] ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 833779665
[ 1.346978] ubi0: available PEBs: 0, total reserved PEBs: 1007, PEBs reserved for bad PEB handling: 13
[ 1.356648] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 1.363475] ubi0: background thread "ubi_bgt0d" started, PID 918
[ 1.370297] block ubiblock0_1: created from ubi0:1(rootfs)
[ 1.375811] ubiblock: device ubiblock0_1 (rootfs) set to be root filesystem
[ 1.383077] rtc-mv f1010300.rtc: setting system clock to 2017-02-13 18:17:46 UTC (1487009866)
[ 1.449666] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[ 1.469753] ata1.00: ATA-8: HGST HTS545050A7E680, GG2OAH10, max UDMA/100
[ 1.476486] ata1.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 1.519768] ata1.00: configured for UDMA/100
[ 1.524551] scsi 0:0:0:0: Direct-Access ATA HGST HTS545050A7 AH10 PQ: 0 ANSI: 5
[ 1.533871] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 1.541440] sd 0:0:0:0: [sda] 4096-byte physical blocks
[ 1.547642] hub 1-1:1.0: USB hub found
[ 1.551809] sd 0:0:0:0: [sda] Write Protect is off
[ 1.556688] hub 1-1:1.0: 4 ports detected
[ 1.560824] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.849650] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[ 1.879655] ata2: SATA link down (SStatus 0 SControl F300)
[ 1.947309] sda: sda1
[ 1.950806] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.959766] VFS: Mounted root (squashfs filesystem) readonly on device 254:0.
[ 1.967477] Freeing unused kernel memory: 172K (c057f000 - c05aa000)
[ 2.112774] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[ 2.119487] scsi host2: usb-storage 1-1.2:1.0
[ 2.460823] init: Console is alive
[ 2.464385] init: - watchdog -
[ 2.527877] init: - preinit -
[ 2.892056] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[ 2.965612] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
/bin/board_detect: /etc/board.d/02_network: line 1: mtd_get_mac_ascii: not found[ 2.998632] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[ 3.032787] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[ 3.060494] random: jshn: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
[ 3.094284] random: procd: uninitialized urandom read (4 bytes read, 14 bits of entropy available)
Press the [f] key and hit [enter] to enter failsafe mode
Press the [1], [2], [3] or [4] key and hit [enter] to select the debug level
[ 3.245036] scsi 2:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 4
[ 3.255099] sd 2:0:0:0: [sdb] 7866368 512-byte logical blocks: (4.03 GB/3.75 GiB)
[ 3.263209] sd 2:0:0:0: [sdb] Write Protect is off
[ 3.268580] sd 2:0:0:0: [sdb] No Caching mode page found
[ 3.273949] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 3.283992] sdb: sdb1
[ 3.288962] sd 2:0:0:0: [sdb] Attached SCSI removable disk
[ 6.267224] UBIFS (ubi0:2): default file-system created
[ 6.299124] UBIFS (ubi0:2): background thread "ubifs_bgt0_2" started, PID 1010
[ 6.361009] UBIFS (ubi0:2): UBIFS: mounted UBI device 0, volume 2, name "rootfs_data"
[ 6.368886] UBIFS (ubi0:2): LEB size: 129024 bytes (126 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
[ 6.378875] UBIFS (ubi0:2): FS size: 122959872 bytes (117 MiB, 953 LEBs), journal size 6193152 bytes (5 MiB, 48 LEBs)
[ 6.389551] UBIFS (ubi0:2): reserved for root: 4952683 bytes (4836 KiB)
[ 6.396212] UBIFS (ubi0:2): media format: w4/r0 (latest is w4/r0), UUID 80528A4E-79D2-41DC-949D-8D1CB987E179, small LPT model
[ 6.409143] mount_root: overlay filesystem has not been fully initialized yet
[ 6.416853] mount_root: switching to ubifs overlay
[ 6.427077] urandom-seed: Seed file not found (/etc/urandom.seed)
[ 6.481400] procd: - early -
[ 6.484358] procd: - watchdog -
[ 7.304578] procd: - ubus -
[ 7.358041] random: ubusd: uninitialized urandom read (4 bytes read, 31 bits of entropy available)
[ 7.367376] random: ubusd: uninitialized urandom read (4 bytes read, 31 bits of entropy available)
[ 7.376442] random: ubusd: uninitialized urandom read (4 bytes read, 31 bits of entropy available)
[ 7.385776] random: ubusd: uninitialized urandom read (4 bytes read, 31 bits of entropy available)
[ 7.395498] procd: - init -
Please press Enter to activate this console.
BusyBox v1.26.2 () built-in shell (ash)
_________
/ /\ _ ___ ___ ___
/ LE / \ | | | __| \| __|
/ DE / \ | |__| _|| |) | _|
/________/ LE \ |____|___|___/|___| lede-project.org
\ \ DE /
\ LE \ / -----------------------------------------------------------
\ DE \ / Reboot (SNAPSHOT, r3425-f28eef4)
\________\/ -----------------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@LEDE:/#
root@LEDE:/#
root@LEDE:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
root@LEDE:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
root@LEDE:/#
root@LEDE:/#
root@LEDE:/# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 1.3M 1.3M 0 100% /rom
tmpfs 123.9M 56.0K 123.9M 0% /tmp
/dev/ubi0_2 109.6M 40.0K 104.8M 0% /overlay
overlayfs:/overlay 109.6M 40.0K 104.8M 0% /
tmpfs 512.0K 0 512.0K 0% /dev
root@LEDE:/# lsmod
root@LEDE:/#
root@LEDE:/#
root@LEDE:/# [ 61.389665] random: nonblocking pool is initialized
root@LEDE:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
root@LEDE:/# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
root@LEDE:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
root@LEDE:/#
root@LEDE:/#
root@LEDE:/#
root@LEDE:/#
root@LEDE:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
root@LEDE:/# ls -al
drwxr-xr-x 1 root root 224 Feb 13 18:17 .
drwxr-xr-x 1 root root 224 Feb 13 18:17 ..
drwxr-xr-x 2 root root 739 Feb 12 14:57 bin
drwxr-xr-x 4 root root 11440 Feb 13 18:17 dev
drwxr-xr-x 1 root root 648 Feb 13 18:18 etc
-rwxr-xr-x 1 root root 78 Feb 12 14:57 init
drwxr-xr-x 10 root root 439 Feb 12 14:57 lib
drwxr-xr-x 2 root root 3 Feb 12 14:57 mnt
drwxr-xr-x 4 root root 360 Feb 13 18:17 overlay
dr-xr-xr-x 52 root root 0 Jan 1 1970 proc
drwxr-xr-x 16 root root 223 Feb 12 14:57 rom
drwxr-xr-x 2 root root 3 Feb 12 14:57 root
drwxr-xr-x 2 root root 722 Feb 12 14:57 sbin
dr-xr-xr-x 11 root root 0 Feb 13 18:17 sys
drwxrwxrwt 16 root root 440 Feb 13 18:18 tmp
drwxr-xr-x 7 root root 89 Feb 12 14:57 usr
lrwxrwxrwx 1 root root 4 Feb 12 14:57 var -> /tmp
drwxr-xr-x 2 root root 3 Feb 12 14:57 www
root@LEDE:/# cat /etc/config/network
config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd0b:b447:8b12::/48'
config interface 'lan'
option type 'bridge'
option ifname 'eth0'
option proto 'dhcp'
config interface 'lan6'
option ifname 'br-lan'
option proto 'dhcpv6'
root@LEDE:/# insmod mii
root@LEDE:/# insmod r8169
[ 568.788429] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[ 568.794113] pci 0000:00:01.0: enabling device (0140 -> 0143)
[ 568.799841] r8169 0000:01:00.0: enabling device (0140 -> 0143)
[ 568.806654] r8169 0000:01:00.0 eth0: RTL8168d/8111d at 0xd095e000, 00:00:00:00:00:30, XID 083000c0 IRQ 83
[ 568.816312] r8169 0000:01:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko]
root@LEDE:/# [ 568.987408] r8169 0000:01:00.0 eth0: link down
[ 568.992209] r8169 0000:01:00.0 eth0: link down
[ 568.998320] device eth0 entered promiscuous mode
[ 569.005129] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[ 571.684344] r8169 0000:01:00.0 eth0: link up
[ 571.689423] br-lan: port 1(eth0) entered forwarding state
[ 571.694906] br-lan: port 1(eth0) entered forwarding state
[ 571.701407] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[ 573.689642] br-lan: port 1(eth0) entered forwarding state
root@LEDE:/#
root@LEDE:/#
root@LEDE:/# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master br-lan state UP qlen 1000
link/ether 00:00:00:00:00:30 brd ff:ff:ff:ff:ff:ff
3: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000
link/ether 00:00:00:00:00:30 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.173/24 brd 192.168.1.255 scope global br-lan
valid_lft forever preferred_lft forever
inet6 fd9d:383b:5515::200:ff:fe00:30/64 scope global
valid_lft forever preferred_lft forever
inet6 fd05:5934:4cb5::200:ff:fe00:30/64 scope global tentative
valid_lft forever preferred_lft forever
inet6 fd9d:383b:5515::56c/128 scope global tentative
valid_lft forever preferred_lft forever
inet6 fe80::200:ff:fe00:30/64 scope link
valid_lft forever preferred_lft forever
root@LEDE:/#
root@LEDE:/#
