If i am trying to install something through ssh I am getting following error
E: dpkg was interrupted, you must manually run ‘sudo dpkg --configure -a’ to correct the problem.
If i am trying to install something through ssh I am getting following error
E: dpkg was interrupted, you must manually run ‘sudo dpkg --configure -a’ to correct the problem.
I have found something new now.
This line from xorg is saying that nvidia driver not able to get loaded.
Jan 28 21:28:24 rnd-nano /usr/lib/gdm3/gdm-x-session[5853]: (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
Jan 28 21:28:24 rnd-nano /usr/lib/gdm3/gdm-x-session[5853]: (EE) Failed to load /usr/lib/xorg/modules/drivers/nvidia_drv.so: libnvidia-rmapi-tegra.so.32.4.4: cannot open shared object file: No such file or directory
Jan 28 21:28:24 rnd-nano /usr/lib/gdm3/gdm-x-session[5853]: (II) UnloadModule: “nvidia”
Jan 28 21:28:24 rnd-nano /usr/lib/gdm3/gdm-x-session[5853]: (II) Unloading nvidia
Jan 28 21:28:24 rnd-nano /usr/lib/gdm3/gdm-x-session[5853]: (EE) Failed to load module “nvidia” (loader failed, 7)
Could you check if your device has this library (libnvidia-rmapi-tegra.so.32.4.4) under /usr/lib/aarch64-linux-gnu/tegra/?
Hey, the Jetson is booting successfully. Please explain me the issue, plus thanks for such a great support. and thanks for helping me to solve this problem in such a short period of time. thanks you once again. @WayneWWW
If possible do explain to me the cause. thank you so much
Hello,
What do you do to bring it back in the end?
I am assuming this did the trick. @WayneWWW
Actually, I guess something is still missing w.r.t my latest question here.
Could you check if your device has this library (libnvidia-rmapi-tegra.so.32.4.4) under /usr/lib/aarch64-linux-gnu/tegra/?
Your gdm3 now is not running with nvidia driver. It is probably using some other drivers from 3rdparty now.
I ran the following command in the directory you mentioned `ls |grep libnvidia-rmapi-tegra.so.32.4.4
and got the following output libnvidia-rmapi-tegra.so.32.4.4
this file is present
`
I saved my new syslog after a sucessful boot, shall i share that?
Could you directly share me the xorg.0.log now? This one should be sufficient for current debug. No need to check full syslog.
/var/log/Xorg.0.log.
sure, here’s the log filexorglog.txt (23.7 KB) @WayneWWW
Then do you have this file ?
/usr/lib/xorg/modules/drivers/nvidia_drv.so
yes, I do have that file.
Could you share me the result of below?
nvidia@nvidia-desktop:/etc/ld.so.conf.d$ sudo ldconfig -v -N |grep libnvidia
this is the output @WayneWWW
/sbin/ldconfig.real: Can’t stat /usr/local/lib/aarch64-linux-gnu: No such file or directory
/sbin/ldconfig.real: Can’t stat /usr/lib/tegra-egl: No such file or directory
/sbin/ldconfig.real: Path /usr/lib/aarch64-linux-gnu/tegra' given more than once /sbin/ldconfig.real: Path /lib/aarch64-linux-gnu’ given more than once
/sbin/ldconfig.real: Path `/usr/lib/aarch64-linux-gnu’ given more than once
/sbin/ldconfig.real: /lib/aarch64-linux-gnu/ld-2.27.so is the dynamic linker, ignoring
/sbin/ldconfig.real: Cannot stat /usr/lib/aarch64-linux-gnu/tegra/libnvidia-ptxjitcompiler.so.1: No such file or directory
libnvidia-container.so.0 → libnvidia-container.so.0.9.0
/sbin/ldconfig.real: Cannot stat /usr/lib/aarch64-linux-gnu/tegra/libnvidia-fatbinaryloader.so.440.18: No such file or directory
libnvidia-fatbinaryloader.so.440.18 → libnvidia-fatbinaryloader.so.32.4.4 (changed)
libnvidia-rmapi-tegra.so.32.4.4 → libnvidia-rmapi-tegra.so.32.4.4
libnvidia-egl-wayland.so.1 → libnvidia-egl-wayland.so
libnvidia-ptxjitcompiler.so.1 → libnvidia-ptxjitcompiler.so.32.4.4 (changed)
libnvidia-glvkspirv.so.32.4.4 → libnvidia-glvkspirv.so.32.4.4
libnvidia-glsi.so.32.4.4 → libnvidia-glsi.so.32.4.4
libnvidia-eglcore.so.32.4.4 → libnvidia-eglcore.so.32.4.4
libnvidia-glcore.so.32.4.4 → libnvidia-glcore.so.32.4.4
libnvidia-tls.so.32.4.4 → libnvidia-tls.so.32.4.4
libnvidia-rmapi-tegra.so.32.4.4 → libnvidia-rmapi-tegra.so.32.4.4
Hmm then I have no idea the why xorg not able to load this driver…
Maybe I need to delete my cache tomorrow and see what is going on… Anyway, thanks for providing the info so far.
will i be able to use deepstream in this state? plus why am i getting this when i am trying to install new package with sudo apt-get upgrade
E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to correct the problem.
Is there any file under /var/lib/dpkg/updates there?
If so, remove then and run apt-get update again.
this is the output of ls in the directory you mentioned
0000 0016 0032 0048 0064 0080 0096 0112 0128 0144 0160 0176 0192
0001 0017 0033 0049 0065 0081 0097 0113 0129 0145 0161 0177 0193
0002 0018 0034 0050 0066 0082 0098 0114 0130 0146 0162 0178 0194
0003 0019 0035 0051 0067 0083 0099 0115 0131 0147 0163 0179 0195
0004 0020 0036 0052 0068 0084 0100 0116 0132 0148 0164 0180 0196
0005 0021 0037 0053 0069 0085 0101 0117 0133 0149 0165 0181 tmp.i
0006 0022 0038 0054 0070 0086 0102 0118 0134 0150 0166 0182
0007 0023 0039 0055 0071 0087 0103 0119 0135 0151 0167 0183
0008 0024 0040 0056 0072 0088 0104 0120 0136 0152 0168 0184
0009 0025 0041 0057 0073 0089 0105 0121 0137 0153 0169 0185
0010 0026 0042 0058 0074 0090 0106 0122 0138 0154 0170 0186
0011 0027 0043 0059 0075 0091 0107 0123 0139 0155 0171 0187
0012 0028 0044 0060 0076 0092 0108 0124 0140 0156 0172 0188
0013 0029 0045 0061 0077 0093 0109 0125 0141 0157 0173 0189
0014 0030 0046 0062 0078 0094 0110 0126 0142 0158 0174 0190
0015 0031 0047 0063 0079 0095 0111 0127 0143 0159 0175 0191
shall I make the directory empty?
please rm them and run apt-get update again and see if dpkg is back to normal.
yes, its working now. what might be the cause?
plus will i be able to use deepstream?