Search results

Thanks a lot: Almost there now. One error while compiling when using your patch file contents: applying patch '../../patches/kernel/0008-amd-no-flr.patch' patching file drivers/pci/quirks.c patch: **** malformed patch at line 4: DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr);

@qwerty0033 can you please paste me the contents of your 0008 patch file?

I am getting closer, I just got confused, and have the patch file on my system. can you please paste me what you ended up with after the changes you mention? I can double check manufacuter and device id's later. This is what I have now in /usr/src/pve-kernel/patches/kernel/0008-amd-no-flr.patch...

finally I found the inner strength to try and then :( kernel root@pve:/usr/src/pve-kernel/patches# ls kernel root@pve:/usr/src/pve-kernel/patches# cd kernal -bash: cd: kernal: No such file or directory root@pve:/usr/src/pve-kernel/patches# cd kernel root@pve:/usr/src/pve-kernel/patches/kernel#...

wow thank you sooo much for holding my hand. Please allow some time in order for me to try it. I will for sure to get back to this.

@seji, or anyone? perhaps there is a guide for the uninitiated on how to patch the kernel? all i find are guides that assume prior knowledge

I needed to patch the kernel because of pci flr issues when passing through onboard sound on amd64, ryzen zen2 system. did not work out.

thanks for the info @seji however this results in no more netowrking and a boot time that takes ages. a start job is running for udev wait for complete device initialization a start job is running for helper to synchronize boot up for ifupdown originally all went smooth with: root@pve:~#...

Ok I went in head first and dpkg -i .deb files. Luckily that created a restor point because I got stuck and now am back again. I am relieved. Is there anyway to create such restore points before making quite drastic changes?

When doing an update using the GUI I noticed that when I reboot the host I get presented an option at early boot to select the boot environment. (e.g. use the current updated kernel or use the kernel from before the update) is there any way to create such a restore point without actually...

@seji once again thanks for your contribution. I am going in with your .deb files and have already downloaded them. can you please share a total noob guide for how to actually 'install' those .deb files? I found some guides that assume some prior knowledge that I don't have yet.

@EricD Welcome back. Thanks for sharing. Earlier in this thread I also had success with the l8st kernel. It's great that it is now part of pve 6.2

I liked your solution even though not fully understanding it yet ;) I figured that it seems to work otherwise there would have been questions already. I am going to dive in and see how far I get. I think a procedure like this should be a standard feature as it is sooooo convenient.

That is great news! I am sorry I could not really analyze your scenario as I am kind of a newcomer to this field. So I am happy that I at least could give you some directions.

not sure if applicable in your scenario. but with a different mobo setup that had iommo group crippled I used pcie_acs_override=downstream and thing got better https://pve.proxmox.com/wiki/Pci_passthrough

I passed through all SATA controllers yes. I did not tinker with mappings. Not sure we can even do that actually.

I used wires to short pins in the memory bank. I have an example photo as attachment, but obivously the wires were in the bank with the memory in it while testing. On the photo they are in an empty bank just to make it more easy to see. Does this change anything for you regarding the...

Thank you MasterPhi. Can you please explain more regarding the breaking of the CPU? I don't mind sharing on level1tech. You are free to do so. Just let me know where you did it so I can read the responses. Or would you like me to share on level1tech? if so then can you please advice on what...

I am happy to report that I was able to assess that ECC error reporting (and also correction (but this is not something the software is responsible for)) is working. The method I used was to use the inner wires of some electrical cable and stick it in a memory bank with 8GB ECC UDIMM (bought to...

thanks so much for this information. I am not sure though I dare to go the custom compilation route.