Mainline Debian on Iomega ix4-300d
Posted by Koen
|
Re: Mainline Debian on Iomega ix4-300d September 09, 2023 05:08PM |
Admin Registered: 13 years ago Posts: 18,575 |
> 2. Installed bodhi kernel on mainline Debian 11 ->
> no leds
Strange! do you have serial console log? is there any error during boot?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> no leds
Strange! do you have serial console log? is there any error during boot?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 10, 2023 04:14AM |
Marvell>> ide reset; ext2load ide 2:1 0x0040000 uImage; ext2load ide 2:1 0x2000000 uInitrd; setenv bootargs $console $mtdparts root=LABEL=rootfs rw rootdelay=5; bootm 0x40000 0x2000000
Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
Found adapter at bus 0, device 1 ... Scanning channels
Device 2 @ 1 0:
Model: WDC WD800JD-75MSA3 Firm: 10.01E04 Ser#: WD-WMAM9CF02972
Type: Hard Disk
Supports 48-bit addressing
Capacity: 76293.9 MB = 74.5 GB (156250000 x 512)
Device 3 @ 1 1:
Model: WDC WD5000AZLX-75K2TA0 Firm: 01.01A01 Ser#: WD-WCC6Z6NZ16LL
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Device 4 @ 1 2:
Model: WDC WD5000AAKS-00A7B0 Firm: 01.03B01 Ser#: WD-WMASY4625414
Type: Hard Disk
Supports 48-bit addressing
Capacity: 476940.0 MB = 465.7 GB (976773168 x 512)
Loading file "uImage" from ide device 2:1 (hdc1)
5137175 bytes read
Loading file "uInitrd" from ide device 2:1 (hdc1)
10142870 bytes read
## Booting kernel from Legacy Image at 00040000 ...
Image Name: Linux-6.4.11-mvebu-tld-1
Created: 2023-09-09 15:54:47 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5137111 Bytes = 4.9 MB
Load Address: 04000000
Entry Point: 04000000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02000000 ...
Image Name: initramfs-6.4.11-mvebu-tld-1
Created: 2023-09-09 15:56:22 UTC
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 10142806 Bytes = 9.7 MB
Load Address: 02000000
Entry Point: 02000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 6.4.11-mvebu-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Sun Aug 20 03:17:26 PDT 2023
[ 0.000000][ T0] CPU: ARMv7 Processor [562f5842] revision 2 (ARMv7), cr=10c5387d
[ 0.000000][ T0] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: Lenovo Iomega ix4-300d
[ 0.000000][ T0] Memory policy: Data cache writealloc
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] HighMem empty
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[ 0.000000][ T0] percpu: Embedded 14 pages/cpu s25300 r8192 d23852 u57344
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 mtdparts=armada-nand:0xe0000@0x0(uboot),0x20000@0xe0000(env),0x20000@0x100000(env2),0x400000@0x120000(zImage),0x400000@0x520000(initrd),0x3F200000@0xE00000(boot),0x40000000@0x0(flash) root=LABEL=rootfs rw rootdelay=5
[ 0.000000][ T0] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 129920
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.000000][ T0] Memory: 490396K/524288K available (10240K kernel code, 867K rwdata, 3444K rodata, 1024K init, 462K bss, 33892K reserved, 0K cma-reserved, 0K highmem)
[ 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.000015][ T0] clocksource: armada_370_xp_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 76450417870 ns
[ 0.000684][ T0] kfence: initialized - using 2097152 bytes for 255 objects at 0x(ptrval)-0x(ptrval)
[ 0.001598][ T0] Console: colour dummy device 80x30
[ 0.001638][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 50.00 BogoMIPS (lpj=250000)
[ 0.001652][ T0] CPU: Testing write buffer coherency: ok
[ 0.001693][ T0] pid_max: default: 32768 minimum: 301
[ 0.002061][ T0] LSM: initializing lsm=capability,integrity
[ 0.002272][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.002287][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.003845][ T1] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.005247][ T1] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.005255][ T1] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.005381][ T1] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.005388][ T1] cblist_init_generic: Setting shift to 1 and lim to 1.
[ 0.005560][ T1] Setting up static identity map for 0x100000 - 0x100060
[ 0.005896][ T1] mvebu-soc-id: MVEBU SoC ID=0x7823, Rev=0x1
[ 0.006021][ T1] mvebu-pmsu: Initializing Power Management Service Unit
[ 0.006191][ T1] rcu: Hierarchical SRCU implementation.
[ 0.006198][ T1] rcu: Max phase no-delay instances is 1000.
[ 0.007188][ T1] smp: Bringing up secondary CPUs ...
[ 0.008027][ T1] Booting CPU 1
[ 0.008382][ T0] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.018454][ T1] smp: Brought up 1 node, 2 CPUs
[ 0.018465][ T1] SMP: Total of 2 processors activated (100.00 BogoMIPS).
[ 0.018473][ T1] CPU: All CPU(s) started in SVC mode.
[ 0.018997][ T1] devtmpfs: initialized
[ 0.025403][ T1] VFP support v0.3: implementor 56 architecture 2 part 20 variant 9 rev 6
[ 0.025789][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.025822][ T1] futex hash table entries: 512 (order: 3, 32768 bytes, linear)
[ 0.026157][ T1] prandom: seed boundary self test passed
[ 0.028513][ T1] prandom: 100 self tests passed
[ 0.028522][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.030119][ T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.030539][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.031702][ T1] audit: initializing netlink subsys (disabled)
[ 0.031981][ T25] audit: type=2000 audit(0.030:1): state=initialized audit_enabled=0 res=1
[ 0.032657][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.032733][ T1] cpuidle: using governor ladder
[ 0.032767][ T1] cpuidle: using governor menu
[ 0.033063][ T17] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 0
[ 0.033073][ T17] hw-breakpoint: CPU 0 failed to disable vector catch
[ 0.033106][ T18] hw-breakpoint: Debug register access (0xee003e17) caused undefined instruction on CPU 1
[ 0.036246][ T1] platform soc: Fixed dependency cycle(s) with /soc/internal-regs/interrupt-controller@20a00
[ 0.210111][ T1] raid6: int32x8 gen() 252 MB/s
[ 0.380088][ T1] raid6: int32x4 gen() 272 MB/s
[ 0.550067][ T1] raid6: int32x2 gen() 422 MB/s
[ 0.720079][ T1] raid6: int32x1 gen() 401 MB/s
[ 0.720087][ T1] raid6: using algorithm int32x2 gen() 422 MB/s
[ 0.890077][ T1] raid6: .... xor() 247 MB/s, rmw enabled
[ 0.890084][ T1] raid6: using intx1 recovery algorithm
[ 0.891234][ T1] SCSI subsystem initialized
[ 0.891707][ T1] usbcore: registered new interface driver usbfs
[ 0.891756][ T1] usbcore: registered new interface driver hub
[ 0.891804][ T1] usbcore: registered new device driver usb
[ 0.892189][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 0.892196][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.892219][ T1] PTP clock support registered
[ 0.894308][ T1] vgaarb: loaded
[ 0.894931][ T1] clocksource: Switched to clocksource armada_370_xp_clocksource
[ 0.895520][ T1] VFS: Disk quotas dquot_6.6.0
[ 0.895609][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.909374][ T1] NET: Registered PF_INET protocol family
[ 0.909557][ T1] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[ 0.910905][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 0.911005][ T1] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[ 0.911028][ T1] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[ 0.911078][ T1] TCP bind hash table entries: 4096 (order: 4, 65536 bytes, linear)
[ 0.911135][ T1] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.911403][ T1] MPTCP token hash table entries: 512 (order: 1, 8192 bytes, linear)
[ 0.911472][ T1] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.911496][ T1] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[ 0.911725][ T1] NET: Registered PF_UNIX/PF_LOCAL protocol family
[ 0.912417][ T1] RPC: Registered named UNIX socket transport module.
[ 0.912426][ T1] RPC: Registered udp transport module.
[ 0.912431][ T1] RPC: Registered tcp transport module.
[ 0.912436][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.912452][ T1] PCI: CLS 0 bytes, default 64
[ 0.912751][ T11] Trying to unpack rootfs image as initramfs...
[ 0.925042][ T1] hw perfevents: enabled with armv7_cortex_a9 PMU driver, 7 counters available
[ 0.926876][ T1] Initialise system trusted keyrings
[ 0.926951][ T1] Key type blacklist registered
[ 0.928549][ T1] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[ 0.928782][ T1] zbud: loaded
[ 0.930827][ T1] NFS: Registering the id_resolver key type
[ 0.930875][ T1] Key type id_resolver registered
[ 0.930882][ T1] Key type id_legacy registered
[ 0.930941][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.930958][ T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 0.995427][ T1] xor: measuring software checksum speed
[ 1.004190][ T1] arm4regs : 1124 MB/sec
[ 1.014520][ T1] 8regs : 959 MB/sec
[ 1.022617][ T1] 32regs : 1221 MB/sec
[ 1.022627][ T1] xor: using function: 32regs (1221 MB/sec)
[ 1.022647][ T1] async_tx: api initialized (async)
[ 1.022661][ T1] Key type asymmetric registered
[ 1.022669][ T1] Asymmetric key parser 'x509' registered
[ 1.023063][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 245)
[ 1.023219][ T1] io scheduler bfq registered
[ 1.028310][ T1] armada-xp-pinctrl d0018000.pin-ctrl: registered pinctrl driver
[ 1.030601][ T1] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 1.031318][ T1] debugfs: Directory 'd0018100.gpio' with parent 'regmap' already present!
[ 1.032274][ T1] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[ 1.032895][ T1] debugfs: Directory 'd0018140.gpio' with parent 'regmap' already present!
[ 1.034664][ T1] mvebu-pcie soc:pcie@82000000: host bridge /soc/pcie@82000000 ranges:
[ 1.034736][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0040000..0x00d0041fff -> 0x0000040000
[ 1.034773][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0044000..0x00d0045fff -> 0x0000044000
[ 1.034810][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0048000..0x00d0049fff -> 0x0000048000
[ 1.034846][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d004c000..0x00d004dfff -> 0x000004c000
[ 1.034881][ T1] mvebu-pcie soc:pcie@82000000: MEM 0x00d0080000..0x00d0081fff -> 0x0000080000
[ 1.034915][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 1.035020][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 1.035056][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 1.035089][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[ 1.035123][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 1.035156][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0300000000
[ 1.035188][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 1.035221][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0400000000
[ 1.035253][ T1] mvebu-pcie soc:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[ 1.035275][ T1] mvebu-pcie soc:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0500000000
[ 1.036197][ T1] mvebu-pcie soc:pcie@82000000: PCI host bridge to bus 0000:00
[ 1.036213][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 1.036228][ T1] pci_bus 0000:00: root bus resource [mem 0xd0040000-0xd0041fff] (bus address [0x00040000-0x00041fff])
[ 1.036240][ T1] pci_bus 0000:00: root bus resource [mem 0xd0044000-0xd0045fff] (bus address [0x00044000-0x00045fff])
[ 1.036252][ T1] pci_bus 0000:00: root bus resource [mem 0xd0048000-0xd0049fff] (bus address [0x00048000-0x00049fff])
[ 1.036263][ T1] pci_bus 0000:00: root bus resource [mem 0xd004c000-0xd004dfff] (bus address [0x0004c000-0x0004dfff])
[ 1.036275][ T1] pci_bus 0000:00: root bus resource [mem 0xd0080000-0xd0081fff] (bus address [0x00080000-0x00081fff])
[ 1.036285][ T1] pci_bus 0000:00: root bus resource [mem 0xf8000000-0xffdfffff]
[ 1.036294][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 1.036403][ T1] pci 0000:00:01.0: [11ab:7823] type 01 class 0x060400
[ 1.037346][ T1] pci 0000:00:05.0: [11ab:7823] type 01 class 0x060400
[ 1.039072][ T1] PCI: bus0: Fast back to back transfers disabled
[ 1.039096][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 1.039124][ T1] pci 0000:00:05.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 1.063267][ T1] pci 0000:01:00.0: [11ab:7042] type 00 class 0x010000
[ 1.063306][ T1] pci 0000:01:00.0: reg 0x10: [mem 0x40000000-0x400fffff 64bit]
[ 1.063329][ T1] pci 0000:01:00.0: reg 0x18: [io 0xf1100000-0xf11000ff]
[ 1.063499][ T1] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCIe x1 link at 0000:00:01.0 (capable of 8.000 Gb/s with 2.5 GT/s PCIe x4 link)
[ 1.063894][ T1] pci 0000:01:00.0: disabling ASPM on pre-1.1 PCIe device. You can enable it with 'pcie_aspm=force'
[ 1.063941][ T1] PCI: bus1: Fast back to back transfers disabled
[ 1.063960][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 1.064321][ T1] pci 0000:02:00.0: [1033:0194] type 00 class 0x0c0330
[ 1.064356][ T1] pci 0000:02:00.0: reg 0x10: [mem 0x4a000000-0x4a001fff 64bit]
[ 1.064523][ T1] pci 0000:02:00.0: PME# supported from D0 D3hot
[ 1.105074][ T1] PCI: bus2: Fast back to back transfers disabled
[ 1.105096][ T1] pci_bus 0000:02: busn_res: [bus 02-ff] end is updated to 02
[ 1.105157][ T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xf8000000-0xf80fffff]
[ 1.105173][ T1] pci 0000:00:05.0: BAR 14: assigned [mem 0xf8100000-0xf81fffff]
[ 1.105185][ T1] pci 0000:00:01.0: BAR 13: assigned [io 0x10000-0x10fff]
[ 1.105201][ T1] pci 0000:01:00.0: BAR 0: assigned [mem 0xf8000000-0xf80fffff 64bit]
[ 1.105224][ T1] pci 0000:01:00.0: BAR 2: assigned [io 0x10000-0x100ff]
[ 1.105239][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 1.105249][ T1] pci 0000:00:01.0: bridge window [io 0x10000-0x10fff]
[ 1.105272][ T1] pci 0000:00:01.0: bridge window [mem 0xf8000000-0xf80fffff]
[ 1.105297][ T1] pci 0000:02:00.0: BAR 0: assigned [mem 0xf8100000-0xf8101fff 64bit]
[ 1.105317][ T1] pci 0000:00:05.0: PCI bridge to [bus 02]
[ 1.105329][ T1] pci 0000:00:05.0: bridge window [mem 0xf8100000-0xf81fffff]
[ 1.105517][ T1] pcieport 0000:00:01.0: enabling device (0140 -> 0143)
[ 1.105662][ T1] pcieport 0000:00:05.0: enabling device (0140 -> 0142)
[ 1.106516][ T1] mv_xor d0060900.xor: Marvell shared XOR driver
[ 1.176180][ T1] mv_xor d0060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 1.180331][ T1] mv_xor d00f0900.xor: Marvell shared XOR driver
[ 1.246230][ T1] mv_xor d00f0900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 1.372685][ T1] Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
[ 1.376468][ T1] printk: console [ttyS0] disabled
[ 1.396836][ T1] d0012000.serial: ttyS0 at MMIO 0xd0012000 (irq = 37, base_baud = 15625000) is a 16550A
[ 1.396909][ T1] printk: console [ttyS0] enabled
[ 1.434145][ T11] Freeing initrd memory: 9908K
[ 2.851585][ T1] sata_mv 0000:01:00.0: Gen-IIE 32 slots 4 ports SCSI mode IRQ via INTx
[ 2.863973][ T1] scsi host0: sata_mv
[ 2.868811][ T1] scsi host1: sata_mv
[ 2.873678][ T1] scsi host2: sata_mv
[ 2.878435][ T1] scsi host3: sata_mv
[ 2.882607][ T1] ata1: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8022000 irq 38
[ 2.891044][ T1] ata2: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8024000 irq 38
[ 2.899457][ T1] ata3: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8026000 irq 38
[ 2.907861][ T1] ata4: SATA max UDMA/133 mmio m1048576@0xf8000000 port 0xf8028000 irq 38
[ 2.917765][ T1] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xd3
[ 2.924851][ T1] nand: Samsung NAND 1GiB 3,3V 8-bit
[ 2.930039][ T1] nand: 1024 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 2.938492][ T1] marvell-nfc d00d0000.nand-controller: No minimum ECC strength, using 1b/512B
[ 2.947784][ T1] Bad block table found at page 524224, version 0x01
[ 2.955015][ T1] Bad block table found at page 524160, version 0x01
[ 2.961901][ T1] nand_read_bbt: bad block at 0x000003c60000
[ 2.967950][ T1] 6 fixed-partitions partitions found on MTD device pxa3xx_nand-0
[ 2.975662][ T1] Creating 6 MTD partitions on "pxa3xx_nand-0":
[ 2.981822][ T1] 0x000000000000-0x0000000e0000 : "u-boot"
[ 2.989367][ T1] 0x0000000e0000-0x000000100000 : "u-boot-env"
[ 2.997040][ T1] 0x000000100000-0x000000120000 : "u-boot-env2"
[ 3.004814][ T1] 0x000000120000-0x000000520000 : "zImage"
[ 3.012136][ T1] 0x000000520000-0x000000920000 : "initrd"
[ 3.019475][ T1] 0x000000e00000-0x000040000000 : "boot"
[ 3.031335][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 3.039928][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 3.084470][ T1] mvneta d0070000.ethernet eth0: Using random mac address 92:93:b2:5f:19:ef
[ 3.095799][ T1] mvneta d0074000.ethernet eth1: Using random mac address 96:b3:72:2f:22:1b
[ 3.104819][ T1] usbcore: registered new interface driver smsc75xx
[ 3.111797][ T1] orion-ehci d0050000.usb: EHCI Host Controller
[ 3.117964][ T1] orion-ehci d0050000.usb: new USB bus registered, assigned bus number 1
[ 3.126417][ T1] orion-ehci d0050000.usb: irq 42, io mem 0xd0050000
[ 3.154981][ T1] orion-ehci d0050000.usb: USB 2.0 started, EHCI 1.00
[ 3.161916][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.04
[ 3.170938][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.178907][ T1] usb usb1: Product: EHCI Host Controller
[ 3.184503][ T1] usb usb1: Manufacturer: Linux 6.4.11-mvebu-tld-1 ehci_hcd
[ 3.191679][ T1] usb usb1: SerialNumber: d0050000.usb
[ 3.197838][ T1] hub 1-0:1.0: USB hub found
[ 3.202347][ T1] hub 1-0:1.0: 1 port detected
[ 3.207766][ T1] orion-ehci d0051000.usb: EHCI Host Controller
[ 3.213907][ T1] orion-ehci d0051000.usb: new USB bus registered, assigned bus number 2
[ 3.222340][ T1] orion-ehci d0051000.usb: irq 43, io mem 0xd0051000
[ 3.264951][ T1] orion-ehci d0051000.usb: USB 2.0 started, EHCI 1.00
[ 3.271849][ T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.04
[ 3.280875][ T1] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 3.288842][ T1] usb usb2: Product: EHCI Host Controller
[ 3.294439][ T1] usb usb2: Manufacturer: Linux 6.4.11-mvebu-tld-1 ehci_hcd
[ 3.301615][ T1] usb usb2: SerialNumber: d0051000.usb
[ 3.307673][ T1] hub 2-0:1.0: USB hub found
[ 3.312179][ T1] hub 2-0:1.0: 1 port detected
[ 3.317899][ T1] usbcore: registered new interface driver usblp
[ 3.324193][ T1] usbcore: registered new interface driver usb-storage
[ 3.331395][ T1] mousedev: PS/2 mouse device common for all mice
[ 3.339199][ T1] rtc-mv d0010300.rtc: registered as rtc0
[ 3.344817][ T1] rtc-mv d0010300.rtc: setting system clock to 2023-09-10T09:09:46 UTC (1694336986)
[ 3.354582][ T1] i2c_dev: i2c /dev entries driver
[ 3.359900][ T1] mv64xxx_i2c d0011000.i2c: can't get pinctrl, bus recovery not supported
[ 3.369194][ T1] at24 0-0050: supply vcc not found, using dummy regulator
[ 3.376904][ T1] at24 0-0050: 8192 byte 24c64 EEPROM, writable, 1 bytes/write
[ 3.385675][ T1] rtc-pcf8563 0-0051: registered as rtc1
[ 3.415013][ T674] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.424575][ T674] ata1.00: ATA-7: WDC WD800JD-75MSA3, 10.01E04, max UDMA/133
[ 3.432029][ T674] ata1.00: 156250000 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 3.442253][ T674] ata1.00: configured for UDMA/133
[ 3.457880][ T11] scsi 0:0:0:0: Direct-Access ATA WDC WD800JD-75MS 1E04 PQ: 0 ANSI: 5
[ 3.468440][ T694] sd 0:0:0:0: [sda] 156250000 512-byte logical blocks: (80.0 GB/74.5 GiB)
[ 3.477444][ T694] sd 0:0:0:0: [sda] Write Protect is off
[ 3.483107][ T694] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 3.493061][ T694] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[ 3.494745][ T1] orion_wdt: Initial timeout 171 sec
[ 3.505851][ T1] device-mapper: uevent: version 1.0.3
[ 3.511633][ T1] device-mapper: ioctl: 4.48.0-ioctl (2023-03-01) initialised: dm-devel@redhat.com
[ 3.521305][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 3.528648][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 3.536128][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 3.543544][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 3.550431][ T694] sda: sda1 sda2 sda3 < sda5 >
[ 3.551779][ T1] debugfs: Directory 'cpu1' with parent 'opp' already present!
[ 3.563696][ T694] sd 0:0:0:0: [sda] Attached SCSI disk
[ 3.564443][ T1] sdhci: Secure Digital Host Controller Interface driver
[ 3.575990][ T1] sdhci: Copyright(c) Pierre Ossman
[ 3.581211][ T1] sdhci-pltfm: SDHCI platform and OF driver helper
[ 3.590255][ T1] marvell-cesa d0090000.crypto: CESA device successfully registered
[ 3.598396][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 3.604574][ T1] usbcore: registered new interface driver usbhid
[ 3.610915][ T112] usb 2-1: new full-speed USB device number 2 using orion-ehci
[ 3.618377][ T1] usbhid: USB HID core driver
[ 3.623631][ T1] NET: Registered PF_INET6 protocol family
[ 3.631215][ T1] Segment Routing with IPv6
[ 3.635726][ T1] RPL Segment Routing with IPv6
[ 3.640541][ T1] In-situ OAM (IOAM) with IPv6
[ 3.645286][ T1] sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
[ 3.653490][ T1] NET: Registered PF_PACKET protocol family
[ 3.660171][ T1] 8021q: 802.1Q VLAN Support v1.8
[ 3.665183][ T1] Key type dns_resolver registered
[ 3.670389][ T1] ThumbEE CPU extension supported.
[ 3.675415][ T1] Registering SWP/SWPB emulation handler
[ 3.722925][ T1] registered taskstats version 1
[ 3.736018][ T1] Loading compiled-in X.509 certificates
[ 3.742425][ T1] Key type .fscrypt registered
[ 3.747720][ T1] Key type fscrypt-provisioning registered
[ 3.753538][ T1] Key type big_key registered
[ 3.781907][ T1] Key type encrypted registered
[ 3.794574][ T1] input: gpio-keys as /devices/platform/gpio-keys/input/input0
[ 3.803065][ T1] clk: Disabling unused clocks
[ 3.852672][ T112] usb 2-1: New USB device found, idVendor=8086, idProduct=0808, bcdDevice= 1.00
[ 3.861650][ T112] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 3.869548][ T112] usb 2-1: Product: USB PnP Sound Device
[ 3.875073][ T112] usb 2-1: Manufacturer: C-Media Electronics Inc.
[ 3.886689][ T112] input: C-Media Electronics Inc. USB PnP Sound Device as /devices/platform/soc/soc:internal-regs/d0051000.usb/usb2/2-1/2-1:1.3/0003:8086:0808.0001/input/input1
[ 3.975659][ T679] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 3.975725][ T112] hid-generic 0003:8086:0808.0001: input,hidraw0: USB HID v1.00 Device [C-Media Electronics Inc. USB PnP Sound Device] on usb-d0051000.usb-1/input3
[ 3.985596][ T679] ata2.00: ATA-10: WDC WD5000AZLX-75K2TA0, 01.01A01, max UDMA/133
[ 4.006546][ T679] ata2.00: 976773168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 4.017213][ T679] ata2.00: configured for UDMA/133
[ 4.022895][ T41] scsi 1:0:0:0: Direct-Access ATA WDC WD5000AZLX-7 1A01 PQ: 0 ANSI: 5
[ 4.033982][ T893] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 4.042260][ T893] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[ 4.048295][ T893] sd 1:0:0:0: [sdb] Write Protect is off
[ 4.053920][ T893] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.063866][ T893] sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[ 4.495124][ T893] sd 1:0:0:0: [sdb] Attached SCSI disk
[ 4.535737][ T684] ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 4.575781][ T684] ata3.00: ATA-8: WDC WD5000AAKS-00A7B0, 01.03B01, max UDMA/133
[ 4.583317][ T684] ata3.00: 976773168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[ 4.594139][ T684] ata3.00: configured for UDMA/133
[ 4.610223][ T432] scsi 2:0:0:0: Direct-Access ATA WDC WD5000AAKS-0 3B01 PQ: 0 ANSI: 5
[ 4.622059][ T41] sd 2:0:0:0: [sdc] 976773168 512-byte logical blocks: (500 GB/466 GiB)
[ 4.630662][ T41] sd 2:0:0:0: [sdc] Write Protect is off
[ 4.636556][ T41] sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 4.646724][ T41] sd 2:0:0:0: [sdc] Preferred minimum I/O size 512 bytes
[ 4.662887][ T41] sd 2:0:0:0: [sdc] Attached SCSI disk
[ 4.959184][ T689] ata4: SATA link down (SStatus 0 SControl 300)
[ 4.978339][ T1] Freeing unused kernel image (initmem) memory: 1024K
[ 4.987279][ T1] Checked W+X mappings: passed, no W+X pages found
[ 4.993744][ T1] Run /init as init process
Loading, please wait...
Starting version 247.3-7+deb11u4
[ 6.661422][ T1326] mtdblock: MTD device 'u-boot' is NAND, please consider using UBI block devices instead.
[ 6.678383][ T1325] mtdblock: MTD device 'u-boot-env' is NAND, please consider using UBI block devices instead.
[ 6.683404][ T1327] mtdblock: MTD device 'u-boot-env2' is NAND, please consider using UBI block devices instead.
[ 6.704816][ T1329] mtdblock: MTD device 'zImage' is NAND, please consider using UBI block devices instead.
[ 6.715261][ T1326] mtdblock: MTD device 'boot' is NAND, please consider using UBI block devices instead.
[ 6.737264][ T1329] mtdblock: MTD device 'initrd' is NAND, please consider using UBI block devices instead.
[ 6.822289][ T1334] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 6.886885][ T1334] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 3
[ 6.897432][ T1334] xhci_hcd 0000:02:00.0: hcc params 0x014042cb hci version 0x96 quirks 0x0000000000000004
[ 6.910691][ T1334] xhci_hcd 0000:02:00.0: xHCI Host Controller
[ 6.918967][ T1334] xhci_hcd 0000:02:00.0: new USB bus registered, assigned bus number 4
[ 6.929257][ T1334] xhci_hcd 0000:02:00.0: Host supports USB 3.0 SuperSpeed
[ 6.941652][ T1334] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.04
[ 6.953013][ T1334] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.964235][ T1334] usb usb3: Product: xHCI Host Controller
[ 6.971237][ T1334] usb usb3: Manufacturer: Linux 6.4.11-mvebu-tld-1 xhci-hcd
[ 6.980472][ T1334] usb usb3: SerialNumber: 0000:02:00.0
[ 6.991479][ T1334] hub 3-0:1.0: USB hub found
[ 6.998881][ T1334] hub 3-0:1.0: 2 ports detected
[ 7.009749][ T1334] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 7.022805][ T1334] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.04
[ 7.034105][ T1334] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 7.052315][ T1334] usb usb4: Product: xHCI Host Controller
[ 7.060167][ T1334] usb usb4: Manufacturer: Linux 6.4.11-mvebu-tld-1 xhci-hcd
[ 7.072928][ T1334] usb usb4: SerialNumber: 0000:02:00.0
[ 7.088854][ T1334] hub 4-0:1.0: USB hub found
[ 7.106894][ T1334] hub 4-0:1.0: 2 ports detected
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.36.1
[/sbin/fsck.ext4 (1) -- /dev/sda2] fsck.ext4 -a -C0 /dev/sda2
rootfs: clean, 41263/4825088 files, 867790/19283712 blocks
done.
[ 13.690590][ T1367] EXT4-fs (sda2): mounted filesystem 6e579b6a-87f3-482e-a34a-faad820bb1e5 r/w with ordered data mode. Quota mode: none.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 16.557200][ T1] systemd[1]: systemd 247.3-7+deb11u4 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified)
[ 16.582478][ T1] systemd[1]: Detected architecture arm.
Welcome to [1mDebian GNU/Linux 11 (bullseye)[0m!
[ 16.699111][ T1] systemd[1]: Set hostname to <lenovo>.
[ 17.766166][ T37] platform gpio-leds: deferred probe pending
[ 19.471848][ T1] systemd[1]: Queued start job for default target Graphical Interface.
[ 20.165353][ C0] random: crng init done
[ 20.210794][ T1] systemd[1]: Created slice system-getty.slice.
[[0;32m OK [0m] Created slice [0;1;39msystem-getty.slice[0m.
[ 20.228640][ T1] systemd[1]: Created slice system-modprobe.slice.
[[0;32m OK [0m] Created slice [0;1;39msystem-modprobe.slice[0m.
[ 20.268528][ T1] systemd[1]: Created slice system-serial\x2dgetty.slice.
[[0;32m OK [0m] Created slice [0;1;39msystem-serial\x2dgetty.slice[0m.
[ 20.308550][ T1] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[[0;32m OK [0m] Created slice [0;1;39msystem-systemd\x2dfsck.slice[0m.
[ 20.348188][ T1] systemd[1]: Created slice User and Session Slice.
[[0;32m OK [0m] Created slice [0;1;39mUser and Session Slice[0m.
[ 20.386375][ T1] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[[0;32m OK [0m] Started [0;1;39mDispatch Password …ts to Console Directory Watch[0m.
[ 20.426199][ T1] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[[0;32m OK [0m] Started [0;1;39mForward Password R…uests to Wall Directory Watch[0m.
[ 20.467169][ T1] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[[0;32m OK [0m] Set up automount [0;1;39mArbitrary…s File System Automount Point[0m.
[ 20.516070][ T1] systemd[1]: Reached target Local Encrypted Volumes.
[[0;32m OK [0m] Reached target [0;1;39mLocal Encrypted Volumes[0m.
[ 20.556041][ T1] systemd[1]: Reached target Paths.
[[0;32m OK [0m] Reached target [0;1;39mPaths[0m.
[ 20.595768][ T1] systemd[1]: Reached target Remote File Systems.
[[0;32m OK [0m] Reached target [0;1;39mRemote File Systems[0m.
[ 20.635730][ T1] systemd[1]: Reached target Slices.
[[0;32m OK [0m] Reached target [0;1;39mSlices[0m.
[ 20.699560][ T1] systemd[1]: Listening on Syslog Socket.
[[0;32m OK [0m] Listening on [0;1;39mSyslog Socket[0m.
[ 20.736777][ T1] systemd[1]: Listening on fsck to fsckd communication Socket.
[[0;32m OK [0m] Listening on [0;1;39mfsck to fsckd communication Socket[0m.
[ 20.754742][ T1] systemd[1]: Listening on initctl Compatibility Named Pipe.
[[0;32m OK [0m] Listening on [0;1;39minitctl Compatibility Named Pipe[0m.
[ 20.773589][ T1] systemd[1]: Listening on Journal Audit Socket.
[[0;32m OK [0m] Listening on [0;1;39mJournal Audit Socket[0m.
[ 20.816819][ T1] systemd[1]: Listening on Journal Socket (/dev/log).
[[0;32m OK [0m] Listening on [0;1;39mJournal Socket (/dev/log)[0m.
[ 20.857078][ T1] systemd[1]: Listening on Journal Socket.
[[0;32m OK [0m] Listening on [0;1;39mJournal Socket[0m.
[ 20.898271][ T1] systemd[1]: Listening on udev Control Socket.
[[0;32m OK [0m] Listening on [0;1;39mudev Control Socket[0m.
[ 20.913931][ T1] systemd[1]: Listening on udev Kernel Socket.
[[0;32m OK [0m] Listening on [0;1;39mudev Kernel Socket[0m.
[ 20.929824][ T1] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[ 20.996276][ T1] systemd[1]: Mounting POSIX Message Queue File System...
Mounting [0;1;39mPOSIX Message Queue File System[0m...
[ 21.021483][ T1] systemd[1]: Mounting Kernel Debug File System...
Mounting [0;1;39mKernel Debug File System[0m...
[ 21.056462][ T1] systemd[1]: Condition check resulted in Kernel Trace File System being skipped.
[ 21.076086][ T1] systemd[1]: Starting Create list of static device nodes for the current kernel...
Starting [0;1;39mCreate list of st…odes for the current kernel[0m...
[ 21.103997][ T1] systemd[1]: Starting Load Kernel Module configfs...
Starting [0;1;39mLoad Kernel Module configfs[0m...
[ 21.187034][ T1] systemd[1]: Starting Load Kernel Module drm...
Starting [0;1;39mLoad Kernel Module drm[0m...
[ 21.235914][ T1] systemd[1]: Starting Load Kernel Module fuse...
Starting [0;1;39mLoad Kernel Module fuse[0m...
[ 21.494205][ T1] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 21.504537][ T1] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[ 21.551133][ T1400] fuse: init (API version 7.38)
[ 21.557558][ T1] systemd[1]: Starting Journal Service...
Starting [0;1;39mJournal Service[0m...
[ 21.669490][ T1] systemd[1]: Starting Load Kernel Modules...
Starting [0;1;39mLoad Kernel Modules[0m...
[ 21.766439][ T1] systemd[1]: Starting Remount Root and Kernel File Systems...
Starting [0;1;39mRemount Root and Kernel File Systems[0m...
[ 21.821065][ T1] systemd[1]: Starting Coldplug All udev Devices...
Starting [0;1;39mColdplug All udev Devices[0m...
[ 21.909593][ T1] systemd[1]: Mounted POSIX Message Queue File System.
[[0;32m OK [0m] Mounted [0;1;39mPOSIX Message Queue File System[0m.
[ 21.938446][ T1405] EXT4-fs (sda2): re-mounted 6e579b6a-87f3-482e-a34a-faad820bb1e5 r/w. Quota mode: none.
[ 21.964670][ T1] systemd[1]: Mounted Kernel Debug File System.
[[0;32m OK [0m] Mounted [0;1;39mKernel Debug File System[0m.
[ 21.982028][ T1] systemd[1]: Finished Create list of static device nodes for the current kernel.
[[0;32m OK [0m] Finished [0;1;39mCreate list of st… nodes for the current kernel[0m.
[ 22.030914][ T1] systemd[1]: modprobe@configfs.service: Succeeded.
[ 22.055757][ T1] systemd[1]: Finished Load Kernel Module configfs.
[[0;32m OK [0m] Finished [0;1;39mLoad Kernel Module configfs[0m.
[ 22.099276][ T1] systemd[1]: modprobe@drm.service: Succeeded.
[ 22.108932][ T1] systemd[1]: Finished Load Kernel Module drm.
[[0;32m OK [0m] Finished [0;1;39mLoad Kernel Module drm[0m.
[ 22.149856][ T1] systemd[1]: modprobe@fuse.service: Succeeded.
[ 22.160334][ T1] systemd[1]: Finished Load Kernel Module fuse.
[[0;32m OK [0m] Finished [0;1;39mLoad Kernel Module fuse[0m.
[ 22.183719][ T1402] adt7475 0-002e: ADT7473 device, revision 0
[ 22.190242][ T1402] adt7475 0-002e: Optional features: fan4 pwm2
[ 22.201533][ T1] systemd[1]: Finished Remount Root and Kernel File Systems.
[[0;32m OK [0m] Finished [0;1;39mRemount Root and Kernel File Systems[0m.
[ 22.275929][ T1] systemd[1]: Mounting FUSE Control File System...
Mounting [0;1;39mFUSE Control File System[0m...
[ 22.313784][ T1] systemd[1]: Mounting Kernel Configuration File System...
Mountin[ 22.371491][ T1402] hwmon hwmon2: temp1_input not attached to any thermal zone
g [0;1;39mKernel Configuration File System[0m...
[ 22.389038][ T1402] hwmon hwmon3: temp1_input not attached to any thermal zone
[ 22.416674][ T1] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[ 22.420761][ T1402] hwmon hwmon4: temp1_input not attached to any thermal zone
[ 22.455825][ T1] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[ 22.542604][ T1402] Asymmetric key parser 'pkcs8' registered
[ 22.566522][ T1] systemd[1]: Starting Load/Save Random Seed...
Starting [0;1;39mLoad/Save Random Seed[0m...
[ 22.625297][ T1] systemd[1]: Starting Create System Users...
Starting [0;1;39mCreate System Users[0m...
[ 22.715068][ T1] systemd[1]: Finished Load Kernel Modules.
[[0;32m OK [0m] Finished [0;1;39mLoad Kernel Modules[0m.
[ 22.798556][ T1] systemd[1]: Mounted FUSE Control File System.
[[0;32m OK [0m] Mounted [0;1;39mFUSE Control File System[0m.
[ 22.847054][ T1] systemd[1]: Mounted Kernel Configuration File System.
[[0;32m OK [0m] Mounted [0;1;39mKernel Configuration File System[0m.
[ 22.916998][ T1] systemd[1]: Starting Apply Kernel Variables...
Starting [0;1;39mApply Kernel Variables[0m...
[ 22.956794][ T1] systemd[1]: Started Journal Service.
[[0;32m OK [0m] Started [0;1;39mJournal Service[0m.
Starting [0;1;39mFlush Journal to Persistent Storage[0m...
[[0;32m OK [0m] Finished [0;1;39mApply Kernel Variables[0m.
[ 23.296817][ T1401] systemd-journald[1401]: Received client request to flush runtime journal.
[[0;32m OK [0m] Finished [0;1;39mLoad/Save Random Seed[0m.
[[0;32m OK [0m] Finished [0;1;39mCreate System Users[0m.
Starting [0;1;39mCreate Static Device Nodes in /dev[0m...
[[0;32m OK [0m] Finished [0;1;39mColdplug All udev Devices[0m.
Starting [0;1;39mHelper to synchronize boot up for ifupdown[0m...
[[0;32m OK [0m] Finished [0;1;39mCreate Static Device Nodes in /dev[0m.
[[0;32m OK [0m] Reached target [0;1;39mLocal File Systems (Pre)[0m.
Starting [0;1;39mRule-based Manage…for Device Events and Files[0m...
[[0;32m OK [0m] Finished [0;1;39mFlush Journal to Persistent Storage[0m.
[[0;32m OK [0m] Started [0;1;39mRule-based Manager for Device Events and Files[0m.
[[0;32m OK [0m] Found device [0;1;39m/dev/ttyS0[0m.
[ 26.450445][ T1420] mtdblock: MTD device 'u-boot' is NAND, please consider using UBI block devices instead.
[ 26.491124][ T1424] mtdblock: MTD device 'u-boot-env' is NAND, please consider using UBI block devices instead.
[ 26.594337][ T1427] mtdblock: MTD device 'zImage' is NAND, please consider using UBI block devices instead.
[ 26.605500][ T1429] mtdblock: MTD device 'u-boot-env2' is NAND, please consider using UBI block devices instead.
[ 26.663885][ T1426] mtdblock: MTD device 'initrd' is NAND, please consider using UBI block devices instead.
[ 26.731962][ T1429] mtdblock: MTD device 'boot' is NAND, please consider using UBI block devices instead.
[ 26.786404][ T1425] mc: Linux media interface: v0.10
[ 27.133634][ T1421] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 27.165233][ T1421] sd 1:0:0:0: Attached scsi generic sg1 type 0
[ 27.189418][ T1421] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 27.492910][ T1425] usbcore: registered new interface driver snd-usb-audio
[ 27.755108][ T1456] Btrfs loaded, zoned=no, fsverity=no
[ 27.766872][ T1421] BTRFS: device fsid bd9b4047-5599-4f64-b90d-119b70bcf29d devid 1 transid 399 /dev/sdb scanned by systemd-udevd (1421)
[ 27.901144][ T1424] BTRFS: device fsid bd9b4047-5599-4f64-b90d-119b70bcf29d devid 2 transid 399 /dev/sdc scanned by systemd-udevd (1424)
[[0;32m OK [0m] Found device [0;1;39mWDC_WD800JD-75MSA3 5[0m.
Activating swap [0;1;39m/dev/disk/…1cde-44c3-89a7-2733df823c76[0m...
[ 28.492444][ T1460] Adding 488444k swap on /dev/sda5. Priority:-2 extents:1 across:488444k FS
[[0;32m OK [0m] Found device [0;1;39mWDC_WD800JD-75MSA3 1[0m.
[[0;32m OK [0m] Activated swap [0;1;39m/dev/disk/b…5-1cde-44c3-89a7-2733df823c76[0m.
[[0;32m OK [0m] Reached target [0;1;39mSwap[0m.
Starting [0;1;39mFile System Check…7b5c-4e53-a7dd-21d251b98b49[0m...
[[0;32m OK [0m] Started [0;1;39mFile System Check Daemon to report status[0m.
[[0;32m OK [0m] Finished [0;1;39mFile System Check…f-7b5c-4e53-a7dd-21d251b98b49[0m.
[[0;32m OK [0m] Finished [0;1;39mHelper to synchronize boot up for ifupdown[0m.
Mounting [0;1;39m/boot[0m...
[ 31.226011][ T1468] ext2 filesystem being mounted at /boot supports timestamps until 2038-01-19 (0x7fffffff)
[[0;32m OK [0m] Mounted [0;1;39m/boot[0m.
[[0;32m OK [0m] Reached target [0;1;39mLocal File Systems[0m.
Starting [0;1;39mRaise network interfaces[0m...
Starting [0;1;39mCreate Volatile Files and Directories[0m...
[[0;32m OK [0m] Finished [0;1;39mCreate Volatile Files and Directories[0m.
[ 32.192951][ T1487] mvneta d0070000.ethernet eth0: PHY [d0072004.mdio-mii:00] driver [Marvell 88E1318S] (irq=POLL)
[ 32.204106][ T1487] mvneta d0070000.ethernet eth0: configuring for phy/rgmii-id link mode
Starting [0;1;39mNetwork Time Synchronization[0m...
Starting [0;1;39mUpdate UTMP about System Boot/Shutdown[0m...
[ 32.360001][ T1500] mvneta d0074000.ethernet eth1: PHY [d0072004.mdio-mii:01] driver [Marvell 88E1318S] (irq=POLL)
[ 32.395624][ T1500] mvneta d0074000.ethernet eth1: configuring for phy/rgmii-id link mode
[[0;1;31mFAILED[0m] Failed to start [0;1;39mRaise network interfaces[0m.
See 'systemctl status networking.service' for details.
[[0;32m OK [0m] Finished [0;1;39mUpdate UTMP about System Boot/Shutdown[0m.
[[0;32m OK [0m] Reached target [0;1;39mNetwork[0m.
[[0;32m OK [0m] Reached target [0;1;39mNetwork is Online[0m.
[[0;32m OK [0m] Started [0;1;39mNetwork Time Synchronization[0m.
[[0;32m OK [0m] Reached target [0;1;39mSystem Initialization[0m.
[[0;32m OK [0m] Started [0;1;39mDaily Cleanup of Temporary Directories[0m.
[[0;32m OK [0m] Reached target [0;1;39mSystem Time Set[0m.
[[0;32m OK [0m] Reached target [0;1;39mSystem Time Synchronized[0m.
[[0;32m OK [0m] Started [0;1;39mDaily apt download activities[0m.
[[0;32m OK [0m] Started [0;1;39mDaily apt upgrade and clean activities[0m.
[[0;32m OK [0m] Started [0;1;39mPeriodic ext4 Onli…ata Check for All Filesystems[0m.
[[0;32m OK [0m] Started [0;1;39mDiscard unused blocks once a week[0m.
[[0;32m OK [0m] Started [0;1;39mDaily rotation of log files[0m.
[[0;32m OK [0m] Started [0;1;39mDaily man-db regeneration[0m.
[[0;32m OK [0m] Reached target [0;1;39mTimers[0m.
[[0;32m OK [0m] Listening on [0;1;39mAvahi mDNS/DNS-SD Stack Activation Socket[0m.
[[0;32m OK [0m] Listening on [0;1;39mD-Bus System Message Bus Socket[0m.
[[0;32m OK [0m] Reached target [0;1;39mSockets[0m.
[[0;32m OK [0m] Reached target [0;1;39mBasic System[0m.
Starting [0;1;39mSave/Restore Sound Card State[0m...
Starting [0;1;39mAvahi mDNS/DNS-SD Stack[0m...
[[0;32m OK [0m] Started [0;1;39mRegular background program processing daemon[0m.
[[0;32m OK [0m] Started [0;1;39mD-Bus System Message Bus[0m.
Starting [0;1;39mRemove Stale Onli…t4 Metadata Check Snapshots[0m...
Starting [0;1;39mInitialize hardware monitoring sensors[0m...
Starting [0;1;39mSystem Logging Service[0m...
Starting [0;1;39mSelf Monitoring a…g Technology (SMART) Daemon[0m...
Starting [0;1;39mOpenBSD Secure Shell server[0m...
Starting [0;1;39mUser Login Management[0m...
Starting [0;1;39mPermit User Sessions[0m...
[[0;32m OK [0m] Finished [0;1;39mSave/Restore Sound Card State[0m.
[[0;32m OK [0m] Reached target [0;1;39mSound Card[0m.
Starting [0;1;39mRotate log files[0m...
Starting [0;1;39mDaily man-db regeneration[0m...
[[0;32m OK [0m] Finished [0;1;39mPermit User Sessions[0m.
[[0;32m OK [0m] Started [0;1;39mGetty on tty1[0m.
[[0;32m OK [0m] Started [0;1;39mSerial Getty on ttyS0[0m.
[[0;32m OK [0m] Reached target [0;1;39mLogin Prompts[0m.
[[0;32m OK [0m] Finished [0;1;39mInitialize hardware monitoring sensors[0m.
Starting [0;1;39mfan speed regulator[0m...
[[0;32m OK [0m] Finished [0;1;39mRemove Stale Onli…ext4 Metadata Check Snapshots[0m.
[[0;32m OK [0m] Started [0;1;39mSystem Logging Service[0m.
[[0;32m OK [0m] Finished [0;1;39mRotate log files[0m.
[[0;32m OK [0m] Started [0;1;39mfan speed regulator[0m.
[[0;32m OK [0m] Started [0;1;39mUser Login Management[0m.
[[0;32m OK [0m] Started [0;1;39mAvahi mDNS/DNS-SD Stack[0m.
[[0;32m OK [0m] Started [0;1;39mShairport Sync - AirPlay Audio Receiver[0m.
[[0;32m OK [0m] Started [0;1;39mOpenBSD Secure Shell server[0m.
[[0;32m OK [0m] Started [0;1;39mSelf Monitoring an…ing Technology (SMART) Daemon[0m.
[[0;32m OK [0m] Reached target [0;1;39mMulti-User System[0m.
[[0;32m OK [0m] Reached target [0;1;39mGraphical Interface[0m.
[[0;32m OK [0m] Started [0;1;39mManage keyboard display[0m.
[[0;32m OK [0m] Started [0;1;39mManage LCD display[0m.
Starting [0;1;39mUpdate UTMP about System Runlevel Changes[0m...
[ 40.076729][ T1520] fbcon: Taking over console
Debian GNU/Linux 11 lenovo ttyS0
lenovo login:
|
Re: Mainline Debian on Iomega ix4-300d September 10, 2023 02:18PM |
Admin Registered: 13 years ago Posts: 18,575 |
I suspect this problem is systemd related.
So it did not get probe again.
I'd suggest either:
- Run the rootfs in Debian 12 and upgrade it to Debian 12.1 (hope this problem got resolved in the latest systemd version).
- Or switch to sysvinit to see if it is OK.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/10/2023 02:22PM by bodhi.
[ 16.557200][ T1] systemd[1]: systemd 247.3-7+deb11u4 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +ZSTD +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=unified) [ 16.582478][ T1] systemd[1]: Detected architecture arm. Welcome to [1mDebian GNU/Linux 11 (bullseye)[0m! [ 16.699111][ T1] systemd[1]: Set hostname to <lenovo>. [ 17.766166][ T37] platform gpio-leds: deferred probe pending [ 19.471848][ T1] systemd[1]: Queued start job for default target Graphical Interface. [ 20.165353][ C0] random: crng init done
So it did not get probe again.
I'd suggest either:
- Run the rootfs in Debian 12 and upgrade it to Debian 12.1 (hope this problem got resolved in the latest systemd version).
- Or switch to sysvinit to see if it is OK.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 09/10/2023 02:22PM by bodhi.
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 14, 2023 03:13PM |
I think the issue is this one but I din't find any solution
http://lists.infradead.org/pipermail/barebox/2015-April/023137.html
platform gpio-leds: deferred probe pending
http://lists.infradead.org/pipermail/barebox/2015-April/023137.html
|
Re: Mainline Debian on Iomega ix4-300d September 14, 2023 04:30PM |
Admin Registered: 13 years ago Posts: 18,575 |
alf45tar,
> http://lists.infradead.org/pipermail/barebox/2015-April/023137.html
Yes, that's a very good find! even though it is specific to barebox bootloader. It makes a lot of sense that it got to mainline Linux kernel eventually.
Because the GPIO LEDs were deferred probe but the kernel never tried to probe it later, that made me think there must be dependency not met somewhere. The above post explained it thouroughly.
Root cause:
The driver for GPIO SPI was not configured into the kernel. So the platform GPIO was deferred and waiting forever for the GPIO SPI to run first.
Both the mainline Debian kernel and my custom kernel did not include this config: CONFIG_GPIO_74X164.
Solution:
I'll add this in the next kernel release so the Iomega ix4-300d GPIO LEDs will work. If you'd like to file a Debian bug report then please do so. You can refer to this post in that bug report.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> http://lists.infradead.org/pipermail/barebox/2015-April/023137.html
Yes, that's a very good find! even though it is specific to barebox bootloader. It makes a lot of sense that it got to mainline Linux kernel eventually.
Because the GPIO LEDs were deferred probe but the kernel never tried to probe it later, that made me think there must be dependency not met somewhere. The above post explained it thouroughly.
Root cause:
The driver for GPIO SPI was not configured into the kernel. So the platform GPIO was deferred and waiting forever for the GPIO SPI to run first.
Both the mainline Debian kernel and my custom kernel did not include this config: CONFIG_GPIO_74X164.
Solution:
I'll add this in the next kernel release so the Iomega ix4-300d GPIO LEDs will work. If you'd like to file a Debian bug report then please do so. You can refer to this post in that bug report.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 16, 2023 10:33AM |
|
Re: Mainline Debian on Iomega ix4-300d September 16, 2023 02:17PM |
Admin Registered: 13 years ago Posts: 18,575 |
> I recompiled the mainline kernel with
>
>
> and now I have 5 leds on /sys/class/leds
Cool!
>
>
> They are working pretty well except
> ix4-300d:hddfail:red that it is always on.
Let me take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
>
>
> CONFIG_GPIO_74X164=m >>
> and now I have 5 leds on /sys/class/leds
Cool!
>
>
> ix4-300d:hdd:blue ix4-300d:hddfail:red > ix4-300d:power:white ix4-300d:sys:blue > ix4-300d:sysfail:red >>
> They are working pretty well except
> ix4-300d:hddfail:red that it is always on.
Let me take a look.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d September 16, 2023 03:34PM |
Admin Registered: 13 years ago Posts: 18,575 |
Try
To see the exact path and name of the leds:
and then see what is the current trigger:
And then try to turn it off:
And then try to turn it on
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
To see the exact path and name of the leds:
ls -l /sys/class/leds/
and then see what is the current trigger:
cat /sys/class/leds/ix4-300d:hdd:blue/trigger cat /sys/class/leds/ix4-300d:hddfail:red/trigger
And then try to turn it off:
echo none > /sys/class/leds/ix4-300d:hdd:blue/trigger echo none > /sys/class/leds/ix4-300d:hddfail:red/trigger
And then try to turn it on
echo default-on > /sys/class/leds/ix4-300d:hdd:blue/trigger
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
alf45tar
Re: Mainline Debian on Iomega ix4-300d September 16, 2023 04:19PM |
|
Re: Mainline Debian on Iomega ix4-300d November 12, 2023 07:09AM |
Registered: 5 months ago Posts: 3 |
Hello everybody
First thanks for this nice procedure to rewamp IX4-300D. I'm having one (iomega) in use and another one (lenovo) for this procedure to rewamp it (that I recently bought).
I'm using win 10 computer and putty serial to proceed.
I'm trying to follow nice procedure from alf45tar nevertheless as I'm from mechanical background I'm a bit lost during some undocumented steps (@ installation of debian when I need to choose full disk space or LVM and on the next steps if I need to use encryptation partition or not).
I reached also the step of the replacement the content of the flash-kernel database file. My question is : Should I keep what is already written inside and add all lines in the procedure ? (with # in front or not)
At that point I got sttuck.
Please keep in mind that I'm from mechanical background and I might not understand straight forward.
Thanks for you help as I'm in the middle of the river ;-)
First thanks for this nice procedure to rewamp IX4-300D. I'm having one (iomega) in use and another one (lenovo) for this procedure to rewamp it (that I recently bought).
I'm using win 10 computer and putty serial to proceed.
I'm trying to follow nice procedure from alf45tar nevertheless as I'm from mechanical background I'm a bit lost during some undocumented steps (@ installation of debian when I need to choose full disk space or LVM and on the next steps if I need to use encryptation partition or not).
I reached also the step of the replacement the content of the flash-kernel database file. My question is : Should I keep what is already written inside and add all lines in the procedure ? (with # in front or not)
At that point I got sttuck.
Please keep in mind that I'm from mechanical background and I might not understand straight forward.
Thanks for you help as I'm in the middle of the river ;-)
|
Re: Mainline Debian on Iomega ix4-300d November 13, 2023 03:50AM |
Registered: 5 months ago Posts: 3 |
|
Re: Mainline Debian on Iomega ix4-300d November 13, 2023 04:51PM |
Registered: 9 years ago Posts: 226 |
|
Re: Mainline Debian on Iomega ix4-300d November 14, 2023 04:21PM |
Admin Registered: 13 years ago Posts: 18,575 |
oleveque,
This thread is about installation of mainline Debian kernel for this NAS.
You might be also insterested in running custom kernel and rootfs that I release here for the Marvell MVEBU NAS (in general):
https://forum.doozan.com/read.php?2,32146
But you will need serial console connected to do the set up to boot this box using my rootfs in the release thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
This thread is about installation of mainline Debian kernel for this NAS.
You might be also insterested in running custom kernel and rootfs that I release here for the Marvell MVEBU NAS (in general):
https://forum.doozan.com/read.php?2,32146
But you will need serial console connected to do the set up to boot this box using my rootfs in the release thread.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d November 15, 2023 04:22PM |
Registered: 5 months ago Posts: 3 |
Hi
Thanks for the answers.
@Bodhi
So far I'm not sure what I should understand but if I'm correct you provided an already packaged customized for this device ? right
@Renojim
I was guessing if I should not be pointing to sda1. Am I right
Thanks for the answers.
@Bodhi
So far I'm not sure what I should understand but if I'm correct you provided an already packaged customized for this device ? right
@Renojim
I was guessing if I should not be pointing to sda1. Am I right
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 3.6T 0 disk
|-sda1 8:1 0 20G 0 part
| `-md0 9:0 0 20G 0 raid1
| |-md0_vg-BFDlv 253:0 0 4G 0 lvm
| `-md0_vg-vol1 253:1 0 16G 0 lvm
`-sda2 8:2 0 3.6T 0 part
`-md1 9:1 0 10.9T 0 raid5
|-md1p1 259:0 0 487.5M 0 part /boot
|-md1p2 259:1 0 10.9T 0 part /
`-md1p3 259:2 0 475.5M 0 part [SWAP]
sdb 8:16 1 495.5M 0 disk
`-sdb1 8:17 1 494M 0 part
sdc 8:32 0 3.6T 0 disk
|-sdc1 8:33 0 20G 0 part
| `-md0 9:0 0 20G 0 raid1
| |-md0_vg-BFDlv 253:0 0 4G 0 lvm
| `-md0_vg-vol1 253:1 0 16G 0 lvm
`-sdc2 8:34 0 3.6T 0 part
`-md1 9:1 0 10.9T 0 raid5
|-md1p1 259:0 0 487.5M 0 part /boot
|-md1p2 259:1 0 10.9T 0 part /
`-md1p3 259:2 0 475.5M 0 part [SWAP]
sdd 8:48 0 3.6T 0 disk
|-sdd1 8:49 0 20G 0 part
| `-md0 9:0 0 20G 0 raid1
| |-md0_vg-BFDlv 253:0 0 4G 0 lvm
| `-md0_vg-vol1 253:1 0 16G 0 lvm
`-sdd2 8:50 0 3.6T 0 part
`-md1 9:1 0 10.9T 0 raid5
|-md1p1 259:0 0 487.5M 0 part /boot
|-md1p2 259:1 0 10.9T 0 part /
`-md1p3 259:2 0 475.5M 0 part [SWAP]
sde 8:64 0 3.6T 0 disk
|-sde1 8:65 0 20G 0 part
| `-md0 9:0 0 20G 0 raid1
| |-md0_vg-BFDlv 253:0 0 4G 0 lvm
| `-md0_vg-vol1 253:1 0 16G 0 lvm
`-sde2 8:66 0 3.6T 0 part
`-md1 9:1 0 10.9T 0 raid5
|-md1p1 259:0 0 487.5M 0 part /boot
|-md1p2 259:1 0 10.9T 0 part /
`-md1p3 259:2 0 475.5M 0 part [SWAP]
|
Re: Mainline Debian on Iomega ix4-300d November 15, 2023 07:58PM |
Admin Registered: 13 years ago Posts: 18,575 |
oleveque,
> @Bodhi
> So far I'm not sure what I should understand but
> if I'm correct you provided an already packaged
> customized for this device ? right
Yes, the rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 in the link above (it's one of the sticky threads) is the Debian system that you can use to boot this box (and other Marvell armv7 boxes). The installation is manual, and need serial console. So it'll take some works to get it booting.
This thread here is about installing the kernel and rootfs from mainline Debian repo. Which is nice if the Debian installer already supports booting it (it seems not).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> @Bodhi
> So far I'm not sure what I should understand but
> if I'm correct you provided an already packaged
> customized for this device ? right
Yes, the rootfs Debian-5.13.8-mvebu-tld-1-rootfs-bodhi.tar.bz2 in the link above (it's one of the sticky threads) is the Debian system that you can use to boot this box (and other Marvell armv7 boxes). The installation is manual, and need serial console. So it'll take some works to get it booting.
This thread here is about installing the kernel and rootfs from mainline Debian repo. Which is nice if the Debian installer already supports booting it (it seems not).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d November 24, 2023 02:46PM |
Registered: 3 years ago Posts: 4 |
Great work on this guys. FWIW I had problems with this device back in the day (2013) where the unit did not boot after a firmware update (stuck 95%). Lenovo did not give support and would not honour the warranty despite proof of purchase etc. It laid dormant in the attic a few years before I learned stuff like hooking up the serial port etc to diagnose. Eventually I managed to figure out how to create a usb recovery drive and fix it. I downloaded stock firmwares and other stuff from lenovo before it disappeared so I am posting links here for anyone who wants original or recovery firmwares and the info I have on it to date. I used the original firmware and modded the unit to have entware but always wanted a pure debian unit. Even better, build openwrt with extroot so that the base OS is embedded.
https://github.com/5p0ng3b0b/ix4-300d
https://mega.nz/fm/bxUCHKAD
Is there enough info to build openwrt for this device yet?
Maybe modifying the config file for Linksys WRT1900AC v1 as a starting point.
https://github.com/5p0ng3b0b/ix4-300d
https://mega.nz/fm/bxUCHKAD
Is there enough info to build openwrt for this device yet?
Maybe modifying the config file for Linksys WRT1900AC v1 as a starting point.
|
Re: Debian bookworm on Iomega ix4-300d March 04, 2024 09:09PM |
Registered: 3 years ago Posts: 4 |
What a great read this post is!
Bought one of these units 10 years ago, it packed up after a year (hung on 95%) No support and Lenovo would not honour the 3yr warranty even after sending amazon purchase info. Everything lenovo I ever had has died, £1200 yoga laptop, 3 Q180 mini PCs, and 2 tablets (all poor soldering on GPU etc), but I digress! The NAS got forgotten and gathered dust in the loft for a few years until I revived it after learning how to make a recovery usb stick and even installed entware with a build environment to make arm static arm binaries (still can't get my head around cross compiling), to make it as close to a linux server as I ever could (I digress again).
TLDR don't buy Lenovo.
As someone who has made a few doorstops in the past messing with u-boot on embedded devices, here is my take on the subject so far. It might be helpful.
Whilst I have kept tabs on this thread, I found this walkthrough on github a couple of days ago.
https://github.com/alf45tar/ix4-300d
It gives good instructions and info, as well as ready made images for debian 12 install , so I gave it a go.
I ran into some issues along the way and worked through them with the help of this thread and a bit of googling.
I followed the walkthrough, but could not log in after creating root password and user after 1st reboot . I started install again and when I got to the shell and chroot part, I did a passwd command and created a user (more on chroot later). Prior to this, I got into doing some stuff with the u-boot environment as I wanted to easily go back to stock if it was not working. One thing I have learned is that you back up your variables, eg 'setenv bootcmd_old $bootcmd'. I makes it easier especially with long commands. I have done 'if then' stuff in the past on u-boot for android dual boot and fallback redundancy, so I set up u-boot environment with this sort of stuff in mind for the future. I willl document what I have done and observed so far.
Firstly, if anyone has already messed up their bootcmd, it is not easy to fix due to serial buffer etc. You can restore it like this.
Here is what I did to set up u-boot. I used extra variables to make it easy to change stuff like boot device, boot delay etc
without having to redo long commands that are prone to typos! When you read through, you will see the logic.
Afterwards, I was able to easily tweak things later once things were working with:
One thing I observed was that it did not matter which version of mtdparts I used, the boot process always detected pxa3xx_nand-0.
With the u-boot stuff done to a point, I set about the initial setup and scripted the whole walkthrough thing and some other additions to make it easy for me (and you) to repeat the process hassle free. After following the walkthough, going though the netinstall, I got to the part where you open a shell to chroot.
Bought one of these units 10 years ago, it packed up after a year (hung on 95%) No support and Lenovo would not honour the 3yr warranty even after sending amazon purchase info. Everything lenovo I ever had has died, £1200 yoga laptop, 3 Q180 mini PCs, and 2 tablets (all poor soldering on GPU etc), but I digress! The NAS got forgotten and gathered dust in the loft for a few years until I revived it after learning how to make a recovery usb stick and even installed entware with a build environment to make arm static arm binaries (still can't get my head around cross compiling), to make it as close to a linux server as I ever could (I digress again).
TLDR don't buy Lenovo.
As someone who has made a few doorstops in the past messing with u-boot on embedded devices, here is my take on the subject so far. It might be helpful.
Whilst I have kept tabs on this thread, I found this walkthrough on github a couple of days ago.
https://github.com/alf45tar/ix4-300d
It gives good instructions and info, as well as ready made images for debian 12 install , so I gave it a go.
I ran into some issues along the way and worked through them with the help of this thread and a bit of googling.
I followed the walkthrough, but could not log in after creating root password and user after 1st reboot . I started install again and when I got to the shell and chroot part, I did a passwd command and created a user (more on chroot later). Prior to this, I got into doing some stuff with the u-boot environment as I wanted to easily go back to stock if it was not working. One thing I have learned is that you back up your variables, eg 'setenv bootcmd_old $bootcmd'. I makes it easier especially with long commands. I have done 'if then' stuff in the past on u-boot for android dual boot and fallback redundancy, so I set up u-boot environment with this sort of stuff in mind for the future. I willl document what I have done and observed so far.
Firstly, if anyone has already messed up their bootcmd, it is not easy to fix due to serial buffer etc. You can restore it like this.
setenv part1 'nand read 0x40000 $kernel_start $kernel_size;nand read 0x2000000 $initrd_start $initrd_size;' setenv part2 'setenv bootargs $console $mtdparts $bootargs_root mem=512M ramdisk_size=$ramdisk_size ramdisk_blocksize=1024 ip=$bootargs_end $mvNetConfig;' setenv part3 'bootm 0x40000 0x2000000;' setenv boot_nand $part$part2$part3;setenv part1;setenv part2;setenv part3 setenv bootcmd $boot_nand saveenv
Here is what I did to set up u-boot. I used extra variables to make it easy to change stuff like boot device, boot delay etc
without having to redo long commands that are prone to typos! When you read through, you will see the logic.
setenv mtdparts $mtdparts_old setenv mtdparts_new mtdparts=pxa3xx_nand-0:0xe0000@0x0(uboot),0x20000@0xe0000(env),0x20000@0x100000(env2),0x400000@0x120000(zImage),0x400000@0x520000(initrd),0x3F200000@0xE00000(boot),0x40000000@0x0(flash) setenv boot_nand $bootcmd setenv hd_dev ide 2:1 setenv hd_root /dev/sda2 setenv hd_delay 10 setenv boot_hd 'ide reset;ext2load $hd_dev 40000 uImage;ext2load $hd_dev 2000000 uInitrd;setenv bootargs $console $mtdparts root=$hd_root rw rootdelay=$hd_delay;bootm 0x40000 0x2000000' setenv deb_install_net 'tftpboot uImage_di_ix4_300d_bookworm;bootm 0x2000000' setenv deb_install_usb 'ext2load usb 0:1 0x0040000 uImage_ix4_300d_bookworm; ext2load usb 0:1 0x2000000 uInitrd_ix4_300d_bookworm;setenv bootargs $console $mtdparts root=/dev/sda2 rw rootdelay=10;bootm 0x40000 0x2000000'I could now easily install via tfpt or USB from u-boot eg: 'run deb_install_net'.
Afterwards, I was able to easily tweak things later once things were working with:
setenv mtdparts $mtdparts_new setenv hd_root LABEL=rootfs setenv hd_delay 5 setenv bootcmd $boot_hdI was entering the saveenv command twice at each stage to ensure both copies were identicle.
One thing I observed was that it did not matter which version of mtdparts I used, the boot process always detected pxa3xx_nand-0.
[ 19.388903] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xd3 [ 19.395338] nand: Samsung NAND 1GiB 3,3V 8-bit [ 19.399823] nand: 1024 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64 [ 19.407535] marvell-nfc d00d0000.nand-controller: No minimum ECC strength, using 1b/512B [ 19.410024] at24 0-0050: 8192 byte 24c64 EEPROM, writable, 1 bytes/write [ 19.549743] Bad block table found at page 524224, version 0x01 [ 19.594060] Bad block table found at page 524160, version 0x01 [ 19.610770] nand_read_bbt: bad block at 0x0000111a0000 [ 19.615999] nand_read_bbt: bad block at 0x00001a6a0000 [ 19.616010] nand_read_bbt: bad block at 0x00001bc80000 [ 19.616026] nand_read_bbt: bad block at 0x00002f4a0000 [ 19.616040] nand_read_bbt: bad block at 0x00003ec60000 [ 19.664737] 6 fixed-partitions partitions found on MTD device pxa3xx_nand-0 [ 19.671776] Creating 6 MTD partitions on "pxa3xx_nand-0": [ 19.677273] 0x000000000000-0x0000000e0000 : "u-boot" [ 19.705285] 0x0000000e0000-0x000000100000 : "u-boot-env" [ 19.711783] 0x000000100000-0x000000120000 : "u-boot-env2" [ 19.718528] 0x000000120000-0x000000520000 : "zImage" [ 19.727087] 0x000000520000-0x000000920000 : "initrd" [ 19.733413] 0x000000e00000-0x000040000000 : "boot" [ 19.994103] marvell-cesa d0090000.crypto: CESA device successfully registeredWith the system fully booted, I can do 'fw_printenv' but 'fw_setenv' does not work even after trying 'flash_unlock /dev/mtd1' and 'flash_unlock /dev/mtd2'. It might be because of old uboot or broken setenv command. I intend to use the box to build new versions later when I get time.
With the u-boot stuff done to a point, I set about the initial setup and scripted the whole walkthrough thing and some other additions to make it easy for me (and you) to repeat the process hassle free. After following the walkthough, going though the netinstall, I got to the part where you open a shell to chroot.
mount --bind /dev /target/dev mount -t proc none /target/proc mount -t sysfs none /target/sys chroot /target /bin/shNow it is time to ensure root password is set and add a normal user by entering:
passwd useradd -m username passwd usernameNow I create a setup script with what needs to be done to get started.
nano /root/setup_server.sh
#!/bin/bash
apt update
apt install -y flash-kernel
cat <<EOF>>/etc/flash-kernel/db
Machine: Lenovo Iomega ix4-300d
Kernel-Flavors: armmp armmp-lpae
DTB-Id: armada-xp-lenovo-ix4-300d.dtb
DTB-Append: yes
U-Boot-Kernel-Address: 0x00008000
U-Boot-Initrd-Address: 0x0
Boot-Kernel-Path: /boot/uImage
Boot-Initrd-Path: /boot/uInitrd
Boot-DTB-Path: /boot/dtb
Required-Packages: u-boot-tools
Bootloader-Sets-Incorrect-Root: no
EOF
update-initramfs -u
if [ "$(df -Th /dev/sda2 | tail -n -1 | awk '{print $2}')" = "ext4" ]; then e2label /dev/sda2 rootfs; fi
cat <<EOF>/etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors
/dev/mtd1 0x00000 0x20000 0x20000
/dev/mtd2 0x00000 0x20000 0x20000
EOF
cd /bin; rm sh; ln -s bash sh
echo "PermitRootLogin yes" >> /etc/ssh/sshd_config
mkdir -p /home/root; cp -r $HOME/.* /home/root/; export HOME=/home/root; cd $HOME
sed -i 's#:/root:#:/home/root:#' /etc/passwd
echo -e "alias ls='ls --color=auto'\neval $(dircolors -b)\nexport TERM=xterm-256color EDITOR=nano" >>.bashrc
echo "PS1='${debian_chroot:+($debian_chroot)}\[\033[01;32m\]\u@\h\[\033[00m\]:\[\033[01;34m\]\w\[\033[00m\]\$ '" >>.bashrc
apt install -y sudo net-tools xterm avahi-daemon smartmontools lm-sensors fancontrol
echo -e "i2c_mv64xxx\nadt7475\ndrivetemp" >>/etc/modules
cat <<EOF>/etc/fancontrol
# Configuration file generated by pwmconfig, changes will be lost
INTERVAL=10
DEVPATH=hwmon1=devices/platform/soc/soc:internal-regs/d0011000.i2c/i2c-0/0-002e hwmon3=devices/platform/soc/soc:pcie@82000000/pci0000:00/0000:00:01.0/0000:01:00.0/ata2/host1/target1:0:0/1:0:0:0
DEVNAME=hwmon1=adt7473 hwmon3=drivetemp
FCTEMPS= hwmon1/pwm1=hwmon3/temp1_input
FCFANS= hwmon1/pwm1=hwmon1/fan1_input
MINTEMP= hwmon1/pwm1=20
MAXTEMP= hwmon1/pwm1=60
MINSTART= hwmon1/pwm1=150
MINSTOP= hwmon1/pwm1=0
EOF
systemctl restart fancontrol.service
systemctl restart fancontrol.service
echo 7 > /sys/class/i2c-adapter/i2c-0/0-002e/hwmon/hwmon1/pwm1_auto_channels_temp
echo 2 > /sys/class/i2c-adapter/i2c-0/0-002e/hwmon/hwmon1/pwm1_enable
apt install -y python3-periphery python3-pil python3-psutil
mkdir -p /opt/ix4-300d
wget -P /opt/ix4-300d https://raw.githubusercontent.com/alf45tar/ix4-300d/main/lcd.py
cat <<EOF>/etc/systemd/system/lcd.service
[Unit]
Description=Manage LCD display
After=default.target
[Service]
ExecStart=python3 /opt/ix4-300d/lcd.py
[Install]
WantedBy=default.target
EOF
systemctl daemon-reload
systemctl enable lcd.service
systemctl start lcd.service
apt install -y evtest
mkdir /opt/ix4-300d
wget -P /opt/ix4-300d https://raw.githubusercontent.com/alf45tar/ix4-300d/main/kbdactions.sh
chmod 755 /opt/ix4-300d/kbdactions.sh
cat <<EOF> /opt/ix4-300d/kbdactions.sh
#!/bin/bash
device='/dev/input/event0'
event_select_press='*code 314 (BTN_SELECT), value 1*'
event_select_release='*code 314 (BTN_SELECT), value 0*'
event_scroll_down_press='*code 178 (KEY_SCROLLDOWN), value 1*'
event_scroll_down_release='*code 178 (KEY_SCROLLDOWN), value 0*'
event_power='*code 116 (KEY_POWER), value 1*'
event_restart='*code 408 (KEY_RESTART), value 1*'
evtest "$device" | while read line; do
case $line in
($event_select_press) systemctl is-active --quiet webmin.service && systemctl stop webmin.service || systemctl restart webmin.service ;;
($event_select_release) echo "SELECT release" ;;
($event_scroll_down_press) systemctl restart lcd.service ;;
($event_scroll_down_release) echo "SCROLl DOWN release" ;;
($event_power) echo "POWER" ;;
($event_restart) echo "RESTART" ;;
esac
done
EOF
cat <<EOF> /etc/systemd/system/kbdactions.service
[Unit]
Description=Manage keyboard display
After=default.target
[Service]
ExecStart=/opt/ix4-300d/kbdactions.sh
[Install]
WantedBy=default.target
EOF
systemctl daemon-reload
systemctl enable kbdactions.service
systemctl start kbdactions.service
wget https://raw.githubusercontent.com/alf45tar/ix4-300d/main/linux-image-6.1.0-12-armmp-lpae_6.1.52-2_armhf.deb
dpkg -i linux-image-6.1.0-12-armmp-lpae_6.1.52-2_armhf.deb
apt install -y gpiod
cat <<EOF>/etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet dhcp
auto eth1
iface eth1 inet static
address 169.254.1.1
netmask 255.255.0.0
gateway 169.254.1.254
EOF
Have fun and keep fighting the fight!
|
Re: Debian bookworm on Iomega ix4-300d March 04, 2024 10:31PM |
Admin Registered: 13 years ago Posts: 18,575 |
scraamble,
> With the system fully booted, I can do
> 'fw_printenv' but 'fw_setenv' does not work even
> after trying 'flash_unlock /dev/mtd1' and
> 'flash_unlock /dev/mtd2'. It might be because of
> old uboot or broken setenv command. I intend to
> use the box to build new versions later when I get
> time.
There are 2 reasons why you could not do fw_setenv. The bootargs mtdparts was apparently not accepted by the kernel. And the current DTS specified that these areas are read-only. There is no need to build new u-boot version to have read/write access for the envs in Debian.
I'm sure what's need to be done will show in the bootlog. Please post output of dmesg here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> With the system fully booted, I can do
> 'fw_printenv' but 'fw_setenv' does not work even
> after trying 'flash_unlock /dev/mtd1' and
> 'flash_unlock /dev/mtd2'. It might be because of
> old uboot or broken setenv command. I intend to
> use the box to build new versions later when I get
> time.
There are 2 reasons why you could not do fw_setenv. The bootargs mtdparts was apparently not accepted by the kernel. And the current DTS specified that these areas are read-only. There is no need to build new u-boot version to have read/write access for the envs in Debian.
I'm sure what's need to be done will show in the bootlog. Please post output of dmesg here.
dmesg
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: Mainline Debian on Iomega ix4-300d March 06, 2024 06:45AM |
Registered: 3 years ago Posts: 4 |
Bodhi,
Thanks, teach a man to fish and all that. I figured it out.
It was because I was using kernel from:
https://raw.githubusercontent.com/alf45tar/ix4-300d/main/linux-image-6.1.0-12-armmp-lpae_6.1.52-2_armhf.deb
I updated to 6.7.5 kernel and all is good. I can now use fw_setenv.
I am discovering some issues along the way. I will attempt to resolve them. One notable issue so far is the MAC addresses from u-boot are not passed to the kernel (at least for me). I made a temp hack until I figure it out.
Thank you again!
Thanks, teach a man to fish and all that. I figured it out.
[ 0.000000] Kernel command line: console=ttyS0,115200 mtdparts=pxa3xx_nand-0:0x20000@0xe0000(env),0x20000@0x100000(env2),0x400000@0x120000(zImage),0x400000@0x520000(initrd),0x3F200000@0xE00000(boot),0x40000000@0x0(flash) root=LABEL=rootfs rw rootdelay=5 [ 0.000000] Unknown kernel command line parameters "mtdparts=pxa3xx_nand-0:0x20000@0xe0000(env),0x20000@0x100000(env2),0x400000@0x120000(zImage),0x400000@0x520000(initrd),0x3F200000@0xE00000(boot),0x40000000@0x0(flash)", will be passed to user space.
It was because I was using kernel from:
https://raw.githubusercontent.com/alf45tar/ix4-300d/main/linux-image-6.1.0-12-armmp-lpae_6.1.52-2_armhf.deb
I updated to 6.7.5 kernel and all is good. I can now use fw_setenv.
I am discovering some issues along the way. I will attempt to resolve them. One notable issue so far is the MAC addresses from u-boot are not passed to the kernel (at least for me). I made a temp hack until I figure it out.
nano /opt/ix4-300d/fixmac.sh #!/bin/bash ip link set dev eth0 down ip link set dev eth0 address $(fw_printenv | grep ^ethaddr | cut -d'=' -f2) ip link set dev eth0 up ip link set dev eth1 down ip link set dev eth1 address $(fw_printenv | grep ^eth1addr | cut -d'=' -f2) ip link set dev eth1 up systemctl restart networking.serviceThen create service to run at boot.
nano /etc/systemd/system/fixmac.service [Unit] Description=Fix eth0 and eth1 Mac addresses [Service] Type=simple ExecStart=/opt/ix4-300d/fixmac.sh [Install] WantedBy=default.targetGet service running.
systemctl daemon-reload systemctl enable fixmac.service systemctl start fixmac.serviceI am currently investigating nothing in /sys/class/leds. I suspect the dtb file. The one I got from the walkthough site was not the same as 6.7.1. Converting both to dts and running a diff gave me:
diff armada-xp-lenovo-ix4-300d.dts armada-xp-lenovo-ix4-300d.dts2 302a303 > interrupts = <0x5d 0x26>; 892,893c893,894 < gpio-sck = <0x1e 0x19 0x01>; < gpio-mosi = <0x1d 0x0f 0x01>; --- > sck-gpios = <0x1e 0x19 0x01>; > mosi-gpios = <0x1d 0x0f 0x01>;I will have to keep digging.
Thank you again!
|
Re: Mainline Debian on Iomega ix4-300d March 06, 2024 01:27PM |
Admin Registered: 13 years ago Posts: 18,575 |
scraamble,
The persistent MAC address problem is common to most of these NAS. Most of the Marvell Armada SoC boxes, regardless from which vendor, use the same u-boot code base from Marvell. I have a similar work around in my released rootfs.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
The persistent MAC address problem is common to most of these NAS. Most of the Marvell Armada SoC boxes, regardless from which vendor, use the same u-boot code base from Marvell. I have a similar work around in my released rootfs.
Quote
https://forum.doozan.com/read.php?2,32146
Note 6. Persistent MAC address (Optional)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
