another init.xz issue


  • Moderator

    @bmaster001 said in another init.xz issue:

    @george1421 said in another init.xz issue:

    What is your dhcp server?

    We use the dhcp server in pfsense 2.2.

    Sorry to get stuck on this, but you are sure in pfsense that you have the next server pointint to your new FOG server?

    I see there are three different models. Which one do you have? What OS did it come with.

    I don’t know where you see those 3 models, but we have a model with an Intel Atom E3826, 8 GB ram, and “Windows 7 Pro Emb” on it. The bios mentions “Phoenix SecureCore Technology”, and is at version HVM3036.

    It appears that there are different hardware configurations for the different OS versions (disk size and such). I got the impression that the CPU also changed with the OS (WinCE vs WinPro). But maybe I was mistaken.

    Don’t boot the system just yet. While I’m trying to find a use case for USB Booting FOS, I don’t think we are at that point just yet.



  • @Wayne-Workman said in another init.xz issue:

    @bmaster001 Understand this is only temporary, you’ll want to set it back to defaults afterwards.

    Web Interface -> FOG Configuration -> FOG Settings -> FOG Boot Settings -> FOG_KERNEL_DEBUG and FOG_KERNEL_LOGLEVEL

    Ok, I did that. What should be the result? The capture-task hangs again at the same point (init.xz…ok). Nothing new is displayed during the process :-/



  • @bmaster001 Understand this is only temporary, you’ll want to set it back to defaults afterwards.

    Web Interface -> FOG Configuration -> FOG Settings -> FOG Boot Settings -> FOG_KERNEL_DEBUG and FOG_KERNEL_LOGLEVEL



  • @Wayne-Workman said in another init.xz issue:

    I think it’s kernel related because of the new hardware. Sounds like the kernel isn’t even starting right.

    Can you boot it to a live linux disk successfully? If you can, what is the output of lsblk and lspci ? You could also turn up fogs kernel debug level so that maybe we see some errors.

    Working on downloading some linux to try booting it from usb. Meanwhile, is turning up the kernel debug level something I can try easily?



  • @Sebastian-Roth said in another init.xz issue:

    @bmaster001 While I am still unsure if those two topics are related I found that Could not select: Exec format error part very interesting. Lately we had at least two people who’s devices wouldn’t boot but print that message after loading the kernel/init.xz. In those cases it was some kind of security chip that needed to be disabled in the BIOS/UEFI firmware. See here and in the wiki. I really hope you find this to be the issue/solution. Otherwise we need to start unpacking the heavy tools for debugging this. Let me know.

    There are not many options in the bios (see screenshots). The “secure boot activation” is disabled (and grayed-out, so I can’t even activate it). Is that the option we are looking for?

    1_1465992475339_IMG_20160615_140221.jpg 0_1465992475338_IMG_20160615_140200.jpg



  • @george1421 said in another init.xz issue:

    What is your dhcp server?

    We use the dhcp server in pfsense 2.2.

    I see there are three different models. Which one do you have? What OS did it come with.

    I don’t know where you see those 3 models, but we have a model with an Intel Atom E3826, 8 GB ram, and “Windows 7 Pro Emb” on it. The bios mentions “Phoenix SecureCore Technology”, and is at version HVM3036. That’s pretty much everything I can find at the moment. I don’t want to boot the preinstalled Windows yet, because I want to capture it as it is, so that I can deploy it again if I mess up :-)

    Concerning your comment about an old ipxe kernel being used: I did a fresh install of fog on a fresh installed centos. I think it downloads the latest kernels during the installation?


  • Moderator

    @Sebastian-Roth Could not select: Exec format error right, that makes me think that an old ipxe kernel is being used. This is like the issue where people are using pxelinux.0 of yesteryear trying to boot bzImage and inits not mounting. I know different error but that is what the error tells me that the bzImage or in this case memdisk is not understood.

    This hardware is a bit different too, why I asked about what model was in use. Some come with Windows CE with an atom processor, others with win7, win10 with different processors. The hard drive setup is a bit confusing to me too. This IS an interesting bit of hardware, though.


  • Developer

    @bmaster001 While I am still unsure if those two topics are related I found that Could not select: Exec format error part very interesting. Lately we had at least two people who’s devices wouldn’t boot but print that message after loading the kernel/init.xz. In those cases it was some kind of security chip that needed to be disabled in the BIOS/UEFI firmware. See here and in the wiki. I really hope you find this to be the issue/solution. Otherwise we need to start unpacking the heavy tools for debugging this. Let me know.


  • Moderator

    What is your dhcp server?

    I checked into this hardware and this is what I would call an industrial computer, its not a normal desktop/laptop. That is OK, I just need to set the framework for what we are dealing with.

    I see there are three different models. Which one do you have? What OS did it come with.

    At this point we are far from out of choices with this unit. I just want to make sure your environment is setup correctly then we can dive into the specific hardware.



  • I think it’s kernel related because of the new hardware. Sounds like the kernel isn’t even starting right.

    Can you boot it to a live linux disk successfully? If you can, what is the output of lsblk and lspci ? You could also turn up fogs kernel debug level so that maybe we see some errors.


Log in to reply
 

347
Online

6.2k
Users

13.6k
Topics

127.9k
Posts