View source for MAGNUS EN1080 10 Year Anniversary Edition (ZBOX-EN1080)

=Details=

[[File:Magnus en1080 image02.jpg|320px]]
<br>

THE 10 YEAR ANNIVERSARY EDITION MAGNUS EN1080 is ZOTAC‘s second generation of water cooling Mini PC. It ascends gaming to the Virtual Reality with an Intel 6th Generation Skylake Core i7 processor and NVIDIA GeForce® GTX 1080 graphics - the first Mini PC to equip NVIDIA‘s new generation flagship graphics. The unique SPECTRA lighting system gives the system a glow of its own, and users can customize the lighting with the SPECTRA utility.
* Resources
** [https://www.zotac.com/se/product/mini_pcs/magnus-en1080-10-year-anniversary-edition MAGNUS EN1080 10 Year Anniversary Edition (ZBOX-EN1080) -- Product Page]
** Windows Drivers: https://www.zotac.com/se/files/download/by_product?p_nid=607475&driver_type=All&os=All
** Linux Drivers: https://webclone.zotac.com/eu/files/download/by_product?p_nid=607474&driver_type=All&os=All
** [https://www.zotac.com/mu/files/download/graphics_cards Generic Driver Page] (find the section titled "ZOTAC GeForce GTX 1080 ArcticStorm Thermaltake  10 週年版" )<br>Windows version says: "FireStorm_V2.0.0.014TT for GTX 1080 ArcticStorm Thermaltake 10 Year Anniversary Edition"
** [https://www.reddit.com/r/htpc/comments/5yhvtm/how_i_finally_fixed_my_4k_video_stuttering/ How I finally fixed my 4k video stuttering problem, a warning to everyone trying or eventually going to try getting a 4k movie PC up and running]

* Chipsets:
** NCT5532 ???

* BIOS
** Latest version as of 2023-05-23 10:12:49 EDT (Tuesday): <tt>Version 2K180904</tt> ( 2018-09-04 ??? )<br>https://www.zotac.com/download/mediadrivers/mb/bios/pb336EN1080.zip
*** <tt>MD5...: 052342935d95a96c55551dbc33e0db6f</tt>
*** <tt>SHA1..: 33e9afdb98233abedfc09201dc4cc06db1a4780e</tt>
*** <tt>SHA256: e9042d0029b69692d628b94d139a7d02679b200c3e9ffd2f3c7694c85c201a81</tt>
** Files in archive:<pre>.&#10;├── AfuEfix64.efi&#10;├── B336P114.bin&#10;├── EFI&#10;│   └── BOOT&#10;│       ├── BootIa32.efi&#10;│       └── Bootx64.efi&#10;├── flash.nsh&#10;├── fparts.txt&#10;├── Fpt.efi&#10;├── Note.txt&#10;├── pb336EN1080.zip&#10;└── Readme.txt&#10;&#10;2 directories, 10 files&#10;</pre>
* PCI Devices:
** 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor Host Bridge/DRAM Registers (rev 05)
** 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)
** 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th/8th Gen Core Processor Gaussian Mixture Model
** 00:14.0 USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller (rev 31)
** 00:14.2 Signal processing controller: Intel Corporation 100 Series/C230 Series Chipset Family Thermal Subsystem (rev 31)
** 00:16.0 Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1 (rev 31)
** 00:17.0 SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode] (rev 31)
** 00:1c.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5 (rev f1)
** 00:1c.5 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #6 (rev f1)
** 00:1c.6 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #7 (rev f1)
** 00:1c.7 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #8 (rev f1)
** 00:1d.0 PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9 (rev f1)
** 00:1f.0 ISA bridge: Intel Corporation B150 Chipset LPC/eSPI Controller (rev 31)
** 00:1f.2 Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller (rev 31)
** 00:1f.3 Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller (rev 31)
** 00:1f.4 SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus (rev 31)
** 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
** 02:00.0 USB controller: ASMedia Technology Inc. ASM1142 USB 3.1 Host Controller
** 03:00.0 Network controller: Intel Corporation Wireless 3165 (rev 81)
** 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
** 05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961

* USB Devices:
** Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
** Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
** Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
** Bus 001 Device 004: ID 2047:0305 Texas Instruments Zotac
** Bus 001 Device 003: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 (SD/SDHC/SDXC) Card Reader
** Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
** Bus 001 Device 005: ID 2047:0200 Texas Instruments MSP430 USB HID Bootstrap Loader
** Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

* LM Sensors drivers known to work:
** coretemp
** nct6775<pre>coretemp-isa-0000&#10;Adapter: ISA adapter&#10;Package id 0:  +37.0°C  (high = +80.0°C, crit = +100.0°C)&#10;Core 0:        +36.0°C  (high = +80.0°C, crit = +100.0°C)&#10;Core 1:        +36.0°C  (high = +80.0°C, crit = +100.0°C)&#10;Core 2:        +38.0°C  (high = +80.0°C, crit = +100.0°C)&#10;Core 3:        +35.0°C  (high = +80.0°C, crit = +100.0°C)&#10;&#10;acpitz-acpi-0&#10;Adapter: ACPI interface&#10;temp1:        +27.8°C  (crit = +119.0°C)&#10;temp2:        +29.8°C  (crit = +119.0°C)&#10;&#10;iwlwifi_1-virtual-0&#10;Adapter: Virtual device&#10;temp1:            N/A  &#10;&#10;pch_skylake-virtual-0&#10;Adapter: Virtual device&#10;temp1:        +48.0°C</pre>

* Processor<br><pre>Architecture:                    x86_64&#10;CPU op-mode(s):                  32-bit, 64-bit&#10;Byte Order:                      Little Endian&#10;Address sizes:                   39 bits physical, 48 bits virtual&#10;CPU(s):                          8&#10;On-line CPU(s) list:             0-7&#10;Thread(s) per core:              2&#10;Core(s) per socket:              4&#10;Socket(s):                       1&#10;NUMA node(s):                    1&#10;Vendor ID:                       GenuineIntel&#10;CPU family:                      6&#10;Model:                           158&#10;Model name:                      Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz&#10;Stepping:                        9&#10;CPU MHz:                         3641.124&#10;CPU max MHz:                     4200.0000&#10;CPU min MHz:                     800.0000&#10;BogoMIPS:                        7200.00&#10;Virtualization:                  VT-x&#10;L1d cache:                       128 KiB&#10;L1i cache:                       128 KiB&#10;L2 cache:                        1 MiB&#10;L3 cache:                        8 MiB&#10;NUMA node0 CPU(s):               0-7&#10;Vulnerability Itlb multihit:     KVM: Mitigation: Split huge pages&#10;Vulnerability L1tf:              Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable&#10;Vulnerability Mds:               Mitigation; Clear CPU buffers; SMT vulnerable&#10;Vulnerability Meltdown:          Mitigation; PTI&#10;Vulnerability Mmio stale data:   Mitigation; Clear CPU buffers; SMT vulnerable&#10;Vulnerability Retbleed:          Mitigation; IBRS&#10;Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp&#10;Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization&#10;Vulnerability Spectre v2:        Mitigation; IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affected&#10;Vulnerability Srbds:             Mitigation; Microcode&#10;Vulnerability Tsx async abort:   Mitigation; Clear CPU buffers; SMT vulnerable&#10;Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtop&#10;                                 ology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_&#10;                                 lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clf&#10;                                 lushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities</pre>
** Intel Core i7-6700 (quad-core 3.4 GHz, up to 4.0 GHz)
* Graphics
** Discrete: Intel Corporation HD Graphics 630 (rev 04)
** PCI: NVIDIA GeForce® GTX 1080 w/ 8GB GDDR5x
** Video Output:
*** 2 x DisplayPort 1.3 
*** 3 x HDMI 2.0 
** Max 4 displays at a time
* Storage
** 2.5“ SATA 6.0Gbps HDD/SSD bay
** M.2 PCIE x4 / SATA SSD slot (22/42,22/60,22/80)
** 3-in-1 SD/SDHC/SDXC SD Card Reader


For some reason, I had the following Linux kernel parameters set ( among others ) on this device for Ubuntu 16.04. I presume that some of this was necessary at one point:

<pre>...
splash fbcon=font:TER6x12 pcie_aspm=off i915.preliminary_hw_support=1 nouveau.modeset=0 snd_hda_intel.audio=1 vt.handoff=1
...
</pre>


==ChatGPT says...==

===Regarding <tt>i915.preliminary_hw_support=1</tt>:===
<i>
The Linux boot parameter i915.preliminary_hw_support=1 was used to enable early support for upcoming Intel graphics hardware in the i915 driver before the hardware was officially supported. This was often necessary for new graphics hardware that was not yet fully supported in the Linux kernel.

However, this boot parameter has been deprecated and removed in recent versions of the Linux kernel, and is no longer necessary or functional. As of kernel version 4.3, preliminary hardware support was enabled by default in the i915 driver, and as of kernel version 4.15, this boot parameter was completely removed.

This means that if you're using a modern version of the Linux kernel, you do not need to use this boot parameter, and it will have no effect if you do. Your Intel HD Graphics 630 should be fully supported by the i915 driver without needing any special boot parameters.

If you're having trouble with your graphics, you should ensure that your Linux kernel and your Mesa drivers are up-to-date, as these provide the most recent support for Intel graphics hardware.
</i>

===Regarding <tt>pcie_aspm=off</tt>:===
<i>
The Linux boot parameter pcie_aspm=off is used to disable Active State Power Management (ASPM) for PCI Express (PCIe) devices.

ASPM is a power management protocol that allows an operating system to save power by setting PCIe devices to low power states when they're not in use. There are two ASPM states: L0s, which reduces power when there's no data to transmit, and L1, which reduces power further when the device is idle.

However, ASPM can sometimes cause issues, including instability or reduced performance, especially on systems with older or non-compliant hardware. If you're experiencing such issues, you might use pcie_aspm=off to disable ASPM and see if that resolves the problem.

Keep in mind that disabling ASPM can potentially increase power consumption, so it's generally recommended to leave it enabled if you're not experiencing any issues.
</i>

===Regarding <tt>nouveau.modeset=0</tt>:===
<i>
The Linux boot parameter nouveau.modeset=0 is used to disable kernel mode-setting for the Nouveau driver, which is the open source graphics driver for Nvidia graphics cards.

Kernel mode-setting (KMS) is a method for setting resolution and depth in the framebuffer for graphics cards. It allows native resolution in the framebuffer and can provide a nice graphical boot sequence.

However, there can be occasions where you may want to disable KMS. For example, you might want to install proprietary Nvidia drivers instead of using the open-source Nouveau drivers. The proprietary drivers often offer better performance or compatibility, but cannot be used at the same time as Nouveau. In such cases, disabling Nouveau with nouveau.modeset=0 prevents it from loading at boot time, which allows the proprietary drivers to load instead.

After you have installed the proprietary drivers, you might want to blacklist the Nouveau drivers to prevent them from loading in the future. This is typically done by adding a line to a file in /etc/modprobe.d/ (e.g., /etc/modprobe.d/blacklist.conf) that reads blacklist nouveau.

Remember to be careful when modifying these settings, as they can affect the boot process and display of your system. Always make sure you have a way to undo your changes, such as by making a backup of any configuration files you modify.
</i>


===Regarding <tt>vt.handoff=1</tt>:===
<i>
The vt.handoff=1 boot parameter is specific to Ubuntu and its derivatives. It's related to the handoff between the bootloader and the kernel during the boot process, specifically concerning the virtual terminal (VT) settings.

When the system boots, the bootloader (GRUB, in the case of most Linux distributions) initializes the display to a particular mode. The vt.handoff parameter tells the kernel to continue using the same mode for the virtual console, creating a smooth transition without any flickering or mode changes.
<br>
Here's what the values of vt.handoff mean:
<br>
* vt.handoff=1 means the kernel should take over the current console settings from the bootloader.
* vt.handoff=7 is usually the default in Ubuntu, meaning the kernel should use tty7 (the seventh virtual console), which is where the X server usually displays the graphical user interface.
Please note that vt.handoff doesn't affect system performance or capabilities; it's primarily about aesthetics during booting.
</i>

=Troubleshooting=
==No Video==
If you are getting no video on any of the video output ports, here's what Zotac says:<br><br>
[https://www.zotac.com/ca/faq/video-card-will-not-show-anything Video Card will not show anything]
<i>

There may be a few reasons. This may be due to a compatibility issue. Check to make sure your motherboard BIOS is up to date. It can also be related to a power supply. Check your power supply to see if it meets the minimum power requirements. Check if the display cable is working correctly and also the monitor itself. You can also try reseating the graphics card onto the motherboard. If none of the above resolve the issue, please contact us.</i>
<br><br>
In my case, one of the power supplies ( the LEFT power socket when the device is viewed from the rear ) was not properly connected and the machine worked completely normally with the exception of not seeing the NVIDIA card at all. When that happened, dmesg output only mentioned the single integrated/discrete video adapter:<pre>jeremy@mediawhore ~ $ dmesg  | grep -i 'nvidia\|vga'&#10;&#10;[    0.299622] kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device&#10;[    0.299622] kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none&#10;[    0.299622] kernel: pci 0000:00:02.0: vgaarb: bridge control possible&#10;[    0.299622] kernel: vgaarb: loaded&#10;[    0.530457] kernel: fb0: VESA VGA frame buffer device&#10;[    1.520599] kernel: fb0: switching to inteldrmfb from VESA VGA&#10;[    1.520688] kernel: i915 0000:00:02.0: vgaarb: deactivate vga console&#10;[    1.522163] kernel: i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem</pre>

However, once the video card is properly seated and BOTH power supplies are properly connected AND the system is rebooted, you should see 2 distinct video devices mentioned in the dmesg output:<pre>jeremy@mediawhore ~ $ dmesg  | grep -i 'nvidia\|vga'&#10;&#10;[Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: setting as boot VGA device&#10;[Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none&#10;[Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: bridge control possible&#10;[Tue May 23 11:07:42 2023] vgaarb: loaded&#10;[Tue May 23 11:07:42 2023] fb0: VESA VGA frame buffer device&#10;[Tue May 23 11:08:20 2023] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client&#10;[Tue May 23 11:08:20 2023] nvidia-nvlink: Nvlink Core is being initialized, major device number 235&#10;[Tue May 23 11:08:20 2023] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem&#10;[Tue May 23 11:08:20 2023] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  440.82  Wed Apr  1 20:04:33 UTC 2020&#10;[Tue May 23 11:08:20 2023] nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms  440.82  Wed Apr  1 19:41:29 UTC 2020&#10;[Tue May 23 11:08:20 2023] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver&#10;[Tue May 23 11:08:20 2023] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0&#10;[Tue May 23 11:08:21 2023] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input3&#10;[Tue May 23 11:08:21 2023] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input4&#10;[Tue May 23 11:08:21 2023] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input5&#10;[Tue May 23 11:08:21 2023] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input6&#10;[Tue May 23 11:08:21 2023] input: HDA NVidia HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input7&#10;[Tue May 23 11:08:21 2023] input: HDA NVidia HDMI/DP,pcm=11 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input8&#10;[Tue May 23 11:08:21 2023] input: HDA NVidia HDMI/DP,pcm=12 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input9&#10;[Tue May 23 11:08:25 2023] audit: type=1400 audit(1684854506.625:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe" pid=2071 comm="apparmor_parser"&#10;[Tue May 23 11:08:25 2023] audit: type=1400 audit(1684854506.625:3): apparmor="STATUS" operation="profile_load" profile="unconfined" name="nvidia_modprobe//kmod" pid=2071 comm="apparmor_parser"</pre>