reComputer AI Lab is a one-stop development platform for reComputer edge hardware, enabling developers to deploy AI models in just two steps and drastically lowering the barrier to edge AI development.
This category is for discussing usage, troubleshooting, deployment cases, and feature requests.
Hi admin, I can’t create a new topic, so please let me post as a comment in this post.
I am currently using a Seeed reComputer Mini J501 kit with the official Seeed JetPack 6.2.1 image:
mfi_recomputer-mini-agx-orin-j501-6.2.1-36.4.3-2026-02-05.tar.gz
Hardware:
Seeed reComputer Mini J501
Jetson AGX Orin module
HDMI monitor connected directly
Serial debug console via ttyTCU0 working normally
Problem:
The system boots successfully, but the HDMI monitor remains completely black.
Initially during boot I observed repeated DRM errors such as:
[drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] Flip event timeout on head 0
[drm:nv_drm_atomic_commit [nvidia_drm]] ERROR [nvidia-drm] Failed to apply atomic modeset
and also:
[nvidia-drm] Failed to grab modeset ownership
After modifying kernel parameters, the flip timeout errors disappeared, but HDMI output is still black.
Current kernel parameters:
nvidia-drm.modeset=1
nvidia-drm.fbdev=0
I also disabled Wayland:
WaylandEnable=false
and switched from gdm3 to lightdm + XFCE, but HDMI is still black.
Important observations:
The following DRM node exists:
/sys/class/drm/card1-HDMI-A-1
Status:
connected
Supported modes include:
2560x1440
1920x1080
etc.
EDID can be read successfully.
lsmod shows:
nvidia_drm
tegra_drm
drm_kms_helper
cat /proc/fb
returns:
0 simple
fbset -i shows:
mode “2560x1440”
I tested:
sudo fbi -T 1 -d /dev/fb0 /usr/share/backgrounds/warty-final-ubuntu.png
No error is reported, but the HDMI monitor still stays black.
startx output:
xinit: connection to X server lost
Server terminated successfully (0)
Couldn’t get a file descriptor referring to the console.
It looks like:
simplefb is active
framebuffer memory exists
HDMI EDID works
but the actual display scanout/display plane may not be active.
Questions:
Is this a known issue on reComputer Mini J501 with JetPack 6.2.1?
Is there a recommended DRM/KMS configuration for stable HDMI output?
Should simplefb be disabled?
Is there any known conflict between:
simplefb
tegra_drm
nvidia_drm
Is there a recommended extlinux.conf configuration for HDMI stability?
Any help or recommended configuration would be greatly appreciated.
Thank you.
I flashed the official Seeed MFI image for reComputer Mini AGX Orin J501, JetPack 6.2.1 / L4T R36.4.4.
HDMI is now detected:
/sys/class/drm/card1-HDMI-A-1/status = connected
EDID is readable
xrandr shows HDMI-0 connected primary 2560x1440
But the screen remains black, and kernel logs show:
[drm:nv_drm_atomic_commit] Flip event timeout on head 0
tegra-mc ... nvdisplayr: secure read ... EMEM address decode error
arm-smmu ... Unhandled context fault
I checked the MFI flash.idx, and the display/DCE firmware is flashed from:
display-t234-dce_with_tegra234-j501x-0000+p3701-0004-recomputer-mini_with_odm_overlay.dtb_with_dce_overlay_aligned_blob_w_bin_sigheader.bin.encrypt
Is there a known issue with the DCE/display overlay loading order or DCB config for J501 + AGX Orin 32GB on R36.4.4?
Hi There,
SO the latest video is pretty cool, I would couple it with a Xiao nRF54LM20A Sense wristband 
Perfect closed-loop system
GL 
PJ 
Subject: JetPack 7 (L4T r39.x) image for reComputer J4012 / J401 carrier — available or planned?
I’m running your JetPack 6.2 / L4T R36.4.3 GMSL image on a reComputer J4012 (Orin NX 16GB, J401 carrier). I need a newer NVIDIA display driver than the 540.x that ships with R36.4 — specifically the 580-series driver, which fixes a DisplayPort DSC (Display Stream Compression) bug that currently prevents me from driving a DSC-mandatory VR headset.
That driver only appears in JetPack 7 (L4T r39.x). My questions:
Thanks.
Hi there,
And Welcome here…
So,You are completely right on the money here, and my strong advice is: No, definitely do not try to force-boot the stock NVIDIA JetPack 7 image.
Others have (many posts) thrown caution to the wind, and YOLO’d it anyway thinking they could hack there way back 
only to add to the BRICK pile of headachesville.
Trying to flash stock JetPack 7 (L4T r39.x) directly onto the reComputer J4012 right now is a recipe for a bricked setup or a massive headache. Here is why you should absolutely hold off and wait for Seeed to release a dedicated Board Support Package (BSP) image:
Custom Carrier Board Quirks: The J401 carrier board is a custom Seeed design with its own specific peripheral routing, interfaces, and pinmux configurations. Stock NVIDIA JetPack images are strictly compiled for NVIDIA’s own reference developer kits. If you flash it, the device trees will mismatch, meaning critical components like your GMSL interface, specific USB routing, and display outputs will immediately break.
JetPack 7 Toolchain Overhauls: JetPack 7 introduces massive underlying architecture alignment shifts (moving toward SBSA standardizations, new kernel models, and stricter bootloader checks). Even on reference dev kits right now, community threads are seeing severe package configuration aborts (nvidia-l4t-bootloader errors) due to stricter board-spec matching. Trying to adapt that manually to the J401 layout is playing on ultra-hard mode.
The 540.x Driver Constraint: For the current JetPack 6.2 (L4T R36.4.x) line, the display driver branch is tightly integrated into that specific BSP generation. There won’t be a point release that backports a 580-series driver into JetPack 6, as major graphics driver updates are tied directly to the major L4T bumps.
Hold steady on your current JetPack 6.2 setup for production. Forcing the upgrade now will completely scramble your GMSL camera setup and hardware pin mapping. It is much safer to wait for Seeed Studio to officially release their tailored JetPack 7 image with the appropriate driver support and validated device trees for the J401 carrier.
HTH
GL PJ
seems kind a light on RAM for what you want to get at the end goal? 
Hi there,
“Aside from the JetPack 7 driver issue, keep an eye on that 16GB memory footprint. Because the Orin NX shares its 16GB across both system RAM and VRAM, driving a heavy DSC-mandatory VR headset is going to leave you with very little headroom for your actual application logic and framebuffers once the OS takes its cut!”
That 16GB of LPDDR5 has to be shared simultaneously by:
The Linux OS kernel and background services.
The application runtime (e.g., ROS2, custom C++/Python pipelines, Unity/Unreal embedded runtimes).
The massive framebuffers required to render dual high-resolution VR displays at 90Hz+.
VR headsets that mandate Display Stream Compression (DSC)—like the Varjo series, Pimax Crystal, or high-end enterprise headsets—are pushing massive native resolutions (often well north of 4K per eye before lens distortion compensation rendering scales it even higher).
Just allocating the ping-pong textures, depth buffers, and runtime memory overhead for a single stereo frame at those resolutions can easily swallow 6GB to 8GB of VRAM on a desktop card. On the Orin NX, that instantly eats up half of his entire system memory, leaving almost nothing left for actual compute, AI model weights, or data processing.
HTH
GL PJ
Hi everyone,
We are evaluating the reComputer J3011 (Jetson Orin Nano 8GB) for a project in El Salvador, and the Seeed sales team suggested we ask here.
Deployment environment:
The devices will be installed inside an outdoor enclosure with ventilation slots (not sealed).
Under direct sun, temperatures can reach around 40 °C, and humidity is high for long periods.
24/7 operation.
Workload: the device will run YOLO26n inference on 4 camera streams simultaneously. In lab/bench tests (not yet in the field), the device reached around 60 °C under this load, as reported by the operating system’s built-in thermal monitoring tools. We are concerned that the combination of this load and the higher ambient temperature inside the enclosure could push it further.
Software: Ubuntu 22.04.5 · Jetson Linux L4T 36.4.3 (JetPack 6.2) · kernel 5.15.148-tegra
Questions:
What is the rated operating temperature range of the reComputer J3011 as a complete system (module + carrier board + heatsink/fan)? What are the storage temperature and humidity ranges?
Could sustained heat inside the enclosure cause thermal throttling? At roughly what temperature does it start, and how much performance loss is typical? Is there a recommended power mode for these conditions? Given the ~60 °C we measured in bench tests, how much margin would we have once the device is inside the enclosure in the field?
Could long-term operation in high heat and humidity degrade performance or lifespan (fan wear, NVMe SSD, carrier board components)? Is the carrier board conformal-coated?
Is there a version with the same specifications but better cooling or a wider operating temperature range, for example the reComputer Industrial J3011 (fanless) or another rugged option? What are the main differences in temperature rating and I/O?
Do you have any recommendations for the enclosure (ventilation, passive heatsinks, dust/insect filters, IP rating) for this kind of deployment?
Thanks in advance!
Hi there
And Welcome Here… charcters I better get a cut of the Sale too, then 
So great question, We know the answer and by the end YOU 
should too!
Cutting Right to the Catch , skipping the Chase.
..
Here is why and Hi David, welcome to the community!
To give you the short, direct engineering reality: Do not deploy the standard reComputer J3011 in that environment.
The standard commercial J3011 is designed for climate-controlled indoor/desktop lab deployments. Putting it inside a vented outdoor box in El Salvador’s 40 °C direct-sun ambient will result in severe thermal throttling and premature hardware failure.
Here is why, addressing your points:
The Thermal Math Doesn’t Work:
A vented enclosure under direct sun regularly sees internal temperatures climb to 55 °C – 65 °C due to solar loading.
If your indoor bench test (at ~22 °C ambient) hit 60 °C, your delta ($\Delta T$) is roughly $+38\text{ }^\circ\text{C}$. Inside a 55 °C enclosure, your core will push 93 °C+.
Tegra thermal throttling initiates at 85 °C, scaling down clock domains and dropping inference FPS. At 95 °C – 99 °C, it hits critical thermal trip and triggers a hard system shutdown.
No Conformal Coating:
The standard J3011 carrier board is not conformal-coated.
An unsealed, slotted enclosure in sustained high humidity will allow condensation cycles, salt/mineral dust, and insects inside, leading to dendritic shorts and corroded traces on bare SMD pads and the SODIMM connector.
Active Fan Failure:
The Proper Solution: reComputer Industrial J3011
If you want to stick with Seeed’s Orin Nano 8GB platform, look at the reComputer Industrial J3011.
Fanless / Passive Cooling: Uses the heavy aluminum finned chassis as the heatsink, eliminating mechanical fan failure.
Industrial Rating: Rated for -20 °C to 60 °C operating temps.
Power & I/O: Built with wide-input industrial power (9V–36V with surge protection) rather than a commercial barrel jack, plus robust mounting brackets.
Enclosure Recommendations:
Use an IP66 or NEMA 4X sealed enclosure with an external solar radiation shield / double-roof sunshade to keep radiant heat off the box.
Avoid slotted vents in humid environments; if heat dissipation requires airflow, use a sealed heat exchanger or a filtered, forced-air push-pull fan system with serviceable louvers/filters on the exhaust/intake.
HTH
GL PJ
Not to leave you Hanging..
can we recommend an industrial version or ways to mitigate the issues?
Indeed, Yes. We can recommend the dedicated reComputer Industrial J3011 and provide concrete hardware/enclosure mitigation strategies.
Here is a focused, ready-to-paste follow-up or replacement :
Instead of the commercial desktop model, switch to the reComputer Industrial J3011 (Orin Nano 8GB).
Key advantages for this specific deployment:
Operating Range: Rated -20 °C to 60 °C, compared to the commercial desktop unit’s limited indoor profile.
Fanless Conduction Cooling: The heavy extruded aluminum finned chassis is the heatsink. Eliminating moving fans avoids premature sleeve/bearing failure from dust and coastal humidity.
Industrial Carrier Board & Ingress Protection: Built for factory floors and harsh outdoor cabinets with an IP40 aluminum enclosure.
Power & Transient Protection: Accepts 9V to 36V DC via industrial terminal blocks (essential for outdoor pole/solar power fluctuations) rather than a commercial barrel connector.
Field I/O: Includes isolated RS485, CAN bus, digital I/O, and dual Gigabit Ethernet ports tailored for multi-camera deployments.
Even with an industrial fanless box, direct solar loading on an outdoor enclosure can push internal ambient past 60 °C. Apply these field mitigations:
Solar Radiation Shielding (Double-Roof):
Never let sunlight hit the primary equipment box directly.
Add a top/side sacrificial sunshield spaced 25 mm to 50 mm off the main cabinet. The air gap allows natural convection to carry away solar radiation heat before it soaks the enclosure.
Thermal Coupling / Passive Heat Conductance:
Closed-Loop Heat Dissipation vs. Vents:
Drop unsealed, slotted louvers—in high humidity, day/night thermal cycling draws humid air inside, causing dew-point condensation.
If passive dissipation through the cabinet walls isn’t enough, use a sealed air-to-air heat exchanger or a thermostatic push-pull sealed vent system equipped with serviceable G3/G4 particulate/moisture filters.
Jetson Power Mode Tuning:
Run the Jetson Orin Nano in the 15W 4-core or 10W power mode (nvpmodel -m 1 or nvpmodel -m 2) rather than uncapped MAXN.
YOLO26n is lightweight; capping CPU clock limits and lowering peak GPU frequencies drops operating $\Delta T$ by 8 °C to 12 °C with negligible inference latency penalty.
Industrial-Grade NVMe SSD:
Better fit, better performance and Longer Lifespan. Learning curve is Medium to Expert. 
This is a great project but would require the BEST hardware to pull it off, This IS THAT! 
HTH
GL PJ
In SoFlo we deal with Roof Heat, I’m talking cook your eggs to Over-Medium in 2 minutes easy. SO breakfast is on Them. 
