Archive for the ‘Hardware’ Category
Posted by jpluimers on 2022/03/24
For my link archive: [Wayback] MSI Z77A-G43 support and downloads
Note that Windows 10 does not seem to need additional drivers, even Wake-on-LAN works with the stock Windows 10 drivers (but does require two BIOS settings and three Windows driver settings, see [Wayback] Wake-on-LAN (WoL) | MSI HQ User-to-User FAQ.
Max processor information based on the below links.
- Max processor that supports VT-d (for virtualisation), but no manual overclocking: i7 3770.
- Max processor that supports manual overclocking, but not VT-d: i7 3770K
From:
Via: [Wayback] MSI Z77A-G43 – Kenmerken – Tweakers
–jeroen
Posted in Hardware, Mainboards, MSI, Power User, Z77A-G43 | Leave a Comment »
Posted by jpluimers on 2022/03/23
[Wayback] msi hq user-to-user faq: wake on lan (wol) by Author Ruudt Swaanen on 3 May, 2017, paraphrased by me:
- In the BIOS:
- Under “Settings -> Advanced -> Power Management Setup”, disable the option “EuP 2013” (my mainboard) or “ERP Ready”.
Disabling this function will keep the LAN port enabled when the system is put to Sleep (S3) or in Shutdown (S5) mode.
Enabling this function will use less power (see [Wayback] What is EuP 2013? | Overclock.net)
- Under “Settings -> Wake Up Event Setup”, enable the option “Resume By PCI or PCI-E Device” (my mainboard) or “Resume by LAN”.
- In the Windows 10 Control Panel, (
control.exe) with an Administrator elevation token):
- In the “Power Options” Control Panel applet (
powercfg.cpl), under “Choose what the power buttons do”, disable the option “Turn on fast startup (recommended)”.
On many MSI based machines, the option “Turn on fast startup (recommended)” interferes with Wake-on-LAN.
- In the “Device Manager” (
devmgmt.msc), under your network adapter change these options (the naming slightly differs per vendor/model; below is for generic Realtek PCIe GBE):
- On the “Power Management” tab, enable these options:
- “Allow this device to wake the computer”
- “Only allow a magic packet to wake the computer”
- On the “Advanced” tab, enable these options:
- “Wake on Magic Packet”
- “Wake on pattern match”
- On the “Advanced” tab, set this value:
- “WOL & Shutdown Link Speed” is “10 Mbps First”
Now test in these global Power States:
- S5 “soft off” (the state where there is a power cord connected, but none of the fans spin)
- S4 “hibernating” (if you have turned that on in the power options)
- S3 “sleeping”
This worked well for S3 and S5 (but not S4) on my MSI Z77A-G43 based Windows 10 PC and only required stock network driver for the “Realtek PCIe GBE Family Controller” shown in the Device Manager (devmgmt.msc) and you can find on [Wayback] Microsoft Update Catalog: Realtek PCIe GBE Family Controller Driver.
For more Wake on LAN blog posts, including how to initiate a Wake-on-LAN request, see the category Wake-on-LAN (WoL).
–jeroen
Posted in Hardware, Mainboards, MSI, Power User | Leave a Comment »
Posted by jpluimers on 2022/03/22
Hey macOS desktop in the basement, thanks for going to sleep while I was in the middle of typing at you via SSH.
Maybe that should be a signal not to sleep, eh?
$ sudo wakeonlan ac:87:a3:19:7e:81
Sending magic packet to 255.255.255.255:9 with
Well, at least that works.
Related:
–jeroen
Posted in Hardware, Network-and-equipment, Power User, Tailscale, VPN, Wireguard | Leave a Comment »
Posted by jpluimers on 2022/03/08
Since this is what I use to VPN home:
pfSense is a free and open source firewall and router that also features unified threat management, load balancing, multi WAN, and more
[Wayback] Download pfSense Community Edition: [Wayback] pfSense-CE-2.5.1-RELEASE-amd64.iso.gz
–jeren
Posted in Internet, pfSense, Power User, routers | Leave a Comment »
Posted by jpluimers on 2022/03/07
It looks like some X9 and X10 Supermicro boards already support PCIe bifurcation (splitting of PCIe slots into multiple channels), which might be worth a try to upgrade some of my older rigs to use NVMe instead of SATA storage as it will allow me to use adapters that support multiple NVMe devices into a single PCIe slot.
The X9 motherboards uses an LGA 2011-R socket, and the X10 motherboards an LGA 2011-R3 sockets.
Both use chipsets not being that different: the X9 uses the C600 series (which are similar to the X79 consumer series), and the X10 uses the C610 series (which are similar to the X99 consumer series).
This is what I found out about the bifurcation support for my boards:
References:
–jeroen
Posted in Hardware, Mainboards, Power User, SuperMicro, X10SRH-CF, X9SRi-3F, X9SRi-F | Leave a Comment »
Posted by jpluimers on 2022/03/02
Sometimes you come across old systems that do not support UEFI booting, so for memory testing you need tools that either are embedded on something like a Linux image that os in MBR, or the plain ISO download of older versions.
I opted for the latest “older” version 4.3 of MemTest86 [Wayback]:
As MemTest86 V9 supports only the newer UEFI platform, older PCs without UEFI support would be unable to boot MemTest86. In order to run MemTest86, PCs with legacy BIOS platform must use the older V4 release of MemTest86. The download links for the V4 downloads are still provided for those that prefer to work with the V4 bootable images.
| V4 Windows Downloads: |
Download |
| Image for creating bootable CD |
[Wayback] Download |
| Image for creating bootable USB Drive |
[Wayback] Download |
| Image for creating bootable Floppy Drive |
[Wayback] Download |
| V4 Linux/Mac Downloads: |
Download |
| Image for creating bootable CD |
[Wayback] Download |
| Image for creating bootable USB Drive |
[Wayback] Download |
| Image for creating bootable Floppy Drive |
[Wayback] Download |
–jeroen
Posted in DELL-9200, Hardware, HP XW6600, Memory, Power User | Leave a Comment »
Posted by jpluimers on 2022/02/18
Some interesting tidbits to reset a UE55MU6100 or similar TV from [Wayback/Archive.is] We have a 2 week old Samsung mu6100 55″ tv which up until an:
- Soft reset: Unplug the TV from the wall, hold down the power button on the rear of the TV for 10 seconds, then plug it back in and turn it on.
- The power button is on the backside : it’s the middle part of the 4-arrow-button.
- Factory reset: power off the TV, and hold down up, down and power buttons together for about 10 seconds, then releasing them when the Samsung Logo shows up.
- Reset to engineer menu: put the TV in standby, then press the info, menu, mute and power buttons on the remote
–jeroen
Posted in 4K Monitor, Displays, Hardware, Home Audio/Video, LifeHacker, MU6100, Power User, Samsung TV | Leave a Comment »
Posted by jpluimers on 2022/02/11
You can still get foam and foil for your old keyboard switches:
Via:
–jeroen
Posted in Keyboards and Keyboard Shortcuts, LifeHacker, Power User | Leave a Comment »
Posted by jpluimers on 2022/02/03
I installed three Samsung 980 Pro NVMe SSD devices in various ESXi rigs.
This is the serial numbers that ESXi came up with:
- Local NVMe Disk (t10.NVMe____Samsung_SSD_980_PRO_1TB_________________E824B311B1382500)
- Local NVMe Disk (t10.NVMe____Samsung_SSD_980_PRO_1TB_________________782DB311B1382500)
- Local NVMe Disk (t10.NVMe____Samsung_SSD_980_PRO_1TB_________________6F2DB311B1382500)
ESXi presents the serial number (actually the EUI64) in reverse byte order of what is on the device labels.
I had to look up what EUI64 was, and it is a kind of UUID (see Universally unique identifier – Wikipedia), but for hardware devices:
- World Wide Name – WikipediaEach WWN is an 8- or 16-byte number, the length and format of which is determined by the most significant four bits, which are referred to as an NAA (Network Address Authority). The remainder of the value is derived from an IEEE OUI (or from Company Id (CID)) and vendor-supplied information. Each format defines a different way to arrange and/or interpret these components. OUIs are used with the U/L and multicast bits zeroed, or sometimes even omitted (and assumed zero). Though CID has U/L set to 1.The WWN formats include:…
- “Mapped EUI-64” formats manage to fit an EUI-64 address into an 8-byte WWN. Since the NAA is mandatory, and takes up a nibble, this represents a four-bit deficit. These four bits are recouped through the following tricks: First, two bits are stolen from the NAA by allocating NAAs 12, 13, 14, and 15 to all refer to the same format. Second, the remaining two bits are recouped by omitting the U/L and multicast bits from the EUI-64’s OUI. When reconstructing the embedded EUI-64 value, the U/L and multicast bits are assumed to have carried zero values.
…
- [Wayback] Base NVM Express – Part One – NVM Express
A namespace ID (NSID) is an identifier used by a controller to provide access to a namespace (handle to a namespace). An NVMe controller may support multiple namespaces that are referenced using NSID. EUI64 (8 bytes), NGUID (16 bytes) and UUID (128-bit) are globally unique namespace identifiers defined in the Base Specification.
- [Wayback] VMware Docs: NVMe Devices with NGUID Device Identifiers
For NVMe devices, ESXi generates device identifiers based on the information it retrieves from the devices. Generally, the NVMe devices support identifiers in EUI64 or NGUID formats, or use both formats. NGUID is a Namespace Globally Unique Identifier that uses the EUI64 16-byte designator format.
- [Wayback] ESXI6.7 nvme ssd issue – VMware Technology Network VMTN
Being a software engineer, I am disturbing by the way this software create the disk ID.
According to the following table from VMware Docs we have some case that the software will not recognize the disk or lost disks.
| ID Formats Supported by Device |
Device Identifier Generated by Host |
| EUI64 ID Format |
NGUID ID Format |
ESXi 6.7 and earlier |
ESXi 6.7 Update 2 |
| yes |
yes |
t10.xxx_EUI64 |
t10.xxx_EUI64 |
| yes |
no |
t10.xxx_EUI64 |
t10.xxx_EUI64 |
| no |
yes |
t10.xxx_controller_serial_number |
eui.xxx (NGUID) as primary ID
t10.xxx_controller_serial_number as alternative primary ID
|
so what if
- The NVMe SSD from the same company may use the same EUI64 for every NVMe SSD on the same interface (say using an ASUS Hyper M.2 X16 PCIe 3.0×4 Expansion card with 4 identical NVMe SSD). It is possible because of bad design from the SSD manufacturer, the EUI64 are all the same for the 4 NVMe SSD, under this case, the ESXI will only recognized one of the 4 disks (since the disk will be t10.xxx_EUI64, and EUI64 are the same for all 4 NVMe SSD, The “storage” “adapters” tab did show there are 4 interfaces (adapters), but the “stroage” “devices” will only show 1 disks.
- Why there is no “no, no” options?
I understand that the NVMe standard 1.3 (for ESXi 6.7) is the base of how the NVMe SSD should be designed, but I think the software should be smart enough to cover the mistakes the hardware company may make and so it can recognized most of the NVMe SSD that is available from the market.
…
I have the same issue in V7.0! Whatever happened to using something you know is unique like serial numbers or something based off the serial number!
My two identical NVMe drives show up as one! Very odd how this one got through testing!
…
Having same issue with the Asus hyper x16 m. 2 pcie card. I have 4 Intel 660p in it and it’s only showing 1. Even when I changed the bifurcation to x4x4x4x4 for that pcie slot. It actually show nothing. When in auto it shows 1. I’m using esxi 7 though. Trying to test out VMware horizon but esxi not detecting all the nvme in the Asus adapter.
- [Wayback/Archive.is] linux.kernel: [PATCH 0/7] Implement NVMe Namespace Descriptor Identification
This patchset implemets NVMe Namespace Descriptor Identification as of
NVMe 1.3. The Namespace Descriptor Identification allows a NVMe host
to query several Namespace Identification mechanisms, such as EUI-64,
NGUID and UUID from the target. If more than one value is set by the
target, it can transmit all set values to the host.
- [Wayback] OS-6042: Need to handle NVMe devices with EUI64 values (SmartOS + ZFS)
NVMe devices with namespaces with an EUI64 value do not attach to the system. It’d be good if these did.
- [Wayback] ⚙ D19905 bhyve: Add EUI64 to NVMe device (FreeBSD)
Add the EUI64 field (part of the Identify Namespace data) to NVMe devices to support UEFI drivers.
The implementation will accept an IEEE Extended Unique Identifier (EUI-64) from the command line. If one isn’t provided, it will create one based on
- [Wayback] nvme-scsi: Use correct byte ordering for eui64 in Dev ID VPD – Patchwork
NVME specifies an EUI64/NGUID in little-endian format, while SCSI
specifies that the Device Identification VPD use big-endian for EUI
formats. The current code copies this bytestream directly from the
Identification Namespace page, meaning we just need to reverse the
bytestream when passing it on to the VPD.
…
This seems to hold true for NGUID devices, but Keith just pointed out to
me that it may not hold true for EUI64 devices. It seems like that case
needs byte swiveling within each field. So I'll NAK for now until I can
figure out if that's the case.
…
This will break existing setups that rely on VPD 0x83 for device
identification (which I think includes older SuSE distros).
And once you change the setup anyway please stop using this buggy
SCSI emulation.
…
- [Wayback] A Quick Tour of NVM Express (NVMe)
…
- nguid, Namespace Globally Unique Identifier (NGUID) and, eui64, IEEE Extended Unique Identifier (EUI64) are assigned when the namespace is created and preserved across namespace and controller operations (e.g. reset, format).
…
These are pictures of the devices in the same order:
Read the rest of this entry »
Posted in ESXi6.5, ESXi6.7, Hardware, NVMe, Power User, SSD, Virtualization, VMware, VMware ESXi | Leave a Comment »
The Wiert Corner - irregular stream of stuff 