Bug in rpi-update (wrong github url to download firmware)?

[u/jodkalemon]

When I run rpi-update on an rpi4b-2gb I get:

If you are unsure, test if your system boots with initramfs options disabled from config.txt
Would you like to proceed? (y/N)
Github API request failed with HTTP 422: https://api.github.com/repos/raspberrypi/rpi-firmware/commits/0

Respond of the link is

{
  "message": "No commit found for SHA: 0",
  "documentation_url": "https://docs.github.com/rest/commits/commits#get-a-commit",
  "status": "422"
}

What happened here and can you reproduce the bug?

[u/KingofGamesYami]

Firmware updates have been distributed through apt for a while now. rpi-update is only used for testing experimental firmware patches. Are you sure you want to run rpi-update?

[u/jodkalemon → u/KingofGamesYami]

Oh, didn't know that. Thought this is needed for the eeprom to be updated.

Edit:

So I just run rpi-eeprom-update which installs the current safe eeprom image which came through apt?

[u/KingofGamesYami → u/jodkalemon]

Edit: So I just run rpi-eeprom-update which installs the current safe eeprom image which came through apt?

No. You run sudo apt update and sudo apt upgrade to update normally. Do not run rpi-eeprom-update.

If you've already run rpi-update in the past and currently have experimental firmware installed, follow the instructions in the section "Downgrade firmware to the last stable release".

https://www.raspberrypi.com/documentation/computers/os.html

After that, you won't need to do anything special in the future.

[u/jodkalemon → u/KingofGamesYami]

Will do that. Thanks for clarification. Always thought it was weird that an update process touched kernels from the repository.

[u/dovyp]

That SHA 0 is a dead giveaway the script is stale. Grab a fresh rpi-update, the firmware URL on their end moved.

[u/saint-lascivious → u/dovyp]

Alternatively, don't, since there are approximately zero reasons for Johnny Homeuser to be running bleeding edge firmware.