be like this. system on> wait till armed (button 1 of key fob) > armed> do alarm stuff
2019-05-17 07:05
S2600WF服务器主板和R2000WF系列服务器的TPS在附录B（分别为120和125页）中提供了诊断LED解码器，如下所示。我有一个客户报告POST失败，视频显示器上显示“32”，琥珀色：ON ON ON关闭绿色：ON ON ON在后部诊断LED上看到关闭。POST进度代码示例表（相同页面）表示该错误是十六进制代码EE（或二进制1110 1110）。但是，在随后的页面中，没有在TPS中描述的错误代码EE（或二进制1110 1110）。以上来自于谷歌翻译以下为原文 The TPS for the S2600WF server board and the R2000WF series servers offer, in Appendix B (pages 120 and 125, respectively), a diagnostic LED decoder., as shown below.I have a customer who reports POST fails, with a "32" on the video display, and Amber : ON ON ON off Green: ON ON ON off seen on the rear diagnostic LEDs.The POST progress code example tables (same pages) indicates that's a error hex code EE (or binary 1110 1110).However, in the pages which follow, there is no error code EE (or binary 1110 1110)described in either TPS.
2018-11-19 14:20
时，channel_up、land_up初始化结束的信号一直是“0”，将user_clk作为采样时钟，显示"waiting for force to be armed, slow or stopped
2015-03-09 10:58
嗨英特尔支持团队， 美好的一天， 我对英特尔服务器主板S2600CW2SR有一些疑问。 根据检查此URL，Ubuntu 16.04包含了基本安装：https：//www.intel.sg/content/www/xa/en/support/articles/000006988/server-products/server-boards.html我是否知道是否包含芯片组和板载驱动程序的安装而不仅仅是安装Ubuntu 16.04？ 如果是，我们是否可以获得有关如何安装英特尔服务器主板S2600CW2SR驱动程序的链接和步骤？请告诉我们。 希望快速回应。以上来自于谷歌翻译以下为原文Hi Intel Support Team,Good day,I have some questions regards with Intel Server board S2600CW2SR.Basic installation was included for Ubuntu 16.04 as per checking to this URL:https://www.intel.sg/content/www/xa/en/support/articles/000006988/server-products/server-boards.html May I know if installation of Chipset and onboard drivers are included and not just installing Ubuntu 16.04?If yes, may we have the link and procedure on how to install the drivers for Intel Server board S2600CW2SR? Please advice us.Hoping for quick response.
2018-11-16 11:25
Bios没有看到系统盘。我通过clonezilla设置图像并出现磁盘。安装系统后，磁盘不会出现在BOOT部分。我尝试从Legacy和UEFI开始。 Plz谁可以帮忙解决这个问题？对不起，我的英语不好。info.png 97.6 K.以上来自于谷歌翻译以下为原文Bios does not see the system disk.I set the image through the clonezilla and the disk appears.After installing the system, the disk does not appear in the section BOOT. I try to start with Legacy and UEFI. Plz who can help in this matter? Sorry for my bad english. info.png 97.6 K
2018-10-17 11:57
大家好...我在使用PowerShell与我的Intel AMT设备进行通信时遇到问题。它之前一直工作得很好，但现在我得到一个Schannel错误70（协议错误）我想这是因为Intel AMT不再支持TLS 1.0了。我怎样才能让poweshell模块再次运行？客户端的AMT版本为12.0.6，FW为12.0.6.1120请指教/海涅以上来自于谷歌翻译以下为原文Hi All... I'm having issues using powershell to communicate with my Intel AMT devices.It's been working just fine before, but now i get a Schannel error 70 (protocol error) I guess it's because of Intel AMT not supporting TLS 1.0 any longer. How can i get the poweshell module to work again?The AMT version on the client is 12.0.6 and FW is 12.0.6.1120 Please advice /Heine
2018-10-24 15:18
PCIe规范定义了3种类型的AtomicOps事务：“AtomicOps的架构适用于设备到主机，设备到设备和主机到设备的交易。”如果英特尔®至强®处理器可扩展系列支持Pcie AtomicOps主机到设备交易？这个问题的背景是它在之前的Xeon代中看起来，只支持PCIe AtomicOps设备到主机的事务：“Intel Xeon处理器E7 V2系列支持PCIe原子操作（作为完成者）”。不确定Scalable系列是否使用基于X86 ISA的指令扩展了对主机到设备的支持？以上来自于谷歌翻译以下为原文PCIe spec defined 3 types of AtomicOps transactions:"AtomicOps are architected for device-to-host, device-to-device, and host-to-device transactions." If Intel® Xeon® Processor Scalable Family support Pcie AtomicOps host-to-device transactions? The background for this question is it looks in previous Xeon generation, only PCIe AtomicOps device-to-host transactions are supported: "The Intel Xeon processor E7 V2 family supports PCIe atomic operations (as a completer)". Not sure if Scalable family extend the support to host-to-device using X86 ISA based instructions?
2018-10-15 11:23
is set, e.g. if even out endpoint is armed and SETUP token is received by SIE, UIR.TRNIF will be set
2019-05-27 14:19
我有一台带有Intel S1200SPS服务器主板的新服务器。我在RAID 1虚拟磁盘上安装了Server 2016，它是在RAID BIOS（ESRT II）中使用双三星EVO 250GB SSD安装的。 RAID还配置了额外的RAID 1虚拟驱动器，包含2个2 TB的WD Gold驱动器，用于数据存储。它运行正常，直到我把它发送给我的客户。主板在运输中损坏，（不会启动POST）所以我用相同的型号替换它，我使用硬件诊断检查所有其他组件，包括三星SSD诊断和WD Lifeguard以确保没有其他任何损坏（正在一定不要影响驱动器上的数据）。诊断是在一个单独的系统上执行的，我可以单独读取驱动器，操作系统和文件都在那里。重新组装系统后，我重新配置BIOS以使用RAID for SATA，因为它是一个新的主板，重新设置RAID 1虚拟驱动器，并将SSD RAID对设置为ESRT II BIOS中的可启动。我对两个RAID虚拟驱动器进行了一致性检查，结果很好，修复了不一致性。然后我将BIOS设置为从RAID阵列启动。在这一点上，我认为它会像原来一样启动。但是，Windows无法识别RAID驱动器，因此无法启动。当我进入恢复模式命令提示符时，虚拟驱动器根本不可用（未在wmic logicaldisk列表中列出）。我希望你以前英特尔公司做过这类事情并且有一个技巧可以帮助我让Server 2016重新启动，而不必浪费时间安装和配置服务器和其他软件。有任何想法吗？以上来自于谷歌翻译以下为原文I have a new server with the Intel S1200SPS server mainboard.I installed Server 2016 on a RAID 1 virtual disk, which was setup in the RAID BIOS (ESRT II) with dual Samsung EVO 250GB SSD's.The RAID was also configured with an additional RAID 1 virtual drive of 2 2-TB WD Gold drives for data storage. It was working fine until I shipped it out to my client.The mainboard was damaged in shipping, (would not power up to POST) so I replaced it with the same exact model,I checked all other components using hardware diagnostics, including Samsung SSD diagnostics and WD Lifeguard to be sure nothing else was damaged (being sure not to affect data on the drives).The diagnostics was performed on a separate system, and I could read the drives individually, that the OS and files are there. After re-assembling the system, I reconfigured the BIOS to use RAID for SATA, and because it's a new mainboard, re-setup the RAID 1 virtual drives, and setting the SSD RAID pair as bootable in the ESRT II BIOS.I did a consistency check on both RAID virtual drives, which went well, fixing inconsistencies.I then set the BIOS to boot from the RAID Array.At this point, I figured it would boot up as originally.However, windows doesn't recognize the RAID drives, and so won't boot up.When I got into recovery mode command prompt, the virtual drives are not available at all (not listed in the wmic logicaldisk list). I'm hoping you Intel guys have done this type of thing before and have a trick up your sleeve to help me get Server 2016 to boot again and not have to lose the hours of time spent installing and configuring Server and other software.Any ideas?
2018-10-31 15:50
limit IN's // EP8AUTOINLENL = 0x00; // SYNCDELAY; // out endpoints do not POR (power-on reset) armed
2019-04-26 14:43
