jan icon indicating copy to clipboard operation
jan copied to clipboard

[AVX] Nitro exited with code: null

Open zdavatz opened this issue 3 months ago • 15 comments

  1. Download the Appimage for Linux with Kernel 6.8.0
  2. Start the App
  3. ./jan-linux-x86_64-0.4.10.AppImage
  4. Download Mistral Instruct 7B Q4
  5. Do a query
  6. Then on my Gentoo Linux Box I get:
Update for version 0.4.10 is not available (latest version: 0.4.10, downgrade is disallowed).
2024-04-03T08:18:50.832Z [NITRO]::CPU informations - 4
2024-04-03T08:18:50.833Z [NITRO]::Debug: Request to kill Nitro
2024-04-03T08:18:50.883Z [NITRO]::Debug: Nitro process is terminated
2024-04-03T08:18:50.884Z [NITRO]::Debug: Spawning Nitro subprocess...
2024-04-03T08:18:50.885Z [NITRO]::Debug: Spawn nitro at path: /home/zeno/jan/extensions/@janhq/inference-nitro-extension/dist/bin/linux-cpu/nitro, and args: 1,127.0.0.1,3928
2024-04-03T08:18:50.893Z [NITRO]::Debug: Nitro exited with code: null
2024-04-03T08:18:50.893Z [NITRO]::Error: child process exited with code null
(node:13858) UnhandledPromiseRejectionWarning: Error: timeout
    at Timeout.timeoutFunc (/home/zeno/jan/extensions/@janhq/inference-nitro-extension/dist/node/index.cjs.js:3074:25)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
(Use `jan --trace-warnings ...` to show where the warning was created)
(node:13858) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
2024-04-03T08:20:30.068Z [NITRO]::CPU informations - 4
2024-04-03T08:20:30.069Z [NITRO]::Debug: Request to kill Nitro
2024-04-03T08:20:30.072Z [NITRO]::Debug: Nitro process is terminated
2024-04-03T08:20:30.073Z [NITRO]::Debug: Spawning Nitro subprocess...
2024-04-03T08:20:30.073Z [NITRO]::Debug: Spawn nitro at path: /home/zeno/jan/extensions/@janhq/inference-nitro-extension/dist/bin/linux-cpu/nitro, and args: 1,127.0.0.1,3928
2024-04-03T08:20:30.083Z [NITRO]::Debug: Nitro exited with code: null
2024-04-03T08:20:30.083Z [NITRO]::Error: child process exited with code null
Error: Loader Message: setup_loader_term_phys_devs:  Failed to detect any valid GPUs in the current config
Warning: vkEnumeratePhysicalDevices
    at GatherPhysicalDevices (../../third_party/dawn/src/dawn/native/vulkan/VulkanInfo.cpp:144)
    at Initialize (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:388)
    at Create (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:301)
    at operator() (../../third_party/dawn/src/dawn/native/vulkan/BackendVk.cpp:556)

(node:13858) UnhandledPromiseRejectionWarning: Error: timeout
    at Timeout.timeoutFunc (/home/zeno/jan/extensions/@janhq/inference-nitro-extension/dist/node/index.cjs.js:3074:25)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
(node:13858) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
  1. Do I need a GPU to run this?
  2. This is disabled latest-screenshot

zdavatz avatar Apr 03 '24 08:04 zdavatz