Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Support] ich777 - AMD Vendor Reset, CoralTPU, hpsahba,...

Featured Replies

9 hours ago, methanoid said:

 

Hi, thanks for any help here

 

I have efifb:off but not vesafb - is that needed?

No, no unsafe interrupts

I have tried with and without acs_override... no difference

 

Not tried Linux (will later) but also tried i440FX instead of Q35 (with existing NVME so wasnt likely to work) - worse

 

Checked my logs and interesting here

 



ErrorWarningSystemArrayLogin


-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \
-device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \
-device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \
-device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \
-device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \
-device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 \
-device pcie-root-port,port=0xe,chassis=7,id=pci.7,bus=pcie.0,addr=0x1.0x6 \
-device pcie-root-port,port=0xf,chassis=8,id=pci.8,bus=pcie.0,addr=0x1.0x7 \
-device pcie-root-port,port=0x10,chassis=9,id=pci.9,bus=pcie.0,addr=0x2 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-netdev tap,fd=33,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ed:cd:78,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=34,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device vfio-pci,host=0000:10:00.0,id=hostdev0,bus=pci.3,addr=0x0,romfile=/boot/GPU_Roms/Powercolor.RX5700.rom \
-device vfio-pci,host=0000:10:00.1,id=hostdev1,bus=pci.4,addr=0x0 \
-device vfio-pci,host=0000:0a:00.0,id=hostdev2,bus=pci.5,addr=0x0 \
-device vfio-pci,host=0000:0a:00.1,id=hostdev3,bus=pci.6,addr=0x0 \
-device vfio-pci,host=0000:0a:00.3,id=hostdev4,bus=pci.7,addr=0x0 \
-device vfio-pci,host=0000:0d:00.0,id=hostdev5,bus=pci.8,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2021-04-15 09:07:11.798+0000: Domain id=2 is tainted: high-privileges
2021-04-15 09:07:11.798+0000: Domain id=2 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2021-04-15T09:07:15.788543Z qemu-system-x86_64: vfio: Cannot reset device 0000:10:00.1, no available reset mechanism.
2021-04-15T09:07:15.932195Z qemu-system-x86_64: vfio: Cannot reset device 0000:10:00.1, no available reset mechanism.
2021-04-15T09:08:52.266352Z qemu-system-x86_64: terminating on signal 15 from pid 11862 (/usr/sbin/libvirtd)
2021-04-15 09:08:58.100+0000: shutting down, reason=shutdown


ErrorWarningSystemArrayLogin


