2023.04 U-Boot Kirkwood

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 20, 2024 05:45PM

Admin
Registered: 14 years ago
Posts: 19,931

AleXSR700 Wrote:
-------------------------------------------------------
> Quick question: is this only for NSA325 or also
> the NSA325v2?

Yes, it is for both. The NSA325 and NSA325v2 are basically identical. Only the form factor is different.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

n325

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 22, 2024 09:40PM

Registered: 5 years ago
Posts: 7

Hi bodhi - My NSA325 returns the following for the command "cat /etc/fw_env.config"

# MTD device name Device offset Env. size Flash sector size Number of sectors
# NAND example
/dev/mtd1 0x0000 0x20000 0x20000 4

cat /proc/mtd returns

mtd0: 00100000 00020000 "uboot"
mtd1: 00080000 00020000 "uboot_env"
mtd2: 00080000 00020000 "key_store"
mtd3: 00080000 00020000 "info"
mtd4: 00a00000 00020000 "etc"
mtd5: 00a00000 00020000 "kernel_1"
mtd6: 02fc0000 00020000 "rootfs1"
mtd7: 00a00000 00020000 "kernel_2"
mtd8: 02fc0000 00020000 "rootfs2"

dmesg | grep -i 'bad' returns nothing

Can I move forward with the flashing? Thank you for your help!

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 12:18AM

Admin
Registered: 14 years ago
Posts: 19,931

n325,

> Hi bodhi - My NSA325 returns the following for the
> command "cat /etc/fw_env.config"
>
> # MTD device name Device offset Env.
> size Flash sector size Number of
> sectors
> # NAND example
> /dev/mtd1 0x0000 0x20000 0x20000 4
>
> cat /proc/mtd returns
>
> mtd0: 00100000 00020000 "uboot"
> mtd1: 00080000 00020000 "uboot_env"
> mtd2: 00080000 00020000 "key_store"
> mtd3: 00080000 00020000 "info"
> mtd4: 00a00000 00020000 "etc"
> mtd5: 00a00000 00020000 "kernel_1"
> mtd6: 02fc0000 00020000 "rootfs1"
> mtd7: 00a00000 00020000 "kernel_2"
> mtd8: 02fc0000 00020000 "rootfs2"
>
> dmesg | grep -i 'bad' returns nothing

Are you running stock u-boot? and running Debian on USB or HDD rootfs?

Please post output of

dmesg

So I can see the complete picture, before I can advise further.

If you have serial console, then post the serial entire boot log (no need to post dmesg if you do this).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

n325

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 08:52AM

Registered: 5 years ago
Posts: 7

I believe it's the stock u-boot. Here is the output from dmesg.

