PXE Boot HP X2 210 (Hybrid tablet Windows 10 Pro)

[Matthieu Jacquart]

@george1421
@Sebastian-Roth
I increase FOG_KERNEL_LOGLEVEL to 7 and activate FOG_KERNEL_DEBUG, which log can I look at after ?

I can boot on ubuntu live USB, it works perfectly

[george1421]

@Matthieu-Jacquart My intent was to not send you in 20 directions all at once. But since a live boot works, once you get the debugging information for the devs, it would be interesting to know what the output of lsblk and lspci -m are.

[Tom Elliott]

How about we get:

ls -lart /var/www/fog/service/ipxe/{bzImage{,32},init{,_32}.xz}

First.

I’m still guessing these files didn’t download properly last time.

[Sebastian Roth]

@Matthieu-Jacquart There is no log file. You will see more output on the screen when your tablet boots up - if so. But maybe you won’t see any more information. Can you boot other clients properly? Just asking to make sure your kernel/inits are fine.

[Matthieu Jacquart]

@Tom Elliott
ls -lart /var/www/fog/service/ipxe/{bzImage{,32},init{,_32}.xz} on fog server give me

root@FOG:~$ ls -lart /var/www/fog/service/ipxe/{bzImage{,32},init{,_32}.xz}
-rw-r--r-- 1 fog www-data 16476332 janv. 21 08:22 /var/www/fog/service/ipxe/init.xz
-rw-r--r-- 1 fog www-data 15448272 janv. 21 08:23 /var/www/fog/service/ipxe/init_32.xz
-rw-r--r-- 1 fog www-data  6847456 janv. 21 08:23 /var/www/fog/service/ipxe/bzImage
-rw-r--r-- 1 fog www-data  6759504 janv. 21 08:23 /var/www/fog/service/ipxe/bzImage32

@Sebastian-Roth Yes other client works perfectly, I deploy image yesterday and no problem. I didn’t see more output when I tried to boot on tablet

@george1421 Ok I’ll give you the result of command on Monday, for now I’m at home

[Tom Elliott]

At least now I know it’s not bad downloaded files and what not.

[Wayne Workman]

@george1421 said:

@Matthieu-Jacquart My intent was to not send you in 20 directions all at once. But since a live boot works, once you get the debugging information for the devs, it would be interesting to know what the output of lsblk and lspci -m are.

I’ll reiterate this. This is easy to get and important to know.

[Sebastian Roth]

@Matthieu-Jacquart Hope we’re not asking too many things here from you. But would it be possible to take a short video of the whole bootup process. Sometimes there are small hints that we only see if we have it right in front of our eyes…

[george1421]

@george1421 said:

… it would be interesting to know what the output of lsblk and lspci -m are.

Thinking about this a bit more, it would also be interesting to know what modules are loaded by what kernel modules were loaded by the live boot OS. You would use lsmod and probably direct the output into a file.

[Matthieu Jacquart]

Ok guys, I’ll give you this on monday
I hop to find a solution, It seems so close to boot properly on fog server !

[Matthieu Jacquart]

@Tom-Elliott @Wayne-Workman @george1421 @Sebastian-Roth

OK, let’s go : Video link (really sorry for quality !!!) : https://youtu.be/ob_5qC7KRqs

For test with (Ubuntu 14.04 LTS Live) : something strange, in file explorer ubuntu just see it’s own file system and USB key, but not internal HDD (windows 10 partitions). If I use live USB key on another computer with SSD, Ubuntu displays Windows partitions (Windows 7)

ubuntu@ubuntu:~$ lsblk 
NAME		MAJ:MIN	RM	SIZE		RO	TYPE	MOUNTPOINT 
sda			8:0    	1   	7.4G  	0 	disk 
└─sda1 		8:1    	1   	7.4G  	0 	part 		/cdrom 
sdb			8:16   	1   	7.4G  	0 	disk 
└─sdb1		8:17   	1   	7.4G  	0 	part          /media/ubuntu/54BF-F230 
loop0		7:0    	0 	962.1M  	1 	loop 		/rofs 
mmcblk0rpmb  	179:24   	0    	4M  		0 	disk 
mmcblk0boot0 	179:8    	0     	4M  		1 	disk 
mmcblk0boot1 	179:16   	0     	4M  		1 	disk 
mmcblk0      	179:0    	0  	58.2G  	0 	disk 
├─mmcblk0p1  179:1    	0   	260M  	0 	part 
├─mmcblk0p2  179:2    	0   	128M  	0 	part 
├─mmcblk0p3  179:3    	0  	57.1G  	0	part 
└─mmcblk0p4  179:4    	0   	746M  	0 	part 

