Show all posts by user
Bootloader tips and tricks
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
I'm back, and have another problem with a stock uboot on a fresh P4 and trying to boot in any configuration. No matter what I throw at it, it simply will not complete the boot. Since it's a first time installation on a stock P4, I'm using instructions posted in https://forum.doozan.com/read.php?2,12096 from the section "Updated 26 Sept 2021", using Debian-5.13.6 (bulby dhargens - uBoot
Re: Debian on Dell Kace M300 - 1 year ago
It seems to work now and boots as expected. Thanks for the help!by dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
It seems the box is now running the new uboot: U-Boot 2022.04-tld-1 (Mar 20 2022 - 18:15:15 -0700) Dell KACE M300 However, since the thumb I have in it is set up for a Stock uboot on ext3 filesystem, it throws this error: [ 7.840186][ T1] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]--- I'll set up ext4 on another thumb with the normal roby dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
daviddyer Wrote: ------------------------------------------------------- > fw_env.config is wrong... Ok, I corrected it to reflect yours, and now fw_printenv works. I have no idea how it got wrong, since I didn't touch it. Here's the output: root@m300-sid:/boot# fw_printenv baudrate=115200 bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; resetby dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
bodhi Wrote: ------------------------------------------------------- > See if the mtds are defined properly (they should > be already defined when you boot Debian rootfs > with stock u-boot). > cat /proc/mtd > cat /etc/fw_env.config Here's the results: root@m300-sid:/boot# cat /proc/mtd dev: size erasesize name mtd0: 0007f000 00001000 "uboot" mtd1: 00by dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
bodhi Wrote: ------------------------------------------------------- > Ignore this error message. Go ahead and continue > the installation Ok, I did that and things were looking promising. But then there were no envs found. root@m300-sid:~# flash_unlock /dev/mtd0 flash_unlock: error!: could not unlock device: /dev/mtd0 error 95 (Operation not supported) root@m300-sby dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
rayknight Wrote: ------------------------------------------------------- > It appears that you did not follow the > instructions at > Kace > M300 U-Boot post. Quoting from the post: > > 1. Unprotect the SPI flash > Note that this is needed to be done only once from > stock u-boot. > Boot with serial console, interrupt u-boot count > down and unprotecby dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
Now that I have a stable install from 5.13.6 --> 6.3.8, I wanted to update the uboot - but can't get past Step 1 in the update instructions. It says to interrupt and protect off all, then boot, and then in Debian run flash_unlock /dev/mtd0. Well, that fails as shown below. # flash_unlock /dev/mtd0 flash_unlock: error!: could not unlock device: /dev/mtd0 error 95 (Opby dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
rayknight Wrote: ------------------------------------------------------- > It appears that you may not have used the latest > rootfs image > Debian-5.13.6-kirkwood-tld-1-rootfs-bodhi.tar.bz2 > to create your boot disk. Using that would give > you bullseye and you could then use the standard > Debian upgrade process to upgrade to bookworm if > desired. You could alsoby dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
Next question: is it stuck at buster, or can I go to bullseye on this - or did I miss a step yet again? root@debian:~# cat /etc/debian_version 10.13by dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
bodhi Wrote: ------------------------------------------------------- > You are booting with stock u-boot. So you need to > install the new kernel with step 4b. > 4b. Boot with DTB file embedded in the kernel > image.Again, this step 4b is for stock U-Boot > only. Well, of course I missed a step! Sheesh. Follow the instructions correctly and it works!by dhargens - Debian
Re: Debian on Dell Kace M300 - 1 year ago
Hi all! This is my first time working with the Kace product - I usually spend my time in the Pogo V4 chain because I have a few of those. I have a serial connection set up to track my steps. This is a stock uboot at the moment - that update will come after kernel 6.3.8 is completed. Following the instructions, I set up a rootfs for 5.2.9 on a Cruzer Ultra 3.1, moved it to the Kace and complby dhargens - Debian
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
bodhi Wrote: ------------------------------------------------------- > Those were very good tests! I think it's all come > down to the top port (USB 2.0) in this box. Finally I got you something useful!! I don't doubt your reasoning a bit - I think it's the top (EHCI) port screwing up too, because 2 drives in the rear ports seem to work fine. If there's a USBby dhargens - uBoot
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
bodhi Wrote: ------------------------------------------------------- > No, the above test did not work as expected > either. Note that you have only 2 USB storage > drives. Should be 3 drives. > > My test was working fine with 3 drives. So my > conclusion is most probably the Sandisk Ultra 3.0 > drive has some unknown quirks. I could see where I was unclear thereby dhargens - uBoot
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
bodhi Wrote: ------------------------------------------------------- > Please run this test. > > - 64G Ultra or 32G Ultra rootfs attached to one of > the rear ports. > - 16G or 32G 2.0 Fit formatted completely (use > fdisk to wipe the drive first) as Ext3 data drive > attached to the other rear port. > - 16G or 32G 2.0 Fit formatted completely (use > fdisk tby dhargens - uBoot
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
- 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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
Heck yes - I jumped on that immediately! Working as hoped. Now I can quit bugging you for this! ;-)by dhargens - uBoot
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
Agreed. I updated to 6.3.8 and it's now using the rear port. Thanks again bodhi!by dhargens - uBoot
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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
Re: 2023.04 U-Boot Kirkwood - Pogo V4 - 1 year ago
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