Table of contents
Requires motherboard bios to support skipping graphics card self-test
Solve the motherboard bios problem and then continue to solve the system problem
antecedent
A few days ago, I installed a Proxmox ve as a server 7*24 boot
But after turning the system, the graphics card is no longer needed
Plus the reason for its power consumption (my gtx650 usually consumes about 10w without load)
I'm thinking about pulling out the graphics card, I can use xshell for ssh connection
Then I pulled it out, turned it on, and sure enough!
Unable to connect to background and ssh
I glanced at the router and found that there was no network address for him at all.
reason
Later, I searched for a similar problem in the post bar, and found that it was because the pcie slot of the graphics card was pulled out, which caused the network port number to change.
Since pve is based on the debian system of linux, and the slogan of the udev version in the current system is divided according to the location (very cheating)
The name has changed, but the configuration file of your network is the configuration file of the previous network card name, naturally there is no network
So there was such a strange scene
Solution
The solution to this problem has also been found. It is relatively simple, that is, to bind the network port number and the mac address of the network port together.
First check the ip address of the network port name (be careful not to regard it as the virtual address of the network card)
ip a
Pay attention to check the name of the network card corresponding to the mac address of your local ip (there may be two network cards with the same mac address, I am, both can connect to ssh; one of them is problematic, if it is set to him, you create The virtual machine cannot be opened and cannot be connected to the network. The problem is not big, just try all of them, usually it starts with enp)
Next open the configuration folder
cd /etc/udev/rules.d
View Files
lsIf you find other files, first use ls -l+ file name to view
If it is found that he is a link file and points to /dev/null (like below)
lrwxrwxrwx 1 root root 9 Jul 18 21:49 60-bridge-network-interface.rules -> /dev/null
that can delete him
rm <文件名>Next create a file (must be this <number>-bridge-network-interface.rules file name and format)
nano 50-bridge-network-interface.rulesThen write the following text
SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="mac地址", NAME="你的网卡名称"
reboot
rebootIn this way, the ip address is bound to the name of the network card.
Notice
This blog only solves the problem of confusing the name of the network card caused by the change of pcie in linux (the blogger is sure that this problem has been solved, but the blogger has not successfully opened Kun, so I suspect that there are other problems such as bios and grub question)
After setting, you need to change the halt on to No Errors in the bios option, that is, no matter what error there is, turn it on first.
There may be other options such as x99 in South China in Advanced->PCI Subsystem Settings->Onboard VGA
shut him down
Don't know about other bios
There is another saying that bios has passed but grub has not passed. If there is a solution, I will update it at the bottom as soon as possible
The blogger’s motherboard x99hd3 does not support skipping the self-test (or can’t find it), so the final verification cannot be done (if this method is useless, remember to contact me to delete the blog)