Bridge Firewalling registered


(Bridge Firewalling registered) what does it mean ?
Can anyone help me with that , my screen is got stuck after that

hello souravmahari,

may I know which release version you’re using? is it a Jetson Nano Developer Kit?

Yes sir it is a jetson nano developer kit, i purchase it from think robotics actually release version means jes pack version ? Or something else
I am attaching some screenshots where I purchased it , this may help you to know the release version

Screenshot_20221013-083749|225x500

hello souravmahari,

please also share the JetPack release version you’ve flashed to this target.
you may also gather SDK report logs (it could generated as zip file) for reference,
thanks

Jet pack release version is
Jetson-nano-jp461-sd-card-image

Hi can you please let me know what to my project submission is near

hello souravmahari,

Bridge firewalling registered this should not the root cause of booting hang,
it’s a simple print of kernel function, br_netfilter_init() has complete.

is this platform you bought from ThinkRobotics also provide board configuration files?
is it identical with Jetson Nano developer kits?

please re-flash the device by using NVIDIA SDK Manager, it’ll parse the board eeprom and assign correct cfg file for image flashing.
thanks

Log report

[ 1.168656] tegradc tegradc.1: dpd enable lookup fail:-19
[ 1.190672] tegradc tegradc.1: dp: aux write got error (0x10000100)
[ 1.196994] tegradc tegradc.1: dp: Failed for I2C write addr:80, size:1, stat:0x10000100 [ 1.217386] tegradc tegradc.1: dp: aux write got error (0x10000100)
[ 1.223683] tegradc tegradc.1: dp: Failed to write DPCD data. CMD Ox600, Status Ox10000100
[ 1.237036] tegradc tegradc.1: dp: aux write got error (0x10000100)
[ 1.243322] tegradc tegradc.1: dp: Failed to write DPCD data. CMD Ox600, Status Ox10000100
[ 1.256362] tegradc tegradc.1: dp: aux write got error (Ox10000100)
[ 1.262653] tegradc tegradc.1: dp: Failed to write DPCD data. CMD Ox600, Status Ox10000100
[ 1.275981] tegradc tegradc.1: dp: aux write got error (Ox10000100)
[ 1.282265] tegradc tegradc.1: dp: Failed to write DPCD data. CMD Ox600, Status Ox10000100
[ 1.290543] tegradc tegradc.1: dp: failed to exit panel power save mode (Oxfffffff2) [ 1.326963] imx219 7-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.327032] imx219 7-0010: board setup failed
[ 1.350851] imx219 8-0010: imx219_board_setup: error during i2c read probe (-121)
[ 1.350909) imx219 8-0010: board setup failed
[ 1.414870] tegradc tegradc.1: dp: aux write got error (Ox10000100)
[ 1.414874] tegradc tegradc.1: dp: Failed to write DPCD data. CMD Ox600, Status Ox10000100 1.419851] tegradc tegradc.1: dp: aux write got error (Ox10000100)
[ 1.419855] tegradc tegradc.1: dp: Failed to write DPCD data. CMD 0x600, Status Ox10000100
[ 1.424829] tegradc tegradc.1: dp: aux write got error (Ox10000100)
[ 1.424832] tegradc tegradc.1: dp: Failed to write DPCD data. CMD Ox600, Status Ox10000100
[ 1.429660] tegradc tegradc.1: dp: aux-write got error (Ox10000100)
[ 1.429663] tegradc tegradc.1: dp: Failed to write DPCD data. CMD Ox600, Status. Ox10000100
[ 1.429666] tegradc 'tegradc.1: dp: failed to exit panel power save mode (Oxfffffff2)
[ 1.429669] hpd: ed id read prepare failed
cp: not writing through dangling symlink ‘etc/resolu.conf’
[ 1.898988] cgroup: cgroup2: unknown option “nsdelegate”
[ 3.103394] using random self ethernet address
[ 3.118761] using random host ethernet address
[ 3.822117] random: crng init done
[ 3.825550) random: 7 urandom warning(s) missed due to ratelimiting
[ 4.027635] using random self ethernet address
[ 4.042287] using random host ethernet address

Yes sir thinkRobotics provide board configuration on file and it is identical to jetson nano

Please si help me with that my project submission is coming Monday . please sir helpe its a humble request

If I rest the jetson nano developer kit and once again install jet pack it’ll be run ? Or not

Do you have serial console access? This tends to work even when graphical mode fails for a directly connected monitor. It isn’t unusual for the system to actually be up and running if it got that far, but fail only in the GUI display. Serial console is from a separate host PC, and thus it can log boot even when the rest of the system fails, and often you can work on text-mode this way even when the local monitor fails. You’d use the micro-OTG USB connector with a micro-B USB cable at the Jetson, and plugged in at the other end to a Linux host PC (technically you could do this with something like PuTTY on a Windows host as well, or a Mac, but tools for working with this on a Linux Ubuntu 18.04 host PC will work best).

Also, is this an ordinary HDMI monitor? Are there any cable adapters?

hello souravmahari,

please try download Jetpack release image, and re-flash the target with provided board configuration.
if you don’t have display monitor connected, you may execute l4t_create_default_user.sh to Skipping oem-config.

1 Like

Thank you ❤️ my problem is solved now it’s working properly

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