After ota update from 32.3 to 32.7.2,The network is not OK when reboot after 'sudo nvbootctrl set-active-boot-slot 0'

Autonomous Machines Jetson & Embedded Systems Jetson AGX Xavier
,
1

Hi,
I update the xavier from 32.3 to 32.7.2, and I execute the command ’ sudo nvbootctrl dump-slots-info’.The following is the the output.
Current bootloader slot: B
Active bootloader slot: B

Then in the following process, when I execute ‘sudo nvbootctrl set-active-boot-slot 0’ and reboot,the network is not ok.
“Make sure device boot to Chain A
→ Follow Xavier image-based update from 32.6.1 to 32.7.2 successfully,then to 35.1failed - #22 by carolyuu steps.”

After the upper process, I excute the commanda “sudo nvbootctrl dump-slots-info” and “ifconfig -a”, the following is the output.
*-desktop:~$ sudo nvbootctrl dump-slots-info
**[sudo] password for *: **
Current bootloader slot: A
Active bootloader slot: A
magic:0x43424e00, version: 3 features: 3 num_slots: 2
slot: 0, priority: 15, suffix: _a, retry_count: 7, boot_successful: 1
slot: 1, priority: 14, suffix: _b, retry_count: 7, boot_successful: 1
*-desktop:~$ ifconfig -a
docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255
ether 02:42:37:05:35:7f txqueuelen 0 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

dummy0: flags=130<BROADCAST,NOARP> mtu 1500
ether f2:3e:59:16:ce:a8 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1 (Local Loopback)
RX packets 4295 bytes 264393 (264.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 4295 bytes 264393 (264.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

3

Hi tianyi2,

Are you connect the LAN cable on your Xavier device?
Check your comment, I don’t see the eth0 in ifconfig.

4

Hi，
Yes,before the the command ‘sudo nvbootctrl set-active-boot-slot 0’, eth0 exists. I can ping baidu OK.
And after reboot after the command ‘sudo nvbootctrl set-active-boot-slot 0’, eth0 doesn’t exist.
Thanks

5

Hi tianyi2,

After OTA update from r32.3 to r32.7.2, it should be at Chain B.
Please make sure below two things:

  1. Is eth0 working?
  2. Run below command to make sure chain A and chain B are boot successful:
    $ sudo nvbootctrl dump-slots-info

If all working, then switch to chain A and reboot.

6

Hi,
After update from r32.3 to r32.7.2, the eth0 work rightly.And the result of $ sudo nvbootctrl dump-slots-info is as following.
Current bootloader slot: B
Active bootloader slot: B

And then execute sudo nvbootctrl set-active-boot-slot 0 and reboot.The result of $ sudo nvbootctrl dump-slots-info is as following.
Current bootloader slot: A
Active bootloader slot: A

And there is no eth0 device.

8

Hi tianyi2,

Our internal team is checking this issue.
Will update result to you.

9

Hi,carolyuu,
Do you have any progress?
Thanks

10

Hi tianyi2,

We’re still checking issue.

11

Hi,carolyuu
Did you check this issue? Do you solve it?
Thanks

12

Hi,
This is under investigation. We will update once there is further progress.

13

Hi,
I have solved it. I added FDT /boot/dtb/kernel_tegra194-p2888-0001-p2822-0000.dtb in /boot/extlinux/exlinux.conf before sudo nvbootctrl set-active-boot-slot 0. Then, reboot, and the network is OK.
Thanks

2 Likes
14

Hi tianyi2,

Thanks for your checking.
The issue fixed with the latest release JetPack-4.6.3 :)

16

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.