So I have been trying to install Proxmox on an old PC and have been having awful luck with it, as I can't even get the web UI to load at all, it just times out when I try to enter (https://xxx.xxx.0.xxx:8006/) into my browser. I have tried Chrome, Edge, and Friefox, a different computer, and have tried setting the device to a static IP address. The thing is, the MAC address tied to my old computer has not been showing up as online in my router's admin page, so it seems like my proxmox machine is never properly connecting to the network, but it's acting like it is, it installs totally fine and shows the web url after the reboot, but that url just never works. Any help would be appreciated.
[SOLVED] Having trouble setting up Proxmox on my network
- Thread starter PlusNine
- Start date
What is the output of
cat /etc/network/interfaces and ip a, when you login to the Proxmox host console (using a physical keyboard and display)?so cat /etc/network/interfaces returns:
and ip a returns:
Code:
auto lo
iface lo inet loopback
iface enp2s0 inet manual
auto vmbr0
iface vmbr0 inet static
address xxx.xxx.0.xxx/24
gateway xxx.xxx.0.1
bridge-ports enp2s0
bridge-stp off
bridge-fd 0and ip a returns:
Code:
1: lo: <LOOPBACK, UP, LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp2s0: <NO-CARRIER, BROADCAST, MULTICAST, UP> mtu 1500 qdisc mq master vmbr0 state DOWN group default qlen 1000
link/ether <Device's MAC address> brd ff:ff:ff:ff:ff:ff
3: vmbr0: <NO-CARRIER, BROADCAST, MULTICAST, UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000
link/ether <Device's MAC address> brd ff:ff:ff:ff:ff:ff
inet 192.168.0.101/24 scope global vmbr0
valid_lft forever preferred_lft foreverI'm assuming you used some non-routable local subnet, which really is no security risk to show.
NO-CARRIER usually means that there is no working cable plugged into the Ethernet port. Can you try with another cable?So I tried with a couple different cables, including the one I use to connect my current desktop and they all still failed. Even ip a returned the same output. It seems like the network interface chip on my old MOBO is fried. Would getting a network interface card help with this issue?
What is the output
lspci, which might show what type of controller it is. Maybe it needs a known work-around. Is the network controller enabled in the motherboard BIOS?Probably, if you don't get one that does not work with Linux.
So
lspci returns this for the ethernet controller: Qualcomm Atheros Killer E220x Gigabit Ethernet Controller (rev 10). If there is a workaround for this I would. And I can't seem to find any network controller options in my BIOS, so I can only assume it's enabled
Looks like you're not the only one. On the internet, it seem to work with Linux for some people but not for others.
I uh... don't know what to make of this. So I have to get a networking card? The user in the thread said after a gurb-install and an update, it started working? How does that actually work? Do I have to use a grub install just to get this working with Proxmox?
It was probably a newer kernel version with a newer driver included. Looks like it is currently not working on Proxmox.Getting a known to work well network add-in PCIe card might be the easiest route to go.
Does ASRock support Linux at all?
In the mean time you could try disabling IOMMU and above 4G decoding to see if that makes the E220x work.
Is there anything in
journalctl -b 0 (scroll with the arrow keys) that might indicate what the problem is and what a work-around might be?I have no idea how to disable IOMMU and above 4G decoding. However, when running
journalctl -b 0, I did find [Firmware Bug]: TSC_DEADLINE disabled due to Errata; please update microcode to version: 0x22 (or later) Any idea how to update this?
Those are common motherboard BIOS settings (press DEL or F2 or something when the system is doing its POST before booting Proxmox). I don't know what motherboard you have but you can probably download a manual.
Totally unrelated, but a BIOS upgrade might fix it, as well as installing microcode for your system, which is recommended.
So I took a stab at installing new microcode as you mentioned, but now I've run into a new issue: I can't install the update because iucode, the main tool is used to update the microcode, cannot be installed. When I initially tried installing iucode, it responded with an error saying that gcc was not installed. I found this unusual but I had a go at installing gcc on the machine, and that won't work. That responds with it's own error, saying it can't modify the locales, and honestly I'm stumped as to what to do. Do I have any realistic options left?
I don't have such problems when I run
apt install intel-microcode or apt install amd64-microcode. But you might have to enable the Debian non-free firmware repositories first.Well the thing is, this device can't connect to the internet, so I have to build the iucode tools on the device locally. After running
apt install intel-microcode on my machine, it told me that the microcode is the newest version, and that I should run apt --fix-broken install. Doing this however, will remove the microcode package. Should I continue with this, or just get a different MOBO for the proxmox tower?
I don't think you should install a package named microcode or iucode. Just install intel-microcode on an Intel system. Maybe I provided you with a unfortunate link? Maybe a motherboard BIOS update would have been much easier. Or first get a known-to-work cheap network PCIe card and just reinstall cleanly?
The iucode thing is the tool to install the microcode. If you 'apt install intel-microcode' it will be brought in as a dependency. In the case where you have no network it might be best to get that working first. I doubt the microcode is keeping the NIC from working.
Well I honestly don't know what's going on anymore. I got a BIOS update from ASRock's website, which specifically mentions a microcode fix, I flash the new BIOS, and even after a reinstall my Proxmox machine still cannot connect. I think I need a different MOBO just to get this working at all