So I guess the first question is if the nVidia binaries are in place? This would show via “sha1sum -c /etc/nv_tegra_release”. The second part may be more difficult. This is to determine which ABI the server shown in yast has…you may need to do some research.
If this ABI exceeds 15, you may need to install a “downgraded” version…some prior version from the recent past using ABI 15. Along with that the XInput would also need downgrade (having the server work but no mouse/keyboard possible wouldn’t be much fun). This ABI version may be what makes or breaks your X11 install. Once a server is in place with support of the 15 ABI, check again the “sha1sum -c /etc/nv_tegra_release”.
From what I can tell the ABI version for the xorg version on YAST is 10. Thats what its showing in the changlog anyway. and as far as the binaries, yes they are in place properly. the system functions just fine in every other aspect except having a GUI.
Below is the output when i use that command. Thoughts?
linux:/home/eclipse # sha1sum -c /etc/nv_tegra_release
/usr/lib/xorg/modules/drivers/nvidia_drv.so: OK
sha1sum: /usr/lib/xorg/modules/extensions/libglx.so: No such file or directory
/usr/lib/xorg/modules/extensions/libglx.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_video.so: No such file o r directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_video.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvwinsys.so: No such file or dire ctory
/usr/lib/arm-linux-gnueabihf/tegra/libnvwinsys.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvomx.so: No such file or directo ry
/usr/lib/arm-linux-gnueabihf/tegra/libnvomx.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvtestio.so: No such file or dire ctory
/usr/lib/arm-linux-gnueabihf/tegra/libnvtestio.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmm.so: No such file or director y
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvodm_imager.so: No such file or directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvodm_imager.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvtestresults.so: No such file or directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvtestresults.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvapputil.so: No such file or dir ectory
/usr/lib/arm-linux-gnueabihf/tegra/libnvapputil.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmm_utils.so: No such file or di rectory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_utils.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvrm_graphics.so: No such file or directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvrm_graphics.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvos.so: No such file or director y
/usr/lib/arm-linux-gnueabihf/tegra/libnvos.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_image.so: No such file o r directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_image.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvddk_vic.so: No such file or dir ectory
/usr/lib/arm-linux-gnueabihf/tegra/libnvddk_vic.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvomxilclient.so: No such file or directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvomxilclient.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libglx.so: No such file or directory
/usr/lib/arm-linux-gnueabihf/tegra/libglx.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmm_camera_v3.so: No such file o r directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_camera_v3.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmm_parser.so: No such file or d irectory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_parser.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_audio.so: No such file o r directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_audio.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvodm_query.so: No such file or d irectory
/usr/lib/arm-linux-gnueabihf/tegra/libnvodm_query.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_utils.so: No such file o r directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_utils.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvtnr.so: No such file or directo ry
/usr/lib/arm-linux-gnueabihf/tegra/libnvtnr.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmm_contentpipe.so: No such file or directory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_contentpipe.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libjpeg.so: No such file or director y
/usr/lib/arm-linux-gnueabihf/tegra/libjpeg.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvddk_2d_v2.so: No such file or d irectory
/usr/lib/arm-linux-gnueabihf/tegra/libnvddk_2d_v2.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvdc.so: No such file or director y
/usr/lib/arm-linux-gnueabihf/tegra/libnvdc.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libtegrav4l2.so: No such file or dir ectory
/usr/lib/arm-linux-gnueabihf/tegra/libtegrav4l2.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite.so: No such file or dire ctory
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvparser.so: No such file or dire ctory
/usr/lib/arm-linux-gnueabihf/tegra/libnvparser.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvsm.so: No such file or director y
/usr/lib/arm-linux-gnueabihf/tegra/libnvsm.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvavp.so: No such file or directo ry
/usr/lib/arm-linux-gnueabihf/tegra/libnvavp.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvtvmr.so: No such file or direct ory
/usr/lib/arm-linux-gnueabihf/tegra/libnvtvmr.so: FAILED open or read
sha1sum: /usr/lib/arm-linux-gnueabihf/tegra/libnvrm.so: No such file or director y
/usr/lib/arm-linux-gnueabihf/tegra/libnvrm.so: FAILED open or read
sha1sum: WARNING: 33 listed files could not be read
linux:/home/eclipse # cd /usr/lib/arm-linux-gnueabihf
linux:/usr/lib/arm-linux-gnueabihf # ll
total 28
drwxr-xr-x 2 root root 4096 Nov 27 00:42 gstreamer-0.10
drwxr-xr-x 2 root root 4096 Nov 27 00:42 gstreamer-1.0
-rwxrwxr-x 1 root root 17844 Nov 27 00:42 libgstnvegl-1.0.so.0
linux:/usr/lib/arm-linux-gnueabihf #
Many of the files say “FAILED”. Most of the nVidia support files are completely gone or replaced. These need to be put back in place…you don’t need to re-flash, just unpack the binaries from “/” with root/sudo permissions. The packaging system won’t know that some of these are already there and to not overwrite them, so I’d just leave the whole binary tarball set of files in “/” (I’m not near a Jetson at the moment, I think there was an L4T installer “nvidia”-something folder with the binary file tarball in it…the name should be pretty obvious once you see it). Each time you add or update software you should check for “FAILED” in that sha1sum command and put the binary support files back in place if anything is “FAILED”.
FYI, I don’t actually know if the ABI version 10 is supported. That version is incredibly old, but maybe it will work. File and package version numbers do not necessarily correspond to ABI, so I’d try to find out for certain what ABI is involved.
so would it be the jetpack or the actual tegra file ( that ends in .tbz2 ) ? I want to make sure i have the right one there, im assuming its the tegra one, and hopefully it puts the right files in the right locations when i tar it from /. Thanks!
There seems to be a forum bug…“Add Reply” does not exist on page 2, I’m using the one from page 1. And I can’t quote. I’m not sure if this post will show up or not, and if it does, where it might appear. Logging out and back in does not help.
I do not use JetPack, I don’t know how it is arranged…I cannot use JetPack because it requires Ubuntu packaging and I’m using Fedora.
However, JetPack should have installed the flash software in a “Linux_for_Tegra” subdirectory. Within this is the “apply_binaries.sh” script, which finds the tar archive in “nv_tegra/nvidia_drivers.tbz2”. Under TK1 this needs to be the R21.4 version…for a TX1, this needs to be the R23.1 version. Place this file in “/” of your Jetson, and run something like:
cd /
sudo -s
bunzip2 < nvidia_drivers.tbz2 | tar xv
linux:/usr/lib # sha1sum -c /etc/nv_tegra_release
/usr/lib/xorg/modules/drivers/nvidia_drv.so: OK
/usr/lib/xorg/modules/extensions/libglx.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_video.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvwinsys.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvomx.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvtestio.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvodm_imager.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvtestresults.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvapputil.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_utils.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvrm_graphics.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvos.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_image.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvddk_vic.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvomxilclient.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libglx.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_camera_v3.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_parser.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_audio.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvodm_query.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite_utils.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvtnr.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmm_contentpipe.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libjpeg.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvddk_2d_v2.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvdc.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libtegrav4l2.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvmmlite.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvparser.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvsm.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvavp.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvtvmr.so: OK
/usr/lib/arm-linux-gnueabihf/tegra/libnvrm.so: OK
linux:/usr/lib #
So now that we have them in the proper location should I attempt to install the xorg-x11-server? Thanks in advance youre quite helpful!
so i went ahead and did an install of xorg-x11-server, xfce4-session, xfce4-terminal and lightdm, and its the same thing black sreen with a white cursor ( non flashing ) in the upper left corner. So were still in the same boat, but i think i can at least get into the SSH and now begin working on it without having to totally reflash the system, so again the popular question, any ideas? lol
I’m dealing with a forum bug…if I’m logged in, the second page truncates before I can see the end. I’m replying from page 1. I’m reading from a second browser which isn’t logged in. Same result in both linux and windows, firefox and IE. So something about login is making it so this thread is corrupted to me…I may end up missing something, but here’s my attempt to answer.
The tar file should unpack to correct directories if it is in “/” when you unpack it with root authority. Once you install other software related to X11, you must re-extract those files again. If you install the missing files and then X11, it’s out of order…you just lost your files again. So install X11, then unpack the tarball again.
well the libglx.so was a “FAILED” so i copied the original and overwrote it, and now it shows up as OK, however, same thing, black screen and that stupid non blinking cursor. seems im getting no where with this thing. I’m pretty much at a loss. is there a way i could setup SSH or something to the jetson and get someone to login and help get it fixed?
With the nVidia files in place, it might be time to now start viewing /var/log/Xorg.0.log.
FYI, the X11 server when running solo (no window manager) has nothing but the big “X” cursor, and typically gray background. No window manager equals big “X” cursor. One could substitute a custom application for a desktop manager and run a single app without windowing. So I wonder if your X11 is working correctly but the desktop is not installed. Double check desktop environment/window manager packages, e.g., KDE and KDM. If you install anything new, double check that the nVidia files are still in place.
I don’t know of a good way to log in remotely via ssh to fix the situation, you almost have to be sitting there to see what the local connected screen looks like. If things go bad, the serial console is usually the choice. The scientific name for that procedure is “poking around” :P
Incidentally, /etc/X11/ usually has the configuration files for telling window managers and display managers and such to run. It really sounds like the SuSE variant you’re using never had graphical display neatly packaged in for use on ARM, or eat least on Jetson. So some added desktop software and double check of the config files might make further progress.
the “cursor” im speaking of is not an X, but a normal “dos prompt” style cursor that doesnt blink.
that /var/log/xorg.0.log file… non existant.
as far as the openSuse version, - Jetson/Porting openSUSE - eLinux.org (its showing that people use the lightDM over top of XFCE4. ) since nothing is working, im looking at other releases of the NVidia drivers. I’m assuming thats probably not the issue, nor is the openSUSE. but something has to give, im going to continute working on this through the weekend, should it not work, come monday im just gonna toss the TK1 idea out the window, it should NOT be this complicated to get a GUI going.
Before i start flashing things all over the place trying to get this working… Do you have any ideas on what we can do from this point to attempt to get this working, aside from going back to the standard OS/GUI which i cant stand. Sorry just very frustrated at this point. There has to be a way, possibly screen sharing? I have teamviewer and can SSH into the jetson FROM my PC with TV on it. Thanks in advance.
I personally just don’t know enough about the SuSE distribution or X11 packaging. I strongly suspect there is some kind of binary ABI mismatch, or possibly just a need to start with some additional frame buffer type support in a kernel feature. There tends to be a progression of supporting software-only based frame buffers, and later adding in hardware acceleration.
One thing which seems to be in common to most all modern graphics display is EDID, the wire on the monitor used to query the monitor. Before making any final decision, would you describe cabling to the monitor, including connector types and adapters? Also, though you may need to install other packages, what is the output of these commands:
I reflashed the board with the newest openSUSE Arm for Jetson package which is 13.2 ( instead of 13.1 ), I just booted it up, yast worked perfectly, network seems to be working as well, same as before.
For the monitor I am using HDMI ( the only output for the TK1 board ), going into a 24" Vizio HD TV, ( that i know works with HDMI from a PCB)
I just verified the network as working bu running “zypper in sudo” so I have sudo installed again. I am wondering if the new OS version will make a difference ( i doubt it but will try. )
So as of right now the system is up and stable with the NVidia Drivers R21.4 and openSUSE 13.2 ARM version, I tried startX with no success. So I am going to go ahead and try running the installer for xorg. maybe this new version will work. who knows at this point.
Seems to be the same issue. I am at a loss at this point.
On Ubuntu, packages required are “edid-decode” and “read-edid”. I think those packages also require more than the default repository. On SuSE, I don’t know what the package name is. Fedora does not have those specific commands so far as I know, but has instead “monitor-edid”…along with slightly different naming, like “monitor-get-edid” instead of “get-edid”. What is the package search command for SuSE? Look for “edid”.
yeah ive tried just about everything i can think of at this point with no prevail, so i dont know what to think at this time. There has to be some way to get a UI working on this board.