hello,
i’m facin an issue after trying to upgrade the ubuntu version, usb ports are not working if i plugged mouse and keyboard , i tried to plug the Arduino and i can see lights on.
I can access the jetson remotely and control it using my pc.
could you please advice me what is the issue exactly ?
some screen shot attached may helps.
You will probably need to provide a serial console boot log since the screenshot doesn’t say much. I can see it is assigning a random ethernet address, but there isn’t much to go by with that, e.g., maybe it has an issue reading the i2c memory, but that is set up and actually read much earlier in boot. Serial console is about the only way to get the very early boot content. A dmesg log over ssh might help, but serial console has this as well as the pre-Linux logging.
You’ll also want to state specifically if this is a dev kit, or some third party carrier board, so on. Include which release is being used (you can find this with “head -n 1 /etc/nv_tegra_release” if you have ssh access).
regarding the first query dmesg file attached.
demsg (63.1 KB)
regarding the 2nd:
jetson@Nano:~$ head -n 1 /etc/nv_tegra_release
Are there any peripherals attached? Especially, is anything running on the PCIe (which can be on an m.2 slot)? There is definitely a PCI bus error, although it says it was able to correct (and this happens to be the last message at the point boot stops).
all attachment unplugged and here is the dmesg log.
dmesg (64.1 KB)
I don’t see the previous PCIe AER corrected error, but I do see xusb_padctl related to PCIe in the new log. This in itself is normal and not an error, it just shows a relation. However, I then see a PCIe bridge log note:
[ 1.288646] kernel: pci 0000:00:01.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 1.288656] kernel: pci 0000:00:02.0: bridge configuration invalid ([bus 00-00]), reconfiguring
I have no idea if this has any indication of a real issue since this might be normal. I only mention it because of the previous PCIe AER corrected error. Was there previously any peripheral attached which might be related? Not a mouse or keyboard or monitor, but perhaps an m.2 card or some special USB device?
Later I do see firmware load errors related to WiFi:
[ 3.796185] kernel: Copyright(c) 2003- 2015 Intel Corporation
[ 3.796409] kernel: iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[ 3.805537] kernel: iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-26.ucode failed with error -2
[ 3.816142] kernel: iwlwifi 0000:01:00.0: Falling back to user helper
[ 3.845051] kernel: tegra-xusb 70090000.xusb: cannot find firmware....retry after 1 second
[ 4.757665] kernel: iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-25.ucode failed with error -2
[ 4.768306] kernel: iwlwifi 0000:01:00.0: Falling back to user helper
[ 4.805344] kernel: iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-24.ucode failed with error -2
[ 4.815162] kernel: iwlwifi 0000:01:00.0: Falling back to user helper
[ 4.823703] kernel: iwlwifi 0000:01:00.0: Direct firmware load for iwlwifi-8265-23.ucode failed with error -2
[ 4.833555] kernel: iwlwifi 0000:01:00.0: Falling back to user helper
[ 4.850248] kernel: tegra-xusb 70090000.xusb: Direct firmware load for tegra21x_xusb_firmware failed with error -2
[ 4.851241] kernel: iwlwifi 0000:01:00.0: loaded firmware version 22.391740.0 op_mode iwlmvm
[ 4.859939] kernel: tegra-xusb 70090000.xusb: Falling back to user helper
[ 4.868451] kernel: tegra-xusb 70090000.xusb: cannot find firmware....retry after 1 second
[ 4.892194] kernel: iwlwifi 0000:01:00.0: Detected Intel(R) Dual Band Wireless AC 8265, REV=0x230
[ 4.894066] kernel: iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
[ 4.894766] kernel: iwlwifi 0000:01:00.0: L1 Enabled - LTR Enabled
That error would not directly cause boot to halt or fail. However, when I see a firmware issue it may mean that a driver is interacting incorrectly with hardware, e.g., it is like using the wrong API version in a way, and something undefined may occur. That interaction could interfere with other drivers and could cause a boot failure (this is again conjecture since I don’t know if that is really going on, but the system is not booting, and this is one of the things which show up as “it shouldn’t do that”).
Then it loads bluetooth and locks up. Perhaps the bluetooth and WiFi are interacting? I don’t know, but is there any other hardware you added in the past where drivers might still be around?
i don’t know what is m.2 card is , but I’m 100% sure that no special USB connected. only thing connected is wifi card and it is working fine. main issue is USB port.
if this will help, this issue pop-up when i tried to update the system from 18.02 to 20.04 and failes, current sys. is 20.04.4 LXDE.
I did not realize the update was to a new Ubuntu release (18.04 to 20.04). My earlier (bad) assumption was that this was just a package update for patches. R32.5.1 does not support any kind of upgrade to Ubuntu 20.04, so much of the software needed to support the hardware will likely break.
Take a look at this list of release versions versus both L4T version and hardware type:
https://developer.nvidia.com/embedded/jetson-linux-archive
Also, the JetPack/SDK Manager releases which flash the specific L4T releases (JetPack is the flash software, L4T is what gets flashed to the Jetson):
https://developer.nvidia.com/embedded/jetpack-archive
Unfortunately, you will find that only Xavier and newer (meaning Orin at this time) support the newer L4T releases which are required for Ubuntu 20.04. This is probably why the firmware load failed…it is the wrong firmware for that hardware and driver combination. I do not know of any workaround to this other than using newer hardware, or remaining at Ubuntu 18.04.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.