- Create directory
mkdir /etc/brave/policies/managed/
sudo mkdir -p /etc/brave/policies/managed/
- Create a file
GroupPolicy.json
Windows Registry Editor Version 5.00 | |
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\BraveSoftware] | |
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\BraveSoftware\Brave] | |
"BraveAIChatEnabled"=dword:00000000 | |
"BraveRewardsDisabled"=dword:00000001 | |
"BraveVPNDisabled"=dword:00000001 | |
"BraveWalletDisabled"=dword:00000001 |
This gist is almost entirely not unlike Derek Seaman's awesome blog:
Proxmox VE 8: Windows 11 vGPU (VT-d) Passthrough with Intel Alder Lake
As such please refer to that for pictures, here i will capture the command lines I used as i sequence the commands a little differently so it makes more logic to me.
This gists assumes you are not running ZFS and are not passing any other PCIE devices (as both of these can require addtional steps - see Derek's blog for more info)
This gist assumes you are not running proxmox in UEFI Secure boot - if you are please refer entirely to dereks blog.
aka what i did to get from nothing to done.
note: these are designed to be primarily a re-install guide for myself (writing things down helps me memorize the knowledge), as such don't take any of this on blind faith - some areas are well tested and the docs are very robust, some items, less so). YMMV
# This file contains pin mappings and other defaults for the Weefun/Weedo | |
# Tina2s based on the GD32F103. It won't work with the ATMega-bsed | |
# Tina/Tina wifi/monoprice cadet. | |
# The biggest issue with this printer is that the USB-serial CH340G's DTR pin | |
# is tied to reset with a 1k resistor - not a capacitor circuit like most. | |
# restart_method of 'tina2s' was added to make sure DTR is held high during | |
# normal operation | |
# Pins were found in https://github.com/weedo3d/TINA2Sfirmware and confirmed |
mkdir -p ~/.local/share/authy
cd ~/.local/share/authy
That will ensure you can check and test that a specific hotkey assignment is actually definately working independantly of the specific desired action. This is important because the desktop environment can also occupy pre-configured 'system keys' and if they are already being mapped to something other default system wide actions then (likely) will silently be ignored.
So being independant here from the subsequent specific desired target actions in some special app or whatever. Which themselves definately might have other own different issues or not behave correctly. And especially when being invoked from the compositor via this method (rather than a logged in user terminal etc.)
Install a working (and compiled) version of virt-viewer. You may view the homebrew package's upstream source on GitHub.
brew tap jeffreywildman/homebrew-virt-manager
brew install virt-viewer
Once that's installed should be able make a call remote-viewer
with a pve-spice.vv file downloaded from proxmox web interface
This step-by-step video tutorial will guide you through the procedure of forcing RGB color output on your M1 Mac.
Here is the direct link to the video tutorial: https://www.youtube.com/watch?v=Z1EqH3fd0V4
The video also has Closed Captions (Subtitles) that you can enable, to make it easier to follow if needed.
#!/usr/bin/env sh | |
set -e | |
NAMES="xterm,xterm-256color,screen,screen-256color,tmux,tmux-256color,xterm-ghostty,ghostty,Ghostty" | |
if [ "$(uname -s)" = "FreeBSD" ]; then | |
curl -o /tmp/termcap.src https://raw.githubusercontent.com/freebsd/freebsd-src/main/share/termcap/termcap | |
# Add ghostty termcap | |
cat << 'EOF' >> /tmp/termcap.src |