I can’t buy any small drives anymore, so I’m loaded with 16G & 32G 2.0 Fits, and 32G Ultras. I have 1 64G Ultra I wasn’t aware I’d set up for rootfs, which was used in my tests.by dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- Quote> It depends if the rootfs is the USB 3.0 drive or > 2.0 drive. I would hope that the rootfs is on the > USB 3.0 drive attched to the rear port. Yes, the 3.0 Ultra rootfs drive is plugged into the top rear port, with another 3.0 Ultra FAT32 in the bottom port and a 2.0 Fit FAT32 in the top port. It never bootby dhargens - uBoot
Because I thought it might have something to do with environment vars, I grabbed this: Pogo_V4> printenv baudrate=115200 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; reset bootcmd_exec=if run load_uimage; then; if run load_initrd; then if run load_dtb; then bootm $load_ui bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi bootby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > It does not matter what file system in on the USB > 2.0 drive. > > The USB drives initiazation failed in your test > with USB 3.0 in the rear port, and USB 2.0 drive > in the top port. But apparently it works in my > test. So that's what it invalidated, i.e we cannot > determine one wayby dhargens - uBoot
Sorry, I should've added this. When it boots with both drives and errors, I stop it, remove a drive and run 'boot' to continue on, which boots properly. Prior to boot (during the stop) I ran your example commands and it came up with the following: Note: power is NOT removed after removing the thumb drive in this test. U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogopby dhargens - uBoot
Just tried it again, and here's the setup: 16G Fit 2.0 in the top port (rootfs label + kernel 5.13.6) 64G Ultra "SanDisk 3.2Gen1" in the rear port (rootfs label + kernel 6.3.8) U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Pogoplug V4 SoC: Kirkwood 88F6192_A1 Model: Cloud Engines PogoPlug Series 4 DRAM: 128 MiB Core: 20 devices, 16 uclasses, devicetree: separateby dhargens - uBoot
- My testing scenarios - uboot ver: U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:24:44 -0700) Note: Power is removed & reapplied at start of each numbered scenario, but not in middle of tests. 1. Booting with a Cruzer Fit 2.0 kernel 5.13.6 in the top, and a massive powered hard drive (Big Damn HD, unknown format, but not rootfs) in a rear port. Constant recycling with "BUG" erroby dhargens - uBoot
Sorry if I was unclear - I only put one drive in at a time. I thought I'd read somewhere here that (as I understand it) you can only have one drive at a time with the 'rootfs' label or it gets confused, so I only ever have one installed at a time. Besides, I don't know which drive loads first, though I'd suspect it's the top port. I meant to say that I made a rootby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- Quote Repeat this test configuration. Interrupt serial console countdown and usb reset usb part usb info Here's the outputs: Pogo_V4> usb reset 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..by dhargens - uBoot
I'm seeing something I'd seen before, but assumed it was related to the issue in mainline kernel. I had used a Cruzer Ultra 3.1 in the back port and it worked well. No errors. Then I couldn't leave things well enough alone, so I created another rootfs on a Cruzer Fit 2.0 and put it in the top port. When it booted, it showed the following: U-Boot 2023.04-tld-1 (Jun 11 2023 - 16:by dhargens - uBoot
Heck yes - I jumped on that immediately! Working as hoped. Now I can quit bugging you for this! ;-)by dhargens - uBoot
Agreed. I updated to 6.3.8 and it's now using the rear port. Thanks again bodhi!by dhargens - uBoot
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, anby dhargens - uBoot
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 toby dhargens - uBoot
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 aby dhargens - uBoot
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 andby dhargens - uBoot
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 faby dhargens - uBoot
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.by dhargens - uBoot
Good to know. I'd hoped I could follow instructions - though I'd skipped some before... Now I've got solid steps to update the couple of boxes I've been messing with. Thanks for the your help. It's appreciated.by dhargens - uBoot
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 theby dhargens - uBoot
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 thby dhargens - uBoot
I installed the latest uboot in the Post 1 instructions, and it displays the following at the beginning of the boot: U-Boot 2023.04-tld-1 (May 10 2023 - 23:00:14 -0700) Pogoplug V4 much 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: -------------------------by dhargens - uBoot
I updated a previously updated 2023.04 with the newest version from Post 1, and it boots fine. I don't have a serial connection for another week, so I can only see dmesg output, and it looks fine. I corrected the 'ethaddr' to what's on the V4's label, but otherwise all vars are from the update. I see there's no 'cpu' in the LED trigger file, though I'mby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > I think we might not be done yet (my mistake in the envs image). So stay tume. I'll be glad to help when I return on the 5th or so.by dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > I migth be able to make them less noisy. But that > will be some day when I can revisit this subject. No worries. As long as it's expected, then I'm good with it. Was trying to point out a difference between boots, which didn't really make sense to me. Seems it's USB hardware, and when I get bacby dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > dhargens, > > I don't see any error in this log. > > 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 **by dhargens - uBoot
bodhi Wrote: ------------------------------------------------------- > That truncated log is not good! > > When you post the good log, please also do this in Debian. > cat /proc/mtd Here's that output on my live system: $ cat /proc/mtd dev: size erasesize name mtd0: 00200000 00020000 "u-boot" mtd1: 00300000 00020000 "uImage" mtd2: 00300000by dhargens - uBoot
One difference between logs 1, 2 and 3 might be that I'm using different USB drives on each boot - some older Sandisk Cruzer Fits (2.0) and a new Sandisk Ultra Fit (3.2). The older Cruzer has an led on it, while the new ones don't - and neither does the Ultra. Didn't think there'd be a difference between them, but maybe they've changed the hardware between 'modelsby dhargens - uBoot
And here's a non-truncated boot from the rear port using a USB 3 drive. It too has errors in the same place as above. 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 NANDby dhargens - uBoot
Here's a non-truncated log of a boot with a USB 2 drive in the top port. I note that there's more error messages ("Bad device specification") when loading envs from usb & sata - but I don't know why. 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 devicesby dhargens - uBoot