Leaderboard

I made the Proxmox experimental branch with kernel 5.8 available on my personal github https://github.com/mdjabirov/pve-edge-kernel/blob/linux-5.8/README.md I also added instructions on how to build it yourself. If someone has enough diskspace (10-20G for the compiler cache) on his/her Proxmox host, and would like to go through the exercise I'd appreciate it, so I can see if it works and fix any omissions in the steps described. I will not publish official releases. Any official .deb files should be downloaded from Proxmox or Fabian's repo. If you choose to try it, you should download and build it yourself. I can add instructions on how to add patches (such as the AMD reset patch) if anyone is interested.

Questa guida trae ispirazione da dortania (credits a loro), ho pensato di farla interattiva e tradotta in italiano. Sono curioso di avere un vostro feedback su come vi trovate Tutorial.mp4 Comandi allegati qui in questo file di testo qui sotto comandi_terminale.txt.zip

Nice you just build the kernel :). You can actually build it now every time Linus Torvalds updates it. I will post instructions on that too - it's a simple git command. Let me fix the missing dpkg-dev add-in in step 1. Thanks for the help.

I haven't had time to do much research on this topic, but here a few things that I came across: 1st check: https://www.kernel.org/doc/Documentation/vfio.txt In particular this section: This device is behind a PCIe-to-PCI bridge [4]_, therefore we also need to add device 0000:06:0d.1 to the group following the same procedure as above. Device 0000:00:1e.0 is a bridge that does not currently have a host driver, therefore it's not required to bind this device to the vfio-pci driver (vfio-pci does not currently support PCI bridges). When I did lspci and checked my TB group id, and then did ls -l /sys/bus/pci/devices/[id]/iommu_group/devices the structure was very similar to what's described there. Essentially the 'leaf' devices are behind a PCI bridge. I don't have the Proxmox console handy now but I will paste the result of this later tonight. I don't think I am saying anything new here - still worth trying and see what happens. I think it would help to reach out to Alex Williamson who is the maintainer of VFIO in the linux kernel https://www.linkedin.com/in/alexwilliamson He might provide helpful tips, or simply tells us not to waste our time as it is not supported. Or this could prompt someone on the Linux kernel team to look into emulating PCI bridge devices. At any rate, he seemed helpful on a reddit board where a user tried to achieve a simpler goal - passthrough a leaf PCIE video card through thunderbolt to his laptop. As you can see this already turned out to be non-trivial at the time You can read the full thread here and see that he provided input:

Ricomincerei da zero con installazione pulita @dandi98

So after a full 1 1/2 days of basically redoing everything from scratch, using VM Assistant (thanks fabiosun and genki84) over the Proxmox installer (latest BS), and running into almost every problem I had originally thought I solved, I now have BS4(?) running and booting purely on the NVME drive with no virtual disk, or EFI from proxmox. Everything is running stable, except the WiFi from the Broadcom card, which I realized that it's actually not the card itself, but Big Sur. Apparently Big Sur bricked WiFi for a ton of BC cards. Post Discussing Fixing the Kext Fix. It also involves accessing the root volume, getting CSR disabled, and a lot more fun. I did all the steps for the fix, but it's still not working currently for me, but I'm using ethernet from the ethernet port, so I'm not stressed. All iServices work as well. I personally would not recommend BS currently - it seems like with the new method of how they are handling root disk access, there's likely going to be a lot of future changes that may or may not break things. My ethernet also kept reverting to a self-assigned nic, so it set things back a bit. One of the early major roadblocks was actually taking a working VM that I had thought I had everything working through console, and then when passing back the GPU, it would not boot and was constantly stuck on [PCIE Passthrough] on the bootloader, and ultimately (half a day later), fixed it by having to blacklist amdgpu again - it would not boot past that no matter what I tried, and blacklisting was the last resort. Currently not passing through the full USB port, but just USB devices (keyboard/mouse). Will likely pass it through later. 03:00 is GPU, 4a:00 is NVME, 4b:00 is Broadcom PCIe, 44:00 is Aq Ethernet vm.conf args: -device isa-applesmc,osk="**" -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -cpu host,+invtsc,vendor=GenuineIntel balloon: 0 bios: ovmf boot: c bootdisk: virtio0 cores: 64 cpu: host hookscript: local:snippets/reset-gpu.pl hostpci0: 03:00,pcie=1,x-vga=1,romfile=vegafrontier.rom hostpci1: 4a:00.0 hostpci2: 4b:00.0,pcie=1 hostpci3: 44:00.0,pcie=1 localtime: 1 machine: q35 memory: 49152 name: mac-x numa: 1 ostype: other scsihw: virtio-scsi-pci smbios1: sockets: 1 usb0: host=0461:4dd7 usb1: host=1d57:5280 usb2: host=05ac:828d usb3: host=0a5c:4500 vga: none vmgenid blacklist.conf blacklist snd_hda_codec_hdmi blacklist snd_hda_intel blacklist snd_hda_codec blacklist snd_hda_core # blacklist radeon blacklist amdgpu blacklist btusb blacklist snd-usb-audio blacklist bcma blacklist xhci_hcd

vedo che piuttosto che sistemare la tua build, preferisci patchare files di sistema

sembra che Big Fart ora sia disponibile in beta pubblica per tutti

Figurati! Sono stato un anno con un sistema inutilizzabile perché non sapevo come risolvere, ora non posso che aiutare chi è nello stesso problema 🙂

In questo momento la radeon VII e' impegnata su un'altra macchine e non riesco a fare i test. La domanda che ho fatto nasce dal fatto che ho provato e confermo che non funziona.

a little update: V23 flashed firmware allows to see my Titan ridge on windows in all PCIE slot I put it (tested on 4 and 2) Linux does not see it in slot 2 Only in slot 4 I can see and pass two pcidevice (TB and USB) with the help of @Gengik84I am trying a new way to proceed DSDT way 🙂

Aggiornamento della prima settimana di agosto: data astrale 302409.32128045824 , siamo riusciti a effettuare il boot e l'installazione pulita di BigSur beta 3 direttamente sull'NVMe Sabrent sull'hack in firma e oggetto della guida. data la presunta incompatibilità con il suddetto NVMe (errori e kp ionvme21), si è optato per l'utilizzo del fix Acidanthera. attualmente stiamo navigando verso nuovi orizzonti. i passi da seguire saranno ancora lunghi. probabilmente non vedremo il nuovo mondo prima di diverso tempo. in questo momento stiamo aggiornando i sistemi. lunga vita e prosperità.