Debian on ReadyNas RN2120
Posted by spiderdijon
|
Re: Debian on ReadyNas RN2120 March 03, 2024 03:26PM |
Admin Registered: 13 years ago Posts: 19,102 |
Backup NAND mtds and also use mtd0 for kwboot
Change to a directory where these backup files will be save.
And then compress the file mtd0.rn2120 to make it less than 1MB (the forum rules only allow files that are upto 1MB).
And attach it here in your post.
You can try kwboot again using mtd0.rn2120 as u-boot image. If this works with kwboot, I'll tweak the image to make it a rescue image.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Change to a directory where these backup files will be save.
nanddump --noecc --omitoob -f mtd0.rn2120 /dev/mtd0 nanddump --noecc --omitoob -f mtd1.rn2120 /dev/mtd1 nanddump --noecc --omitoob -f mtd2.rn2120 /dev/mtd2 nanddump --noecc --omitoob -f mtd3.rn2120 /dev/mtd3 nanddump --noecc --omitoob -f mtd4.rn2120 /dev/mtd4
And then compress the file mtd0.rn2120 to make it less than 1MB (the forum rules only allow files that are upto 1MB).
tar cjf mtd0.rn2120.tar.bz2 mtd0.rn2120
And attach it here in your post.
You can try kwboot again using mtd0.rn2120 as u-boot image. If this works with kwboot, I'll tweak the image to make it a rescue image.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 04, 2024 05:15AM |
Registered: 9 months ago Posts: 27 |
Looks good! cpuinfo reports two processors now. However what ever is causing
Is still present.
pci 0000:00:01.0: not ready after 65535ms; giving up
Is still present.
BootROM 1.20
Booting from NAND flash
General initialization - Version: 1.0.0
High speed PHY - Version: 2.1.8 (COM-PHY-V22)
Update Device ID PEX0782311AB
Update Device ID PEX1782311AB
Update Device ID PEX2782311AB
Update Device ID PEX3782311AB
Update Device ID PEX4782311AB
Update Device ID PEX5782311AB
Update Device ID PEX6782311AB
Update PEX Device ID 0x78230
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run with PBS.
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED
▒
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **
U-Boot 2011.12-gd923454 (Sep 08 2015 - 18:59:32) Marvell version: v2011.12 2014_T2.0p1
Netgear version: 09/08/2015 ReadyNAS-2120 v2.0
Board: DB-78460-BP rev 2.0
SoC: MV78230 B0
running 2 CPUs
Custom configuration
CPU: Marvell PJ4B (584) v7 (Rev 2) LE
CPU 0
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 250 [MHz]
DDR @ 600 [MHz]
DDR 32Bit Width, FastPath Memory Access
DDR ECC Disabled
DRAM: 2 GiB
▒
Map: Code: 0x7fedf000:0x7ff9f204
BSS: 0x7ffefc20
Stack: 0x7f9deef8
Heap: 0x7f9df000:0x7fedf000
NAND: 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000005de0000
nand_read_bbt: Bad block at 0x000005e00000
Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0.0(0-0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1-1): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1.0(2-2): Root Complex Interface, Detected Link X1, GEN 2.0
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Host Mode
Modules Detected:
Net: egiga0, egiga1 [PRIME]
Power On!
FDT loaded successfully
Found 2 disks present
Hit any key to stop autoboot: 0
Marvell>>
Marvell>>
Marvell>> setenv bootdev usb
Unknown command 'setenv' - try 'help'
Marvell>>
BootROM 1.20
Booting from NAND flash
General initialization - Version: 1.0.0
High speed PHY - Version: 2.1.8 (COM-PHY-V22)
Update Device ID PEX0782311AB
Update Device ID PEX1782311AB
Update Device ID PEX2782311AB
Update Device ID PEX3782311AB
Update Device ID PEX4782311AB
Update Device ID PEX5782311AB
Update Device ID PEX6782311AB
Update PEX Device ID 0x78230
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run with PBS.
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED
▒
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **
U-Boot 2011.12-gd923454 (Sep 08 2015 - 18:59:32) Marvell version: v2011.12 2014_T2.0p1
Netgear version: 09/08/2015 ReadyNAS-2120 v2.0
Board: DB-78460-BP rev 2.0
SoC: MV78230 B0
running 2 CPUs
Custom configuration
CPU: Marvell PJ4B (584) v7 (Rev 2) LE
CPU 0
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 250 [MHz]
DDR @ 600 [MHz]
DDR 32Bit Width, FastPath Memory Access
DDR ECC Disabled
DRAM: 2 GiB
▒
Map: Code: 0x7fedf000:0x7ff9f204
BSS: 0x7ffefc20
Stack: 0x7f9deef8
Heap: 0x7f9df000:0x7fedf000
NAND: 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000005de0000
nand_read_bbt: Bad block at 0x000005e00000
Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0.0(0-0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1-1): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1.0(2-2): Root Complex Interface, Detected Link X1, GEN 2.0
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Host Mode
Modules Detected:
Net: egiga0, egiga1 [PRIME]
Power On!
FDT loaded successfully
Found 2 disks present
Hit any key to stop autoboot: 0
Marvell>>
Marvell>>
Marvell>>
Marvell>>
Marvell>> setenv bootdev usb
Marvell>> setenv device 0:1
Marvell>> setenv load_image_addr 0x02000000
Marvell>> setenv load_initrd_addr 0x3000000
Marvell>> setenv load_image 'echo loading uImage ...; ext2load $bootdev $device $load_image_addr /boot/uImage'
Marvell>> setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd'
Marvell>> setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial"'
Marvell>> setenv bootcmd_exec 'echo Booting Debian from $bootdev; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_initrd; bootm $load_image_addr $load_initrd_addr'
Marvell>> setenv bootcmd_custom_usb 'usb start; run set_bootargs; run bootcmd_exec'
Marvell>> setenv bootcmd 'run bootcmd_custom_usb'
Marvell>> setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)'
Marvell>> setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"'
Marvell>> boot
(Re)start USB...
USB: Active port: 0
Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 2 USB Device(s) found
scanning bus for storage devices... 1 Storage Device(s) found
Booting Debian from usb
loading uImage ...
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
5238129 bytes read
loading uInitrd ...
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
5254542 bytes read
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-6.7.5-mvebu-370xp-tld-3
Created: 2024-03-04 11:02:33 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5238065 Bytes = 5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
Image Name: initramfs-6.7.5-mvebu-370xp-tld-
Created: 2024-03-04 11:04:04 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 5254478 Bytes = 5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
Starting kernel ...
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 6.7.5-mvebu-370xp-tld-3 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Thu Feb 29 19:03:59 PST 2024
[ 0.000000][ T0] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[ 0.000000][ T0] CPU: div instructions available: patching division code
[ 0.000000][ T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: NETGEAR ReadyNAS 2120
[ 0.000000][ T0] printk: legacy bootconsole [earlycon0] enabled
[ 0.000000][ T0] Memory policy: Data cache writealloc
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x000000002fffffff]
[ 0.000000][ T0] HighMem [mem 0x0000000030000000-0x000000007fffffff]
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000007fffffff]
[ 0.000000][ T0] percpu: Embedded 29 pages/cpu s25364 r8192 d85228 u118784
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) earlyprintk=serial mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs) reason=normal bdtype=rn2120
[ 0.000000][ T0] Unknown kernel command line parameters "reason=normal bdtype=rn2120", will be passed to user space.
[ 0.000000][ T0] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 522560
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.000000][ T0] Memory: 2053672K/2097152K available (10240K kernel code, 873K rwdata, 3536K rodata, 1024K init, 318K bss, 43480K reserved, 0K cma-reserved, 1310708K highmem)
[ 0.000000][ T0] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 0.000000][ T0] rcu: RCU restricting CPUs from NR_CPUS=4 to nr_cpu_ids=2.
[ 0.000000][ T0] Trampoline variant of Tasks RCU enabled.
[ 0.000000][ T0] Tracing variant of Tasks RCU enabled.
[ 0.000000][ T0] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[ 0.000000][ T0] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=2
[ 0.000000][ T0] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] L2C: DT/platform modifies aux control register: 0x1a696b10 -> 0x1a696b12
[ 0.000000][ T0] Aurora cache controller enabled, 16 ways, 1024 kB
[ 0.000000][ T0] Aurora: CACHE_ID 0x00000100, AUX_CTRL 0x1a696b12
[ 0.000000][ T0] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000][ T0] Switching to timer-based delay loop, resolution 40ns
[ 0.000001][ T0] sched_clock: 32 bits at 25MHz, resolution 40ns, wraps every 85899345900ns
[ 0.008519][ T0] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[ 0.020758][ T0] kfence: initialized - using 2097152 bytes for 255 objects at 0x(ptrval)-0x(ptrval)
[ 0.030509][ T0] Console: colour dummy device 80x30
[ 0.035674][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=250000)
[ 0.046694][ T0] CPU: Testing write buffer coherency: ok
[ 0.052302][ T0] pid_max: default: 32768 minimum: 301
[ 0.062113][ T0] LSM: initializing lsm=capability,integrity
[ 0.069350][ T0] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.077349][ T0] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes, linear)
[ 0.091708][ T1] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.099729][ T1] RCU Tasks: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[ 0.107736][ T1] RCU Tasks Trace: Setting shift to 1 and lim to 1 rcu_task_cb_adjust=1.
[ 0.116152][ T1] Setting up static identity map for 0x100000 - 0x100060
[ 0.123396][ T1] mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x2
[ 0.129344][ T1] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.136415][ T1] rcu: Hierarchical SRCU implementation.
[ 0.141916][ T1] rcu: Max phase no-delay instances is 1000.
[ 0.148876][ T1] smp: Bringing up secondary CPUs ...
[ 0.154900][ T1] Booting CPU 1
[ 0.158594][ T0] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.168668][ T1] smp: Brought up 1 node, 2 CPUs
[ 0.179788][ T1] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[ 0.186758][ T1] CPU: All CPU(s) started in SVC mode.
[ 0.193822][ T1] devtmpfs: initialized
[ 0.205293][ T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[ 0.214129][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.224800][ T1] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.235389][ T1] prandom: seed boundary self test passed
[ 0.243465][ T1] prandom: 100 self tests passed
[ 0.248240][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.256172][ T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.263357][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.274308][ T1] audit: initializing netlink subsys (disabled)
[ 0.280733][ T30] audit: type=2000 audit(0.260:1): state=initialized audit_enabled=0 res=1
[ 0.281630][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.289221][ T1] cpuidle: using governor ladder
[ 0.300736][ T1] cpuidle: using governor menu
[ 0.305574][ T19] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0
[ 0.315278][ T19] hw-breakpoint: CPU 0 failed to disable vector catch
[ 0.321927][ T20] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1
[ 0.335676][ T1] platform soc: Fixed dependency cycle(s) with /soc/internal-regs/interrupt-controller@20a00
[ 0.520172][ T1] raid6: int32x8 gen() 227 MB/s
[ 0.690169][ T1] raid6: int32x4 gen() 243 MB/s
[ 0.860116][ T1] raid6: int32x2 gen() 378 MB/s
[ 1.030107][ T1] raid6: int32x1 gen() 394 MB/s
[ 1.035055][ T1] raid6: using algorithm int32x1 gen() 394 MB/s
[ 1.210131][ T1] raid6: .... xor() 190 MB/s, rmw enabled
[ 1.215687][ T1] raid6: using intx1 recovery algorithm
[ 1.222844][ T1] SCSI subsystem initialized
[ 1.227846][ T1] usbcore: registered new interface driver usbfs
[ 1.234113][ T1] usbcore: registered new interface driver hub
[ 1.240226][ T1] usbcore: registered new device driver usb
[ 1.246310][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 1.251969][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 1.261791][ T1] PTP clock support registered
[ 1.268757][ T1] vgaarb: loaded
[ 1.272925][ T1] clocksource: Switched to clocksource armada_370_xp_clocksource
[ 1.285511][ T1] VFS: Disk quotas dquot_6.6.0
[ 1.290371][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 1.314389][ T1] NET: Registered PF_INET protocol family
[ 1.320161][ T1] IP idents hash table entries: 16384 (order: 5, 131072 bytes, linear)
[ 1.330020][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 1.339237][ T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 1.347770][ T1] TCP established hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 1.356292][ T1] TCP bind hash table entries: 8192 (order: 5, 131072 bytes, linear)
[ 1.364306][ T1] TCP: Hash tables configured (established 8192 bind 8192)
[ 1.371797][ T1] MPTCP token hash table entries: 1024 (order: 2, 16384 bytes, linear)
[ 1.380148][ T1] UDP hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 1.387482][ T1] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes, linear)
[ 1.395740][ T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 1.402953][ T1] RPC: Registered named UNIX socket transport module.
[ 1.409548][ T1] RPC: Registered udp transport module.
[ 1.414945][ T1] RPC: Registered tcp transport module.
[ 1.420323][ T1] RPC: Registered tcp-with-tls transport module.
[ 1.426493][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 1.433632][ T1] PCI: CLS 0 bytes, default 64
[ 1.439096][ T29] Trying to unpack rootfs image as initramfs...
[ 1.445335][ T1] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 1.457172][ T1] Initialise system trusted keyrings
[ 1.462406][ T1] Key type blacklist registered
[ 1.468841][ T1] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[ 1.476175][ T1] zbud: loaded
[ 1.489034][ T1] NFS: Registering the id_resolver key type
[ 1.494859][ T1] Key type id_resolver registered
[ 1.499726][ T1] Key type id_legacy registered
[ 1.504623][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 1.512038][ T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 1.668664][ T1] xor: measuring software checksum speed
[ 1.675627][ T29] Freeing initrd memory: 5132K
[ 1.682990][ T1] arm4regs : 1199 MB/sec
[ 1.699108][ T1] 8regs : 888 MB/sec
[ 1.713052][ T1] 32regs : 1108 MB/sec
[ 1.718087][ T1] xor: using function: arm4regs (1199 MB/sec)
[ 1.724009][ T1] async_tx: api initialized (async)
[ 1.729050][ T1] Key type asymmetric registered
[ 1.733842][ T1] Asymmetric key parser 'x509' registered
[ 1.739768][ T1] bounce: pool size: 64 pages
[ 1.744730][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[ 1.753304][ T1] io scheduler bfq registered
[ 1.761141][ T1] armada-xp-pinctrl d0018000.pin-ctrl: registered pinctrl driver
[ 1.772011][ T1] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 1.782326][ T1] debugfs: Directory 'd0018100.gpio' with parent 'regmap' already present!
[ 1.791844][ T1] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 1.802045][ T1] debugfs: Directory 'd0018140.gpio' with parent 'regmap' already present!
[ 1.812241][ T1] mvebu-pcie soc:pcie@82000000: host bridge /soc/pcie@82000000 ranges:
[ 1.820405][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0040000..0x00d0041fff -> 0x0000040000
[ 1.829653][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0044000..0x00d0045fff -> 0x0000044000
[ 1.838885][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0048000..0x00d0049fff -> 0x0000048000
[ 1.848114][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d004c000..0x00d004dfff -> 0x000004c000
[ 1.857342][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0080000..0x00d0081fff -> 0x0000080000
[ 1.866568][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 1.876316][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 1.886068][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 1.895812][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 1.905555][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 1.915296][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 1.925038][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 1.934784][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 1.944541][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[ 1.954284][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[ 1.965190][ T1] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
[ 1.972592][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 1.978789][ T1] pci_bus 0000:00: root bus resource [mem 0xd0040000-0xd0041fff] (bus address [0x00040000-0x00041fff])
[ 1.989643][ T1] pci_bus 0000:00: root bus resource [mem 0xd0044000-0xd0045fff] (bus address [0x00044000-0x00045fff])
[ 2.000527][ T1] pci_bus 0000:00: root bus resource [mem 0xd0048000-0xd0049fff] (bus address [0x00048000-0x00049fff])
[ 2.011384][ T1] pci_bus 0000:00: root bus resource [mem 0xd004c000-0xd004dfff] (bus address [0x0004c000-0x0004dfff])
[ 2.022229][ T1] pci_bus 0000:00: root bus resource [mem 0xd0080000-0xd0081fff] (bus address [0x00080000-0x00081fff])
[ 2.033070][ T1] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[ 2.040613][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 3.332978][ T1] pci 0000:00:01.0: not ready after 1023ms; waiting
[ 4.422972][ T1] pci 0000:00:01.0: not ready after 2047ms; waiting
[ 6.502955][ T1] pci 0000:00:01.0: not ready after 4095ms; waiting
[ 10.662948][ T1] pci 0000:00:01.0: not ready after 8191ms; waiting
[ 19.062955][ T1] pci 0000:00:01.0: not ready after 16383ms; waiting
[ 35.702947][ T1] pci 0000:00:01.0: not ready after 32767ms; waiting
[ 68.982954][ T1] pci 0000:00:01.0: not ready after 65535ms; giving up
[ 68.989784][ T1] pci 0000:00:02.0: [11ab:7823] type 01 class 0x060400
[ 68.997380][ T1] pci 0000:00:05.0: [11ab:7823] type 01 class 0x060400
[ 69.006803][ T1] PCI: bus0: Fast back to back transfers disabled
[ 69.013107][ T1] pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 69.021793][ T1] pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 69.030887][ T1] pci 0000:01:00.0: [1b4b:9170] type 00 class 0x010601
[ 69.037622][ T1] pci 0000:01:00.0: reg 0x10: [io 0xfffffff8-0xffffffff]
[ 69.044603][ T1] pci 0000:01:00.0: reg 0x14: [io 0xfffffffc-0xffffffff]
[ 69.051552][ T1] pci 0000:01:00.0: reg 0x18: [io 0xfffffff8-0xffffffff]
[ 69.058518][ T1] pci 0000:01:00.0: reg 0x1c: [io 0xfffffffc-0xffffffff]
[ 69.065483][ T1] pci 0000:01:00.0: reg 0x20: [io 0xfffffff0-0xffffffff]
[ 69.072430][ T1] pci 0000:01:00.0: reg 0x24: [mem 0x42000000-0x420001ff]
[ 69.079395][ T1] pci 0000:01:00.0: reg 0x30: [mem 0xd0000000-0xd000ffff pref]
[ 69.086828][ T1] pci 0000:01:00.0: Enabling fixed DMA alias to 00.1
[ 69.093413][ T1] pci 0000:01:00.0: PME# supported from D3hot
[ 69.099838][ T1] pci 0000:00:02.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[ 69.133048][ T1] PCI: bus1: Fast back to back transfers disabled
[ 69.139305][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 69.146974][ T1] pci 0000:02:00.0: [1b73:1009] type 00 class 0x0c0330
[ 69.153708][ T1] pci 0000:02:00.0: reg 0x10: [mem 0x48000000-0x4800ffff 64bit]
[ 69.161181][ T1] pci 0000:02:00.0: reg 0x18: [mem 0x48010000-0x48010fff 64bit]
[ 69.168672][ T1] pci 0000:02:00.0: reg 0x20: [mem 0x48011000-0x48011fff 64bit]
[ 69.176239][ T1] pci 0000:02:00.0: supports D1
[ 69.180930][ T1] pci 0000:02:00.0: PME# supported from D0 D1 D3hot D3cold
[ 69.188522][ T1] pci 0000:00:05.0: ASPM: current common clock configuration is inconsistent, reconfiguring
[ 69.223008][ T1] PCI: bus2: Fast back to back transfers disabled
[ 69.229265][ T1] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 69.236656][ T1] pci 0000:00:02.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff]
[ 69.244226][ T1] pci 0000:00:05.0: BAR 14: assigned [mem 0xf8100000-0xf81fffff]
[ 69.251773][ T1] pci 0000:00:02.0: BAR 13: assigned [io 0x10000-0x10fff]
[ 69.258850][ T1] pci 0000:01:00.0: BAR 6: assigned [mem 0xf8000000-0xf800ffff pref]
[ 69.266760][ T1] pci 0000:01:00.0: BAR 5: assigned [mem 0xf8010000-0xf80101ff]
[ 69.274238][ T1] pci 0000:01:00.0: BAR 4: assigned [io 0x10000-0x1000f]
[ 69.281182][ T1] pci 0000:01:00.0: BAR 0: assigned [io 0x10010-0x10017]
[ 69.288148][ T1] pci 0000:01:00.0: BAR 2: assigned [io 0x10018-0x1001f]
[ 69.295108][ T1] pci 0000:01:00.0: BAR 1: assigned [io 0x10020-0x10023]
[ 69.302051][ T1] pci 0000:01:00.0: BAR 3: assigned [io 0x10024-0x10027]
[ 69.309010][ T1] pci 0000:00:02.0: PCI bridge to [bus 01]
[ 69.314667][ T1] pci 0000:00:02.0: bridge window [io 0x10000-0x10fff]
[ 69.321618][ T1] pci 0000:00:02.0: bridge window [mem 0xf8000000-0xf80fffff]
[ 69.329107][ T1] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8100000-0xf810ffff 64bit]
[ 69.337111][ T1] pci 0000:02:00.0: BAR 2: assigned [mem 0xf8110000-0xf8110fff 64bit]
[ 69.345125][ T1] pci 0000:02:00.0: BAR 4: assigned [mem 0xf8111000-0xf8111fff 64bit]
[ 69.353137][ T1] pci 0000:00:05.0: PCI bridge to [bus 02]
[ 69.358783][ T1] pci 0000:00:05.0: bridge window [mem 0xf8100000-0xf81fffff]
[ 69.366454][ T1] pcieport 0000:00:02.0: enabling device (0140 -> 0143)
[ 69.373391][ T1] pcieport 0000:00:05.0: enabling device (0140 -> 0142)
[ 69.381977][ T1] mv_xor d0060900.xor: Marvell shared XOR driver
[ 69.464748][ T1] mv_xor d0060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 69.477303][ T1] mv_xor d00f0900.xor: Marvell shared XOR driver
[ 69.544744][ T1] mv_xor d00f0900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 69.718880][ T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 69.732140][ T1] printk: legacy console [ttyS0] disabled
[ 69.759474][ T1] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 38, base_baud = 15625000) is a 16550A
[ 69.769263][ T1] printk: legacy console [ttyS0] enabled
[ 69.769263][ T1] printk: legacy console [ttyS0] enabled
[ 69.780303][ T1] printk: legacy bootconsole [earlycon0] disabled
[ 69.780303][ T1] printk: legacy bootconsole [earlycon0] disabled
[ 69.827559][ T1] ahci 0000:01:00.0: enabling device (0146 -> 0147)
[ 69.834335][ T1] ahci 0000:01:00.0: AHCI 0001.0000 32 slots 2 ports 6 Gbps 0x3 impl SATA mode
[ 69.843195][ T1] ahci 0000:01:00.0: flags: 64bit ncq sntf led only pmp fbs pio slum part sxs
[ 69.855019][ T1] scsi host0: ahci
[ 69.860085][ T1] scsi host1: ahci
[ 69.864386][ T1] ata1: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010100 irq 40 lpm-pol 0
[ 69.873330][ T1] ata2: SATA max UDMA/133 abar m512@0xf8010000 port 0xf8010180 irq 40 lpm-pol 0
[ 69.883751][ T1] sata_mv d00a0000.sata: slots 32 ports 2
[ 69.892298][ T1] scsi host2: sata_mv
[ 69.897393][ T1] scsi host3: sata_mv
[ 69.901821][ T1] ata3: SATA max UDMA/133 irq 41 lpm-pol 0
[ 69.907562][ T1] ata4: SATA max UDMA/133 irq 41 lpm-pol 0
[ 69.915612][ T1] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 69.922698][ T1] nand: Hynix H27U1G8F2BTR-BC
[ 69.927286][ T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 69.935988][ T1] Bad block table found at page 65472, version 0x01
[ 69.942786][ T1] Bad block table found at page 65408, version 0x01
[ 69.949448][ T1] nand_read_bbt: bad block at 0x000005de0000
[ 69.955319][ T1] nand_read_bbt: bad block at 0x000005e00000
[ 69.961233][ T1] 5 cmdlinepart partitions found on MTD device pxa3xx_nand-0
[ 69.968498][ T1] Creating 5 MTD partitions on "pxa3xx_nand-0":
[ 69.974668][ T1] 0x000000000000-0x000000180000 : "u-boot"
[ 69.982608][ T1] 0x000000180000-0x0000001a0000 : "u-boot-env"
[ 69.991031][ T1] 0x000000200000-0x000000800000 : "uImage"
[ 69.999158][ T1] 0x000000800000-0x000000c00000 : "minirootfs"
[ 70.007564][ T1] 0x000000c00000-0x000008000000 : "ubifs"
[ 70.016759][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 70.025363][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 70.086532][ T1] mvneta d0070000.ethernet eth0: Using random mac address fa:89:c7:cc:ef:53
[ 70.101344][ T1] mvneta d0074000.ethernet eth1: Using random mac address d6:00:2c:8c:88:eb
[ 70.110545][ T1] usbcore: registered new interface driver smsc75xx
[ 70.117653][ T1] orion-ehci d0050000.usb: EHCI Host Controller
[ 70.124113][ T1] orion-ehci d0050000.usb: new USB bus registered, assigned bus number 1
[ 70.132610][ T1] orion-ehci d0050000.usb: irq 45, io mem 0xd0050000
[ 70.162968][ T1] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00
[ 70.169966][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.07
[ 70.179030][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 70.187041][ T1] usb usb1: Product: EHCI Host Controller
[ 70.192682][ T1] usb usb1: Manufacturer: Linux 6.7.5-mvebu-370xp-tld-3 ehci_hcd
[ 70.200344][ T1] usb usb1: SerialNumber: d0050000.usb
[ 70.206824][ T1] hub 1-0:1.0: USB hub found
[ 70.211386][ T1] hub 1-0:1.0: 1 port detected
[ 70.215767][ T695] ata2: SATA link down (SStatus 0 SControl 300)
[ 70.222404][ T1] usbcore: registered new interface driver usblp
[ 70.222583][ T690] ata1: SATA link down (SStatus 0 SControl 300)
[ 70.230506][ T1] usbcore: registered new interface driver usb-storage
[ 70.242348][ T1] mousedev: PS/2 mouse device common for all mice
[ 70.246001][ T711] ata3: SATA link down (SStatus 0 SControl F300)
[ 70.250070][ T1] i2c_dev: i2c /dev entries driver
[ 70.260494][ T1] mv64xxx_i2c d0011000.i2c: can't get pinctrl, bus recovery not supported
[ 70.273023][ T1] rtc-ds1307 0-0068: 'wakeup-source' is set, request for an IRQ is disabled!
[ 70.283615][ T1] rtc-ds1307 0-0068: registered as rtc0
[ 70.290066][ T1] rtc-ds1307 0-0068: setting system clock to 2024-03-04T11:09:00 UTC (1709550540)
[ 70.404960][ T1] orion_wdt: Initial timeout 171 sec
[ 70.411439][ T1] device-mapper: uevent: version 1.0.3
[ 70.417344][ T1] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[ 70.427079][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 70.434370][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 70.441709][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 70.449257][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 70.457425][ T1] debugfs: Directory 'cpu1' with parent 'opp' already present!
[ 70.467103][ T1] sdhci: Secure Digital Host Controller Interface driver
[ 70.474046][ T1] sdhci: Copyright(c) Pierre Ossman
[ 70.479364][ T1] sdhci-pltfm: SDHCI platform and OF driver helper
[ 70.490622][ T1] marvell-cesa d0090000.crypto: CESA device successfully registered
[ 70.498861][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 70.505699][ T1] usbcore: registered new interface driver usbhid
[ 70.512000][ T1] usbhid: USB HID core driver
[ 70.512997][ T10] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 70.518551][ T1] NET: Registered PF_INET6 protocol family
[ 70.531824][ T1] Segment Routing with IPv6
[ 70.536258][ T1] RPL Segment Routing with IPv6
[ 70.541043][ T1] In-situ OAM (IOAM) with IPv6
[ 70.545777][ T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 70.555047][ T1] NET: Registered PF_PACKET protocol family
[ 70.561135][ T1] 8021q: 802.1Q VLAN Support v1.8
[ 70.566415][ T1] Key type dns_resolver registered
[ 70.571713][ T1] ThumbEE CPU extension supported.
[ 70.576736][ T1] Registering SWP/SWPB emulation handler
[ 70.596885][ T716] ata4: SATA link down (SStatus 0 SControl F300)
[ 70.656307][ T1] registered taskstats version 1
[ 70.661254][ T1] Loading compiled-in X.509 certificates
[ 70.694762][ T1] Key type .fscrypt registered
[ 70.699414][ T1] Key type fscrypt-provisioning registered
[ 70.705274][ T1] Key type big_key registered
[ 70.730593][ T10] usb 1-1: New USB device found, idVendor=05dc, idProduct=c75c, bcdDevice= 1.02
[ 70.749336][ T10] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 70.757327][ T10] usb 1-1: Product: USB Flash Drive
[ 70.762417][ T10] usb 1-1: Manufacturer: Lexar
[ 70.767115][ T10] usb 1-1: SerialNumber: 20131017233031296A5A
[ 70.774993][ T10] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 70.783034][ T10] scsi host4: usb-storage 1-1:1.0
[ 70.870053][ T1] Key type encrypted registered
[ 70.881599][ T1] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 70.891239][ T1] clk: Disabling unused clocks
[ 70.898538][ T1] Freeing unused kernel image (initmem) memory: 1024K
[ 70.925154][ T1] Checked W+X mappings: passed, no W+X pages found
[ 70.931612][ T1] Run /init as init process
Loading, please wait...
Starting systemd-udevd version 252.19-1~deb12u1
[ 71.865173][ T25] scsi 4:0:0:0: Direct-Access Lexar USB Flash Drive 8.07 PQ: 0 ANSI: 4
[ 71.879489][ T700] sd 4:0:0:0: [sda] 15351808 512-byte logical blocks: (7.86 GB/7.32 GiB)
[ 71.891855][ T700] sd 4:0:0:0: [sda] Write Protect is off
[ 71.898378][ T700] sd 4:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 71.915283][ T700] sda: sda1
[ 71.920848][ T700] sd 4:0:0:0: [sda] Attached SCSI removable disk
[ 72.363761][ T1335] mtdblock: MTD device 'u-boot' is NAND, please consider using UBI block devices instead.
[ 72.365016][ T1334] mtdblock: MTD device 'uImage' is NAND, please consider using UBI block devices instead.
[ 72.383239][ T1339] mtdblock: MTD device 'minirootfs' is NAND, please consider using UBI block devices instead.
[ 72.386260][ T1338] mtdblock: MTD device 'u-boot-env' is NAND, please consider using UBI block devices instead.
[ 72.399453][ T1345] usbcore: registered new interface driver uas
[ 72.419784][ T1346] mtdblock: MTD device 'ubifs' is NAND, please consider using UBI block devices instead.
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Will now check root file system ... fsck from util-linux 2.38.1
[/sbin/fsck.ext3 (1) -- /dev/sda1] fsck.ext3 -a -C0 /dev/sda1
rootfs: clean, 29758/480496 files, 316298/1918720 blocks
done.
[ 83.205348][ T1369] EXT4-fs (sda1): mounting ext3 file system using the ext4 subsystem
[ 83.262757][ T1369] EXT4-fs (sda1): mounted filesystem fc59c260-6003-47cc-a825-1bf226996f9b ro with ordered data mode. Quota mode: none.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 3.06 booting
INIT: No inittab.d directory found
Using makefile-style concurrent boot in runlevel S.
Setting hostname to 'debian'...done.
Starting hotplug events dispatcher: systemd-udevd.
Synthesizing the initial hotplug events (subsystems)...done.
Synthesizing the initial hotplug events (devices)...done.
Waiting for /dev to be fully populated...[ 86.402508][ T1556] lm75 0-004c: supply vs not found, using dummy regulator
[ 86.451232][ T1561] mtdblock: MTD device 'u-boot' is NAND, please consider using UBI block devices instead.
[ 86.500751][ T1564] mtdblock: MTD device 'uImage' is NAND, please consider using UBI block devices instead.
[ 86.528783][ T1553] mtdblock: MTD device 'minirootfs' is NAND, please consider using UBI block devices instead.
[ 86.558408][ T1559] mtdblock: MTD device 'u-boot-env' is NAND, please consider using UBI block devices instead.
[ 86.595485][ T1556] hwmon hwmon4: temp1_input not attached to any thermal zone
[ 86.606247][ T1558] mtdblock: MTD device 'ubifs' is NAND, please consider using UBI block devices instead.
[ 86.663608][ T1556] lm75 0-004c: hwmon4: sensor 'g751'
[ 86.822219][ T1556] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 86.913075][ T1556] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 2
[ 86.953316][ T1556] xhci_hcd 0000:02:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000000080010
[ 87.015231][ T1556] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 87.021236][ T1556] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
[ 87.022302][ T1553] sd 4:0:0:0: Attached scsi generic sg0 type 0
[ 87.117810][ T1556] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[ 87.128851][ T1556] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.07
[ 87.138076][ T1556] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 87.183857][ T1556] usb usb2: Product: xHCI Host Controller
[ 87.232910][ T1556] usb usb2: Manufacturer: Linux 6.7.5-mvebu-370xp-tld-3 xhci-hcd
[ 87.320343][ T1556] usb usb2: SerialNumber: 0000:02:00.0
[ 87.348471][ T1556] hub 2-0:1.0: USB hub found
[ 87.358379][ T1556] hub 2-0:1.0: 2 ports detected
[ 87.384344][ T1556] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 87.415164][ T1556] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.07
[ 87.456558][ T1556] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 87.481595][ T1556] usb usb3: Product: xHCI Host Controller
[ 87.512660][ T1556] usb usb3: Manufacturer: Linux 6.7.5-mvebu-370xp-tld-3 xhci-hcd
[ 87.552086][ T1556] usb usb3: SerialNumber: 0000:02:00.0
[ 87.568166][ T1556] hub 3-0:1.0: USB hub found
[ 87.583008][ T1556] hub 3-0:1.0: 2 ports detected
done.
Activating swap:.
[ 88.526075][ T1711] EXT4-fs (sda1): re-mounted fc59c260-6003-47cc-a825-1bf226996f9b r/w. Quota mode: none.
Will now check all file systems.
Checking all file systems.
LABEL=rootfs is mounted
Done checking file systems.
Log is being saved in /var/log/fsck/checkfs if that location is writable.
Cleaning up temporary files...Cleaning /tmp...done.
/tmp.
Will now mount local filesystems:.
Will now activate swapfile swap, if any:done.
Checking minimum space in /tmp...done.
Cleaning up temporary files....
Starting Setting kernel variables: sysctl.
[ 90.682981][ C0] random: crng init done
Initializing random number generator...done.
[ 91.173080][ T2101] mvneta d0070000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
[ 91.196095][ T2101] mvneta d0070000.ethernet eth0: configuring for phy/rgmii-id link mode
Configuring network interfaces...Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/c2:90:9a:b0:fd:d6
Sending on LPF/eth0/c2:90:9a:b0:fd:d6
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 5
[ 94.343236][ T945] mvneta d0070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 9
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPOFFER of 10.11.15.78 from 10.11.15.1
DHCPREQUEST for 10.11.15.78 on eth0 to 255.255.255.255 port 67
DHCPACK of 10.11.15.78 from 10.11.15.1
bound to 10.11.15.78 -- renewal in 3040 seconds.
done.
Starting RPC port mapper daemon: rpcbind.
Starting NFS common utilities: statd idmapd.
Cleaning up temporary files....
INIT: Entering runlevel: 2
Using makefile-style concurrent boot in runlevel 2.
Not starting NFS kernel daemon: no exports ... (warning).
Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
2255 (syslogd)
.
Starting NTP server: ntpd2024-03-04T03:09:39 ntpd[2305]: INIT: ntpd ntpsec-1.2.2: Starting
2024-03-04T03:09:39 ntpd[2305]: INIT: Command line: /usr/sbin/ntpd -p /var/run/ntpd.pid -g -u 104:109
.
Starting NTP server: ntpd2024-03-04T03:09:39 ntpd[2282]: INIT: ntpd ntpsec-1.2.2: Starting
2024-03-04T03:09:39 ntpd[2282]: INIT: Command line: /usr/sbin/ntpd -p /run/ntpd.pid -c /etc/ntpsec/ntp.conf -g -N -u ntpsec:ntpsec
.
Starting periodic command scheduler: cron.
Starting system message bus: dbus.
Starting OpenBSD Secure Shell server: sshd
.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
2291 (klogd)
.
Running local boot scripts (/etc/rc.local)
[ 111.524413][ T2346] Setting Persistent MAC address to 28:C6:8E:35:86:60
<13>Mar 4 03:09:41 root[2353]: Setting Persistent MAC address to 28:C6:8E:35:86:60
Killed old client process
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/c2:90:9a:b0:fd:d6
Sending on LPF/eth0/c2:90:9a:b0:fd:d6
Sending on Socket/fallback
DHCPRELEASE of 10.11.15.78 on eth0 to 10.11.15.1 port 67
[ 113.478329][ T945] mvneta d0070000.ethernet eth0: Link is Down
Internet Systems Consortium DHCP Client 4.4.3-P1
Copyright 2004-2022 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
[ 113.600925][ T2385] mvneta d0070000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
[ 113.613641][ T2385] mvneta d0070000.ethernet eth0: configuring for phy/rgmii-id link mode
Listening on LPF/eth0/28:c6:8e:35:86:60
Sending on LPF/eth0/28:c6:8e:35:86:60
Sending on Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 6
[ 116.743198][ T23] mvneta d0070000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 15
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 18
DHCPOFFER of 10.11.15.78 from 10.11.15.1
DHCPREQUEST for 10.11.15.78 on eth0 to 255.255.255.255 port 67
DHCPACK of 10.11.15.78 from 10.11.15.1
bound to 10.11.15.78 -- renewal in 3444 seconds.
.
Debian GNU/Linux 12 debian ttyS0
debian login: root
Password:
Linux debian 6.7.5-mvebu-370xp-tld-3 #1 SMP PREEMPT Thu Feb 29 19:03:59 PST 2024 armv7l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Mon Mar 4 02:59:31 PST 2024 from 10.11.17.100 on pts/0
debian
10.11.15.78
NETGEAR ReadyNAS 2120
Linux version 6.7.5-mvebu-370xp-tld-3 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Thu Feb 29 19:03:59 PST 2024
Debian 12.4
Mon Mar 4 03:10:12 PST 2024 up 2 minutes
root@debian:~# cat /proc/cpuinfo
processor : 0
model name : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 50.00
Features : half thumb fastmult vfp edsp thumbee vfpv3 tls idiva idivt vfpd32 lpae
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x584
CPU revision : 2
processor : 1
model name : ARMv7 Processor rev 2 (v7l)
BogoMIPS : 50.00
Features : half thumb fastmult vfp edsp thumbee vfpv3 tls idiva idivt vfpd32 lpae
CPU implementer : 0x56
CPU architecture: 7
CPU variant : 0x2
CPU part : 0x584
CPU revision : 2
Hardware : Marvell Armada 370/XP (Device Tree)
Revision : 0000
Serial : 0000000000000000
root@debian:~#
|
Re: Debian on ReadyNas RN2120 March 04, 2024 05:35AM |
Registered: 9 months ago Posts: 27 |
|
Re: Debian on ReadyNas RN2120 March 04, 2024 06:05AM |
Registered: 9 months ago Posts: 27 |
I have tried the kwboot again and still no luck:
I have looked into the XMODEM transfer with a saleae logic analyser and can note two things:
1. That the baud rate does not change when setting the -B option. It always stays at 115200
2. The transfer appears to be going fine. Lots of ACKs from the RN2120 for the first ~100 blocks then the RN2120 pulls its TX pin low mid byte (and mid block) and doesn't respond after that. No errors or NAKS from the RN2120.
I have attached the capture here if it is useful. It can be opened with the saleae logic "Logic 2" software.
pi@poepi:~$ ./kwboot_static -a -b mtd0.rn2120 -t /dev/ttyAMA4 -p kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v1 with NAND boot signature Patching image boot signature to UART Sending boot message. Please reboot the target...\ Sending boot image header (112640 bytes)... 0 % [......................................................................] 8 % [........................................E
I have looked into the XMODEM transfer with a saleae logic analyser and can note two things:
1. That the baud rate does not change when setting the -B option. It always stays at 115200
2. The transfer appears to be going fine. Lots of ACKs from the RN2120 for the first ~100 blocks then the RN2120 pulls its TX pin low mid byte (and mid block) and doesn't respond after that. No errors or NAKS from the RN2120.
I have attached the capture here if it is useful. It can be opened with the saleae logic "Logic 2" software.
|
Re: Debian on ReadyNas RN2120 March 04, 2024 02:09PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
> Looks good! cpuinfo reports two processors now.
Nice!
> However what ever is causing
>
>
> Is still present.
I'm not sure what's going on with this yet.
Usually the PCIe bus in these NAS are used for the 2nd and 3rd SATA. Have you tried booting with any SATA drive in each slot?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Looks good! cpuinfo reports two processors now.
Nice!
> However what ever is causing
>
>
> pci 0000:00:01.0: not ready after 65535ms; giving > up >>
> Is still present.
I'm not sure what's going on with this yet.
Usually the PCIe bus in these NAS are used for the 2nd and 3rd SATA. Have you tried booting with any SATA drive in each slot?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 04, 2024 02:29PM |
Admin Registered: 13 years ago Posts: 19,102 |
> 1. That the baud rate does not change when setting
> the -B option. It always stays at 115200
It is OK. The baudrate is whatever the Marvell BootROM uses, and it is 115200.
> 2. The transfer appears to be going fine. Lots of
> ACKs from the RN2120 for the first ~100 blocks
> then the RN2120 pulls its TX pin low mid byte (and
> mid block) and doesn't respond after that. No
> errors or NAKS from the RN2120.
Sounds like we are seeing a BootROM bug.
Could you try -s option (don't use -a) and just pick some random number. From the current default = 10 going up.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> the -B option. It always stays at 115200
It is OK. The baudrate is whatever the Marvell BootROM uses, and it is 115200.
> 2. The transfer appears to be going fine. Lots of
> ACKs from the RN2120 for the first ~100 blocks
> then the RN2120 pulls its TX pin low mid byte (and
> mid block) and doesn't respond after that. No
> errors or NAKS from the RN2120.
Sounds like we are seeing a BootROM bug.
Could you try -s option (don't use -a) and just pick some random number. From the current default = 10 going up.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 04, 2024 03:50PM |
Admin Registered: 13 years ago Posts: 19,102 |
Since we can't kwboot this box yet, I will write the instruction to create and run a boot script. This will save time executing these setenvs commands.
I'm sure by now it has become too tedious to mannual copy/paste these commands to the prompt :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/04/2024 03:59PM by bodhi.
I'm sure by now it has become too tedious to mannual copy/paste these commands to the prompt :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/04/2024 03:59PM by bodhi.
|
Re: Debian on ReadyNas RN2120 March 04, 2024 10:44PM |
Admin Registered: 13 years ago Posts: 19,102 |
How to create a u-boot boot script on USB rootfs
Often time, when booting with stock u-boot, or during testing, we'd want to have a way to excute several commands at the prompt. The script can be run at the u-boot prompt interactively, or saved to an existing env so that it always run during boot (be extra careful with saving envs, some stock u-boot will corrupt the envs when you do that). During testing, never save the envs if you don't know how stock u-boot behave. Of course, if you can kwboot the box with a backup u-boot image then the risk is minimal.
Note that the script load address used in Step3 is 0x02000000 for RN2120 board. It is for convenience to use the same load address for the uImage. On other other boards, a different load address might need to be used.
1. Create the boot file boot.cmd in rootfs /boot. This file contains the setenv commands to boot this box.
For example, to boot the RN2120 box with stock u-boot, the current setenvs are:
The /boot/boot.cmd file should contain the above commands.
2. Create the boot script boot.scr
3. Power up (or reboot). At u-boot prompt, copy and paste the following command:
So from now on, you need only 1 command to copy and paste to the u-boot prompt.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/05/2024 09:12PM by bodhi.
Often time, when booting with stock u-boot, or during testing, we'd want to have a way to excute several commands at the prompt. The script can be run at the u-boot prompt interactively, or saved to an existing env so that it always run during boot (be extra careful with saving envs, some stock u-boot will corrupt the envs when you do that). During testing, never save the envs if you don't know how stock u-boot behave. Of course, if you can kwboot the box with a backup u-boot image then the risk is minimal.
Note that the script load address used in Step3 is 0x02000000 for RN2120 board. It is for convenience to use the same load address for the uImage. On other other boards, a different load address might need to be used.
1. Create the boot file boot.cmd in rootfs /boot. This file contains the setenv commands to boot this box.
For example, to boot the RN2120 box with stock u-boot, the current setenvs are:
setenv bootdev usb setenv device 0:1 setenv load_image_addr 0x02000000 setenv load_initrd_addr 0x3000000 setenv load_image 'echo loading uImage ...; ext2load $bootdev $device $load_image_addr /boot/uImage' setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd' setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial"' setenv bootcmd_exec 'echo Booting Debian from $bootdev; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_initrd; bootm $load_image_addr $load_initrd_addr' setenv bootcmd_custom_usb 'usb start; run set_bootargs; run bootcmd_exec' setenv bootcmd 'run bootcmd_custom_usb' setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)' setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"'
The /boot/boot.cmd file should contain the above commands.
2. Create the boot script boot.scr
cd /boot mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Boot Script" -d boot.cmd boot.scr sync
3. Power up (or reboot). At u-boot prompt, copy and paste the following command:
usb start; ext2load usb 0:1 0x02000000 /boot/boot.scr; source 0x02000000; bootYou could also run a command to load and verify the envs were set correctly, and then boot:
usb start; ext2load usb 0:1 0x02000000 /boot/boot.scr; source 0x02000000; printenv boot
So from now on, you need only 1 command to copy and paste to the u-boot prompt.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/05/2024 09:12PM by bodhi.
|
Re: Debian on ReadyNas RN2120 March 05, 2024 02:17PM |
Registered: 9 months ago Posts: 27 |
Ah! Success on the kwboot. I found another thread : https://forum.doozan.com/read.php?3,95249 and it seems the power button needs to be pressed and held down during the first stage (bootloader?) upload. I was able to successfully boot using mtd0.rn2120 backup file. Interestingly it worked fine without the -a flag. I also managed to build kwboot from source but I doubt that helped.
root@poepi:/home/pi/u-boot# tools/kwboot -b ../mtd0.rn2120 -t /dev/ttyAMA4
TEST kwboot version 2024.04-rc3-00004-gabd4fb5ac1-dirty
Detected kwbimage v1 with NAND boot signature
Patching image boot signature to UART
Sending boot message. Please reboot the target.../
Sending boot image header (112640 bytes)...
0 % [......................................................................]
8 % [......................................................................]
16 % [......................................................................]
23 % [......................................................................]
31 % [......................................................................]
39 % [......................................................................]
47 % [......................................................................]
55 % [......................................................................]
63 % [......................................................................]
71 % [......................................................................]
79 % [......................................................................]
87 % [......................................................................]
95 % [.......................................A ]
Done
General initialization - Version: 1.0.0
High speed PHY - Version: 2.1.8 (COM-PHY-V22)
Update Device ID PEX0782311AB
Update Device ID PEX1782311AB
Update Device ID PEX2782311AB
Update Device ID PEX3782311AB
Update Device ID PEX4782311AB
Update Device ID PEX5782311AB
Update Device ID PEX6782311AB
Update PEX Device ID 0x78230
High speed PHY - Ended Successfully
DDR3 Training Sequence - Ver 5.7.1
DDR3 Training Sequence - Run with PBS.
DDR3 Training Sequence - Ended Successfully
Sending boot image data (882472 bytes)...
0 % [......................................................................]
1 % [......................................................................]
2 % [......................................................................]
3 % [......................................................................]
4 % [......................................................................]
5 % [......................................................................]
6 % [......................................................................]
7 % [......................................................................]
8 % [......................................................................]
9 % [......................................................................]
10 % [......................................................................]
11 % [......................................................................]
12 % [......................................................................]
13 % [......................................................................]
14 % [......................................................................]
15 % [......................................................................]
16 % [......................................................................]
17 % [......................................................................]
18 % [......................................................................]
19 % [......................................................................]
20 % [......................................................................]
21 % [......................................................................]
22 % [......................................................................]
23 % [......................................................................]
24 % [......................................................................]
25 % [......................................................................]
26 % [......................................................................]
27 % [......................................................................]
28 % [......................................................................]
29 % [......................................................................]
30 % [......................................................................]
31 % [......................................................................]
32 % [......................................................................]
33 % [......................................................................]
34 % [......................................................................]
35 % [......................................................................]
36 % [......................................................................]
37 % [......................................................................]
38 % [......................................................................]
39 % [......................................................................]
40 % [......................................................................]
41 % [......................................................................]
42 % [......................................................................]
43 % [......................................................................]
44 % [......................................................................]
45 % [......................................................................]
46 % [......................................................................]
47 % [......................................................................]
48 % [......................................................................]
49 % [......................................................................]
50 % [......................................................................]
51 % [......................................................................]
52 % [......................................................................]
53 % [......................................................................]
54 % [......................................................................]
55 % [......................................................................]
56 % [......................................................................]
57 % [......................................................................]
58 % [......................................................................]
59 % [......................................................................]
60 % [......................................................................]
61 % [......................................................................]
62 % [......................................................................]
63 % [......................................................................]
64 % [......................................................................]
66 % [......................................................................]
67 % [......................................................................]
68 % [......................................................................]
69 % [......................................................................]
70 % [......................................................................]
71 % [......................................................................]
72 % [......................................................................]
73 % [......................................................................]
74 % [......................................................................]
75 % [......................................................................]
76 % [......................................................................]
77 % [......................................................................]
78 % [......................................................................]
79 % [......................................................................]
80 % [......................................................................]
81 % [......................................................................]
82 % [......................................................................]
83 % [......................................................................]
84 % [......................................................................]
85 % [......................................................................]
86 % [......................................................................]
87 % [......................................................................]
88 % [......................................................................]
89 % [......................................................................]
90 % [......................................................................]
91 % [......................................................................]
92 % [......................................................................]
93 % [......................................................................]
94 % [......................................................................]
95 % [......................................................................]
96 % [......................................................................]
97 % [......................................................................]
98 % [......................................................................]
99 % [................................... ]
Done
Finishing transfer
[Type Ctrl-\ + c to quit]
__ __ _ _
| \/ | __ _ _ ____ _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| | | | (_| | | \ V / __/ | |
|_| |_|\__,_|_| \_/ \___|_|_|
_ _ ____ _
| | | | | __ ) ___ ___ | |_
| | | |___| _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
\___/ |____/ \___/ \___/ \__|
** LOADER **
U-Boot 2011.12-gd923454 (Sep 08 2015 - 18:59:32) Marvell version: v2011.12 2014_T2.0p1
Netgear version: 09/08/2015 ReadyNAS-2120 v2.0
Board: DB-78460-BP rev 2.0
SoC: MV78230 B0
running 2 CPUs
Custom configuration
CPU: Marvell PJ4B (584) v7 (Rev 2) LE
CPU 0
CPU @ 1200 [MHz]
L2 @ 600 [MHz]
TClock @ 250 [MHz]
DDR @ 600 [MHz]
DDR 32Bit Width, FastPath Memory Access
DDR ECC Disabled
DRAM: 2 GiB
▒
Map: Code: 0x7fedf000:0x7ff9f204
BSS: 0x7ffefc20
Stack: 0x7f9deef8
Heap: 0x7f9df000:0x7fedf000
NAND: 128 MiB
MMC: MRVL_MMC: 0
Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01
nand_read_bbt: Bad block at 0x000005de0000
nand_read_bbt: Bad block at 0x000005e00000
Initialize and scan all PCI interfaces
PEX unit.port(active IF[-first bus]):
------------------------------------------
PEX 0.0(0-0): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 0.1(1-1): Root Complex Interface, Detected Link X1, GEN 2.0
PEX 1.0(2-2): Root Complex Interface, Detected Link X1, GEN 2.0
FPU initialized to Run Fast Mode.
USB 0: Host Mode
USB 1: Host Mode
USB 2: Host Mode
Modules Detected:
Net: egiga0, egiga1 [PRIME]
Power On!
FDT loaded successfully
Found 2 disks present
Hit any key to stop autoboot: 0
NAND read: device 0 offset 0x200000, size 0x400000
4194304 bytes read: OK
NAND read: device 0 offset 0x800000, size 0x400000
4194304 bytes read: OK
## Booting kernel from Legacy Image at 02000000 ...
Image Name: Linux-4.4.218.armada.1
Created: 2023-06-28 22:22:10 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3477992 Bytes = 3.3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 03000000 ...
Image Name: initramfs
Created: 2024-01-10 5:26:30 UTC
Image Type: ARM Linux RAMDisk Image (lzma compressed)
Data Size: 3427797 Bytes = 3.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01000000
Booting using the fdt blob at 0x01000000
Loading Kernel Image ... OK
Using Ramdisk in place at 03000040, end 03344e15
Using Device Tree in place at 01000000, end 01007542
Updating device tree successful
Starting kernel ...
Starting the boot process...
Detected system type: RN2120
Loading kernel modules...done
Boot mode: Normal
UBI device number 0, total 918 LEBs (116563968 bytes, 111.2 MiB), available 9 LEBs (1142784 bytes, 1.1 MiB), LEB size 126976 bytes (124.0 KiB)
Bringing up network...done
Bringing up RAID arrays...done
e2fsck 1.42.13 (17-May-2015)
0e358660_root: recovering journal
0e358660_root: clean, 13396/1048576 files, 213834/1047552 blocks
Switching root to RAID device.
Welcome to ReadyNASOS 6.10.10!
[ OK ] Listening on Journal Socket (/dev/log).
[ OK ] Listening on udev Kernel Socket.
[ OK ] Created slice User and Session Slice.
[ OK ] Reached target Encrypted Volumes.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
|
Re: Debian on ReadyNas RN2120 March 05, 2024 02:44PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
> Ah! Success on the kwboot. I found another thread
> : https://forum.doozan.com/read.php?3,95249 and it
> seems the power button needs to be pressed and
> held down during the first stage (bootloader?)
> upload. I was able to successfully boot using
> mtd0.rn2120 backup file. Interestingly it worked
> fine without the -a flag. I also managed to build
> kwboot from source but I doubt that helped.
Congrats! could you do a kwboot run with my built kwboot static version. This is to make sure that it could be recommended to others.
I will attach a tweak mtd0 to be used as rescue version in the next post.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Ah! Success on the kwboot. I found another thread
> : https://forum.doozan.com/read.php?3,95249 and it
> seems the power button needs to be pressed and
> held down during the first stage (bootloader?)
> upload. I was able to successfully boot using
> mtd0.rn2120 backup file. Interestingly it worked
> fine without the -a flag. I also managed to build
> kwboot from source but I doubt that helped.
Congrats! could you do a kwboot run with my built kwboot static version. This is to make sure that it could be recommended to others.
I will attach a tweak mtd0 to be used as rescue version in the next post.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 05, 2024 02:52PM |
Admin Registered: 13 years ago Posts: 19,102 |
Netgear RN2120 Rescue u-boot
The Synology DS414 u-boot can be used as a rescue u-boot. Please see this thread to download uboot.2024.04-rc3-tld-1.ds414.kwb:
https://forum.doozan.com/read.php?2,136786,136855#msg-136855
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 03/07/2024 04:21PM by bodhi.
The Synology DS414 u-boot can be used as a rescue u-boot. Please see this thread to download uboot.2024.04-rc3-tld-1.ds414.kwb:
https://forum.doozan.com/read.php?2,136786,136855#msg-136855
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 03/07/2024 04:21PM by bodhi.
|
Re: Debian on ReadyNas RN2120 March 05, 2024 06:14PM |
Registered: 9 months ago Posts: 27 |
bodhi Wrote:
-------------------------------------------------------
> Congrats! could you do a kwboot run with my built
> kwboot static version. This is to make sure that
> it could be recommended to others.
>
I can confirm the static built kwboot also works:
-------------------------------------------------------
> Congrats! could you do a kwboot run with my built
> kwboot static version. This is to make sure that
> it could be recommended to others.
>
I can confirm the static built kwboot also works:
root@poepi:/home/pi# ./kwboot_static -b mtd0.rn2120 -t /dev/ttyUSB0 kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v1 with NAND boot signature Patching image boot signature to UART Sending boot message. Please reboot the target...\ Sending boot image header (112640 bytes)... 0 % [......................................................................] 8 % [......................................................................] 16 % [......................................................................] 23 % [......................................................................] 31 % [......................................................................] 39 % [......................................................................] 47 % [......................................................................] 55 % [......................................................................] 63 % [......................................................................] 71 % [......................................................................] 79 % [......................................................................] 87 % [......................................................................] 95 % [........................................ ] Done General initialization - Version: 1.0.0 High speed PHY - Version: 2.1.8 (COM-PHY-V22) Update Device ID PEX0782311AB Update Device ID PEX1782311AB Update Device ID PEX2782311AB Update Device ID PEX3782311AB Update Device ID PEX4782311AB Update Device ID PEX5782311AB Update Device ID PEX6782311AB Update PEX Device ID 0x78230 High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 5.7.1 DDR3 Training Sequence - Run with PBS. DDR3 Training Sequence - Ended Successfully
|
Re: Debian on ReadyNas RN2120 March 05, 2024 06:41PM |
Registered: 9 months ago Posts: 27 |
I tried the script to boot the device into debian with just a single line and it works well. There is a typo in your instructions: boot.scr / uboot.scr but otherwise very clear, thank you.
You are correct with the pci 0000:00:01.0 issue, I seem to only have 2 / 4 drive bays working (they all function in the default OS)
You are correct with the pci 0000:00:01.0 issue, I seem to only have 2 / 4 drive bays working (they all function in the default OS)
|
Re: Debian on ReadyNas RN2120 March 05, 2024 11:55PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon ,
bodhi Wrote:
-------------------------------------------------------
> Netgear RN2120 Rescue u-boot
>
> This u-boot image uboot.rn2120.rescue.img can be
> used in kwboot the box. As spiderdijon has found
> in
> the
> above post, the power button must be pushed
> and hold at the start of kwboot to make it
> successful.
>
> Warning: this u-boot image cannot
> be flashed to NAND. It should only be used in
> kwboot to unbrick the box
>
> uboot.rn2120.rescue.img.tar.bz2
>
I'd like to see this working, too.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
bodhi Wrote:
-------------------------------------------------------
> Netgear RN2120 Rescue u-boot
>
> This u-boot image uboot.rn2120.rescue.img can be
> used in kwboot the box. As spiderdijon has found
> in
> the
> above post, the power button must be pushed
> and hold at the start of kwboot to make it
> successful.
>
> Warning: this u-boot image cannot
> be flashed to NAND. It should only be used in
> kwboot to unbrick the box
>
> uboot.rn2120.rescue.img.tar.bz2
>
> md5: > 3da67813e1369d1d55120cd8a23b7368 > uboot.rn2120.rescue.img.tar.bz2 > sha256: > f5f31f25df7fbf979680a0850c0f5cb532c8aa40ef108d44593400e5fc3174ba > uboot.rn2120.rescue.img.tar.bz2 >
I'd like to see this working, too.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 06, 2024 03:28AM |
Registered: 9 months ago Posts: 27 |
I assumed I would kwboot the uboot.rn2120.rescue.img file is that correct? If so it did not work:
root@poepi:/home/pi# ./kwboot_static -b uboot.rn2120.rescue.img -t /dev/ttyUSB0 kwboot version 2024.04-rc3-00001-g0861eab8ec-dirty Detected kwbimage v1 with NAND boot signature Image has invalid data checksum uboot.rn2120.rescue.img: Invalid image. root@poepi:/home/pi# md5sum uboot.rn2120.rescue.img 5e5af21ba1614fe979d697b3c3602e97 uboot.rn2120.rescue.img root@poepi:/home/pi# md5sum uboot.rn2120.rescue.img.tar.bz2 3da67813e1369d1d55120cd8a23b7368 uboot.rn2120.rescue.img.tar.bz2
|
Re: Debian on ReadyNas RN2120 March 06, 2024 01:34PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
> Image has invalid data checksum
> uboot.rn2120.rescue.img: Invalid image.
Strange, I would expect to see this with a much older kwboot. I'll double check.
In the meantime, please kwboot with the ds4141 u-boot that I uploaded before. As long as it starts running, then we're almost done.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Image has invalid data checksum
> uboot.rn2120.rescue.img: Invalid image.
Strange, I would expect to see this with a much older kwboot. I'll double check.
In the meantime, please kwboot with the ds4141 u-boot that I uploaded before. As long as it starts running, then we're almost done.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 06, 2024 08:19PM |
Admin Registered: 13 years ago Posts: 19,102 |
> > Image has invalid data checksum
> > uboot.rn2120.rescue.img: Invalid image.
>
> Strange, I would expect to see this with a much
> older kwboot. I'll double check.
>
OK. I can see why it did not work.
> In the meantime, please kwboot with the ds4141
> u-boot that I uploaded before. As long as it
> starts running, then we're almost done.
I'd like to see the ds414 u-boot image started by the BootROM (to prove that it really runs the image transfered over by kwboot).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> > uboot.rn2120.rescue.img: Invalid image.
>
> Strange, I would expect to see this with a much
> older kwboot. I'll double check.
>
OK. I can see why it did not work.
> In the meantime, please kwboot with the ds4141
> u-boot that I uploaded before. As long as it
> starts running, then we're almost done.
I'd like to see the ds414 u-boot image started by the BootROM (to prove that it really runs the image transfered over by kwboot).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 07, 2024 05:21AM |
Registered: 9 months ago Posts: 27 |
It appears to boot the uboot but is missing loading env variables from SPI flash. With ID bytes of 0xFF 0xFF 0xFF it's likely it's actually not accessing anything at all. Is this because there is no SPI NOR Flash on this device? It looks like it uses NAND flash instead? I guess the purpose of this test was just to see if it got this far as it's for a different device and it did!
Edited 2 time(s). Last edit at 03/07/2024 09:39AM by spiderdijon.
root@ubuntu:/home/spiderdijon# kwboot -a -b Downloads/uboot.2024.04-rc3-tld-1.ds414.kwb -t /dev/ttyUSB0 kwboot version 2022.01+dfsg-2ubuntu2.5 Patching image boot signature to UART Aligning image header to Xmodem block size Sending boot message. Please reboot the target...- ^[[C Waiting 2s and flushing tty Sending boot image header (86272 bytes)... 0 % [......................................................................] 10 % [......................................................................] 20 % [......................................................................] 31 % [......................................................................] 41 % [......................................................................] 52 % [......................................................................] 62 % [......................................................................] 72 % [......................................................................] 83 % [......................................................................] 93 % [............................................ ] Done U-Boot SPL 2024.04-rc3-tld-1-00001-g0861eab8ec-dirty (Feb 27 2024 - 16:41:40 -0800) High speed PHY - Version: 2.1.5 (COM-PHY-V20) High speed PHY - Ended Successfully DDR3 Training Sequence - Ver 5.7.4 DDR3 Training Sequence - Ended Successfully Trying to boot from BOOTROM Returning to BootROM (return address 0xffff0aa0)... Sending boot image data (717764 bytes)... 0 % [......................................................................] 1 % [......................................................................] 2 % [......................................................................] 3 % [......................................................................] 5 % [......................................................................] 6 % [......................................................................] 7 % [......................................................................] 8 % [......................................................................] 10 % [......................................................................] 11 % [......................................................................] 12 % [......................................................................] 13 % [......................................................................] 14 % [......................................................................] 16 % [......................................................................] 17 % [......................................................................] 18 % [......................................................................] 19 % [......................................................................] 21 % [......................................................................] 22 % [......................................................................] 23 % [......................................................................] 24 % [......................................................................] 26 % [......................................................................] 27 % [......................................................................] 28 % [......................................................................] 29 % [......................................................................] 31 % [......................................................................] 32 % [......................................................................] 33 % [......................................................................] 34 % [......................................................................] 36 % [......................................................................] 37 % [......................................................................] 38 % [......................................................................] 39 % [......................................................................] 41 % [......................................................................] 42 % [......................................................................] 43 % [......................................................................] 44 % [......................................................................] 46 % [......................................................................] 47 % [......................................................................] 48 % [......................................................................] 49 % [......................................................................] 51 % [......................................................................] 52 % [......................................................................] 53 % [......................................................................] 54 % [......................................................................] 56 % [......................................................................] 57 % [......................................................................] 58 % [......................................................................] 59 % [......................................................................] 61 % [......................................................................] 62 % [......................................................................] 63 % [......................................................................] 64 % [......................................................................] 66 % [......................................................................] 67 % [......................................................................] 68 % [......................................................................] 69 % [......................................................................] 71 % [......................................................................] 72 % [......................................................................] 73 % [......................................................................] 74 % [......................................................................] 76 % [......................................................................] 77 % [......................................................................] 78 % [......................................................................] 79 % [......................................................................] 81 % [......................................................................] 82 % [......................................................................] 83 % [......................................................................] 84 % [......................................................................] 86 % [......................................................................] 87 % [......................................................................] 88 % [......................................................................] 89 % [......................................................................] 91 % [......................................................................] 92 % [......................................................................] 93 % [......................................................................] 94 % [......................................................................] 96 % [......................................................................] 97 % [......................................................................] 98 % [......................................................................] 99 % [........ ] Done Finishing transfer [Type Ctrl-\ + c to quit] U-Boot 2024.04-rc3-tld-1-00001-g0861eab8ec-dirty (Feb 27 2024 - 16:41:40 -0800) SoC: MV78230-B0 at 1200 MHz DRAM: 1 GiB (600 MHz, 32-bit, ECC not enabled) Core: 25 devices, 17 uclasses, devicetree: separate Loading Environment from SPIFlash... jedec_spi_nor spi-flash@0: unrecognized JEDEC id bytes: ff, ff, ff *** Warning - spi_flash_probe_bus_cs() failed, using default environment In: serial@12000 Out: serial@12000 Err: serial@12000 Model: Synology DS414 Board: DS414 Incomplete environment, populating from SPI flash jedec_spi_nor spi-flash@0: unrecognized JEDEC id bytes: ff, ff, ff Failed to initialize SPI flash at 0:0 Net: Error: ethernet@70000 No valid MAC address found. Error: ethernet@74000 No valid MAC address found. No ethernet found. Hit any key to stop autoboot: 0 jedec_spi_nor spi-flash@0: unrecognized JEDEC id bytes: ff, ff, ff Failed to initialize SPI flash at 0:0 (error 0) No SPI flash selected. Please run `sf probe' No SPI flash selected. Please run `sf probe' Wrong Image Type for bootm command ERROR -91: can't get kernel image! =>
Edited 2 time(s). Last edit at 03/07/2024 09:39AM by spiderdijon.
|
Re: Debian on ReadyNas RN2120 March 07, 2024 02:38PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
> It appears to boot the uboot but is missing
> loading env variables from SPI flash. With ID
> bytes of 0xFF 0xFF 0xFF it's likely it's actually
> not accessing anything at all. Is this because
> there is no SPI NOR Flash on this device?
> It looks
> like it uses NAND flash instead?
Correct, there is no SPI flash. This box uses NAND flash.
> I guess the
> purpose of this test was just to see if it got
> this far as it's for a different device and it
> did!
There are 2 purposes. Yes, the whole idea is to see the loaded u-boot mage actually runs. In previous test, we use the stock mdt0, and it was loaded and run OK. But there is no way to tell if it was not the u-boot in NAND that was used, since both are identical.
And like you said, good to see we can use the DS414 u-boot to rescue this box when needed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> It appears to boot the uboot but is missing
> loading env variables from SPI flash. With ID
> bytes of 0xFF 0xFF 0xFF it's likely it's actually
> not accessing anything at all. Is this because
> there is no SPI NOR Flash on this device?
> It looks
> like it uses NAND flash instead?
Correct, there is no SPI flash. This box uses NAND flash.
> I guess the
> purpose of this test was just to see if it got
> this far as it's for a different device and it
> did!
There are 2 purposes. Yes, the whole idea is to see the loaded u-boot mage actually runs. In previous test, we use the stock mdt0, and it was loaded and run OK. But there is no way to tell if it was not the u-boot in NAND that was used, since both are identical.
And like you said, good to see we can use the DS414 u-boot to rescue this box when needed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 07, 2024 04:31PM |
Admin Registered: 13 years ago Posts: 19,102 |
Dual boot Debian and stock OS on Netgear RN2120
Currently the RN2120 can be booted into Debian with the following envs:
So we want to set up the dual boot to enable booting to either system.
At u-boot prompt, change the bootcmd env, and add 2 more envs:
Now if the Debian USB rootfs is not attached, it will boot into stock OS. If the Debian USB rootfs is attached, it will boot into Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/07/2024 04:35PM by bodhi.
Currently the RN2120 can be booted into Debian with the following envs:
setenv bootdev usb setenv device 0:1 setenv load_image_addr 0x02000000 setenv load_initrd_addr 0x3000000 setenv load_image 'echo loading uImage ...; ext2load $bootdev $device $load_image_addr /boot/uImage' setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd' setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial"' setenv bootcmd_exec 'echo Booting Debian from $bootdev; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_initrd; bootm $load_image_addr $load_initrd_addr' setenv bootcmd_custom_usb 'usb start; run set_bootargs; run bootcmd_exec' setenv bootcmd 'run bootcmd_custom_usb' setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)' setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"'
So we want to set up the dual boot to enable booting to either system.
At u-boot prompt, change the bootcmd env, and add 2 more envs:
setenv bootcmd 'run bootcmd_custom_usb; run bootcmd_stock; reset' setenv set_bootargs_stock 'console=ttyS0,115200 pm_disable=yes mv_cpu_count=2' setenv bootcmd_stock 'echo Booting Stock; run set_bootargs_stock; nand read 0x2000000 0x200000 0x400000; nand read 0x3000000 0x800000 0x400000; bootm 0x2000000 0x3000000 0x1000000'And then,
boot
Now if the Debian USB rootfs is not attached, it will boot into stock OS. If the Debian USB rootfs is attached, it will boot into Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/07/2024 04:35PM by bodhi.
|
Re: Debian on ReadyNas RN2120 March 08, 2024 03:34AM |
Registered: 9 months ago Posts: 27 |
|
Re: Debian on ReadyNas RN2120 March 08, 2024 05:33AM |
Registered: 9 months ago Posts: 27 |
I have also been doing further research on the PCI issue and the missing Marvell 88SE9170 SATA Controller.
I installed hwinfo to get a better view:
What it looks like currently is that the "not ready" PCI device is a PCI bridge in the SoC:
uboot can see both controllers. I have 3 disks installed and uboot prints:
Explicitly scanning the pci busses in uboot confirms this:
uboot is also using a generic dtb file apparently for the armada xp dev board, not sure if that is an issue?
I wonder if there is a way to reset the pci-e bridge early on in the boot? Or conversely if it is being reset then maybe don't reset it? Asking to rescan the pci bus in debian results in the same not ready messages:
and dmesg:
Edited 5 time(s). Last edit at 03/08/2024 06:04AM by spiderdijon.
root@debian:~# lspci 00:02.0 PCI bridge: Marvell Technology Group Ltd. MV78230 [Armada XP] ARM SoC (rev 02) 00:05.0 PCI bridge: Marvell Technology Group Ltd. MV78230 [Armada XP] ARM SoC (rev 02) 01:00.0 SATA controller: Marvell Technology Group Ltd. 88SE9170 PCIe 2.0 x1 2-port SATA 6 Gb/s Controller (rev 12) 02:00.0 USB controller: Fresco Logic FL1009 USB 3.0 Host Controller (rev 02)
I installed hwinfo to get a better view:
root@debian:~# hwinfo --pci
02: PCI 02.0: 0604 PCI bridge (Normal decode)
[Created at pci.386]
Unique ID: _Znp.NpKyVLv59K9
SysFS ID: /devices/platform/soc/soc:pcie@82000000/pci0000:00/0000:00:02.0
SysFS BusID: 0000:00:02.0
Hardware Class: bridge
Model: "Marvell MV78230 [Armada XP] ARM SoC"
Vendor: pci 0x11ab "Marvell Technology Group Ltd."
Device: pci 0x7823 "MV78230 [Armada XP] ARM SoC"
SubVendor: pci 0x11ab "Marvell Technology Group Ltd."
SubDevice: pci 0x11ab
Revision: 0x02
Module Alias: "pci:v000011ABd00007823sv000011ABsd000011ABbc06sc04i00"
Config Status: cfg=new, avail=yes, need=no, active=unknown
03: PCI 05.0: 0604 PCI bridge (Normal decode)
[Created at pci.386]
Unique ID: CvwD.NpKyVLv59K9
SysFS ID: /devices/platform/soc/soc:pcie@82000000/pci0000:00/0000:00:05.0
SysFS BusID: 0000:00:05.0
Hardware Class: bridge
Model: "Marvell MV78230 [Armada XP] ARM SoC"
Vendor: pci 0x11ab "Marvell Technology Group Ltd."
Device: pci 0x7823 "MV78230 [Armada XP] ARM SoC"
SubVendor: pci 0x11ab "Marvell Technology Group Ltd."
SubDevice: pci 0x11ab
Revision: 0x02
Module Alias: "pci:v000011ABd00007823sv000011ABsd000011ABbc06sc04i00"
Config Status: cfg=new, avail=yes, need=no, active=unknown
04: PCI 200.0: 0c03 USB Controller (XHCI)
[Created at pci.386]
Unique ID: B35A.g6ex55Kr1b9
Parent ID: CvwD.NpKyVLv59K9
SysFS ID: /devices/platform/soc/soc:pcie@82000000/pci0000:00/0000:00:05.0/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: usb controller
Model: "Fresco Logic FL1009 USB 3.0 Host Controller"
Vendor: pci 0x1b73 "Fresco Logic"
Device: pci 0x1009 "FL1009 USB 3.0 Host Controller"
SubVendor: pci 0x1b73 "Fresco Logic"
SubDevice: pci 0x0000
Revision: 0x02
Driver: "xhci_hcd"
Driver Modules: "xhci_pci"
Memory Range: 0xf8100000-0xf810ffff (rw,non-prefetchable)
Memory Range: 0xf8110000-0xf8110fff (rw,non-prefetchable)
Memory Range: 0xf8111000-0xf8111fff (rw,non-prefetchable)
IRQ: 53 (no events)
Module Alias: "pci:v00001B73d00001009sv00001B73sd00000000bc0Csc03i30"
Driver Info #0:
Driver Status: xhci_pci is active
Driver Activation Cmd: "modprobe xhci_pci"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #3 (PCI bridge)
05: PCI 100.0: 0106 SATA controller (AHCI 1.0)
[Created at pci.386]
Unique ID: VCu0.ijp247hmZmD
Parent ID: _Znp.NpKyVLv59K9
SysFS ID: /devices/platform/soc/soc:pcie@82000000/pci0000:00/0000:00:02.0/0000:01:00.0
SysFS BusID: 0000:01:00.0
Hardware Class: storage
Model: "Marvell SATA controller"
Vendor: pci 0x1b4b "Marvell Technology Group Ltd."
Device: pci 0x9170
SubVendor: pci 0x1b4b "Marvell Technology Group Ltd."
SubDevice: pci 0x9170
Revision: 0x12
Driver: "ahci"
I/O Ports: 0x10010-0x10017 (rw)
I/O Ports: 0x10020-0x10023 (rw)
I/O Ports: 0x10018-0x1001f (rw)
I/O Ports: 0x10024-0x10027 (rw)
I/O Ports: 0x10000-0x10fff (rw)
Memory Range: 0xf8010000-0xf80101ff (rw,non-prefetchable)
Memory Range: 0xf8000000-0xf800ffff (ro,non-prefetchable,disabled)
IRQ: 40 (362 events)
Module Alias: "pci:v00001B4Bd00009170sv00001B4Bsd00009170bc01sc06i01"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #2 (PCI bridge)
root@debian:~#
What it looks like currently is that the "not ready" PCI device is a PCI bridge in the SoC:
[ 3.332969][ T1] pci 0000:00:01.0: not ready after 1023ms; waiting <--- PCI bridge for the First 88SE9170 [ 4.422965][ T1] pci 0000:00:01.0: not ready after 2047ms; waiting [ 6.502945][ T1] pci 0000:00:01.0: not ready after 4095ms; waiting [ 10.662938][ T1] pci 0000:00:01.0: not ready after 8191ms; waiting [ 19.062946][ T1] pci 0000:00:01.0: not ready after 16383ms; waiting [ 35.702938][ T1] pci 0000:00:01.0: not ready after 32767ms; waiting [ 68.982945][ T1] pci 0000:00:01.0: not ready after 65535ms; giving up [ 68.989777][ T1] pci 0000:00:02.0: [11ab:7823] type 01 class 0x060400 <--- PCI Bridge for USB 3.0 controller [ 68.997369][ T1] pci 0000:00:05.0: [11ab:7823] type 01 class 0x060400 <--- PCI bridge for Second 88SE9170
uboot can see both controllers. I have 3 disks installed and uboot prints:
Initialize and scan all PCI interfaces PEX unit.port(active IF[-first bus]): ------------------------------------------ PEX 0.0(0-0): Root Complex Interface, Detected Link X1, GEN 2.0 PEX 0.1(1-1): Root Complex Interface, Detected Link X1, GEN 2.0 PEX 1.0(2-2): Root Complex Interface, Detected Link X1, GEN 2.0 FPU initialized to Run Fast Mode. USB 0: Host Mode USB 1: Host Mode USB 2: Host Mode Modules Detected: Net: egiga0, egiga1 [PRIME] Power On! FDT loaded successfully Found 3 disks present
Explicitly scanning the pci busses in uboot confirms this:
Scanning PCI devices on bus 0 BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ 00.00.00 0x1b4b 0x9170 Mass storage controller 0x06 <--- First 88SE9170 (missing when booting debian kernel) 00.01.00 0x0001 0x7823 Memory controller 0x80 Marvell>> pci 1 Scanning PCI devices on bus 1 BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ 01.00.00 0x1b4b 0x9170 Mass storage controller 0x06 <--- Second 88SE9170 01.01.00 0x11ab 0x7823 Memory controller 0x80 Marvell>> pci 2 Scanning PCI devices on bus 2 BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ 02.00.00 0x1b73 0x1009 Serial bus controller 0x03 <--- USB3.0 controller 02.01.00 0x11ab 0x7823 Memory controller 0x80
uboot is also using a generic dtb file apparently for the armada xp dev board, not sure if that is an issue?
fdtfile=armada-xp-db.dtb
I wonder if there is a way to reset the pci-e bridge early on in the boot? Or conversely if it is being reset then maybe don't reset it? Asking to rescan the pci bus in debian results in the same not ready messages:
root@debian:~# ls /sys/bus/pci/devices/ . .. 0000:00:02.0 0000:00:05.0 0000:01:00.0 0000:02:00.0 root@debian:~# echo "1" > /sys/bus/pci/rescan [ 175.362261][ T2509] pci 0000:00:01.0: not ready after 1023ms; waiting [ 176.422247][ T2509] pci 0000:00:01.0: not ready after 2047ms; waiting [ 178.502245][ T2509] pci 0000:00:01.0: not ready after 4095ms; waiting [ 182.662205][ T2509] pci 0000:00:01.0: not ready after 8191ms; waiting [ 191.222125][ T2509] pci 0000:00:01.0: not ready after 16383ms; waiting [ 207.861983][ T2509] pci 0000:00:01.0: not ready after 32767ms; waiting [ 241.141696][ T2509] pci 0000:00:01.0: not ready after 65535ms; giving up root@debian:~#
and dmesg:
[ 174.082556] pci_bus 0000:00: scanning bus [ 175.362261] pci 0000:00:01.0: not ready after 1023ms; waiting [ 176.422247] pci 0000:00:01.0: not ready after 2047ms; waiting [ 178.502245] pci 0000:00:01.0: not ready after 4095ms; waiting [ 182.662205] pci 0000:00:01.0: not ready after 8191ms; waiting [ 191.222125] pci 0000:00:01.0: not ready after 16383ms; waiting [ 207.861983] pci 0000:00:01.0: not ready after 32767ms; waiting [ 241.141696] pci 0000:00:01.0: not ready after 65535ms; giving up [ 241.149669] pci 0000:00:02.0: scanning [bus 01-01] behind bridge, pass 0 [ 241.149693] pci_bus 0000:01: scanning bus [ 241.149706] pci_bus 0000:01: bus scan returning with max=01 [ 241.149722] pci 0000:00:05.0: scanning [bus 02-02] behind bridge, pass 0 [ 241.149738] pci_bus 0000:02: scanning bus [ 241.149750] pci_bus 0000:02: bus scan returning with max=02 [ 241.149764] pci 0000:00:02.0: scanning [bus 01-01] behind bridge, pass 1 [ 241.149781] pci 0000:00:05.0: scanning [bus 02-02] behind bridge, pass 1 [ 241.149797] pci_bus 0000:00: bus scan returning with max=02
Edited 5 time(s). Last edit at 03/08/2024 06:04AM by spiderdijon.
|
Re: Debian on ReadyNas RN2120 March 08, 2024 01:14PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
> Do these envs need to be saved permanently at this
> point? Not much point adding them to the script on
> the USB drive as the USB drive is already present!
> :)
Yes! now that you can run kwboot, we should go a head and make the envs permanent. And also see that it works Debian, too.
Assuming you've already done the dual boot set up above and tested it.
Power up (or reboot) and interrupt u-boot countdown, and run the boot.scr to populate the envs. Double check they are OK.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Do these envs need to be saved permanently at this
> point? Not much point adding them to the script on
> the USB drive as the USB drive is already present!
> :)
Yes! now that you can run kwboot, we should go a head and make the envs permanent. And also see that it works Debian, too.
Assuming you've already done the dual boot set up above and tested it.
Quote
Currently the RN2120 can be booted into Debian with the following envs:
setenv bootdev usb
setenv device 0:1
setenv load_image_addr 0x02000000
setenv load_initrd_addr 0x3000000
setenv load_image 'echo loading uImage ...; ext2load $bootdev $device $load_image_addr /boot/uImage'
setenv load_initrd 'echo loading uInitrd ...; ext2load $bootdev $device $load_initrd_addr /boot/uInitrd'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 earlyprintk=serial"'
setenv bootcmd_exec 'echo Booting Debian from $bootdev; setenv fdt_skip_update yes; setenv initrd_high 0xffffffff; run load_image; run load_initrd; bootm $load_image_addr $load_initrd_addr'
setenv bootcmd_custom_usb 'usb start; run set_bootargs; run bootcmd_exec'
setenv bootcmd 'run bootcmd_custom_usb'
setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)'
setenv set_bootargs 'setenv bootargs "console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial"'
So we want to set up the dual boot to enable booting to either system.
At u-boot prompt, change the bootcmd env, and add 2 more envs:
setenv bootcmd 'run bootcmd_custom_usb; run bootcmd_stock; reset'
setenv set_bootargs_stock 'console=ttyS0,115200 pm_disable=yes mv_cpu_count=2'
setenv bootcmd_stock 'echo Booting Stock; run set_bootargs_stock; nand read 0x2000000 0x200000 0x400000; nand read 0x3000000 0x800000 0x400000; bootm 0x2000000 0x3000000 0x1000000'
Power up (or reboot) and interrupt u-boot countdown, and run the boot.scr to populate the envs. Double check they are OK.
printenvAnd then
saveenvAnd boot into Debian,
fw_printenvAnd then reboot, let it boot automatically back to Debian.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 09, 2024 01:19AM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
> uboot can see both controllers. I have 3 disks
> installed
There are 6 slots, perhaps move the 3rd HDD from the left (ususally the physical location is correct) to each of the remaining slots (and reboot each time). See if the behavior change.
The current mainline RN2120 DTS looks correct to me. The armada-xp-db version just enables all the PCIe buses (not selecting the relevant bus numbers like the RN2120 DTS,).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> uboot can see both controllers. I have 3 disks
> installed
There are 6 slots, perhaps move the 3rd HDD from the left (ususally the physical location is correct) to each of the remaining slots (and reboot each time). See if the behavior change.
The current mainline RN2120 DTS looks correct to me. The armada-xp-db version just enables all the PCIe buses (not selecting the relevant bus numbers like the RN2120 DTS,).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 09, 2024 04:49AM |
Registered: 9 months ago Posts: 27 |
I have tried many combinations of HDDs and the outcome is always the same. The first sata controller fails to start and is missing once booted into debian.
There is a slight difference in the PCI-E section of the dtb between the xp-db and rn2120. Using fdt-viewer:
armada-xp-db.dtb pcie@1,0
armada-xp-netgear-rn2120.dtb pcie@1,0
Unsure what that byte means but there is a difference at least.
There is a slight difference in the PCI-E section of the dtb between the xp-db and rn2120. Using fdt-viewer:
armada-xp-db.dtb pcie@1,0
clocks = <0x00 0x00 0x00 0x07 0x00 0x00 0x00 0x05>;
armada-xp-netgear-rn2120.dtb pcie@1,0
clocks = <0x00 0x00 0x00 0x08 0x00 0x00 0x00 0x05>;
Unsure what that byte means but there is a difference at least.
|
Re: Debian on ReadyNas RN2120 March 11, 2024 11:17AM |
Registered: 9 months ago Posts: 27 |
The auto booting debian from USB works well which is great, but the sata controller issue persists. The unit only has 4 drive bays. It also has two e-sata ports on the rear which connect directly to the SoC (not via PCI-E). Drives are only detected in 2/4 bays which is consistent with the missing sata controller. I have had a look at other DTS files which turn up on google and there appears to be slight changes over the years in some but I'm not able to compile them from source. For example:
https://git.ustc.edu.cn/chendotjs/linux/-/blob/bc844d58f697dff3ded4b410094ee89f5cedc04c/arch/arm/boot/dts/armada-xp-netgear-rn2120.dts
However as you say to dts/dtb looks fine and I can't see any other reports of a missing sata controller. But I'm not sure how many other people have use one of these on a recentish kernel so who knows. Any pointers on where to investigate? I'm at a bit of a loss!
https://git.ustc.edu.cn/chendotjs/linux/-/blob/bc844d58f697dff3ded4b410094ee89f5cedc04c/arch/arm/boot/dts/armada-xp-netgear-rn2120.dts
However as you say to dts/dtb looks fine and I can't see any other reports of a missing sata controller. But I'm not sure how many other people have use one of these on a recentish kernel so who knows. Any pointers on where to investigate? I'm at a bit of a loss!
|
Re: Debian on ReadyNas RN2120 March 11, 2024 02:39PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
> The auto booting debian from USB works well which
> is great,
Cool!
> but the sata controller issue persists.
> The unit only has 4 drive bays. It also has two
> e-sata ports on the rear which connect directly to
> the SoC (not via PCI-E).
Yes, together that's 6 slots. 4 by PCIe.
> However as you say to dts/dtb looks fine and I
> can't see any other reports of a missing sata
> controller. But I'm not sure how many other people
> have use one of these on a recentish kernel so who
> knows. Any pointers on where to investigate? I'm
> at a bit of a loss!
The most recent MVEBU PCIe stil have bugs that showed up some cases. I think this might be one of those, unfortunately. It was marked as broken at some point and got reverted by this commit.
https://github.com/torvalds/linux/commit/3bfc37d92687b4b19056998cebc02f94fbc81427
I actualy reverted it myself locally when I found that PCIe was no longer working because of that original commit. I tested on the Kirwood and MVEBU SoCs USB 3.0 controller. However, I did not test on any SATA PCIe controller.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/11/2024 10:59PM by bodhi.
> The auto booting debian from USB works well which
> is great,
Cool!
> but the sata controller issue persists.
> The unit only has 4 drive bays. It also has two
> e-sata ports on the rear which connect directly to
> the SoC (not via PCI-E).
Yes, together that's 6 slots. 4 by PCIe.
> However as you say to dts/dtb looks fine and I
> can't see any other reports of a missing sata
> controller. But I'm not sure how many other people
> have use one of these on a recentish kernel so who
> knows. Any pointers on where to investigate? I'm
> at a bit of a loss!
The most recent MVEBU PCIe stil have bugs that showed up some cases. I think this might be one of those, unfortunately. It was marked as broken at some point and got reverted by this commit.
https://github.com/torvalds/linux/commit/3bfc37d92687b4b19056998cebc02f94fbc81427
Quote
committed on Aug 4, 2023
Revert "PCI: mvebu: Mark driver as BROKEN"
b3574f5 ("PCI: mvebu: Mark driver as BROKEN") made it impossible to
enable the pci-mvebu driver. The driver does have known problems, but as
Russell and Uwe reported, it does work in some configurations, so removing
it broke some working setups.
Revert b3574f5 so pci-mvebu is available.
Quote
committed on Feb 9, 2023
PCI: mvebu: Mark driver as BROKEN
People are reporting that pci-mvebu.c driver does not work with recent
mainline kernel. There are more bugs which prevents its for daily usage.
So lets mark it as broken for now, until somebody would be able to fix it
in mainline kernel.
I actualy reverted it myself locally when I found that PCIe was no longer working because of that original commit. I tested on the Kirwood and MVEBU SoCs USB 3.0 controller. However, I did not test on any SATA PCIe controller.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 03/11/2024 10:59PM by bodhi.
|
Re: Debian on ReadyNas RN2120 March 12, 2024 01:04AM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon ,
I'm reading and thinking about this problem. Will let you know.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I'm reading and thinking about this problem. Will let you know.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 13, 2024 04:40PM |
Admin Registered: 13 years ago Posts: 19,102 |
spiderdijon,
I did some digging and reading, and I don't think I can do any thing more regarding the 1st PCIe SATA controller. This driver is way too complicated, and I'm not familiar with PCI.
I think we can call it a success in bringing up this box (with the PCI caveat). And we should write an installation post for RN2120, woud you like to do that? In this thread, I wrote individual topic posts to add some to the Wiki (I did). I think we can gather those posts' content into the steps of the installation instruction.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
I did some digging and reading, and I don't think I can do any thing more regarding the 1st PCIe SATA controller. This driver is way too complicated, and I'm not familiar with PCI.
I think we can call it a success in bringing up this box (with the PCI caveat). And we should write an installation post for RN2120, woud you like to do that? In this thread, I wrote individual topic posts to add some to the Wiki (I did). I think we can gather those posts' content into the steps of the installation instruction.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Debian on ReadyNas RN2120 March 14, 2024 07:08AM |
Registered: 9 months ago Posts: 27 |