,0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) root=/dev/nfs rw init=/init
PID hash table entries: 2048 (order: 11, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 512MB = 512MB total
Memory: 506752KB available (5360K code, 302K data, 2872K init, 0K highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Console: colour dummy device 80x30
Calibrating delay loop... 1599.07 BogoMIPS (lpj=7995392)
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
NET: Registered protocol family 16
Feroceon L2: Enabling L2
Feroceon L2: Cache support initialised.
invoking softwareStaggeredSpinUp()..., it will delay 5 seconds to spin up the second harddisk

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 02:04PM

Admin
Registered: 14 years ago
Posts: 19,931

So your system is all stock.

Yes you can install new u-boot and Debian rootfs.

But I would recommend to connect serial console during installation to make sure you can have a recovery path, in case something goes wrong.

Quote
Installation Steps
A. Preparation

A.1. UART booting

It is strongly recommmended that you try to run kwboot to test this boot image with UART booting before flashing to NAND. This is the rescue path when and if the flashing goes wrong for some reason. See example here. And to download latest ARM kwboot binary for UART booting see here.

Of course, you can do it blind, but prepare to connect serial console if you cannot boot after installation. And remember to keep the log of the entire session (on the terminal) when you flash u-boot and prepare the rootfs.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

n325

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 23, 2024 03:09PM

Registered: 5 years ago
Posts: 7

Thank you. I do have access to a serial console so will follow that approach.

Reply Quote

n325

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 26, 2024 07:53PM

Registered: 5 years ago
Posts: 7

I successfully competed the process and the device now booted into Debian. Thank you bodhi for your help!

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 27, 2024 01:56PM

Admin
Registered: 14 years ago
Posts: 19,931

Cool!

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

n325

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 28, 2024 02:39PM

Registered: 5 years ago
Posts: 7

I found the following services failed. How can I fix these services?

root@debian:/# systemctl list-units --failed
UNIT LOAD ACTIVE SUB DESCRIPTION
* cockpit.service loaded failed failed Cockpit Web Service
* systemd-journal-flush.service loaded failed failed Flush Journal to Persistent Storage
* systemd-journald.service loaded failed failed Journal Service
* systemd-logind.service loaded failed failed User Login Management
* systemd-udevd.service loaded failed failed Rule-based Manager for Device Events and Files
* systemd-journald-dev-log.socket loaded failed failed Journal Socket (/dev/log)
* systemd-journald.socket loaded failed failed Journal Socket
* systemd-udevd-control.socket loaded failed failed udev Control Socket
* systemd-udevd-kernel.socket loaded failed failed udev Kernel Socket

LOAD = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB = The low-level unit activation state, values depend on unit type.
9 loaded units listed.

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 28, 2024 03:45PM

Admin
Registered: 14 years ago
Posts: 19,931

> I found the following services failed. How can I
> fix these services?

This basic rootfs init system is sysvinit.

Are you running systemd? If you have not set up for systemd then you can use uEnv.txt to run it

It was mentioned in the installation instruction.

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

Note 5 (Optional):

Note 5.1. To boot with systemd

After loged into Debian, run:

apt-get install systemd
And then add parameter init=/usr/bin/systemd to your u-boot env bootargs.

- For example,
fw_setenv set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts init=/usr/bin/systemd'

- Or, if you are booting with my latest u-boot images you can also use the uEnv.txt capability to do this. In the default envs, custom_params is a variable that allows you to add extra bootargs. So add the following line to uEnv.txt:
custom_params=earlyprintk=serial init=/usr/bin/systemd

While in Debian,

cd /boot
echo "custom_params=earlyprintk=serial init=/usr/bin/systemd" > uEnv.txt
sync

And reboot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

n325

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
May 28, 2024 04:41PM

Registered: 5 years ago
Posts: 7

bodhi Wrote:
-------------------------------------------------------
> > I found the following services failed. How can
> I
> > fix these services?
>
> This basic rootfs init system is sysvinit.
>
> Are you running systemd? If you have not set up
> for systemd then you can use uEnv.txt to run it
>
> It was mentioned in the installation instruction.
>
>

Quote
https://forum.doozan.com/read.php?2,12096
>
> Note 5 (Optional):
>
> Note 5.1. To boot with systemd
>
> After loged into Debian, run:
>
> apt-get install systemd
> And then add parameter init=/usr/bin/systemd to
> your u-boot env bootargs.
>
> - For example,
> fw_setenv set_bootargs 'setenv bootargs
> console=ttyS0,115200 root=LABEL=rootfs
> rootdelay=10 $mtdparts init=/usr/bin/systemd'
>
> - Or, if you are booting with my latest u-boot
> images you can also use the uEnv.txt capability to
> do this. In the default envs, custom_params is a
> variable that allows you to add extra bootargs. So
> add the following line to uEnv.txt:
> custom_params=earlyprintk=serial
> init=/usr/bin/systemd
>

>
> While in Debian,
>

> cd /boot
> echo "custom_params=earlyprintk=serial
> init=/usr/bin/systemd" > uEnv.txt
> sync
>

>
> And reboot.

Yes, I was running systemd. I actually upgraded to Debian 6.8.7 now and I don't see any failed services now. Thank you!

Reply Quote

MireQ

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 02:36PM

Registered: 9 months ago
Posts: 7

Hello. It's my first post on this forum. I have old NSA325 v2 and I would like to change software with new one from bodhi.
I am not totally newbie and know what is terminal, basic Linux commands, etc., but I need someone who can support me.

For instance, while I am trying to install U-Boot from this topic, after I sent command:
nanddump --noecc --omitoob -l 0x80000 -f mtd0.nsa325 /dev/mtd

I got answer:

nanddump: unrecognized option '--noecc'
Usage: nanddump [OPTIONS] MTD-device
Dumps the contents of a nand mtd partition

and I have no idea, how to solve it.

bodhi, could you please support me?

Greetings from Poland ;)

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 02:48PM

Admin
Registered: 14 years ago
Posts: 19,931

MireQ,

> I am not totally newbie and know what is terminal,
> basic Linux commands, etc., but I need someone who
> can support me.

Ask questions whenever you need!

>
> For instance, while I am trying to install U-Boot
> from this topic, after I sent command:
> nanddump --noecc --omitoob -l 0x80000 -f
> mtd0.nsa325 /dev/mtd
>
> I got answer:
>
> nanddump: unrecognized option '--noecc'
> Usage: nanddump [OPTIONS] MTD-device
> Dumps the contents of a nand mtd partition
>
> and I have no idea, how to solve it.

- Are you inside stock OS?
- The nanddump command has many old and new versions, so syntax or options might be different. You can try and see what the options are

nanddump --help

Or you can use nanddump from my uploaded tools tarball.

https://forum.doozan.com/read.php?3,27280

Quote

While in stock OS, you can download the following binpack so that the normal tools for use in nand installation will be available in the system. Since Dropbox use https, you can download it to an USB stick on another Linux box and copy this tarball to the stock OS (I'll upload this to my available storage here so stock wget can be used, when I can).

Dowload at Dropbox
linux-tools-installation-bodhi.tar.gz
md5:
e58f442411eb35e641d40ea0577e00ff linux-tools-installation-bodhi.tar.gz
sha256:
88dfa8eadb319e2e286320643a654bf89bff0b0d450562fce09938e7f3b0007d linux-tools-installation-bodhi.tar.gz
Date: May 18 00:31 PST

This binpack contains these files:
tools/
tools/busybox
tools/e2fsck
tools/nanddump
tools/fw_printenv
tools/flash_erase
tools/nandwrite
tools/fw_env.config

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

MireQ

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 03:18PM

Registered: 9 months ago
Posts: 7

bodhi Wrote:
-------------------------------------------------------
> MireQ,
>
> > I am not totally newbie and know what is
> terminal,
> > basic Linux commands, etc., but I need someone
> who
> > can support me.
>
> Ask questions whenever you need!
>
> >
> > For instance, while I am trying to install
> U-Boot
> > from this topic, after I sent command:
> > nanddump --noecc --omitoob -l 0x80000 -f
> > mtd0.nsa325 /dev/mtd
> >
> > I got answer:
> >
> > nanddump: unrecognized option '--noecc'
> > Usage: nanddump [OPTIONS] MTD-device
> > Dumps the contents of a nand mtd partition
> >
> > and I have no idea, how to solve it.
>
> - Are you inside stock OS?
> - The nanddump command has many old and new
> versions, so syntax or options might be different.
> You can try and see what the options are
>
>

> nanddump --help
>

>
> Or you can use nanddump from my uploaded tools
> tarball.
>
> https://forum.doozan.com/read.php?3,27280
>
>

Quote

While in stock OS, you can download the
> following binpack so that the normal tools for use
> in nand installation will be available in the
> system. Since Dropbox use https, you can download
> it to an USB stick on another Linux box and copy
> this tarball to the stock OS (I'll upload this to
> my available storage here so stock wget can be
> used, when I can).
>
> Dowload at Dropbox
> linux-tools-installation-bodhi.tar.gz
> md5:
> e58f442411eb35e641d40ea0577e00ff
> linux-tools-installation-bodhi.tar.gz
> sha256:
> 88dfa8eadb319e2e286320643a654bf89bff0b0d450562fce09938e7f3b0007d
> linux-tools-installation-bodhi.tar.gz
> Date: May 18 00:31 PST
>
> This binpack contains these files:
> tools/
> tools/busybox
> tools/e2fsck
> tools/nanddump
> tools/fw_printenv
> tools/flash_erase
> tools/nandwrite
> tools/fw_env.config

Thanks bodhi,
Yes, I am inside stock.
I can say that I have read few topics (about Debian/Rootfs, U-boot, also your binpack) and the initially tried to make few steps in these areas, but I have met problems:
1. I cannot copy tools to /usr/local/bin or /usr/sbin in stock OS because I receive info like this:
cp: can't create '/usr/local/bin/busybox': Read-only file system
and I don't know what I can do, so then I tried:
2. to change U-boot even I have not tools installed. I get info like I wrote above in my first post.
3. In the meantime I prepared, I hope correctly, an USB flash drive for booting from Stock U-boot, but didn't decide to follow this way and tried to install your U-boot.

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 03:44PM

Admin
Registered: 14 years ago
Posts: 19,931

MireQ,

> Yes, I am inside stock.
> I can say that I have read few topics (about
> Debian/Rootfs, U-boot, also your binpack) and the
> initially tried to make few steps in these areas,
> but I have met problems:
> 1. I cannot copy tools to /usr/local/bin or
> /usr/sbin in stock OS because I receive info like
> this:
> cp: can't create '/usr/local/bin/busybox':
> Read-only file system
> and I don't know what I can do, so then I tried:

The binaries can be run directly, there is no need to copy them to /usr/local/bin or /usr/sbin. So extract it to /tmp (in RAM), or some folder like /locadisk. If the root / is also read only then use the /tmp folder.

mkdir /localdisk
cd /localdisk
tar -xf linux-tools-installation-bodhi.tar.gz

And execute it like this

cd /localdisk/tools
./nanddump > nanddump --noecc --omitoob -l 0x80000 -f mtd0.nsa325 /dev/mtd0

It's been a long time so I forgot what the syntax of this nanddump. If the above does not work, try this to see the options

./nanddump --help

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

MireQ

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 04:02PM

Registered: 9 months ago
Posts: 7

bodhi Wrote:
-------------------------------------------------------
> MireQ,
>
> > Yes, I am inside stock.
> > I can say that I have read few topics (about
> > Debian/Rootfs, U-boot, also your binpack) and
> the
> > initially tried to make few steps in these
> areas,
> > but I have met problems:
> > 1. I cannot copy tools to /usr/local/bin or
> > /usr/sbin in stock OS because I receive info
> like
> > this:
> > cp: can't create '/usr/local/bin/busybox':
> > Read-only file system
> > and I don't know what I can do, so then I
> tried:
>
> The binaries can be run directly, there is no need
> to copy them to /usr/local/bin or /usr/sbin. So
> extract it to /tmp (in RAM), or some folder like
> /locadisk. If the root / is also read only then
> use the /tmp folder.
>
>

> mkdir /localdisk
> cd /localdisk
> tar -xf linux-tools-installation-bodhi.tar.gz
>

>
>
> And execute it like this
>
>

> cd /localdisk/tools
> ./nanddump > nanddump --noecc --omitoob -l 0x80000
> -f mtd0.nsa325 /dev/mtd0
>

>
Here I have answer: sh: ./nanddump: Text file busy

> It's been a long time so I forgot what the syntax
> of this nanddump. If the above does not work, try
> this to see the options
>
>

> ./nanddump --help
>

Here is the same: sh: ./nanddump: Text file busy

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 20, 2025 04:34PM

Admin
Registered: 14 years ago
Posts: 19,931

While in stock OS,

dmesg
cat /proc/mtd
cat /etc/fw_env.config
cd /localdisk/tools
ls -larth

And post the entire log here.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

MireQ

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 21, 2025 10:02AM

Registered: 9 months ago
Posts: 7

bodhi Wrote:
-------------------------------------------------------
> While in stock OS,
>
>

> dmesg
> cat /proc/mtd
> cat /etc/fw_env.config
> cd /localdisk/tools
> ls -larth
>

> And post the entire log here.

/localdisk/tools # dmesg

Access     Pretec   08GB REX100      1.00 PQ: 0 ANSI: 5
sd 2:0:0:0: [sdc] 15917056 512-byte logical blocks: (8.14 GB/7.58 GiB)
sd 2:0:0:0: [sdc] Write Protect is off
sd 2:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 2:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
sd 2:0:0:0: [sdc] Assuming drive cache: write through
sd 2:0:0:0: [sdc] Attached SCSI removable disk
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
svc: failed to register lockdv1 RPC service (errno 97).
GbE port 0: TxEnable WA - Enabled, deep=1, tx_en_bk=1


***************************************
*            HD1 stand by now!        *
***************************************

***************************************
*            HD0 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by loop0  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by zyfw_downloader !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************

#######################################
#              HD0 awaked by loop0  !        #
#######################################
---> HD0 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

#######################################
#              HD0 awaked by swapper  !        #
#######################################
---> HD0 back to green on, off blink

#######################################
#              HD1 awaked by swapper !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink

***************************************
*            HD0 stand by now!        *
***************************************

***************************************
*            HD1 stand by now!        *
***************************************
In usb_disconnect, and number is 1 .....
usb 2-1: USB disconnect, address 2

#######################################
#              HD0 awaked by loop0  !        #
#######################################
---> HD0 back to green on, off blink
FAT: bread failed in fat_clusters_flush
FAT: Directory bread(block 32768) failed
FAT: Directory bread(block 32769) failed
FAT: Directory bread(block 32770) failed
FAT: Directory bread(block 32771) failed
FAT: Directory bread(block 32772) failed
FAT: Directory bread(block 32773) failed
FAT: Directory bread(block 32774) failed
FAT: Directory bread(block 32775) failed

#######################################
#              HD1 awaked by sh !        #
sleep 5 seconds for staggered wake up
#######################################
---> HD1 back to green on, off blink
FAT: bread failed in fat_clusters_flush
FAT: bread failed in fat_clusters_flush
FAT: bread failed in fat_clusters_flush
xhci_hcd 0000:00:01.0: remove, state 1
In usb_disconnect, and number is 0 .....
usb usb2: USB disconnect, address 1
xhci_hcd 0000:00:01.0: Host controller not halted, aborting reset.
xhci_hcd 0000:00:01.0: USB bus 2 deregistered
xhci_hcd 0000:00:01.0: xHCI Host Controller
xhci_hcd 0000:00:01.0: new USB bus registered, assigned bus number 2
xhci_hcd 0000:00:01.0: irq 9, io mem 0xe0000000
usb usb2: config 1 interface 0 altsetting 0 endpoint 0x81 has no SuperSpeed companion descriptor
usb usb2: configuration #1 chosen from 1 choice
xHCI xhci_add_endpoint called for root hub
xHCI xhci_check_bandwidth called for root hub
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 4 ports detected
usb 2-1: new SuperSpeed USB device using xhci_hcd and address 2
In hub_port_init, and number is 2, retry 0, port 1 .....
usb 2-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 3:0:0:0: Direct-Access     Pretec   08GB REX100      1.00 PQ: 0 ANSI: 5
sd 3:0:0:0: [sdc] 15917056 512-byte logical blocks: (8.14 GB/7.58 GiB)
sd 3:0:0:0: [sdc] Write Protect is off
sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
sd 3:0:0:0: [sdc] Assuming drive cache: write through
sd 3:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 3:0:0:0: Attached scsi generic sg2 type 0
usb-storage: device scan complete
sd 3:0:0:0: [sdc] Assuming drive cache: write through
sd 3:0:0:0: [sdc] Attached SCSI removable disk
FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!

***************************************
*            HD1 stand by now!        *
***************************************

***************************************
*            HD0 stand by now!        *
***************************************

/localdisk/tools # cat /proc/mtd

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

/localdisk/tools # cat /etc/fw_env.config

# Configuration file for fw_(printenv/saveenv) utility.
# Up to two entries are valid, in this case the redundand
# environment sector is assumed present.
# Notice, that the "Number of sectors" is ignored on NOR.

# MTD device name       Device offset   Env. size       Flash sector size       Number of sectors
# NAND example
/dev/mtd1               0x0000          0x20000         0x20000                 4

/localdisk/tools # cd /localdisk/tools
/localdisk/tools # ls -larth

-rwxr-xr-x    1 root     root        1.5M Nov 15  2010 busybox
-rwxr-xr-x    1 root     root      768.6K Jun 20  2011 e2fsck
-rwxr-xr-x    1 root     root       28.9K Jun 30  2014 nandwrite
-rwxr-xr-x    1 root     root       25.0K Jun 30  2014 flash_erase
-rwxr-xr-x    1 root     root      652.8K May 17  2016 fw_printenv
-rw-r--r--    1 root     root         329 May 17  2016 fw_env.config
drwxrwxrwx    3 root     root           0 Jan 21 16:45 ..
drwxr-xr-x    2 root     root           0 Jan 21 16:45 .
-rwxr-xr-x    1 root     root           0 Jan 21 16:46 nanddump

Regarding to ls -larth command I can say that directly after executing binaries the nanddump size is 25.9K, but after I run the command nanddump --noecc --omitoob -l 0x80000 -f mtd0.nsa325 /dev/mtd0 its size becomes to 0 KB

===
moderator edit: please use code tags (formatted code button) to post log.

Edited 2 time(s). Last edit at 01/21/2025 01:34PM by bodhi.

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 21, 2025 01:36PM

Admin
Registered: 14 years ago
Posts: 19,931

MireQ,

Extract the tools tarball again. And

./nanddump --help

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

MireQ

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 23, 2025 04:44PM

Registered: 9 months ago
Posts: 7

bodhi, thanks,

Finally I got it, I installed both your u-boot and Debian on a usb drive.
Now my goal is to install OMV, but I have met new problems. How can I configure it to have DNS support in OMV and in the terminal?
I have 2 disks in NSA325 and would like to configure them as RAID1 preferably in OMV interface, but it can be in console. But for that I need DNS translation....
Now for the 3rd time I lost access to the box and I need to prepare the USB tomorrow again.
Could you please help me?
I know I am writing in wrong topic, but I don't want to start a new one.

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 23, 2025 06:43PM

Admin
Registered: 14 years ago
Posts: 19,931

MireQ,

> Finally I got it, I installed both your u-boot and
> Debian on a usb drive.

Cool!

> Now my goal is to install OMV, but I have met new
> problems. How can I configure it to have DNS
> support in OMV and in the terminal?
> I have 2 disks in NSA325 and would like to
> configure them as RAID1 preferably in OMV
> interface, but it can be in console. But for that
> I need DNS translation....

You can look at the Wiki thread fo topic about OMV

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

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

MireQ

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 27, 2025 12:36PM

Registered: 9 months ago
Posts: 7

bodhi Wrote:
-------------------------------------------------------
> MireQ,
>
> > Finally I got it, I installed both your u-boot
> and
> > Debian on a usb drive.
>
> Cool!
>
> > Now my goal is to install OMV, but I have met
> new
> > problems. How can I configure it to have DNS
> > support in OMV and in the terminal?
> > I have 2 disks in NSA325 and would like to
> > configure them as RAID1 preferably in OMV
> > interface, but it can be in console. But for
> that
> > I need DNS translation....
>
> You can look at the Wiki thread fo topic about
> OMV
>
> https://forum.doozan.com/read.php?2,23630

bodhi,

thank you very much. This was very helpful. Now I have installed everything I wanted. But there is one thing I don't understand. After restarting the box is unreachable on my network. It doesn't matter how it is restarted - from the OMV menu or from Terminal. The same is true after a power outage. After several re-installations, I discovered that there is a way around this. If the box is unreachable after a reboot, I unplug the box, remove the flash drive and put it back in, turn on the power, press the power button and everything is OK. Is it normal?

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 27, 2025 03:02PM

Admin
Registered: 14 years ago
Posts: 19,931

MireQ,

> thank you very much. This was very helpful. Now I
> have installed everything I wanted. But there is
> one thing I don't understand. After restarting the
> box is unreachable on my network.

I recall it is a known problem with the later versions of OMV (OMV reset the network file to its own upon reboot)

> It doesn't
> matter how it is restarted - from the OMV menu or
> from Terminal. The same is true after a power
> outage. After several re-installations, I
> discovered that there is a way around this. If the
> box is unreachable after a reboot, I unplug the
> box, remove the flash drive and put it back in,
> turn on the power, press the power button and
> everything is OK. Is it normal?

I can't remember where in this forum some users have discovered and had a work around. Too bad I did not save the link.

Try searching the forum for it.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

MireQ

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 28, 2025 04:57AM

Registered: 9 months ago
Posts: 7

bodhi,
Is not the problem at the boot level?
As I wrote above, the sequence “remove the power plug > remove the USB stick > wait a while > insert the USB stick > plug in the power > press the power button” works.
However, restarting from the console or menu, as well as after a power outage, does not work.

Shutting down the system from the menu and then pressing the power button also doesn’t work.

I know it sounds strange, but it seems that the key step is cutting the power and removing the USB stick.

Maybe you could take a look at my configuration?

For now, I don’t have a serial console, but I can buy a converter.

MireQ

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
January 28, 2025 01:29PM

Admin
Registered: 14 years ago
Posts: 19,931

MireQ,

> Is not the problem at the boot level?

At the kernel booting level, yes. Not u-boot. But there should be no problem with the network if you don't install OMV.

> For now, I don’t have a serial console, but I
> can buy a converter.

It's best that you connect serial console.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

Bobby

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
August 30, 2025 04:18AM

Registered: 4 years ago
Posts: 27

Are these bad blocks a problem?

# dmesg | grep -i 'bad'
[ 5.005612] Scanning device for bad blocks
[ 5.025558] Bad eraseblock 157 at 0x0000013a0000
[ 5.065124] Bad eraseblock 515 at 0x000004060000
[ 5.073605] Bad eraseblock 548 at 0x000004480000
[ 5.086856] Bad eraseblock 631 at 0x000004ee0000
[ 5.107856] Bad eraseblock 795 at 0x000006360000

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
August 30, 2025 12:39PM

Admin
Registered: 14 years ago
Posts: 19,931

> Are these bad blocks a problem?
>
> # dmesg | grep -i 'bad'
> [ 5.005612] Scanning device for bad blocks
> [ 5.025558] Bad eraseblock 157 at
> 0x0000013a0000
> [ 5.065124] Bad eraseblock 515 at
> 0x000004060000
> [ 5.073605] Bad eraseblock 548 at
> 0x000004480000
> [ 5.086856] Bad eraseblock 631 at
> 0x000004ee0000
> [ 5.107856] Bad eraseblock 795 at
> 0x000006360000

Not a problem. The new u-boot only uses the first 1 MB. That's 8 blocks (block 0 to 7).

These bad blocks above are in stock kernel and rootfs area. If you don't use stock FW, then no worry.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

Bobby

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
September 01, 2025 02:48AM

Registered: 4 years ago
Posts: 27

I wanted to update uBoot 2017 to 2023.

After step 7 I decided to check the new envs with my backup envs to see any differences. They are very different. Is it ok to proceed with an reboot or should I change something?

Backup

arcNumber=2097
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
custom_params=zswap.enabled=1
device=0:1
devices=usb ide mmc
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-nsa325.dtb
ethact=egiga0
ethaddr=EC:43:F6:AA:78:3E
if_netconsole=ping $serverip
ipaddr=192.168.0.231
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x1c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x1100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
machid=0x831
mainlineLinux=yes
mtdids=nand0=orion_nand
mtdparts=nand_mtd:0x100000(uboot),0x80000(uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
partition=nand0,2
preboot_nc=run if_netconsole start_netconsole
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
serverip=192.168.0.220
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
usb_ready_retry=15

New envs

baudrate=115200
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset
bootcmd_exec=if run load_uimage; then; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdelay=10
bootdev=usb
console=ttyS0,115200
device=0:1
devices=usb sata
disks=0 1 2 3
dtb_file=/boot/dts/kirkwood-nsa325.dtb
ethaddr=EC:43:F6:AA:78:3E
if_netconsole=ping $serverip
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_dtb_addr=0x2c00000
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_initrd_addr=0x01100000
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
load_uimage_addr=0x800000
mtdparts=mtdparts=orion_nand:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2)
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb reset; sleep 1; usb reset";  setenv scan_sata "sata init";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin serial,nc; setenv stdout serial,nc; setenv stderr serial,nc; version;
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=echo Initializing devices...; setenv init_usb "usb reset; sleep 1; usb reset"; setenv init_sata sata init;  setenv init_mmc mmc rescan; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices; do for disknum in $disks; do if test $uenv_loaded -eq 0; then setenv device_type $devtype; setenv disk_number $disknum; run uenv_read; fi; done; done;
uenv_read=echo Loading envs from $device_type $disk_number...; if load $device_type  $disk_number:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; echo ... envs loaded; fi

Reply Quote

bodhi

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
September 01, 2025 12:33PM

Admin
Registered: 14 years ago
Posts: 19,931

Bobby,

> After step 7 I decided to check the new envs with
> my backup envs to see any differences. They are
> very different. Is it ok to proceed with an reboot
> or should I change something?

Yes, the new u-boot envs are quite different from the 2017.07. This is due to some old commands are now obsolete, and there are new features. The new set of default envs will allow booting this box. The MAC address is important to retrofit so that it will be resilient with some old and buggy network routers.

There are other envs that you might have customized before with 2017.07 u-boot (e.g. network related info). But if you don't care to have ethernet working during u-boot booting then you can change them later after reboot.

> ipaddr=192.168.0.231
> serverip=192.168.0.220

Using the newly flashed default envs will have no problem booting. Also if you already connected serial console then it's even better, you can observe the new u-boot behavior.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Reply Quote

Bobby

Re: 2023.04 U-Boot Kirkwood - ZyXEL NSA325
September 01, 2025 01:07PM

Registered: 4 years ago
Posts: 27

Okay, rebooted.

I don't see errors during boot. But also no internet on the NSA325. I can login over ssh from my laptop, so LAN seems ok. But apt update gives 'Temporary failure resolving ' and ping gives ' Name or service not known'. So a DNS problem?

/etc/network/interfaces


rename /end0=eth0

auto lo eth0
iface lo inet loopback
# primary network interface
auto eth0
iface eth0 inet static
 address 192.168.2.21
 netmask 255.255.255.0
 gateway 192.168.2.1
 dns-nameservers  8.8.8.8 8.8.4.4 1.1.1.1

and Dmesg

[Mon Sep  1 19:48:08 2025] Booting Linux on physical CPU 0x0
[Mon Sep  1 19:48:08 2025] Linux version 6.15.2-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 PREEMPT Tue Jun 17 17:38:35 PDT 2025
[Mon Sep  1 19:48:08 2025] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[Mon Sep  1 19:48:08 2025] CPU: VIVT data cache, VIVT instruction cache
[Mon Sep  1 19:48:08 2025] OF: fdt: Machine model: ZyXEL NSA325
[Mon Sep  1 19:48:08 2025] Memory policy: Data cache writeback
[Mon Sep  1 19:48:08 2025] Zone ranges:
[Mon Sep  1 19:48:08 2025]   Normal   [mem 0x0000000000000000-0x000000001fffffff]
[Mon Sep  1 19:48:08 2025] Movable zone start for each node
[Mon Sep  1 19:48:08 2025] Early memory node ranges
[Mon Sep  1 19:48:08 2025]   node   0: [mem 0x0000000000000000-0x000000001fffffff]
[Mon Sep  1 19:48:08 2025] Initmem setup node 0 [mem 0x0000000000000000-0x000000001fffffff]
[Mon Sep  1 19:48:08 2025] OF: reserved mem: Reserved memory: No reserved-memory node in the DT
[Mon Sep  1 19:48:08 2025] pcpu-alloc: s0 r0 d131072 u131072 alloc=1*131072
[Mon Sep  1 19:48:08 2025] pcpu-alloc: [0] 0
[Mon Sep  1 19:48:08 2025] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:0x100000(uboot),0x80000(stock_uboot_env),0x80000(key_store),0x80000(info),0xA00000(etc),0xA00000(kernel_1),0x2FC0000(rootfs1),0xA00000(kernel_2),0x2FC0000(rootfs2) init=/bin/systemd
[Mon Sep  1 19:48:08 2025] printk: log buffer data + meta data: 131072 + 409600 = 540672 bytes
[Mon Sep  1 19:48:08 2025] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes, linear)
[Mon Sep  1 19:48:08 2025] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes, linear)
[Mon Sep  1 19:48:08 2025] Built 1 zonelists, mobility grouping on.  Total pages: 131072
[Mon Sep  1 19:48:08 2025] mem auto-init: stack:off, heap alloc:on, heap free:off
[Mon Sep  1 19:48:08 2025] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[Mon Sep  1 19:48:08 2025] rcu: Preemptible hierarchical RCU implementation.
[Mon Sep  1 19:48:08 2025]      Trampoline variant of Tasks RCU enabled.
[Mon Sep  1 19:48:08 2025]      Tracing variant of Tasks RCU enabled.
[Mon Sep  1 19:48:08 2025] rcu: RCU calculated value of scheduler-enlistment delay is 10 jiffies.
[Mon Sep  1 19:48:08 2025] RCU Tasks: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=1.
[Mon Sep  1 19:48:08 2025] RCU Tasks Trace: Setting shift to 0 and lim to 1 rcu_task_cb_adjust=1 rcu_task_cpu_ids=1.
[Mon Sep  1 19:48:08 2025] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[Mon Sep  1 19:48:08 2025] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[Mon Sep  1 19:48:08 2025] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 9556302233 ns
[Mon Sep  1 19:48:08 2025] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 10737418237ns
[Mon Sep  1 19:48:08 2025] Switching to timer-based delay loop, resolution 5ns
[Mon Sep  1 19:48:08 2025] Console: colour dummy device 80x30
[Mon Sep  1 19:48:08 2025] Calibrating delay loop (skipped), value calculated using timer frequency.. 400.00 BogoMIPS (lpj=2000000)
[Mon Sep  1 19:48:08 2025] CPU: Testing write buffer coherency: ok
[Mon Sep  1 19:48:08 2025] pid_max: default: 32768 minimum: 301
[Mon Sep  1 19:48:08 2025] LSM: initializing lsm=capability
[Mon Sep  1 19:48:08 2025] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[Mon Sep  1 19:48:08 2025] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[Mon Sep  1 19:48:08 2025] Setting up static identity map for 0x100000 - 0x100058
[Mon Sep  1 19:48:08 2025] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1
[Mon Sep  1 19:48:08 2025] rcu: Hierarchical SRCU implementation.
[Mon Sep  1 19:48:08 2025] rcu:         Max phase no-delay instances is 1000.
[Mon Sep  1 19:48:08 2025] Memory: 490488K/524288K available (11264K kernel code, 1653K rwdata, 5428K rodata, 1024K init, 445K bss, 31916K reserved, 0K cma-reserved)
[Mon Sep  1 19:48:08 2025] devtmpfs: initialized
[Mon Sep  1 19:48:08 2025] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[Mon Sep  1 19:48:08 2025] posixtimers hash table entries: 512 (order: -1, 2048 bytes, linear)
[Mon Sep  1 19:48:08 2025] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[Mon Sep  1 19:48:08 2025] prandom: seed boundary self test passed
[Mon Sep  1 19:48:08 2025] prandom: 100 self tests passed
[Mon Sep  1 19:48:08 2025] pinctrl core: initialized pinctrl subsystem
[Mon Sep  1 19:48:08 2025] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[Mon Sep  1 19:48:08 2025] DMA: preallocated 256 KiB pool for atomic coherent allocations
[Mon Sep  1 19:48:08 2025] audit: initializing netlink subsys (disabled)
[Mon Sep  1 19:48:08 2025] audit: type=2000 audit(0.080:1): state=initialized audit_enabled=0 res=1
[Mon Sep  1 19:48:08 2025] thermal_sys: Registered thermal governor 'step_wise'
[Mon Sep  1 19:48:08 2025] cpuidle: using governor ladder
[Mon Sep  1 19:48:08 2025] cpuidle: using governor menu
[Mon Sep  1 19:48:08 2025] Feroceon L2: Enabling L2
[Mon Sep  1 19:48:08 2025] Feroceon L2: Cache support initialised.
[Mon Sep  1 19:48:08 2025] No ATAGs?
[Mon Sep  1 19:48:08 2025] raid6: int32x8  gen()   152 MB/s
[Mon Sep  1 19:48:08 2025] raid6: int32x4  gen()   144 MB/s
[Mon Sep  1 19:48:09 2025] raid6: int32x2  gen()   193 MB/s
[Mon Sep  1 19:48:09 2025] raid6: int32x1  gen()   149 MB/s
[Mon Sep  1 19:48:09 2025] raid6: using algorithm int32x2 gen() 193 MB/s
[Mon Sep  1 19:48:09 2025] raid6: .... xor() 122 MB/s, rmw enabled
[Mon Sep  1 19:48:09 2025] raid6: using intx1 recovery algorithm
[Mon Sep  1 19:48:09 2025] SCSI subsystem initialized
[Mon Sep  1 19:48:09 2025] libata version 3.00 loaded.
[Mon Sep  1 19:48:09 2025] usbcore: registered new interface driver usbfs
[Mon Sep  1 19:48:09 2025] usbcore: registered new interface driver hub
[Mon Sep  1 19:48:09 2025] usbcore: registered new device driver usb
[Mon Sep  1 19:48:09 2025] pps_core: LinuxPPS API ver. 1 registered
[Mon Sep  1 19:48:09 2025] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[Mon Sep  1 19:48:09 2025] PTP clock support registered
[Mon Sep  1 19:48:09 2025] vgaarb: loaded
[Mon Sep  1 19:48:09 2025] clocksource: Switched to clocksource orion_clocksource
[Mon Sep  1 19:48:09 2025] VFS: Disk quotas dquot_6.6.0
[Mon Sep  1 19:48:09 2025] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[Mon Sep  1 19:48:09 2025] netfs: FS-Cache loaded
[Mon Sep  1 19:48:09 2025] NET: Registered PF_INET protocol family
[Mon Sep  1 19:48:09 2025] IP idents hash table entries: 8192 (order: 4, 65536 bytes, linear)
[Mon Sep  1 19:48:09 2025] tcp_listen_portaddr_hash hash table entries: 1024 (order: 0, 4096 bytes, linear)
[Mon Sep  1 19:48:09 2025] Table-perturb hash table entries: 65536 (order: 6, 262144 bytes, linear)
[Mon Sep  1 19:48:09 2025] TCP established hash table entries: 4096 (order: 2, 16384 bytes, linear)
[Mon Sep  1 19:48:09 2025] TCP bind hash table entries: 4096 (order: 3, 32768 bytes, linear)
[Mon Sep  1 19:48:09 2025] TCP: Hash tables configured (established 4096 bind 4096)
[Mon Sep  1 19:48:09 2025] MPTCP token hash table entries: 512 (order: 0, 6144 bytes, linear)
[Mon Sep  1 19:48:09 2025] UDP hash table entries: 256 (order: 1, 8192 bytes, linear)
[Mon Sep  1 19:48:09 2025] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes, linear)
[Mon Sep  1 19:48:09 2025] NET: Registered PF_UNIX/PF_LOCAL protocol family
[Mon Sep  1 19:48:09 2025] RPC: Registered named UNIX socket transport module.
[Mon Sep  1 19:48:09 2025] RPC: Registered udp transport module.
[Mon Sep  1 19:48:09 2025] RPC: Registered tcp transport module.
[Mon Sep  1 19:48:09 2025] RPC: Registered tcp-with-tls transport module.
[Mon Sep  1 19:48:09 2025] RPC: Registered tcp NFSv4.1 backchannel transport module.
[Mon Sep  1 19:48:09 2025] PCI: CLS 0 bytes, default 32
[Mon Sep  1 19:48:09 2025] Trying to unpack rootfs image as initramfs...
[Mon Sep  1 19:48:10 2025] Freeing initrd memory: 6132K
[Mon Sep  1 19:48:11 2025] Initialise system trusted keyrings
[Mon Sep  1 19:48:11 2025] Key type blacklist registered
[Mon Sep  1 19:48:11 2025] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[Mon Sep  1 19:48:11 2025] NFS: Registering the id_resolver key type
[Mon Sep  1 19:48:11 2025] Key type id_resolver registered
[Mon Sep  1 19:48:11 2025] Key type id_legacy registered
[Mon Sep  1 19:48:11 2025] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[Mon Sep  1 19:48:11 2025] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[Mon Sep  1 19:48:11 2025] fuse: init (API version 7.43)
[Mon Sep  1 19:48:11 2025] xor: measuring software checksum speed
[Mon Sep  1 19:48:11 2025]    arm4regs        :  1467 MB/sec
[Mon Sep  1 19:48:11 2025]    8regs           :   894 MB/sec
[Mon Sep  1 19:48:11 2025]    32regs          :  1267 MB/sec
[Mon Sep  1 19:48:11 2025] xor: using function: arm4regs (1467 MB/sec)
[Mon Sep  1 19:48:11 2025] async_tx: api initialized (async)
[Mon Sep  1 19:48:11 2025] Key type asymmetric registered
[Mon Sep  1 19:48:11 2025] Asymmetric key parser 'x509' registered
[Mon Sep  1 19:48:11 2025] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[Mon Sep  1 19:48:11 2025] io scheduler bfq registered
[Mon Sep  1 19:48:11 2025] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[Mon Sep  1 19:48:11 2025] gpio gpiochip0: Static allocation of GPIO base is deprecated, use dynamic allocation.
[Mon Sep  1 19:48:11 2025] gpio gpiochip1: Static allocation of GPIO base is deprecated, use dynamic allocation.
[Mon Sep  1 19:48:11 2025] ledtrig-cpu: registered to indicate activity on CPUs
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000: Parsing ranges property...
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1044000..0x00f1045fff -> 0x0000044000
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0x00f1080000..0x00f1081fff -> 0x0000080000
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000:      MEM 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000:       IO 0xffffffffffffffff..0x00fffffffe -> 0x0200000000
[Mon Sep  1 19:48:11 2025] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: root bus resource [bus 00-ff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: root bus resource [mem 0xf1044000-0xf1045fff] (bus address [0x00044000-0x00045fff])
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: root bus resource [mem 0xf1080000-0xf1081fff] (bus address [0x00080000-0x00081fff])
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: root bus resource [io  0x1000-0xeffff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: scanning bus
[Mon Sep  1 19:48:11 2025] PCI/pwrctrl: Skipping OF node: pcie
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: [11ab:6282] type 01 class 0x060400 PCIe Root Port
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: PCI bridge to [bus 00]
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0:   bridge window [io  0x0000-0x0fff]
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0:   bridge window [mem 0x00000000-0x000fffff]
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: vgaarb: pci_notify
[Mon Sep  1 19:48:11 2025] /mbus@f1000000/pcie@82000000/pcie@1,0: Fixed dependency cycle(s) with /mbus@f1000000/pcie@82000000/pcie@1,0/interrupt-controller
[Mon Sep  1 19:48:11 2025] PCI/pwrctrl: Skipping OF node: pcie
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: fixups for bus
[Mon Sep  1 19:48:11 2025] PCI: bus0: Fast back to back transfers disabled
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 0
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: scanning [bus 00-00] behind bridge, pass 1
[Mon Sep  1 19:48:11 2025] pci_bus 0000:01: scanning bus
[Mon Sep  1 19:48:11 2025] pci 0000:01:00.0: [1033:0194] type 00 class 0x0c0330 PCIe Endpoint
[Mon Sep  1 19:48:11 2025] pci 0000:01:00.0: BAR 0 [mem 0x90000000-0x90001fff 64bit]
[Mon Sep  1 19:48:11 2025] pci 0000:01:00.0: PME# supported from D0 D3hot
[Mon Sep  1 19:48:11 2025] pci 0000:01:00.0: PME# disabled
[Mon Sep  1 19:48:11 2025] 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 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[Mon Sep  1 19:48:11 2025] pci 0000:01:00.0: vgaarb: pci_notify
[Mon Sep  1 19:48:11 2025] pci_bus 0000:01: fixups for bus
[Mon Sep  1 19:48:11 2025] PCI: bus1: Fast back to back transfers disabled
[Mon Sep  1 19:48:11 2025] pci_bus 0000:01: bus scan returning with max=01
[Mon Sep  1 19:48:11 2025] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: bus scan returning with max=01
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]: assigned
[Mon Sep  1 19:48:11 2025] pci 0000:01:00.0: BAR 0 [mem 0xe0000000-0xe0001fff 64bit]: assigned
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: PCI bridge to [bus 01]
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0:   bridge window [mem 0xe0000000-0xe00fffff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: resource 4 [mem 0xf1040000-0xf1041fff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: resource 5 [mem 0xf1044000-0xf1045fff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: resource 6 [mem 0xf1080000-0xf1081fff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: resource 7 [mem 0xe0000000-0xefffffff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:00: resource 8 [io  0x1000-0xeffff]
[Mon Sep  1 19:48:11 2025] pci_bus 0000:01: resource 1 [mem 0xe0000000-0xe00fffff]
[Mon Sep  1 19:48:11 2025] pcieport 0000:00:01.0: vgaarb: pci_notify
[Mon Sep  1 19:48:11 2025] pcieport 0000:00:01.0: assign IRQ: got 0
[Mon Sep  1 19:48:11 2025] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[Mon Sep  1 19:48:11 2025] pcieport 0000:00:01.0: enabling bus mastering
[Mon Sep  1 19:48:11 2025] pcieport 0000:00:01.0: vgaarb: pci_notify
[Mon Sep  1 19:48:11 2025] pci 0000:00:01.0: enabling bus mastering
[Mon Sep  1 19:48:11 2025] mv_xor f1060800.xor: Marvell shared XOR driver
[Mon Sep  1 19:48:11 2025] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[Mon Sep  1 19:48:11 2025] mv_xor f1060900.xor: Marvell shared XOR driver
[Mon Sep  1 19:48:11 2025] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[Mon Sep  1 19:48:11 2025] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[Mon Sep  1 19:48:11 2025] printk: legacy console [ttyS0] disabled
[Mon Sep  1 19:48:11 2025] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 28, base_baud = 12500000) is a 16550A
[Mon Sep  1 19:48:11 2025] printk: legacy console [ttyS0] enabled
[Mon Sep  1 19:48:12 2025] loop: module loaded
[Mon Sep  1 19:48:12 2025] sata_mv f1080000.sata: version 1.28
[Mon Sep  1 19:48:12 2025] sata_mv f1080000.sata: slots 32 ports 2
[Mon Sep  1 19:48:12 2025] scsi host0: sata_mv
[Mon Sep  1 19:48:13 2025] scsi host1: sata_mv
[Mon Sep  1 19:48:13 2025] ata1: SATA max UDMA/133 irq 29 lpm-pol 0
[Mon Sep  1 19:48:13 2025] ata2: SATA max UDMA/133 irq 29 lpm-pol 0
[Mon Sep  1 19:48:13 2025] nand: device found, Manufacturer ID: 0xec, Chip ID: 0xf1
[Mon Sep  1 19:48:13 2025] nand: Samsung NAND 128MiB 3,3V 8-bit
[Mon Sep  1 19:48:13 2025] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[Mon Sep  1 19:48:13 2025] Scanning device for bad blocks
[Mon Sep  1 19:48:13 2025] Bad eraseblock 157 at 0x0000013a0000
[Mon Sep  1 19:48:13 2025] Bad eraseblock 515 at 0x000004060000
[Mon Sep  1 19:48:13 2025] Bad eraseblock 548 at 0x000004480000
[Mon Sep  1 19:48:13 2025] Bad eraseblock 631 at 0x000004ee0000
[Mon Sep  1 19:48:13 2025] Bad eraseblock 795 at 0x000006360000
[Mon Sep  1 19:48:13 2025] 9 cmdlinepart partitions found on MTD device orion_nand
[Mon Sep  1 19:48:13 2025] Creating 9 MTD partitions on "orion_nand":
[Mon Sep  1 19:48:13 2025] 0x000000000000-0x000000100000 : "uboot"
[Mon Sep  1 19:48:13 2025] 0x000000100000-0x000000180000 : "stock_uboot_env"
[Mon Sep  1 19:48:13 2025] 0x000000180000-0x000000200000 : "key_store"
[Mon Sep  1 19:48:13 2025] 0x000000200000-0x000000280000 : "info"
[Mon Sep  1 19:48:13 2025] 0x000000280000-0x000000c80000 : "etc"
[Mon Sep  1 19:48:13 2025] 0x000000c80000-0x000001680000 : "kernel_1"
[Mon Sep  1 19:48:13 2025] 0x000001680000-0x000004640000 : "rootfs1"
[Mon Sep  1 19:48:13 2025] 0x000004640000-0x000005040000 : "kernel_2"
[Mon Sep  1 19:48:13 2025] 0x000005040000-0x000008000000 : "rootfs2"
[Mon Sep  1 19:48:13 2025] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[Mon Sep  1 19:48:13 2025] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[Mon Sep  1 19:48:13 2025] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[Mon Sep  1 19:48:13 2025] mv643xx_eth: Set the PHY to fix link down
[Mon Sep  1 19:48:13 2025] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address ec:43:f6:aa:78:3e
[Mon Sep  1 19:48:13 2025] orion-ehci f1050000.ehci: EHCI Host Controller
[Mon Sep  1 19:48:13 2025] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[Mon Sep  1 19:48:13 2025] orion-ehci f1050000.ehci: irq 32, io mem 0xf1050000
[Mon Sep  1 19:48:13 2025] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[Mon Sep  1 19:48:13 2025] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.15
[Mon Sep  1 19:48:13 2025] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Mon Sep  1 19:48:13 2025] usb usb1: Product: EHCI Host Controller
[Mon Sep  1 19:48:13 2025] usb usb1: Manufacturer: Linux 6.15.2-kirkwood-tld-1 ehci_hcd
[Mon Sep  1 19:48:13 2025] usb usb1: SerialNumber: f1050000.ehci
[Mon Sep  1 19:48:13 2025] hub 1-0:1.0: USB hub found
[Mon Sep  1 19:48:13 2025] hub 1-0:1.0: 1 port detected
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: vgaarb: pci_notify
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: assign IRQ: got 33
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: enabling bus mastering
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: xHCI Host Controller
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: hcc params 0x014042c3 hci version 0x96 quirks 0x0000000000000004
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: enabling Mem-Wr-Inval
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: xHCI Host Controller
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[Mon Sep  1 19:48:13 2025] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 6.15
[Mon Sep  1 19:48:13 2025] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Mon Sep  1 19:48:13 2025] usb usb2: Product: xHCI Host Controller
[Mon Sep  1 19:48:13 2025] usb usb2: Manufacturer: Linux 6.15.2-kirkwood-tld-1 xhci-hcd
[Mon Sep  1 19:48:13 2025] usb usb2: SerialNumber: 0000:01:00.0
[Mon Sep  1 19:48:13 2025] hub 2-0:1.0: USB hub found
[Mon Sep  1 19:48:13 2025] hub 2-0:1.0: 2 ports detected
[Mon Sep  1 19:48:13 2025] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[Mon Sep  1 19:48:13 2025] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 6.15
[Mon Sep  1 19:48:13 2025] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Mon Sep  1 19:48:13 2025] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[Mon Sep  1 19:48:13 2025] usb usb3: Product: xHCI Host Controller
[Mon Sep  1 19:48:13 2025] ata1.00: ATA-8: SAMSUNG HD103SJ, 1AJ10001, max UDMA/133
[Mon Sep  1 19:48:13 2025] usb usb3: Manufacturer: Linux 6.15.2-kirkwood-tld-1 xhci-hcd
[Mon Sep  1 19:48:13 2025] ata1.00: 1953525168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[Mon Sep  1 19:48:13 2025] usb usb3: SerialNumber: 0000:01:00.0
[Mon Sep  1 19:48:13 2025] hub 3-0:1.0: USB hub found
[Mon Sep  1 19:48:13 2025] ata1.00: configured for UDMA/133
[Mon Sep  1 19:48:13 2025] hub 3-0:1.0: 2 ports detected
[Mon Sep  1 19:48:13 2025] xhci_hcd 0000:01:00.0: vgaarb: pci_notify
[Mon Sep  1 19:48:13 2025] usbcore: registered new interface driver usb-storage
[Mon Sep  1 19:48:13 2025] i2c_dev: i2c /dev entries driver
[Mon Sep  1 19:48:13 2025] scsi 0:0:0:0: Direct-Access     ATA      SAMSUNG HD103SJ  0001 PQ: 0 ANSI: 5
[Mon Sep  1 19:48:13 2025] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
[Mon Sep  1 19:48:13 2025] sd 0:0:0:0: [sda] Write Protect is off
[Mon Sep  1 19:48:13 2025] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[Mon Sep  1 19:48:13 2025] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Mon Sep  1 19:48:13 2025] rtc-pcf8563 0-0051: is a wakeup source
[Mon Sep  1 19:48:13 2025] sd 0:0:0:0: [sda] Preferred minimum I/O size 512 bytes
[Mon Sep  1 19:48:13 2025] rtc-pcf8563 0-0051: registered as rtc0
[Mon Sep  1 19:48:13 2025] rtc-pcf8563 0-0051: setting system clock to 2025-09-01T17:48:14 UTC (1756748894)
[Mon Sep  1 19:48:13 2025] device-mapper: uevent: version 1.0.3
[Mon Sep  1 19:48:13 2025] usb 1-1: new high-speed USB device number 2 using orion-ehci
[Mon Sep  1 19:48:13 2025]  sda: sda1
[Mon Sep  1 19:48:13 2025] device-mapper: ioctl: 4.49.0-ioctl (2025-01-17) initialised: dm-devel@lists.linux.dev
[Mon Sep  1 19:48:13 2025] sd 0:0:0:0: [sda] Attached SCSI disk
[Mon Sep  1 19:48:13 2025] device-mapper: multipath round-robin: version 1.2.0 loaded
[Mon Sep  1 19:48:13 2025] device-mapper: multipath queue-length: version 0.2.0 loaded
[Mon Sep  1 19:48:13 2025] device-mapper: multipath service-time: version 0.3.0 loaded
[Mon Sep  1 19:48:13 2025] device-mapper: dm-log-userspace: version 1.3.0 loaded
[Mon Sep  1 19:48:13 2025] sdhci: Secure Digital Host Controller Interface driver
[Mon Sep  1 19:48:13 2025] sdhci: Copyright(c) Pierre Ossman
[Mon Sep  1 19:48:13 2025] hid: raw HID events driver (C) Jiri Kosina
[Mon Sep  1 19:48:13 2025] drop_monitor: Initializing network drop monitor service
[Mon Sep  1 19:48:13 2025] NET: Registered PF_INET6 protocol family
[Mon Sep  1 19:48:13 2025] Segment Routing with IPv6
[Mon Sep  1 19:48:13 2025] RPL Segment Routing with IPv6
[Mon Sep  1 19:48:13 2025] In-situ OAM (IOAM) with IPv6
[Mon Sep  1 19:48:13 2025] NET: Registered PF_PACKET protocol family
[Mon Sep  1 19:48:13 2025] Key type dns_resolver registered
[Mon Sep  1 19:48:13 2025] registered taskstats version 1
[Mon Sep  1 19:48:13 2025] Loading compiled-in X.509 certificates
[Mon Sep  1 19:48:13 2025] Key type .fscrypt registered
[Mon Sep  1 19:48:13 2025] Key type fscrypt-provisioning registered
[Mon Sep  1 19:48:13 2025] Key type big_key registered
[Mon Sep  1 19:48:13 2025] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=85.32
[Mon Sep  1 19:48:13 2025] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[Mon Sep  1 19:48:13 2025] usb 1-1: Product: USB2.0 Hub
[Mon Sep  1 19:48:13 2025] hub 1-1:1.0: USB hub found
[Mon Sep  1 19:48:13 2025] hub 1-1:1.0: 4 ports detected
[Mon Sep  1 19:48:14 2025] Key type encrypted registered
[Mon Sep  1 19:48:14 2025] "cryptomgr_test" (116) uses obsolete ecb(arc4) skcipher
[Mon Sep  1 19:48:14 2025] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl F300)
[Mon Sep  1 19:48:14 2025] ata2.00: ATA-9: WDC WD20EURS-63SPKY0, 80.00A80, max UDMA/133
[Mon Sep  1 19:48:14 2025] ata2.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32)
[Mon Sep  1 19:48:14 2025] clk: Disabling unused clocks
[Mon Sep  1 19:48:14 2025] ata2.00: configured for UDMA/133
[Mon Sep  1 19:48:14 2025] scsi 1:0:0:0: Direct-Access     ATA      WDC WD20EURS-63S 0A80 PQ: 0 ANSI: 5
[Mon Sep  1 19:48:14 2025] sd 1:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.82 TiB)
[Mon Sep  1 19:48:14 2025] sd 1:0:0:0: [sdb] 4096-byte physical blocks
[Mon Sep  1 19:48:14 2025] usb 1-1.2: new high-speed USB device number 3 using orion-ehci
[Mon Sep  1 19:48:14 2025] sd 1:0:0:0: [sdb] Write Protect is off
[Mon Sep  1 19:48:14 2025] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[Mon Sep  1 19:48:14 2025] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[Mon Sep  1 19:48:14 2025] sd 1:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes
[Mon Sep  1 19:48:14 2025]  sdb: sdb1
[Mon Sep  1 19:48:14 2025] sd 1:0:0:0: [sdb] Attached SCSI disk
[Mon Sep  1 19:48:14 2025] Freeing unused kernel image (initmem) memory: 1024K
[Mon Sep  1 19:48:14 2025] Checked W+X mappings: passed, no W+X pages found
[Mon Sep  1 19:48:14 2025] Run /init as init process
[Mon Sep  1 19:48:14 2025]   with arguments:
[Mon Sep  1 19:48:14 2025]     /init
[Mon Sep  1 19:48:14 2025]   with environment:
[Mon Sep  1 19:48:14 2025]     HOME=/
[Mon Sep  1 19:48:14 2025]     TERM=linux
[Mon Sep  1 19:48:14 2025] usb 1-1.2: New USB device found, idVendor=0951, idProduct=1603, bcdDevice= 1.00
[Mon Sep  1 19:48:14 2025] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[Mon Sep  1 19:48:14 2025] usb 1-1.2: Product: DataTraveler 2.0
[Mon Sep  1 19:48:14 2025] usb 1-1.2: Manufacturer: Kingston
[Mon Sep  1 19:48:14 2025] usb 1-1.2: SerialNumber: 001372995DDDF980A61C0D21
[Mon Sep  1 19:48:14 2025] usb-storage 1-1.2:1.0: USB Mass Storage device detected
[Mon Sep  1 19:48:14 2025] scsi host2: usb-storage 1-1.2:1.0
[Mon Sep  1 19:48:15 2025] scsi 2:0:0:0: Direct-Access     Kingston DataTraveler 2.0 1.00 PQ: 0 ANSI: 2
[Mon Sep  1 19:48:15 2025] sd 2:0:0:0: [sdc] 31252024 512-byte logical blocks: (16.0 GB/14.9 GiB)
[Mon Sep  1 19:48:15 2025] sd 2:0:0:0: [sdc] Write Protect is off
[Mon Sep  1 19:48:15 2025] sd 2:0:0:0: [sdc] Mode Sense: 16 03 09 51
[Mon Sep  1 19:48:15 2025] sd 2:0:0:0: [sdc] Incomplete mode parameter data
[Mon Sep  1 19:48:16 2025] sd 2:0:0:0: [sdc] Assuming drive cache: write through
[Mon Sep  1 19:48:16 2025]  sdc: sdc1
[Mon Sep  1 19:48:16 2025] sd 2:0:0:0: [sdc] Attached SCSI removable disk
[Mon Sep  1 19:48:17 2025] usbcore: registered new interface driver uas
[Mon Sep  1 19:48:17 2025] md0: detected capacity change from 0 to 5860025344
[Mon Sep  1 19:48:28 2025] EXT4-fs (sdc1): mounted filesystem 97c2781b-1ee9-41a7-863d-abe72fcbaa25 ro with ordered data mode. Quota mode: none.
[Mon Sep  1 19:48:29 2025] systemd[1]: Inserted module 'autofs4'
[Mon Sep  1 19:48:29 2025] systemd[1]: systemd 252.38-1~deb12u1 running in system mode (+PAM +AUDIT +SELINUX +APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL +ACL +BLKID +CURL +ELFUTILS +FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBFDISK +PCRE2 -PWQUALITY +P11KIT +QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP +SYSVINIT default-hierarchy=unified)
[Mon Sep  1 19:48:29 2025] systemd[1]: Detected architecture arm.
[Mon Sep  1 19:48:29 2025] systemd[1]: Hostname set to <debian>.
[Mon Sep  1 19:48:31 2025] systemd[1]: Queued start job for default target graphical.target.
[Mon Sep  1 19:48:31 2025] systemd[1]: Created slice system-getty.slice - Slice /system/getty.
[Mon Sep  1 19:48:31 2025] systemd[1]: Created slice system-modprobe.slice - Slice /system/modprobe.
[Mon Sep  1 19:48:32 2025] systemd[1]: Created slice system-serial\x2dgetty.slice - Slice /system/serial-getty.
[Mon Sep  1 19:48:32 2025] systemd[1]: Created slice user.slice - User and Session Slice.
[Mon Sep  1 19:48:32 2025] systemd[1]: Started systemd-ask-password-console.path - Dispatch Password Requests to Console Directory Watch.
[Mon Sep  1 19:48:32 2025] systemd[1]: Started systemd-ask-password-wall.path - Forward Password Requests to Wall Directory Watch.
[Mon Sep  1 19:48:32 2025] systemd[1]: Set up automount proc-sys-fs-binfmt_misc.automount - Arbitrary Executable File Formats File System Automount Point.
[Mon Sep  1 19:48:32 2025] systemd[1]: Expecting device dev-md0.device - /dev/md0...
[Mon Sep  1 19:48:32 2025] systemd[1]: Expecting device dev-ttyS0.device - /dev/ttyS0...
[Mon Sep  1 19:48:32 2025] systemd[1]: Reached target cryptsetup.target - Local Encrypted Volumes.
[Mon Sep  1 19:48:32 2025] systemd[1]: Reached target integritysetup.target - Local Integrity Protected Volumes.
[Mon Sep  1 19:48:32 2025] systemd[1]: Reached target nss-lookup.target - Host and Network Name Lookups.
[Mon Sep  1 19:48:32 2025] systemd[1]: Reached target paths.target - Path Units.
[Mon Sep  1 19:48:32 2025] systemd[1]: Reached target slices.target - Slice Units.
[Mon Sep  1 19:48:32 2025] systemd[1]: Reached target veritysetup.target - Local Verity Protected Volumes.
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on rpcbind.socket - RPCbind Server Activation Socket.
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on systemd-fsckd.socket - fsck to fsckd communication Socket.
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on systemd-initctl.socket - initctl Compatibility Named Pipe.
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on systemd-journald-audit.socket - Journal Audit Socket.
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on systemd-journald-dev-log.socket - Journal Socket (/dev/log).
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on systemd-journald.socket - Journal Socket.
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on systemd-udevd-control.socket - udev Control Socket.
[Mon Sep  1 19:48:32 2025] systemd[1]: Listening on systemd-udevd-kernel.socket - udev Kernel Socket.
[Mon Sep  1 19:48:32 2025] systemd[1]: dev-hugepages.mount - Huge Pages File System was skipped because of an unmet condition check (ConditionPathExists=/sys/kernel/mm/hugepages).
[Mon Sep  1 19:48:32 2025] systemd[1]: Mounting dev-mqueue.mount - POSIX Message Queue File System...
[Mon Sep  1 19:48:32 2025] random: crng init done
[Mon Sep  1 19:48:32 2025] systemd[1]: Mounting proc-fs-nfsd.mount - NFSD configuration filesystem...
[Mon Sep  1 19:48:32 2025] systemd[1]: Mounting sys-kernel-debug.mount - Kernel Debug File System...
[Mon Sep  1 19:48:32 2025] systemd[1]: Mounting sys-kernel-tracing.mount - Kernel Trace File System...
[Mon Sep  1 19:48:32 2025] systemd[1]: auth-rpcgss-module.service - Kernel Module supporting RPCSEC_GSS was skipped because of an unmet condition check (ConditionPathExists=/etc/krb5.keytab).
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting kmod-static-nodes.service - Create List of Static Device Nodes...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting modprobe@configfs.service - Load Kernel Module configfs...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting modprobe@dm_mod.service - Load Kernel Module dm_mod...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting modprobe@drm.service - Load Kernel Module drm...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting modprobe@efi_pstore.service - Load Kernel Module efi_pstore...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting modprobe@fuse.service - Load Kernel Module fuse...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting modprobe@loop.service - Load Kernel Module loop...
[Mon Sep  1 19:48:33 2025] systemd[1]: systemd-fsck-root.service - File System Check on Root Device was skipped because of an unmet condition check (ConditionPathExists=!/run/initramfs/fsck-root).
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting systemd-journald.service - Journal Service...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting systemd-modules-load.service - Load Kernel Modules...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting systemd-remount-fs.service - Remount Root and Kernel File Systems...
[Mon Sep  1 19:48:33 2025] systemd[1]: Starting systemd-udev-trigger.service - Coldplug All udev Devices...
[Mon Sep  1 19:48:33 2025] systemd[1]: Mounted dev-mqueue.mount - POSIX Message Queue File System.
[Mon Sep  1 19:48:33 2025] systemd[1]: Mounted proc-fs-nfsd.mount - NFSD configuration filesystem.
[Mon Sep  1 19:48:33 2025] EXT4-fs (sdc1): re-mounted 97c2781b-1ee9-41a7-863d-abe72fcbaa25 r/w.
[Mon Sep  1 19:48:33 2025] systemd[1]: Mounted sys-kernel-debug.mount - Kernel Debug File System.
[Mon Sep  1 19:48:33 2025] systemd[1]: Mounted sys-kernel-tracing.mount - Kernel Trace File System.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished kmod-static-nodes.service - Create List of Static Device Nodes.
[Mon Sep  1 19:48:34 2025] systemd[1]: modprobe@configfs.service: Deactivated successfully.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished modprobe@configfs.service - Load Kernel Module configfs.
[Mon Sep  1 19:48:34 2025] systemd[1]: modprobe@dm_mod.service: Deactivated successfully.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished modprobe@dm_mod.service - Load Kernel Module dm_mod.
[Mon Sep  1 19:48:34 2025] systemd[1]: modprobe@drm.service: Deactivated successfully.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished modprobe@drm.service - Load Kernel Module drm.
[Mon Sep  1 19:48:34 2025] systemd[1]: modprobe@efi_pstore.service: Deactivated successfully.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished modprobe@efi_pstore.service - Load Kernel Module efi_pstore.
[Mon Sep  1 19:48:34 2025] systemd[1]: modprobe@fuse.service: Deactivated successfully.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished modprobe@fuse.service - Load Kernel Module fuse.
[Mon Sep  1 19:48:34 2025] systemd[1]: modprobe@loop.service: Deactivated successfully.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished modprobe@loop.service - Load Kernel Module loop.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished systemd-modules-load.service - Load Kernel Modules.
[Mon Sep  1 19:48:34 2025] systemd[1]: Finished systemd-remount-fs.service - Remount Root and Kernel File Systems.
[Mon Sep  1 19:48:34 2025] systemd[1]: Activating swap swapfile.swap - /swapfile...
[Mon Sep  1 19:48:34 2025] Adding 1048572k swap on /swapfile.  Priority:-2 extents:3 across:1196028k
[Mon Sep  1 19:48:34 2025] systemd[1]: Mounting sys-fs-fuse-connections.mount - FUSE Control File System...
[Mon Sep  1 19:48:34 2025] systemd[1]: Mounting sys-kernel-config.mount - Kernel Configuration File System...
[Mon Sep  1 19:48:34 2025] systemd[1]: systemd-firstboot.service - First Boot Wizard was skipped because of an unmet condition check (ConditionFirstBoot=yes).
[Mon Sep  1 19:48:34 2025] systemd[1]: systemd-pstore.service - Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
[Mon Sep  1 19:48:34 2025] systemd[1]: Starting systemd-random-seed.service - Load/Save Random Seed...
[Mon Sep  1 19:48:35 2025] systemd[1]: systemd-repart.service - Repartition Root Disk was skipped because no trigger condition checks were met.
[Mon Sep  1 19:48:35 2025] systemd[1]: Starting systemd-sysctl.service - Apply Kernel Variables...
[Mon Sep  1 19:48:35 2025] systemd[1]: Starting systemd-sysusers.service - Create System Users...
[Mon Sep  1 19:48:35 2025] systemd[1]: Activated swap swapfile.swap - /swapfile.
[Mon Sep  1 19:48:35 2025] systemd[1]: Started systemd-journald.service - Journal Service.
[Mon Sep  1 19:48:35 2025] systemd-journald[264]: Received client request to flush runtime journal.
[Mon Sep  1 19:48:37 2025] sd 0:0:0:0: Attached scsi generic sg0 type 0
[Mon Sep  1 19:48:37 2025] sd 1:0:0:0: Attached scsi generic sg1 type 0
[Mon Sep  1 19:48:38 2025] sd 2:0:0:0: Attached scsi generic sg2 type 0
[Mon Sep  1 19:48:39 2025] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[Mon Sep  1 19:48:39 2025] EXT4-fs (md0): mounted filesystem e7bf3836-3951-469f-8f11-064e57266385 r/w with ordered data mode. Quota mode: none.
[Mon Sep  1 19:48:39 2025] orion_wdt: Initial timeout 21 sec
[Mon Sep  1 19:48:40 2025] marvell-cesa f1030000.crypto: CESA device successfully registered
[Mon Sep  1 19:48:47 2025] usb 1-1.2: reset high-speed USB device number 3 using orion-ehci
[Mon Sep  1 19:48:54 2025] usb 1-1.2: reset high-speed USB device number 3 using orion-ehci
[Mon Sep  1 19:49:00 2025] mv643xx_eth: Set the PHY back to auto-negotiation mode
[Mon Sep  1 19:49:00 2025] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[Mon Sep  1 19:49:00 2025] mv643xx_eth_port mv643xx_eth_port.0 eth0: link down
[Mon Sep  1 19:49:03 2025] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[Mon Sep  1 19:49:04 2025] NFSD: Using nfsdcld client tracking operations.
[Mon Sep  1 19:49:04 2025] NFSD: no clients to reclaim, skipping NFSv4 grace period (net f0000000)

cat /etc/netconfig
#
# The network configuration file. This file is currently only used in
# conjunction with the TI-RPC code in the libtirpc library.
#
# Entries consist of:
#
#       <network_id> <semantics> <flags> <protofamily> <protoname> \
#               <device> <nametoaddr_libs>
#
# The <device> and <nametoaddr_libs> fields are always empty in this
# implementation.
#
udp        tpi_clts      v     inet     udp     -       -
tcp        tpi_cots_ord  v     inet     tcp     -       -
udp6       tpi_clts      v     inet6    udp     -       -
tcp6       tpi_cots_ord  v     inet6    tcp     -       -
rawip      tpi_raw       -     inet      -      -       -
local      tpi_cots_ord  -     loopback  -      -       -
unix       tpi_cots_ord  -     loopback  -      -       -
root@debian:~# cat /etc/networks
default         0.0.0.0
loopback        127.0.0.0
link-local      169.254.0.0

I don't recognise the 169.254.x.x in the link-local

Edited 2 time(s). Last edit at 09/01/2025 02:17PM by Bobby.

Reply Quote