jetson linux api on l4t 32.5.1. is different than docs
i am using l4t 32.5.1. when i look up the documentation in jetson linux api ([this](https://docs.nvidia.com/jetson/l4t-multimedia/group__ee__nvbuffering__group.html#ga4212a5f3d97ca8fda12c563d3609fbdb)), there are some differences in the files. such as there is no nvbuffertransformex in the nvbuf\_utils.h file in the system, but there is in the docs. i was just wondering where the problem is?
hi,

certain functions will be supported in next jetpack 4.6(r32.6) release. on jetpack 4.5.1, the supported functions are all in

/usr/src/jetson\_multimedia\_api/include/nvbuf\_utils.h
welcome to the forum! :slight\_smile:

[image] adamski234:

i had linux59 installed since the nvidia drivers were released. but after the update to rc4, the driver stopped working, and while trying to update/reinstall i found out that the driver was not in the unstable repos. not 440xx, not 450xx,… a couple of things to check:

(1) make sure your file realy exists

(2) your file path does not seem to be correct full path, should it be something like c://users/…

(3) you can also try a relative path, namely, copying your tiff file to the same directory as where you start your jupyter. then, use… i'm using ubuntu linux on my computer to type this, and i've been a regular linux user for the better part of the last 5 years.

i have to be honest, if by "making dvds" you mean video editing, you're going to be disappointed with what any version of linux has to offer. the tools linux has for the average home user's video editing needs are far, far behind what microsoft and apple give away for free with their systems. 

that aside, linux has excellent tools for the other needs you mentioned, and any major linux version you try is going to have all the major tools available. the key differences between linux versions (commonly called "distros" or "distributions") are generally found in default installed software, how you obtain new software (package management), and maybe hardware detection.

personally, i would recommend ubuntu. there are other excellent choices out there (fedora, suse), but i give ubuntu the nod for its excellent combination of default software, hardware support, and tools for installing new software. plus, it has a great community that will help you get started.

[additional info regarding video editing - 
i'm referring to software accessible to the average home user. i am not referring to professional, hollywood-level software. there is nothing available on linux that compares to apple's imovie or microsoft's windows movie maker, which is what i assume the asker is hoping for. if you know of such a program, i'd be happy to hear about it.] [@jbcousins92](/u/jbcousins92) i took a look at your repository and it looks like the course is expecting you to add the image in the \_includes/02-image.md file instead of the index.md file. can you try adding the same image there and letting the bot check it out? seek and tell are still required.

see here: <https://docs.lvgl.io/latest/en/html/overview/file-system.html#use-drivers-for-images> Hi feet.lost,

 

 

Thanks for reaching out! 

 

You can find version 2.1 of Edison's image in the following link: 

 

 <http://downloadmirror.intel.com/25028/eng/edison-image-ww25.5-15.zip> 

 

Let me know if you need any other version. 

-Peter.
 
 
 
 
 
 
 
 
 

[View solution in original post](/t5/Intel-Makers/Yocto-2-1-image-Download-Link/m-p/318752#M8587) looking around i think i found the answer myself.

there is are batch and script files in jabref/runtime/bin.

from those, the needed command line call can be derived. using the shipped jvm from inside the mentioned folder the call i looked for would be:

java --add-opens=javafx.controls/javafx.scen… Did you had ACS common installed in your AEM.

<https://adobe-consulting-services.github.io/acs-aem-commons/features/versioned-clientlibs/index.html>




[View solution in original post](/t5/adobe-experience-manager/aem-implementation-of-versioning-for-clientlibs-and-css/m-p/399346#M7116) my legendary persistence has paid off!

from looking at other dockerfiles in the repo, i discovered that the js files needed were not being copied to the image in the original dockerfile i used to base this on. no wonder it was looking everywhere and not finding anything!

:point\_right: copy ./build… thanks for your comment!

i definitely should’ve used mkshell, not sure why i wasn’t. it does seem to produce a different error:

make: entering directory '/build/source/doc/manual'

xsltproc --nonet --param section.autolabel 1 --param section.label.includes.component.label 1 --param html.stylesheet …