In most older (maybe also newer?) DELL workstations and thin clients, for example: DELL Precision T5810 and DELL Wyse 3040, Debian is not able to boot after installation is completed.
This is because your workstation expects to boot from /EFI/BOOT/BOOTX64.EFI and it cannot find it.
There is a way to manually configure this in Setup page and point to the correct grubx64.efi
location, but for some reason it keeps trying to load from /EFI/BOOT/BOOTX64.EFI
.
The workaround provided here is basically renaming the grubx64.efi
into BOOTX64.EFI
and put it exactly where your workstation is expecting it.
Debian 12 Bookworm running on QEMU
Initially, it had qcow2 image size of 16GB, and this is how to double its size to 32GB:
host $ qemu-img resize diskimage.qcow2 +16G
Boot into Debian 12 and run fdisk with root privilege:
$ su
mirror of The Ultimate Beginner's Guide to GPU Passthrough (Proxmox, Windows 10) by /u/cjalas
>Welcome all, to the first installment of my Idiot Friendly tutorial series! I'll be guiding you through the process of configuring GPU Passthrough for your Proxmox Virtual Machine Guests. This guide is aimed at beginners to virtualization, particularly for Proxmox users. It is intended as an overall guide for passing through a GPU (or multiple GPUs) to your Virtual Machine(s). It is not intended as an all-exhaustive how-to guide; however, I will do my best to provide you with all the necessary resources and sources for the passthrough process, from start to finish. If something doesn't work properly, please check /r/Proxmox, /r/Homelab, /r/VFIO, or
- Soldering tools.
- 4x Female header jumper wires.
- 2x ST-Link v2 clone, one is used as a target and the other is used as a programmer.
- This guide has only been tested on ST-Link v2 clone with STM32F103C8T6 mounted on it.
- This guide was written and tested on macOS Sonoma. It should work on Linux, and also Windows under WSL/WSL2.
import matplotlib.pyplot as plt | |
import pandas as pd | |
import numpy as np | |
import subprocess | |
import re | |
all_colors = ['tab:blue', 'tab:orange', 'tab:green', 'tab:red', 'tab:purple', 'tab:brown', 'tab:pink', 'tab:gray', 'tab:olive', 'tab:cyan'] | |
plt.style.use('dark_background') | |
while True: |
import os | |
import shlex | |
import subprocess | |
# Redirect stderr and stdout of a subprocess to the python ones | |
def exec_cmd_with_output(cmd): | |
stdoutlines = [] | |
a_process = subprocess.Popen(shlex.split(cmd), stdout=subprocess.PIPE, stderr=subprocess.STDOUT) | |
for line in a_process.stdout: |
import glob | |
import time | |
import serial | |
import serial.threaded | |
import threading | |
import queue | |
# find alternative to define queue in user space, not here please | |
ATResponse = queue.Queue() |
#!/bin/bash | |
for sysdevpath in $(find /sys/bus/usb/devices/usb*/ -name dev); do | |
( | |
syspath="${sysdevpath%/dev}" | |
devname="$(udevadm info -q name -p $syspath)" | |
[[ "$devname" == "bus/"* ]] && exit | |
eval "$(udevadm info -q property --export -p $syspath)" | |
[[ -z "$ID_SERIAL" ]] && exit | |
echo "/dev/$devname - $ID_SERIAL" |
STLink Upgrade software is written in Java. As of the date this gist was initially written, it did not seem to work with Java natively installed on Apple M1. It requires x86_64 architecture execution under Rosetta.
This guide is about installing Java OpenJDK 17 support via Homebrew x86_64, on Apple M1 machine, in order to be able to run STLinkUpgrade.jar software by ST Microelectronics.
https://www.st.com/en/development-tools/stsw-link007.html
It is similar to installing Homebrew natively, with added arch --x86_64
prefix before the command line:
#!/bin/bash | |
set -e | |
# Prerequisite for Linux (Ubuntu-based): | |
# sudo apt-get install libncurses-dev flex libgmp3-dev libmpfr-dev bison libmpc-dev zlib1g-dev automake build-essential libtool patch tar wget | |
# If you have newer texinfo in the system, please uninstall or temporarily disable it during building this script: | |
# sudo apt-get purge texinfo | |
# Prerequisite for macOS (Homebrew): |