They had to figure out how to fix it without incurring the original problem the break was meant to solve. They patched the kernel to fix a potential security bug with memory allocation buffer overrun. In doing so they crippled the primary AI application people purchase the device for. Now they have to integrate the new solution into mainline without requiring the users to downgrade, perform a complex kernel patch, or run in CPU slug mode.
1 Like
well summarised.
Some sort of gesture to the buyers would be appropriate even after the fix finally arrives.
If possible a memory upgrade option would be appreciated. Somebody already tried this themselves by desoldering and switching the 8Gb memory modules for 16Gb (and flashing a modified firmware)
An official path to do this would unlock the full power of this board!
Thank you for putting the instructions in a step-by-step way. I was able to do this and get the Ollama to work without needing to reflash the jetson.
1 Like
Super helpful!
1 Like
Hi,
We need more time for the r35 changes.
Will let you know once it is ready.
Thanks.
1 Like
Absolute Legend, wasn’t on my list of things to learn (patching and compiling a Kernel) but this was the perfect How-to for it.
Was running r36.4.7 and this worked perfectly to llama3 running in a container. Thanks much!
1 Like
Hi, all
Please ignore this message if you are using JetPack6/r36.4.7.
For the user who uses JetPack 5/r35.6.3, please find below the fix information.
Thanks.