Registration Issues with Dell Precision 7720 and M.2 Sata
-
I have a fairly new laptop that I am trying to get registered with my system, but when I attempt to do a Full Host Registration, I get the following error:
I’ve tried changing the sata operation model from Intel Rapid Restore Technology to AHCI and reregistering the machine, but it just fails.
Does anyone have any thoughts on how I can get this machine working with FOG?
-
This is a really new system, its highly possible that linux doesn’t support it just yet.
Can you try this, manually register this device. Then schedule a manual deployment. It doesn’t matter what you deploy, the debug deployment will allow us to get access to the FOS console. Once at the command prompt on the target computer key in the following commands.
lspci -nnlsblkdf -h
Now I’ll give you a tip.
Before you do the above.
- At the linux prompt give root a password, just key in
passwdand give it any password hello will work. - key in the following command to get the ip address of the FOS (target) computer.
ip addr show - With those two bits of information you can use putty to connect to the target computer over the network. With putty its much easier to copy and paste screen shots then on the FOS console directly.
-
Here is the output of those commands.
lspci -nn --- 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5918] (rev 05) 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 05) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591d] (rev 04) 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 05) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) 00:17.0 RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 31) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #2 [8086:a111] (rev f1) 00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a154] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a171] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3] (rev 31) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1bb8] (rev a1) 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 04:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) 05:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) 05:01.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) 05:02.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) --- lsblk --- --- df -h --- Filesystem Size Used Avail Use% Mounted on /dev/root 103M 88M 9.7M 91% / ---EDIT:
Found this link that shows it’s at least supported in some way
look at #4 -
@bedcruncher said in Registration Issues with Dell Precision 7720 and M.2 Sata:
RAID bus controller [0104]: Intel Corporation SATA Controller [RAID mode] [8086:2822] (rev 31)
Well this is a good sign the rest are bad news. But lets work with this.
Is this a uefi system? I see that raid is enabled on this sata controller. If uefi = yes take the system out of raid mode and hopefully the
lsblkcommand will show us the block devices. When you switch out of raid mode the line I commented above will change from [raid mode] to something else. -
Can you confirm of this has a kaby lake chipset or sky lake?
@Developers it looks like the release date on the 7720 was in May 2017.
-
lspci -nn 00:00.0 Host bridge [0600]: Intel Corporation Device [8086:5918] (rev 05) 00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 05) 00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:591d] (rev 04) 00:04.0 Signal processing controller [1180]: Intel Corporation Skylake Processor Thermal Subsystem [8086:1903] (rev 05) 00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-H USB 3.0 xHCI Controller [8086:a12f] (rev 31) 00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Thermal subsystem [8086:a131] (rev 31) 00:15.0 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #0 [8086:a160] (rev 31) 00:15.1 Signal processing controller [1180]: Intel Corporation Sunrise Point-H Serial IO I2C Controller #1 [8086:a161] (rev 31) 00:16.0 Communication controller [0780]: Intel Corporation Sunrise Point-H CSME HECI #1 [8086:a13a] (rev 31) 00:17.0 SATA controller [0106]: Intel Corporation Sunrise Point-H SATA controller [AHCI mode] [8086:a102] (rev 31) 00:1c.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #2 [8086:a111] (rev f1) 00:1c.2 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #3 [8086:a112] (rev f1) 00:1c.4 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #5 [8086:a114] (rev f1) 00:1d.0 PCI bridge [0604]: Intel Corporation Sunrise Point-H PCI Express Root Port #9 [8086:a118] (rev f1) 00:1f.0 ISA bridge [0601]: Intel Corporation Sunrise Point-H LPC Controller [8086:a154] (rev 31) 00:1f.2 Memory controller [0580]: Intel Corporation Sunrise Point-H PMC [8086:a121] (rev 31) 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a171] (rev 31) 00:1f.4 SMBus [0c05]: Intel Corporation Sunrise Point-H SMBus [8086:a123] (rev 31) 00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (5) I219-LM [8086:15e3] (rev 31) 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation Device [10de:1bb8] (rev a1) 02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32) 03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI Express Card Reader [10ec:525a] (rev 01) 04:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) 05:00.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) 05:01.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) 05:02.0 PCI bridge [0604]: Intel Corporation JHL6340 Thunderbolt 3 Bridge (C step) [Alpine Ridge 2C 2016] [8086:15da] (rev ff) 3d:00.0 Non-Volatile memory controller [0108]: Toshiba America Info Systems Device [1179:0115] (rev 01) lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:0 0 477G 0 disk |-nvme0n1p1 259:1 0 500M 0 part |-nvme0n1p2 259:2 0 128M 0 part |-nvme0n1p3 259:3 0 475.9G 0 part `-nvme0n1p4 259:4 0 473M 0 part df -h Filesystem Size Used Avail Use% Mounted on /dev/root 103M 88M 9.7M 91% /I am thinking it has the skylake chipset at least from the line
00:01.0 PCI bridge [0604]: Intel Corporation Skylake PCIe Controller (x16) [8086:1901] (rev 05) -
@bedcruncher Sweet. lsblk now sees the nvme disk.
The skylake kabylake was an after thought as I was looking up the specs on the 7720.
Now that lsblk can see the disk give it a shot again with imaging.
-
It’s now uploading an image, but to make this more straightforward without having to make the bios changes every time. I will have to probably rebuild the base image without the Intel Raid mode turned on just to prevent it messing with the OS.
-
@bedcruncher It should image ok without raid mode enabled.
We use a boot usb flash drive to install a consistent bios in a winpe environment. During image we use cctk in the winpe environment to adjust the bios settings. This way we have a consistent configuration when the device leaves our buildup area.
let me check on something…
-
@george1421
Can you provide me a link explaining a bit more about that?
Both the boot usb, and cctk? -
There is… (said with a zest of a 5 year old girl)
http://en.community.dell.com/techcenter/enterprise-client/w/wiki/7532.dell-command-configure
cctk for linux. So in theory we could use a FOG custom task to configure the bios. But then we would need to reboot after the configuration for the firmware to reconfigure for the new settings… that may add more complications then fix. But it IS interesting for post imaging ensuring that the bios settings are right.
-
Sorry I had to go to a meeting.
If you are using the dell cctk kit with windows or in a winpe boot drive you can issue a command like this
cctk.exe bootorder --enabledevice=hdd,embnic,usbdev --disabledevice=floppy,cdromto modify the boot order or change other things in the bios. I think we can do the same thing in fog using the linux version and a post install script. It won’t address your issue (that has to be done before FOS boots) but it could provide some interesting options. -
@george1421
Yeah… I understand the whole meeting thing. Sucks to start working on something and constantly get pulled away on other less interesting things.I’ll look at that article and see what I can do to integrate it into my processes.
Will report back when I have more information to share.
