Search results

In the meantime I spent about a week, in order to get a BIOS onto that board (X99I Server), that would make it behave, the way it should for my use case. That means enabled and working ECC and also enabled and working Serial Console Redirection. Although the physical connection for the latter...

Just out of curiosity: Are those non-working devices (each) directly attached to a CPU/chipset PCIe port, or is there a PCIe-switch involved, inbetween? Edit: Maybe provide a PCIe tree view (lspci -t -v).

Please have the respect and use english in an international and clearly english speaking forum like this. I mean we obviously can use google translate, but why should we have to? Besides that, according to the provided information, I guess we are talking about a Chinese X79 board of some kind...

Great work! Just one note: As you are passing through the whole graphics device, and your chosen motherboard still features a real COM-port, it might be a good idea to enable serial console on the Proxmox system. Just in case something ever goes wrong with the pass-through and you would like to...

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 choices: - Scrap that POS and get something more...

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 still working with it. And in your case it seems...

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 that directly to the passed-through PCIe device...

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 LMDE repositories might at some point get in 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 (https://www.asmedia.com.tw/product/012Yq70sX2zI9xN5/7c5YQ79xz8urEGr1). Der Switch kann mit max. x2, aber Gen3...

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 is. :-)

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 board with an oscilloscope, Maybe that could give...

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 UART adapters, the above might help your...

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 USB devices passed to VMs. So, you clearly are not...

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 boot, there is a lot going on before that. Do you...

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 exclusively provided for SOL-usage by default. And only...

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 diesbetreffend, würden bei mir und meinen Kollegen große...

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 analysis. Just know, that the latest update broke...

Wenn der i915 Treiber die PCI-ID deiner GPU nicht in seiner eigenen Liste der unterstützten IDs findet, dann lädt er natürlich auch nicht. Dass lspci den Namen dekodieren kann ist davon völlig unabhängig. Das ist nur der Abgleich der PCI-ID mit einer textuellen Liste und das Einsetzen des dort...