Qengineering / Jetson-Nano-image

Jetson Nano image with deep learning frameworks
https://qengineering.eu/install-tensorflow-2.4.0-on-jetson-nano.html
BSD 3-Clause "New" or "Revised" License
123 stars 23 forks source link

Running Jtop causes the system to brick next time it is rebooted #12

Open v2thegreat opened 2 years ago

v2thegreat commented 2 years ago

Currently running jtop at any point makes it so that the system ends up crashing when the machine is rebooted

Here are some screenshots that might be useful for you guys

My plan right now is that I'm just going to reinstall everything from scratch and make sure that I don't run jtop, but I would like to use jtop in the future since it is a really nice utility

PXL_20220101_202100201

PXL_20220101_202153177

Overall, I ❤️ the work you guys have put into this!

Qengineering commented 2 years ago

Dear @v2thegreat,

I've tried to reproduce your issue. Downloaded the image and flashed it on a new SD. No problem with JTop. Did a sudo apt-get update and sudo apt-get upgrade. Still no problem. I can use JTop as any other program and reboot without any hitch.

My intuition tells me that your operating system is somewhere, corrupted in some way. I would recommend backing up all your work to USB and getting a new and fresh OS.

v2thegreat commented 2 years ago

The thing is, I've tried this 3-4 times. I had installed some additional packages and stuff when I got things working. I'm currently using a jetson nano 4GB. This time I'll do a more detailed overview of what I end up doing. Oh, I should mention: I disable the desktop since that enables me to free up more memory. Did you try that out as well?

I can't think of anything at this time that I might be doing, so I'll get back to you on it if things happen again, this time with detailed instructions for what is going wrong if I can

Qengineering commented 2 years ago

I will wait. I can imagine that turning off the desktop image doesn't make JTop happy. By the way, I'll help you as best I can, but the whole problem is more of a JTop issue than an SD image problem. I think, if you had an original JetPack image, without the extra software we put on it, you'd still be in trouble.