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
> I don't know what happened to make it stop > booting. I had previously tried moving the usb > around without luck. The only thing I changed > here to get it working again was kwboot with the > 2017 version. I did not make that permanent or > change any other environment variables. That > being said, and according to the log, it's using > the 2023 veby bodhi - uBoot
bluzfanmr1, > I know better, but didn't keep the logs. Lesson > learned. I did not try the previous u-boot (2017) > and installed 2023.04 straight from stock. Yes, I > had set up netconsole, but it wasn't working. I > didn't think of trying to kwboot the older u-boot, > so I tried it and it worked! I now have both > serial and netconsole workingby bodhi - uBoot
Further more, try finding your box in the network, and log in. It might have booted into Debian, but you can not see that in serial console. In this case, fixing the envs is easy.by bodhi - uBoot
bluzfanmr1, > Do I have a > hardware issue with this new box or have I done > something wrong? The appearance does look much like a HW problem, but I'd bet it is not. Just your envs are messed up. > 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 > DRAby bodhi - uBoot
@gennnarino, > bodhi i bought it new, and it has 2 memory > chip... > i used this uboot from : > https://drive.google.com/drive/folders/1wJ9hGKyweA2AlRZaQnZuu3SdrYaCwz77 > > It is for wd my cloud mirror gen 2 That's why you see only 512MB! RAM capacity is always hardcoded in u-boot. > where i can find for ultra version? I don't know where you cby bodhi - Debian
xanatos, I don't reread posts in unless I try to find something. Did not realize there were more info when you updated. > So the stock kernel seems to be much much faster > (at least with btrfs). I did not pay much attention to btrfs. So not sure what can be improved in the kernel or user space. > Made some tests with Ext4. The Ext4 partition is > at the end of thby bodhi - Debian
user45 Wrote: ------------------------------------------------------- > OK have my usb ready to go. Cool! > It doesnt boot to debian because I think I need to > interrupt u-boot count down as per > https://forum.doozan.com/read.php?2,102054,105374#msg-105374 > So I guess that means resolder my serial port > connections? Yes. If you want to boot Debian with stockby bodhi - Off-Topic
user45, That installation method is quite old. See here for installing latest Debian and u-boot: https://forum.doozan.com/read.php?3,134562,134565#msg-134565by bodhi - Off-Topic
Quote> docker: Error response from daemon: failed to > create task for container: failed to create shi m > task: OCI runtime create failed: runc create > failed: unable to start container process: err or > during container init: error setting cgroup config > for procHooks process: bpf_prog_query(B > PF_CGROUP_DEVICE) failed This docker error is not related to bootargsby bodhi - Debian
Quotedid I do something wrong? Yes. The last initramfs is for the older kernel. > ls -lart /boot ...... -rw-r--r-- 1 root root 10065543 Jun 4 08:41 initrd.img-5.13.8-mvebu-tld-1 The docker installation populated this: > ls -lart /lib/modules lrwxrwxrwx 1 root docker 18 Jun 4 22:19 6.3.5-mvebu-tld-1 -> /path/to/module.ko So you need to reinstall kernel 6.3.5-mvebby bodhi - Debian
Chris, Yes. It should be there. depmod: ERROR: could not open directory /lib/modules/6.3.5-mvebu-tld-1: No such file or directory The error above error indicated that you have not installed the kernel 6.3.5-mvebu-tld-1 in the rootfs. Do uname -a ls -lart /lib/modules ls -lart /boot mount lsblk df -hby bodhi - Debian
How To Shrink initramfs The approach described here in this tutorial works perfectly for the kernel and rootfs I releases here: Kirkwood and MVEBU. In general, it should work for any Debian kernel. However, it aso depends on how a particular kernel is configured. IOW, whether the necessary mouldes were already built into the kernel, or some other loadable modules must be loaded early. Pleaby bodhi - Debian
Chris, > So now I have the newest kernel with Debian, > on the stick, only the uImage and uInitrd. > I know this is not a complete Linux and kernel, That's incorrect. 1. The stick has the kernel files only (not a rootfs), and you are running the Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 rootfs on HDD. This rootfs is a complete Debian system, with the kernel runnby bodhi - Debian
Chris Wrote: ------------------------------------------------------- > But I can remain with the uImage and uIntrd on the > stick till then, yes? > > Thank You! For now, boot with both EXT3 USB rootfs and HDD rootfs. The kernel will load the HDD rootfs. And then we'll update a bit more logistics to ensure that will happens everytime.by bodhi - Debian
OK, we'll pick it up tomorrow.by bodhi - Debian
run sata_init sleep 5 Do it a few timesby bodhi - Debian
bodhi Wrote: ------------------------------------------------------- > Ah! I forgot. > > > run sata_init > sleep 5 > ext2ls scsi 0:1 /boot > > If the files are listed correctly then do, > > ext2load scsi 0:1 0x00800000 boot/uImage; ext2load > scsi 0:1 0x02100000 boot/uInitrd; bootm 0x00800000 > 0x02100000' > boot > See above.by bodhi - Debian
Ah! I forgot. run sata_init sleep 5 ext2ls scsi 0:1 /boot If the files are listed correctly then do, ext2load scsi 0:1 0x00800000 boot/uImage; ext2load scsi 0:1 0x02100000 boot/uInitrd; bootm 0x00800000 0x02100000' bootby bodhi - Debian
Try scsi initby bodhi - Debian
How about: scsi reset sleep 5 ext2ls scsi 0:1 /boot or if scsi reset failed: scsi init If the files are listed correctly then do, ext2load scsi 0:1 0x00800000 boot/uImage; ext2load scsi 0:1 0x02100000 boot/uInitrd; bootm 0x00800000 0x02100000' bootby bodhi - Debian
Chris, I've corrected the typos (thanks bluzfanmr1).by bodhi - Debian
> boot successful :) Cool! > Next step? > I'm starting to be sleepy, here is 23 ... Come back tomorrow and try these next steps (before I'll wake up in PST timezone :) Remove the USB roofs, and plug in the HDD rootfs. Power up, interrupt u-boot countdown and, ide reset If the output shows that the HDD is initialized with capacity,... then do, ext2ls ide 0:by bodhi - Debian