![]() One of the first messages is "unknown video mode 317, press ENTER to see video modes available, SPACE to continue. Howver installation failed at the same point (I think). Having seen quite some warnings and the message cdrom not found I waited for my external (USB attached) CD/DVD player to arrive. Installation ended with "\nInstallation aborted" message at some point. Since I had no CD/DVD player yet installed I created a bootable USB key from the Proxmox install ISO. The new brick is rather impressive and should serve me for a lot of years to come: i7-980X CPU on Asus Sabertooth X58 mobo w 24 GB of DDR3 (3-channel) memory. I built myself a brand new brick for virtualizing my home network and getting rid of all my old hardware. If vim is not working and you get “Command not found”, try nano instead.As an unexperienced Linux user and absolute newbie to ProxMox I failed installing ProxMox VE 1.8 right from the start. Note, this will not persist through a reboot as this is done within the “live image”, so don’t reboot in this process until Proxmox has completely installed.ĮDIT: It seems vim may no longer be part of the installer in 6.3. This should start the Proxmox installer and everything else is smooth sailing. ![]() ![]() $ vim /etc/X11/nf # update Driver "amdgpu"-> "fbdev" <-be sure to get all instances in the case of a multi-head card which tripped me up initially. What to do? Run the following: $ chmod 1777 /tmp ![]() While digging through the logs I noticed that the installer was failing trying to start the X server for the GUI. The bad is that the Proxmox installer fails and dumps out to a command prompt after obtaining a DHCP lease. Fortunately, it has a Ryzen 4700U and should smoke my Pi4 and older Intel 4200U Proxmox box. I was lucky enough to get my hands on one of the new Asus PN50 Ryzen 7 boxes yesterday. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |