2023.04 U-Boot Kirkwood - Pogo V4
Posted by bodhi
|
2023.04 U-Boot Kirkwood - Pogo V4 May 07, 2023 09:07PM |
Admin Registered: 13 years ago Posts: 18,545 |
In addition to the capabilties provided by u-boot 2017.07-tld-1 for Pogo V4 , this 2023.04-tld-1 Pogo V4 u-boot has the following new capabilties:
- Supports for USB 3.0. You can now boot with the rootfs in either one of the 2 USB 3.0 ports in the back.
- Netconsole enhancement. (See Note C.1.2).
- Distro boot (see Note C.2 after the Installation Steps for usage).
=========================================
Update 11 Jun 2023: Fixed netconsole
Update 25 May 2023
Update 20 May 2023
Update 17 May 2023
Download at Dropbox
uboot.2023.04-tld-1.pogo_v4.bodhi.tar
As always, please verify the hash of what you've downloaded!
This tarball includes 4 files
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.
A.2. Flashing tools
If you are running an OS (eg. stock FW) that does not provide mtd-utils and uboot-tools (fw_setenv, fw_printenv, flash_erase, nandwrite), you can download the NAND and U-Boot tools binaries here in this thread.
B. Flashing Instruction:
1. Setup fw_env.config
U-Boot envs config should be defined as followed in your /etc/fw_env.config
cat /etc/fw_env.config
If you don't have /etc/fw_env.config file in your system then go ahead and create this file:
- And your mtd partitions should be:
cat /proc/mtd
2. Backup mtd0 and envs
Save your current uBoot image and envs image in mtd0, and save your current u-boot envs with fw_printenv. Copy these 3 files to a persistent storage.
2.1 Dumping NAND mtd0:
2.2. Save envs:
3. Check for bad blocks
Be sure there is no bad block in the first 1M of your NAND. This is very important, if there is bad block in the first 1M (blocks 0 to 7), don't flash u-boot, because you will almost certainly soft-brick your box.
Example of bad block in mtd0:
This bad eraseblock 3 is the 4th block which resides within mtd0 first 1M (block 0 to block 7). Please stop at this step and post question in this thread for a workaround.
4. Extract the archive to /tmp
5. Flash u-boot image to NAND
Be extra careful with the next 2 commands, you should see output that look like below in those steps. If there is error, then do not reboot, post your problem here so we can help.
Erase 4 blocks
Write the image
6. Flash default u-boot envs image
If you are upgrading from 2017.07-tld-1 u-boot, you can skip this step. But some envs will need to be updated before reboot. See Note section below after the installation steps. Especially if your rootfs is SATA, then you must adjust the env described in Note section "C.1.1 SATA boot envs". Or if you are using netconsole then you must adjust the env described in Note section "C.1.2 Netconsole envs".
Be extra careful with the next 2 commands, you should see output that look like below. If there is error, then do not reboot, post your problem here so we can help.
Erase 1 block
Write the image
7. Restore MAC address
Modify the following u-boot variable using fw_setenv:
Restore the MAC address using the saved envs in current_envs.txt. Or find the MAC address on the sticker outside the case. Replace xx:xx:xx:xx:xx:xx with the real values.
Don't reboot if there is error while listing U-Boot envs.
8. (Optional) Activate netconsole
Skip this step if you already have serial console connected. Netconsole can be set up anytime later.
Adjust 192.168.0.xxx and 192.168.0.yyy below to the real numbers in your network configuration. 192.168.0.xxx is this pogoplug static IP address, and 192.168.0.yyy is the IP address of the netconsole server where it will monitor the output from this pogoplug. The ipaddr can be any unique address that you want to use. serverip is IP address of the netconsole server, so usually a Linux box in your network.
9. Reboot
Upon reboot, in either serial console or netconsole, U-Boot banner should show:
DONE installation.
C. Note
C.1. Envs changes from 2017.07-tld-1 u-to 2023.04-tld-1 u-boot.
As mentioned in Step 6, if you are upgrading from 2017.07-tld-1 u-boot then this is a u-boot drop in replacement (no need to flash new default envs image). However there are changes in envs for 2023.04-tld-1 that need to be retrofitted if you have chosen not flashing the default envs in Step 6.
C.1.1 SATA boot envs
In this new u-boot, the SATA device was changed from "ide" to "sata", and also the command to start it. So if SATA is the boot drive, you must adjust these envs.
C.1.2 Netconsole envs
Both serial console and netconsole input and output are now muxed to one console.
So in this new u-boot, the stdin/stdout/stderr netconsole was change from "serial" to "serial,nc". Therefore, if netconsole is used, you must adjust the start_netconsole env.
C.2. Distro Boot
C.2.1 (Optional) Booting all distros
In this new u-boot, I've implemented the Distro Boot capability. So any distro (such as Ubuntu, Alpine, Fedora, etc.) can be booted as long as they conform to the Distro Boot standard. However, for the purpose of booting our Debian Kirkwood kernel released here for this box, it is not relevant and should be ignored.
C.2.2 Using boot.scr to recover from damaged or corrupted envs NAND block
Included in the tarball uboot.2023.04-tld-1.pogo_v4.bodhi.tar is the script file uboot.2023.04-tld-1.pogo_v4.boot.scr. This is a Distro-Boot-compliant boot script. It can be used to recover from a damaged/corrupted envs NAND block, or if the envs NAND block has never been flashed (same as corrupted).
So for whatever reason, if in serial console, U-Boot reported the CRC error while loading the envs, using the boot.scr will provide a minimalist booting envs and enable booting into Debian. And then the default envs image can be flashed.
- Mount the USB rootfs on another Linux box. Assuming it is mounted at /media/sdb1.
- Unmount and then bring it back to the Pogo V4. Power up and let it boot automatically. The boot.scr should come into play, and allow booting to Debian.
C.3. uEnv.txt
This capabilty is the same as in previously released u-boot-2017.07-tld-1.
Description TBD.
END of NOTE.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 18 time(s). Last edit at 07/01/2023 03:36PM by bodhi.
- Supports for USB 3.0. You can now boot with the rootfs in either one of the 2 USB 3.0 ports in the back.
- Netconsole enhancement. (See Note C.1.2).
- Distro boot (see Note C.2 after the Installation Steps for usage).
=========================================
Update 11 Jun 2023: Fixed netconsole
Update 25 May 2023
Update 20 May 2023
Update 17 May 2023
Download at Dropbox
uboot.2023.04-tld-1.pogo_v4.bodhi.tar
md5sum 17175072c15f4ae52fea939e02dc1272 sha256sum 92887073f5c37755430c5ea647fba2f14c45838d1a5448ffd70a69e77b466acf
As always, please verify the hash of what you've downloaded!
This tarball includes 4 files
uboot.2023.04-tld-1.pogo_v4.kwb uboot.2023.04-tld-1.pogo_v4.environment.img uboot.2023.04-tld-1.pogo_v4.environment uboot.2023.04-tld-1.pogo_v4.boot.scr
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.
A.2. Flashing tools
If you are running an OS (eg. stock FW) that does not provide mtd-utils and uboot-tools (fw_setenv, fw_printenv, flash_erase, nandwrite), you can download the NAND and U-Boot tools binaries here in this thread.
B. Flashing Instruction:
1. Setup fw_env.config
U-Boot envs config should be defined as followed in your /etc/fw_env.config
cat /etc/fw_env.config
# MTD device name Device offset Env. size Flash sector size Number of sectors /dev/mtd0 0xc0000 0x20000 0x20000
If you don't have /etc/fw_env.config file in your system then go ahead and create this file:
echo "/dev/mtd0 0xc0000 0x20000 0x20000" > /etc/fw_env.config
- And your mtd partitions should be:
cat /proc/mtd
dev: size erasesize name mtd0: 00200000 00020000 "u-boot" mtd1: 00300000 00020000 "uImage" mtd2: 00300000 00020000 "uImage2" mtd3: 00800000 00020000 "failsafe" mtd4: 07000000 00020000 "root"
2. Backup mtd0 and envs
Save your current uBoot image and envs image in mtd0, and save your current u-boot envs with fw_printenv. Copy these 3 files to a persistent storage.
2.1 Dumping NAND mtd0:
nanddump --noecc --omitoob -l 0x80000 -f mtd0.pogo_v4 /dev/mtd0 nanddump --noecc --omitoob -f mtd0.pogo_v4.envs -s 786432 -l 131072 /dev/mtd0
2.2. Save envs:
fw_printenv > current_envs.txtFor most stock OS, there is no fw_printenv. So it's OK if this step fails.
3. Check for bad blocks
Be sure there is no bad block in the first 1M of your NAND. This is very important, if there is bad block in the first 1M (blocks 0 to 7), don't flash u-boot, because you will almost certainly soft-brick your box.
Example of bad block in mtd0:
dmesg | grep -i 'bad' [ 2.413231] Scanning device for bad blocks [ 2.417731] Bad eraseblock 3 at 0x000000060000
This bad eraseblock 3 is the 4th block which resides within mtd0 first 1M (block 0 to block 7). Please stop at this step and post question in this thread for a workaround.
4. Extract the archive to /tmp
cd /tmp tar xf uboot.2023.04-tld-1.pogo_v4.bodhi.tar
5. Flash u-boot image to NAND
Be extra careful with the next 2 commands, you should see output that look like below in those steps. If there is error, then do not reboot, post your problem here so we can help.
Erase 4 blocks
flash_erase /dev/mtd0 0 4Expected output:
Erase Total 4 Units Performing Flash Erase of length 131072 at offset 0x60000 done
Write the image
nandwrite /dev/mtd0 /tmp/uboot.2023.04-tld-1.pogo_v4.kwbExpected output:
Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x60000
6. Flash default u-boot envs image
If you are upgrading from 2017.07-tld-1 u-boot, you can skip this step. But some envs will need to be updated before reboot. See Note section below after the installation steps. Especially if your rootfs is SATA, then you must adjust the env described in Note section "C.1.1 SATA boot envs". Or if you are using netconsole then you must adjust the env described in Note section "C.1.2 Netconsole envs".
Be extra careful with the next 2 commands, you should see output that look like below. If there is error, then do not reboot, post your problem here so we can help.
Erase 1 block
flash_erase /dev/mtd0 0xc0000 1Expected output:
Erase Total 1 Units Performing Flash Erase of length 131072 at offset 0xc0000 done
Write the image
nandwrite -s 786432 /dev/mtd0 /tmp/uboot.2023.04-tld-1.pogo_v4.environment.imgExpected output:
Writing data to block 6 at offset 0xc0000
7. Restore MAC address
Modify the following u-boot variable using fw_setenv:
Restore the MAC address using the saved envs in current_envs.txt. Or find the MAC address on the sticker outside the case. Replace xx:xx:xx:xx:xx:xx with the real values.
fw_setenv ethaddr 'xx:xx:xx:xx:xx:xx'For sanity check, list you envs again
fw_printenv
Don't reboot if there is error while listing U-Boot envs.
8. (Optional) Activate netconsole
Skip this step if you already have serial console connected. Netconsole can be set up anytime later.
Adjust 192.168.0.xxx and 192.168.0.yyy below to the real numbers in your network configuration. 192.168.0.xxx is this pogoplug static IP address, and 192.168.0.yyy is the IP address of the netconsole server where it will monitor the output from this pogoplug. The ipaddr can be any unique address that you want to use. serverip is IP address of the netconsole server, so usually a Linux box in your network.
fw_setenv preboot 'run preboot_nc' fw_setenv ipaddr '192.168.0.xxx' fw_setenv serverip '192.168.0.yyy'
9. Reboot
Upon reboot, in either serial console or netconsole, U-Boot banner should show:
U-Boot 2023.04-tld-1 (Jun 11 2023....) Pogo V4
DONE installation.
C. Note
C.1. Envs changes from 2017.07-tld-1 u-to 2023.04-tld-1 u-boot.
As mentioned in Step 6, if you are upgrading from 2017.07-tld-1 u-boot then this is a u-boot drop in replacement (no need to flash new default envs image). However there are changes in envs for 2023.04-tld-1 that need to be retrofitted if you have chosen not flashing the default envs in Step 6.
C.1.1 SATA boot envs
In this new u-boot, the SATA device was changed from "ide" to "sata", and also the command to start it. So if SATA is the boot drive, you must adjust these envs.
fw_setenv devices 'sata usb mmc' fw_setenv init_sata 'sata init' fw_setenv scan_disk 'echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start"; 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' fw_setenv uenv_init_devices 'echo Initializing devices...; setenv init_usb "usb start"; setenv init_sata "sata init"; setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done'
C.1.2 Netconsole envs
Both serial console and netconsole input and output are now muxed to one console.
So in this new u-boot, the stdin/stdout/stderr netconsole was change from "serial" to "serial,nc". Therefore, if netconsole is used, you must adjust the start_netconsole env.
fw_setenv start_netconsole 'setenv ncip $serverip; setenv bootdelay 10; setenv stdin serial,nc; setenv stdout serial,nc; setenv stderr serial,nc; version'
C.2. Distro Boot
C.2.1 (Optional) Booting all distros
In this new u-boot, I've implemented the Distro Boot capability. So any distro (such as Ubuntu, Alpine, Fedora, etc.) can be booted as long as they conform to the Distro Boot standard. However, for the purpose of booting our Debian Kirkwood kernel released here for this box, it is not relevant and should be ignored.
C.2.2 Using boot.scr to recover from damaged or corrupted envs NAND block
Included in the tarball uboot.2023.04-tld-1.pogo_v4.bodhi.tar is the script file uboot.2023.04-tld-1.pogo_v4.boot.scr. This is a Distro-Boot-compliant boot script. It can be used to recover from a damaged/corrupted envs NAND block, or if the envs NAND block has never been flashed (same as corrupted).
So for whatever reason, if in serial console, U-Boot reported the CRC error while loading the envs, using the boot.scr will provide a minimalist booting envs and enable booting into Debian. And then the default envs image can be flashed.
- Mount the USB rootfs on another Linux box. Assuming it is mounted at /media/sdb1.
cd /media/sdb1/boot cp -a uboot.2023.04-tld-1.pogo_v4.boot.scr boot.scr sync
- Unmount and then bring it back to the Pogo V4. Power up and let it boot automatically. The boot.scr should come into play, and allow booting to Debian.
C.3. uEnv.txt
This capabilty is the same as in previously released u-boot-2017.07-tld-1.
Description TBD.
END of NOTE.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 18 time(s). Last edit at 07/01/2023 03:36PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 07, 2023 09:51PM |
Registered: 1 year ago Posts: 44 |
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 07, 2023 10:42PM |
Admin Registered: 13 years ago Posts: 18,545 |
mrc333777 Wrote:
-------------------------------------------------------
> awsome, i will be ready to try it on these two
> PogoPlug V4-A3-01
> i have one PogoPlugPro.v3 as well is that
> different?
It is different. The Pogo V3 is OXNAS architecture.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> awsome, i will be ready to try it on these two
> PogoPlug V4-A3-01
> i have one PogoPlugPro.v3 as well is that
> different?
It is different. The Pogo V3 is OXNAS architecture.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 08, 2023 04:32PM |
Registered: 9 years ago Posts: 442 |
Were can the code for the 2023.04 rebase be found? Your github repository still appears to be at 2017.07
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 08, 2023 05:57PM |
Admin Registered: 13 years ago Posts: 18,545 |
> Were can the code for the 2023.04 rebase be found?
> Your
> github
> repository still appears to be at 2017.07
That will come later after I'm done with the u-boot releases here. By the way, I will only release new u-boot if there is significant capability added, or bug fixes. Otherwise, you will not be missing anything running 2017.07 version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Your
> github
> repository still appears to be at 2017.07
That will come later after I'm done with the u-boot releases here. By the way, I will only release new u-boot if there is significant capability added, or bug fixes. Otherwise, you will not be missing anything running 2017.07 version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 09, 2023 01:45AM |
Registered: 1 year ago Posts: 81 |
I was successful kwbooting from the new 2023.04 image.
Made a new rootfs with the 5.13.6-kirkwood kernel on a SanDisk 3.2Gen1 (Ultra Fit) and it worked fine.
I didn't set any environment vars to do it, and it didn't fall apart when I upgraded the system & completed the install etc.
I would consider that a success.
Was hoping for the cpu setting for the LED too, but this is a great accomplishment, and I'm happy to have it. Maybe it can be wedged in on the next point increment with other fixes if needed...
I then tried to get a throughput test on the USB 3 to compare against the USB 2, but the write test failed with:
The read test worked, showing the following:
I can provide the boot messages (serial connection) if it's useful.
Made a new rootfs with the 5.13.6-kirkwood kernel on a SanDisk 3.2Gen1 (Ultra Fit) and it worked fine.
I didn't set any environment vars to do it, and it didn't fall apart when I upgraded the system & completed the install etc.
I would consider that a success.
Was hoping for the cpu setting for the LED too, but this is a great accomplishment, and I'm happy to have it. Maybe it can be wedged in on the next point increment with other fixes if needed...
I then tried to get a throughput test on the USB 3 to compare against the USB 2, but the write test failed with:
# dd if=/dev/zero of=test_write.img bs=1G count=1 oflag=dsync dd: memory exhausted by input buffer of size 1073741824 bytes (1.0 GiB)I'm sure I don't have the settings right for this small box.
The read test worked, showing the following:
# hdparm -Tt /dev/sda /dev/sda: Timing cached reads: 378 MB in 2.00 seconds = 188.94 MB/sec Timing buffered disk reads: 170 MB in 3.01 seconds = 56.45 MB/secI'll test USB 2 later.
I can provide the boot messages (serial connection) if it's useful.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 09, 2023 01:58AM |
Admin Registered: 13 years ago Posts: 18,545 |
dhargens
> I was successful kwbooting from the new 2023.04
> image.
> Made a new rootfs with the 5.13.6-kirkwood kernel
> on a SanDisk 3.2Gen1 (Ultra Fit) and it worked
> fine.
> I didn't set any environment vars to do it, and it
> didn't fall apart when I upgraded the system &
> completed the install etc.
>
> I would consider that a success.
Awesome!
>
> Was hoping for the cpu setting for the LED too,
> but this is a great accomplishment, and I'm happy
> to have it. Maybe it can be wedged in on the next
> point increment with other fixes if needed...
The CPU LED trigger is in the kernel. So you will see it in the next kernel release.
>
> I then tried to get a throughput test on the USB 3
> to compare against the USB 2, but the write test
> failed with:
>
> small box.
I would suggest a smaller file such as 50MB. This box only has 128MB RAM. So if you use large file, i.e 1GB, it will swap out to disk, and then the test is invalid.
> The read test worked, showing the following:
>
Cool!
It was a very good test! thanks.
I'll upload another build version (just to iron out the logistics), no more real change for this u-boot.
BTW, this u-boot release will determine how the rest of other Kirkwood boards's u-boots will be. So you're our designated tester :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/09/2023 02:03AM by bodhi.
> I was successful kwbooting from the new 2023.04
> image.
> Made a new rootfs with the 5.13.6-kirkwood kernel
> on a SanDisk 3.2Gen1 (Ultra Fit) and it worked
> fine.
> I didn't set any environment vars to do it, and it
> didn't fall apart when I upgraded the system &
> completed the install etc.
>
> I would consider that a success.
Awesome!
>
> Was hoping for the cpu setting for the LED too,
> but this is a great accomplishment, and I'm happy
> to have it. Maybe it can be wedged in on the next
> point increment with other fixes if needed...
The CPU LED trigger is in the kernel. So you will see it in the next kernel release.
>
> I then tried to get a throughput test on the USB 3
> to compare against the USB 2, but the write test
> failed with:
>
> # dd if=/dev/zero of=test_write.img bs=1G count=1 > oflag=dsync > dd: memory exhausted by input buffer of size > 1073741824 bytes (1.0 GiB) >> I'm sure I don't have the settings right for this
> small box.
I would suggest a smaller file such as 50MB. This box only has 128MB RAM. So if you use large file, i.e 1GB, it will swap out to disk, and then the test is invalid.
> The read test worked, showing the following:
>
> # hdparm -Tt /dev/sda > /dev/sda: > Timing cached reads: 378 MB in 2.00 seconds = > 188.94 MB/sec > Timing buffered disk reads: 170 MB in 3.01 > seconds = 56.45 MB/sec >
Cool!
It was a very good test! thanks.
I'll upload another build version (just to iron out the logistics), no more real change for this u-boot.
BTW, this u-boot release will determine how the rest of other Kirkwood boards's u-boots will be. So you're our designated tester :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/09/2023 02:03AM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 09, 2023 02:12AM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> The CPU LED trigger is in the kernel. So you will
> see it in the next kernel release.
Way cool!
> I would suggest a smaller file such as 50MB. This
> box only has 128MB RAM. So if you use large file,
> i.e 1GB, it will swap out to disk, and then the
> test is invalid.
Makes perfect sense. I knew it was something simple.
Here's the corrected test:
# dd if=/dev/zero of=test_write.img bs=50M count=1 oflag=dsync
1+0 records in
1+0 records out
52428800 bytes (52 MB, 50 MiB) copied, 3.34359 s, 15.7 MB/s
I DO have the swap file turned on, so I can turn it off and see if that's affecting it.
Setting the test to 100M kills the thing - as expected - dropping it to 1.8 MB/s. So that obviously is not a valid test.
USB 2 to come later.
> BTW, this u-boot release will determine how the
> rest of other boards's u-boot will be. So you're
> our designated tester :)
Glad to do it! I've got a few V4s I can test on.
Edited 1 time(s). Last edit at 05/09/2023 08:46AM by dhargens.
-------------------------------------------------------
> The CPU LED trigger is in the kernel. So you will
> see it in the next kernel release.
Way cool!
> I would suggest a smaller file such as 50MB. This
> box only has 128MB RAM. So if you use large file,
> i.e 1GB, it will swap out to disk, and then the
> test is invalid.
Makes perfect sense. I knew it was something simple.
Here's the corrected test:
# dd if=/dev/zero of=test_write.img bs=50M count=1 oflag=dsync
1+0 records in
1+0 records out
52428800 bytes (52 MB, 50 MiB) copied, 3.34359 s, 15.7 MB/s
I DO have the swap file turned on, so I can turn it off and see if that's affecting it.
Setting the test to 100M kills the thing - as expected - dropping it to 1.8 MB/s. So that obviously is not a valid test.
USB 2 to come later.
> BTW, this u-boot release will determine how the
> rest of other boards's u-boot will be. So you're
> our designated tester :)
Glad to do it! I've got a few V4s I can test on.
Edited 1 time(s). Last edit at 05/09/2023 08:46AM by dhargens.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 11, 2023 02:51PM |
Admin Registered: 13 years ago Posts: 18,545 |
I've uploaded an updated version in the first post.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 11, 2023 05:40PM |
Registered: 1 year ago Posts: 81 |
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 16, 2023 11:08PM |
Admin Registered: 13 years ago Posts: 18,545 |
Hi dhargens,
> Great to hear! I'll get to it next week - busy
> weekend ahead, starting tomorrow.
Are you ready to test the installation instruction?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> Great to hear! I'll get to it next week - busy
> weekend ahead, starting tomorrow.
Are you ready to test the installation instruction?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 17, 2023 03:24PM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> Are you ready to test the installation instruction?
Yes, I have some time set aside for this evening and should be able to get started.
Are there any other notes I need to know about before doing this? Pointers, maybe?
(Not worried about it, just want to make sure I get the steps down correctly. And...I've slept since then too.)
-------------------------------------------------------
> Are you ready to test the installation instruction?
Yes, I have some time set aside for this evening and should be able to get started.
Are there any other notes I need to know about before doing this? Pointers, maybe?
(Not worried about it, just want to make sure I get the steps down correctly. And...I've slept since then too.)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 17, 2023 07:12PM |
Admin Registered: 13 years ago Posts: 18,545 |
Hi dhargens,
The 1st post now includes flashing instruction.
> Are there any other notes I need to know about
> before doing this? Pointers, maybe?
To test install this u-boot do 2 tests.
1. Don't flash the envs image in Step 6
And retrofit the envs. See if that makes sense. Especially if you have an HDD rootfs that you can boot with.
2. Flash the envs image in Step 6, just like the initial installation. Check out that it works fine.
And optionally then restore your saved envs. Or keep the new envs as is. Either way is fine, but I think you should use the new envs, they were streamlined to remove uneccessary stuff.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/17/2023 07:13PM by bodhi.
The 1st post now includes flashing instruction.
> Are there any other notes I need to know about
> before doing this? Pointers, maybe?
To test install this u-boot do 2 tests.
1. Don't flash the envs image in Step 6
Quote
6. Flash default u-boot envs image
If you are upgrading from 2017.07-tld-1 u-boot, you can skip this step. But some envs will need to be updated. See Note section below after the installation steps.
And retrofit the envs. See if that makes sense. Especially if you have an HDD rootfs that you can boot with.
2. Flash the envs image in Step 6, just like the initial installation. Check out that it works fine.
And optionally then restore your saved envs. Or keep the new envs as is. Either way is fine, but I think you should use the new envs, they were streamlined to remove uneccessary stuff.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/17/2023 07:13PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 18, 2023 07:00PM |
Registered: 1 year ago Posts: 81 |
Ok, after some hardware issues and other unexpected problems, I finally got things working. Here's my findings.
Booted USB into Debian 5.13.6-kirkwood-tld-1, which has been updated to current.
Connected by serial port.
Steps:
confirmed kwboot for this uboot works. It did the last time too, so I had no worries.
stepped thru Sect B (Flashing) steps 1-7. No problems.
1. /etc/fw_env.config & /proc/mtd correct, no changes.
2. dumped NAND mtd0 and saved current_envs.txt
3. checked for bad blocks - no errors
5a. flashed u-boot image to NAND
my output:
my output:
7. no need to restore MAC, as it was unchanged
Reboot worked as expected, and booted into shiny new uboot from USB.
Shutdown and moved the USB to the back port (USB 3) and it also booted as expected.
YAY!!
Since all steps went without error, I continued to the alternate methods in your last message.
6. I wrote the new environment.img to NAND:
Note C.1. SATA boot envs
a. fw_setenv devices 'sata usb mmc'
my output:
Note: I've never created/edited /boot/uEnv.txt because I haven't understood what should be put in there. Mostly what I read was to use it as a work-around to get problematic things to work. Mine's not had these problems, so I've been able to skip it (it seems, anyway).
So then I rebooted to test another drive (USB 2) to see if its fw_printenv was working, and here's the output:
Yeah, that ain't right. Looks like ... no vars, no boot.
My guess is writing the environment.img wasn't done correctly, but I'm not sure how to fix it. I see the error:
Forgot to include the following:
Edited 1 time(s). Last edit at 05/18/2023 07:02PM by dhargens.
Booted USB into Debian 5.13.6-kirkwood-tld-1, which has been updated to current.
Connected by serial port.
Steps:
confirmed kwboot for this uboot works. It did the last time too, so I had no worries.
stepped thru Sect B (Flashing) steps 1-7. No problems.
1. /etc/fw_env.config & /proc/mtd correct, no changes.
2. dumped NAND mtd0 and saved current_envs.txt
3. checked for bad blocks - no errors
5a. flashed u-boot image to NAND
my output:
root@deb03:/tmp# flash_erase /dev/mtd0 0 4 Erasing 128 Kibyte @ 60000 -- 100 % complete5b. wrote image
my output:
root@deb03:/tmp# nandwrite /dev/mtd0 /tmp/uboot.2023.04-tld-1.pogo_v4.kwb Writing data to block 0 at offset 0x0 Writing data to block 1 at offset 0x20000 Writing data to block 2 at offset 0x40000 Writing data to block 3 at offset 0x600006. skipped, as I was upgrading from 2017.07-tld-1 u-boot.
7. no need to restore MAC, as it was unchanged
Reboot worked as expected, and booted into shiny new uboot from USB.
Shutdown and moved the USB to the back port (USB 3) and it also booted as expected.
YAY!!
Since all steps went without error, I continued to the alternate methods in your last message.
6. I wrote the new environment.img to NAND:
root@deb03:/tmp# /usr/sbin/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.2023.04-tld-1.pogo_v4.environment.img Writing data to block 6 at offset 0xc0000no error.
Note C.1. SATA boot envs
a. fw_setenv devices 'sata usb mmc'
my output:
root@deb03:~# fw_setenv devices 'sata usb mmc' Cannot read environment, using default Cannot read default environment from fileI stopped here. Didn't think to get a 'fw_printenv' of the vars first, but that would've told me none of the environment vars was working (outputs same error). I'm sure something's not right in my environment.
Note: I've never created/edited /boot/uEnv.txt because I haven't understood what should be put in there. Mostly what I read was to use it as a work-around to get problematic things to work. Mine's not had these problems, so I've been able to skip it (it seems, anyway).
So then I rebooted to test another drive (USB 2) to see if its fw_printenv was working, and here's the output:
U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700)
Pogoplug V4
SoC: Kirkwood 88F6192_A1
Model: Cloud Engines PogoPlug Series 4
DRAM: 128 MiB
Core: 20 devices, 16 uclasses, devicetree: separate
NAND: 128 MiB
MMC: mvsdio@90000: 0
Loading Environment from NAND... NAND read from offset c0000 failed -74
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
pcie0.0: Link up
Net:
Warning: ethernet-controller@72000 (eth0) using random MAC address - 1a:e7:a7:36:29:65
eth0: ethernet-controller@72000
Hit any key to stop autoboot: 0
Card did not respond to voltage select! : -110
starting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 2 USB Device(s) found
scanning bus xhci_pci for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Device 0: Vendor: SanDisk' Rev: 1.00 Prod: Cruzer Fit
Type: Removable Hard Disk
Capacity: 14664.0 MB = 14.3 GB (30031872 x 512)
... is now current device
Scanning usb 0:1...
Device 0: unknown device
ethernet-controller@72000 Waiting for PHY auto negotiation to complete....... done
BOOTP broadcast 1
BOOTP broadcast 2
BOOTP broadcast 3
BOOTP broadcast 4
*** Unhandled DHCP Option in OFFER/ACK: 125
*** Unhandled DHCP Option in OFFER/ACK: 2
*** Unhandled DHCP Option in OFFER/ACK: 125
*** Unhandled DHCP Option in OFFER/ACK: 2
DHCP client bound to address 192.168.1.200 (1780 ms)
*** ERROR: `serverip' not set
Cannot autoload with TFTPGET
Pogo_V4>
Yeah, that ain't right. Looks like ... no vars, no boot.
My guess is writing the environment.img wasn't done correctly, but I'm not sure how to fix it. I see the error:
Loading Environment from NAND... NAND read from offset c0000 failed -74What do I need to do to get things loaded correctly at this point? I do have the pre-update env vars saved in a file, but since I borked the .img file I didn't think I'd have much luck with the old-var reload without help.
Forgot to include the following:
Pogo_V4> printenv
arch=arm
baudrate=115200
board=pogo_v4
board_name=pogo_v4
boot_a_script=load ${devtype} ${devnum}:${distro_bootpart} ${scriptaddr} ${prefix}${script}; source $}
boot_extlinux=sysboot ${devtype} ${devnum}:${distro_bootpart} any ${scriptaddr} ${prefix}${boot_sysli}
boot_net_usb_start=usb start
boot_pci_enum=pci enum
boot_prefixes=/ /boot/
boot_script_dhcp=boot.scr.uimg
boot_scripts=boot.scr.uimg boot.scr
boot_syslinux_conf=extlinux/extlinux.conf
boot_targets=mmc0 usb0 sata0 dhcp
bootcmd=run distro_bootcmd
bootcmd_dhcp=devtype=dhcp; run boot_net_usb_start; run boot_pci_enum; if dhcp ${scriptaddr} ${boot_sc;
bootcmd_mmc0=devnum=0; run mmc_boot
bootcmd_sata0=devnum=0; run sata_boot
bootcmd_usb0=devnum=0; run usb_boot
bootdelay=10
bootfile=boot.scr.uimg
bootfstype=ext4
console=ttyS0,115200
cpu=arm926ejs
distro_bootcmd=for target in ${boot_targets}; do run bootcmd_${target}; done
distro_bootpart_uuid=23781415-01
ethact=ethernet-controller@72000
ethaddr=1a:e7:a7:36:29:65
fdt_addr_r=0x2c00000
fdtcontroladdr=7b51650
fdtfile=kirkwood-pogoplug-series-4.dtb
kernel_addr_r=0x800000
loadaddr=0x800000
mmc_boot=if mmc dev ${devnum}; then devtype=mmc; run scan_dev_for_boot_part; fi
mtdids=nand0=orion_nand
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
ramdisk_addr_r=0x01100000
sata_boot=if sata dev ${devnum}; then devtype=sata; run scan_dev_for_boot_part; fi
scan_dev_for_boot=echo Scanning ${devtype} ${devnum}:${distro_bootpart}...; for prefix in ${boot_pref;
scan_dev_for_boot_part=part list ${devtype} ${devnum} -bootable devplist; env exists devplist || setet
scan_dev_for_extlinux=if test -e ${devtype} ${devnum}:${distro_bootpart} ${prefix}${boot_syslinux_coni
scan_dev_for_scripts=for script in ${boot_scripts}; do if test -e ${devtype} ${devnum}:${distro_bootpe
scriptaddr=0x200000
soc=kirkwood
ubifs_boot=if ubi part ${bootubipart} ${bootubioff} && ubifsmount ubi0:${bootubivol}; then devtype=ubi
usb_boot=usb start; if usb dev ${devnum}; then devtype=usb; run scan_dev_for_boot_part; fi
vendor=cloudengines
ver=U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700)\
Pogoplug V4
Environment size: 2847/131068 bytes
Pogo_V4>
Edited 1 time(s). Last edit at 05/18/2023 07:02PM by dhargens.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 18, 2023 07:31PM |
Admin Registered: 13 years ago Posts: 18,545 |
6. I wrote the new environment.img to NAND: root@deb03:/tmp# /usr/sbin/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.2023.04-tld-1.pogo_v4.environment.img Writing data to block 6 at offset 0xc0000 no error.
Did you erase the NAND block first?
Quote
6. Flash default u-boot envs image
If you are upgrading from 2017.07-tld-1 u-boot, you can skip this step. But some envs will need to be updated. See Note section below after the installation steps.
Be extra careful with the next 2 commands, you should see output that look like below. If there is error, then do not reboot, post your problem here so we can help.
Erase 1 block
/usr/sbin/flash_erase /dev/mtd0 0xc0000 1
Expected output:
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0xc0000 done
Write the image
/usr/sbin/nandwrite -s 786432 /dev/mtd0 /tmp/uboot.2023.04-tld-1.pogo_v4.environment.img
Expected output:
Writing data to block 6 at offset 0xc0000
======
OK so to recover from this. The quickest way is to source the envs from a script file. But I have not created this file :) my oversight, I should have included it in the tarball. Let me do that and come back.
We can also recover using the uEnv.txt approach but we'll need to have script anyway, so let's do the script.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 18, 2023 07:48PM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> Did you erase the NAND block first?
Well, I thought I was being careful and stepping thru this, but obviously not. Guess I cherry-picked it and missed a pretty important step.
> OK so to recover from this. The quickest way is to
> source the envs from a script file. But I have not
> created this file :) my oversight, I should have
> included it in the tarball. Let me do that and
> come back.
>
> We can also recover using the uEnv.txt approach
> but we'll need to have script anyway, so let's do
> the script.
Sounds good. Maybe my mistake will help others when they see what screws up when you don't read, eh?
Sheesh.
-------------------------------------------------------
> Did you erase the NAND block first?
Quote
6. Flash default u-boot envs image
>
> If you are upgrading from 2017.07-tld-1 u-boot,
> you can skip this step. But some envs will need to
> be updated. See Note section below after the
> installation steps.
>
> Be extra careful with the next 2 commands, you
> should see output that look like below. If there
> is error, then do not reboot, post your problem
> here so we can help.
>
> Erase 1 block
> /usr/sbin/flash_erase /dev/mtd0 0xc0000 1
> Expected output:
> Erase Total 1 Units
> Performing Flash Erase of length 131072 at offset
> 0xc0000 done
>
> Write the image
> /usr/sbin/nandwrite -s 786432 /dev/mtd0
> /tmp/uboot.2023.04-tld-1.pogo_v4.environment.img
> Expected output:
> Writing data to block 6 at offset 0xc0000
Well, I thought I was being careful and stepping thru this, but obviously not. Guess I cherry-picked it and missed a pretty important step.
> OK so to recover from this. The quickest way is to
> source the envs from a script file. But I have not
> created this file :) my oversight, I should have
> included it in the tarball. Let me do that and
> come back.
>
> We can also recover using the uEnv.txt approach
> but we'll need to have script anyway, so let's do
> the script.
Sounds good. Maybe my mistake will help others when they see what screws up when you don't read, eh?
Sheesh.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 18, 2023 10:54PM |
Admin Registered: 13 years ago Posts: 18,545 |
Quote
Sounds good. Maybe my mistake will help others when they see what screws up when you don't read, eh?
Right on! also it is an opportunity to test this script. It should be an important part of your Debian rootfs.
=====
The script is attached to this post.
Mount the USB rootfs on another Linux box. Assuming it is mounted at /media/sdb1.
cd /media/sdb1/boot cp -a uboot.2023.04-tld-1.pogo_v4.boot.scr boot.scr syncUnmount and then bring it back to the Pogo V4.
With serial console connected, power up and let it boot automatically. The boot.scr should come into play, and allow booting to Debian.
Please post entire serial console log here.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/18/2023 11:14PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 18, 2023 11:21PM |
Registered: 1 year ago Posts: 81 |
It booted fine - found the uboot script /boot.scr and continued onward.
Here's the console log to the boot prompt:
So at least now it boots fine. Do I erase the NAND block next and retry the nandwrite of the image next, or do you have more I need to do?
Here's the console log to the boot prompt:
U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700)
Pogoplug V4
SoC: Kirkwood 88F6192_A1
Model: Cloud Engines PogoPlug Series 4
DRAM: 128 MiB
Core: 20 devices, 16 uclasses, devicetree: separate
NAND: 128 MiB
MMC: mvsdio@90000: 0
Loading Environment from NAND... NAND read from offset c0000 failed -74
*** Warning - readenv() failed, using default environment
In: serial
Out: serial
Err: serial
pcie0.0: Link up
Net:
Warning: ethernet-controller@72000 (eth0) using random MAC address - 1a:e7:a7:36:29:65
eth0: ethernet-controller@72000
Hit any key to stop autoboot: 10 9 8 7 6 5 4 3 2 1 0
Card did not respond to voltage select! : -110
starting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 2 USB Device(s) found
scanning bus xhci_pci for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Device 0: Vendor: SanDisk Rev: 1.00 Prod: Cruzer Fit
Type: Removable Hard Disk
Capacity: 7632.0 MB = 7.4 GB (15630336 x 512)
... is now current device
Scanning usb 0:1...
Found U-Boot script /boot.scr
1163 bytes read in 9 ms (126 KiB/s)
## Executing script at 00200000
loading uImage ...
5435888 bytes read in 165 ms (31.4 MiB/s)
loading uInitrd ...
9672378 bytes read in 270 ms (34.2 MiB/s)
loading DTB file ...
9970 bytes read in 19 ms (511.7 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-5.13.6-kirkwood-tld-1
Created: 2021-09-24 0:22:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5435824 Bytes = 5.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-5.13.6-kirkwood-tld-1
Created: 2023-05-19 0:29:23 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9672314 Bytes = 9.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 02c00000
Booting using the fdt blob at 0x2c00000
Working FDT set to 2c00000
Starting kernel ...
Loading Kernel Image
Loading Ramdisk to 07212000, end 07b4b67a ... OK
Loading Device Tree to 0720c000, end 072116f1 ... OK
Working FDT set to 720c000
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.13.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Sat Jul 31 22:10:39 PDT 2021
[ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: Pogoplug v4
[ 0.000000][ T0] printk: bootconsole [earlycon0] enabled
[ 0.000000][ T0] Memory policy: Data cache writeback
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 32512
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot)ro,3M(uImage),3M(uImage2),8M(failsafe),112M(root) earlyprintk=serial
[ 0.000000][ T0] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.000000][ T0] Memory: 101108K/131072K available (11264K kernel code, 1553K rwdata, 4272K rodata, 1024K init, 309K bss, 29964K reserved, 0K cma-reserved)
[ 0.000000][ T0] random: get_random_u32 called from ____cache_alloc+0x408/0x7b4 with crng_init=0
[ 0.000000][ T0] trace event string verifier disabled
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 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] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[ 0.000003][ T0] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[ 0.008559][ T0] Switching to timer-based delay loop, resolution 6ns
[ 0.016442][ T0] Console: colour dummy device 80x30
[ 0.021731][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.033012][ T0] pid_max: default: 32768 minimum: 301
[ 0.038998][ T0] LSM: Security Framework initializing
[ 0.044559][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.052654][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.063309][ T0] CPU: Testing write buffer coherency: ok
[ 0.072632][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.080053][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.086353][ T1] rcu: Hierarchical SRCU implementation.
[ 0.094083][ T1] devtmpfs: initialized
[ 0.106697][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.117390][ T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.180865][ T1] prandom32: self test passed (less than 6 bits correlated)
[ 0.188027][ T1] prandom: seed boundary self test passed
[ 0.199937][ T1] prandom: 100 self tests passed
[ 0.204743][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.213201][ T1] NET: Registered protocol family 16
[ 0.219791][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.228927][ T1] audit: initializing netlink subsys (disabled)
[ 0.237178][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.237744][ T16] audit: type=2000 audit(0.220:1): state=initialized audit_enabled=0 res=1
[ 0.253195][ T1] cpuidle: using governor ladder
[ 0.258126][ T1] cpuidle: using governor menu
[ 0.263636][ T1] Feroceon L2: Enabling L2
[ 0.267952][ T1] Feroceon L2: Cache support initialised.
[ 0.287109][ T1] No ATAGs?
[ 2.568569][ C0] random: fast init done
[ 7.590231][ T39] "cryptomgr_test" (39) uses obsolete ecb(arc4) skcipher
[ 7.636119][ T59] wait_for_initramfs() called before rootfs_initcalls
[ 7.848910][ T1] raid6: int32x8 gen() 74 MB/s
[ 8.018682][ T1] raid6: int32x8 xor() 46 MB/s
[ 8.188638][ T1] raid6: int32x4 gen() 76 MB/s
[ 8.358743][ T1] raid6: int32x4 xor() 49 MB/s
[ 8.528715][ T1] raid6: int32x2 gen() 100 MB/s
[ 8.698704][ T1] raid6: int32x2 xor() 60 MB/s
[ 8.868659][ T1] raid6: int32x1 gen() 75 MB/s
[ 9.038884][ T1] raid6: int32x1 xor() 43 MB/s
[ 9.043837][ T1] raid6: using algorithm int32x2 gen() 100 MB/s
[ 9.049934][ T1] raid6: .... xor() 60 MB/s, rmw enabled
[ 9.055406][ T1] raid6: using intx1 recovery algorithm
[ 9.061198][ T1] vgaarb: loaded
[ 9.065401][ T1] SCSI subsystem initialized
[ 9.070639][ T1] usbcore: registered new interface driver usbfs
[ 9.076888][ T1] usbcore: registered new interface driver hub
[ 9.083020][ T1] usbcore: registered new device driver usb
[ 9.089093][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 9.094744][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 9.104593][ T1] PTP clock support registered
[ 9.111966][ T1] clocksource: Switched to clocksource orion_clocksource
[ 9.263031][ T1] VFS: Disk quotas dquot_6.6.0
[ 9.267785][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 9.319730][ T1] NET: Registered protocol family 2
[ 9.325072][ T1] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 9.343379][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 9.362036][ T1] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 9.370393][ T1] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 9.402044][ T1] TCP: Hash tables configured (established 1024 bind 1024)
[ 9.409475][ T1] MPTCP token hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 9.432074][ T1] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 9.439311][ T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 9.462354][ T1] NET: Registered protocol family 1
[ 9.472451][ T1] RPC: Registered named UNIX socket transport module.
[ 9.479060][ T1] RPC: Registered udp transport module.
[ 9.491997][ T1] RPC: Registered tcp transport module.
[ 9.497386][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 9.522001][ T1] PCI: CLS 0 bytes, default 32
[ 9.527112][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 9.534873][ T58] Trying to unpack rootfs image as initramfs...
[ 12.128299][ T58] Freeing initrd memory: 9448K
[ 12.963164][ T1] Initialise system trusted keyrings
[ 12.968375][ T1] Key type blacklist registered
[ 12.973533][ T1] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[ 12.980816][ T1] zbud: loaded
[ 12.986355][ T1] NFS: Registering the id_resolver key type
[ 12.992239][ T1] Key type id_resolver registered
[ 12.997114][ T1] Key type id_legacy registered
[ 13.001862][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 13.009282][ T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 13.017377][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 13.024833][ T1] jffs2: version 2.2. (NAND) (SUMMARY) ¬ 2001-2006 Red Hat, Inc.
[ 13.033394][ T1] fuse: init (API version 7.34)
[ 13.038663][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 13.046134][ T1] orangefs_init: module version upstream loaded
[ 13.052313][ T1] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabled
[ 13.213677][ T1] xor: measuring software checksum speed
[ 13.232489][ T1] arm4regs : 746 MB/sec
[ 13.259628][ T1] 8regs : 447 MB/sec
[ 13.279909][ T1] 32regs : 651 MB/sec
[ 13.285013][ T1] xor: using function: arm4regs (746 MB/sec)
[ 13.290838][ T1] async_tx: api initialized (async)
[ 13.295950][ T1] Key type asymmetric registered
[ 13.300732][ T1] Asymmetric key parser 'x509' registered
[ 13.306421][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 13.314623][ T1] io scheduler bfq registered
[ 13.616374][ T1] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47
[ 13.624348][ T1] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49
[ 13.632903][ T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 13.643799][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges:
[ 13.653752][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0x00f1040000..0x00f1041fff -> 0x0000040000
[ 13.663886][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 13.674516][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: IO 0xffffffffffffffff..0x00fffffffe -> 0x0100000000
[ 13.685536][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 13.693827][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 13.700010][ T1] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0x00040000-0x00041fff])
[ 13.710877][ T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 13.718461][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 13.725600][ T1] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[ 13.732351][ T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 13.741417][ T1] PCI: bus0: Fast back to back transfers disabled
[ 13.747744][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 13.756781][ T1] pci 0000:01:00.0: [1b73:1009] type 00 class 0x0c0330
[ 13.763536][ T1] pci 0000:01:00.0: reg 0x10: [mem 0x90000000-0x9000ffff 64bit]
[ 13.771023][ T1] pci 0000:01:00.0: reg 0x18: [mem 0x90010000-0x90010fff 64bit]
[ 13.778534][ T1] pci 0000:01:00.0: reg 0x20: [mem 0x90011000-0x90011fff 64bit]
[ 13.786143][ T1] pci 0000:01:00.0: supports D1
[ 13.790846][ T1] pci 0000:01:00.0: PME# supported from D0 D1 D3hot
[ 13.797396][ 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 4.000 Gb/s with 5.0 GT/s PCIe x1 link)
[ 13.843321][ T1] PCI: bus1: Fast back to back transfers disabled
[ 13.849594][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 13.857223][ T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[ 13.864825][ T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[ 13.872766][ T1] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe000ffff 64bit]
[ 13.880768][ T1] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0010000-0xe0010fff 64bit]
[ 13.888796][ T1] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0011000-0xe0011fff 64bit]
[ 13.896829][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 13.902516][ T1] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 13.910141][ T1] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[ 13.917883][ T1] mv_xor f1060800.xor: Marvell shared XOR driver
[ 13.983649][ T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 13.995634][ T1] mv_xor f1060900.xor: Marvell shared XOR driver
[ 14.063639][ T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 14.076068][ T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 14.085257][ T1] printk: console [ttyS0] disabled
[ 14.090333][ T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 10416666) is a 16550A
[ 14.100333][ T1] printk: console [ttyS0] enabled
[ 14.100333][ T1] printk: console [ttyS0] enabled
[ 14.110135][ T1] printk: bootconsole [earlycon0] disabled
[ 14.110135][ T1] printk: bootconsole [earlycon0] disabled
[ 14.134698][ T1] loop: module loaded
[ 14.139755][ T1] sata_mv f1080000.sata: slots 32 ports 2
[ 14.151106][ T1] scsi host0: sata_mv
[ 14.156039][ T1] scsi host1: sata_mv
[ 14.160277][ T1] ata1: SATA max UDMA/133 irq 32
[ 14.165148][ T1] ata2: SATA max UDMA/133 irq 32
[ 14.171498][ T1] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 14.178586][ T1] nand: Hynix H27U1G8F2BTR-BC
[ 14.183135][ T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 14.191823][ T1] Scanning device for bad blocks
[ 14.297789][ T1] 5 cmdlinepart partitions found on MTD device orion_nand
[ 14.304762][ T1] Creating 5 MTD partitions on "orion_nand":
[ 14.310590][ T1] 0x000000000000-0x000000200000 : "u-boot"
[ 14.318564][ T1] 0x000000200000-0x000000500000 : "uImage"
[ 14.326389][ T1] 0x000000500000-0x000000800000 : "uImage2"
[ 14.334254][ T1] 0x000000800000-0x000001000000 : "failsafe"
[ 14.342233][ T1] 0x000001000000-0x000008000000 : "root"
[ 14.351365][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 14.359936][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All Rights Reserved.
[ 14.372101][ T1] libphy: Fixed MDIO Bus: probed
[ 14.379112][ T1] libphy: orion_mdio_bus: probed
[ 14.408684][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 14.492501][ T94] ata1: SATA link down (SStatus 0 SControl F300)
[ 14.833769][ T96] ata2: SATA link down (SStatus 0 SControl F300)
[ 15.173444][ T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 5e:2b:15:71:ec:b6
[ 15.183106][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 15.190353][ T1] ehci-pci: EHCI PCI platform driver
[ 15.195610][ T1] ehci-orion: EHCI orion driver
[ 15.200621][ T1] orion-ehci f1050000.ehci: EHCI Host Controller
[ 15.206884][ T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 15.215507][ T1] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[ 15.252019][ T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 15.259136][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.13
[ 15.268118][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 15.276046][ T1] usb usb1: Product: EHCI Host Controller
[ 15.281610][ T1] usb usb1: Manufacturer: Linux 5.13.6-kirkwood-tld-1 ehci_hcd
[ 15.289014][ T1] usb usb1: SerialNumber: f1050000.ehci
[ 15.295464][ T1] hub 1-0:1.0: USB hub found
[ 15.299981][ T1] hub 1-0:1.0: 1 port detected
[ 15.305989][ T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 15.311930][ T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 15.321852][ T1] xhci_hcd 0000:01:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000000080010
[ 15.332750][ T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.13
[ 15.341703][ T1] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 15.349638][ T1] usb usb2: Product: xHCI Host Controller
[ 15.355232][ T1] usb usb2: Manufacturer: Linux 5.13.6-kirkwood-tld-1 xhci-hcd
[ 15.362636][ T1] usb usb2: SerialNumber: 0000:01:00.0
[ 15.368888][ T1] hub 2-0:1.0: USB hub found
[ 15.373485][ T1] hub 2-0:1.0: 2 ports detected
[ 15.379178][ T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 15.385220][ T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[ 15.393371][ T1] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ 15.400450][ T1] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 15.409734][ T1] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.13
[ 15.418713][ T1] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 15.426642][ T1] usb usb3: Product: xHCI Host Controller
[ 15.432230][ T1] usb usb3: Manufacturer: Linux 5.13.6-kirkwood-tld-1 xhci-hcd
[ 15.439609][ T1] usb usb3: SerialNumber: 0000:01:00.0
[ 15.446077][ T1] hub 3-0:1.0: USB hub found
[ 15.450581][ T1] hub 3-0:1.0: 2 ports detected
[ 15.456742][ T1] usbcore: registered new interface driver usb-storage
[ 15.464197][ T1] mousedev: PS/2 mouse device common for all mice
[ 15.592013][ T17] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 15.793266][ T17] usb 1-1: New USB device found, idVendor=0781, idProduct=5571, bcdDevice= 1.00
[ 15.802165][ T17] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 15.810014][ T17] usb 1-1: Product: Cruzer Fit
[ 15.814655][ T17] usb 1-1: Manufacturer: SanDisk
[ 15.819441][ T17] usb 1-1: SerialNumber: 4C530001061106120510
[ 15.826454][ T17] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 15.834207][ T17] scsi host2: usb-storage 1-1:1.0
[ 16.492027][ T1] rtc-mv f1010300.rtc: internal RTC not ticking
[ 16.498384][ T1] i2c /dev entries driver
[ 16.503552][ T1] device-mapper: uevent: version 1.0.3
[ 16.509263][ T1] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.com
[ 16.519093][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 16.526400][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 16.533734][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 16.541118][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 16.547922][ T1] device-mapper: raid: Loading target version 1.15.1
[ 16.556554][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 16.562926][ T1] drop_monitor: Initializing network drop monitor service
[ 16.570560][ T1] NET: Registered protocol family 10
[ 16.577838][ T1] Segment Routing with IPv6
[ 16.582334][ T1] RPL Segment Routing with IPv6
[ 16.587164][ T1] NET: Registered protocol family 17
[ 16.592656][ T1] Key type dns_resolver registered
[ 16.598531][ T1] registered taskstats version 1
[ 16.603434][ T1] Loading compiled-in X.509 certificates
[ 16.609578][ T1] zswap: loaded using pool lzo/zbud
[ 16.615250][ T1] Key type ._fscrypt registered
[ 16.619955][ T1] Key type .fscrypt registered
[ 16.624665][ T1] Key type fscrypt-provisioning registered
[ 16.633960][ T1] Key type big_key registered
[ 16.683501][ T1] Key type encrypted registered
[ 16.697869][ T1] Freeing unused kernel memory: 1024K
[ 16.723313][ T1] Checked W+X mappings: passed, no W+X pages found
[ 16.729686][ T1] Run /init as init process
Loading, please wait...
[ 16.893929][ T58] scsi 2:0:0:0: Direct-Access SanDisk Cruzer Fit 1.00 PQ: 0 ANSI: 6
[ 16.913855][ T7] sd 2:0:0:0: [sda] 15630336 512-byte logical blocks: (8.00 GB/7.45 GiB)
[ 16.933611][ T7] sd 2:0:0:0: [sda] Write Protect is off
[ 16.952141][ T7] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Starting version 247.3-7+deb11u2
[ 16.979200][ T7] sda: sda1
[ 16.988963][ T7] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 18.154373][ T137] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[ 18.442377][ T141] usbcore: registered new interface driver uas
[ 18.602894][ T7] mvsdio f1090000.mvsdio: Got CD GPIO
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/sda1] fsck.ext4 -a -C0 /dev/sda1
rootfs: clean, 18156/488640 files, 368121/1953536 blocks
done.
[ 29.483112][ T168] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null). Quota mode: none.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 30.441204][ T1] systemd[1]: System time before build time, advancing clock.
[ 30.510946][ T1] systemd[1]: Inserted module 'autofs4'
[ 30.605870][ T1] systemd[1]: systemd 247.3-7+deb11u2 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)
[ 30.630983][ T1] systemd[1]: Detected architecture arm.
Welcome to Debian GNU/Linux 11 (bullseye)!
[ 30.674388][ T1] systemd[1]: Set hostname to <deb04>.
[ 33.246776][ T1] systemd[1]: Queued start job for default target Graphical Interface.
[ 33.258699][ T1] random: systemd: uninitialized urandom read (16 bytes read)
[ 33.266662][ T1] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[ 33.279831][ T1] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[ 33.291863][ T1] systemd[1]: Created slice system-getty.slice.
[ OK ] Created slice system-getty.slice.
[ 33.332417][ T1] random: systemd: uninitialized urandom read (16 bytes read)
[ 33.341478][ T1] systemd[1]: Created slice system-modprobe.slice.
[ OK ] Created slice system-modprobe.slice.
[ 33.382364][ T1] random: systemd: uninitialized urandom read (16 bytes read)
[ 33.391385][ T1] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 33.433749][ T1] systemd[1]: Created slice User and Session Slice.
[ OK ] Created slice User and Session Slice.
[ 33.473215][ T1] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Dispatch Password …ts to Console Directory Watch.
[ 33.513058][ T1] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ OK ] Started Forward Password R…uests to Wall Directory Watch.
[ 33.554309][ T1] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ OK ] Set up automount Arbitrary…s File System Automount Point.
[ 33.592885][ T1] systemd[1]: Reached target Local Encrypted Volumes.
[ OK ] Reached target Local Encrypted Volumes.
[ 33.633214][ T1] systemd[1]: Reached target Paths.
[ OK ] Reached target Paths.
[ 33.672978][ T1] systemd[1]: Reached target Slices.
[ OK ] Reached target Slices.
[ 33.715488][ T1] systemd[1]: Listening on RPCbind Server Activation Socket.
[ OK ] Listening on RPCbind Server Activation Socket.
[ 33.753676][ T1] systemd[1]: Listening on fsck to fsckd communication Socket.
[ OK ] Listening on fsck to fsckd communication Socket.
[ 33.793108][ T1] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ 33.834468][ T1] systemd[1]: Listening on Journal Audit Socket.
[ OK ] Listening on Journal Audit Socket.
[ 33.873806][ T1] systemd[1]: Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket (/dev/log).
[ 33.914065][ T1] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 33.954160][ T1] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 33.993603][ T1] systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 34.033932][ T1] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[ 34.049731][ T1] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 34.098315][ T1] systemd[1]: Mounting NFSD configuration filesystem...
Mounting NFSD configuration filesystem...
[ 34.148502][ T1] systemd[1]: Mounting RPC Pipe File System...
Mounting RPC Pipe File System...
[ 34.199512][ T1] systemd[1]: Mounting Kernel Debug File System...
Mounting Kernel Debug File System...
[ 34.249272][ T1] systemd[1]: Mounting Kernel Trace File System...
Mounting Kernel Trace File System...
[ 34.292806][ T1] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[ 34.313100][ T1] systemd[1]: Starting Restore / save the current clock...
Starting Restore / save the current clock...
[ 34.360699][ T1] systemd[1]: Starting Create list of static device nodes for the current kernel...
Starting Create list of st‚odes for the current kernel...
[ 34.420419][ T1] systemd[1]: Starting Load Kernel Module configfs...
[ 34.427797][ C0] random: crng init done
[ 34.431902][ C0] random: 7 urandom warning(s) missed due to ratelimiting
Starting Load Kernel Module configfs...
[ 34.500077][ T1] systemd[1]: Starting Load Kernel Module drm...
Starting Load Kernel Module drm...
[ 34.550284][ T1] systemd[1]: Starting Load Kernel Module fuse...
Starting Load Kernel Module fuse...
[ 34.607014][ T1] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 34.617616][ T1] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[ 34.635288][ T1] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 34.664182][ T1] systemd[1]: Starting Load Kernel Modules...
Starting Load Kernel Modules...
[ 34.729399][ T1] systemd[1]: Starting Remount Root and Kernel File Systems...
Starting Remount Root and Kernel File Systems...
[ 34.809374][ T1] systemd[1]: Starting Coldplug All udev Devices...
Starting Coldplug All udev Devices...
[ 34.987031][ T1] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted POSIX Message Queue File System.
[ 35.064277][ T1] systemd[1]: Mounted NFSD configuration filesystem.
[ OK ] Mounted NFSD configuration filesystem.
[ 35.113811][ T1] systemd[1]: Mounted RPC Pipe File System.
[ OK ] Mounted RPC Pipe File System.
[ 35.153793][ T1] systemd[1]: Mounted Kernel Debug File System.
[ OK ] Mounted Kernel Debug File System.
[ 35.193685][ T1] systemd[1]: Mounted Kernel Trace File System.
[ OK ] Mounted Kernel Trace File System.
[ 35.235426][ T1] systemd[1]: Finished Restore / save the current clock.
[ OK ] Finished Restore / save the current clock.
[ 35.296288][ T214] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[ 35.356633][ T1] systemd[1]: Finished Create list of static device nodes for the current kernel.
[ OK ] Finished Create list of st… nodes for the current kernel.
[ 35.445832][ T1] systemd[1]: modprobe@configfs.service: Succeeded.
[ 35.474265][ T1] systemd[1]: Finished Load Kernel Module configfs.
[ OK ] Finished Load Kernel Module configfs.
[ 35.505911][ T1] systemd[1]: modprobe@drm.service: Succeeded.
[ 35.534285][ T1] systemd[1]: Finished Load Kernel Module drm.
[ OK ] Finished Load Kernel Module drm.
[ 35.566284][ T1] systemd[1]: modprobe@fuse.service: Succeeded.
[ 35.584221][ T1] systemd[1]: Finished Load Kernel Module fuse.
[ OK ] Finished Load Kernel Module fuse.
[ 35.632459][ T1] systemd[1]: Finished Load Kernel Modules.
[ OK ] Finished Load Kernel Modules.
[ 35.675440][ T1] systemd[1]: Finished Remount Root and Kernel File Systems.
[ OK ] Finished Remount Root and Kernel File Systems.
[ 35.763091][ T1] systemd[1]: Activating swap /swapfile1...
Activating swap /swapfile1...
[ 35.845194][ T1] systemd[1]: Mounting FUSE Control File System...
Mounting FUSE Control File System...
[ 35.922271][ T218] Adding 524284k swap on /swapfile1. Priority:-2 extents:3 across:540668k FS
[ 35.973354][ T1] systemd[1]: Mounting Kernel Configuration File System...
Mounting Kernel Configuration File System...
[ 36.063210][ T1] systemd[1]: Starting pNFS block layout mapping daemon...
Starting pNFS block layout mapping daemon...
[ 36.094900][ T1] systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped.
[ 36.127690][ T1] systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped.
[ 36.174221][ T1] systemd[1]: Starting Load/Save Random Seed...
Starting Load/Save Random Seed...
[ 36.228505][ T1] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 36.299316][ T1] systemd[1]: Starting Create System Users...
Starting Create System Users...
[ 36.356910][ T1] systemd[1]: Activated swap /swapfile1.
[ OK ] Activated swap /swapfile1.
[ 36.465284][ T1] systemd[1]: Started Journal Service.
[ OK ] Started Journal Service.
[ OK ] Mounted FUSE Control File System.
[ OK ] Mounted Kernel Configuration File System.
[ OK ] Started pNFS block layout mapping daemon.
[ OK ] Finished Load/Save Random Seed.
[ OK ] Finished Apply Kernel Variables.
[ OK ] Reached target Swap.
Starting Flush Journal to Persistent Storage...
[ OK ] Finished Create System Users.
Starting Create Static Device Nodes in /dev...
[ OK ] Finished 37.111911][ T210] systemd-journald[210]: Received client request to flush runtime journal.
;1;39mColdplug All udev Devices.
[ 37.155338][ T210] systemd-journald[210]: File /var/log/journal/c4334d5b2fba8bce5294b56551baee86/system.journal corrupted or uncleanly shut down, renaming and replacing.
Starting Helper to synchronize boot up for ifupdown...
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Preprocess NFS configuration...
Starting Rule-based Manage‚for Device Events and Files...
[ OK ] Finished Preprocess NFS configuration.
Starting NFSv4 ID-name mapping service...
[ OK ] Reached target NFS client services.
[ OK ] Finished Flush Journal to Persistent Storage.
Starting Create Volatile Files and Directories...
[ OK ] Started NFSv4 ID-name mapping service.
[ OK ] Started Rule-based Manager for Device Events and Files.
[ OK ] Finished Create Volatile Files and Directories.
Starting RPC bind portmap service...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started RPC bind portmap service.
[ OK ] Reached target RPC Port Mapper.
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Periodic ext4 Onli…ata Check for All Filesystems.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Update the plocate database daily.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started D-Bus System Message Bus.
Starting Remove Stale Onli‚t4 Metadata Check Snapshots...
Starting User Login Management...
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Finished Remove Stale Onli…ext4 Metadata Check Snapshots.
[ OK ] Started User Login Management.
[ OK ] Found device /dev/ttyS0.
[ 41.262205][ T242] orion_wdt: Initial timeout 25 sec
[ 42.059128][ T241] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 42.112528][ T239] sd 2:0:0:0: Attached scsi generic sg0 type 0
[* ] A start job is running for Helper t‚oot up for ifupdown (9s / 3min 3s)
[ OK ] Finished Helper to synchronize boot up for ifupdown.
Starting Raise network interfaces...
[** ] A start job is running for Raise network interfaces (12s / 5min 10s)
[ 46.992825][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 47.003487][ T100] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ ***] A start job is running for Raise network interfaces (14s / 5min 10s)
[ OK ] Finished Raise network interfaces.
[ OK ] Reached target Network.
Starting NFS Mount Daemon...
Starting Network Time Service...
Starting /etc/rc.local Compatibility...
Starting OpenBSD Secure Shell server...
[ OK ] Started systune service.
[ OK ] Started NFS Mount Daemon.
Starting NFS server and services...
[ OK ] Started Network Time Service.
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started OpenBSD Secure Shell server.
[ 56.297973][ T386] NFSD: Using UMH upcall client tracking operations.
[ 56.304717][ T386] NFSD: starting 90-second grace period (net f000001c)
[ OK ] Finished NFS server and services.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
Starting LSB: Starts syslogd...
Starting Permit User Sessions...
[ OK ] Finished Permit User Sessions.
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[ OK ] Started LSB: Starts syslogd.
Starting LSB: Starts klogd...
[ OK ] Started LSB: Starts klogd.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Finished Update UTMP about System Runlevel Changes.
Debian GNU/Linux 11 deb04 ttyS0
deb04 login:
So at least now it boots fine. Do I erase the NAND block next and retry the nandwrite of the image next, or do you have more I need to do?
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 19, 2023 12:46AM |
Admin Registered: 13 years ago Posts: 18,545 |
> It booted fine - found the uboot script /boot.scr
> and continued onward.
Cool! This is another major enhancement but I did not want to advertise it (it's not relevant to what we do here, and it'll take some detailed explanation).
> Here's the console log to the boot prompt:
It looks good.
>
> So at least now it boots fine. Do I erase the NAND
> block next and retry the nandwrite of the image
> next, or do you have more I need to do?
Yes, so back to Step 6 and onward.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> and continued onward.
Cool! This is another major enhancement but I did not want to advertise it (it's not relevant to what we do here, and it'll take some detailed explanation).
> Here's the console log to the boot prompt:
It looks good.
>
> So at least now it boots fine. Do I erase the NAND
> block next and retry the nandwrite of the image
> next, or do you have more I need to do?
Yes, so back to Step 6 and onward.
Quote
6. Flash default u-boot envs image
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 19, 2023 01:29AM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> > So at least now it boots fine. Do I erase the NAND
> > block next and retry the nandwrite of the image
> > next, or do you have more I need to do?
>
> Yes, so back to Step 6 and onward.
>
So I tried:
-------------------------------------------------------
> > So at least now it boots fine. Do I erase the NAND
> > block next and retry the nandwrite of the image
> > next, or do you have more I need to do?
>
> Yes, so back to Step 6 and onward.
>
Quote
6. Flash default u-boot envs image
So I tried:
root@deb05:/tmp# /usr/sbin/flash_erase /dev/mtd0 0xc0000 1
flash_erase: error!: /dev/mtd0
error 13 (Permission denied)
I seem to remember somewhere here about having to unlock a write-protect setting, but I'm not finding it to reference. Did I hit that problem here, or is it something else?
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 19, 2023 02:55PM |
Admin Registered: 13 years ago Posts: 18,545 |
dhargens,
> I seem to remember somewhere here about having to
> unlock a write-protect setting, but I'm not
> finding it to reference. Did I hit that problem
> here, or is it something else?
No, it is not related to that. Let me look at my script again.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I seem to remember somewhere here about having to
> unlock a write-protect setting, but I'm not
> finding it to reference. Did I hit that problem
> here, or is it something else?
No, it is not related to that. Let me look at my script again.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 19, 2023 03:05PM |
Admin Registered: 13 years ago Posts: 18,545 |
Here is the updated boot script. I've had a wrong mtdparts in the script before. It was
Please try again.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
setenv mtdparts "mtdparts=orion_nand:2M(u-boot)ro,3M(uImage),3M(uImage2),8M(failsafe),112M(root)"
Should be
setenv mtdparts "mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)"
Please try again.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 19, 2023 04:19PM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> Here is the updated boot script. I've had a wrong
> mtdparts in the script before. It should be:
That change makes sense. I'll get to it after midnight CT (in office now) and let you know it works. ;-)
I have a 2nd V4 with 2017.07 on it, so thought I'd update it. I did something new this time - I followed the instructions! (It works a lot better that way!)
I made several thumbs for booting, and on this one (it's hard to keep track) doesn't look like the /boot.scr is there - and it doesn't need it either.
There are 2 places where I notice that my output differs from the instructions:
on Step 5, under "Erase 4 blocks", the Expected output on both my V4s shows the following:
It boots from either USB 2 or 3, and seems like a perfectly functioning system now. I have the boot logs and can include them if you'd like.
So, in conclusion, if you follow the instructions ... the update of uboot from 2017.07 to 2023.04 works perfectly and is straightforward. OTOH, if you don't follow them, you'll need bodhi's help to get out of it.
-------------------------------------------------------
> Here is the updated boot script. I've had a wrong
> mtdparts in the script before. It should be:
setenv mtdparts "mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)"> Please try again.
That change makes sense. I'll get to it after midnight CT (in office now) and let you know it works. ;-)
I have a 2nd V4 with 2017.07 on it, so thought I'd update it. I did something new this time - I followed the instructions! (It works a lot better that way!)
I made several thumbs for booting, and on this one (it's hard to keep track) doesn't look like the /boot.scr is there - and it doesn't need it either.
There are 2 places where I notice that my output differs from the instructions:
on Step 5, under "Erase 4 blocks", the Expected output on both my V4s shows the following:
# flash_erase /dev/mtd0 0 4 Erasing 128 Kibyte @ 60000 -- 100 % completeand on Step 6, under "Erase 1 block", my outputs both show:
# /usr/sbin/flash_erase /dev/mtd0 0xc0000 1 Erasing 128 Kibyte @ c0000 -- 100 % completeIt still works, but isn't what's shown on the page. It might be that our versions of 'nandwrite' are different, and I can check that if you'd like. It didn't seem to matter, it worked just fine.
It boots from either USB 2 or 3, and seems like a perfectly functioning system now. I have the boot logs and can include them if you'd like.
So, in conclusion, if you follow the instructions ... the update of uboot from 2017.07 to 2023.04 works perfectly and is straightforward. OTOH, if you don't follow them, you'll need bodhi's help to get out of it.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 19, 2023 05:21PM |
Admin Registered: 13 years ago Posts: 18,545 |
> I have a 2nd V4 with 2017.07 on it, so thought I'd
> update it. I did something new this time - I
> followed the instructions! (It works a
> lot better that way!)
> I made several thumbs for booting, and on this one
> (it's hard to keep track) doesn't look like the
> /boot.scr is there - and it doesn't need it
> either.
Right! you don't need the boot.scr at all. It boots from the envs in the NAND block. The boot.scr is there to have a minimalist booting process, in case the env NAND block has problem, or had not been flashed.
>
> There are 2 places where I notice that my output
> differs from the instructions:
>
> on Step 5, under "Erase 4 blocks", the Expected
> output on both my V4s shows the following:
>
> both show:
>
> page. It might be that our versions of 'nandwrite'
> are different, and I can check that if you'd like.
> It didn't seem to matter, it worked just fine.
That's OK. flash_erase and nandwrite come in different versions. From time to time the developers changed the output format. And sometime the output is wrong. Such as
> It boots from either USB 2 or 3, and seems like a
> perfectly functioning system now. I have the boot
> logs and can include them if you'd like.
Cool! no need to post log. But keep them in safe place in case we need to see it again.
>
> So, in conclusion, if you follow the
> instructions ... the update of uboot from
> 2017.07 to 2023.04 works perfectly and is
> straightforward. OTOH, if you don't follow
> them, you'll need bodhi's help to get out of it.
:) I'll update the tarball to include the boot.scr and add another Note so users will have it ready to perform recovery when needed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> update it. I did something new this time - I
> followed the instructions! (It works a
> lot better that way!)
> I made several thumbs for booting, and on this one
> (it's hard to keep track) doesn't look like the
> /boot.scr is there - and it doesn't need it
> either.
Right! you don't need the boot.scr at all. It boots from the envs in the NAND block. The boot.scr is there to have a minimalist booting process, in case the env NAND block has problem, or had not been flashed.
>
> There are 2 places where I notice that my output
> differs from the instructions:
>
> on Step 5, under "Erase 4 blocks", the Expected
> output on both my V4s shows the following:
>
> # flash_erase /dev/mtd0 0 4 > Erasing 128 Kibyte @ 60000 -- 100 % complete >> and on Step 6, under "Erase 1 block", my outputs
> both show:
>
> # /usr/sbin/flash_erase /dev/mtd0 0xc0000 1 > Erasing 128 Kibyte @ c0000 -- 100 % complete >> It still works, but isn't what's shown on the
> page. It might be that our versions of 'nandwrite'
> are different, and I can check that if you'd like.
> It didn't seem to matter, it worked just fine.
That's OK. flash_erase and nandwrite come in different versions. From time to time the developers changed the output format. And sometime the output is wrong. Such as
Erasing 128 Kibyte @ 60000 -- 100 % complete
> It boots from either USB 2 or 3, and seems like a
> perfectly functioning system now. I have the boot
> logs and can include them if you'd like.
Cool! no need to post log. But keep them in safe place in case we need to see it again.
>
> So, in conclusion, if you follow the
> instructions ... the update of uboot from
> 2017.07 to 2023.04 works perfectly and is
> straightforward. OTOH, if you don't follow
> them, you'll need bodhi's help to get out of it.
:) I'll update the tarball to include the boot.scr and add another Note so users will have it ready to perform recovery when needed.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 20, 2023 01:08AM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> Here is the updated boot script. I've had a wrong
> mtdparts in the script before.
>
> Please try again.
Yup, that fixed it. Boots fine, did BOTH parts of Step 6 (flash_erase & nandwrite), then removed the boot.scr because it no longer needed the crutch, and it booted as expected. Changed the MAC to what's on the label and this one's a success! I'm now 2 for 2 updating from 2017.07 to 2023.04, with major assistance on the first update due to operator error.
-------------------------------------------------------
> Here is the updated boot script. I've had a wrong
> mtdparts in the script before.
>
> Please try again.
Yup, that fixed it. Boots fine, did BOTH parts of Step 6 (flash_erase & nandwrite), then removed the boot.scr because it no longer needed the crutch, and it booted as expected. Changed the MAC to what's on the label and this one's a success! I'm now 2 for 2 updating from 2017.07 to 2023.04, with major assistance on the first update due to operator error.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 20, 2023 05:13PM |
Admin Registered: 13 years ago Posts: 18,545 |
I've updated the first post: Overview, and uploaded new tarball to include boot.scr (therefore hash values change).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 20, 2023 07:35PM |
Registered: 1 year ago Posts: 44 |
bodhi Wrote:
-------------------------------------------------------
> I've updated the first post: Overview, and
> uploaded new tarball to include boot.scr
> (therefore hash values change).
i have not messed with the 2 pogo-v4-a3-01 yet that i have here.
this first message here onward, is what i need to follow to completely update them?
-------------------------------------------------------
> I've updated the first post: Overview, and
> uploaded new tarball to include boot.scr
> (therefore hash values change).
i have not messed with the 2 pogo-v4-a3-01 yet that i have here.
this first message here onward, is what i need to follow to completely update them?
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 21, 2023 12:00AM |
Admin Registered: 13 years ago Posts: 18,545 |
Use only the 1st post for installation, and ignore the testing done in subsequent posts.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/21/2023 02:12PM by bodhi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/21/2023 02:12PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 23, 2023 04:53PM |
Admin Registered: 13 years ago Posts: 18,545 |
Hi dhargens,
> > It boots from either USB 2 or 3, and seems like
> a
> > perfectly functioning system now. I have the
> boot
> > logs and can include them if you'd like.
>
> Cool! no need to post log. But keep them in safe
> place in case we need to see it again.
Please post the boot log. I'd like to double check a few things.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/23/2023 04:54PM by bodhi.
> > It boots from either USB 2 or 3, and seems like
> a
> > perfectly functioning system now. I have the
> boot
> > logs and can include them if you'd like.
>
> Cool! no need to post log. But keep them in safe
> place in case we need to see it again.
Please post the boot log. I'd like to double check a few things.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 05/23/2023 04:54PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 May 24, 2023 06:15PM |
Registered: 1 year ago Posts: 81 |
bodhi Wrote:
-------------------------------------------------------
> Please post the boot log. I'd like to double check a few things.
Here's an early boot log, with some lines truncated due to capturing a minicom window.
I'm not home to check these things until June 5 or 6, but it's a start.
I'll post another log I recorded (not truncated) in the next post.
-------------------------------------------------------
> Please post the boot log. I'd like to double check a few things.
Here's an early boot log, with some lines truncated due to capturing a minicom window.
I'm not home to check these things until June 5 or 6, but it's a start.
I'll post another log I recorded (not truncated) in the next post.
U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700)
Pogoplug V4
SoC: Kirkwood 88F6192_A1
Model: Cloud Engines PogoPlug Series 4
DRAM: 128 MiB
Core: 20 devices, 16 uclasses, devicetree: separate
NAND: 128 MiB
MMC: mvsdio@90000: 0
Loading Environment from NAND... OK
In: serial
Out: serial
Err: serial
pcie0.0: Link up
Net: eth0: ethernet-controller@72000
Hit any key to stop autoboot: 0
starting USB...
Bus ehci@50000: USB EHCI 1.00
Bus xhci_pci: Register 400081f NbrPorts 4
Starting the controller
USB XHCI 1.00
scanning bus ehci@50000 for devices... 2 USB Device(s) found
scanning bus xhci_pci for devices... 1 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Unknown command 'ide' - try 'help'
Card did not respond to voltage select! : -110
Partition Map for USB device 0 -- Partition Type: DOS
Part Start Sector Num Sectors UUID Type
1 2048 15631360 23781415-01 83
loading envs from usb 0 ...
Failed to load '/boot/uEnv.txt'
Unknown command 'ide' - try 'help'
Card did not respond to voltage select! : -110
running scan_disk ...
Scan device usb
device usb 0:1
1 bytes read in 12 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
5435888 bytes read in 236 ms (22 MiB/s)
loading uInitrd ...
9671910 bytes read in 409 ms (22.6 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
9970 bytes read in 20 ms (486.3 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-5.13.6-kirkwood-tld-1
Created: 2021-09-24 0:22:58 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 5435824 Bytes = 5.2 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-5.13.6-kirkwood-tld-1
Created: 2023-05-18 22:08:03 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 9671846 Bytes = 9.2 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
Booting using the fdt blob at 0x1c00000
Working FDT set to 1c00000
Starting kernel ...
Loading Kernel Image
Loading Ramdisk to 07213000, end 07b4c4a6 ... OK
Loading Device Tree to 0720d000, end 072126f1 ... OK
Working FDT set to 720d000
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 5.13.6-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.31
[ 0.000000][ T0] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[ 0.000000][ T0] CPU: VIVT data cache, VIVT instruction cache
[ 0.000000][ T0] OF: fdt: Machine model: Pogoplug v4
[ 0.000000][ T0] Memory policy: Data cache writeback
[ 0.000000][ T0] Zone ranges:
[ 0.000000][ T0] Normal [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Movable zone start for each node
[ 0.000000][ T0] Early memory node ranges
[ 0.000000][ T0] node 0: [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Initmem setup node 0 [mem 0x0000000000000000-0x0000000007ffffff]
[ 0.000000][ T0] Built 1 zonelists, mobility grouping on. Total pages: 32512
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdpa)
[ 0.000000][ T0] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes, linear)
[ 0.000000][ T0] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes, linear)
[ 0.000000][ T0] mem auto-init: stack:off, heap alloc:on, heap free:off
[ 0.000000][ T0] Memory: 101108K/131072K available (11264K kernel code, 1553K rwdata, 4272K rod)
[ 0.000000][ T0] random: get_random_u32 called from ____cache_alloc+0x408/0x7b4 with crng_init=0
[ 0.000000][ T0] trace event string verifier disabled
[ 0.000000][ T0] rcu: Preemptible hierarchical RCU implementation.
[ 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] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_is
[ 0.000003][ T0] sched_clock: 32 bits at 166MHz, resolution 6ns, wraps every 12884901885ns
[ 0.000090][ T0] Switching to timer-based delay loop, resolution 6ns
[ 0.001402][ T0] Console: colour dummy device 80x30
[ 0.001516][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 333)
[ 0.001578][ T0] pid_max: default: 32768 minimum: 301
[ 0.002194][ T0] LSM: Security Framework initializing
[ 0.002469][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.002545][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.004761][ T0] CPU: Testing write buffer coherency: ok
[ 0.008470][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.008938][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.009453][ T1] rcu: Hierarchical SRCU implementation.
[ 0.011731][ T1] devtmpfs: initialized
[ 0.020043][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19s
[ 0.020215][ T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.076223][ T1] prandom32: self test passed (less than 6 bits correlated)
[ 0.076293][ T1] prandom: seed boundary self test passed
[ 0.082630][ T1] prandom: 100 self tests passed
[ 0.082675][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.085178][ T1] NET: Registered protocol family 16
[ 0.086520][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.088036][ T1] audit: initializing netlink subsys (disabled)
[ 0.090317][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.090878][ T16] audit: type=2000 audit(0.080:1): state=initialized audit_enabled=0 res=1
[ 0.091169][ T1] cpuidle: using governor ladder
[ 0.091313][ T1] cpuidle: using governor menu
[ 0.092093][ T1] Feroceon L2: Enabling L2
[ 0.092171][ T1] Feroceon L2: Cache support initialised.
[ 0.105752][ T1] No ATAGs?
[ 2.560099][ C0] random: fast init done
[ 7.401024][ T39] "cryptomgr_test" (39) uses obsolete ecb(arc4) skcipher
[ 7.440073][ T59] wait_for_initramfs() called before rootfs_initcalls
[ 7.650364][ T1] raid6: int32x8 gen() 74 MB/s
[ 7.820161][ T1] raid6: int32x8 xor() 46 MB/s
[ 7.990154][ T1] raid6: int32x4 gen() 76 MB/s
[ 8.160173][ T1] raid6: int32x4 xor() 49 MB/s
[ 8.330256][ T1] raid6: int32x2 gen() 100 MB/s
[ 8.500202][ T1] raid6: int32x2 xor() 60 MB/s
[ 8.670260][ T1] raid6: int32x1 gen() 75 MB/s
[ 8.840147][ T1] raid6: int32x1 xor() 43 MB/s
[ 8.840173][ T1] raid6: using algorithm int32x2 gen() 100 MB/s
[ 8.840193][ T1] raid6: .... xor() 60 MB/s, rmw enabled
[ 8.840212][ T1] raid6: using intx1 recovery algorithm
[ 8.840631][ T1] vgaarb: loaded
[ 8.841475][ T1] SCSI subsystem initialized
[ 8.842265][ T1] usbcore: registered new interface driver usbfs
[ 8.842374][ T1] usbcore: registered new interface driver hub
[ 8.842459][ T1] usbcore: registered new device driver usb
[ 8.842793][ T1] pps_core: LinuxPPS API ver. 1 registered
[ 8.842817][ T1] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti>
[ 8.842869][ T1] PTP clock support registered
[ 8.845619][ T1] clocksource: Switched to clocksource orion_clocksource
[ 8.996658][ T1] VFS: Disk quotas dquot_6.6.0
[ 8.996819][ T1] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 9.019722][ T1] NET: Registered protocol family 2
[ 9.019973][ T1] IP idents hash table entries: 2048 (order: 2, 16384 bytes, linear)
[ 9.021391][ T1] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 4096 bytes, linear)
[ 9.021470][ T1] TCP established hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 9.021522][ T1] TCP bind hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 9.021565][ T1] TCP: Hash tables configured (established 1024 bind 1024)
[ 9.021955][ T1] MPTCP token hash table entries: 512 (order: 0, 6144 bytes, linear)
[ 9.022070][ T1] UDP hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 9.022134][ T1] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes, linear)
[ 9.022482][ T1] NET: Registered protocol family 1
[ 9.036250][ T1] RPC: Registered named UNIX socket transport module.
[ 9.036286][ T1] RPC: Registered udp transport module.
[ 9.036304][ T1] RPC: Registered tcp transport module.
[ 9.036322][ T1] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 9.036349][ T1] PCI: CLS 0 bytes, default 32
[ 9.036616][ T1] NetWinder Floating Point Emulator V0.97 (double precision)
[ 9.037505][ T58] Trying to unpack rootfs image as initramfs...
[ 11.617889][ T58] Freeing initrd memory: 9448K
[ 12.557366][ T1] Initialise system trusted keyrings
[ 12.557473][ T1] Key type blacklist registered
[ 12.557852][ T1] workingset: timestamp_bits=30 max_order=15 bucket_order=0
[ 12.558040][ T1] zbud: loaded
[ 12.560287][ T1] NFS: Registering the id_resolver key type
[ 12.560349][ T1] Key type id_resolver registered
[ 12.560372][ T1] Key type id_legacy registered
[ 12.560438][ T1] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 12.560476][ T1] nfs4flexfilelayout_init: NFSv4 Flexfile Layout Driver Registering...
[ 12.560499][ T1] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 12.560912][ T1] jffs2: version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
[ 12.561745][ T1] fuse: init (API version 7.34)
[ 12.562351][ T1] orangefs_debugfs_init: called with debug mask: :none: :0:
[ 12.562688][ T1] orangefs_init: module version upstream loaded
[ 12.562716][ T1] SGI XFS with ACLs, security attributes, realtime, scrub, quota, no debug enabld
[ 12.715454][ T1] xor: measuring software checksum speed
[ 12.728820][ T1] arm4regs : 746 MB/sec
[ 12.750937][ T1] 8regs : 447 MB/sec
[ 12.766165][ T1] 32regs : 651 MB/sec
[ 12.766192][ T1] xor: using function: arm4regs (746 MB/sec)
[ 12.766227][ T1] async_tx: api initialized (async)
[ 12.766257][ T1] Key type asymmetric registered
[ 12.766277][ T1] Asymmetric key parser 'x509' registered
[ 12.766371][ T1] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246)
[ 12.766490][ T1] io scheduler bfq registered
[ 13.063960][ T1] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 47
[ 13.064006][ T1] kirkwood-pinctrl f1010000.pin-controller: unknown pinctrl group 49
[ 13.064582][ T1] kirkwood-pinctrl f1010000.pin-controller: registered pinctrl driver
[ 13.067524][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@820000:
[ 13.067659][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0x00f1040000..0x00f1041fff ->0
[ 13.067728][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: MEM 0xffffffffffffffff..0x00fffff0
[ 13.067778][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: IO 0xffffffffffffffff..0x00fffff0
[ 13.068214][ T1] mvebu-pcie mbus@f1000000:pcie@82000000: PCI host bridge to bus 0000:00
[ 13.068251][ T1] pci_bus 0000:00: root bus resource [bus 00-ff]
[ 13.068288][ T1] pci_bus 0000:00: root bus resource [mem 0xf1040000-0xf1041fff] (bus address [0)
[ 13.068320][ T1] pci_bus 0000:00: root bus resource [mem 0xe0000000-0xefffffff]
[ 13.068349][ T1] pci_bus 0000:00: root bus resource [io 0x1000-0xeffff]
[ 13.068532][ T1] pci 0000:00:01.0: [11ab:6281] type 01 class 0x060400
[ 13.068592][ T1] pci 0000:00:01.0: reg 0x38: [mem 0x00000000-0x000007ff pref]
[ 13.070305][ T1] PCI: bus0: Fast back to back transfers disabled
[ 13.070361][ T1] pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 13.070718][ T1] pci 0000:01:00.0: [1b73:1009] type 00 class 0x0c0330
[ 13.070778][ T1] pci 0000:01:00.0: reg 0x10: [mem 0x90000000-0x9000ffff 64bit]
[ 13.070827][ T1] pci 0000:01:00.0: reg 0x18: [mem 0x90010000-0x90010fff 64bit]
[ 13.070872][ T1] pci 0000:01:00.0: reg 0x20: [mem 0x90011000-0x90011fff 64bit]
[ 13.071013][ T1] pci 0000:01:00.0: supports D1
[ 13.071041][ T1] pci 0000:01:00.0: PME# supported from D0 D1 D3hot
[ 13.071157][ T1] pci 0000:01:00.0: 2.000 Gb/s available PCIe bandwidth, limited by 2.5 GT/s PCI)
[ 13.096997][ T1] PCI: bus1: Fast back to back transfers disabled
[ 13.097048][ T1] pci_bus 0000:01: busn_res: [bus 01-ff] end is updated to 01
[ 13.097375][ T1] pci 0000:00:01.0: BAR 14: assigned [mem 0xe0000000-0xe00fffff]
[ 13.097419][ T1] pci 0000:00:01.0: BAR 6: assigned [mem 0xe0100000-0xe01007ff pref]
[ 13.097462][ T1] pci 0000:01:00.0: BAR 0: assigned [mem 0xe0000000-0xe000ffff 64bit]
[ 13.097508][ T1] pci 0000:01:00.0: BAR 2: assigned [mem 0xe0010000-0xe0010fff 64bit]
[ 13.097552][ T1] pci 0000:01:00.0: BAR 4: assigned [mem 0xe0011000-0xe0011fff 64bit]
[ 13.097596][ T1] pci 0000:00:01.0: PCI bridge to [bus 01]
[ 13.097628][ T1] pci 0000:00:01.0: bridge window [mem 0xe0000000-0xe00fffff]
[ 13.097816][ T1] pcieport 0000:00:01.0: enabling device (0140 -> 0142)
[ 13.098763][ T1] mv_xor f1060800.xor: Marvell shared XOR driver
[ 13.157291][ T1] mv_xor f1060800.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 13.161258][ T1] mv_xor f1060900.xor: Marvell shared XOR driver
[ 13.227296][ T1] mv_xor f1060900.xor: Marvell XOR (Registers Mode): ( xor cpy intr )
[ 13.231695][ T1] Serial: 8250/16550 driver, 2 ports, IRQ sharing disabled
[ 13.233827][ T1] printk: console [ttyS0] disabled
[ 13.233975][ T1] f1012000.serial: ttyS0 at MMIO 0xf1012000 (irq = 25, base_baud = 10416666) is A
[ 14.332390][ T1] printk: console [ttyS0] enabled
[ 14.350507][ T1] loop: module loaded
[ 14.355565][ T1] sata_mv f1080000.sata: slots 32 ports 2
[ 14.366905][ T1] scsi host0: sata_mv
[ 14.371741][ T1] scsi host1: sata_mv
[ 14.376073][ T1] ata1: SATA max UDMA/133 irq 32
[ 14.380868][ T1] ata2: SATA max UDMA/133 irq 32
[ 14.387271][ T1] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 14.394319][ T1] nand: Hynix H27U1G8F2BTR-BC
[ 14.398882][ T1] nand: 128 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
[ 14.407603][ T1] Scanning device for bad blocks
[ 14.513657][ T1] 5 cmdlinepart partitions found on MTD device orion_nand
[ 14.520637][ T1] Creating 5 MTD partitions on "orion_nand":
[ 14.526489][ T1] 0x000000000000-0x000000200000 : "u-boot"
[ 14.534416][ T1] 0x000000200000-0x000000500000 : "uImage"
[ 14.542225][ T1] 0x000000500000-0x000000800000 : "uImage2"
[ 14.550107][ T1] 0x000000800000-0x000001000000 : "failsafe"
[ 14.558097][ T1] 0x000001000000-0x000008000000 : "root"
[ 14.567266][ T1] wireguard: WireGuard 1.0.0 loaded. See www.wireguard.com for information.
[ 14.575828][ T1] wireguard: Copyright (C) 2015-2019 Jason A. Donenfeld <Jason@zx2c4.com>. All R.
[ 14.587942][ T1] libphy: Fixed MDIO Bus: probed
[ 14.594939][ T1] libphy: orion_mdio_bus: probed
[ 14.624277][ T1] mv643xx_eth: MV-643xx 10/100/1000 ethernet driver version 1.4
[ 14.718222][ T94] ata1: SATA link down (SStatus 0 SControl F300)
[ 15.067418][ T96] ata2: SATA link down (SStatus 0 SControl F300)
[ 15.387102][ T1] mv643xx_eth_port mv643xx_eth_port.0 eth0: port 0 with MAC address 00:25:31:05:3
[ 15.396759][ T1] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 15.404007][ T1] ehci-pci: EHCI PCI platform driver
[ 15.409254][ T1] ehci-orion: EHCI orion driver
[ 15.414265][ T1] orion-ehci f1050000.ehci: EHCI Host Controller
[ 15.420528][ T1] orion-ehci f1050000.ehci: new USB bus registered, assigned bus number 1
[ 15.429155][ T1] orion-ehci f1050000.ehci: irq 29, io mem 0xf1050000
[ 15.465668][ T1] orion-ehci f1050000.ehci: USB 2.0 started, EHCI 1.00
[ 15.472779][ T1] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.13
[ 15.481807][ T1] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 15.489737][ T1] usb usb1: Product: EHCI Host Controller
[ 15.495298][ T1] usb usb1: Manufacturer: Linux 5.13.6-kirkwood-tld-1 ehci_hcd
[ 15.502702][ T1] usb usb1: SerialNumber: f1050000.ehci
[ 15.509150][ T1] hub 1-0:1.0: USB hub found
[ 15.513670][ T1] hub 1-0:1.0: 1 port detected
[ 15.519679][ T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 15.525725][ T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 15.535548][ T1] xhci_hcd 0000:01:00.0: hcc params 0x200073a1 hci version 0x100 quirks 0x0000000
[ 15.546445][ T1] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.13
[ 15.555391][ T1] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 15.563326][ T1] usb usb2: Product: xHCI Host Controller
[ 15.568921][ T1] usb usb2: Manufacturer: Linux 5.13.6-kirkwood-tld-1 xhci-hcd
[ 15.576324][ T1] usb usb2: SerialNumber: 0000:01:00.0
[ 15.582578][ T1] hub 2-0:1.0: USB hub found
[ 15.587180][ T1] hub 2-0:1.0: 2 ports detected
[ 15.592869][ T1] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 15.598905][ T1] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 3
[ 15.607060][ T1] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ 15.614142][ T1] usb usb3: We don't know the algorithms for LPM for this host, disabling LPM.
[ 15.623421][ T1] usb usb3: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.13
[ 15.632402][ T1] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 15.640330][ T1] usb usb3: Product: xHCI Host Controller
[ 15.645918][ T1] usb usb3: Manufacturer: Linux 5.13.6-kirkwood-tld-1 xhci-hcd
[ 15.653297][ T1] usb usb3: SerialNumber: 0000:01:00.0
[ 15.659752][ T1] hub 3-0:1.0: USB hub found
[ 15.664260][ T1] hub 3-0:1.0: 2 ports detected
[ 15.670418][ T1] usbcore: registered new interface driver usb-storage
[ 15.677869][ T1] mousedev: PS/2 mouse device common for all mice
[ 15.805666][ T17] usb 1-1: new high-speed USB device number 2 using orion-ehci
[ 16.006789][ T17] usb 1-1: New USB device found, idVendor=0781, idProduct=5571, bcdDevice= 1.26
[ 16.015690][ T17] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 16.023546][ T17] usb 1-1: Product: Firebird USB Flash Drive
[ 16.029399][ T17] usb 1-1: Manufacturer: SanDisk
[ 16.034184][ T17] usb 1-1: SerialNumber: 4C532000030912115120
[ 16.041224][ T17] usb-storage 1-1:1.0: USB Mass Storage device detected
[ 16.048980][ T17] scsi host2: usb-storage 1-1:1.0
[ 16.725670][ T1] rtc-mv f1010300.rtc: internal RTC not ticking
[ 16.732032][ T1] i2c /dev entries driver
[ 16.737199][ T1] device-mapper: uevent: version 1.0.3
[ 16.742919][ T1] device-mapper: ioctl: 4.45.0-ioctl (2021-03-22) initialised: dm-devel@redhat.cm
[ 16.752752][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 16.760053][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 16.767389][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 16.774768][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 16.781567][ T1] device-mapper: raid: Loading target version 1.15.1
[ 16.790193][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 16.796565][ T1] drop_monitor: Initializing network drop monitor service
[ 16.804200][ T1] NET: Registered protocol family 10
[ 16.811475][ T1] Segment Routing with IPv6
[ 16.815961][ T1] RPL Segment Routing with IPv6
[ 16.820784][ T1] NET: Registered protocol family 17
[ 16.826281][ T1] Key type dns_resolver registered
[ 16.832097][ T1] registered taskstats version 1
[ 16.837001][ T1] Loading compiled-in X.509 certificates
[ 16.843149][ T1] zswap: loaded using pool lzo/zbud
[ 16.848825][ T1] Key type ._fscrypt registered
[ 16.853531][ T1] Key type .fscrypt registered
[ 16.858241][ T1] Key type fscrypt-provisioning registered
[ 16.867547][ T1] Key type big_key registered
[ 16.917311][ T1] Key type encrypted registered
[ 16.931649][ T1] Freeing unused kernel memory: 1024K
[ 16.956962][ T1] Checked W+X mappings: passed, no W+X pages found
[ 16.963332][ T1] Run /init as init process
Loading, please wait...
[ 17.129082][ T58] scsi 2:0:0:0: Direct-Access SanDisk Cruzer Fit 1.26 PQ: 0 ANSI: 5
[ 17.148764][ T7] sd 2:0:0:0: [sda] 15633408 512-byte logical blocks: (8.00 GB/7.45 GiB)
[ 17.167384][ T7] sd 2:0:0:0: [sda] Write Protect is off
[ 17.185789][ T7] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support A
Starting version 247.3-7+deb11u2
[ 17.212500][ T7] sda: sda1
[ 17.226867][ T7] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 18.426145][ T141] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[ 18.694388][ T141] usbcore: registered new interface driver uas
[ 18.832785][ T7] mvsdio f1090000.mvsdio: Got CD GPIO
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/sda1] fsck.ext4 -a -C0 /dev/sda1
rootfs: clean, 18126/488640 files, 361170/1953920 blocks
done.
[ 29.724119][ T168] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null). Quota.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 30.720330][ T1] systemd[1]: System time before build time, advancing clock.
[ 30.790908][ T1] systemd[1]: Inserted module 'autofs4'
[ 30.890535][ T1] systemd[1]: systemd 247.3-7+deb11u2 running in system mode. (+PAM +AUDIT +SELI)
[ 30.915735][ T1] systemd[1]: Detected architecture arm.
Welcome to Debian GNU/Linux 11 (bullseye)!
[ 30.967660][ T1] systemd[1]: Set hostname to <deb03>.
[ 33.521996][ T1] systemd[1]: Queued start job for default target Graphical Interface.
[ 33.534036][ T1] random: systemd: uninitialized urandom read (16 bytes read)
[ 33.541997][ T1] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local .
[ 33.555166][ T1] systemd[1]: (This warning is only shown for the first unit using IP firewallin)
[ 33.567386][ T1] systemd[1]: Created slice system-getty.slice.
[ OK ] Created slice system-getty.slice.
[ 33.606062][ T1] random: systemd: uninitialized urandom read (16 bytes read)
[ 33.615154][ T1] systemd[1]: Created slice system-modprobe.slice.
[ OK ] Created slice system-modprobe.slice.
[ 33.656104][ T1] random: systemd: uninitialized urandom read (16 bytes read)
[ 33.665143][ T1] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 33.707367][ T1] systemd[1]: Created slice User and Session Slice.
[ OK ] Created slice User and Session Slice.
[ 33.746852][ T1] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Dispatch Password â¦ts to Console Directory Watch.
[ 33.786776][ T1] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ OK ] Started Forward Password Râ¦uests to Wall Directory Watch.
[ 33.827938][ T1] systemd[1]: Set up automount Arbitrary Executable File Formats File System Aut.
[ OK ] Set up automount Arbitraryâ¦s File System Automount Point.
[ 33.866588][ T1] systemd[1]: Reached target Local Encrypted Volumes.
[ OK ] Reached target Local Encrypted Volumes.
[ 33.906825][ T1] systemd[1]: Reached target Paths.
[ OK ] Reached target Paths.
[ 33.946630][ T1] systemd[1]: Reached target Slices.
[ OK ] Reached target Slices.
[ 33.989055][ T1] systemd[1]: Listening on RPCbind Server Activation Socket.
[ OK ] Listening on RPCbind Server Activation Socket.
[ 34.027349][ T1] systemd[1]: Listening on fsck to fsckd communication Socket.
[ OK ] Listening on fsck to fsckd communication Socket.
[ 34.066821][ T1] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ 34.108064][ T1] systemd[1]: Listening on Journal Audit Socket.
[ OK ] Listening on Journal Audit Socket.
[ 34.147381][ T1] systemd[1]: Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket (/dev/log).
[ 34.187692][ T1] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 34.227705][ T1] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 34.267251][ T1] systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 34.307539][ T1] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[ 34.323457][ T1] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 34.352242][ T1] systemd[1]: Mounting NFSD configuration filesystem...
Mounting NFSD configuration filesystem...
[ 34.412271][ T1] systemd[1]: Mounting RPC Pipe File System...
Mounting RPC Pipe File System...
[ 34.463292][ T1] systemd[1]: Mounting Kernel Debug File System...
Mounting Kernel Debug File System...
[ 34.513098][ T1] systemd[1]: Mounting Kernel Trace File System...
Mounting Kernel Trace File System...
[ 34.556406][ T1] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS be.
[ 34.576444][ T1] systemd[1]: Starting Restore / save the current clock...
Starting Restore / save the current clock...
[ 34.624497][ T1] systemd[1]: Starting Create list of static device nodes for the current kernel.
Starting Create list of st…odes for the current kernel...
[ 34.712746][ T1] systemd[1]: Starting Load Kernel Module configfs...
Starting Load Kernel Module configfs...
[ 34.764097][ T1] systemd[1]: Starting Load Kernel Module drm...
Starting Load Kernel Module drm...
[ 34.813872][ T1] systemd[1]: Starting Load Kernel Module fuse...
Starting Load Kernel Module fuse...
[ 34.861376][ T1] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being.
[ 34.871952][ T1] systemd[1]: Condition check resulted in File System Check on Root Device being.
[ 34.889893][ T1] systemd[1]: Starting Journal Service...
Starting Journ[ 34.905356][ C0] random: crng init done
[ 34.909492][ C0] random: 7 urandom warning(s) missed due to ratelimiting
al Service...
[ 34.968286][ T1] systemd[1]: Starting Load Kernel Modules...
Starting Load Kernel Modules...
[ 35.017751][ T1] systemd[1]: Starting Remount Root and Kernel File Systems...
Starting Remount Root and Kernel File Systems...
[ 35.124373][ T1] systemd[1]: Starting Coldplug All udev Devices...
Starting Coldplug All udev Devices...
[ 35.301996][ T1] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted POSIX Message Queue File System.
[ 35.387210][ T1] systemd[1]: Mounted NFSD configuration filesystem.
[ OK ] Mounted NFSD configuration filesystem.
[ 35.415373][ T1] systemd[1]: Mounted RPC Pipe File System.
[ OK ] Mounted RPC Pipe File System.
[ 35.487880][ T1] systemd[1]: Mounted Kernel Debug File System.
[ OK ] Mounted Kernel Debug File System.
[ 35.527291][ T1] systemd[1]: Mounted Kernel Trace File System.
[ OK ] Mounted Kernel Trace File System.
[ 35.566436][ T1] systemd[1]: Finished Restore / save the current clock.
[ OK ] Finished Restore / save the current clock.
[ 35.614531][ T214] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro. Quota mode: none.
[ 35.636074][ T1] systemd[1]: Finished Create list of static device nodes for the current kernel.
[ OK ] Finished Create list of st⦠nodes for the current kernel.
[ 35.693932][ T1] systemd[1]: modprobe@configfs.service: Succeeded.
[ 35.746124][ T1] systemd[1]: Finished Load Kernel Module configfs.
[ OK ] Finished Load Kernel Module configfs.
[ 35.789390][ T1] systemd[1]: modprobe@drm.service: Succeeded.
[ 35.817748][ T1] systemd[1]: Finished Load Kernel Module drm.
[ OK ] Finished Load Kernel Module drm.
[ 35.839739][ T1] systemd[1]: modprobe@fuse.service: Succeeded.
[ 35.866178][ T1] systemd[1]: Finished Load Kernel Module fuse.
[ OK ] Finished Load Kernel Module fuse.
[ 35.916152][ T1] systemd[1]: Finished Load Kernel Modules.
[ OK ] Finished Load Kernel Modules.
[ 35.959150][ T1] systemd[1]: Finished Remount Root and Kernel File Systems.
[ OK ] Finished Remount Root and Kernel File Systems.
[ 36.046697][ T1] systemd[1]: Activating swap /swapfile1...
Activating swap /swapfile1...
[ 36.132510][ T1] systemd[1]: Mounting FUSE Control File System...
Mounting FUSE Control File System...
[ 36.205809][ T218] Adding 524284k swap on /swapfile1. Priority:-2 extents:3 across:540668k FS
[ 36.248274][ T1] systemd[1]: Mounting Kernel Configuration File System...
Mounting Kernel Configuration File System...
[ 36.327129][ T1] systemd[1]: Starting pNFS block layout mapping daemon...
Starting pNFS block layout mapping daemon...
[ 36.359635][ T1] systemd[1]: Condition check resulted in Rebuild Hardware Database being skippe.
[ 36.388420][ T1] systemd[1]: Condition check resulted in Platform Persistent Storage Archival b.
[ 36.448076][ T1] systemd[1]: Starting Load/Save Random Seed...
Starting Load/Save Random Seed...
[ 36.497643][ T1] systemd[1]: Starting Apply Kernel Variables...
Starting Apply Kernel Variables...
[ 36.567711][ T1] systemd[1]: Starting Create System Users...
Starting Create System Users...
[ 36.636143][ T1] systemd[1]: Activated swap /swapfile1.
[ OK ] Activated swap /swapfile1.
[ 36.709107][ T1] systemd[1]: Started Journal Service.
[ OK ] Started Journal Service.
[ OK ] Mounted FUSE Control File System.
[ OK ] Mounted Kernel Configuration File System.
[ OK ] Started pNFS block layout mapping daemon.
[ OK ] Finished Load/Save Random Seed.
[ OK ] Reached target Swap.
Starting Flush Journal to Persistent Storage...
[ OK ] Finished Apply Kernel Variables.
[ OK ] Finished Create System Users.
Starting Create Static Device Nodes in /dev...
[ 37.327824][ T210] systemd-journald[210]: Received client request to flush runtime journal.
[ 37.377084][ T210] systemd-journald[210]: File /var/log/journal/c4334d5b2fba8bce5294b56551baee86/.
[ OK ] Finished Coldplug All udev Devices.
Starting Helper to synchronize boot up for ifupdown...
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Preprocess NFS configuration...
Starting Rule-based Manage…for Device Events and Files...
[ OK ] Finished Preprocess NFS configuration.
Starting NFSv4 ID-name mapping service...
[ OK ] Reached target NFS client services.
[ OK ] Finished Flush Journal to Persistent Storage.
[ OK ] Started NFSv4 ID-name mapping service.
Starting Create Volatile Files and Directories...
[ OK ] Started Rule-based Manager for Device Events and Files.
[ OK ] Finished Create Volatile Files and Directories.
Starting RPC bind portmap service...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started RPC bind portmap service.
[ OK ] Reached target RPC Port Mapper.
[ OK ] Finished Update UTMP about System Boot/Shutdown.
[ OK ] Reached target System Initialization.
[ OK ] Started Daily apt download activities.
[ OK ] Started Daily apt upgrade and clean activities.
[ OK ] Started Periodic ext4 Onliâ¦ata Check for All Filesystems.
[ OK ] Started Daily man-db regeneration.
[ OK ] Started Update the plocate database daily.
[ OK ] Started Daily Cleanup of Temporary Directories.
[ OK ] Reached target Timers.
[ OK ] Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
[ OK ] Listening on D-Bus System Message Bus Socket.
[ OK ] Reached target Sockets.
[ OK ] Reached target Basic System.
Starting Avahi mDNS/DNS-SD Stack...
[ OK ] Started D-Bus System Message Bus.
Starting Remove Stale Onli…t4 Metadata Check Snapshots...
Starting User Login Management...
[ OK ] Started Avahi mDNS/DNS-SD Stack.
[ OK ] Finished Remove Stale Onliâ¦ext4 Metadata Check Snapshots.
[ OK ] Started User Login Management.
[ OK 41.981863][ T241] orion_wdt: Initial timeout 25 sec
0m] Found device /dev/ttyS0.
[ 42.817407][ T245] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 42.868500][ T244] sd 2:0:0:0: Attached scsi generic sg0 type 0
[ OK ] Finished Helper to synchronize boot up for ifupdown.
Starting Raise network interfaces...
[ *** ] A start job is running for Raise network interfaces (14s / 5min 10s)
[ 47.778448][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flod
[ OK ] Finished Raise network interfaces.
[ OK ] Reached target Network.
Starting NFS Mount Daemon...
Starting Network Time Service...
Starting /etc/rc.local Compatibility...
Starting OpenBSD Secure Shell server...
[ OK ] Started NFS Mount Daemon.
Starting NFS server and services...
[ OK ] Started Network Time Service.
[ OK ] Started /etc/rc.local Compatibility.
[ OK ] Started OpenBSD Secure Shell server.
[ 57.275034][ T382] NFSD: Using UMH upcall client tracking operations.
[ 57.281757][ T382] NFSD: starting 90-second grace period (net f000001c)
[ OK ] Finished NFS server and services.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
Starting LSB: Starts syslogd...
Starting Permit User Sessions...
[ OK ] Finished Permit User Sessions.
[ OK ] Started Getty on tty1.
[ OK ] Started Serial Getty on ttyS0.
[ OK ] Reached target Login Prompts.
[ OK ] Started LSB: Starts syslogd.
Starting LSB: Starts klogd...
[ OK ] Started LSB: Starts klogd.
[ OK ] Reached target Multi-User System.
[ OK ] Reached target Graphical Interface.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Finished Update UTMP about System Runlevel Changes.
Debian GNU/Linux 11 deb03 ttyS0
deb03 login:
