Welcome! Log In Create A New Profile

Advanced

problem with uboot on NSA325v2

Posted by diet 
problem with uboot on NSA325v2
March 23, 2020 09:58AM
Hello Bohdi,

I have a NSA325v2 with u-boot version 1.1.4:

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

U-Boot 1.1.4 (Jul 18 2013 - 10:47:29) Marvell version: 3.5.9

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

Soc: 88F6282 A1CPU running @ 1600Mhz L2 running @ 533Mhz
SysClock = 533Mhz , TClock = 200Mhz

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

CPU : Marvell Feroceon (Rev 1)
Kernel address is 0xc80000.


So I want to update it but the uboot device /dev/mtd0 isn't writable (by default, I think).
I have badblock on that device too:

[ 20.767781] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
[ 20.774166] nand: Eon NAND 128MiB 3,3V 8-bit
[ 20.778469] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 20.784155] Scanning device for bad blocks
[ 20.793896] Bad eraseblock 100 at 0x000000c80000
[ 20.804099] Bad eraseblock 200 at 0x000001900000

# cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"

# mtdinfo /dev/mtd0
mtd0
Name: uboot
Type: nand
Eraseblock size: 131072 bytes, 128.0 KiB
Amount of eraseblocks: 8 (1048576 bytes, 1024.0 KiB)
Minimum input/output unit size: 2048 bytes
Sub-page size: 512 bytes
OOB size: 64 bytes
Character device major/minor: 90:0
Bad blocks are allowed: true
Device is writable: false


Do have an idea, how I can erase (and flash) it?

Thanks for your help
Re: problem with uboot on NSA325v2
March 23, 2020 04:28PM
diet,


> [ 20.784155] Scanning device for bad blocks
> [ 20.793896] Bad eraseblock 100 at
> 0x000000c80000
> [ 20.804099] Bad eraseblock 200 at
> 0x000001900000

The bad blocks are OK. They are not in the 1st MB where u-boot is.

> So I want to update it but the uboot device
> /dev/mtd0 isn't writable (by default, I think).
> I have badblock on that device too:

Interrupt serial console at countdown and get the listing of envs

printenv
And post the entire serial console log here.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: problem with uboot on NSA325v2
March 24, 2020 09:48AM
Sorry for the "noise" about u-boot.
In the meantime I got the new u-boot (after "resetting" the firmware to the origin).

But now i have another problem:

The envoronment seems okay for me:
U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 10 <0x08><0x08><0x08> 9 <0x08><0x08><0x08> 0 
NSA325> printenv
arcNumber=4495
bootargs=console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-nsa325.dtb
ethact=egiga0
ethaddr=52:3b:20:9c:11:51
if_netconsole=ping $serverip
init_ide=ide reset
init_mmc=mmc rescan
init_usb=usb start
ipaddr=172.16.3.210
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
scan_ide=ide reset
scan_mmc=mmc rescan
scan_usb=usb start
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_loaded=0
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

Environment size: 3111/131068 bytes
NSA325>


I want to use only HDDs (without USB device) but the booted kernel throws a panic:

NSA325> bootd
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: WDC WD10EFRX-68FYTN0 Firm: 82.00A82 Ser#:  WD-WCC4J6YHADU6
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Unknown command 'mmc' - try 'help'
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

Partition Map for IDE device 1  --   Partition Type: EFI

