She/They
Everything runs 24/7, but now I am thinking about theoretical power saving modes. Besides any built in power saving whatever (a little clueless), you could always throttle the CPU more. Not sure if it would be worth it without testing with a power meter.
I had to change mine to mac address naming on my proxmox server after the second time the name changed due to a GPU or SSD being added. It was kind of like, so what, if an SSD dies suddenly or I have some issue with a device you are going to rename my fucking nic card again while I am trying to troubleshoot? Absolutely deranged.
Sorry, didn’t make it home until today and not sure if you get notifications on edits. You will need a monitor and keyboard hooked up to your server as you will not have ssh access until the network config is “fixed”. I would do the below with the GPU removed, so you know 100% that your networking config is correct before mucking about further.
Add a /etc/systemd/network/99-default.link with the below contents.
# SPDX-License-Identifier: MIT-0
#
# This config file is installed as part of systemd.
# It may be freely copied and edited (following the MIT No Attribution license).
#
# To make local modifications, one of the following methods may be used:
# 1. add a drop-in file that extends this file by creating the
# /etc/systemd/network/99-default.link.d/ directory and creating a
# new .conf file there.
# 2. copy this file into /etc/systemd/network or one of the other paths checked
# by systemd-udevd and edit it there.
# This file should not be edited in place, because it'll be overwritten on upgrades.
[Match]
OriginalName=*
[Link]
NamePolicy=mac
MACAddressPolicy=persistent
I forget if you have to reboot, but I am going to assume so. At this point, you can get the new name of your nic card and fix your network config.
ip link should list all of your nic devices, both real and virtual. Here is how mine looks like for reference, with the MAC obfuscated:1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enxAABBCCDDEEFF: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master vmbr0 state UP mode DEFAULT group default qlen 1000
link/ether AA:BB:CC:DD:EE:FF brd ff:ff:ff:ff:ff:ff
3: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DEFAULT group default qlen 1000
link/ether AA:BB:CC:DD:EE:FF brd ff:ff:ff:ff:ff:ff
You will need to edit your /etc/network/interfaces file so the correct card is used.
/etc/network/interfaces, just in case you mess something up.sudo vim /etc/network/interfaces (or whatever text editor makes you happy)
It will need to look something like below. I have to have DHCP turned on for mine, so your config likely uses static. Really all you need to do is change wherever it says enp yada yada to the enxAABBCCDDEEFF you identified above. source /etc/network/interfaces.d/*
auto lo
iface lo inet loopback
iface enxAABBCCDDEEFF inet manual
auto vmbr0
iface vmbr0 inet dhcp
#iface vmbr0 inet static
#address 192.168.5.100/20
#gateway 192.168.0.1
bridge-ports enxAABBCCDDEEFF
bridge-stp off
bridge-fd 0
sudo systemctl restart networking.serviceHopefully at this point you have nework access again. Check the below, do some ping tests, and if it doesn’t work, double check that you edited the interfaces file correctly.
sudo systemctl status networking.service will show you if anything went wrong and hopefully show that everything is working correctlyip -br addr show should show that the interface is up now.lo UNKNOWN 127.0.0.1/8 ::1/128
enxAABBCCDDEEFF UP
vmbr0 UP 192.168.5.100/20
At this point, if all is well, I would reboot anyways, just to make sure. If you add any GPUs, sata drives, other PCI device, disable/enable wifi/bt in the BIOS, or anything else that changes the PCI numbering, you don’t have to worry about your NIC changing.
I am not at home, but what I did was change the 99-default.link file. I found this from the two pages below. https://wiki.debian.org/NetworkInterfaceNames#CUSTOM_SCHEMES_USING_.LINK_FILES https://wiki.debian.org/NetworkInterfaceNames
Basically, by doing this, your nic cards will be forcibly named using the mac address:
#/etc/systemd/network/99-default.link
[Match]
OriginalName=*
[Link]
NamePolicy=mac
MACAddressPolicy=persistent
Afterwards, you will need to reboot and then update your network config file to use the correct names. I don’t ever change the network config with the GUI in proxmox as it has wrecked it too many times. I will update this reply again later with some more information on what to do.
I changed my settings to name nic cards by mac address instead of the enumeration as I got sick of the name changing when I would add/remove pci devices.
I lucked out. Success at last! Now I can continue to code furiously doing things I know how to do.
Been there. Done that. FML on searching for programming help some days. Versioning is a nightmare as the way you “used” to do things is no longer relevant and the rest of the results are some asshole saying it is a duplicate question that was answered 10 years ago…that is no longer fucking relevant!
Sorry. Yesterday sucked. I hope today is less frustration and more things working like they are supposed to.
I never considered old DOS games until now. Thank you!
I think I vaguely remember something about that, but I would be pretty upset if the keyboard navigation was unusable. It is almost as bad as the stupid mouse enabled BIOSs that never work. It doesn’t even work on the Dell laptop I have for work. The keyboard navigation is always extra special in those cases and involves a lot of button mashing to get to the correct thing, if I can figure it out at all.
I don’t use wired mice either and had to dig the old gaming mouse out recently so I could get to some menus on a new machine to pair the mouse. I have done the mouse pairing thing through console and it isn’t the best experience, especially if you are trying to figure out if things are working in the first place. For me, I could figure it out. For a new user, you are asking a lot.
Just give me an old school OS installer with simple menus, easy keyboard navigation, and the bare minimum guidance needed to not entirely fuck it up.
The best was on arch because I had no idea how to use pacman, which I needed to install man, when I needed how to use pacman. I will have to take a look at tldr. I mostly use Debian without a desktop environment, but have an Arch VM for gaming here and there. Works out.
I get confused every time I install a distro and man isn’t installed by default. I guess I get the bare minimum philosophy, but it throws me off every time. First thing I install is vim, man, git, and probably a couple other things I can’t remember right now.
I do like a decent man page that has examples for us dummies and I have found that they have improved a lot over the years.
laughs in evil PLC programmer A little forces enabled, a change here, and maybe just move this wire over there while I am at it…
deleted by creator
Day 1 was some awesome crazy dude on IRC teaching me how to compile the kernel from source, what options to choose, and then installing Slackware.
Thank you! I will give that a shot tomorrow and test it
I will take a look at it, but the fundamental issue is it screws with the iommu groups too and then I have to go fix that in proxmox. If I can at least guarantee a network connection then I can remote in and fix it in the event something goes really wrong.
It is only the nvme drives that do it. That damn PCI busses and iommu groups get renumbered every damn time I remove or add one. The SATA is safe though.
I have a hatred for the enp id thing as it isn’t any better for me. It changes on me every time I add/remove a hard drive or enable/disable the WiFi card in the BIOS. For someone who is building up a server and making changes to it, this becomes a real pain. What happens if a drive dies? Do I have to change the network config yet again over this?
Put your foot down, establish boundaries, and take a well deserved vacation with 0 communication to work while on it. Otherwise, I would start looking somewhere else. Your health is more important.
Edit: Also, hit them a few times with your Wabbajack for me.
I think this view is a little short sighted. I am glad that you don’t seem picky about your peripherals, but they are very important to others. As someone with a disability, if my mouse didn’t work on Linux, I wouldn’t even bother trying. I have spent a lot of money on peripherals and them working in Mac and Windows, but not Linux would be utterly rage inducing. It is irritating enough that I can’t adjust the dpi in Linux, but it is at least usable. I am still salty that every single pair of headphones I own use proprietary codecs that are not supported.
I absolutely do not blame anyone for not using Linux if their peripherals do not work. I get that it is the “fault” of proprietary drivers. Unfortunately, some devices are not popular enough or too difficult for someone in the Linux community to want to work on it. I don’t blame the community either. However, telling someone they can’t use their mouse or keyboard the way it was intended isn’t going to convince anyone to use Linux.
My point is, hardware costs money, is a physical device that you touch for hours at a time, and is configured to make your life easier. Tactile and ergonomic comfort is important. Macros, lights, and dpi settings are important to some people. For me, it is just dpi and smooth scrolling. Not everyone is happy with a cheap mouse and keyboard or wants to throw perfectly functional electronics in the bin.