Ok so it’s not on the OS level. Might be a wake setting in the bios. Allow wake from USB might fix it.
Power management requires coordination between vendor firmware and linux, so new kernels may require updated vendor firmware. The ACPI open standard tells linux how to discover and configure the hardware. Some vendors support acpi_osi=linux on the kernel command line, others may need system-dependent entries.
From https://discussion.fedoraproject.org/t/issues-with-amd-gpu/135241
That’s all I got sorry. Good luck
What’s
sudo lsmod | grep amd && sudo dmesg | grep VGA
Return?
Also is KDE the standard DE for bazzite?
What kernel, distro, and gpu are you running?
At home I’m 100% linux. When I was freelance I built out pure linux systems for small businesses. Nextcloud, Odoo, Google Docs were what I deployed. I still support some clients and it’s only getting easier.
Absolutely this for windows. Linux however allowed crowdstrike to run without it being a boot time event. I administer a mixed environment. I worked 18 hours straight remediating that outage.
No. If the device was encrypted it had to be done locally. Laptops had to either be wiped and restored to backup or a sysadmin had to reset the machine locally with a local admin. There was no remote remediation possible unless the sysadmin gave the user a local admin account and password.
On Linux I was able to push the new file over the network and reboot the machine.
On windows companies were shipping laptops or restoring to backups.
That Crowd strike outage was pretty evident of how easy windows is to secure. Linux had the same failure but since admins are able to secure the OS in a more granular way and can update packages in situ without touching the registry, Linux users could still boot into their OS and patch the broken file. No such luck in Windows.
Windows is absolutely more difficult to secure than linux. I can restrict access down to the kernel level in linux. Windows has no such granularity
Are you backing up files from the FS or sre you backing up the snapshots? I had a corrupted journal from a power outage that borked my install. Could not get to the snapshots on boot. Booted into a live disk and recovered the snapshot that way. Would’ve taken hours to restore from a standard backup, however it was minutes restoring the snapshot.
If you’re not backing up BTRFS snapshots and just backing up files you’re better off just using ext4.
Do you rely on snapshotting and journaling? If so backup your snapshots.
The trains did not in fact run on time.
https://www.snopes.com/fact-check/loco-motive/
https://www.bloomberg.com/news/articles/2016-11-15/stop-saying-mussolini-made-the-trains-run-on-time
Considering it’s tailscale, one may want to have the service fail though as tailscale is sometimes not used for convenience but security concerns instead.
Delay the start of your containers with the tailscale dependency. Are you using required or depends_on in your docker-compose.yml
https://hatchjs.com/docker-compose-conditionally-start-service/
If you’re using kubernetes you can make the requirements at the pod level
https://stackoverflow.com/questions/69423932/container-initialization-order-in-pod-on-k8s
Edit: If using docker-compose.yml you can set a condition on a healthcheck
You can also specify a condition that must be met before the service is started. For example, the following configuration will start the web
service only if the db
service is healthy:
version: ‘3.7’
services:
web:
image: nginx
depends_on:
– db
condition: service_healthy
The service_healthy
condition checks the health of the db
service using the docker-compose ps
command. If the db
service is healthy, the web
service will be started.
Ah ok thanks for that.
I wonder if that includes steamdecks running steamos
To add to this, OP may want to put their thoughts down in writing. An email or memo or note or anything as long as it’s not a text or other personal non work form of communication.
Lay it all out, over write it, put too much detail and then pare it down to what OP believes to be acceptable. Have some copies of it.
Give them the written missive that boils down to “leave me alone” Make a note of the time and date.
If the co-worker keeps being a pest, go to HR, with a copy of the missive, and a note of the date it was given to co-worker so that co-worker cannot wheedle their way into making it about them trying to “help” OP.
Also, fuck every co-worker who pulls unprofessional shit like this. It’s abhorrent and borderline harassment.
In my humble opinion the point of self hosting an LLM is so that the data doesn’t leave your LAN.
Boot to live disk.
Edit vmconfig to not start at boot.
Mount vmdisk to live disk
Fix ssh