Part	Start LBA	End LBA		Name
	Attributes
	Type GUID
	Partition GUID
  1	0x00000800	0x74706d8e	"Linux filesystem"
	attrs:	0x0000000000000000
	type:	0fc63daf-8483-4772-8e79-3d69d8477de4
	type:	linux
	guid:	7beba40a-7380-42c0-a850-3edb6bc6fc31
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: WDC WD10EFRX-68FYTN0 Firm: 82.00A82 Ser#:  WD-WCC4J6YHADU6
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
device ide 0:1
** Bad device ide 0 **
device ide 1:1
1 bytes read in 49 ms (0 Bytes/s)
Found bootable drive on ide 1
loading uImage ...
5202928 bytes read in 1625 ms (3.1 MiB/s)
loading uInitrd ...
7995967 bytes read in 2810 ms (2.7 MiB/s)
loading DTB /boot/dts/kirkwood-nsa325.dtb ...
14006 bytes read in 45 ms (303.7 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.5.1-kirkwood-tld-1
   Created:      2020-03-24  14:12:04 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5202864 Bytes = 5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.5.1-kirkwood-tld-1
   Created:      2020-03-24  14:13:11 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7995903 Bytes = 7.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 1f36d000, end 1fb0d1ff ... OK
   Loading Device Tree to 1f366000, end 1f36c6b5 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.5.1-kirkwood-tld-1 (root@tldDebian) (gcc version 8.3.0 (Debian 8.3.0-6)) #1.0 PREEMPT Sat Feb 1 22:28:36 PST 2020
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: ZyXEL NSA325
...
[    8.423092][  T120] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    8.434620][  T120] ata2.00: ATA-9: WDC WD10EFRX-68FYTN0, 82.00A82, max UDMA/133
[    8.442056][  T120] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    8.454230][  T120] ata2.00: configured for UDMA/133
[    8.469662][   T22] scsi 1:0:0:0: Direct-Access     ATA      WDC WD10EFRX-68F 0A82 PQ: 0 ANSI: 5
[    8.479492][    T7] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    8.488232][    T7] sd 1:0:0:0: [sda] 4096-byte physical blocks
[    8.494303][    T7] sd 1:0:0:0: [sda] Write Protect is off
[    8.499922][    T7] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    8.556684][    T7]  sda: sda1
[    8.561064][    T7] sd 1:0:0:0: [sda] Attached SCSI disk
[   18.403151][    T1] md: Waiting for all devices to be available before autodetect
[   18.410668][    T1] md: If you don't use raid, use raid=noautodetect
[   18.417798][    T1] md: Autodetecting RAID arrays.
[   18.422615][    T1] md: autorun ...
[   18.426174][    T1] md: ... autorun DONE.
[   18.430374][    T1] VFS: Cannot open root device "LABEL=rootfs" or unknown-block(0,0): error -6
[   18.439163][    T1] Please append a correct "root=" boot option; here are the available partitions:
[   18.448323][    T1] 1f00            1024 mtdblock0 
[   18.448326][    T1]  (driver?)
[   18.456327][    T1] 1f01            4096 mtdblock1 
[   18.456329][    T1]  (driver?)
[   18.464327][    T1] 1f02           32768 mtdblock2 
[   18.464329][    T1]  (driver?)
[   18.472287][    T1] 1f03           93184 mtdblock3 
[   18.472289][    T1]  (driver?)
[   18.480267][    T1] 0800       976762584 sda 
[   18.480270][    T1]  driver: sd
[   18.487809][    T1]   0801       976761543 sda1 7beba40a-7380-42c0-a850-3edb6bc6fc31
[   18.487812][    T1] 
[   18.497794][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   18.506792][    T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.5.1-kirkwood-tld-1 #1.0
[   18.514653][    T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   18.521661][    T1] [<8010f668>] (unwind_backtrace) from [<8010b9f4>] (show_stack+0x10/0x14)
[   18.530139][    T1] [<8010b9f4>] (show_stack) from [<80119e8c>] (panic+0xfc/0x328)
[   18.537749][    T1] [<80119e8c>] (panic) from [<80f0157c>] (mount_block_root+0x1c8/0x260)
[   18.545966][    T1] [<80f0157c>] (mount_block_root) from [<80f01704>] (mount_root+0xf0/0x130)
[   18.554529][    T1] [<80f01704>] (mount_root) from [<80f01888>] (prepare_namespace+0x144/0x180)
[   18.563266][    T1] [<80f01888>] (prepare_namespace) from [<80f010a4>] (kernel_init_freeable+0x144/0x1a0)
[   18.572882][    T1] [<80f010a4>] (kernel_init_freeable) from [<809d9904>] (kernel_init+0x8/0x10c)
[   18.581797][    T1] [<809d9904>] (kernel_init) from [<801010e0>] (ret_from_fork+0x14/0x34)
[   18.590092][    T1] Exception stack(0x9ec8dfb0 to 0x9ec8dff8)
[   18.595857][    T1] dfa0:                                     00000000 00000000 00000000 00000000
[   18.604770][    T1] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   18.613680][    T1] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   18.621032][    T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

hopefully yout don't need the full output to give me a hint.

Thank you for your help
Re: problem with uboot on NSA325v2
March 26, 2020 09:57PM
You are missing the rootfs volume label on the drive. Take the disk to another Linux system and plug it in and then run:
lsblk -f

This should help you to identify which device is the disk you just plugged in. You then need to run the following command based on what your disk was identified as. My example assumes it was identified as sdb and your file system is the first partition sdb1.

e2label /dev/sdb1 rootfs

You should now safely eject the disk and take it back to the NSA25 and try again.

Ray
Re: problem with uboot on NSA325v2
March 26, 2020 10:01PM
Most likely what Ray said!

Furthermore, you've cut out the most important part in the serial console bootlog:

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.5.1-kirkwood-tld-1 (root@tldDebian) (gcc version 8.3.0 (Debian 8.3.0-6)) #1.0 PREEMPT Sat Feb 1 22:28:36 PST 2020
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: ZyXEL NSA325
...

What happens here is crucial:)


