-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Viseron on jetson, Darknet not recognizing cuda (v3.0.0b6) #759
Comments
Interesting, is the issue still present on 3.0.0b7? |
unfortunatly yes ( i have tried both gstreamer configuration an ffmpeg) on jetson nano: [s6-init] making user provided files available at /var/run/s6/etc...exited 0. |
Which Jetpack version are you running on? |
root@jetson:/usr/local/mesh_services/meshagent# sudo apt-cache show nvidia-jetpack Package: nvidia-jetpack Package: nvidia-jetpack Package: nvidia-jetpack |
What is t he output of |
eldadh@jetson:~$ dpkg-query --show nvidia-l4t-core |
Hmm, seems to match whats inside the container... Does the docker tag You might get some database version issues so its best to start fresh by either deleting the |
in b3 version, there was SQL issues: eldadh@jetson:~$ sudo docker logs viseron |
Right, forgot about that. |
|
unfortunately yes, [cont-init.d] executing container initialization scripts... |
i have a jetson nano and I was thinking of trying this. Did you ever get the native nvida acceleration running? |
I ran the latest beta ( [v3.0.0b6])
however it doesn't seem to recognize cuda on jetson nano
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 10-adduser: executing...
usermod: no changes
************************ UID/GID *************************
User uid: 1000
User gid: 1000
************************** Done **************************
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-gid-video-device: executing...
[cont-init.d] 20-gid-video-device: exited 0.
[cont-init.d] 30-edgetpu-permission: executing...
************** Setting EdgeTPU permissions ***************
Coral Vendor IDs:
"1a6e"
"18d1"
No EdgeTPU USB device was found
No EdgeTPU PCI device was found
************************** Done **************************
[cont-init.d] 30-edgetpu-permission: exited 0.
[cont-init.d] 40-set-env-vars: executing...
****** Checking for hardware acceleration platforms ******
OpenCL cannot be used
VA-API cannot be used
CUDA is available!
PostgreSQL major version: 10
PostgreSQL bin: /usr/lib/postgresql/10/bin
*********************** Done *****************************
[cont-init.d] 40-set-env-vars: exited 0.
[cont-init.d] 50-check-if-rpi: executing...
********** Checking if we are running on an RPi **********
Not running on any supported RPi
*********************** Done *****************************
[cont-init.d] 50-check-if-rpi: exited 0.
[cont-init.d] 55-check-if-jetson: executing...
****** Checking if we are running on a Jetson Board ******
Running on a Jetson Nano
*********************** Done *****************************
[cont-init.d] 55-check-if-jetson: exited 0.
[cont-init.d] 60-ffmpeg-path: executing...
****************** Getting FFmpeg path *******************
FFmpeg path: /usr/bin/ffmpeg
*********************** Done *****************************
[cont-init.d] 60-ffmpeg-path: exited 0.
[cont-init.d] 70-gstreamer-path: executing...
***************** Getting GStreamer path *****************
GStreamer path: /usr/bin/gst-launch-1.0
*********************** Done *****************************
[cont-init.d] 70-gstreamer-path: exited 0.
[cont-init.d] 80-postgres: executing...
***************** Preparing PostgreSQL *******************
Database has already been initialized.
*********************** Done *****************************
[cont-init.d] 80-postgres: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Starting PostgreSQL Server...
/var/run/postgresql:5432 - no response
Waiting for PostgreSQL Server to start...
2024-05-23 11:45:55.087 IDT [496] LOG: listening on IPv4 address "127.0.0.1", port 5432
2024-05-23 11:45:55.087 IDT [496] LOG: could not bind IPv6 address "::1": Cannot assign requested address
2024-05-23 11:45:55.087 IDT [496] HINT: Is another postmaster already running on port 5432? If not, wait a few seconds and retry.
2024-05-23 11:45:55.097 IDT [496] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-05-23 11:45:55.134 IDT [498] LOG: database system was interrupted; last known up at 2024-05-23 11:44:26 IDT
2024-05-23 11:45:55.189 IDT [498] LOG: database system was not properly shut down; automatic recovery in progress
2024-05-23 11:45:55.203 IDT [498] LOG: redo starts at 0/1694608
2024-05-23 11:45:55.203 IDT [498] LOG: invalid record length at 0/1694640: wanted 24, got 0
2024-05-23 11:45:55.203 IDT [498] LOG: redo done at 0/1694608
2024-05-23 11:45:55.253 IDT [496] LOG: database system is ready to accept connections
/var/run/postgresql:5432 - accepting connections
PostgreSQL Server has started!
[2024-05-23 11:45:58] [INFO ] [viseron.core] - -------------------------------------------
[2024-05-23 11:45:58] [INFO ] [viseron.core] - Initializing Viseron 3.0.0b6
[2024-05-23 11:45:58] [INFO ] [viseron.components] - Setting up component logger
[2024-05-23 11:45:58] [INFO ] [viseron.components] - Setup of component logger took 0.0 seconds
[2024-05-23 11:45:58] [INFO ] [viseron.components] - Setting up component data_stream
[2024-05-23 11:45:58] [DEBUG ] [viseron.components.data_stream] - ulimit -u output: unlimited
[2024-05-23 11:45:58] [DEBUG ] [viseron.components.data_stream] - Max threads: 999999
[2024-05-23 11:45:58] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(data_stream, initial daemon)> in the watchdog
[2024-05-23 11:45:58] [INFO ] [viseron.components] - Setup of component data_stream took 0.0 seconds
[2024-05-23 11:45:58] [INFO ] [viseron.components] - Setting up component storage
[2024-05-23 11:45:59] [INFO ] [alembic.runtime.migration] - Context impl PostgresqlImpl.
[2024-05-23 11:45:59] [INFO ] [alembic.runtime.migration] - Will assume transactional DDL.
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.storage] - Current database revision: 5f972755b320
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic event/domain/registered/camera, <bound method Storage._camera_registered of <viseron.components.storage.Storage object at 0x7f432c1f60>>
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/stopping, <bound method Storage._shutdown of <viseron.components.storage.Storage object at 0x7f432c1f60>>
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component storage took 0.2 seconds
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component webserver
[2024-05-23 11:45:59] [DEBUG ] [asyncio] - Using selector: EpollSelector
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method Webserver.stop of <Webserver(Tornado Webserver, initial daemon)>>
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component webserver took 0.0 seconds
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component ffmpeg
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component darknet
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component nvr
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setting up component mog2
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component nvr took 0.0 seconds
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component ffmpeg took 0.0 seconds
[2024-05-23 11:45:59] [INFO ] [viseron.components] - Setup of component mog2 took 0.0 seconds
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet] - Using native Darknet
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet] - Using weights /detectors/models/darknet/yolov7-tiny.weights and config /detectors/models/darknet/yolov7-tiny.cfg, 416x416
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet] - Creating Darknet data file /home/abc/darknet_data.data
[2024-05-23 11:45:59] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.input_thread, initial daemon)> in the watchdog
[2024-05-23 11:45:59] [DEBUG ] [viseron.watchdog] - Registering <RestartableThread(child_process.darknet.object_detector.output_thread, initial daemon)> in the watchdog
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.data_stream] - Subscribing to data topic viseron/signal/shutdown, <bound method ChildProcessWorker.stop of <viseron.components.darknet.DarknetNative object at 0x7f40ff8700>>
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] - Try to load cfg: /detectors/models/darknet/yolov7-tiny.cfg, weights: /detectors/models/darknet/yolov7-tiny.weights, clear = 0
viseron: get_gpu_compute_capability: Unknown error 1080216688
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA status Error: file: ./src/dark_cuda.c: func: get_gpu_compute_capability() line: 607
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] -
[2024-05-23 11:45:59] [DEBUG ] [viseron.components.darknet.libdarknet] - CUDA Error: no CUDA-capable device is detected
The text was updated successfully, but these errors were encountered: