The NanoPi is not officially supported on Ubuntu, as you are using a
custom build. I would advise to report the bug to your image
distributor. Marking as invalid. Since the error is `
mmc_load_image_raw_sector: mmc block read error` from uboot it might be
related to uboot anyways.
** Also affects: linux (Ubuntu Noble)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Oracular)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu Noble)
Status: New => Triaged
** Changed in: linux (Ubuntu Oracular)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Oracular)
Status: Triaged => Invalid
** Changed in: linux (Ubuntu Noble)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2090788
Title:
On a NanoPi R4S, oracular fails the first reboot
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Noble:
Invalid
Status in linux source package in Oracular:
Invalid
Bug description:
On a freshly installed NanoPi R4S, the first reboot hangs with this
error:
### ERROR ### Please RESET the board ###
All reboots after this work OK. The problem only exists with the
oracular image from https://sd-card-
images.johang.se/boards/nanopi_r4s.html; I'm using the image ubuntu-
oracular-arm64-eo3ye4.bin.gz.
Images for noble and plucky are also affected; jammy works OK. An
Armbian noble image is also OK.
I apologize for posting this, but it's probable that help from
somebody with intimate knowledge of the reboot mechanism is required
to debug this. That's definitely not me ;-) It is also possible that
the problem lies with U-Boot, but since jammy works OK, I don't think
so.
Messages leading up to this message:
[ OK ] Reached target reboot.target - System Reboot.
[ 117.632275] reboot: Restarting system
U-Boot TPL 2024.10johang-dirty (Nov 01 2024 - 02:10:40)
lpddr4_set_rate: change freq to 400MHz 0, 1
Channel 0: LPDDR4, 400MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
Channel 1: LPDDR4, 400MHz
BW=32 Col=10 Bk=8 CS0 Row=15 CS1 Row=15 CS=2 Die BW=16 Size=2048MB
256B stride
lpddr4_set_rate: change freq to 800MHz 1, 0
Trying to boot from BOOTROM
Returning to boot ROM...
U-Boot SPL 2024.10johang-dirty (Nov 01 2024 - 02:10:40 +0000)
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
Trying to boot from MMC2
mmc_load_image_raw_sector: mmc block read error
SPL: failed to boot from all boot devices
### ERROR ### Please RESET the board ###
ProblemType: Bug
DistroRelease: Ubuntu 24.10
Package: linux-image-6.11.0-9-generic 6.11.0-9.9
ProcVersionSignature: Ubuntu 6.11.0-9.9-generic 6.11.0
Uname: Linux 6.11.0-9-generic aarch64
ApportVersion: 2.30.0-0ubuntu4
Architecture: arm64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/timer',
'/dev/snd/seq'] failed with exit code 1:
CasperMD5CheckResult: unknown
Date: Sun Dec 1 18:20:49 2024
Lspci-vt: -[0000:00]---00.0-[01]----00.0 Realtek Semiconductor Co., Ltd.
RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller
ProcFB:
ProcKernelCmdLine: root=PARTUUID=df945dd4-02 rw rootwait
RelatedPackageVersions:
linux-restricted-modules-6.11.0-9-generic N/A
linux-backports-modules-6.11.0-9-generic N/A
linux-firmware 20240913.gita34e7a5f-0ubuntu2
RfKill:
SourcePackage: linux
StagingDrivers: rockchip_vdec
UpgradeStatus: No upgrade log present (probably fresh install)
acpidump:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2090788/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
