HP Elitebook failure to network boot HELP



  • Let me start by saying I’m the noobs noob. I downloaded and installed ubuntu 11.10 and Fog 0.32 a couple of years ago and have never had any major problems whatsoever, until now. I have about 150 various HP desktops and latops that I use Fog image creation and deployment on right out of the box so I haven’t had a need to learn any linux. The problem is this. I have 14 Hp Elitebook 8530w that I image very often but I have 1 that I cannot image at all. It freezes at some point during the pxe boot and then after about 30 seconds the screen goes to a complete random color blur. I think that I might might need to tweek the boot file but I have no idea what where or how. Help


  • Moderator

    When you select an option from the PXE menu, such as Full Host Registration and Inventory, FOG always uses the default bzImage. After a host is registered, you can specify which kernel to use for all tasks created and scheduled through the FOG web UI. If you have to manage multiple bzImage files for compatibility reasons, use the “Host kernel” setting for each host to specify the kernel that works best for that system. You can also group hosts, and update all host kernel settings for particular group of hosts. Just remember that groups in FOG 0.32 are a bit unusual. They are used for changing settings on all hosts in the group, but will not show your existing group settings.



  • I can confirm that this kernel also works for the HP Elitedesk 800 G1 SFF



  • [quote=“Jaymes Driver, post: 25225, member: 3582”]Then you undo your command
    [code]
    mv bzImage bzImage.orig.2014APR01
    [/code]
    which backed up your current bzImage to bzImage.orig.2014APR01.

    So first back up your new kernel
    [code]
    mv bzImage bzImage.new.2014APR10
    [/code]
    then run this command
    [code]
    mv bzImage.orig.2014APR01 bzImage
    [/code]
    and all will be well.[/quote]

    Thanks,
    As soon as i get a break in the workflow i’ll give this a shot!

    K


  • Developer

    Then you undo your command
    [code]
    mv bzImage bzImage.orig.2014APR01
    [/code]
    which backed up your current bzImage to bzImage.orig.2014APR01.

    So first back up your new kernel
    [code]
    mv bzImage bzImage.new.2014APR10
    [/code]
    then run this command
    [code]
    mv bzImage.orig.2014APR01 bzImage
    [/code]
    and all will be well.



  • Just playing the devils advocate here. You state that it “will work on many systems” and I won’t dispute that; but, what if it doesn’t work on all of the different HP models that I have to work with? Just trying to find out what step to take to revert to the previous, or at the moment, current kernel before going forward. I’ve been working on computers for long enough to know that the unexpected often jumps up and bites you in the butt. As soon as I know how to return to the original kernel, I’ll use your kernel.

    Thanks
    K


  • Senior Developer

    You don’t need to do anything.

    This kernel will work on many systems.

    Yes, mv is sort of like rename. However it’s more in depth than that.



  • I take it the mv command is similar to a Windows “rename” command. After imaging with your kernel, how do I get back to my normal imaging solution?


  • Senior Developer

    Try my kernel. On the fog server as the root user in a terminal run these commands:
    [code]cd /tftpboot/fog/kernel
    mv bzImage bzImage.orig.2014APR01
    wget -O bzImage --no-check-certificate https://mastacontrola.com/fogboot/kernel/bzImage32[/code]


Log in to reply
 

457
Online

39010
Users

10725
Topics

101895
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.