June 30, 20206 yr 26 minutes ago, ich777 said: Great, can you share what you did only to give me a little bit of insight (since I'm not having any new AMD hardware)? Yes, you find a button in my Plugin and also on in the CA APP at my Docker containers. Do you know why user patch is not working? I use this two. It's like the docker don't use it. 60369a4f8d61bacd437adab0518581afb90bea24..0d14f06cd6657ba3446a5eb780672da487b068e7.patch 0d14f06cd6657ba3446a5eb780672da487b068e7..5727043c73fdfe04597971b5f3f4850d879c1f4f.patch
June 30, 20206 yr Author 3 minutes ago, rachid596 said: Do you know why user patch is not working? I use this two. It's like the docker don't use it. 60369a4f8d61bacd437adab0518581afb90bea24..0d14f06cd6657ba3446a5eb780672da487b068e7.patch 2.12 kB · 0 downloads 0d14f06cd6657ba3446a5eb780672da487b068e7..5727043c73fdfe04597971b5f3f4850d879c1f4f.patch 2.83 kB · 0 downloads I will look into it and correct it if there is a problem Will let you know but please give me a few days...
June 30, 20206 yr No problem. You have time. I do it manually now [emoji23][emoji23][emoji23].Have a good day Envoyé de mon HD1913 en utilisant Tapatalk
June 30, 20206 yr Author 15 minutes ago, rachid596 said: No problem. You have time. I do it manually now . Have a good day Envoyé de mon HD1913 en utilisant Tapatalk The patch files are read... I see this if I use your two files in the log: patching file drivers/pci/quirks.c Hunk #1 FAILED at 5133. Hunk #2 FAILED at 5143. 2 out of 2 hunks FAILED -- saving rejects to file drivers/pci/quirks.c.rej patching file drivers/pci/quirks.c The rej file shows that these section can't be patched: --- drivers/pci/quirks.c +++ drivers/pci/quirks.c @@ -5133,6 +5133,7 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x443, quirk_intel_qat_vf_cap); * FLR may cause the following to devices to hang: * * AMD Starship/Matisse HD Audio Controller 0x1487 + * AMD Starship USB 3.0 Host Controller 0x148c * AMD Matisse USB 3.0 Host Controller 0x149c * Intel 82579LM Gigabit Ethernet Controller 0x1502 * Intel 82579V Gigabit Ethernet Controller 0x1503 @@ -5143,6 +5144,7 @@ static void quirk_no_flr(struct pci_dev *dev) dev->dev_flags |= PCI_DEV_FLAGS_NO_FLR_RESET; } DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_no_flr); +DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_no_flr); DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x149c, quirk_no_flr); DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr); DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_no_flr);
June 30, 20206 yr OK Thank you. I will do it manually now. It's easy [emoji16]Envoyé de mon HD1913 en utilisant Tapatalk
June 30, 20206 yr The patch files are read... I see this if I use your two files in the log:patching file drivers/pci/quirks.cHunk #1 FAILED at 5133.Hunk #2 FAILED at 5143.2 out of 2 hunks FAILED -- saving rejects to file drivers/pci/quirks.c.rejpatching file drivers/pci/quirks.c The rej file shows that these section can't be patched:--- drivers/pci/quirks.c+++ drivers/pci/quirks.c@@ -5133,6 +5133,7 @@ DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x443, quirk_intel_qat_vf_cap); * FLR may cause the following to devices to hang: * * AMD Starship/Matisse HD Audio Controller 0x1487+ * AMD Starship USB 3.0 Host Controller 0x148c * AMD Matisse USB 3.0 Host Controller 0x149c * Intel 82579LM Gigabit Ethernet Controller 0x1502 * Intel 82579V Gigabit Ethernet Controller 0x1503@@ -5143,6 +5144,7 @@ static void quirk_no_flr(struct pci_dev *dev) dev->dev_flags |= PCI_DEV_FLAGS_NO_FLR_RESET;}DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x1487, quirk_no_flr);+DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x148c, quirk_no_flr);DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_AMD, 0x149c, quirk_no_flr);DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1502, quirk_no_flr);DECLARE_PCI_FIXUP_EARLY(PCI_VENDOR_ID_INTEL, 0x1503, quirk_no_flr); How do you access to the full log ? My chrome browser hang and i have to close it and ré open it. Envoyé de mon HD1913 en utilisant Tapatalk
June 30, 20206 yr Author 2 minutes ago, rachid596 said: How do you access to the full log ? My chrome browser hang and i have to close it and ré open it. Envoyé de mon HD1913 en utilisant Tapatalk I do this completely differently... But you can do that by enabling this option in the template: Or you can let the window open and after the build finished the browser windows should recover and you can scroll through the full log (in my case with Firefox). And the last way is to open up a terminal (wether it's via Putty, the webconsole or any other SSH connection to your server) and type in: 'docker attach NAMEOFYOUCONTAINER' (without quotes and replace NAMEOFYOURCONTAINER with the containername eg: Unraid-Kernel-Helper).
June 30, 20206 yr 50 minutes ago, ich777 said: I do this completely differently... But you can do that by enabling this option in the template: Or you can let the window open and after the build finished the browser windows should recover and you can scroll through the full log (in my case with Firefox). And the last way is to open up a terminal (wether it's via Putty, the webconsole or any other SSH connection to your server) and type in: 'docker attach NAMEOFYOUCONTAINER' (without quotes and replace NAMEOFYOURCONTAINER with the containername eg: Unraid-Kernel-Helper). OK, I can't understant, now patch file is working sending incremental file list ./ 60369a4f8d61bacd437adab0518581afb90bea24..0d14f06cd6657ba3446a5eb780672da487b068e7.patch sent 2,379 bytes received 38 bytes 4,834.00 bytes/sec total size is 2,168 speedup is 0.90 ---Applying patches to Kernel, please wait!--- patching file drivers/pci/quirks.c Hunk #1 succeeded at 3719 with fuzz 2 (offset -23 lines). Hunk #2 succeeded at 4877 with fuzz 1 (offset 288 lines). patching file drivers/ata/libata-core.c Hunk #1 succeeded at 2388 (offset 1 line). Hunk #2 succeeded at 2481 (offset 4 lines). Hunk #3 succeeded at 2534 (offset 4 lines). Hunk #4 succeeded at 2559 (offset 4 lines). Hunk #5 succeeded at 2655 (offset 5 lines). patching file drivers/scsi/hpsa.c Hunk #1 succeeded at 978 (offset 2 lines). patching file drivers/scsi/mvsas/mv_init.c Hunk #1 succeeded at 655 (offset -31 lines). patching file fs/reiserfs/resize.c patching file fs/reiserfs/super.c patching file arch/x86/kvm/x86.c Hunk #1 succeeded at 116 with fuzz 1 (offset 7 lines). patching file include/linux/blkdev.h Hunk #1 succeeded at 1165 with fuzz 2 (offset -159 lines). patching file drivers/pci/quirks.c Hunk #1 succeeded at 3564 (offset 173 lines). patching file include/linux/pci_ids.h Hunk #1 succeeded at 1797 (offset 13 lines). patching file lib/raid6/algos.c Hunk #1 succeeded at 28 with fuzz 2 (offset -5 lines). Hunk #2 succeeded at 234 (offset 9 lines). Hunk #3 succeeded at 319 (offset 15 lines). It's work with 6.8.9 and 6.9 In attachement the log file and patch file. 2020-06-30_18.34.43.log 60369a4f8d61bacd437adab0518581afb90bea24..0d14f06cd6657ba3446a5eb780672da487b068e7.patch
July 1, 20206 yr Big big thanks to ich777 for this container + instructions. Also big thanks to rachid596 for providing this AMD USB/Audio fix patch from reddit. Such a gamechanger. Love this community. Was able to build this in ~10min with a full core workout. The log showed successful patch of AMD function level reset fix ./ quirk_no_flr.patch sent 2,302 bytes received 38 bytes 4,680.00 bytes/sec total size is 2,168 speedup is 0.93 ---Applying patches to Kernel, please wait!--- patching file drivers/pci/quirks.c Hunk #1 succeeded at 3719 with fuzz 2 (offset -23 lines). Hunk #2 succeeded at 4877 with fuzz 1 (offset 288 lines). patching file drivers/ata/libata-core.c Hunk #1 succeeded at 2388 (offset 1 line). Hunk #2 succeeded at 2481 (offset 4 lines). Hunk #3 succeeded at 2534 (offset 4 lines). Hunk #4 succeeded at 2559 (offset 4 lines). Hunk #5 succeeded at 2655 (offset 5 lines). patching file drivers/scsi/hpsa.c Hunk #1 succeeded at 978 (offset 2 lines). patching file drivers/scsi/mvsas/mv_init.c Hunk #1 succeeded at 655 (offset -31 lines). patching file fs/reiserfs/resize.c patching file fs/reiserfs/super.c patching file arch/x86/kvm/x86.c Hunk #1 succeeded at 116 with fuzz 1 (offset 7 lines). patching file include/linux/blkdev.h Hunk #1 succeeded at 1165 with fuzz 2 (offset -159 lines). patching file drivers/pci/quirks.c Hunk #1 succeeded at 3564 (offset 173 lines). patching file include/linux/pci_ids.h Hunk #1 succeeded at 1797 (offset 13 lines). patching file lib/raid6/algos.c Hunk #1 succeeded at 28 with fuzz 2 (offset -5 lines). Hunk #2 succeeded at 234 (offset 9 lines). Hunk #3 succeeded at 319 (offset 15 lines). patching file drivers/pci/quirks.c Hunk #1 succeeded at 5238 (offset 109 lines). And now I'm rocking and rolling in plex with nvidia and got my Win10 VM with USB hub + audio passthrough working. Life is good. 2020-07-01_05.29.38.log quirk_no_flr.patch
July 1, 20206 yr Author 22 minutes ago, bigbangus said: Big big thanks to ich777 for this container + instructions. Also big thanks to rachid596 for providing this AMD USB/Audio fix patch from reddit. Such a gamechanger. Love this community. Was able to build this in ~10min with a full core workout. The log showed successful patch of AMD function level reset fix And now I'm rocking and rolling in plex with nvidia and got my Win10 VM with USB hub + audio passthrough working. Life is good. 2020-07-01_05.29.38.log 361.07 kB · 0 downloads quirk_no_flr.patch 2.12 kB · 0 downloads Appreciated. If you got any suggestions for improvements please feel free to ask, but I think the container has enough features for now... Please if you ever rebuilding the Kernel/Images again, delete the container and redownload it from the CA App to be always on the latest version and up to date
July 1, 20206 yr 26 minutes ago, ich777 said: If you got any suggestions for improvements please feel free to ask, but I think the container has enough features for now... It's pretty pretty awesome considering. I would say maybe adding a time stamp or elapsed time on build in the log would be good to benchmark and identify anything odd. You mentioned some expected build times in your post, so I thought that would be good. But really if you read the log it's sufficient to see what happened. So again. not really it's pretty awesome. 27 minutes ago, ich777 said: Please if you ever rebuilding the Kernel/Images again, delete the container and redownload it from the CA App to be always on the latest version and up to date Already deleted!
July 1, 20206 yr Author 18 minutes ago, bigbangus said: It's pretty pretty awesome considering. I would say maybe adding a time stamp or elapsed time on build in the log would be good to benchmark and identify anything odd. You mentioned some expected build times in your post, so I thought that would be good. But really if you read the log it's sufficient to see what happened. So again. not really it's pretty awesome. The build times are completely variable since some tasks are core count dependent and some tasks favour clock speed so a real comparison is not really possible... Also I don't want to compare the virtual size of things based on this container... The mentioned 30 minutes are really for slow machines with let's say a Core2Duo or something similary...
July 2, 20206 yr ---Trying to get latest version for DigitalDevices driver--- ---Latest version for DigitalDevices driver: v0.9.37--- ---Trying to get latest version for LibreELEC driver--- ---Latest version for LibreELEC driver: v1.4.0--- ---nVidia driver manually set to: v450.51--- ---Trying to get latest version for Seccomp--- ---Latest version for DigitalDevices driver: v0.9.37--- ---Trying to get latest version for LibreELEC driver--- ---Latest version for LibreELEC driver: v1.4.0--- ---nVidia driver manually set to: v450.51--- ---Trying to get latest version for Seccomp--- ---Latest version for Seccomp: v2.4.3--- ---Trying to get latest version for 'nvidia-container-runtime' driver--- ---Latest version for 'nvidia-container-runtime': v3.2.0--- ---Trying to get latest version for 'nvidia-toolkit' driver--- ---Can't get latest version for 'nvidia-toolkit', putting container into sleep mode!--- what am I missing? Edited July 2, 20206 yr by emrepolat7
July 2, 20206 yr Author 53 minutes ago, emrepolat7 said: ---Trying to get latest version for DigitalDevices driver--- ---Latest version for DigitalDevices driver: v0.9.37--- ---Trying to get latest version for LibreELEC driver--- ---Latest version for LibreELEC driver: v1.4.0--- ---nVidia driver manually set to: v450.51--- ---Trying to get latest version for Seccomp--- ---Latest version for DigitalDevices driver: v0.9.37--- ---Trying to get latest version for LibreELEC driver--- ---Latest version for LibreELEC driver: v1.4.0--- ---nVidia driver manually set to: v450.51--- ---Trying to get latest version for Seccomp--- ---Latest version for Seccomp: v2.4.3--- ---Trying to get latest version for 'nvidia-container-runtime' driver--- ---Latest version for 'nvidia-container-runtime': v3.2.0--- ---Trying to get latest version for 'nvidia-toolkit' driver--- ---Can't get latest version for 'nvidia-toolkit', putting container into sleep mode!--- what am I missing? Nothing, they moved the toolkit to another location, give me some time and i will fix this, will report back
July 2, 20206 yr Author 1 hour ago, emrepolat7 said: what am I missing? All fixed now, please delete the container and redownload it from the CA App.
July 2, 20206 yr Author 1 minute ago, emrepolat7 said: thank you very much. 👏 it was really fast Please report back if everything works as expected. What version are you building for? 6.8.3 or 6.9.0beta22?
July 2, 20206 yr Author 5 minutes ago, emrepolat7 said: my version is 6.9.0beta22. Nice, I tried it for this version and should work well Please report back if everything working as expecte.
July 2, 20206 yr Author 10 minutes ago, emrepolat7 said: I think I have to install GPU card first! Yes, the gpu must be installed in the server to show up.
July 8, 20206 yr Author Container updated and now fully compatible with v6.9.0beta24 (prebuilt images will be updated soon). EDIT: Prebuilt images are now online.
July 8, 20206 yr I compile my kernel for bêta 24 with nvidia and it's work.Great News no more need flr patch for Audio and usb passthrough on x570 ryzen Board. It's implemented in 5.7.7 stock kernel [emoji16].Envoyé de mon HD1913 en utilisant Tapatalk
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.