Since upgrading Jetpack to 6.1 and going from CUDA 12.2 to 12.6, there’s an issue with Ubuntu coming back after ‘Screen Blank’. Whenever Screen Blank (Settings->Power) is enabled, it blanks the screen, then when moving mouse or pressing a key to ‘wake it up’ it returns with a fully bright Blue screen (no icons, no mouse, nothing).
Re-plugging the HDMI cable gives me back the expected screen where one has to enter a password for the user after screen lock. Never had this problem in Jetpack 6.0 with CUDA 12.2.
Since one of the updates going from CUDA 12.2 to 12.6 was the use of Open drivers instead of proprietary drivers (seeing release notes), I’m slightly suspecting an issue there but would like to confirm if this could be an issue.
After checking every component and replacing by a spare it turned out that a short HDMI to Display converter cable is the cause of this behavior. That is to say: a spare, identical HDMI to Display converter does not give the Blue Screen.
However: taking this ‘faulty’ HDMI to Display converter back to an existing Jetpack 6.0 Orin AGX that I have (and I’ve always used this cable with that machine), there is no Blue Screen after Screen Blank problem, so there is some combination of hardware and software going on, only exhibited on the Jetpack 6.1 fresh install.
I say ‘fresh install’ because my mentioning an upgrade was not entirely correct. We have several Orin AGX devices running Jetpack 6.0 and now just ordered a new one, for which I used sdkmanager to install Jetpack 6.1. It was an upgrade only in the sense that our installed base uses Jetpack 6.0, but on this Orin it’s a fresh install.
Do you mean when you connect the faulty converter to other JetPack 6.0 devices, it can work correctly?
It only causes issues when connected to a JetPack 6.1 device?
I did check another monitor, same thing. And yes: I mean when I connect the faulty converter to other JetPack 6.0 devices, it works correctly.
However, to test more, now I also upgraded an existing JetPack 6.0 Orin AGX to JetPack 6.1 and there the faulty connector is not problematic! So for now it’s uniquely the freshly installed new Orin AGX that has this problem, with this converter, and not other 6.1 devices.
That sounds like not exactly reproducible (I don’t have another Orin lying around to do a fresh install on), so I can’t reproduce it on another either and this Orin will be shipped to a trial now (with non-faulty converter obviously), so I guess we’ll need to let this rest for now.
Thanks for your help in trying to reproduce. I will update if I know of / experience similar issues later!