public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Craig Setera <craigjunk@setera.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] Updates to u-boot script for Raspberry Pi 4b devices
Date: Sun, 22 Sep 2024 15:01:40 -0500	[thread overview]
Message-ID: <6bdcbd8c-d598-402d-ae11-bf1be906bb27@setera.org> (raw)
In-Reply-To: <d18a71c1-d6d0-42ef-bff9-ed3f0eec883a@setera.org>

[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]

Today I tried to use this process to upgrade to latest core version 
(188) and the resulting card is not properly working, despite this 
process working for the last couple of releases. Looking in Git, it 
doesn't seem like there were other boot.cmd changes that might have 
caused issues, so thought I'd check here to see if anyone knew what 
might have changed in the most recent release relative to u-boot on RPi?

Thanks for any insights.

Craig

On 6/16/24 10:28 AM, Craig Setera wrote:
> FWIW... I just used my updated u-boot script to update the image for 
> 186 and went through the setup process using serial console for my 
> Raspberry Pi.  My process:
>
> * Download backup from IPFire
> * Flash new image to SD Card
> * Update u-boot script
> * Make new image using script
> * Boot and do initial setup via serial console
> * Login to web admin and restore backup
>
> Even though this is a few more steps than just doing an "in place" 
> upgrade, I actually like that I am keeping the previous SD card and 
> can swap back if something goes wrong.
>
> Craig
>

      reply	other threads:[~2024-09-22 20:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-20 12:17 Craig Setera
2024-05-23 17:01 ` Michael Tremer
2024-06-04 12:40   ` Craig Setera
2024-06-10 16:42     ` Michael Tremer
2024-06-11  0:10       ` Craig Setera
2024-06-16 15:28         ` Craig Setera
2024-09-22 20:01           ` Craig Setera [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6bdcbd8c-d598-402d-ae11-bf1be906bb27@setera.org \
    --to=craigjunk@setera.org \
    --cc=development@lists.ipfire.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox