Good Day Everyone,
Very novice linux\proxmox user here.
Running proxmox ve, very recent kernal but not positive which, on a consumer mobo (Gigabyte Gaming K7, Ryzen 9 5900X, Nvidia 1060)
I changed my network configuration incorrectly (dumb) and lost access to the proxmox webui. Whoops. Accidentally included the Proxmox management port on a bond, neglected to set any IPs on that bond.
As this is not the first time I did this, I connected a monitor to my GPU as my CPU has no display out, and reach the below on boot. It never drops to a shell, or single-user mode. Keystrokes do not appear on screen as does not a cursor. No, enter does not bring up a log on. No ProxMox welcome banner, either.
Adding nomodeset 3 to the end of the kernal grub line (linux?) results in the same for the latest kernel, I'm pretty sure I tried the same for the older kernel and rescue modes, but I'm not positive I tried. I'm pretty sure the rescue modes display a larger debug log, that doesn't indicate the below ss but fail to reach single-user mode, too.
This is in a homelab, and all the VMs and LXCs seem to boot.
ProxMox VE can't be reached by hostname or IP. Doesn't appear Proxmox is even asking for an IP from the router (PFSense.)
Only thing I can think of that would stop the console from displaying on host is\was blacklisting the GPU drivers in proxmox for passthrough.
I'm away from the homelab right now, but upon return, I aim to boot a linux rescue USB or ubuntu on the hardware, try to browse to the /etc/interfaces and host file, and adjust the management interface that way, if even possible. I'm also going to try an AMD GPU to see if that allows boot into console.
I'm posting to ask for any advice in the interim. Thanks!
Very novice linux\proxmox user here.
Running proxmox ve, very recent kernal but not positive which, on a consumer mobo (Gigabyte Gaming K7, Ryzen 9 5900X, Nvidia 1060)
I changed my network configuration incorrectly (dumb) and lost access to the proxmox webui. Whoops. Accidentally included the Proxmox management port on a bond, neglected to set any IPs on that bond.
As this is not the first time I did this, I connected a monitor to my GPU as my CPU has no display out, and reach the below on boot. It never drops to a shell, or single-user mode. Keystrokes do not appear on screen as does not a cursor. No, enter does not bring up a log on. No ProxMox welcome banner, either.
Adding nomodeset 3 to the end of the kernal grub line (linux?) results in the same for the latest kernel, I'm pretty sure I tried the same for the older kernel and rescue modes, but I'm not positive I tried. I'm pretty sure the rescue modes display a larger debug log, that doesn't indicate the below ss but fail to reach single-user mode, too.
This is in a homelab, and all the VMs and LXCs seem to boot.
ProxMox VE can't be reached by hostname or IP. Doesn't appear Proxmox is even asking for an IP from the router (PFSense.)
Only thing I can think of that would stop the console from displaying on host is\was blacklisting the GPU drivers in proxmox for passthrough.
I'm away from the homelab right now, but upon return, I aim to boot a linux rescue USB or ubuntu on the hardware, try to browse to the /etc/interfaces and host file, and adjust the management interface that way, if even possible. I'm also going to try an AMD GPU to see if that allows boot into console.
I'm posting to ask for any advice in the interim. Thanks!