I’m getting PCIe error messages on my Jetson Nano running ubuntu 18.04. It is able to fully load the desktop environment,but at this point I see a lot of errors all of the same kind that have two bad consequences :
I also don’t know if HDCP is supported or not. I do wonder though, there is a definite PCIe error. You don’t have to have added devices of your own for this to occur since there can be internal PCIe devices (e.g., a bridge, even if not used). You say you are not using any PCIe devices. Are any even plugged in?
Also, I noticed complaints about extended attributes:
[ 17.034748] squashfs: SQUASHFS error: Xattrs in filesystem, these will be ignored
[ 17.044275] squashfs: SQUASHFS error: unable to read xattr id index table
Was this system customized in any way? Is it purely the dev kit from NVIDIA with the SD card mounted on the module and not on the carrier board? It just seems strange to see this if something about the install or kernel wasn’t “average”.
Also, you stated this kernel modification (and I suspect the kernel configuration might be an issue for at least some of this):
removing “CONFIG_PCIEASPM_POWERSAVE=y” and setting “CONFIG_PCIEASPM_PERFORMANCE=y”
Did you set “CONFIG_PCIEASPM_POWERSAVE=n”? This seems correct, but that’s different from just removing the config. When you made those modifications, did you use a kernel configuration editor, e.g., “make menuconfig” (or similar)? If edited directly with an editor the results won’t be good.
I don’t think. The devices attached to the jetson nano are mouse,keyboard,hdmi cable,kiwibird sdcard to usb adapter. I can’t use the sd card directly anymore. It boots 1 time on 10 tries. With the usb adapter it boots more frequently.
—> Was this system customized in any way?
I’ve installed ubuntu from the prebuilt image provided bv nvidia. I have enabled kvm by downloading the source code from here :
I’ve changed that parameter to fix another error,that’s my monitor that after sometime it shuts down and never comes back. And even when I turn it off,it does not turn on until I reboot the jetson nano. I was playing with the energy saving parameters.
PCI “AER” is “Advanced Error Reporting”. Some hardware has a chance to partially or fully recover if that is enabled, and it also helps in debugging. This won’t show up because a feature is added (well, turning off reporting and then turning it on would change seeing the messages), but this is rarely anything but either (A) hardware issues (some temporary), or (B) incorrect drivers. The latter is unlikely, but not impossible.
Do understand that the image on the SD card the Linux o/s, but it is not the boot content. The boot content itself must be of a release matching the SD card (some releases match a range, but quite often if you change an SD card or create one for the first time, and it fails, then it is an issue of that boot stage software which is not on the SD card). Flashing with JetPack/SDK Manager flashes the module itself (the QSPI memory in it), which is what flashes that boot content. You’ve updated the SD card, and it doesn’t work, so flashing the module itself is a very good initial step to fix. Certainly you can’t know hardware or software until both module and SD card have correct releases.
Note that JetPack/SDKM is a front end to flash software running on the host PC, whereas L4T (Ubuntu plus NVIDIA drivers) is what actually gets flashed. The two releases are tied together, so if you know one, then the other is also determined. You can see the L4T release with “head -n 1 /etc/nv_tegra_release”, which could also be found on the SD card looking at it from a host PC. You can see instructions for a specific release by going to the specific L4T release. A list of releases are available for each here (Nano can use 4.x JetPack or 32.x series L4T):