The board itself (hardware-wise) would be relatively good, however, the BIOS is really bad. And no support from the "manufacturer" at all.
I have that same board and contacted them with a question. No answer at all.
So, you basically have two...
What you did is most likely, that you just pulled out the rug (=SATA controller device) from under the Proxmox's feet (=Kernel).
So in other words:
If you want to pass-through a device, it should be made absolutely clear, that nothing else is...
Setup a Windows Remote Desktop connection (RDP), so that you can have a look at the VM, in the "non-working" cases. Debugging is everything.
Often it is also necessary to extract the Legacy Video BIOS (ROM-file) from the graphics card and pass...
Works perfectly fine. I have some systems setup like that, due to details in the use case, that made this appear to be the best choice. I am talking about home setups, as this is not considered to be best practice.
Most likely a bad idea, as the...
The key you are looking for probably is "GRUB_DISABLE_OS_PROBER". Googling that string will tell you details.
And who would've thought, that Github isn't Grub?!? ;-)
Leute, ihr müsst schon uplink (hin vom Switch zum System) und downlink (vom Switch zu den eigentlichen ICs) unterscheiden.
Auf der Karte scheint ja ein Gen3 Packet-Switch zu sitzen...
Final idea for today, considering the board's age:
Did you already check the voltage level of the CMOS battery? The evil range somewhere between 0-2V is always a good explanation for "stupid" or "weird" stuff going on. If it's nothing else, that...
Don't get me wrong, but this should not be a very hard task.
So, the logical conclusion would be, that you either have defective hardware, or that you are doing something wrong.
You could also have a look at the output on the COM-header of your...
As I just re-read your posting, this seems like it might be helpful:
https://www.seeedstudio.com/blog/2019/12/11/rs232-vs-ttl-beginner-guide-to-serial-communication/
As you wrote about all those different, but most likely all TTL-level, USB to...
Run "dpkg -l |grep proxmox-kernel".
Look up the exact name of the kernel you want to remove.
Afterwards "apt --purge remove proxmox-kernel-[version]", where "[version]" matches the versioning name, that you previously looked up. Real easy.
If you want your Container to access the GPU resources, then all you actually do is allow the LXC access to certain files and directories (corresponding to actual hardware access) on the host system.
This has absolutely nothing to do with your...
The screenshot you posted is from PCI(e) initialization. There should be a lot of output before that.
So no, I doubt, that the kernel crashes "that fast". "0.34 seconds" (according to your screenshot) might sound early, but in terms of kernel...
According to the blockdiagram, that Supermicro provides, your UARTs are both coming directly from the Aspeed AST2400 BMC. Plus there seems to be a suspicious "Serial Mux" BIOS setting in the "IPMI" Submenu.
Might be, that both UARTs are...
Da ich professionell im Bereich Produktsupport für Hard- und Software unterwegs bin, kann ich dir folgendes sagen:
Problembeschreibungen (z.B. Betreffzeile einer Mail, oder in einem Ticketingsystem, etc.) im Stile deiner letzten Auswahlen...
@UdoB ist nicht sein erster Treffer bzgl. "Subject". Mich irritiert diese unprofessionelle Schreibart auch, zumal ich da vor einiger Zeit in einem anderen Thread von ihm eine sehr unprofessionelle Art und Ausdrucksweise gesehen habe, gegenüber...
I updated to 6.14.8 today, with my setup with an GTX 980Ti, passed-through to a Windows 10 VM. After the update, no more successful graphics pass-through. Reverted back to 6.14.5 and everything is back to working. Didn't have time for further...