[    8.423092][  T120] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    8.434620][  T120] ata2.00: ATA-9: WDC WD10EFRX-68FYTN0, 82.00A82, max UDMA/133
[    8.442056][  T120] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    8.454230][  T120] ata2.00: configured for UDMA/133
[    8.469662][   T22] scsi 1:0:0:0: Direct-Access     ATA      WDC WD10EFRX-68F 0A82 PQ: 0 ANSI: 5

That's why I always insist to see the full bootlog. Don't abbreviate the log, it takes very little space in the forum.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: problem with uboot on NSA325v2
March 27, 2020 05:28AM
I checked the label (once again and fscked the filesystem too): it's allright

And now the full bootlog:

U-Boot 2017.07-tld-1 (Sep 05 2017 - 00:42:03 -0700)
ZyXEL NSA325 2-Bay Power Media Server

SoC:   Kirkwood 88F6282_A1
DRAM:  512 MiB
WARNING: Caches not enabled
NAND:  128 MiB
In:    serial
Out:   serial
Err:   serial
Net:   egiga0
MV88E1318 PHY initialized on egiga0
Hit any key to stop autoboot: 10 <0x08><0x08><0x08> 9 <0x08><0x08><0x08> 8 <0x08><0x08><0x08> 7 <0x08><0x08><0x08> 6 <0x08><0x08><0x08> 5 <0x08><0x08><0x08> 4 <0x08><0x08><0x08> 3 <0x08><0x08><0x08> 2 <0x08><0x08><0x08> 1 <0x08><0x08><0x08> 0 
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: WDC WD10EFRX-68FYTN0 Firm: 82.00A82 Ser#:  WD-WCC4J6YHADU6
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
Unknown command 'mmc' - try 'help'
## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0

## Unknown partition table type 0
loading envs from usb 0 ...
** Bad device usb 0 **

Partition Map for IDE device 1  --   Partition Type: EFI

Part	Start LBA	End LBA		Name
	Attributes
	Type GUID
	Partition GUID
  1	0x00000800	0x74706d8e	"Linux filesystem"
	attrs:	0x0000000000000000
	type:	0fc63daf-8483-4772-8e79-3d69d8477de4
	type:	linux
	guid:	7beba40a-7380-42c0-a850-3edb6bc6fc31
Unknown command 'mmc' - try 'help'
running scan_disk ...
Scan device usb
device usb 0:1
** Bad device usb 0 **
device usb 1:1
** Bad device usb 1 **
device usb 2:1
** Bad device usb 2 **
device usb 3:1
** Bad device usb 3 **
Scan device ide

Reset IDE: Bus 0: not available  Bus 1: OK 
  Device 1: Model: WDC WD10EFRX-68FYTN0 Firm: 82.00A82 Ser#:  WD-WCC4J6YHADU6
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 953869.7 MB = 931.5 GB (1953525168 x 512)
device ide 0:1
** Bad device ide 0 **
device ide 1:1
1 bytes read in 50 ms (0 Bytes/s)
Found bootable drive on ide 1
loading uImage ...
5202928 bytes read in 1625 ms (3.1 MiB/s)
loading uInitrd ...
7995967 bytes read in 2811 ms (2.7 MiB/s)
loading DTB /boot/dts/kirkwood-nsa325.dtb ...
14006 bytes read in 44 ms (310.5 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-5.5.1-kirkwood-tld-1
   Created:      2020-03-24  14:12:04 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    5202864 Bytes = 5 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-5.5.1-kirkwood-tld-1
   Created:      2020-03-24  14:13:11 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    7995903 Bytes = 7.6 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
   Loading Kernel Image ... OK
   Loading Ramdisk to 1f36d000, end 1fb0d1ff ... OK
   Loading Device Tree to 1f366000, end 1f36c6b5 ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
[    0.000000][    T0] Booting Linux on physical CPU 0x0
[    0.000000][    T0] Linux version 5.5.1-kirkwood-tld-1 (root@tldDebian) (gcc version 8.3.0 (Debian 8.3.0-6)) #1.0 PREEMPT Sat Feb 1 22:28:36 PST 2020
[    0.000000][    T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000][    T0] CPU: VIVT data cache, VIVT instruction cache
[    0.000000][    T0] OF: fdt: Machine model: ZyXEL NSA325
[    0.000000][    T0] Memory policy: Data cache writeback
[    0.000000][    T0] Built 1 zonelists, mobility grouping on.  Total pages: 130048
[    0.000000][    T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
[    0.000000][    T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[    0.000000][    T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[    0.000000][    T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[    0.000000][    T0] Memory: 495276K/524288K available (9216K kernel code, 926K rwdata, 3860K rodata, 1024K init, 296K bss, 29012K reserved, 0K cma-reserved)
[    0.000000][    T0] random: get_random_u32 called from ____cache_alloc+0x470/0x80c with crng_init=0
[    0.000000][    T0] rcu: Preemptible hierarchical RCU implementation.
[    0.000000][    T0] 	Tasks RCU enabled.
[    0.000000][    T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[    0.000000][    T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[    0.000000][    T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[    0.000007][    T0] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[    0.000042][    T0] Switching to timer-based delay loop, resolution 5ns
[    0.000682][    T0] Console: colour dummy device 80x30
[    0.000727][    T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[    0.000748][    T0] pid_max: default: 32768 minimum: 301
[    0.001058][    T0] LSM: Security Framework initializing
[    0.001200][    T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001224][    T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[    0.001352][    T0] *** VALIDATE tmpfs ***
[    0.002073][    T0] *** VALIDATE proc ***
[    0.002296][    T0] *** VALIDATE cgroup1 ***
[    0.002316][    T0] *** VALIDATE cgroup2 ***
[    0.002408][    T0] CPU: Testing write buffer coherency: ok
[    0.004077][    T1] Setting up static identity map for 0x100000 - 0x100058
[    0.004335][    T1] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[    0.004608][    T1] rcu: Hierarchical SRCU implementation.
[    0.006779][    T1] devtmpfs: initialized
[    0.013216][    T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.013247][    T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[    0.013494][    T1] xor: measuring software checksum speed
[    0.110103][    T1]    arm4regs  :  1452.400 MB/sec
[    0.210068][    T1]    8regs     :   872.000 MB/sec
[    0.310066][    T1]    32regs    :  1268.000 MB/sec
[    0.310081][    T1] xor: using function: arm4regs (1452.400 MB/sec)
[    0.310099][    T1] prandom: seed boundary self test passed
[    0.313232][    T1] prandom: 100 self tests passed
[    0.313241][    T1] pinctrl core: initialized pinctrl subsystem
[    0.314086][    T1] thermal_sys: Registered thermal governor 'step_wise'
[    0.314682][    T1] NET: Registered protocol family 16
[    0.315242][    T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[    0.316050][    T1] audit: initializing netlink subsys (disabled)
[    0.317265][   T14] audit: type=2000 audit(0.310:1): state=initialized audit_enabled=0 res=1
[    0.317378][    T1] cpuidle: using governor ladder
[    0.317453][    T1] cpuidle: using governor menu
[    0.317878][    T1] Feroceon L2: Enabling L2
[    0.317920][    T1] Feroceon L2: Cache support initialised.
[    0.323083][    T1] No ATAGs?
[    2.560048][    C0] random: fast init done
[    4.150617][    T1] raid6: int32x8  gen()   140 MB/s
[    4.320196][    T1] raid6: int32x8  xor()    87 MB/s
[    4.490204][    T1] raid6: int32x4  gen()   142 MB/s
[    4.660193][    T1] raid6: int32x4  xor()    92 MB/s
[    4.830272][    T1] raid6: int32x2  gen()   176 MB/s
[    5.000132][    T1] raid6: int32x2  xor()   125 MB/s
[    5.170345][    T1] raid6: int32x1  gen()   134 MB/s
[    5.340365][    T1] raid6: int32x1  xor()    92 MB/s
[    5.340373][    T1] raid6: using algorithm int32x2 gen() 176 MB/s
[    5.340380][    T1] raid6: .... xor() 125 MB/s, rmw enabled
[    5.340386][    T1] raid6: using intx1 recovery algorithm
[    5.340608][    T1] vgaarb: loaded
[    5.341093][    T1] SCSI subsystem initialized
[    5.341522][    T1] usbcore: registered new interface driver usbfs
[    5.341574][    T1] usbcore: registered new interface driver hub
[    5.341644][    T1] usbcore: registered new device driver usb
[    5.341813][    T1] pps_core: LinuxPPS API ver. 1 registered
[    5.341823][    T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[    5.341844][    T1] PTP clock support registered
[    5.343039][    T1] clocksource: Switched to clocksource orion_clocksource
[    6.346089][    T1] *** VALIDATE bpf ***
[    6.346467][    T1] VFS: Disk quotas dquot_6.6.0
[    6.346543][    T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[    6.346630][    T1] *** VALIDATE ramfs ***
[    6.354856][    T1] NET: Registered protocol family 2
[    6.355574][    T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[    6.355613][    T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    6.355676][    T1] TCP bind hash table entries: 4096 (order: 2, 16384 bytes, linear)
[    6.355728][    T1] TCP: Hash tables configured (established 4096 bind 4096)
[    6.355844][    T1] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[    6.355870][    T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[    6.356066][    T1] NET: Registered protocol family 1
[    6.356678][    T1] RPC: Registered named UNIX socket transport module.
[    6.356689][    T1] RPC: Registered udp transport module.
[    6.356696][    T1] RPC: Registered tcp transport module.
[    6.356702][    T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    6.356714][    T1] PCI: CLS 0 bytes, default 32
[    6.356977][    T1] Trying to unpack rootfs image as initramfs...
[    6.358810][    T1] Initramfs unpacking failed: broken padding
[    6.381515][    T1] Freeing initrd memory: 7812K
[    6.381646][    T1] NetWinder Floating Point Emulator V0.97 (double precision)
[    6.382708][    T1] Initialise system trusted keyrings
[    6.382766][    T1] Key type blacklist registered
[    6.382966][    T1] workingset: timestamp_bits=30 max_order=17 bucket_order=0
[    6.383138][    T1] zbud: loaded
[    6.384149][    T1] NFS: Registering the id_resolver key type
[    6.384175][    T1] Key type id_resolver registered
[    6.384183][    T1] Key type id_legacy registered
[    6.384200][    T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    6.384215][    T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[    6.384570][    T1] jffs2: version 2.2. (NAND) (SUMMARY)  <0xc2><0xa9> 2001-2006 Red Hat, Inc.
[    6.384934][    T1] *** VALIDATE jffs2 ***
[    6.384948][    T1] fuse: init (API version 7.31)
[    6.384964][    T1] *** VALIDATE fuse ***
[    6.384975][    T1] *** VALIDATE fuse ***
[    6.385273][    T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[    6.385442][    T1] orangefs_init: module version upstream loaded
[    6.385453][    T1] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled
[    6.386030][    T1] *** VALIDATE xfs ***
[    6.413730][    T1] async_tx: api initialized (async)
[    6.413750][    T1] Key type asymmetric registered
[    6.413758][    T1] Asymmetric key parser 'x509' registered
[    6.413807][    T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[    6.415017][    T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[    6.416195][    T1] mvebu-gpio f1010140.gpio: IRQ index 3 not found
[    6.416696][    T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[    6.416715][    T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[    6.416727][    T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[    6.416738][    T1] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[    6.416842][    T1] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400
[    6.416874][    T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[    6.418048][    T1] PCI: bus0: Fast back to back transfers disabled
[    6.418070][    T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[    6.418242][    T1] pci 0000:01:00.0: [1033:0194] type 00 class 0x0c0330
[    6.418289][    T1] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00001fff 64bit]
[    6.418432][    T1] pci 0000:01:00.0: PME# supported from D0 D3hot
[    6.418503][    T1] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s x1 link at 0000:00:01.0 (capable of 4.000 Gb/s with 5 GT/s x1 link)
[    6.444098][    T1] PCI: bus1: Fast back to back transfers disabled
[    6.444120][    T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[    6.444278][    T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[    6.444292][    T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[    6.444309][    T1] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe0001fff 64bit]
[    6.444330][    T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[    6.444344][    T1] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe00fffff]
[    6.444437][    T1] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[    6.444503][    T1] pci 0000:01:00.0: enabling device (0140 -> 0142)
[    6.444952][    T1] mv_xor f1060800.xor: Marvell shared XOR driver
[    6.503834][    T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    6.505845][    T1] mv_xor f1060900.xor: Marvell shared XOR driver
[    6.563822][    T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[    6.566033][    T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[    6.567176][    T1] printk: console [ttyS0] disabled
[    6.567258][    T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 26, base_baud = 12500000) is a 16550A
[    7.527374][    T1] printk: console [ttyS0] enabled
[    7.538923][    T1] loop: module loaded
[    7.543338][    T1] sata_mv f1080000.sata: slots 32 ports 2
[    7.551921][    T1] scsi host0: sata_mv
[    7.556304][    T1] scsi host1: sata_mv
[    7.560373][    T1] ata1: SATA max UDMA/133 irq 32
[    7.565241][    T1] ata2: SATA max UDMA/133 irq 32
[    7.570891][    T1] nand: device found, Manufacturer ID: 0x92, Chip ID: 0xf1
[    7.578077][    T1] nand: Eon NAND 128MiB 3,3V 8-bit
[    7.583087][    T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[    7.591397][    T1] Scanning device for bad blocks
[    7.601043][    T1] Bad eraseblock 100 at 0x000000c80000
[    7.611154][    T1] Bad eraseblock 200 at 0x000001900000
[    7.655744][    T1] 4 cmdlinepart partitions found on MTD device orion_nand
[    7.662732][    T1] Creating 4 MTD partitions on "orion_nand":
[    7.668622][    T1] 0x000000000000-0x000000100000 : "u-boot"
[    7.675491][    T1] 0x000000100000-0x000000500000 : "uImage"
[    7.682231][    T1] 0x000000500000-0x000002500000 : "rootfs"
[    7.689132][    T1] 0x000002500000-0x000008000000 : "data"
[    7.697046][    T1] libphy: Fixed MDIO Bus: probed
[    7.702504][    T1] libphy: orion_mdio_bus: probed
[    7.708516][    T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[    7.717220][    T1] mv643xx_eth: Set the PHY to fix link down
[    7.717773][    T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 52:3b:20:9c:11:51
[    7.733196][    T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    7.740488][    T1] ehci-pci: EHCI PCI platform driver
[    7.745775][    T1] ehci-orion: EHCI orion driver
[    7.750652][    T1] orion-ehci f1050000.ehci: EHCI Host Controller
[    7.756940][    T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[    7.765514][    T1] orion-ehci f1050000.ehci: irq 30, io mem 0xf1050000
[    7.793087][    T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[    7.800069][    T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.05
[    7.809113][    T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    7.817102][    T1] usb usb1: Product: EHCI Host Controller
[    7.822723][    T1] usb usb1: Manufacturer: Linux 5.5.1-kirkwood-tld-1 ehci_hcd
[    7.830092][    T1] usb usb1: SerialNumber: f1050000.ehci
[    7.836084][    T1] hub 1-0:1.0: USB hub found
[    7.840583][    T1] hub 1-0:1.0: 1 port detected
[    7.846001][    T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    7.852003][    T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[    7.860473][    T1] xhci_hcd 0000:01:00.0: hcc params 0x014042cb hci version 0x96 quirks 0x0000000000000004
[    7.870758][    T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.05
[    7.879799][    T1] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    7.887786][    T1] usb usb2: Product: xHCI Host Controller
[    7.893419][    T1] usb usb2: Manufacturer: Linux 5.5.1-kirkwood-tld-1 xhci-hcd
[    7.900784][    T1] usb usb2: SerialNumber: 0000:01:00.0
[    7.906153][  T118] ata1: SATA link down (SStatus 0 SControl F300)
[    7.912912][    T1] hub 2-0:1.0: USB hub found
[    7.917471][    T1] hub 2-0:1.0: 2 ports detected
[    7.922874][    T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[    7.928902][    T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[    7.937079][    T1] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[    7.944172][    T1] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[    7.953246][    T1] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.05
[    7.962249][    T1] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    7.970219][    T1] usb usb3: Product: xHCI Host Controller
[    7.975833][    T1] usb usb3: Manufacturer: Linux 5.5.1-kirkwood-tld-1 xhci-hcd
[    7.983191][    T1] usb usb3: SerialNumber: 0000:01:00.0
[    7.989039][    T1] hub 3-0:1.0: USB hub found
[    7.993591][    T1] hub 3-0:1.0: 2 ports detected
[    7.998955][    T1] usbcore: registered new interface driver usb-storage
[    8.006063][    T1] mousedev: PS/2 mouse device common for all mice
[    8.012596][    T1] i2c /dev entries driver
[    8.021811][    T1] rtc rtc0: invalid alarm value: 2020-03-12T34:18:00
[    8.028757][    T1] rtc-pcf8563 0-0051: registered as rtc0
[    8.035866][    T1] device-mapper: uevent: version 1.0.3
[    8.041457][    T1] device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: dm-devel@redhat.com
[    8.051044][    T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[    8.058360][    T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[    8.065858][    T1] device-mapper: multipath service-time: version 0.3.0 loaded
[    8.073275][    T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[    8.080098][    T1] device-mapper: raid: Loading target version 1.15.0
[    8.088527][    T1] hid: raw HID events driver (C) Jiri Kosina
[    8.094789][    T1] exFAT: Version 1.3.0
[    8.098809][    T1] drop_monitor: Initializing network drop monitor service
[    8.106318][    T1] NET: Registered protocol family 17
[    8.111706][    T1] Key type dns_resolver registered
[    8.117108][    T1] registered taskstats version 1
[    8.121965][    T1] Loading compiled-in X.509 certificates
[    8.127605][    T1] zswap: loaded using pool lzo/zbud
[    8.132847][    T1] Key type ._fscrypt registered
[    8.137598][    T1] Key type .fscrypt registered
[    8.158813][    T1] Key type big_key registered
[    8.166232][    T1] Key type encrypted registered
[    8.174279][    T1] rtc-pcf8563 0-0051: setting system clock to 2020-03-27T10:05:54 UTC (1585303554)
[    8.184452][    T1] Waiting 10 sec before mounting root device...
[    8.213072][   T15] usb 1-1: new high-speed USB device number 2 using orion-ehci
[    8.264897][   T15] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=85.32
[    8.273846][   T15] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[    8.281729][   T15] usb 1-1: Product: USB2.0 Hub
[    8.287179][   T15] hub 1-1:1.0: USB hub found
[    8.292028][   T15] hub 1-1:1.0: 4 ports detected
[    8.423083][  T120] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[    8.434604][  T120] ata2.00: ATA-9: WDC WD10EFRX-68FYTN0, 82.00A82, max UDMA/133
[    8.442032][  T120] ata2.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[    8.454217][  T120] ata2.00: configured for UDMA/133
[    8.469646][   T22] scsi 1:0:0:0: Direct-Access     ATA      WDC WD10EFRX-68F 0A82 PQ: 0 ANSI: 5
[    8.479480][    T7] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[    8.488218][    T7] sd 1:0:0:0: [sda] 4096-byte physical blocks
[    8.494289][    T7] sd 1:0:0:0: [sda] Write Protect is off
[    8.499907][    T7] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    8.556966][    T7]  sda: sda1
[    8.561356][    T7] sd 1:0:0:0: [sda] Attached SCSI disk
[   18.403145][    T1] md: Waiting for all devices to be available before autodetect
[   18.410663][    T1] md: If you don't use raid, use raid=noautodetect
[   18.417806][    T1] md: Autodetecting RAID arrays.
[   18.422618][    T1] md: autorun ...
[   18.426177][    T1] md: ... autorun DONE.
[   18.430378][    T1] VFS: Cannot open root device "LABEL=rootfs" or unknown-block(0,0): error -6
[   18.439168][    T1] Please append a correct "root=" boot option; here are the available partitions:
[   18.448326][    T1] 1f00            1024 mtdblock0 
[   18.448329][    T1]  (driver?)
[   18.456330][    T1] 1f01            4096 mtdblock1 
[   18.456332][    T1]  (driver?)
[   18.464329][    T1] 1f02           32768 mtdblock2 
[   18.464331][    T1]  (driver?)
[   18.472290][    T1] 1f03           93184 mtdblock3 
[   18.472292][    T1]  (driver?)
[   18.480270][    T1] 0800       976762584 sda 
[   18.480273][    T1]  driver: sd
[   18.487813][    T1]   0801       976761543 sda1 7beba40a-7380-42c0-a850-3edb6bc6fc31
[   18.487815][    T1] 
[   18.497797][    T1] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   18.506796][    T1] CPU: 0 PID: 1 Comm: swapper Not tainted 5.5.1-kirkwood-tld-1 #1.0
[   18.514657][    T1] Hardware name: Marvell Kirkwood (Flattened Device Tree)
[   18.521665][    T1] [<8010f668>] (unwind_backtrace) from [<8010b9f4>] (show_stack+0x10/0x14)
[   18.530142][    T1] [<8010b9f4>] (show_stack) from [<80119e8c>] (panic+0xfc/0x328)
[   18.537751][    T1] [<80119e8c>] (panic) from [<80f0157c>] (mount_block_root+0x1c8/0x260)
[   18.545969][    T1] [<80f0157c>] (mount_block_root) from [<80f01704>] (mount_root+0xf0/0x130)
[   18.554532][    T1] [<80f01704>] (mount_root) from [<80f01888>] (prepare_namespace+0x144/0x180)
[   18.563269][    T1] [<80f01888>] (prepare_namespace) from [<80f010a4>] (kernel_init_freeable+0x144/0x1a0)
[   18.572886][    T1] [<80f010a4>] (kernel_init_freeable) from [<809d9904>] (kernel_init+0x8/0x10c)
[   18.581801][    T1] [<809d9904>] (kernel_init) from [<801010e0>] (ret_from_fork+0x14/0x34)
[   18.590094][    T1] Exception stack(0x9ec8dfb0 to 0x9ec8dff8)
[   18.595860][    T1] dfa0:                                     00000000 00000000 00000000 00000000
[   18.604773][    T1] dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
[   18.613684][    T1] dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
[   18.621034][    T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---


show these lines

[    6.356977][    T1] Trying to unpack rootfs image as initramfs...
[    6.358810][    T1] Initramfs unpacking failed: broken padding

a problem?

Thanks for all your help!
Dieter
Re: problem with uboot on NSA325v2
March 27, 2020 05:57AM
Maybe I found my problem (reading the thread 'Linux Kernel 5.5.1 Kirkwood package and Debian rootfs' again):

I have no idea what I can do without a running armel device (the NSA is my only device) with step 3 (dpkg -i linux-image-5.5.1-kirkwood-tld-1_1.0_armel.deb), so I skipped this step and I think this was my fault.

I there any way to do this step on a x86-system (maybe untarring data.tar.xz and doing all the things by hand which are in control.tar.xz)?

Uff.-(
Re: problem with uboot on NSA325v2
March 27, 2020 06:10AM
diet,

Quote

[ 6.356977][ T1] Trying to unpack rootfs image as initramfs...
[ 6.358810][ T1] Initramfs unpacking failed: broken padding

Yes that was the problem!


> I have no idea what I can do without a running
> armel device (the NSA is my only device) with step
> 3 (dpkg -i
> linux-image-5.5.1-kirkwood-tld-1_1.0_armel.deb),
> so I skipped this step and I think this was my
> fault.

> I there any way to do this step on a x86-system
> (maybe untarring data.tar.xz and doing all the
> things by hand which are in control.tar.xz)?
>

No need to have armel device. You just follow the instruction and use the rootfs tarball Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 to create the rootfs using your x86 system.

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

And boot with this Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs.

After you are successfully booted, the system is running OK, then upgrade the kernel while the NSA325 box is running.

There is no need to worry about the kernel linux-5.5.1-kirkwood-tld-1 until after you have your box running.

I mentiond this in the release thread:

Quote

Note: If this is your first time installation, then you need rootfs Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (this has kernel linux-5.2.9-kirkwood-tld-1 already installed). Please scroll down to 25 Aug 2019 section for download link and installation instruction.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 2 time(s). Last edit at 03/27/2020 06:12AM by bodhi.
Re: problem with uboot on NSA325v2
March 27, 2020 08:58AM
Thank you for all your help!

Now I have a running 5.5.1 kernel in a bulleye system (that's what I wanted.-)

I think I made some steps in a wrong order.-(

Keep well and fit
Dieter
Re: problem with uboot on NSA325v2
March 27, 2020 05:02PM
diet Wrote:
-------------------------------------------------------
> Thank you for all your help!
>
> Now I have a running 5.5.1 kernel in a bulleye
> system (that's what I wanted.-)
>
> I think I made some steps in a wrong order.-(
>
> Keep well and fit
> Dieter

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: problem with uboot on NSA325v2
March 30, 2020 07:13AM
But now I found out how slow this device is.-(

with nfs I get ~ 35 MB/s (write speed)

with scp (to the NSA) only ~ 10 MB/s (the same scp to a laptop gives me ~ 50 GB/s)

Allthough the HD shows (with hdparm -t) ~ 124.46 MB/sec and
ethtool shows Speed: 1000Mb/s (which are ~ 125 MB/s)

I think this device is too slow for my requisitions.-)
Is it the CPU or the minimal memory (512 MB), which slows it down?
Re: problem with uboot on NSA325v2
March 30, 2020 05:21PM
Dieter,

Samba and NFS needs to be tuned to get the real performance. The basic rootfs I released is a very basic system and has no tuning done for it.

Look at the Wiki thread for some benchmark numbers to see they match with what you see on your box. One immediate improvement you can make is Increase "NFSD max_block_size".

https://forum.doozan.com/read.php?2,23630

Quote

Benchmarks

Pogo ProV3 vs Pogo E02
Another Pogo Pro V3 benchmarks
Network performance - SAMBA - NFS (various protocols)
Pogo Pro V3 Network NFS benchmarks
Kirkwood vs OXNAS network performance (with flow control)
Kirkwood vs OXNAS network performance (flow control turned off )
OXNAS vs OXNAS network performance (flow control turned off)

Quote

NFS

NFS - HowTo set up NFS shares (and boot NFS rootfs)
Boot your Dockstar (and other plugs) using NFS rootfs
Increase NFSD max_block_size

=======

This NFS tuning subject is something I've been avoid to do it myself. We have many experienced users in this forum, but nobody cares enough (or has the time to do it) to try and write a tutorial.

I don't want to stop building kernels and spend my free time on this subject :) But perhaps I need to.


-bodhi
===========================
Forum Wiki
bodhi's corner
Re: problem with uboot on NSA325v2
March 31, 2020 09:07AM
I do wish there was a definitive guide for optimal file transfers between low CPU/RAM devices. I see similar questions from time to time but don't have a good answer to provide anyone.

It seems like there is some sort of upper limit in the range you're seeing though I haven't identified what it is exactly.
Re: problem with uboot on NSA325v2
March 31, 2020 05:24PM
1000001101000,

> I do wish there was a definitive guide for optimal
> file transfers between low CPU/RAM devices. I see
> similar questions from time to time but don't have
> a good answer to provide anyone.

There was a pretty good one. I need to find the link to that site. I recall I saved it somewhere.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: problem with uboot on NSA325v2
April 01, 2020 07:04PM
Quote
bodhi
There was a pretty good one. I need to find the link to that site. I recall I saved it somewhere.

I remember it wrong! that was network tuning only. And we don't have any network performance problem with my built kernel (I use network config from Debian and did not change any parameters).

As of right now, Samba is probably faster than NFS, ironically :), because we aleady have tuning specifics in smb.conf.

-bodhi
===========================
Forum Wiki
bodhi's corner
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: