Pi 5: NVMe (Innogrit IG5216, 1dbe:5216) stays "Device not ready, CSTS=0x0" after re-probe on 6.18 – recovers on 6.12
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- c, linux, raspberry-pi
- Domain
- backend, operating-systems
Research direction
Compare the reported behavior in kernels 6.18.50 and 6.12.75, focusing on the brcm-pcie re-probe path and NVMe controller initialization on Raspberry Pi 5. Start by locating the PCIe driver and relevant kernel changes between those versions, then reproduce with the Apacer AS2280P4U and the supplied boot settings. Done means the cause of CSTS=0x0 is identified and the drive initializes reliably after boot or re-probe.
Written by the indexing model from the issue text.
Description
Describe the bug
An Apacer AS2280P4U 256GB SSD (Innogrit IG5216, 1dbe:5216, FW 2.O.3.1G) on the Pi 5 PCIe port cannot boot (rootfs on the ssd).
Booted fine from NVMe until ~[mid-Sept 2026], when apt moved the system to 6.18.
NVMe boot: link comes up, but the controller never gets ready:
brcm-pcie 1000110000.pcie: link up, 5.0 GT/s PCIe x1 (!SSC)
nvme nvme0: Device not ready; aborting initialisation, CSTS=0x0 (after ~50 s)
Re-probing the port from the initramfs (brcm-pcie unbind/bind of 1000110000.pcie):
- 6.12.75: recovers first time, boots from NVMe.
- 6.18.50: same
CSTS=0x0on every retry, root never appears.
SD boot (bootloader doesn't touch the SSD), 6.18.50: link down on every boot; the same re-probe brings it up every time.
Pi 5 Rev 1.1 + [carrier board], bootloader 2026/09/25 (same with 2026/05/26), BOOT_ORDER=0xf4166, PCIE_PROBE=1.
Bootloader side: raspberrypi/rpi-eeprom#912.
Steps to reproduce the behaviour
- Pi 5 + [carrier board, e.g. Raspberry Pi M.2 HAT+] + Apacer AS2280P4U 256GB with Raspberry Pi OS (trixie).
- BOOT_ORDER=0xf4166 (NVMe first), boot kernel 6.18.50 → hangs waiting for root; serial log shows the above.
- Same, but kernel 6.12.75 via
os_prefix→CSTS=0x0after 50 s, then a brcm-pcie unbind/bind recovers it.
Raspberry Pi 5 Model B Rev 1.1 (reproduced on [3] Pi 5 boards, [carrier boards]).
The same drive works in a PC M.2 slot and in a USB (RTL9210) enclosure on the Pi. Other NVMe drives work on the same Pis/HAT.
Device (s)
Raspberry Pi 5
System
- Raspberry Pi OS trixie, kernels 6.18.50+rpt-rpi-2712 (bad), 6.12.75+rpt-rpi-2712 (recovers)
- Bootloader 2026/09/25 (1accd665); same result with 2026/05/26 (086b83e3)
BOOT_ORDER=0xf4166,PCIE_PROBE=1, PCIe Gen 2 (default)
Logs
No response
Additional context
No response
- Dominant language
- C
- Stars
- 13.3k
- Forks
- 5.5k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 31
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from raspberrypi/linux
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7415 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
rp1-cfe doesn't forward V4L2_EVENT_SOURCE_CHANGE event from csi-2 sensor driver to userspace appOpen
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
raspberrypi/linux#7399 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
raspberrypi/linux#7357 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
raspberrypi/linux#7054 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
raspberrypi/linux#7770 ·
Maintainers usually reply within 1 day
All issues in raspberrypi/linux
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LedgerHQ/app-bitcoin-legacy#306 ·
-
[issue]: Ventoy2Disk.sh can leave the end of VTOYEFI unwritten (xzcat | dd without iflag=fullblock)Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
prusa3d/Prusa-Firmware-Buddy#5629 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 3 days
-
Issue PRL on WindowsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day