* illumos/uefi-edk2 update 2023-11 @ 2024-02-12 12:42 Stephan Althaus 2024-02-12 14:48 ` Andy Fiddaman 0 siblings, 1 reply; 7+ messages in thread From: Stephan Althaus @ 2024-02-12 12:42 UTC (permalink / raw) To: illumos-developer Hello! I would like to update OI pkg://system/bhyve/firmware to the latest release to work on my PCIe GPU passthru tests.. The upstream repo https://github.com/tianocore/edk2 is on release 202311, whereas https://github.com/illumos/uefi-edk2 is still on 202308-1. May someone please kindly trigger someone to update... (?) Thanks! Regards, Stephan ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: illumos/uefi-edk2 update 2023-11 2024-02-12 12:42 illumos/uefi-edk2 update 2023-11 Stephan Althaus @ 2024-02-12 14:48 ` Andy Fiddaman 2024-02-13 12:05 ` [developer] " Stephan Althaus 0 siblings, 1 reply; 7+ messages in thread From: Andy Fiddaman @ 2024-02-12 14:48 UTC (permalink / raw) To: illumos-developer [-- Attachment #1: Type: text/plain, Size: 579 bytes --] Last time I tried to build 202311 on illumos it failed due to a number of conflicting type definitions. I haven't had the time to get back to it and see what is going on there. If you want to try building it yourself then you should be able to just take the upstream tianocore 202311 tag and cherry pick the last three commits from the il-edk2-stable202308, resolving any conflicts, then start from there. Otherwise I can take a look at the weekend. In the past I've updated this in OmniOS first then pushed the branch to illumos after some period of soak testing. Andy [-- Attachment #2: Type: text/html, Size: 713 bytes --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [developer] Re: illumos/uefi-edk2 update 2023-11 2024-02-12 14:48 ` Andy Fiddaman @ 2024-02-13 12:05 ` Stephan Althaus 2024-02-13 12:19 ` Marcel Telka 2024-02-16 9:29 ` Stephan Althaus 0 siblings, 2 replies; 7+ messages in thread From: Stephan Althaus @ 2024-02-13 12:05 UTC (permalink / raw) To: developer, illumos [-- Attachment #1: Type: text/plain, Size: 2084 bytes --] On 2/12/24 15:48, Andy Fiddaman wrote: > Last time I tried to build 202311 on illumos it failed due to a number > of conflicting type definitions. I haven't had the time to get back to > it and see what is going on there. > > If you want to try building it yourself then you should be able to > just take the upstream tianocore 202311 tag and cherry pick the last > three commits from the il-edk2-stable202308, resolving any conflicts, > then start from there. > > Otherwise I can take a look at the weekend. In the past I've updated > this in OmniOS first then pushed the branch to illumos after some > period of soak testing. > > Andy > *illumos <https://illumos.topicbox.com/latest>* / illumos-developer / > see discussions <https://illumos.topicbox.com/groups/developer> + > participants <https://illumos.topicbox.com/groups/developer/members> + > delivery options > <https://illumos.topicbox.com/groups/developer/subscription> Permalink > <https://illumos.topicbox.com/groups/developer/T0e71dad0bc17329a-Mdd0c9611fb1f17d9ee9d9e2a> > Hi Andy! Thanks for the hint! Here on OI we lack python >= 3.10 from what i see.. $ pip3 install -r pip-requirements.txt --upgrade ERROR: Ignored the following versions that require a different python version: 0.19.0 Requires-Python >=3.10; 0.19.1 Requires-Python >=3.10; 0.19.2 Requires-Python >=3.10; 0.19.3 Requires-Python >=3.10; 0.19.4 Requires-Python >=3.10; 0.19.5 Requires-Python >=3.10; 0.19.6 Requires-Python >=3.10; 0.19.7 Requires-Python >=3.10; 0.19.8 Requires-Python >=3.10; 0.19.9 Requires-Python >=3.10; 0.20.0 Requires-Python >=3.10; 0.21.2 Requires-Python >=3.10; 0.21.3 Requires-Python >=3.10 .. so i should try to integrate py-312 for OI first ?? i have absolutely no idea what has to be done additionally, there are sooo many python packages for OI, so this seems out of scope to me right now. i think i will try to use proxmox first to see if my hardware is able to do what i want and then see if i can do it with bhyve.. Thanks! Stephan [-- Attachment #2: Type: text/html, Size: 3437 bytes --] ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [developer] Re: illumos/uefi-edk2 update 2023-11 2024-02-13 12:05 ` [developer] " Stephan Althaus @ 2024-02-13 12:19 ` Marcel Telka 2024-02-16 9:29 ` Stephan Althaus 1 sibling, 0 replies; 7+ messages in thread From: Marcel Telka @ 2024-02-13 12:19 UTC (permalink / raw) To: illumos-developer On Tue, Feb 13, 2024 at 01:05:45PM +0100, Stephan Althaus wrote: > .. so i should try to integrate py-312 for OI first ?? i have absolutely no FYI, https://github.com/OpenIndiana/oi-userland/pull/15955 -- +-------------------------------------------+ | Marcel Telka e-mail: marcel@telka.sk | | homepage: http://telka.sk/ | +-------------------------------------------+ ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [developer] Re: illumos/uefi-edk2 update 2023-11 2024-02-13 12:05 ` [developer] " Stephan Althaus 2024-02-13 12:19 ` Marcel Telka @ 2024-02-16 9:29 ` Stephan Althaus 2024-10-29 15:25 ` Stephan Althaus 1 sibling, 1 reply; 7+ messages in thread From: Stephan Althaus @ 2024-02-16 9:29 UTC (permalink / raw) To: developer Hello! Small update on this.. The goal i want to achieve is to have a GPU passthrough on OI to a Windows vm with bhyve... I now tested linux/proxmox (kvm) and FreeBSD 14 (bhyve) with success, so i can assume the Hardware and the BIOS settings are ok. FreeBSD has this version of the edk2 image: $ pkg search edk2 edk2-bhyve-g202308_4 EDK2 Firmware for bhyve .. so version 202311 seems not to be needed (?) What i see if i try it on OI, is that immu-intrmap-enable="true"; in /platform/i86pc/kernel/drv/rootnex.conf leads to error messages when i start the bhyve test script with messages APIC ERROR Interrupt on CPU 0. Status 0 = 0 Status 1 = 40. on the console and the system is not responsive anymore.. Do i _need_ immu-intrmap-enable="true"; ? I currently have these values set: immu-enable="true"; #immu-intrmap-enable="true"; immu-blacklist= "SMBIOS","Supermicro","X10DRI-T","" ; immu-dvma-mapping="xlate"; immu-dvma-unity-drivers="igb","ahci","ixgbe","ehci","xhci","nvme"; immu-dvma-xlate-drivers="mpt"; Is anyone around with a success story who has been there and done that ? i want to passtrough this: $ pptadm list -o all DEV VENDOR DEVICE SUBVENDOR SUBDEVICE REV PATH LABEL /dev/ppt0 1002 743f 1da2 e458 c7 /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/display@0 Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 XT/6500M] /dev/ppt1 1002 ab28 1002 ab28 0 /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/pci1002,ab28@0,1 Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller ... using this test script: $ /usr/sbin/bhyve -U bd60bf59-0ed6-61a1-f0ed-b17e99ada165 -A -H \ -B 1,manufacturer=OpenIndiana,product=OpenIndianaHVM,version=1.0,serial=69a18a85-c1df-c266-f620-a99a632d3c11,sku=001,family=VirtualMachine \ -c 4 -m 16G -w \ -s 31:0,lpc -l bootrom,/usr/share/bhyve/firmware/BHYVE.fd,fwcfg=qemu \ -s 0,hostbridge,model=i440fx \ -s 4:0,nvme,/dev/zvol/rdsk/home2/vm/win10vol \ -s 6:0,virtio-net-viona,vnic0 \ -s 30:0,fbuf,vga=off,tcp=0.0.0.0:5905 \ -s 30:1,xhci,tablet \ -S -s 8:0,passthru,/dev/ppt0,rom=/home2/vm/Navi24.rom \ -s 8:1,passthru,/dev/ppt1 \ win10 The GPU can be seen within the vm (error 43), it seems the card doesn't get initialized.. Any hints are welcome.. Regards, Stephan ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [developer] Re: illumos/uefi-edk2 update 2023-11 2024-02-16 9:29 ` Stephan Althaus @ 2024-10-29 15:25 ` Stephan Althaus 2024-10-30 8:32 ` Stephan Althaus 0 siblings, 1 reply; 7+ messages in thread From: Stephan Althaus @ 2024-10-29 15:25 UTC (permalink / raw) To: developer Hi All! I thought i'd try out a GPU passthrough on OI to a Windows vm with bhyve again. This time it is an AMD RX 6400, and i verified the System settings with FreeBSD 4.1, there the GPU is working, so the BIOS settings and the GPU-ROM are ok. The VM startscripts and data are within a NVME zpool, so that i can switch to OI easily and have the same with FrreBSD and OI. When i enable immu-intrmap-enable="true"; in /platform/i86pc/kernel/drv/rootnex.conf this leads to error messages when i start the bhyve test script with messages APIC ERROR Interrupt on CPU 0. Status 0 = 0 Status 1 = 40. on the console and the system is not responsive anymore.. When i leave it toimmu-intrmap-enable=" false", the Windows vm starts and the GPU has error 43 within the device-manager. What can i do to see where the APIC error comes from ? some dtrace script maybe ? Any help is appreciated. Regards, Stephan P.S. The test command: /usr/sbin/bhyve -U bd60bf59-0ed6-61a1-f0ed-b17e99ada165 -A -H \ -B 1,manufacturer=OpenIndiana,product=OpenIndianaHVM,version=1.0,serial=69a18a85-c1df-c266-f620-a99a632d3c11,sku=001,family=VirtualMachine \ -c 4 -m 16G -w \ -s 31:0,lpc -l bootrom,/home2/vm/BHYVE_UEFI.fd \ -s 0,hostbridge,model=i440fx \ -s 4:0,nvme,/dev/zvol/rdsk/home2/vm/win10vol \ -s 6:0,virtio-net-viona,vnic0 \ -s 7:0,ahci-cd,/home2/vm/virtio-win-0.1.240.iso \ -s 30:0,fbuf,tcp=0.0.0.0:5905,w=1920,h=1080 \ -s 30:1,xhci,tablet \ -S \ -s 8:0,passthru,/dev/ppt0,rom=/home2/vm/Navi24.rom \ -s 8:1,passthru,/dev/ppt1 \ win10 $ pptadm DEV VENDOR DEVICE PATH /dev/ppt0 1002 743f /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/display@0 /dev/ppt1 1002 ab28 /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/pci1002,ab28@0,1 On 2/16/24 10:29, Stephan Althaus wrote: > Hello! > > Small update on this.. > > The goal i want to achieve is to have a GPU passthrough on OI to a > Windows vm with bhyve... > > I now tested linux/proxmox (kvm) and FreeBSD 14 (bhyve) with success, > so i can assume the Hardware and the BIOS settings are ok. > > FreeBSD has this version of the edk2 image: > > $ pkg search edk2 > edk2-bhyve-g202308_4 EDK2 Firmware for bhyve > > .. so version 202311 seems not to be needed (?) > > What i see if i try it on OI, is that > > immu-intrmap-enable="true"; > > in > > /platform/i86pc/kernel/drv/rootnex.conf > > leads to error messages when i start the bhyve test script with messages > APIC ERROR Interrupt on CPU 0. Status 0 = 0 Status 1 = 40. > on the console and the system is not responsive anymore.. > > > Do i _need_ immu-intrmap-enable="true"; ? > > > I currently have these values set: > > immu-enable="true"; > #immu-intrmap-enable="true"; > immu-blacklist= > "SMBIOS","Supermicro","X10DRI-T","" > ; > immu-dvma-mapping="xlate"; > immu-dvma-unity-drivers="igb","ahci","ixgbe","ehci","xhci","nvme"; > immu-dvma-xlate-drivers="mpt"; > > Is anyone around with a success story who has been there and done that ? > > > i want to passtrough this: > > $ pptadm list -o all > DEV VENDOR DEVICE SUBVENDOR SUBDEVICE REV > PATH LABEL > /dev/ppt0 1002 743f 1da2 e458 c7 > /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/display@0 > Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 > XT/6500M] > /dev/ppt1 1002 ab28 1002 ab28 0 > /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/pci1002,ab28@0,1 > Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio > Controller > > ... using this test script: > > $ /usr/sbin/bhyve -U bd60bf59-0ed6-61a1-f0ed-b17e99ada165 -A -H \ > -B > 1,manufacturer=OpenIndiana,product=OpenIndianaHVM,version=1.0,serial=69a18a85-c1df-c266-f620-a99a632d3c11,sku=001,family=VirtualMachine > \ > -c 4 -m 16G -w \ > -s 31:0,lpc -l bootrom,/usr/share/bhyve/firmware/BHYVE.fd,fwcfg=qemu \ > -s 0,hostbridge,model=i440fx \ > -s 4:0,nvme,/dev/zvol/rdsk/home2/vm/win10vol \ > -s 6:0,virtio-net-viona,vnic0 \ > -s 30:0,fbuf,vga=off,tcp=0.0.0.0:5905 \ > -s 30:1,xhci,tablet \ > -S -s 8:0,passthru,/dev/ppt0,rom=/home2/vm/Navi24.rom \ > -s 8:1,passthru,/dev/ppt1 \ > win10 > > The GPU can be seen within the vm (error 43), it seems the card > doesn't get initialized.. > > Any hints are welcome.. > > > Regards, > > Stephan > > > > ------------------------------------------ > illumos: illumos-developer > Permalink: > https://illumos.topicbox.com/groups/developer/T0e71dad0bc17329a-M635020990ad99de8499b28ad > Delivery options: > https://illumos.topicbox.com/groups/developer/subscription ------------------------------------------ illumos: illumos-developer Permalink: https://illumos.topicbox.com/groups/developer/T0e71dad0bc17329a-M54c5f6bf883f52445dbaedfd Delivery options: https://illumos.topicbox.com/groups/developer/subscription ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [developer] Re: illumos/uefi-edk2 update 2023-11 2024-10-29 15:25 ` Stephan Althaus @ 2024-10-30 8:32 ` Stephan Althaus 0 siblings, 0 replies; 7+ messages in thread From: Stephan Althaus @ 2024-10-30 8:32 UTC (permalink / raw) To: developer On 10/29/24 16:25, Stephan Althaus wrote: > Hi All! > > I thought i'd try out a GPU passthrough on OI to a Windows vm with > bhyve again. > > This time it is an AMD RX 6400, and i verified the System settings > with FreeBSD 4.1, there the GPU is working, so the BIOS settings and > the GPU-ROM are ok. > > The VM startscripts and data are within a NVME zpool, so that i can > switch to OI easily and have the same with FrreBSD and OI. > > When i enable immu-intrmap-enable="true"; in > /platform/i86pc/kernel/drv/rootnex.conf > this leads to error messages when i start the bhyve test script with > messages > APIC ERROR Interrupt on CPU 0. Status 0 = 0 Status 1 = 40. > on the console and the system is not responsive anymore.. > > When i leave it toimmu-intrmap-enable=" false", the Windows vm starts > and the GPU has error 43 within the device-manager. > > What can i do to see where the APIC error comes from ? some dtrace > script maybe ? > > Any help is appreciated. > > Regards, > Stephan > > P.S. The test command: > > /usr/sbin/bhyve -U bd60bf59-0ed6-61a1-f0ed-b17e99ada165 -A -H \ > -B > 1,manufacturer=OpenIndiana,product=OpenIndianaHVM,version=1.0,serial=69a18a85-c1df-c266-f620-a99a632d3c11,sku=001,family=VirtualMachine > \ > -c 4 -m 16G -w \ > -s 31:0,lpc -l bootrom,/home2/vm/BHYVE_UEFI.fd \ > -s 0,hostbridge,model=i440fx \ > -s 4:0,nvme,/dev/zvol/rdsk/home2/vm/win10vol \ > -s 6:0,virtio-net-viona,vnic0 \ > -s 7:0,ahci-cd,/home2/vm/virtio-win-0.1.240.iso \ > -s 30:0,fbuf,tcp=0.0.0.0:5905,w=1920,h=1080 \ > -s 30:1,xhci,tablet \ > -S \ > -s 8:0,passthru,/dev/ppt0,rom=/home2/vm/Navi24.rom \ > -s 8:1,passthru,/dev/ppt1 \ > win10 > > $ pptadm > DEV VENDOR DEVICE PATH > /dev/ppt0 1002 743f > /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/display@0 > /dev/ppt1 1002 ab28 > /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/pci1002,ab28@0,1 > > > On 2/16/24 10:29, Stephan Althaus wrote: >> Hello! >> >> Small update on this.. >> >> The goal i want to achieve is to have a GPU passthrough on OI to a >> Windows vm with bhyve... >> >> I now tested linux/proxmox (kvm) and FreeBSD 14 (bhyve) with >> success, so i can assume the Hardware and the BIOS settings are ok. >> >> FreeBSD has this version of the edk2 image: >> >> $ pkg search edk2 >> edk2-bhyve-g202308_4 EDK2 Firmware for bhyve >> >> .. so version 202311 seems not to be needed (?) >> >> What i see if i try it on OI, is that >> >> immu-intrmap-enable="true"; >> >> in >> >> /platform/i86pc/kernel/drv/rootnex.conf >> >> leads to error messages when i start the bhyve test script with messages >> APIC ERROR Interrupt on CPU 0. Status 0 = 0 Status 1 = 40. >> on the console and the system is not responsive anymore.. >> >> >> Do i _need_ immu-intrmap-enable="true"; ? >> >> >> I currently have these values set: >> >> immu-enable="true"; >> #immu-intrmap-enable="true"; >> immu-blacklist= >> "SMBIOS","Supermicro","X10DRI-T","" >> ; >> immu-dvma-mapping="xlate"; >> immu-dvma-unity-drivers="igb","ahci","ixgbe","ehci","xhci","nvme"; >> immu-dvma-xlate-drivers="mpt"; >> >> Is anyone around with a success story who has been there and done that ? >> >> >> i want to passtrough this: >> >> $ pptadm list -o all >> DEV VENDOR DEVICE SUBVENDOR SUBDEVICE REV >> PATH LABEL >> /dev/ppt0 1002 743f 1da2 e458 c7 >> /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/display@0 >> Advanced Micro Devices, Inc. [AMD/ATI] Navi 24 [Radeon RX 6400/6500 >> XT/6500M] >> /dev/ppt1 1002 ab28 1002 ab28 0 >> /pci@7a,0/pci8086,6f08@3/pci1002,1478@0/pci1002,1479@0/pci1002,ab28@0,1 >> Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio >> Controller >> >> ... using this test script: >> >> $ /usr/sbin/bhyve -U bd60bf59-0ed6-61a1-f0ed-b17e99ada165 -A -H \ >> -B >> 1,manufacturer=OpenIndiana,product=OpenIndianaHVM,version=1.0,serial=69a18a85-c1df-c266-f620-a99a632d3c11,sku=001,family=VirtualMachine >> \ >> -c 4 -m 16G -w \ >> -s 31:0,lpc -l bootrom,/usr/share/bhyve/firmware/BHYVE.fd,fwcfg=qemu \ >> -s 0,hostbridge,model=i440fx \ >> -s 4:0,nvme,/dev/zvol/rdsk/home2/vm/win10vol \ >> -s 6:0,virtio-net-viona,vnic0 \ >> -s 30:0,fbuf,vga=off,tcp=0.0.0.0:5905 \ >> -s 30:1,xhci,tablet \ >> -S -s 8:0,passthru,/dev/ppt0,rom=/home2/vm/Navi24.rom \ >> -s 8:1,passthru,/dev/ppt1 \ >> win10 >> >> The GPU can be seen within the vm (error 43), it seems the card >> doesn't get initialized.. >> >> Any hints are welcome.. >> >> >> Regards, >> >> Stephan >> >> >> >> ------------------------------------------ >> illumos: illumos-developer >> Permalink: >> https://illumos.topicbox.com/groups/developer/T0e71dad0bc17329a-M635020990ad99de8499b28ad >> Delivery options: >> https://illumos.topicbox.com/groups/developer/subscription > > > > ------------------------------------------ > illumos: illumos-developer > Permalink: > https://illumos.topicbox.com/groups/developer/T0e71dad0bc17329a-M54c5f6bf883f52445dbaedfd > Delivery options: > https://illumos.topicbox.com/groups/developer/subscription Hi! I tested the move of the vm data to a SATA drive, removed the nvme drive, but the APIC Interrupt errors persist. Which additional drivers of the 168 used $ modinfo |awk '{print $6}'|sort -u|wc 168 168 1146 do i have to blacklist in rootnex.conf ?? Anyone BTDT ? Here's some messages-output that may be of interest: user@smhost:~$ grep DMAR /var/adm/messages |grep "8:5 > ^C user@smhost:~$ grep DMAR /var/adm/messages |grep "8:5" Oct 30 08:52:24 smhost acpica: [ID 137418 kern.notice] ACPI: DMAR 0x0000000079F05458 000138 (v01 ALASKA A M I 00000001 INTL 20091013) Oct 30 08:52:24 smhost genunix: [ID 958256 kern.info] Processing DMAR ACPI table Oct 30 08:52:24 smhost genunix: [ID 680212 kern.notice] NOTICE: DMAR ACPI table: skipping unsupported unit type ATSR Oct 30 08:52:24 smhost genunix: [ID 533727 kern.notice] NOTICE: DMAR ACPI table: skipping unsupported unit type RHSA user@smhost:~$ grep iomm /var/adm/messages |grep "8:5" Oct 30 08:52:24 smhost iommulib: [ID 321598 kern.info] NOTICE: iommulib_nexus_register: rootnex-1: Succesfully registered NEXUS i86pc nexops=fffffffffbd30040 Oct 30 08:52:24 smhost genunix: [ID 970263 kern.info] iommu0: unit setup Oct 30 08:52:24 smhost genunix: [ID 970279 kern.info] iommu1: unit setup Oct 30 08:52:24 smhost genunix: [ID 466022 kern.info] iommu0: creating domainid arena iommu0_domainid_arena Oct 30 08:52:24 smhost genunix: [ID 160421 kern.info] iommu1: creating domainid arena iommu1_domainid_arena Oct 30 08:52:24 smhost genunix: [ID 733261 kern.info] isa0: iommu: Found LPC device Oct 30 08:52:24 smhost genunix: [ID 969345 kern.info] isa0: iommu: iommu1-domain-2-xlate-DVMA-arena: Creating dvma vmem arena [0x1000 - 0x9a000] Oct 30 08:52:24 smhost genunix: [ID 331729 kern.info] isa0: iommu: iommu1-domain-2-xlate-DVMA-arena: Adding dvma vmem span [0x100000 - 0x79034000] Oct 30 08:52:24 smhost genunix: [ID 325630 kern.info] isa0: iommu: iommu1-domain-2-xlate-DVMA-arena: Adding dvma vmem span [0x100000000 - 0x2080000000] Oct 30 08:52:24 smhost genunix: [ID 352456 kern.info] vgatext: iommu: Found GFX device Oct 30 08:52:24 smhost genunix: [ID 137511 kern.info] ppt: iommu: Found GFX device Oct 30 08:52:24 smhost genunix: [ID 664311 kern.notice] NOTICE: iommu0 running Oct 30 08:52:24 smhost iommulib: [ID 345192 kern.info] NOTICE: iommulib_register: iommu0: Detected IOMMU registration from vendor Intel Oct 30 08:52:24 smhost iommulib: [ID 643661 kern.info] NOTICE: iommulib_register: iommu0: Succesfully registered IOMMU unit from vendor=Intel, ops=fffffeb1ae8dad80, data=fffffeb1ae136b00, IOMMULIB unitid=1 Oct 30 08:52:24 smhost genunix: [ID 341888 kern.notice] NOTICE: iommu1 running Oct 30 08:52:24 smhost iommulib: [ID 345192 kern.info] NOTICE: iommulib_register: iommu1: Detected IOMMU registration from vendor Intel Oct 30 08:52:24 smhost iommulib: [ID 643661 kern.info] NOTICE: iommulib_register: iommu1: Succesfully registered IOMMU unit from vendor=Intel, ops=fffffeb1ae8dad20, data=fffffeb1ae136880, IOMMULIB unitid=2 Oct 30 08:52:24 smhost amd_iommu: [ID 251261 kern.info] NOTICE: amd_iommu: No AMD IOMMU ACPI IVRS table Regards, Stephan ------------------------------------------ illumos: illumos-developer Permalink: https://illumos.topicbox.com/groups/developer/T0e71dad0bc17329a-Me195bb0082c187610dd28f76 Delivery options: https://illumos.topicbox.com/groups/developer/subscription ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2024-10-30 8:34 UTC | newest] Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2024-02-12 12:42 illumos/uefi-edk2 update 2023-11 Stephan Althaus 2024-02-12 14:48 ` Andy Fiddaman 2024-02-13 12:05 ` [developer] " Stephan Althaus 2024-02-13 12:19 ` Marcel Telka 2024-02-16 9:29 ` Stephan Althaus 2024-10-29 15:25 ` Stephan Althaus 2024-10-30 8:32 ` Stephan Althaus
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).