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

[Sebastian Roth]

@Matthieu-Jacquart Sorry, forgot to upload it! My fault. Here it is.

[Matthieu Jacquart]

@Sebastian-Roth ok, I’m at home now, I’ll test this on monday

[Matthieu Jacquart]

@Sebastian-Roth Ok, here it is :

When I launch boot command, nothing happens, it stays on this screen

[george1421]

@Matthieu-Jacquart While I don’t have an answer for you, this picture is interesting. The client requests the bzImage file and replies with file not found, but then a bit latter it does find the file. It does the same thing with the init. Eventually it does get down to boot and then stops.

It would be interesting to know what the apache logs look like at the same moments you get the above messages. I would inspect the apache error and access log. From the web server side does everything look normal where there is just three access requests for bzImage and then a few for the init? Or are there error messages logged in the apache error log?

This picture makes me ask more questions than it provides an aswer:
The question I have is the tablet not waiting long enough for the web server to respond with the file? Is there an error on the first few attempts and then it works? Is the web server slow to respond? Is your network connection faulty between the tablet and the web server?

I also noted a bug in the image request (not related to your issue). The last 2 parameters are missing a space between “consoleblank=0isdebug=yes” should be “consoleblank=0 isdebug=yes”

[Matthieu Jacquart]

@george1421 All error are my mistakes :

• I forgot blanck between “consoleblank=0 isdebug=yes”
• for replies “file not found”, I’ve just make error when I wrote the command. When it was weel written, it works immediately

I’m going to reproduce command without making mistakes

[Sebastian Roth]

@Matthieu-Jacquart Hmmm, looks interesting. But as George already said this seams to throw up even more questions. Please take a look at the apache error and access logs to see what happened at that point.

And there are more typos which probably don’t cause an issue at this stage yet but might later on: “rw” instead of “rz”, missing ‘/’ in “init=/sbin/init” and “root=/dev/ram0”.

Can you please post the ouput of the following commands on your FOG server:

ls -al /var/www/fog/service/ipxe/bzImage
ls -al /var/www/fog/service/ipxe/init.xz
file /var/www/fog/service/ipxe/bzImage

Just want to see if the filesizes match and what version that kernel is.

[Matthieu Jacquart]

@Sebastian-Roth I repeat ipxe shell command without error (I hope so…)

And for fog server command :

root@FOG:/opt/svn/trunk$ ls -al /var/www/fog/service/ipxe/bzImage
-rw-r--r-- 1 fog www-data 6883968 f▒vr.  1 08:06 /var/www/fog/service/ipxe/bzImage
root@FOG:/opt/svn/trunk$ ls -al /var/www/fog/service/ipxe/init.xz
-rw-r--r-- 1 fog www-data 18747540 f▒vr.  1 08:05 /var/www/fog/service/ipxe/init.xz
root@FOG:/opt/svn/trunk$ file /var/www/fog/service/ipxe/bzImage
/var/www/fog/service/ipxe/bzImage: Linux kernel x86 boot executable bzImage, version 4.4.0 (root@debian64) #2 SMP Mon Jan 25 12:44:48 EST 2016, RO-rootFS, swap_dev 0x6, Normal VGA

[Tom Elliott]

@Matthieu-Jacquart after that is all done, (init’s loaded and kernel loaded into memory) I think you need to type boot.

[Tom Elliott]

@Matthieu-Jacquart Also, could you try the loading without the init=/sbin/init part? I know you’re doing a ton of work, but I’m only working of a theory as to the corruption of the file during load up.

[Sebastian Roth]

@Matthieu-Jacquart So this looks good from my point of view. Sizes match and you have a very recent kernel image. Good on the one hand but we are still in a loss on why it just hangs on your machine. Looking at ways on how to get more output I found the linux kernel option earlyprintk. From what I read it needs to be enabled when compiling the kernel. Right now I am building one and will let you know about where to download and how to test it as soon as I have it ready.

[Matthieu Jacquart]

@Tom-Elliott I typed “boot” after init and kernel loaded, but it always stays on this screen, nothing change.

After that, I typed command without init=/sbin/init but it seems similar

and boot always gives same result (I mean nothing ;))

I can do all test you need, ideally in 2 weeks I had to have cloned these 32 tablet

[Sebastian Roth]

So here we go. The new kernel command line with added parameters should be like this (all the other things stay the same):

iPXE shell> kernel http://${next-server}/fog/service/ipxe/bzImage_epk debug earlyprintk=efi loglevel=7 initrd=init.xz init=/sbin/init root=/dev/ram0 rw ramdisk_size=127000 pcie_aspm=off consoleblank=0 isdebug=yes

See I added two more parameters (sorry for all the typing!). Here you find a kernel file called bzImage_epk. Please download this and put it in /var/www/fog/service/ipxe/ on your FOG server. Keep the different name so you don’t have to move around your normal kernel. In the command shown above you see it referenced as bzImage_epk as well. Give this a try please.

[Matthieu Jacquart]

@Sebastian-Roth OK done, but I saw no differences…

[Sebastian Roth]

@Matthieu-Jacquart Thanks a lot for all the testing and pictures! No output from the kernel whatsoever?! This is a really hard one we are tackling here. Looking through the iPXE source code again I might have found some more debugging options we could try. Download this iPXE binary (DEBUG=image_cmd,image,efi_image) and give it a try. Will bring you to the shell again. Just try the same commands as before.

[george1421]

@Sebastian-Roth Its interesting here, in that bzImage (I suspect) is getting corrupted, where in my test bzImage was getting downloaded but instead the root fs was being corrupted (somehow). Again this is only speculation, but it seems consistent with the bzImage or init not making it to the client correctly to be executed.

[Tom Elliott]

@george1421 maybe secure boot is blocking it?

[george1421]

@Tom-Elliott said:

@george1421 maybe secure boot is blocking it?

Good point since bzImage is an OS. The OP should check to see if secure boot is turned off, or even can be turned off.

[Matthieu Jacquart]

@Sebastian-Roth Ok, I think there are interesting things
Are the command ok for you ?

@Tom-Elliott @george1421 Secure boot is disable in bios, if not I couldn’t even boot on ipxe file

[Sebastian Roth]

@Matthieu-Jacquart At least we get some more information now. From what I can tell this looks all reasonable. shell.ipxe is detected as script and bzImage is detected as EFI binary. The message “format not recognized” seams kind of odd but makes sense when looking at the source code. I don’t know why the iPXE developers have it this way, but seams ok!
Just init.xz is not properly recognized. But again according to the source code that seams fine - see this comment in src/core/image.c:

        /* Try to detect image type, if applicable.  Ignore failures,
         * since we expect to handle some unrecognised images
         * (e.g. kernel initrds, multiboot modules, random files
         * provided via our EFI virtual filesystem, etc).
         */

So what I am wondering about is what happens when you run the boot command after this? Do you see any more debug messages (you should from what I see in the code)? Please try and wait at least for 5 minutes to see if anything happens. As well you might want to try the bzImage_epk binary (plus debug earlyprintk=efi parameters) again.

[Matthieu Jacquart]

@Sebastian-Roth Ok, I forgot to tell you but after taking pictures I’ve entered boot command and waited at least15 minutes, nothing happens
I’m going to test with bzImage_epk