-nodefaults \
-chardev socket,id=charmonitor,fd=31,server,nowait \
-mon chardev=charmonitor,id=monitor,mode=control \
-rtc base=localtime \
-no-hpet \
-no-shutdown \
-boot strict=on \
-device pcie-root-port,port=0x8,chassis=1,id=pci.1,bus=pcie.0,multifunction=on,addr=0x1 \
-device pcie-root-port,port=0x9,chassis=2,id=pci.2,bus=pcie.0,addr=0x1.0x1 \
-device pcie-root-port,port=0xa,chassis=3,id=pci.3,bus=pcie.0,addr=0x1.0x2 \
-device pcie-root-port,port=0xb,chassis=4,id=pci.4,bus=pcie.0,addr=0x1.0x3 \
-device pcie-root-port,port=0xc,chassis=5,id=pci.5,bus=pcie.0,addr=0x1.0x4 \
-device pcie-root-port,port=0xd,chassis=6,id=pci.6,bus=pcie.0,addr=0x1.0x5 \
-device pcie-root-port,port=0xe,chassis=7,id=pci.7,bus=pcie.0,addr=0x1.0x6 \
-device pcie-root-port,port=0xf,chassis=8,id=pci.8,bus=pcie.0,addr=0x1.0x7 \
-device pcie-root-port,port=0x10,chassis=9,id=pci.9,bus=pcie.0,addr=0x2 \
-device ich9-usb-ehci1,id=usb,bus=pcie.0,addr=0x7.0x7 \
-device ich9-usb-uhci1,masterbus=usb.0,firstport=0,bus=pcie.0,multifunction=on,addr=0x7 \
-device ich9-usb-uhci2,masterbus=usb.0,firstport=2,bus=pcie.0,addr=0x7.0x1 \
-device ich9-usb-uhci3,masterbus=usb.0,firstport=4,bus=pcie.0,addr=0x7.0x2 \
-device virtio-serial-pci,id=virtio-serial0,bus=pci.2,addr=0x0 \
-netdev tap,fd=33,id=hostnet0 \
-device virtio-net,netdev=hostnet0,id=net0,mac=52:54:00:ed:cd:78,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=34,server,nowait \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device vfio-pci,host=0000:10:00.0,id=hostdev0,bus=pci.3,addr=0x0,romfile=/boot/GPU_Roms/Powercolor.RX5700.rom \
-device vfio-pci,host=0000:10:00.1,id=hostdev1,bus=pci.4,addr=0x0 \
-device vfio-pci,host=0000:0a:00.0,id=hostdev2,bus=pci.5,addr=0x0 \
-device vfio-pci,host=0000:0a:00.1,id=hostdev3,bus=pci.6,addr=0x0 \
-device vfio-pci,host=0000:0a:00.3,id=hostdev4,bus=pci.7,addr=0x0 \
-device vfio-pci,host=0000:0d:00.0,id=hostdev5,bus=pci.8,addr=0x0 \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2021-04-15 09:09:54.742+0000: Domain id=3 is tainted: high-privileges
2021-04-15 09:09:54.742+0000: Domain id=3 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2021-04-15T09:10:04.876682Z qemu-system-x86_64: vfio: Cannot reset device 0000:10:00.1, no available reset mechanism.
2021-04-15T09:10:05.020320Z qemu-system-x86_64: vfio: Cannot reset device 0000:10:00.1, no available reset mechanism.

 

It hangs on 2nd boot (this is both listed here)

 

Looks to me like the Reset ISNT working, since that is where it hangs!

 

No that's actually an old entry I never removed. I tried it in my unraid beginnings.. 

 

Is the vendor-reset really loaded? Pls check with lsmod..

 

Don't worry, Q35 is best for every OS.

Edited by giganode

  • Replies 2.4k
  • Views 480k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • can i be the first to say, wow!, i can see how this will be VERY useful for people wanting to pass through hardware to containers, and now being able to build out an image is impressive work indeed!,

  • Im still confused by him. He does not want to update to 8.6.3 from 8.6.2 due to personal reasons. Yet he keeps saying the only thing it fixed was a venerability. So I guess that he needs this venerabi

Posted Images

21 minutes ago, giganode said:

 

No that's actually an old entry I never removed. I tried it in my unraid beginnings.. 

 

Is the vendor-reset really loaded? Pls check with lsmod..

 

Don't worry, Q35 is best for every OS.

 

vendor_reset           81920  0

 

from lsmod.... is that loaded?

8 minutes ago, methanoid said:

 

vendor_reset           81920  0

 

from lsmod.... is that loaded?

 

Yes, it's loaded.. I saw your issue on github.. let's see what ajmadsen says about it if you give him the requested data..

definetely an unexpected behaviour.....

jpo.jpg 

Here's my IOMMU when I DONT use any ACS patches -   I see at bottom both GPUS (Nvidia in one group, AMD in two) but BOTH audio sections dont show FLR enabled and at top the pair of USB controllers we normally have to pass (allegedly other one doesnt like being passed) one of which doesnt show FLR enabled.    I wonder if the BIOS is borked? I'm clutching at straws

Hi,

 

i would like to know if with the tools i have the posibility to add kernel-debug-modules-extra in the  customized Unraid Kernel ?

 

Thanks for your help :)

  • Author
1 hour ago, JamesAdams said:

i would like to know if with the tools i have the posibility to add kernel-debug-modules-extra in the  customized Unraid Kernel ?

You can add everything you want to the images, simply enable the 'Custom Build' mode and the container will stop right at the beginning and copy the build script to the specified appdata directory for the container and you can open up a console and do everything step by step and include whatever you want.

23 minutes ago, ich777 said:

You can add everything you want to the images, simply enable the 'Custom Build' mode and the container will stop right at the beginning and copy the build script to the specified appdata directory for the container and you can open up a console and do everything step by step and include whatever you want.

