2023.04 U-Boot Kirkwood - Pogo V4
Posted by bodhi
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 06, 2023 02:52PM |
Admin Registered: 13 years ago Posts: 18,900 |
bluzfanmr1,
> @bodhi one last quick question. I noticed a file
> named uInitr in the boot folder that
> I've never noticed before. Should that file be
> there or can it be deleted? I thought I may have
> left the d off the end when copying
> and pasting earlier in the upgrade process. Thank
> you.
It was your copy/paste typo, delete that file uInitr.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> @bodhi one last quick question. I noticed a file
> named uInitr in the boot folder that
> I've never noticed before. Should that file be
> there or can it be deleted? I thought I may have
> left the d off the end when copying
> and pasting earlier in the upgrade process. Thank
> you.
It was your copy/paste typo, delete that file uInitr.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 06, 2023 02:56PM |
Admin Registered: 13 years ago Posts: 18,900 |
BTW, the /boot folder should be listed with reversed chronological order. It helps to see if they need some attention.
For example, you can tell if initramfs had been regenerated by a Debian upgrade, but the uInitrd was not recreated.
I also have a habit of copying uImage and uInitrd as followed:
This will come handy in the future. If after upgrading kernel and you have a problem. You can then boot with serial/net console, adjust the envs and boot back to previous version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 06/06/2023 08:51PM by bodhi.
ls -larth /boot/
For example, you can tell if initramfs had been regenerated by a Debian upgrade, but the uInitrd was not recreated.
I also have a habit of copying uImage and uInitrd as followed:
cp -a uImage uImage.6.3.5-kirkwood-tld-1 cp -a uInitrd uInitrd.6.3.5-kirkwood-tld-1
This will come handy in the future. If after upgrading kernel and you have a problem. You can then boot with serial/net console, adjust the envs and boot back to previous version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 06/06/2023 08:51PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 06, 2023 03:05PM |
Registered: 4 years ago Posts: 60 |
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 07, 2023 10:13PM |
Registered: 1 year ago Posts: 96 |
I installed the latest uboot in the Post 1 instructions, and it displays the following at the beginning of the boot:
Also, bodhi Wrote:
-------------------------------------------------------
> CPU LED trigger is in the kernel, not in u-boot. I
> think I will release new Kirkwood kernel version
> sometime this week.
So if I'm on initramfs-5.13.6-kirkwood-tld-1, I need to upgrade to 6.x to get that, correct? Can I do that by upgrading the system to 6 (bookworm), or do I need to completely reinstall the rootfs and start over from scratch? Does updating uInitrd with mkimage after the upgrade take care of this?
I'm missing how I get your kernel updates into the system without starting all over again.
U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700) Pogoplug V4much as I would expect it to do. However, I don't know if it's really the latest version or not. How can I tell if I'm up to date on uboot versioning?
Also, bodhi Wrote:
-------------------------------------------------------
> CPU LED trigger is in the kernel, not in u-boot. I
> think I will release new Kirkwood kernel version
> sometime this week.
So if I'm on initramfs-5.13.6-kirkwood-tld-1, I need to upgrade to 6.x to get that, correct? Can I do that by upgrading the system to 6 (bookworm), or do I need to completely reinstall the rootfs and start over from scratch? Does updating uInitrd with mkimage after the upgrade take care of this?
I'm missing how I get your kernel updates into the system without starting all over again.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 07, 2023 11:04PM |
Admin Registered: 13 years ago Posts: 18,900 |
dhargens,
> How can I tell if I'm up to date on uboot versioning?
The Installation post last Update is 25 May. That 's the hint. However, I've updated the Installation Step 9 to make that clear.
> I'm missing how I get your kernel updates into the
> system without starting all over again.
Go to the rootfs/kernel installation thread and use the latest kernel (it is released and announced on top).
https://forum.doozan.com/read.php?2,12096
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> How can I tell if I'm up to date on uboot versioning?
The Installation post last Update is 25 May. That 's the hint. However, I've updated the Installation Step 9 to make that clear.
Quote
Update 25 May 2023
Update 20 May 2023
Update 17 May 2023
<snip>
9. Reboot
Upon reboot, in either serial console or netconsole, U-Boot banner should show:
U-Boot 2023.04-tld-1 (May 25 ....)
Pogo V4
DONE installation.
> I'm missing how I get your kernel updates into the
> system without starting all over again.
Go to the rootfs/kernel installation thread and use the latest kernel (it is released and announced on top).
https://forum.doozan.com/read.php?2,12096
Quote
<snip>
Latest released kernel: linux-6.3.5-kirkwood-tld-1-bodhi.tar.bz2 (02 Jun 2023)
<snip>
=======================================================================
Updated 02 Jun 2023:
Kernel linux-6.3.5-kirkwood-tld-1 package has been uploaded. The following features were added/updated:
- General kernel upgrade. Some code rebase were needed in the patch.
- Add support for Check Point L-50 (Kirkwood 88F6821).
- Add CONFIG_LEDS_TRIGGER_CPU. This new trigger cpu can be used to blink the Status LED when there are system activities, and turn it off by default.
- See Important Note in Step 5 about uInitrd size.
Credits:
- Thanks Gravelrash for doing all the works to add support for the Check Point L-50.
Latest Linux kernel 6.x general release information can be found at:
LinuxChanges log
Download at Dropbox:
linux-6.3.5-kirkwood-tld-1-bodhi.tar.bz2
md5:
978fe815306d448a5e5e4e8b2356fba0
sha256:
d48f19bf1064c24ef383d38134d2caa9e53c00c134f5484a26033b6fb24aea0c
And as always, please verify the hash of what you've downloaded!
This tarball contains 6 files:
linux-image-6.3.5-kirkwood-tld-1_1_armel.deb
linux-headers-6.3.5-kirkwood-tld-1_1_armel.deb
config-6.3.5-kirkwood-tld-1
zImage-6.3.5-kirkwood-tld-1
linux-dtb-6.3.5-kirkwood-tld-1.tar
linux-6.3.5-kirkwood-tld-1.patch
Installation:
1. Backup your current uImage and uInitrd. In the /boot directory, these are files for your current kernel (xx.xx.xx is the version number):
Quote
uInitrd
uImage
initrd.img-xx.xx.xx-kirkwood-xxx
System.map-xx.xx.xx-kirkwood-xxx
vmlinuz-xx.xx.xx-kirkwood-xxx
config-xx.xx.xx-kirkwood-xxx
dts/
2. Extract the kernel and the DTB files in the archive:
cd /boot
tar -xjf linux-6.3.5-kirkwood-tld-1-bodhi.tar.bz2
tar -xf linux-dtb-6.3.5-kirkwood-tld-1.tar
3. And install it with dpkg. Remove flash-kernel first to avoid potential problem (if flash-kernel was not installed then you'll see some error output):
cd /boot
apt-get remove flash-kernel
dpkg -i linux-image-6.3.5-kirkwood-tld-1_1_armel.deb
4. Create uImage and uInitrd and setup for booting.
I'm using the GoFlex Net booting with USB drive as an example here. Please replace its name (kirkwood-goflexnet.dtb) with the box you are installing on (for example, kirkwood-pogo_e02.dtb). Please look inside the rootfs /boot/dts/ for the correct DTB file name for your box.
Below are the 2 different alternatives in booting (method 4b is required for booting with older U-Boot that does not support FDT, but should not be used if running latest u-boot).
- Choose option 4a if you are going to use the current rootfs for many different Kirkwood boxes, as is. It should boot most of the Kirkwood boxes. And with the latest U-Boot for Kirkwood that suports FDT (if you are installing both the new u-boot and rootfs for the first time, too). This is the preferred method.
- Choose option 4b (This method is required for booting with older U-Boot that does not support FDT) if you only use the current rootfs for the box you're installing on, and don't want to modify u-boot envs. Note that if you are installing from stock OS, u-boot envs must be modified to boot with USB or HDD (please see Boot Kirkwood rootfs with stock u-boot for how to set up the envs in serial console).
4a. Boot with DTB file (standard way to boot FDT kernel). Recommended.
Generate the uImage and uInitrd (the kernel files vmlinuz-6.3.5-kirkwood-tld-1 and initrd.img-6.3.5-kirkwood-tld-1 were generated by dpkg in Step 3):
cd /boot
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.3.5-kirkwood-tld-1 -d vmlinuz-6.3.5-kirkwood-tld-1 uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.3.5-kirkwood-tld-1 -d initrd.img-6.3.5-kirkwood-tld-1 uInitrd
4b. Boot with DTB file embedded in the kernel image.Again, this step 4b is for stock U-Boot only.
Please replace kirkwood-goflexnet.dtb below with the correct DTB name for your box.
Generate the uImage and uInitrd (the kernel files vmlinuz-6.2.7-kirkwood-tld-1 and initrd.img-6.2.7-kirkwood-tld-1 were generated by dpkg in Step 3):
cd /boot
mv uImage uImage.orig
mv uInitrd uInitrd.orig
cp -a zImage-6.3.5-kirkwood-tld-1 zImage.fdt
cat dts/kirkwood-goflexnet.dtb >> zImage.fdt
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-6.3.5-kirkwood-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-6.3.5-kirkwood-tld-1 -d initrd.img-6.3.5-kirkwood-tld-1 uInitrd
5. The new uImage and uInitrd files should be created in /boot directory now.
5.a Important Note: Check your uInitrd size to see if it is larger than 11 MB.
ls -lh /boot/uInitrd
If it is, then do one of the 2 following alternatives.
1. (Recommended) Shrink the initramfs to get a smaller size than 11MB. This approach does not require changing u-boot envs. See here for tutorial: How To Shrink initramfs.
2. See Section B in the u-boot installation thread B. Load addresses for large systems for how to adjust u-boot envs before reboot.
5.b You're ready to reboot the system:
sync
sync
sync
shutdown -r now
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 07, 2023 11:14PM |
Admin Registered: 13 years ago Posts: 18,900 |
Furthermore, the version tld-1 is the unique extra version.
U-Boot 2023.04-tld-1 (May 25 ....)
It means my patch version number is tld-1 (tld stands for Tony's Linux Distribution). The timestamp is really redundant. If I release another 2023.04 u-boot for this box then it should be tld-2....and so on.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
U-Boot 2023.04-tld-1 (May 25 ....)
It means my patch version number is tld-1 (tld stands for Tony's Linux Distribution). The timestamp is really redundant. If I release another 2023.04 u-boot for this box then it should be tld-2....and so on.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 07, 2023 11:21PM |
Admin Registered: 13 years ago Posts: 18,900 |
Quote
So if I'm on initramfs-5.13.6-kirkwood-tld-1, I need to upgrade to 6.x to get that, correct? Can I do that by upgrading the system to 6 (bookworm), or do I need to completely reinstall the rootfs and start over from scratch? Does updating uInitrd with mkimage after the upgrade take care of this?
No, you would install the new kernel, following the instruction I quote above. No need to reinstall anything.
Debian version is not the same as kernel version. You can run the latest kernel on bullseye or bookworm. or you can run older kernel with bookworm. Basically, as long as the kernel version is not too old, then it will be OK.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 07, 2023 11:55PM |
Registered: 1 year ago Posts: 96 |
bodhi Wrote:
-------------------------------------------------------
> Furthermore, the version tld-1 is the unique extra
> version.
>
> U-Boot 2023.04-tld-1 (May 25 ....)
>
> It means my patch version number is tld-1 (tld
> stands for Tony's Linux Distribution). The
> timestamp is really redundant. If I release
> another 2023.04 u-boot for this box then it should
> be tld-2....and so on.
Ok, then by that logic I'm up to date since it shows
-------------------------------------------------------
> Furthermore, the version tld-1 is the unique extra
> version.
>
> U-Boot 2023.04-tld-1 (May 25 ....)
>
> It means my patch version number is tld-1 (tld
> stands for Tony's Linux Distribution). The
> timestamp is really redundant. If I release
> another 2023.04 u-boot for this box then it should
> be tld-2....and so on.
Ok, then by that logic I'm up to date since it shows
U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700)because the date's immaterial.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 12:06AM |
Admin Registered: 13 years ago Posts: 18,900 |
dhargens Wrote:
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Furthermore, the version tld-1 is the unique
> extra
> > version.
> >
> > U-Boot 2023.04-tld-1 (May 25 ....)
> >
> > It means my patch version number is tld-1 (tld
> > stands for Tony's Linux Distribution). The
> > timestamp is really redundant. If I release
> > another 2023.04 u-boot for this box then it
> should
> > be tld-2....and so on.
>
> Ok, then by that logic I'm up to date since it
> shows
>
We were testing. The versioning scheme only applies after it was formally release.
So you are running an interim version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bodhi Wrote:
> -------------------------------------------------------
> > Furthermore, the version tld-1 is the unique
> extra
> > version.
> >
> > U-Boot 2023.04-tld-1 (May 25 ....)
> >
> > It means my patch version number is tld-1 (tld
> > stands for Tony's Linux Distribution). The
> > timestamp is really redundant. If I release
> > another 2023.04 u-boot for this box then it
> should
> > be tld-2....and so on.
>
> Ok, then by that logic I'm up to date since it
> shows
>
> U-Boot 2023.04-tld-1 (May 10 2023 - > 23:00:14 -0700) >> because the date's immaterial.
We were testing. The versioning scheme only applies after it was formally release.
So you are running an interim version.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 12:29AM |
Registered: 1 year ago Posts: 96 |
bodhi Wrote:
-------------------------------------------------------
> We were testing. The versioning scheme only
> applies after it was formally release.
>
> So you are running an interim version.
So how do I get to the current version? I downloaded & re-installed (I think) the latest uboot using the instructions, and still ended up with this interim version.
In the mean time, I followed your directives and updated to kernel 6.3.5-kirkwood-tld-1, and it works as expected.
[I may have learned that the kernel doesn't follow the release versioning (bullseye / bookworm), but we'll see if that takes hold or not.]
And what's the difference between 'cpu' and 'cpu0' in the LED trigger file?
-------------------------------------------------------
> We were testing. The versioning scheme only
> applies after it was formally release.
>
> So you are running an interim version.
So how do I get to the current version? I downloaded & re-installed (I think) the latest uboot using the instructions, and still ended up with this interim version.
In the mean time, I followed your directives and updated to kernel 6.3.5-kirkwood-tld-1, and it works as expected.
[I may have learned that the kernel doesn't follow the release versioning (bullseye / bookworm), but we'll see if that takes hold or not.]
And what's the difference between 'cpu' and 'cpu0' in the LED trigger file?
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 12:49AM |
Admin Registered: 13 years ago Posts: 18,900 |
> So how do I get to the current version? I
> downloaded & re-installed (I think) the latest
> uboot using the instructions, and still ended up
> with this interim version.
Now that's interesting. I'll check the tarball and the date.
> In the mean time, I followed your directives and
> updated to kernel 6.3.5-kirkwood-tld-1, and it
> works as expected.
> [I may have learned that the kernel doesn't
> follow the release versioning (bullseye /
> bookworm), but we'll see if that takes hold or
> not.]
That's the differrence between the mainline Debian installation and a Debian derivative distro. Each Debian version, eg. bullseye and bookworm, is pegged to a Linux kernel version. So there is a misconception is that you have to run a Linux kernel that is consistent with Debian version. On the contrary, you're not limited to a kernel provided by Debian mainline.
In our custom distribution, we can pick and chose. So for example, you can chose to stay with kernel 5.15.x and run bookworm. No problem. bookworm is the OS version, which could be running kernel as old as 5.15.x, or 5.4.x,.... As long as you don't run a kernel that's too old, it will run fine. Linux does not break userspace.
> And what's the difference between 'cpu' and 'cpu0'
> in the LED trigger file?
For multi-core CPU boxes, you also see cpu1,...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> downloaded & re-installed (I think) the latest
> uboot using the instructions, and still ended up
> with this interim version.
Now that's interesting. I'll check the tarball and the date.
> In the mean time, I followed your directives and
> updated to kernel 6.3.5-kirkwood-tld-1, and it
> works as expected.
> [I may have learned that the kernel doesn't
> follow the release versioning (bullseye /
> bookworm), but we'll see if that takes hold or
> not.]
That's the differrence between the mainline Debian installation and a Debian derivative distro. Each Debian version, eg. bullseye and bookworm, is pegged to a Linux kernel version. So there is a misconception is that you have to run a Linux kernel that is consistent with Debian version. On the contrary, you're not limited to a kernel provided by Debian mainline.
In our custom distribution, we can pick and chose. So for example, you can chose to stay with kernel 5.15.x and run bookworm. No problem. bookworm is the OS version, which could be running kernel as old as 5.15.x, or 5.4.x,.... As long as you don't run a kernel that's too old, it will run fine. Linux does not break userspace.
> And what's the difference between 'cpu' and 'cpu0'
> in the LED trigger file?
For multi-core CPU boxes, you also see cpu1,...
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 01:12AM |
Admin Registered: 13 years ago Posts: 18,900 |
dhargens,
> So how do I get to the current version? I
> downloaded & re-installed (I think) the latest
> uboot using the instructions, and still ended up
> with this interim version.
My bad. May 10 is the last u-boot image version. Update May 26 only changed the default envs image and the script.
So I've updated the installation Steps
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> So how do I get to the current version? I
> downloaded & re-installed (I think) the latest
> uboot using the instructions, and still ended up
> with this interim version.
My bad. May 10 is the last u-boot image version. Update May 26 only changed the default envs image and the script.
So I've updated the installation Steps
Quote
9. Reboot
Upon reboot, in either serial console or netconsole, U-Boot banner should show:
U-Boot 2023.04-tld-1 (May 10 ....)
Pogo V4
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 01:18AM |
Registered: 1 year ago Posts: 96 |
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 03:44PM |
Registered: 1 year ago Posts: 96 |
bodhi Wrote:
-------------------------------------------------------
> That's the differrence between the mainline Debian
> installation and a Debian derivative distro. Each
> Debian version, eg. bullseye and bookworm, is
> pegged to a Linux kernel version. So there is a
> misconception is that you have to run a Linux
> kernel that is consistent with Debian version. On
> the contrary, you're not limited to a kernel
> provided by Debian mainline.
>
> In our custom distribution, we can pick and chose.
> So for example, you can chose to stay with kernel
> 5.15.x and run bookworm. No problem. bookworm is
> the OS version, which could be running kernel as
> old as 5.15.x, or 5.4.x,.... As long as you don't
> run a kernel that's too old, it will run fine.
> Linux does not break userspace.
That's an excellent explanation, and made sense. Thank you for that!
And I'd forgotten to ask - now that there's the cpu setting in the LED trigger file, how can I set it to a specific setting on boot, short of creating a boot script that runs every time (which seems clumsy). Hopefully there's a setting somewhere, or can I set it in uEnv.txt?
And related - is there a doc somewhere that lists uEnv.txt options, or is it simply an as-needed thing to override settings?
-------------------------------------------------------
> That's the differrence between the mainline Debian
> installation and a Debian derivative distro. Each
> Debian version, eg. bullseye and bookworm, is
> pegged to a Linux kernel version. So there is a
> misconception is that you have to run a Linux
> kernel that is consistent with Debian version. On
> the contrary, you're not limited to a kernel
> provided by Debian mainline.
>
> In our custom distribution, we can pick and chose.
> So for example, you can chose to stay with kernel
> 5.15.x and run bookworm. No problem. bookworm is
> the OS version, which could be running kernel as
> old as 5.15.x, or 5.4.x,.... As long as you don't
> run a kernel that's too old, it will run fine.
> Linux does not break userspace.
That's an excellent explanation, and made sense. Thank you for that!
And I'd forgotten to ask - now that there's the cpu setting in the LED trigger file, how can I set it to a specific setting on boot, short of creating a boot script that runs every time (which seems clumsy). Hopefully there's a setting somewhere, or can I set it in uEnv.txt?
And related - is there a doc somewhere that lists uEnv.txt options, or is it simply an as-needed thing to override settings?
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 04:23PM |
Admin Registered: 13 years ago Posts: 18,900 |
> And I'd forgotten to ask - now that there's the
> cpu setting in the LED trigger file, how can I set
> it to a specific setting on boot, short of
> creating a boot script that runs every time (which
> seems clumsy)
Look at /etc/rc.local. I have some example in this initscript.
This /etc/rc.local is the last script Debian runs during booting. So you can echo value cpu to the trigger for the status LED.
> And related - is there a doc somewhere that lists
> uEnv.txt options, or is it simply an as-needed
> thing to override settings?
uEnv.txt contains whatever u-boot env you want to adjust. It could be some experiment you're doing that you don't want to save to flash. Or it could be something you want to set permanently, but also does not want to save to flash.
For example, to make the box boot faster, if you always boot with USB rootfs (this box has USB, SATA, and MMC).
Put this in you uEnv.txt
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> cpu setting in the LED trigger file, how can I set
> it to a specific setting on boot, short of
> creating a boot script that runs every time (which
> seems clumsy)
Look at /etc/rc.local. I have some example in this initscript.
Quote
https://forum.doozan.com/read.php?2,12096
Updated 26 Sept 2021:
Basic Debian bullseye Kirkwood rootfs for most Kirwood plugs:
- tarball size: 234M
- install size: 668M
- The init system used in this rootfs is sysvinit . To boot with systemd, see Notes below.
- Installed packages: nano, avahi, ntp, busybox-syslogd (log to RAM), htop, isc-dhcp-client, dialog, bzip2, nfs server/client, iperf, ethtool, sysvinit-core, sysvinit, sysvinit-utils, u-boot-tools, and mtd-utils.
- see LED controls examples in /etc/rc.local, and /etc/init.d/halt
- see some useful aliases in /root/.profile
- root password: root
This /etc/rc.local is the last script Debian runs during booting. So you can echo value cpu to the trigger for the status LED.
> And related - is there a doc somewhere that lists
> uEnv.txt options, or is it simply an as-needed
> thing to override settings?
uEnv.txt contains whatever u-boot env you want to adjust. It could be some experiment you're doing that you don't want to save to flash. Or it could be something you want to set permanently, but also does not want to save to flash.
For example, to make the box boot faster, if you always boot with USB rootfs (this box has USB, SATA, and MMC).
Put this in you uEnv.txt
devices=usb
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 08, 2023 10:56PM |
Registered: 1 year ago Posts: 96 |
bodhi Wrote:
-------------------------------------------------------
> Look at /etc/rc.local. I have some example in this initscript.
> This /etc/rc.local is the last script Debian runs
> during booting. So you can echo value cpu
> to the trigger for the status LED.
Ah, yes, I remember seeing that before. Thanks for the reminder.
> For example, to make the box boot faster, if you
> always boot with USB rootfs (this box has USB,
> SATA, and MMC).
>
> Put this in your uEnv.txt
I'll do that soon. It'll also eliminate the 'errors' I thought I was seeing (but you explained why they weren't) in my 3-part post with logs earlier in this topic.
-------------------------------------------------------
> Look at /etc/rc.local. I have some example in this initscript.
> This /etc/rc.local is the last script Debian runs
> during booting. So you can echo value cpu
> to the trigger for the status LED.
Ah, yes, I remember seeing that before. Thanks for the reminder.
> For example, to make the box boot faster, if you
> always boot with USB rootfs (this box has USB,
> SATA, and MMC).
>
> Put this in your uEnv.txt
> devices=usb
I'll do that soon. It'll also eliminate the 'errors' I thought I was seeing (but you explained why they weren't) in my 3-part post with logs earlier in this topic.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 09, 2023 09:52PM |
Registered: 1 year ago Posts: 96 |
I'm having a problem with upgrading the Debian kernel from 5.13 to 6.3.5 and using it in one of the rear USB 3 ports.
I've created a USB 3 drive with rootfs & kernel 5.13, install it on the V4 and then update it to 6.3.5.
U-Boot 2023.04-tld-1 (May 10) is installed on this.
It boots fine from the rear port when booting in 5.13, but when the installation to 6.3.5 completes and it reboots, 6.3.5 errors with:
When moved to the top port 6.3.5 boots to a normal prompt.
I'm including both boot logs here. You'll note that on the top-port logs that at 10.003147 the USB drive is found (bolded below). However, on the rear-port logs that piece is missing completely.
In both cases the next step is to free the unused kernel at 13.296127 (top) and 13.243012 (rear) and continue the steps, but because rear-port doesn't know about the USB drive it can't continue normally.
Ideas?
Top-port logs:
Rear-port logs:
Edited 2 time(s). Last edit at 06/09/2023 10:00PM by dhargens.
I've created a USB 3 drive with rootfs & kernel 5.13, install it on the V4 and then update it to 6.3.5.
U-Boot 2023.04-tld-1 (May 10) is installed on this.
It boots fine from the rear port when booting in 5.13, but when the installation to 6.3.5 completes and it reboots, 6.3.5 errors with:
ALERT! LABEL=rootfs does not exist. Dropping to a shell!with the (initramfs) prompt.
When moved to the top port 6.3.5 boots to a normal prompt.
I'm including both boot logs here. You'll note that on the top-port logs that at 10.003147 the USB drive is found (bolded below). However, on the rear-port logs that piece is missing completely.
In both cases the next step is to free the unused kernel at 13.296127 (top) and 13.243012 (rear) and continue the steps, but because rear-port doesn't know about the USB drive it can't continue normally.
Ideas?
Top-port logs:
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: 10 9 8 7 6 5 4 3 2 1 0
Initializing devices...
resetting 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
resetting 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
Loading envs from usb 0...
Failed to load '/boot/uEnv.txt'
Loading envs from usb 1...
** Bad device specification usb 1 **
Couldn't find partition usb 1:1
Can't set block device
Loading envs from usb 2...
** Bad device specification usb 2 **
Couldn't find partition usb 2:1
Can't set block device
Loading envs from usb 3...
** Bad device specification usb 3 **
Couldn't find partition usb 3:1
Can't set block device
Loading envs from sata 0...
** Bad device specification sata 0 **
Couldn't find partition sata 0:1
Can't set block device
Loading envs from sata 1...
** Bad device specification sata 1 **
Couldn't find partition sata 1:1
Can't set block device
Loading envs from sata 2...
** Bad device specification sata 2 **
Couldn't find partition sata 2:1
Can't set block device
Loading envs from sata 3...
** Bad device specification sata 3 **
Couldn't find partition sata 3:1
Can't set block device
running scan_disk ...
Scan device usb
resetting 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
resetting 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 usb 0:1
1 bytes read in 12 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
6116624 bytes read in 171 ms (34.1 MiB/s)
loading uInitrd ...
10339244 bytes read in 285 ms (34.6 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10178 bytes read in 28 ms (354.5 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-6.3.5-kirkwood-tld-1
Created: 2023-06-10 0:01:51 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6116560 Bytes = 5.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02100000 ...
Image Name: initramfs-6.3.5-kirkwood-tld-1
Created: 2023-06-10 0:02:07 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 10339180 Bytes = 9.9 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 07170000, end 07b4c36c ... OK
Loading Device Tree to 0716a000, end 0716f7c1 ... OK
Working FDT set to 716a000
Starting kernel ...
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 6.3.5-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 PREEMPT Wed May 31 18:12:24 PDT 2023
[ 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: 32480
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
[ 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: 98144K/131072K available (12288K kernel code, 1697K rwdata, 5228K rodata, 1024K init, 302K bss, 32928K reserved, 0K cma-reserved)
[ 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] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[ 0.000003][ T0] sched_clock: 32 bits at 167MHz, resolution 6ns, wraps every 12884901885ns
[ 0.000074][ T0] Switching to timer-based delay loop, resolution 6ns
[ 0.003103][ T0] Console: colour dummy device 80x30
[ 0.003197][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.003242][ T0] pid_max: default: 32768 minimum: 301
[ 0.004448][ T0] LSM: initializing lsm=capability,integrity
[ 0.005129][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.005186][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.009101][ T0] CPU: Testing write buffer coherency: ok
[ 0.014137][ T1] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.014168][ T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[ 0.014752][ T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[ 0.015511][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.016003][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.016650][ T1] rcu: Hierarchical SRCU implementation.
[ 0.016675][ T1] rcu: Max phase no-delay instances is 1000.
[ 0.019631][ T1] devtmpfs: initialized
[ 0.032119][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.032190][ T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.032977][ T1] prandom: seed boundary self test passed
[ 0.039349][ T1] prandom: 100 self tests passed
[ 0.039373][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.044248][ T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.045695][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.048033][ T1] audit: initializing netlink subsys (disabled)
[ 0.051470][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.052112][ T16] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
[ 0.052342][ T1] cpuidle: using governor ladder
[ 0.052472][ T1] cpuidle: using governor menu
[ 0.053362][ T1] Feroceon L2: Enabling L2
[ 0.05[ 9.441103][ T1] rtc-mv f1010300.rtc: internal RTC not ticking
[ 9.447565][ T1] i2c_dev: i2c /dev entries driver
[ 9.453905][ T1] device-mapper: uevent: version 1.0.3
[ 9.459794][ T1] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[ 9.469986][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 9.477314][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 9.484658][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 9.492134][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 9.498912][ T1] device-mapper: raid: Loading target version 1.15.1
[ 9.507840][ T1] ledtrig-cpu: registered to indicate activity on CPUs
[ 9.514749][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 9.521256][ T1] drop_monitor: Initializing network drop monitor service
[ 9.529159][ T1] NET: Registered PF_INET6 protocol family
[ 9.538150][ T1] Segment Routing with IPv6
[ 9.542610][ T1] RPL Segment Routing with IPv6
[ 9.547440][ T1] In-situ OAM (IOAM) with IPv6
[ 9.552317][ T1] NET: Registered PF_PACKET protocol family
[ 9.558652][ T1] Key type dns_resolver registered
[ 9.586932][ T1] registered taskstats version 1
[ 9.592225][ T1] Loading compiled-in X.509 certificates
[ 9.599688][ T1] zswap: loaded using pool lzo/zbud
[ 9.605937][ T1] Key type .fscrypt registered
[ 9.610564][ T1] Key type fscrypt-provisioning registered
[ 9.626519][ T1] Key type big_key registered
[ 9.685521][ T1] Key type encrypted registered
[ 9.832528][ T105] "cryptomgr_test" (105) uses obsolete ecb(arc4) skcipher
[ 10.003147][ T8] scsi 2:0:0:0: Direct-Access USB SanDisk 3.2Gen1 1.00 PQ: 0 ANSI: 6
[ 10.023372][ T19] sd 2:0:0:0: [sda] 120164352 512-byte logical blocks: (61.5 GB/57.3 GiB)
[ 10.042366][ T19] sd 2:0:0:0: [sda] Write Protect is off
[ 10.061158][ T19] sd 2:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 10.090833][ T19] sda: sda1
[ 10.101938][ T19] sd 2:0:0:0: [sda] Attached SCSI removable disk
[ 13.296127][ T1] Freeing unused kernel image (initmem) memory: 1024K
[ 13.312312][ T1] Checked W+X mappings: passed, no W+X pages found
[ 13.318692][ T1] Run /init as init process
Loading, please wait...
Starting version 247.3-7+deb11u2
[ 14.678856][ T140] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[ 15.004195][ T139] usbcore: registered new interface driver uas
[ 15.121258][ T19] 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: recovering journal
rootfs: clean, 21314/3760128 files, 684458/15020288 blocks
done.
[ 26.357145][ T169] EXT4-fs (sda1): mounted filesystem 58dc21e1-dd0e-4deb-8a54-24b4ea056afa with ordered data mode. Quota mode: none.
done.
Begin: Running /scripts/local-bottom ... done.
Begin: Running /scripts/init-bottom ... done.
[ 27.306855][ T1] systemd[1]: System time before build time, advancing clock.
[ 27.386844][ T1] systemd[1]: Inserted module 'autofs4'
[ 27.514508][ 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)
[ 27.539682][ T1] systemd[1]: Detected architecture arm.
Welcome to Debian GNU/Linux 11 (bullseye)!
[ 27.598295][ T1] systemd[1]: Set hostname to <jumper1912>.
[ 30.630240][ T1] systemd[1]: Queued start job for default target Graphical Interface.
[ 31.271110][ C0] random: crng init done
[ 31.275774][ T1] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[ 31.288956][ T1] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[ 31.333173][ T1] systemd[1]: Created slice system-getty.slice.
[ OK ] Created slice system-getty.slice.
[ 31.374945][ T1] systemd[1]: Created slice system-modprobe.slice.
[ OK ] Created slice system-modprobe.slice.
[ 31.414867][ T1] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ OK ] Created slice system-serial\x2dgetty.slice.
[ 31.454318][ T1] systemd[1]: Created slice User and Session Slice.
[ OK ] Created slice User and Session Slice.
[ 31.492292][ T1] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ OK ] Started Dispatch Password ‚ts to Console Directory Watch.
[ 31.532231][ T1] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ OK ] Started Forward Password R‚uests to Wall Directory Watch.
[ 31.573677][ T1] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ OK ] Set up automount Arbitrary‚s File System Automount Point.
[ 31.621941][ T1] systemd[1]: Reached target Local Encrypted Volumes.
[ OK ] Reached target Local Encrypted Volumes.
[ 31.662413][ T1] systemd[1]: Reached target Paths.
[ OK ] Reached target Paths.
[ 31.702031][ T1] systemd[1]: Reached target Slices.
[ OK ] Reached target Slices.
[ 31.744344][ T1] systemd[1]: Listening on RPCbind Server Activation Socket.
[ OK ] Listening on RPCbind Server Activation Socket.
[ 31.782828][ T1] systemd[1]: Listening on fsck to fsckd communication Socket.
[ OK ] Listening on fsck to fsckd communication Socket.
[ 31.822281][ T1] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ OK ] Listening on initctl Compatibility Named Pipe.
[ 31.863667][ T1] systemd[1]: Listening on Journal Audit Socket.
[ OK ] Listening on Journal Audit Socket.
[ 31.902991][ T1] systemd[1]: Listening on Journal Socket (/dev/log).
[ OK ] Listening on Journal Socket (/dev/log).
[ 31.943279][ T1] systemd[1]: Listening on Journal Socket.
[ OK ] Listening on Journal Socket.
[ 31.983360][ T1] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
[ 32.022702][ T1] systemd[1]: Listening on udev Kernel Socket.
[ OK ] Listening on udev Kernel Socket.
[ 32.063393][ T1] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[ 32.112055][ T1] systemd[1]: Mounting POSIX Message Queue File System...
Mounting POSIX Message Queue File System...
[ 32.160812][ T1] systemd[1]: Mounting NFSD configuration filesystem...
Mounting NFSD configuration filesystem...
[ 32.230633][ T1] systemd[1]: Mounting RPC Pipe File System...
Mounting RPC Pipe File System...
[ 32.292095][ T1] systemd[1]: Mounting Kernel Debug File System...
Mounting Kernel Debug File System...
[ 32.332320][ T1] systemd[1]: Mounting Kernel Trace File System...
Mounting Kernel Trace File System...
[ 32.352271][ T1] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[ 32.406492][ T1] systemd[1]: Starting Restore / save the current clock...
Starting Restore / save the current clock...
[ 32.471583][ T1] systemd[1]: Starting Create list of static device nodes for the current kernel...
Starting Create list of st‚odes for the current kernel...
[ 32.553571][ T1] systemd[1]: Starting Load Kernel Module configfs...
Starting Load Kernel Module configfs...
[ 32.593576][ T1] systemd[1]: Starting Load Kernel Module drm...
Starting Load Kernel Module drm...
[ 32.650371][ T1] systemd[1]: Starting Load Kernel Module fuse...
Starting Load Kernel Module fuse...
[ 32.727157][ T1] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 32.739039][ T1] systemd[1]: Condition check resulted in File System Check on Root Device being skipped.
[ 32.787593][ T1] systemd[1]: Starting Journal Service...
Starting Journal Service...
[ 32.873241][ T1] systemd[1]: Starting Load Kernel Modules...
Starting Load Kernel Modules...
[ 32.945689][ T1] systemd[1]: Starting Remount Root and Kernel File Systems...
Starting Remount Root and Kernel File Systems...
[ 33.047746][ T1] systemd[1]: Starting Coldplug All udev Devices...
Starting Coldplug All udev Devices...
[ 33.256776][ T1] systemd[1]: Mounted POSIX Message Queue File System.
[ OK ] Mounted POSIX Message Queue File System.
[ 33.303250][ T1] systemd[1]: Mounted NFSD configuration filesystem.
[ OK ] Mounted NFSD configuration filesystem.
[ 33.351938][ T1] systemd[1]: Mounted RPC Pipe File System.
[ OK ] Mounted RPC Pipe File System.
[ 33.393913][ T1] systemd[1]: Mounted Kernel Debug File System.
[ OK ] Mounted Kernel Debug File System.
[ 33.433419][ T1] systemd[1]: Mounted Kernel Trace File System.
[ OK ] Mounted Kernel Trace File System.
[ 33.476341][ T1] systemd[1]: Finished Restore / save the current clock.
[ OK ] Finished Restore / save the current clock.
[ 33.552443][ 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.
[ 33.608951][ T214] EXT4-fs (sda1): re-mounted 58dc21e1-dd0e-4deb-8a54-24b4ea056afa. Quota mode: none.
[ 33.699712][ T1] systemd[1]: modprobe@configfs.service: Succeeded.
[ 33.734990][ T1] systemd[1]: Finished Load Kernel Module configfs.
[ OK ] Finished Load Kernel Module configfs.
[ 33.795663][ T1] systemd[1]: modprobe@drm.service: Succeeded.
[ 33.831751][ T1] systemd[1]: Finished Load Kernel Module drm.
[ OK ] Finished Load Kernel Module drm.
[ 33.863125][ T1] systemd[1]: Started Journal Service.
[ OK ] Started Journal Service.
[ OK ] Finished Load Kernel Module fuse.
[ OK ] Finished Load Kernel Modules.
[ OK ] Finished Remount Root and Kernel File Systems.
Activating swap /swapfile1...
Mounting FUSE Control File System...
[ 34.201943][ T217] Adding 524284k swap on /swapfile1. Priority:-2 extents:3 across:540668k FS
Mounting Kernel Configuration File System...
Starting pNFS block layout mapping daemon...
Starting Flush Journal to Persistent Storage...
Starting Load/Save Random Seed...
Starting Apply Kernel Variables...
Starting Create System Users...
[ OK ] Activated swap /swapfile1.
[ OK ] Mounted FUSE Control File System.
[ OK ] Mounted Kernel Configuration File System.
[ 34.938380][ T210] systemd-journald[210]: Received client request to flush runtime journal.
[ OK ] Started pNFS block layout mapping daemon.
[ OK ] Reached target Swap.
[ 35.034583][ T210] systemd-journald[210]: File /var/log/journal/c4334d5b2fba8bce5294b56551baee86/system.journal corrupted or uncleanly shut down, renaming and replacing.
[ OK ] Finished Load/Save Random Seed.
[ OK ] Finished Apply Kernel Variables.
[ OK ] Finished Create System Users.
Starting Create Static Device Nodes in /dev...
[ OK ] Finished Coldplug All udev Devices.
Starting Helper to synchronize boot up for ifupdown...
[ OK ] Finished Create Static Device Nodes in /dev.
[ OK ] Finished Flush Journal to Persistent Storage.
[ OK ] Reached target Local File Systems (Pre).
[ OK ] Reached target Local File Systems.
Starting Preprocess NFS configuration...
Starting Create Volatile Files and Directories...
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 ] Started NFSv4 ID-name mapping service.
[ OK ] Finished Create Volatile Files and Directories.
Starting RPC bind portmap service...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Rule-based Manager for Device Events and Files.
[ 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.
[ 39.971266][ T247] orion_wdt: Initial timeout 25 sec
[ 40.845254][ T245] marvell-cesa f1030000.crypto: CESA device successfully registered
[ 40.945325][ T248] sd 2:0:0:0: Attached scsi generic sg0 type 0
[* ] A start job is running for Helper t‚ot up for ifupdown (11s / 3min 4s)
[ OK ] Finished Helper to synchronize boot up for ifupdown.
Starting Raise network interfaces...
[** ] A start job is running for Raise network interfaces (13s / 5min 11s)
[*** ] A start job is running for Raise network interfaces (14s / 5min 11s)
[ *** ] A start job is running for Raise network interfaces (14s / 5min 11s)
[ *** ] A start job is running for Raise network interfaces (15s / 5min 11s)
[ 45.980903][ C0] mv643xx_eth_port mv643xx_eth_port.0 eth0: link up, 1000 Mb/s, full duplex, flow control disabled
[ 45.991515][ T17] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ ***] A start job is running for Raise network interfaces (15s / 5min 11s)
[ **] A start job is running for Raise network interfaces (16s / 5min 11s)
[ *] A start job is running for Raise network interfaces (16s / 5min 11s)
[ **] A start job is running for Raise network interfaces (17s / 5min 11s)
[ ***] A start job is running for Raise network interfaces (17s / 5min 11s)
[ *** ] A start job is running for Raise network interfaces (18s / 5min 11s)
[ *** ] A start job is running for Raise network interfaces (18s / 5min 11s)
[*** ] A start job is running for Raise network interfaces (19s / 5min 11s)
[** ] A start job is running for Raise network interfaces (19s / 5min 11s)
[* ] A start job is running for Raise network interfaces (20s / 5min 11s)
[ 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.
[ 53.525896][ T385] NFSD: Using UMH upcall client tracking operations.
[ 53.532629][ T385] NFSD: starting 90-second grace period (net f0000000)
[ 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 jumper1912 ttyS0
jumper1912 login:
Rear-port logs:
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: 10 9 8 7 6 5 4 3 2 1 0
Initializing devices...
resetting 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... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
resetting 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... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
Loading envs from usb 0...
Failed to load '/boot/uEnv.txt'
Loading envs from usb 1...
** Bad device specification usb 1 **
Couldn't find partition usb 1:1
Can't set block device
Loading envs from usb 2...
** Bad device specification usb 2 **
Couldn't find partition usb 2:1
Can't set block device
Loading envs from usb 3...
** Bad device specification usb 3 **
Couldn't find partition usb 3:1
Can't set block device
Loading envs from sata 0...
** Bad device specification sata 0 **
Couldn't find partition sata 0:1
Can't set block device
Loading envs from sata 1...
** Bad device specification sata 1 **
Couldn't find partition sata 1:1
Can't set block device
Loading envs from sata 2...
** Bad device specification sata 2 **
Couldn't find partition sata 2:1
Can't set block device
Loading envs from sata 3...
** Bad device specification sata 3 **
Couldn't find partition sata 3:1
Can't set block device
running scan_disk ...
Scan device usb
resetting 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... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
resetting 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... 1 USB Device(s) found
scanning bus xhci_pci for devices... 2 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
device usb 0:1
1 bytes read in 20 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
6116624 bytes read in 67 ms (87.1 MiB/s)
loading uInitrd ...
10339244 bytes read in 112 ms (88 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10178 bytes read in 28 ms (354.5 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-6.3.5-kirkwood-tld-1
Created: 2023-06-10 0:01:51 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 6116560 Bytes = 5.8 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 02100000 ...
Image Name: initramfs-6.3.5-kirkwood-tld-1
Created: 2023-06-10 0:02:07 UTC
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 10339180 Bytes = 9.9 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 07170000, end 07b4c36c ... OK
Loading Device Tree to 0716a000, end 0716f7c1 ... OK
Working FDT set to 716a000
Starting kernel ...
[ 0.000000][ T0] Booting Linux on physical CPU 0x0
[ 0.000000][ T0] Linux version 6.3.5-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 PREEMPT Wed May 31 18:12:24 PDT 2023
[ 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: 32480
[ 0.000000][ T0] Kernel command line: console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
[ 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: 98144K/131072K available (12288K kernel code, 1697K rwdata, 5228K rodata, 1024K init, 302K bss, 32928K reserved, 0K cma-reserved)
[ 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] rcu: srcu_init: Setting srcu_struct sizes based on contention.
[ 0.000000][ T0] clocksource: orion_clocksource: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 11467562657 ns
[ 0.000003][ T0] sched_clock: 32 bits at 167MHz, resolution 6ns, wraps every 12884901885ns
[ 0.000074][ T0] Switching to timer-based delay loop, resolution 6ns
[ 0.003106][ T0] Console: colour dummy device 80x30
[ 0.003201][ T0] Calibrating delay loop (skipped), value calculated using timer frequency.. 333.33 BogoMIPS (lpj=1666666)
[ 0.003244][ T0] pid_max: default: 32768 minimum: 301
[ 0.004456][ T0] LSM: initializing lsm=capability,integrity
[ 0.005130][ T0] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.005185][ T0] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes, linear)
[ 0.009103][ T0] CPU: Testing write buffer coherency: ok
[ 0.014158][ T1] cblist_init_generic: Setting adjustable number of callback queues.
[ 0.014189][ T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[ 0.014774][ T1] cblist_init_generic: Setting shift to 0 and lim to 1.
[ 0.015527][ T1] Setting up static identity map for 0x100000 - 0x100058
[ 0.016019][ T1] mvebu-soc-id: MVEBU SoC ID=0x6281, Rev=0x3
[ 0.016668][ T1] rcu: Hierarchical SRCU implementation.
[ 0.016694][ T1] rcu: Max phase no-delay instances is 1000.
[ 0.019652][ T1] devtmpfs: initialized
[ 0.032131][ T1] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.032200][ T1] futex hash table entries: 256 (order: -1, 3072 bytes, linear)
[ 0.032986][ T1] prandom: seed boundary self test passed
[ 0.039357][ T1] prandom: 100 self tests passed
[ 0.039380][ T1] pinctrl core: initialized pinctrl subsystem
[ 0.044267][ T1] NET: Registered PF_NETLINK/PF_ROUTE protocol family
[ 0.045714][ T1] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.048037][ T1] audit: initializing netlink subsys (disabled)
[ 0.051471][ T1] thermal_sys: Registered thermal governor 'step_wise'
[ 0.052114][ T16] audit: type=2000 audit(0.040:1): state=initialized audit_enabled=0 res=1
[ 0.052347][ T1] cpuidle: using governor ladder
[ 0.052477][ T1] cpuidle: using governor menu
[ 0.053369][ T1] Feroceon L2: Enabling L2
[ 0.053423][ T1] Fe[ 9.441436][ T1] rtc-mv f1010300.rtc: internal RTC not ticking
[ 9.447881][ T1] i2c_dev: i2c /dev entries driver
[ 9.454126][ T1] device-mapper: uevent: version 1.0.3
[ 9.460003][ T1] device-mapper: ioctl: 4.47.0-ioctl (2022-07-28) initialised: dm-devel@redhat.com
[ 9.470249][ T1] device-mapper: multipath round-robin: version 1.2.0 loaded
[ 9.477582][ T1] device-mapper: multipath queue-length: version 0.2.0 loaded
[ 9.484928][ T1] device-mapper: multipath service-time: version 0.3.0 loaded
[ 9.492399][ T1] device-mapper: dm-log-userspace: version 1.3.0 loaded
[ 9.499174][ T1] device-mapper: raid: Loading target version 1.15.1
[ 9.508146][ T1] ledtrig-cpu: registered to indicate activity on CPUs
[ 9.515051][ T1] hid: raw HID events driver (C) Jiri Kosina
[ 9.521622][ T1] drop_monitor: Initializing network drop monitor service
[ 9.529515][ T1] NET: Registered PF_INET6 protocol family
[ 9.538295][ T1] Segment Routing with IPv6
[ 9.542801][ T1] RPL Segment Routing with IPv6
[ 9.547631][ T1] In-situ OAM (IOAM) with IPv6
[ 9.552466][ T1] NET: Registered PF_PACKET protocol family
[ 9.558808][ T1] Key type dns_resolver registered
[ 9.587222][ T1] registered taskstats version 1
[ 9.592523][ T1] Loading compiled-in X.509 certificates
[ 9.599994][ T1] zswap: loaded using pool lzo/zbud
[ 9.606255][ T1] Key type .fscrypt registered
[ 9.610879][ T1] Key type fscrypt-provisioning registered
[ 9.626932][ T1] Key type big_key registered
[ 9.685917][ T1] Key type encrypted registered
[ 9.833136][ T102] "cryptomgr_test" (102) uses obsolete ecb(arc4) skcipher
[ 13.243012][ T1] Freeing unused kernel image (initmem) memory: 1024K
[ 13.262640][ T1] Checked W+X mappings: passed, no W+X pages found
[ 13.269014][ T1] Run /init as init process
Loading, please wait...
Starting version 247.3-7+deb11u2
[ 14.589161][ T137] input: gpio_keys as /devices/platform/gpio_keys/input/input0
[ 14.980701][ T8] 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: Waiting for root file system ... Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelay= (did the system wait long enough?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! LABEL=rootfs does not exist. Dropping to a shell!
BusyBox v1.30.1 (Debian 1:1.30.1-6+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
Edited 2 time(s). Last edit at 06/09/2023 10:00PM by dhargens.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 09, 2023 10:13PM |
Registered: 4 years ago Posts: 60 |
dhargens Wrote:
-------------------------------------------------------
> I'm having a problem with upgrading the Debian
> kernel from 5.13 to 6.3.5 and using it in one of
> the rear USB 3 ports.
>
I had the same issue and had to go back to the earlier kernel to get the rear ports to work.
Edited 1 time(s). Last edit at 06/09/2023 10:14PM by bluzfanmr1.
-------------------------------------------------------
> I'm having a problem with upgrading the Debian
> kernel from 5.13 to 6.3.5 and using it in one of
> the rear USB 3 ports.
>
I had the same issue and had to go back to the earlier kernel to get the rear ports to work.
Edited 1 time(s). Last edit at 06/09/2023 10:14PM by bluzfanmr1.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 09, 2023 10:36PM |
Admin Registered: 13 years ago Posts: 18,900 |
Thanks bluzfanmr1,
> I had the same issue and had to go back to the
> earlier kernel to get the rear ports to work.
Good to know, another good data point. Let me try my Sandisk Ultra Fit.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I had the same issue and had to go back to the
> earlier kernel to get the rear ports to work.
Good to know, another good data point. Let me try my Sandisk Ultra Fit.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 09, 2023 11:02PM |
Admin Registered: 13 years ago Posts: 18,900 |
OK. Looks like kernel 6.3.5 has this problem with USB 3.0 rootfs in the rear port.
@dhargens,
Try kernel 6.2.7-kirkwood-tld-1. This should work fine.
I'll take a look deeper.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
@dhargens,
Try kernel 6.2.7-kirkwood-tld-1. This should work fine.
Quote
https://forum.doozan.com/read.php?2,12096
Updated 23 Mar 2023:
Kernel linux-6.2.7-kirkwood-tld-1 package has been uploaded. The following features were added/updated:
I'll take a look deeper.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 09, 2023 11:28PM |
Admin Registered: 13 years ago Posts: 18,900 |
1st post updated:
Something is lacking in netconsole implementation. It is not robust enough.
When u-boot crashes and reset (due to wrong envs settings), netconsole artifacts cause a big problem. I think that's what dhargens saw a few posts ago, and had to kwboot the 2017.07 version to recover.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/10/2023 01:01AM by bodhi.
Quote
8. (Optional) Activate netconsole
Please do not activate netconsole! I'm troubleshooting a problem, stay tune... .
Something is lacking in netconsole implementation. It is not robust enough.
When u-boot crashes and reset (due to wrong envs settings), netconsole artifacts cause a big problem. I think that's what dhargens saw a few posts ago, and had to kwboot the 2017.07 version to recover.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/10/2023 01:01AM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 10, 2023 11:56AM |
Registered: 4 years ago Posts: 60 |
bodhi Wrote:
-------------------------------------------------------
> 1st post updated:
>
>
> Something is lacking in netconsole implementation.
> It is not robust enough.
>
> When u-boot crashes and reset (due to wrong envs
> settings), netconsole artifacts cause a big
> problem. I think that's what dhargens saw a few
> posts ago, and had to kwboot the 2017.07 version
> to recover.
I now remember that I believe that's what happened to me as well, noted by this post. The last thing I did was enable netconsole. Not sure if this helps at all but it jarred my memory about the last thing I did before things stopped working.
-------------------------------------------------------
> 1st post updated:
>
>
>Quote
8. (Optional) Activate netconsole
>
> Please do not activate netconsole!
> I'm troubleshooting a problem, stay tune...
> .
> Something is lacking in netconsole implementation.
> It is not robust enough.
>
> When u-boot crashes and reset (due to wrong envs
> settings), netconsole artifacts cause a big
> problem. I think that's what dhargens saw a few
> posts ago, and had to kwboot the 2017.07 version
> to recover.
I now remember that I believe that's what happened to me as well, noted by this post. The last thing I did was enable netconsole. Not sure if this helps at all but it jarred my memory about the last thing I did before things stopped working.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 10, 2023 12:43PM |
Registered: 1 year ago Posts: 96 |
bodhi Wrote:
-------------------------------------------------------
> When u-boot crashes and reset (due to wrong envs
> settings), netconsole artifacts cause a big
> problem. I think that's what dhargens saw a few
> posts ago, and had to kwboot the 2017.07 version
> to recover.
Don’t know if this helps, but I’m not enabling netconsole because I have hardwired a serial connection in my boxes. I skip it completely.
-------------------------------------------------------
> When u-boot crashes and reset (due to wrong envs
> settings), netconsole artifacts cause a big
> problem. I think that's what dhargens saw a few
> posts ago, and had to kwboot the 2017.07 version
> to recover.
Don’t know if this helps, but I’m not enabling netconsole because I have hardwired a serial connection in my boxes. I skip it completely.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 10, 2023 03:00PM |
Admin Registered: 13 years ago Posts: 18,900 |
Thanks bluzfanmr1!
> > When u-boot crashes and reset (due to wrong
> envs
> > settings), netconsole artifacts cause a big
> > problem. I think that's what bluzfanmr1 saw a few
> > posts ago, and had to kwboot the 2017.07
> version
> > to recover.
>
> I now remember that I believe that's what happened
> to me as well, noted by this
> post.
> The last thing I did was enable netconsole. Not
> sure if this helps at all but it jarred my memory
> about the last thing I did before things stopped
> working.
Sorry, I meant bluzfanmr1 above.
As of right now, netconsole works fine if the booting is normal. But if for whatever reason, u-boot failed to complete the boot, and then the envs were left in an inconsistent state. So I need to find a way, i.e. patching this code, to make it more robust.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/10/2023 04:05PM by bodhi.
> > When u-boot crashes and reset (due to wrong
> envs
> > settings), netconsole artifacts cause a big
> > problem. I think that's what bluzfanmr1 saw a few
> > posts ago, and had to kwboot the 2017.07
> version
> > to recover.
>
> I now remember that I believe that's what happened
> to me as well, noted by this
> post.
> The last thing I did was enable netconsole. Not
> sure if this helps at all but it jarred my memory
> about the last thing I did before things stopped
> working.
Sorry, I meant bluzfanmr1 above.
As of right now, netconsole works fine if the booting is normal. But if for whatever reason, u-boot failed to complete the boot, and then the envs were left in an inconsistent state. So I need to find a way, i.e. patching this code, to make it more robust.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/10/2023 04:05PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 12, 2023 12:06AM |
Admin Registered: 13 years ago Posts: 18,900 |
I've uploaded the latest version.
This version has the netconsole problem resolved. Hope it will be the last update for this u-boot! I'm happy with this implementation, in that it will make netconsole a lot more robust the way it should be.
There is no change in other parts. So just reflash it using Step 5. And reboot.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
Update 11 Jun 2023
......
Upon reboot, in either serial console or netconsole, U-Boot banner should show:
U-Boot 2023.04-tld-1 (Jun 11 2023....)
Pogo V4
This version has the netconsole problem resolved. Hope it will be the last update for this u-boot! I'm happy with this implementation, in that it will make netconsole a lot more robust the way it should be.
There is no change in other parts. So just reflash it using Step 5. And reboot.
Quote
5. Flash u-boot image to NAND
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 20, 2023 07:31PM |
Registered: 1 year ago Posts: 96 |
bluzfanmr1 Wrote:
-------------------------------------------------------
> dhargens Wrote:
> -------------------------------------------------------
> > I'm having a problem with upgrading the Debian
> > kernel from 5.13 to 6.3.5 and using it in one
> > of the rear USB 3 ports.
>
> I had the same issue and had to go back to the
> earlier kernel to get the rear ports to work.
bodhi Wrote:
-------------------------------------------------------
> OK. Looks like kernel 6.3.5 has this problem with
> USB 3.0 rootfs in the rear port.
>
> @dhargens,
>
> Try kernel 6.2.7-kirkwood-tld-1. This should work fine.
>
> I'll take a look deeper.
Related to USB on the rear ports, I can confirm that in U-Boot 2017.07 the following happens:
This happens with either a USB 2.x or 3.x in the port.
I don't have immediate access to a box with U-Boot 2023.04-tld-1 (May) installed, but I'm pretty sure it did the same thing.
I haven't installed it yet, but does the June revision of U-Boot 2023.04 fix this problem, or only the netconsole issue?
I'd be very happy with a version that uses the hi-speed of USB 3.x, and (as always) giddy if the cpu LED setting were included as well.
-------------------------------------------------------
> dhargens Wrote:
> -------------------------------------------------------
> > I'm having a problem with upgrading the Debian
> > kernel from 5.13 to 6.3.5 and using it in one
> > of the rear USB 3 ports.
>
> I had the same issue and had to go back to the
> earlier kernel to get the rear ports to work.
bodhi Wrote:
-------------------------------------------------------
> OK. Looks like kernel 6.3.5 has this problem with
> USB 3.0 rootfs in the rear port.
>
> @dhargens,
>
> Try kernel 6.2.7-kirkwood-tld-1. This should work fine.
>
> I'll take a look deeper.
Related to USB on the rear ports, I can confirm that in U-Boot 2017.07 the following happens:
5.13.6-kirkwood-tld-1: # lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda `-sda1 ext4 1.0 rootfs a1847d3f-589b-4ff2-8253-0f91de3aad6e 25.9G 4% / sdb `-sdb1 vfat FAT32 7055-C950
6.3.5-kirkwood-tld-1: # lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda `-sda1 ext4 1.0 rootfs a1847d3f-589b-4ff2-8253-0f91de3aad6e 25.7G 5% /
6.2.7-kirkwood-tld-1: # lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINT sda `-sda1 ext4 1.0 rootfs a1847d3f-589b-4ff2-8253-0f91de3aad6e 25.2G 7% / sdb `-sdb1 vfat FAT32 7055-C950
This happens with either a USB 2.x or 3.x in the port.
I don't have immediate access to a box with U-Boot 2023.04-tld-1 (May) installed, but I'm pretty sure it did the same thing.
I haven't installed it yet, but does the June revision of U-Boot 2023.04 fix this problem, or only the netconsole issue?
I'd be very happy with a version that uses the hi-speed of USB 3.x, and (as always) giddy if the cpu LED setting were included as well.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 20, 2023 07:45PM |
Admin Registered: 13 years ago Posts: 18,900 |
dhargens,
> I haven't installed it yet, but does the June
> revision of U-Boot 2023.04 fix this problem, or
> only the netconsole issue?
Only netconsole issue was fixed. It's more critical, since it could hang the box if the envs were set incorrectly (due to a crash and reboot). What I did was forcing the console back to a default state that ignores the wrong settings by netconsole.
>
> I'd be very happy with a version that uses the
> hi-speed of USB 3.x, and (as always) giddy if the
> cpu LED setting were included as well.
I'll revisit this 6.3.5 issue when I have some time. For now, I think using USB 3.0 rootfs is a more important capability, and that you can have with linux-6.2.7-kirkwood-tld-1.
===
edit: Typos
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/20/2023 10:20PM by bodhi.
> I haven't installed it yet, but does the June
> revision of U-Boot 2023.04 fix this problem, or
> only the netconsole issue?
Only netconsole issue was fixed. It's more critical, since it could hang the box if the envs were set incorrectly (due to a crash and reboot). What I did was forcing the console back to a default state that ignores the wrong settings by netconsole.
>
> I'd be very happy with a version that uses the
> hi-speed of USB 3.x, and (as always) giddy if the
> cpu LED setting were included as well.
I'll revisit this 6.3.5 issue when I have some time. For now, I think using USB 3.0 rootfs is a more important capability, and that you can have with linux-6.2.7-kirkwood-tld-1.
===
edit: Typos
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/20/2023 10:20PM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 20, 2023 08:39PM |
Registered: 1 year ago Posts: 96 |
bodhi Wrote:
-------------------------------------------------------
> > I'd be very happy with a version that uses the
> > hi-speed of USB 3.x, and (as always) giddy if
> > the cpu LED setting were included as well.
>
> I'll revisit this 6.3.5 issue when I have some
> time. For now, I think using USB 3.0 rootfs is a
> more important capability, and that you can have
> with linux-6.2.7-kirkwood-tld-1.
I'd agree. Thanks for clarifying what was supplied in 6.2.7.
-------------------------------------------------------
> > I'd be very happy with a version that uses the
> > hi-speed of USB 3.x, and (as always) giddy if
> > the cpu LED setting were included as well.
>
> I'll revisit this 6.3.5 issue when I have some
> time. For now, I think using USB 3.0 rootfs is a
> more important capability, and that you can have
> with linux-6.2.7-kirkwood-tld-1.
I'd agree. Thanks for clarifying what was supplied in 6.2.7.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 20, 2023 10:48PM |
Admin Registered: 13 years ago Posts: 18,900 |
OK. Looks like I might have to release a new kernel 6.3.x to fix this issue. It is broken in mainline kernel.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/21/2023 12:54AM by bodhi.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 06/21/2023 12:54AM by bodhi.
|
Re: 2023.04 U-Boot Kirkwood - Pogo V4 June 21, 2023 09:58PM |
Admin Registered: 13 years ago Posts: 18,900 |
Please see new kernel release:
https://forum.doozan.com/read.php?2,12096,135445#msg-135445
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
https://forum.doozan.com/read.php?2,12096,135445#msg-135445
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
