Checkout this, it will also apply to Debian i believe.
https://wiki.archlinux.org/title/F2FS
Chapter 3.2
If have used f2fs on SDmmc and Emmc and it behaves very well. For nvme I have chosen to use btrfs, as repair/recovery I think is better supported.
Hi Frank, Was this patch fixed in mainline? I have ordered Patriot P300, 512GB, M.2 SSD (P300P512GM28) for my Bpi-R3, is it going to be a pain to install? I can still cancel the order as I have not received the SSD.
the patch was not accepted in mainline and daniel did a second attempt…but i had no issues yet with nvme…
Thanks, for quick response, I guess I will not cancel the order, lets see if the Patriot P300, 512GB, M.2 SSD (P300P512GM28) works out of the box with BPi-R3 running Current stable release - OpenWrt 23.05.0
i guess the patch is included in openwrt (but not mainline linux) as daniel posted it too…
I would be interested in this outcome, as I’d like to do this also.
As I currently understand, we cannot boot from nvme devices?
nvme devices can be used for applications, opkg installed packages?
Yes,you have to boot from mmc or spi till linux kernel is loaded…rootfs can be on nvme
Just wanted to share my experience on a similar issue I had about PCIe link down.
I fixed my issue by replacing my M.2 hard drive with a new one that was clearly indicated to be compatible with NVMe. My issue was because I didn’t noticed the M.2 hard drive that I purchased was only supporting SATA and wasn’t compatible with NVMe.
Yes r3 has only pcie connected to m.2 slot. No sata or usb lanes…
Reboots randomly after about a day. There are constant errors in the logs on the pci bus
Wed Oct 11 22:12:52 2023 kern.info kernel: [18415.914974] pcieport 0000:00:00.0: AER: Corrected error received: 0000:00:00.0
Wed Oct 11 22:12:52 2023 kern.warn kernel: [18415.922203] pcieport 0000:00:00.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Wed Oct 11 22:12:52 2023 kern.warn kernel: [18415.931756] pcieport 0000:00:00.0: device [14c3:1f32] error status/mask=000000c1/00006000
Wed Oct 11 22:12:52 2023 kern.warn kernel: [18415.940106] pcieport 0000:00:00.0: [ 0] RxErr (First)
Wed Oct 11 22:12:52 2023 kern.warn kernel: [18415.946891] pcieport 0000:00:00.0: [ 6] BadTLP
Wed Oct 11 22:12:52 2023 kern.warn kernel: [18415.952966] pcieport 0000:00:00.0: [ 7] BadDLLP
Wed Oct 11 22:12:52 2023 kern.info kernel: [18415.959061] pcieport 0000:00:00.0: AER: Multiple Corrected error received: 0000:00:00.0
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.016360] pcieport 0000:00:00.0: AER: can't find device of ID0000
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.022619] pcieport 0000:00:00.0: AER: Multiple Corrected error received: 0000:00:00.0
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.080292] pcieport 0000:00:00.0: AER: can't find device of ID0000
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.086570] pcieport 0000:00:00.0: AER: Multiple Corrected error received: 0000:00:00.0
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.144216] pcieport 0000:00:00.0: AER: can't find device of ID0000
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.150469] pcieport 0000:00:00.0: AER: Multiple Corrected error received: 0000:00:00.0
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.208146] pcieport 0000:00:00.0: AER: can't find device of ID0000
Wed Oct 11 22:12:52 2023 kern.info kernel: [18416.214409] pcieport 0000:00:00.0: AER: Uncorrected (Fatal) error received: 0000:00:00.0
Wed Oct 11 22:12:52 2023 kern.err kernel: [18416.222489] pcieport 0000:00:00.0: PCIe Bus Error: severity=Uncorrected (Fatal), type=Transaction Layer, (Requester ID)
Wed Oct 11 22:12:52 2023 kern.err kernel: [18416.233251] pcieport 0000:00:00.0: device [14c3:1f32] error status/mask=00004020/00400000
Wed Oct 11 22:12:52 2023 kern.err kernel: [18416.241594] pcieport 0000:00:00.0: [ 5] SDES (First)
Wed Oct 11 22:12:52 2023 kern.err kernel: [18416.248373] pcieport 0000:00:00.0: [14] CmpltTO
Wed Oct 11 22:12:52 2023 kern.debug kernel: [18416.254469] pcieport 0000:00:00.0: AER: broadcast error_detected message
Wed Oct 11 22:12:52 2023 kern.warn kernel: [18416.261159] nvme nvme0: frozen state error detected, reset controller
NVMe A-Data Falcon 1TB AFALCON-1T-C. Disabled APST in the kernel boot. Nothing helps.
UPDATE:Received the Patriot P300, 512GB, M.2 SSD (P300P512GM28) today and installed it in my Bpi-R3. It is not recognized by the system! I have both kmod-nvme and block-mount packages installed. I guess I am just out of luck and will have to buy another SSD that is known to work with Bpi-R3. What a pain, it is very difficult and time consuming to remove all the antennas and then install them again to be able to reach the bottom of PCB to install the M.2 Nvme.
yes the metal case does not have a hole for replacing the nvme…
With kernel parameters fw_setenv bootargs pci=nomsi. The system works more stably. There are no errors in the logs. But about once a day, the router reboots. My NVMe drive supports msi-x. Does the PCI driver work with interruptions?
Mt7986 pcie uses interrupts
Do not know about msi support…maybe @sam33 or @Ryder.Lee can answer this
Update: Installed Crucial P3 500GB SSD and it works out of the box. Crucial P3 500GB PCIe 3.0 3D NAND NVMe M.2 SSD (Model: CT500P3SSD8).
I’ve ordered a 2TB Seagate Barracuda Q5 M.2 NVME SSD ( ZP2000CV3A001 ), but hasn’t arrived yet!
What are your opinion, will it be okay for bpi-r3?
Finally arrived, and can report it works out of the box!
Hi! how did you do that?
I bought the WD BLUE SN580 1TB model. But it’s not showing up.
thank you!
Hi. Whats about your SSD? Does it work?
Hi Radek! it works flawlessly.