1st post updated: Quote8. (Optional) Activate netconsole Please do not activate netconsole! I'm troubleshooting a problem, stay tune... .by bodhi - uBoot
1st post updated: Quote8. (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 toby bodhi - uBoot
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. Quotehttps://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.by bodhi - uBoot
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.by bodhi - uBoot
@Mischif, Could you write an installation instruction for this box (booting from USB) ? Perhaps now is the time to do that. For some idea how to structure the instruction: https://forum.doozan.com/read.php?2,88619 If you don't want to or don't have time, then I'll do when I start the installation.by bodhi - Debian
> I didn't see anything in netconsole but it booted! Cool! netconsole is a bit cumbersome. But it's good if you don't want to connect serial all the time. There are various versions of netconsole. If you run Ubuntu or the like, install netcat.traditional. It's easier to follow existing examples in this forum with the traditional version.by bodhi - uBoot
Cool! you can reboot now.by bodhi - uBoot
Looks good! Now onward to step 8 to 11.by bodhi - uBoot
wsdickerson, It's hard to read the way you post log. Can you just copy/paste what's on your SSH terminal here? Everything seems OK. Please proceed to the next step.by bodhi - uBoot
> ** cd /media/sdb1 > ** tar -xjf > Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 Were you the root user while doing the above? > uboot.2017.07-tld-1.pogo_e02.bodhi.tar. > > What is the next step? (Step 4? or > https://forum.doozan.com/read.php?3,12381 > "Flashing Instructions"?) > > I have not done a cold boot. Do all the steps in tby bodhi - uBoot
> 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. Quotehttps://forum.doozan.com/read.php?2,12096 Updated 26 Sept 2021: Basic Debby bodhi - uBoot
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 Quote9. Reboot Upon rby bodhi - uBoot
bowent, > I've managed to get updated u-boot installed and > am able to boot from USB devices. Part of the > issue i was having before was that cut and paste > of commands from the web site to the putty serial > console was failing (but not in a way that was > visually noticable). Once i started typing all of > the commands, i was able to boot USB ide,USB sataby bodhi - Debian
> 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 expectedby bodhi - uBoot
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 Tonyby bodhi - uBoot
QuoteSo 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 toby bodhi - uBoot
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.by bodhi - uBoot
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. QuoteUpdate 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 sby bodhi - uBoot
Your box is Pogo E02 so make sure you use the Pogo E02 u-boot: uboot.2017.07-tld-1.pogo_e02.bodhi.tarby bodhi - uBoot
I posted above: QuoteSee here for how to install latest Debian kernel and U-Boot. https://forum.doozan.com/read.php?3,135359,135361#msg-135361by bodhi - uBoot
> What filesystem would be supported? Try using Ext3.by bodhi - uBoot
wsdickerson, > mount /dev/sdb1 /tmp/usb_stick: mounting > /dev/sdb1 on /tmp/usb_stick failed: Invalid > argument Sounds like you are still running stock OS. See here for how to install latest Debian kernel and U-Boot. Stock OS is quite old and limited, so it is quite possible that it does not support FAT32 Quote/dev/sdb1 1 584 3926016 c Win95 FAT32 (LBA) While in stockby bodhi - uBoot
> I'm back with good news, over 5 years running and > the duel sd card system is still running. Nice!by bodhi - uBoot
Chris, > SWAP is there and functioning automatically . > md0 not anymore. Don’t really know why he is > still looking for it I guess this will be your own research about RAID (Perhaps you need to reassemble the RAID array?).by bodhi - Debian
BTW, the /boot folder should be listed with reversed chronological order. It helps to see if they need some attention. 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-kby bodhi - uBoot
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.by bodhi - uBoot
Your boot log showed some failures. Dependency failed for /dev/md0. Dependency failed for Swap. So where is md0? and where is swap? lsblk swaponby bodhi - Debian
> But I'm still using RAID, but not booting from > raid. > Should I still set that? In that case don't set raid=noautodetect > I mean the complete bootargs. When you want to add a kernel boot option, you need to change the env where the bootargs is set. Similar to your addition of systemd.unified_cgroup_hierarchy=0. Quotesetenv set_bootargs_debian "setenvby bodhi - Debian
> You can boot to debian, you have root, just > installed new u-boot and u-boot env, then all > problems will be solved. > > > ...will be happy ever after... > > Don't play with old U-boot. Good advice David!by bodhi - Debian
Chris, > please consider using UBI > block devices instead. > [42644.933011] mtdblock: MTD device > 'reserve2' is NAND, please consider using UBI > block devices instead. > very often. > where or what is here the problem? There is no problem. It is just an info message that suggest using UBI for NAND partition. Usually you should see it only once. Butby bodhi - Debian