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

[Matthieu Jacquart]

@Tom-Elliott Oh, my English is too bad to well understand…
I can access to the fog menu with the hybrid, but only with efi file. And after fogmenu, I can’t launch any options : I’ve got error with options “boot on hard drive” and “memtest”

and for other options (quick image, or quick / full registration), screen stay black.

[Tom Elliott]

@Matthieu-Jacquart Want to hit me up on chat and maybe we can teamviewer?

[george1421]

@Matthieu-Jacquart It looks like the grub.cfg is not formatted properly. For now I will sit down and wait to see what Tom is able to do for you.

[Matthieu Jacquart]

@george1421 Do you think I made a mistake ?
I can try to do usb key once again ?

[george1421]

@Matthieu-Jacquart From the error it sounds like something is confused in the grub.cfg file only. I would check to see if there isn’t something missing in that file.

[Matthieu Jacquart]

@george1421 ok, I plug usb key on another computer and I had same result

[george1421]

@Matthieu-Jacquart

Sorry I was not clear, busy morning here.

What you need to do is to look at the configuration of the /boot/grub/grub.cfg file on the flash drive. You can edit this on a windows computer or via linux. I’m suspecting that this file is either missing (you skipped a step) or the structure is not what grub expects. If you still can’t get it to work, I have a captured image on my home computer that I can post tonight. That way all you have to do is to write it to a flash drive and there are no other steps that are needed.

[Matthieu Jacquart]

@george1421 Indeed, there is no grub.cfg in boot/grub…
27/01/2016 09:33 <DIR> i386-efi
27/01/2016 09:35 <DIR> locale
27/01/2016 09:33 <DIR> fonts
27/01/2016 09:33 <DIR> x86_64-efi
27/01/2016 09:33 1 024 grubenv
27/01/2016 09:35 <DIR> i386-pc

But there’s a grub.efi in EFI/boot folder

I’m going to home, work day finish for me, I’ll continue tests tomorrow !

[george1421]

@Matthieu-Jacquart OK, I will have something for you in the morning, cheers.

[sarge_212]

Just FYI, I had to manually make the grub.cfg file. Running grub-install on an ubuntu box didn’t make the grub.cfg file as expected.

[george1421]

@sarge_212 said:

Just FYI, I had to manually make the grub.cfg file. Running grub-install on an ubuntu box didn’t make the grub.cfg file as expected.

Yes this is expected. The bash script posted here will create the complete image file without having to mess around with running this and editing that.
https://forums.fogproject.org/topic/6532/usb-boot-target-device-into-fog-debug-os/19
But it does require having all of the grub2 files downloaded either through yum or apt-get as you would need if you manually executed the files. Understand this process is still under development but it works for me, as they say.

[Matthieu Jacquart]

@george1421 Hi George
Not sure to understand, you will sent me the grub.cfg file, or you want me to test your new script ?
Thanks
Matthieu

[Sebastian Roth]

I think George meant you better create grub.cfg config yourself and put it in /boot/grub/grub.cfg
Here is his example config:

set timeout=10
set default=0
insmod all_video

menuentry "FOG 32-bit Debug Kernel" {
 linux  /boot/bzImage32 loglevel=7 init=/sbin/init root=/dev/ram0 rw ramdisk_size=127000 pcie_aspm=off consoleblank=0 isdebug=yes
 initrd /boot/init_32.xz
}

menuentry "FOG 64-bit Debug Kernel" {
 linux  /boot/bzImage loglevel=7 init=/sbin/init root=/dev/ram0 rw ramdisk_size=127000 pcie_aspm=off consoleblank=0 isdebug=yes
 initrd /boot/init.xz
}

[Matthieu Jacquart]

@Sebastian-Roth
Ok thanks, that’s good.
Here it is :

[george1421]

@Matthieu-Jacquart Success!! this is good news at least the FOG debug OS will run on this tablet.

Please boot this tablet again using this flash drive. Make sure the usb etherent adapter is plugged in and connected to your network. When you get this screen in your picture, press enter a few time. This should give you a command prompt. Then key in ip addr show Hopefully it should show you a correct IP address for the usb ethernet adapter. If it does then the FOG debug OS sees that ethernet adapter and it can communicate with the network. If you can get to this point where the fog kernel is running and can talk on the network you have passed part two requirement. Since you are getting the fog menu you have already passed part one of the requirement to pxe boot.

If this is successful we need to identify why the hand off between ipxe (not created by the fog project) and the fog kernel is giving you a blank screen. You might want to do a refresh (update) of the fog environment since this post is a few days old. There has been many updates to fog and I believe the fog kernel too. It may now work with the updates.

[Matthieu Jacquart]

@george1421 ok, command “ip addr show” gives me result for usb ethernet adapter :

I updated my fog server each day, including this morning, but no change for blank screen…

[george1421]

@Matthieu-Jacquart OK the fog kernel has passed with success. Now we need to identify why the ipxe handoff to the fog kernel is giving us a black screen. At this point I don’t have an answer. When I get to the office, I will try to see if I can find a system that does this.

@Sebastian-Roth Do you know the git version of ipxe that is currently deployed with the FOG trunk? I just checked the rom-o-matic and it has version d0bfd (which is different than yesterday morning)

[Sebastian Roth]

Great stuff. So we know the kernel is fine. Funny that this is true for most of those new devices but we are still not sure why hand off from iPXE to the kernel does not work nicely.

Please try as George suggested to see if our client kernel is able to see and use your USB NIC. But if it does not, then this is a different issue as the initial black screen after the FOG menu. Not sure which one we should address first. Well let’s see. Hopefully you see if getting an IP.

So if you get some time you might want to test this ipxe.efi file with debugging for kernel image loading enabled (DEBUG=image_cmd). There might be lots of messages (in colors) scrolling past. Or maybe nothing. We will see how this behaves on your device. Please take a picture or video if you can (readable test is important!).

[Matthieu Jacquart]

@Sebastian-Roth
What do you mean with “Please try as George suggested to see if our client kernel is able to see and use your USB NIC” ?

I’ve just renamed 1454065283074-ipxe.efi as ipxe.efi and put it in tftpboot, check “FOG_KERNEL_DEBUG” in fog settings, but no difference, always blank screen after loding kernel.bz and init.xz…

[Sebastian Roth]

@Matthieu-Jacquart Sorry, didn’t see you posted a picture already. So forget what I said about George’s suggestion. Network looks good!
Too bad that we don’t see anything even with his debug enabled ipxe.efi binary. Well then lets try another way. Here is a different ipxe.efi file which brings you to the iPXE shell. Then try the following commands. Hope I got this all right. Sorry for all the typing involved but hopefully we might see some kind hint where things go wrong.

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

Question is, what do you see after imgstat? Please take a picture. Then you can try booting it using the command boot.