Thanks i go test that :)

  • Author
19 minutes ago, JamesAdams said:

Thanks i go test that :)

Keep in mind that you have go through the build script line by line or at least condition by condition for everything you need.

19 minutes ago, ich777 said:

Keep in mind that you have go through the build script line by line or at least condition by condition for everything you need.

Sorry I did not understand :(

  • Author
26 minutes ago, JamesAdams said:

Sorry I did not understand :(

What did you not understand?

On 4/19/2021 at 5:01 PM, ich777 said:

What did you not understand?

 

the phrase, my english must not be good enough :D

@ich777

 

if I understood correctly if I want to install the kernel-debug-modules-extra I must launch the container and activate the Custom Build Mode option then I edit the build script which is in /usr/src.

 

I have good ?

  • Author
2 minutes ago, JamesAdams said:

I must launch the container and activate the Custom Build Mode option then I edit the build script which is in /usr/src.

Yes you can do that or you execute every line or at least every command from the script in the terminal.

Just now, ich777 said:

Yes you can do that or you execute every line or at least every command from the script in the terminal.

 

Ok thanks :)

On 4/19/2021 at 10:04 AM, methanoid said:

jpo.jpg 

Here's my IOMMU when I DONT use any ACS patches -   I see at bottom both GPUS (Nvidia in one group, AMD in two) but BOTH audio sections dont show FLR enabled and at top the pair of USB controllers we normally have to pass (allegedly other one doesnt like being passed) one of which doesnt show FLR enabled.    I wonder if the BIOS is borked? I'm clutching at straws

 

I removed RX5700 and put a GT740 in.... zero issues with any reboots etc. I was doing it to try to confirm the BIOS wasnt at fault or my config. I am now pretty sure its either the FLR patch that is at fault OR my Powercolor RX5700 is not same as other RX5700s. I have tried non Powercolor BIOS rom in config and no difference....    I guess my unRAID VMs are gonna have to be done using 2 x GT740s

  • Author

@methanoid of you are interested I now have a plugin ready for the soundcard.

Hook me up with a short message so I can send you the details.

@ich777 First of all.... very impressive container. Does this also update Qemu versions? The latest Qemu version is 6.0.0 rc4 but I am only seeing Qemu 5.1.

  • Author
5 hours ago, pavo said:

@ich777 First of all.... very impressive container. Does this also update Qemu versions? The latest Qemu version is 6.0.0 rc4 but I am only seeing Qemu 5.1.

No, this doesn't update Qemu since I don't know how the version from Qemu is built, you can only include drivers/modules/tools/patches (also if I would know that I wouldn't implement this into the container since this can cause much troubles).

Hi,

 

Anyone know how to install kernel-debug-modules-extra ? I searched but not found any info on the commands to be executed to install it :(

 

Thanks.

 

  • Author
1 hour ago, JamesAdams said:

kernel-debug-modules-extra

May I ask why do you need this?

What do you want to do with the extra debug symbols?

1 minute ago, ich777 said:

May I ask why do you need this?

What do you want to do with the extra debug symbols?

 

I need it to limit the internet speed of certain vm without that we cannot on unraid because we do not have access to the qdisk

 

Look my post here :)

 

  • Author
1 minute ago, JamesAdams said:

Look my post here :)

Like @SimonF said you need to enable it in the Kernel, simply change the command 'make oldconfig' with 'make menuconfig' this should bring up a menu where you can choose between the different modules that you want to enable.

9 minutes ago, ich777 said:

Like @SimonF said you need to enable it in the Kernel, simply change the command 'make oldconfig' with 'make menuconfig' this should bring up a menu where you can choose between the different modules that you want to enable.

 

Where would I see the menu ?

  • Author
1 hour ago, JamesAdams said:

 

Where would I see the menu ?

When you enabled Custom Mode and you are building it by hand with the console.

48 minutes ago, ich777 said:

When you enabled Custom Mode and you are building it by hand with the console.

 

Ok, thanks i found, but in the menu i don't found the kernel module CONFIG_NET_SCH_HTB of which speaks @SimonF

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.

Guest
Reply to this topic...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.