ubuntu@ubuntu:~$ lspci -m 
00:00.0 "Host bridge" "Intel Corporation" "Device 2280" -r22 "Hewlett-Packard Company" "Device 8173" 
00:02.0 "VGA compatible controller" "Intel Corporation" "Device 22b0" -r22 "Hewlett-Packard Company" "Device 8173" 
00:03.0 "Multimedia controller" "Intel Corporation" "Device 22b8" -r22 "Hewlett-Packard Company" "Device 8173" 
00:0a.0 "Non-VGA unclassified device" "Intel Corporation" "Device 22d8" -r22 "Hewlett-Packard Company" "Device 8173" 
00:0b.0 "Signal processing controller" "Intel Corporation" "Device 22dc" -r22 "Unknown vendor 7270" "Device 8086" 
00:14.0 "USB controller" "Intel Corporation" "Device 22b5" -r22 -p30 "Hewlett-Packard Company" "Device 8173" 
00:1a.0 "Encryption controller" "Intel Corporation" "Device 2298" -r22 "Hewlett-Packard Company" "Device 8173" 
00:1c.0 "PCI bridge" "Intel Corporation" "Device 22c8" -r22 "" "" 
00:1f.0 "ISA bridge" "Intel Corporation" "Device 229c" -r22 "Hewlett-Packard Company" "Device 8173" 
01:00.0 "Network controller" "Intel Corporation" "Device 3165" -r81 "Intel Corporation" "Device 4010" 

ubuntu@ubuntu:~$ lsmod 
Module                  Size  Used by 
dm_crypt               24576  0 
intel_rapl             20480  0 
intel_powerclamp       20480  0 
coretemp               16384  0 
hp_wmi                 16384  0 
sparse_keymap          16384  1 hp_wmi 
kvm                   479232  0 
crct10dif_pclmul       16384  0 
crc32_pclmul           16384  0 
ghash_clmulni_intel    16384  0 
aesni_intel           172032  0 
aes_x86_64             20480  1 aesni_intel 
lrw                    16384  1 aesni_intel 
gf128mul               16384  1 lrw 
glue_helper            16384  1 aesni_intel 
ablk_helper            16384  1 aesni_intel 
cryptd                 20480  3 ghash_clmulni_intel,aesni_intel,ablk_helper 
iwlwifi               188416  0 
joydev                 20480  0 
cfg80211              524288  1 iwlwifi 
snd_intel_sst_acpi     16384  0 
snd_soc_rt5670        106496  0 
dm_multipath           24576  0 
snd_intel_sst_core     73728  1 snd_intel_sst_acpi 
snd_soc_rt5640         94208  0 
snd_soc_sst_mfld_platform    77824  1 snd_intel_sst_core 
snd_soc_rl6231         16384  2 snd_soc_rt5640,snd_soc_rt5670 
scsi_dh                16384  1 dm_multipath 
snd_soc_core          196608  3 snd_soc_rt5640,snd_soc_rt5670,snd_soc_sst_mfld_platform 
lpc_ich                24576  0 
snd_compress           20480  1 snd_soc_core 
snd_pcm_dmaengine      16384  1 snd_soc_core 
i915_bpo             1130496  3 
btusb                  40960  0 
i2c_hid                20480  0 
snd_pcm               106496  5 snd_soc_rt5640,snd_soc_rt5670,snd_soc_core,snd_soc_sst_mfld_platform,snd_pcm_dmaengine 
snd_seq_midi           16384  0 
snd_seq_midi_event     16384  1 snd_seq_midi 
mei_txe                20480  0 
mei                    90112  1 mei_txe 
snd_rawmidi            32768  1 snd_seq_midi 
shpchp                 40960  0 
snd_seq                65536  2 snd_seq_midi_event,snd_seq_midi 
snd_seq_device         16384  3 snd_seq,snd_rawmidi,snd_seq_midi 
snd_timer              32768  2 snd_pcm,snd_seq 
intel_ips              20480  1 i915_bpo 
drm_kms_helper        126976  1 i915_bpo 
snd                    86016  8 snd_soc_core,snd_timer,snd_pcm,snd_seq,snd_rawmidi,snd_soc_sst_mfld_platform,snd_seq_device,snd_compress 
drm                   344064  5 i915_bpo,drm_kms_helper 
dw_dmac                16384  0 
8250_fintek            16384  0 
soc_button_array       16384  0 
pwm_lpss_platform      16384  0 
soundcore              16384  1 snd 
dw_dmac_core           24576  1 dw_dmac 
i2c_designware_platform    16384  0 
int3400_thermal        16384  0 
rfkill_gpio            16384  0 
bnep                   20480  2 
i2c_algo_bit           16384  1 i915_bpo 
rfcomm                 69632  8 
spi_pxa2xx_platform    24576  0 
pwm_lpss               16384  1 pwm_lpss_platform 
i2c_designware_core    16384  1 i2c_designware_platform 
8250_dw                16384  0 
int3403_thermal        16384  0 
acpi_thermal_rel       16384  1 int3400_thermal 
processor_thermal_device    16384  0 
iosf_mbi               16384  1 intel_rapl 
bluetooth             491520  22 bnep,btusb,rfcomm 
parport_pc             32768  0 
mac_hid                16384  0 
pinctrl_cherryview     32768  2 
acpi_pad               20480  0 
ppdev                  20480  0 
lp                     20480  0 
parport                45056  3 lp,ppdev,parport_pc 
squashfs               49152  1 
overlay                45056  1 
nls_iso8859_1          16384  2 
dm_mirror              24576  0 
dm_region_hash         24576  1 dm_mirror 
dm_log                 20480  2 dm_region_hash,dm_mirror 
uas                    24576  0 
usb_storage            69632  3 uas 
hid_generic            16384  0 
usbhid                 53248  0 
hid                   110592  3 i2c_hid,hid_generic,usbhid 
mmc_block              36864  0 
video                  20480  1 i915_bpo 
wmi                    20480  1 hp_wmi 
sdhci_acpi             16384  0 
sdhci                  45056  1 sdhci_acpi 

