We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
would be nice if nvme boot was documented.
building the default image from git master doesnt appear to have pci enabled in uboot at all?
=> nvme scan => => pci Scanning PCI devices on bus 0 BusDevFun VendorId DeviceId Device Class Sub-Class _____________________________________________________________ =>
this looks relevant
PCIe1: pcie@3400000 disabled PCIe2: pcie@3500000 disabled PCIe3: pcie@3600000 Root Complex: no link PCIe4: pcie@3700000 disabled PCIe5: pcie@3800000 Root Complex: x1 gen3 PCIe6: pcie@3900000 disabled
The text was updated successfully, but these errors were encountered:
linux seems to be unhappy about the m.2 slot as well:
[ 133.829728] pcieport 0001:00:00.0: AER: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) [ 133.839742] pcieport 0001:00:00.0: AER: device [1957:8d80] error status/mask=00000001/00006000 [ 133.848529] pcieport 0001:00:00.0: AER: [ 0] RxErr
using the x8 pcie slot instead fixes this, but i'm assuming uboot isnt configured to scan that
Sorry, something went wrong.
Switching from a crucial to samsung made it work.
Leaving open just in case this is a hardware issue that should be investigated?
Just for the record: Samsung SSD 980 PRO NVMe M.2 (Model: MZ-V8P1T0) was detected fine by u-boot and Linux.
No branches or pull requests
would be nice if nvme boot was documented.
building the default image from git master doesnt appear to have pci enabled in uboot at all?
this looks relevant
The text was updated successfully, but these errors were encountered: