Differences

This shows you the differences between two versions of the page.

--- tech:linux [2026/06/14 23:53] – [Step 4: Manual Driver Override (Optional)] glong
+++ tech:linux [2026/06/15 18:53] (current) – glong
@@ Line 2: / Line 2: @@
 Ubunut 24.04
+[[:tech:Linux:AI Setup]] \\
 ====== Install all drivers needed for using V100 on Ubuntu 24.04 LTS ======
@@ Line 88: / Line 90: @@
 ====== GeForce 210 Driver Override Guide ======
-To configure a Driver Override for your GeForce 210, follow these steps to isolate the card from the proprietary NVIDIA driver and allow the open-source ''nouveau'' driver to manage the desktop display.
+We cannot fix this the ''nouveau'' driver cannot live with the V100 NVidia driver
-===== Step 1: Identify Device IDs =====
-Use ''lspci'' to find the exact Hardware IDs for your GeForce 210 at PCI address ''0000:01:00.0''.
-lspci -nn | grep -i "GeForce 210"
-Note the hexadecimal IDs (e.g., ''10de:0a65'').
-<code>
-root@test1:~# lspci -nn | grep "210"
-:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [GeForce 210] [10de:0a65] (rev a2)
-</code>
-===== Step 2: Isolate the Card with pci-stub =====
-Bind the device to ''pci-stub'' at boot time so the proprietary driver cannot claim it.
-* Open your GRUB configuration:
-sudo nano /etc/default/grub
-* Append ''pci-stub.ids='' with your hardware IDs to ''GRUB_CMDLINE_LINUX_DEFAULT'':
-GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci-stub.ids=10de:0a65"
-* Update GRUB:
-<code>
-root@test1:~# grep GRUB_CMDLINE_LINUX_DEFAULT  /etc/default/grub
-GRUB_CMDLINE_LINUX_DEFAULT="pci-stub.ids=10de:0a65"
-</code>
-sudo update-grub
-===== Step 3: Ensure nouveau is Loaded =====
-Ensure the open-source driver is not blacklisted and is forced to load at boot.
-* Remove any ''blacklist nouveau'' lines found in files within ''/etc/modprobe.d/''.
-* Add ''nouveau'' to your modules list:
-echo “nouveau” | sudo tee -a /etc/modules-load.d/modules.conf
-===== Step 4: Manual Driver Override (Optional) =====
-If the card does not bind correctly after rebooting, create a manual override script to forcibly unbind any driver and attach ''nouveau''.
-<code>
-#!/bin/bash
-## Unbind from any existing driver
-echo "0000:01:00.0" > /sys/bus/pci/devices/0000:01:00.0/driver/unbind
-## Force bind to nouveau
-echo "nouveau" > /sys/bus/pci/devices/0000:01:00.0/driver_override
-echo "0000:01:00.0" > /sys/bus/pci/drivers/nouveau/bind
-</code>
-===== Step 5: Verify Configuration =====
-Reboot your system and verify the kernel driver in use for each card.
-lspci -nnk | grep -A 3 "VGA|3D"
-The GeForce 210 should show ''Kernel driver in use: nouveau'', while your V100s should remain under the ''nvidia'' driver.
-------------------------------
-Does this DokuWiki format work for your documentation needs, or would you like to add more technical details about the V100 configuration as well?
@@ Line 251: / Line 197: @@
 ===== 2. Install the NVIDIA Container Toolkit =====
+https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html
 Add the official package repositories and install the toolkit:
@@ Line 258: / Line 205: @@
 curl -fsSL https://github.io | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg
-curl -s -L https://github.io | \
+curl -fsSL https://nvidia.github.io/libnvidia-container/gpgkey | sudo gpg --dearmor -o /usr/share/keyrings/nvidia-container-toolkit-keyring.gpg \
-sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \
+  && curl -s -L https://nvidia.github.io/libnvidia-container/stable/deb/nvidia-container-toolkit.list | \
-sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list
+    sed 's#deb https://#deb [signed-by=/usr/share/keyrings/nvidia-container-toolkit-keyring.gpg] https://#g' | \
+    sudo tee /etc/apt/sources.list.d/nvidia-container-toolkit.list
+sudo sed -i -e '/experimental/ s/^#//g' /etc/apt/sources.list.d/nvidia-container-toolkit.list
 # Update package list and install
 sudo apt-get update
-sudo apt-get install -y nvidia-container-toolkit
+export NVIDIA_CONTAINER_TOOLKIT_VERSION=1.19.1-1
+  sudo apt-get install -y \
+      nvidia-container-toolkit=${NVIDIA_CONTAINER_TOOLKIT_VERSION} \
+      nvidia-container-toolkit-base=${NVIDIA_CONTAINER_TOOLKIT_VERSION} \
+      libnvidia-container-tools=${NVIDIA_CONTAINER_TOOLKIT_VERSION} \
+      libnvidia-container1=${NVIDIA_CONTAINER_TOOLKIT_VERSION}
 </code>
@@ Line 284: / Line 241: @@
 <code>
-sudo docker run --rm --gpus all ubuntu nvidia-smi
+docker run --rm --runtime=nvidia --gpus all ubuntu nvidia-smi
 </code>
@@ Line 299: / Line 256: @@
 If you plan to deploy enterprise-grade AI workloads, you can also authenticate your Docker client to the NVIDIA NGC Container Registry using an API key. This gives you direct access to fine-tuned, GPU-optimized AI models and microservices.
+====== Installing LM Studio on Ubuntu 24.04 ======
+To install LM Studio on Ubuntu 24.04 LTS, you have two primary options: the **headless lms daemon** (ideal for servers, command-line usage, or API orchestration) or the **AppImage** (for the full graphical interface).
+---
+===== Option 1: Headless Daemon (lms) =====
+If you intend to use LM Studio for backend services, API hosting, or CI/CD, the ''lms'' daemon is the official, recommended approach.
+==== 1. Install the Daemon ====
+Run the following command in your terminal to download and execute the official installer:
+<code>
+curl -fsSL https://lmstudio.ai/install.sh | bash
+</code>
+==== 2. Usage ====
+Once the installation script completes, you can interact with the service directly using the ''lms'' CLI.
+To start the background service:
+<code>
+lms daemon up
+</code>
+**Note:** If you encounter an "Illegal instruction" error upon execution, ensure your system's ''libc'' and environment variables are fully updated. This can sometimes occur on bleeding-edge hardware configurations.
+---
+===== Option 2: Graphical AppImage (Full GUI) =====
+If you require the standard LM Studio desktop interface, you must download the AppImage. Note that Ubuntu 24.04 enforces strict sandboxing rules that require manual adjustment.
+==== 1. Download and Make Executable ====
+Download the latest Linux AppImage from the official LM Studio website, then give it execution permissions:
+<code>
+chmod +x LM_Studio-*.AppImage
+</code>
+==== 2. Extract and Configure Sandbox ====
+The application will likely fail to launch unless you fix the ''chrome-sandbox'' permissions. Extract the AppImage and update the owner permissions:
+<code>
+# Extract the AppImage
+./LM_Studio-*.AppImage --appimage-extract
+# Navigate to the extracted folder
+cd squashfs-root
+# Fix sandbox permissions
+sudo chown root:root chrome-sandbox
+sudo chmod 4755 chrome-sandbox
+</code>
+==== 3. Launch the Application ====
+You can now run the application from within the extracted directory:
+<code>
+./lm-studio
+</code>
+If you still encounter sandboxing issues and prefer to bypass it, you can launch with the ''--no-sandbox'' flag (use with caution):
+<code>
+./lm-studio --no-sandbox
+</code>
+---
+===== Troubleshooting & Performance =====
+^ Issue ^ Resolution ^
+| **Missing Dependencies** | Install base libraries: \\ <code>sudo apt install libatk1.0-0 libatk-bridge2.0-0 libcups2 libgdk-pixbuf2.0-0 libgtk-3-0 libpango-1.0-0 libcairo2 libxcomposite1 libxdamage1 libasound2t64 libatspi2.0-0</code> |
+| **Hardware Acceleration** | For integrated or discrete GPUs, ensure your drivers (such as ''intel-media-va-driver-non-free'' for Intel setups) are properly configured via ''mesa'' to ensure local model inference acceleration. |