for phy in $(find /sys/kernel -name 'phy[0-9]'); do | |
(cd $phy | |
l=1500 | |
h=5000 | |
echo 0 $l $h > "$phy/aql_txq_limit" | |
echo 1 $l $h > "$phy/aql_txq_limit" | |
echo 2 $l $h > "$phy/aql_txq_limit" | |
echo 3 $l $h > "$phy/aql_txq_limit" | |
echo 8000 > "$phy/aql_threshold" |
* Tension X,Y,Z axis: https://www.youtube.com/watch?v=MV-rbU5Fpfc | |
* Check that the extruder screw has the right tension: https://www.youtube.com/watch?v=8bACUeH6WDs | |
* Check that all screws are tightened | |
* Level the X axis, use two glue sticks on both sides of print bed to determine if the X axis is leveled: https://www.youtube.com/watch?v=Cmwq9r5tePk | |
* Use the "paper test" to set the Z offset (run G1 Z0 F300 on the printer to position the hotend to the lowest position on the print bed) | |
* Use fine tuning to find the right Z offset | |
* Print the modified spool holder for added stability: https://www.thingiverse.com/thing:6631744 | |
* Print the Z axis gantry support for added stability: https://www.thingiverse.com/thing:6516352 | |
* Lubricate X,Y,Z axis with lithium grease | |
* Print first layer test. |
{ | |
config, | |
pkgs, | |
options, | |
... | |
}: let | |
hostname = "oatman-pc"; # to alllow per-machine config | |
in { | |
networking.hostName = hostname; |
Currently Marlin Version - 2.1.2.2
Warning
Marlin binaries are created from official Marlin pre configuration repository, use at your own risk. Review compilation badge for succesfully build!!!
Suggested to take the config files and compile yourself, compilation guide.
Tip
From the next list of brand/printers/configurations:
- the first part shows the complilation process status, if you see passing the compilation was ok... if you see failing the compilation had issues
# Cura V3KE Thumbnail creator | |
# Kolio ([email protected]) | |
# | |
# This only works with Cura 5.0+ | |
import base64 | |
from UM.Logger import Logger | |
from cura.Snapshot import Snapshot | |
from PyQt6.QtCore import QByteArray, QIODevice, QBuffer |
Getting 802.11r Fast Transition working with WPA(2)-Enterprise is quite painful. There is information on the forums, but things have changed quite a bit during the last few years. These are notes mostly for my own benefit.
Tricky bits as of OpenWRT 23.05 (in Luci "WLAN roaming" tab of wireless network settings):
- NAS Id should be set to something unique, like the name of the AP.
- Mobility domain defaults to a sane value. Leave it empty.
- Reassociation deadline's default of 1000 is bad. Apparently Cisco uses 20000 here, setting that appears to be helpful.
- FT Protocol "Over the air" is the good setting.
If you're using WPA2-PSK, check "Generate PMK locally" and you're done. Save&apply and it should just work.
version: "3.9" | |
volumes: | |
postgres: | |
services: | |
postgres: | |
image: postgres | |
restart: unless-stopped | |
healthcheck: |
Just thought I'd put together some detail on deploying Tailscale using Docker and Portainer. These bits-and-pieces are available elsewhere, but not together, so hopefully this will save someone a bit of time if you'd like to add Tailscale to an existing Docker install:
Here's my annotated recommended docker-compose, to use with Portainer-Stacks. Note that I'm not using a pre-made Auth Key. I started that way, but realized it was very easy to simply check the Portainer log for the tailscaled container once the stack is running. In that log you'll see the standard Auth link that you can use to authorize the container. This way you don't need to create a key in advance, or create a reusable key that introduces a security risk:
version: '3.9'
services:
tailscale:
image: tailscale/tailscale
container_name: tailscaled