MAGNUS EN1080 10 Year Anniversary Edition (ZBOX-EN1080) - Revision history

Jeremy at 18:06, 19 February 2026

2026-02-19T18:06:35Z

← Older revision		Revision as of 18:06, 19 February 2026
Line 60:		Line 60:
	* Processor<br><pre>Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz Stepping: 9 CPU MHz: 3641.124 CPU max MHz: 4200.0000 CPU min MHz: 800.0000 BogoMIPS: 7200.00 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 1 MiB L3 cache: 8 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Mmio stale data: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Retbleed: Mitigation; IBRS Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affected Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Mitigation; Clear CPU buffers; SMT vulnerable 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 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_ 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 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>		* Processor<br><pre>Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz Stepping: 9 CPU MHz: 3641.124 CPU max MHz: 4200.0000 CPU min MHz: 800.0000 BogoMIPS: 7200.00 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 1 MiB L3 cache: 8 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Mmio stale data: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Retbleed: Mitigation; IBRS Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affected Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Mitigation; Clear CPU buffers; SMT vulnerable 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 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_ 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 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)		** Intel Core i7-6700 (quad-core 3.4 GHz, up to 4.0 GHz)
			* Memory
			** Type: DDR4 260-pin SO-DIMM 1.2V Non-ECC Dual channel
			** Supported Speed: DDR4-2400 MHz
			** Maximum Capacity: Up to 32GB total
			** Slots: 2 slots, max 16GB per slot
	* Graphics		* Graphics
	** Discrete: Intel Corporation HD Graphics 630 (rev 04)		** Discrete: Intel Corporation HD Graphics 630 (rev 04)

Jeremy at 04:50, 15 January 2026

2026-01-15T04:50:47Z

← Older revision		Revision as of 04:50, 15 January 2026
Line 143:		Line 143:

	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' [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: setting as boot VGA device [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: bridge control possible [Tue May 23 11:07:42 2023] vgaarb: loaded [Tue May 23 11:07:42 2023] fb0: VESA VGA frame buffer device [Tue May 23 11:08:20 2023] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client [Tue May 23 11:08:20 2023] nvidia-nvlink: Nvlink Core is being initialized, major device number 235 [Tue May 23 11:08:20 2023] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [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 [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 [Tue May 23 11:08:20 2023] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver [Tue May 23 11:08:20 2023] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0 [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 [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 [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 [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 [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 [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 [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 [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" [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>		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' [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: setting as boot VGA device [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: bridge control possible [Tue May 23 11:07:42 2023] vgaarb: loaded [Tue May 23 11:07:42 2023] fb0: VESA VGA frame buffer device [Tue May 23 11:08:20 2023] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client [Tue May 23 11:08:20 2023] nvidia-nvlink: Nvlink Core is being initialized, major device number 235 [Tue May 23 11:08:20 2023] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [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 [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 [Tue May 23 11:08:20 2023] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver [Tue May 23 11:08:20 2023] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0 [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 [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 [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 [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 [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 [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 [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 [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" [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>

			[[Category:Devices]]

Jeremy at 15:25, 23 May 2023

2023-05-23T15:25:17Z

← Older revision		Revision as of 15:25, 23 May 2023
Line 131:		Line 131:
	Please note that vt.handoff doesn't affect system performance or capabilities; it's primarily about aesthetics during booting.		Please note that vt.handoff doesn't affect system performance or capabilities; it's primarily about aesthetics during booting.
	</i>		</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' [ 0.299622] kernel: pci 0000:00:02.0: vgaarb: setting as boot VGA device [ 0.299622] kernel: pci 0000:00:02.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [ 0.299622] kernel: pci 0000:00:02.0: vgaarb: bridge control possible [ 0.299622] kernel: vgaarb: loaded [ 0.530457] kernel: fb0: VESA VGA frame buffer device [ 1.520599] kernel: fb0: switching to inteldrmfb from VESA VGA [ 1.520688] kernel: i915 0000:00:02.0: vgaarb: deactivate vga console [ 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' [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: setting as boot VGA device [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: VGA device added: decodes=io+mem,owns=io+mem,locks=none [Tue May 23 11:07:42 2023] pci 0000:01:00.0: vgaarb: bridge control possible [Tue May 23 11:07:42 2023] vgaarb: loaded [Tue May 23 11:07:42 2023] fb0: VESA VGA frame buffer device [Tue May 23 11:08:20 2023] snd_hda_intel 0000:01:00.1: Handle vga_switcheroo audio client [Tue May 23 11:08:20 2023] nvidia-nvlink: Nvlink Core is being initialized, major device number 235 [Tue May 23 11:08:20 2023] nvidia 0000:01:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=none:owns=io+mem [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 [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 [Tue May 23 11:08:20 2023] [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver [Tue May 23 11:08:20 2023] [drm] Initialized nvidia-drm 0.0.0 20160202 for 0000:01:00.0 on minor 0 [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 [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 [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 [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 [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 [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 [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 [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" [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>

Jeremy: /* Regarding vt.handoff=1: */

2023-05-23T14:58:17Z

Regarding vt.handoff=1:

← Older revision		Revision as of 14:58, 23 May 2023
Line 124:		Line 124:

	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.		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:		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=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.		* 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.		Please note that vt.handoff doesn't affect system performance or capabilities; it's primarily about aesthetics during booting.
	</i>		</i>

Jeremy: /* ChatGPT says... */

2023-05-23T14:55:54Z

ChatGPT says...

← Older revision		Revision as of 14:55, 23 May 2023
Line 116:		Line 116:

	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.		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.

			Here's what the values of vt.handoff mean:

			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>		</i>

Jeremy: /* Details */

2023-05-23T14:34:20Z

Details

← Older revision		Revision as of 14:34, 23 May 2023
Line 58:		Line 58:
	** nct6775<pre>coretemp-isa-0000 Adapter: ISA adapter Package id 0: +37.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +36.0°C (high = +80.0°C, crit = +100.0°C) Core 1: +36.0°C (high = +80.0°C, crit = +100.0°C) Core 2: +38.0°C (high = +80.0°C, crit = +100.0°C) Core 3: +35.0°C (high = +80.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C (crit = +119.0°C) temp2: +29.8°C (crit = +119.0°C) iwlwifi_1-virtual-0 Adapter: Virtual device temp1: N/A pch_skylake-virtual-0 Adapter: Virtual device temp1: +48.0°C</pre>		** nct6775<pre>coretemp-isa-0000 Adapter: ISA adapter Package id 0: +37.0°C (high = +80.0°C, crit = +100.0°C) Core 0: +36.0°C (high = +80.0°C, crit = +100.0°C) Core 1: +36.0°C (high = +80.0°C, crit = +100.0°C) Core 2: +38.0°C (high = +80.0°C, crit = +100.0°C) Core 3: +35.0°C (high = +80.0°C, crit = +100.0°C) acpitz-acpi-0 Adapter: ACPI interface temp1: +27.8°C (crit = +119.0°C) temp2: +29.8°C (crit = +119.0°C) iwlwifi_1-virtual-0 Adapter: Virtual device temp1: N/A pch_skylake-virtual-0 Adapter: Virtual device temp1: +48.0°C</pre>

	* Processor		* Processor<br><pre>Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian Address sizes: 39 bits physical, 48 bits virtual CPU(s): 8 On-line CPU(s) list: 0-7 Thread(s) per core: 2 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 158 Model name: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz Stepping: 9 CPU MHz: 3641.124 CPU max MHz: 4200.0000 CPU min MHz: 800.0000 BogoMIPS: 7200.00 Virtualization: VT-x L1d cache: 128 KiB L1i cache: 128 KiB L2 cache: 1 MiB L3 cache: 8 MiB NUMA node0 CPU(s): 0-7 Vulnerability Itlb multihit: KVM: Mitigation: Split huge pages Vulnerability L1tf: Mitigation; PTE Inversion; VMX conditional cache flushes, SMT vulnerable Vulnerability Mds: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Meltdown: Mitigation; PTI Vulnerability Mmio stale data: Mitigation; Clear CPU buffers; SMT vulnerable Vulnerability Retbleed: Mitigation; IBRS Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization Vulnerability Spectre v2: Mitigation; IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS Not affected Vulnerability Srbds: Mitigation; Microcode Vulnerability Tsx async abort: Mitigation; Clear CPU buffers; SMT vulnerable 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 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_ 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 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)		** Intel Core i7-6700 (quad-core 3.4 GHz, up to 4.0 GHz)
	* Graphics		* Graphics

Jeremy: /* Details */

2023-05-23T14:32:18Z

Details

@@ Line 11: / Line 11: @@
 ** [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]
 * Processor

Jeremy at 14:11, 23 May 2023

2023-05-23T14:11:00Z

@@ Line 15: / Line 15: @@
 ** Intel Core i7-6700 (quad-core 3.4 GHz, up to 4.0 GHz)
 * Graphics
-** NVIDIA GeForce® GTX 1080 w/ 8GB GDDR5x
+** Discrete: Intel Corporation HD Graphics 630 (rev 04)
-** Video Output 2 x DisplayPort 1.3
+** PCI: NVIDIA GeForce® GTX 1080 w/ 8GB GDDR5x
-** 3 x HDMI 2.0
+** Video Output:
-** max 4 displays
+*** 2 x DisplayPort 1.3
 * Storage
 ** 2.5“ SATA 6.0Gbps HDD/SSD bay
@@ Line 31: / Line 33: @@
 ...
 </pre>

Jeremy at 13:57, 23 May 2023

2023-05-23T13:57:23Z

← Older revision		Revision as of 13:57, 23 May 2023
Line 6:		Line 6:
	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.		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		* Resources
	** [https://www.zotac.com/se/product/mini_pcs/magnus-en1080-10-year-anniversary-edition Product Page]		** [https://www.zotac.com/se/product/mini_pcs/magnus-en1080-10-year-anniversary-edition MAGNUS EN1080 10 Year Anniversary Edition (ZBOX-EN1080) -- Product Page]
	** [https://www.zotac.com/mu/files/download/graphics_cards Driver Page] (~~named~~ "ZOTAC GeForce GTX 1080 ArcticStorm Thermaltake 10 Year Anniversary Edition")		** 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]		** [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]

Line 21:		Line 23:
	** M.2 PCIE x4 / SATA SSD slot (22/42,22/60,22/80)		** M.2 PCIE x4 / SATA SSD slot (22/42,22/60,22/80)
	** 3-in-1 SD/SDHC/SDXC SD Card Reader		** 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>

Jeremy: /* Details */

2020-05-13T22:23:40Z

Details

← Older revision		Revision as of 22:23, 13 May 2020
Line 5:		Line 5:

	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.		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 Product Page]
			** [https://www.zotac.com/mu/files/download/graphics_cards Driver Page] (named "ZOTAC GeForce 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]

	* [https://www.zotac.com/se/product/mini_pcs/magnus-en1080-10-year-anniversary-edition Product Page]
	* [https://www.zotac.com/mu/files/download/graphics_cards Driver Page] (named "ZOTAC GeForce GTX 1080 ArcticStorm Thermaltake 10 Year Anniversary Edition")
	* Processor		* Processor
	** Intel Core i7-6700 (quad-core 3.4 GHz, up to 4.0 GHz)		** Intel Core i7-6700 (quad-core 3.4 GHz, up to 4.0 GHz)