I see, boot_debian_usb=usb start; sleep 5; fatload usb 0:1 0x00800000 /boot/uImage; fatload usb 0:1 0x02100000 /boot/uRamdisk; bootm 0x00800000 0x02100000 bootcmd=run set_bootargs_debian; run boot_debian_usb; reset So you are still booting with the FAT USB drive using fatload. See this Step 4 in this thread. https://forum.doozan.com/read.php?2,133718,133722#msg-133722 The new u-by bodhi - Debian
Chris, > But I am booting the uImage and uInitrd from the > stick. > Can I boot somehow direct from HDD? Yes you can. I forgot that's where you are. > It didn't work because uInitrd is too big, no? Not that reason. You have updated u-boot so the initrd size is irrelevant. We need to changes some envs to make it boot HDD rootfs. Also make it boot USB if the HDDby bodhi - Debian
Chris, > do I need to copy now the uImage and uInitrd to > the stick? If you intend to use the stick as a rescue system then you should install the new kernel on the USB rootfs. Remove the HDD, and boot back to USB, and then do the kernel installation. If you don't think you would use the USB rootfs at all, then copying the kernel files only would be OK. As I mentionedby bodhi - Debian
Looks like sending PM is broken. Thanks bluzfanmr1 for pointing out the typos in the release threads! bluzfanmr1 or Chris, please try sending PM to me (test if it's really broken).by bodhi - Off-Topic
Chris, > now I've deledet mdo and changed only to /dev/sda1 > to rootfs and it's booting That's what I would do. > another question the update to newr kernel doesn't > work > > 2023-06-02 22:48:46 (15.4 MB/s) - > 'linux-6.2.8-mvebu-tld-1-bodhi.tar.bz2' saved > [37044194/37044194] > > root@debian:/boot# tar -xjf >by bodhi - Debian
Mischif, > Still no luck with emmc, same pattern every time - > when I boot the device after a long while the > kernel sees the mmc, but I get an error every time > I try to interact with it; when I reboot either > with the same kernel or an updated one I get the > "Card stuck being busy" error. I think a capacitor > or something is blown out on my board.by bodhi - Debian
Usually, the rootfs is on md0.by bodhi - Debian
Chris, [ 8.244490][ T1817] md/raid1:md0: active with 2 out of 2 mirrors [ 8.251369][ T1817] md0: detected capacity change from 0 to 2240512 [ 8.257932][ T1822] md/raid1:md2: not clean -- starting background reconstrun [ 8.267977][ T1832] md/raid1:md1: active with 2 out of 2 mirrors [ 8.268578][ T1822] md/raid1:md2: active with 2 out of 2 mirrors [ 8.274362][ T1832] md1by bodhi - Debian
Hi Mischif , I've released kernel 6.3.5-mvebu-tld-1. QuoteKernel 6.3.5-mvebu-tld-1 package has been uploaded. New/Updated in this release: - General kernel upgrade. Some code and DTS rebase were needed in the patch. - Add support for Mavell MMP3 SoC (CONFIG_ARCH_MMP and assiocated configs). - Add support for Dell Wyse 3020 (works on eMMC in still in progress). -Add CONFIGby bodhi - Debian
Kernel 6.3.5-mvebu-tld-1 package has been uploaded. See 1st post for download link. Please create a new thread for any installation problem or questions.by bodhi - Debian
Kernel linux-6.3.5-kirkwood-tld-1 package has been uploaded. See 1st post for download link. And please create a new thread for any installation problem or question.by bodhi - Debian
> done that, Can you show the log of the boot with USB rootfs and then how you run "mdadm --assemble --scan", and mount the rootfs partition.by bodhi - Debian
OK Chris. I think since you are booting with a new kernel. You might need to reassamble the RAID array.. See this post: https://forum.doozan.com/read.php?3,130039,130404#msg-130404 And also the link I've mentioned in the post QuoteVery carefully. See posts from Mijzelf and me starting from here: https://forum.doozan.com/read.php?2,129924,129934#msg-129934 If you have valby bodhi - Debian
Ah, Try again. You don't need to do saveenv. Only use saveenv when you're sure that it is working and you want to commit the change. setenv set_bootargs_debian 'setenv bootargs root=/dev/ram console=ttyS0,115200 earlyprintk=serial' and then bootby bodhi - Debian
Chris, Please post the entire boot log (don't post excerpt).by bodhi - Debian
> this is the bootlog with the usb > debian > 192.168.1.210 > WD MyCloud Ex2 Ultra > Linux version 5.13.8-mvebu-tld-1 (root@tldDebian) > (gcc (Debian 8.3.0-6) 8.3.0, G > NU ld (GNU Binutils for Debian) 2.31.1) #1.0 SMP > PREEMPT Sat Aug 7 14:58:41 PDT > 2021 > Debian 11.7 > Thu Jun 1 12:57:16 PDT 2023 up 1 minute > root@debian:~# > Cool!by bodhi - Debian
Chris, Excellent, you're very close, almost there! You are booting with the kernel on USB: USB0: Port (usbActive) : 0 Interface (usbType = 3) : USB XHCI 1.00 scanning bus 0 for devices... 2 USB Device(s) found scanning usb for storage devices... 1 Storage Device(s) found scanning usb for ethernet devices... 0 Ethernet Device(s) found reading /boot/uImage 5236by bodhi - Debian
Some more observation. For low RAM Kirkwood boxes (128MB, 256MB), we actually need to change the initramfs compression back to gzip. Both lzma and zstd are just too slow in these boxes.by bodhi - Debian
Chris, And yes, you can uninstall kernel 6. > Is there a way to uninstall the kernel 6 ? Because > I have problems installing omv, and I think it is > because the kernel 6 is there. Log in and do this to see exactly which kernel you are running. And get the list of kernels that have been installed. uname -a dpkg -l | grep linux-image Once you got the list you can uninstby bodhi - Debian
Chris, > if I manage to boot from USB is it possible to > install the Dbian on the HDD and only let the boot > image on the USB? Yes. You can boot with the kernel files on USB, and the rootfs on HDD. > how? Have you read the first 6 posts in this thread? take your time to read these instruction to see if you inderstand them.by bodhi - Debian
gennnarino, > U-Boot 2013.01-g7c1da33-dirty_v1.04 (Jul 17 2017 - > 18:43:06) Marvell version: 2014_T3.0p6 > DRAM: 512 MiB If U-Boot sees 512MB RAM like this, there is no way to make kernel recognize 1GB. Either this is a bad u-boot, or one of the RAM chip is faulty (but was not reported in the boot log). Did you buy this box used or brand new? you can open the box and see if tby bodhi - Debian
bowent, > > Change the root=Label=rootfs to root=/dev/sda1 and > tftp boot again. > > Note that the root=/dev/sda1 usage is a good solution only if you don't intend to have more than 1 USB drive attached during boot. As soon as you have another USB drive attached in addition to the rootfs, you will have problem booting. The foolproof solution is to use root=LABELby bodhi - Debian
> You can firmly but carefully push each pin into > the solder for each connection until they stick > without falling. I cut off the top of the pins to > get them to fit into the end of the cable > connectors. The middle pin has tape around it to > keep the 3 connections from touching. Just be > careful not to push the pins too hard or you will > end up with oneby bodhi - uBoot
Chris, NAND read: device 0 offset 0x500000, size 0x500000 5242880 bytes read: OK NAND read: device 0 offset 0xa00000, size 0x500000 5242880 bytes read: OK ## Booting image at 00a00000 ... ## Booting kernel from Legacy Image at 00a00000 ... Image Name: Kernel-v5.11.5 Created: 2021-03-09 13:50:46 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Sizeby bodhi - Debian
All, I recall some users reported this issue. It is best to use command line to label the disk. Don't use GUI (i.e. Ubuntu, Mint,...). Assuming the partition in /dev/sdb1. If formatting mkfs.ext3 -L rootfs /dev/sdb1 If already formattted: e2label /dev/sdb1 rootfsby bodhi - Debian
dancyran, > I also followed your instructions and successfully > got the new 2023.04 U-Boot Kirkwood PogoV4 > working without any issue. I upgraded my Pogoplug > V4 A3 from the last 2017.07 U Boot. Cool! > On review of my old fw_printenv with the new one - > I see that 'machid=f78' and 'arcNumber=3860' are > no longer needed That'sby bodhi - uBoot
bluzfanmr1, > I was able to use the shirt pin method to gain > serial access Cool! I thought I was the only one lazy and soldering challenge :) > and then install this latest U-Boot > and Debian. I was a little rusty on the timing > when trying to kwboot but after a few tries got it > down pat! Awesome!by bodhi - uBoot
> As previously stated, it'd be wise to do two > separate rootfs images for both sysvinit and > systemd before bookworm officially releases, but I > understand this isn't really doable from size vs > hosting space. I have to disagree. IMO, Debian is not at the point where systemd is a must-have. When that time comes, I'll switch to systemd for the rootfs. Inby bodhi - Debian
Chris, > So here the serial output of dmesg right? No. The serial boot log starts from the u-boot banner, and ends at the Debian login prompt. It's my shortcut way of asking how do you boot the system. Are the kernel files stored on flash, or are they stored on USB drive? So if you post the entire serial boot log, I don't have to ask, and you answer, .... the quickest and beby bodhi - Debian
dhargens, CPU LED trigger is in the kernel, not in u-boot. I think I will release new Kirkwood kernel version sometime this week.by bodhi - uBoot