Search results

Wenn dein Linux Kernel noch mechanisch arbeitet, dann würde das einiges erklären. :cool: Jetzt ernsthaft und zum Thema: Falls deine NUC keine eingebaute EFI-Shell mehr besitzt besogst du dir ein passenden X64-Binary z.B. hier: https://github.com/pbatard/UEFI-Shell/releases . In dem Fall dann...

Zeit für ein Support-Ticket bei Asus. Im Gegensatz zu uns werden die dafür bezahlt. Das sieht nämlich aktuell irgendwie nicht Proxmox-spezifisch aus.

Wenn der Controller wirklich aus dem PCI-Listing verschwindet, dann hast du höchstwahrscheinlich kein Problem mit dem Linux Kernel. Edit: BIOS- oder Hardware-Thematik klingen da schon viel realistischer.

Definiere mal "NIC vorhanden"! Eventuell führt das Einbauen der 2. NVMe einfach nur zu einer Verschiebung der Kennung des Netzwerkcontrollers (enpXsX). Das hat dann nichts damit zu tun, dass dieser nicht mehr funktionieren würde, sondern ist vielmehr ein Konfiguratonsproblem.

Why did you just create a completely new thread, for the exactly same topic? Do you think, that creating just thread after thread will magically solve your problem?

Just FYI, for the quirk to apply you would have to build a test Linux Kernel for your machine, with the PCI ID of you controller in question, added to the list of devices, that the "quirk_no_bus_reset" should be applied to. To my knowledge, there is no other/obvious way to test it. Simply a...

So, directly attached to a PCH-port then, in this case. Did you "unbind" the devices from the "ahci" driver, before loading your VM(s)? This could also be an issue. Edit: PCIe reset issues are not that uncommon. Maybe you need to add a "quirk" entry to the PCI subsystem for this to work...

Please re-read what I wrote. Did I say he should add the COM-port to the Windows VM? Th buzz-word is "serial console redirection" of the Linux Kernel messages from the Proxmox host. In case something does not work as intended, at some point, this can be really helpful.

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...