[george1421]

While I’m not sure what this means at this moment, this disk structure does look interesting. Unless I’m reading this wrong (likely) it appears you have 2 or 3 hard drives in this device.

mmcblk0rpmb     179:24      0       4M          0   disk 
mmcblk0boot0    179:8       0       4M          1   disk 
mmcblk0boot1    179:16      0       4M          1   disk 
mmcblk0         179:0       0   58.2G   0   disk 
├─mmcblk0p1  179:1      0       260M    0   part 
├─mmcblk0p2  179:2      0       128M    0   part 
├─mmcblk0p3  179:3      0   57.1G   0   part 
└─mmcblk0p4  179:4      0       746M    0   part 

[Matthieu Jacquart]

mmcblk0 seems to be internal SSD with the different Windows 10 partitions, and sda1 / sdb1 were 2 USB keys

[george1421]

Where I’m confused is this.

I understand that mmcblk0 is a physical disk and it has 4 partitions. I’m good with that. But the concern (in my mind) is what is mmcblk0rpmb, mmcblk0boot0, mmcblk0boot1 which also appear to be disks and how will fog deal with them. I might suspect that mmcblk0rpmb is the firmware of this device, and then there are two disks for the boot code, maybe a primary and a backup (??) But that is only a guess.

The question would be will this confuse the fog boot kernel? I guess we will need the fog devs to answer on that one.

[Tom Elliott]

@george1421 mmcblk0rpmb is not used at all -> kernels that we have published actually prevent this disk from being seen. The only other part that may be a bit “weird” is the boot0/boot1 disks, but those aren’t even read in in the case of resizable images.

[george1421]

@Tom-Elliott From what it sounds like something is not allowing the fog client OS to boot. One thought was that it couldn’t enumerate the disks or something similar, but that is only a very uneducated guess.

[Tom Elliott]

@george1421 I understand, I was just giving information pertinent to your prior posting.

Though I will have to add, mmc disks are actually working, so if it’s stuck on the disk it would be a bit odd. From the sounds of it, it’s either stuck (meaning maybe just taking longer to load – I’m guessing you’ve waited more the 2-5 minutes with the same results?), or impatience.

[Wayne Workman]

I suppose the simple things have been checked, for instance removing any extra storage devices like SD cards and MicroSD cards ?

[Matthieu Jacquart]

@Wayne-Workman Yes, there’s just internal SSD and RJ45 adapteur
@Tom-Elliott I’ve been waiting much more than 5 minutes, around 1 hour, and still nothing…

Something interesting, I have some error message when I choose boot from hard disk or memtest86 :

Just testing with last svn / kernel 4.4, same trouble

[george1421]

@Matthieu-Jacquart If you are willing and have a general knowledge of linux, I would like you to try something.

I’ve been working on an idea about booting the FOG Client kernel (the bits of FOG code that run on the target computer to load or capture images) using a usb drive. Understand this is only for debugging purposes. Right now it is not clear in my mind if the booting issues with these newer efi based systems are with the PXE boot kernel, the FOG Client kernel, or the hand off between ipxe and the FOG kernel.

To test this I wrote a document to create a uefi boot media that will boot the fog kernel from USB. You can not capture or deploy using this kernel only access command line tools. But the point of this exercise is to see if it boots, period.

If you have a spare 2GB or larger usb flash drive, are comfortable with some linux commands and have a little time; could you follow the instructions outlined here: https://forums.fogproject.org/topic/6532/usb-boot-target-device-into-fog-debug-os/3

For the sake of the test, I only want you to execute what appears id method #3. Understand these instructions were written for ubuntu, but they should translate to debian without issue ( ) . At the bottom there is a copy and paste section where you can copy the commands paste them into a text editor, change the reference to the usb flash drive and then just execute the commands one after another through a remote terminal. It takes me less and 5 minutes to execute the commands once you have the apt-get files installed.

For the flash drive start with a freshly formatted flash drive using a windows computer and format it fat32 (note the first step of my instructions tells linux to reformat the drive, any existing content will be lost). If you have any questions about this, please post back here.

What I want to test:

1. Does it boot?
2. IF it doesn’t boot is there an error message?
3. Does this image boot on any other device you have that is in uefi mode?

After this test we will add in the grub insmod commands and test again. But first lets see if you can build the boot drive and get it to boot on this table as is.