Menu

#10 Imaging Low Memory Devices

v1.0 (example)
closed
nobody
None
5
2014-04-06
2010-01-30
Christopher
No

I'm currently working on a solution to image Hp Thin Client Models t5725 and t5525 using FOG. I have been able to successfully image the t5725 Thin Clients that are runing Windows Embedded Standard (WES) and have 1 GB RAM. However I have run into a standstill on the t5525 model. The t5525 is running a linux based OS on it and only has 128 MB RAM. I can boot to the PXE menu fine and select any of it's options, but when it goes to loading bzImage and initrd it errors stating Kernel Panic - Not Enough Memory to Load Image. I am assuming this is correct due to that the device only has 128 MB RAM.

I have been able to successfully image the t5525 model using Altiris using it's PXE server. It seems that in the Altiris image process when the thin client pxe boots it loads into a FreeDos environment and then the image is dumped to the thin client. Can I do something like this using FOG? Maybe by editing the pxeboot menu and providing the necessary tools there. Any advice and input is appreciated.

Discussion

  • Christopher

    Christopher - 2010-02-10

    I found this link that refers to what I am trying to do.
    http://www.fogproject.org/wiki/index.php?title=Am_I_able_to_modify_the_PXE_menu_to_run_other_applications%3F
    However, I can not use nettbootdisk to do what I am wanting. I read that default security on Windows 2003 networks will prevent the netbootdisk tool from working. Which seems to be accurate because I can pxe boot to netbootdisk but when i try to map a share, or even do a net view all I get are errors. Is there a different tool that I can use other than netbootdisk to boot to DOS and map a windows network share?

    Here is what I am trying to do.
    -PXE boot to DOS
    -Map a network drive that contains an executable and the image of my thin client
    -running this executable will push the thin client image to the thin client I have pxe booted from

    The image file is saved as IMAGE.dd perhaps I do not even need to boot to the windows share to run the executable to push the image. Is there something else that I can do with the PXE boot menu to just dump the IMAGE.dd file to the thin client. Can you somehow make dd run from the pxe boot menu, so that it just dumps the IMAGE.dd file to the thin client?

    Please help.

     
  • Christopher

    Christopher - 2010-02-10
    • priority: 5 --> 9
     
  • microleaks

    microleaks - 2010-03-19

    Can you try lowing the value for: FOG_KERNEL_RAMDISK_SIZE in for settings, regenerate the pxe boot menu and try again.

     
  • microleaks

    microleaks - 2010-03-19
    • status: open --> pending
     
  • Christopher

    Christopher - 2010-03-29
    • priority: 9 --> 5
    • status: pending --> open
     
  • Christopher

    Christopher - 2010-03-29

    I have lowered the FOG_KERNEL_RAMDISK_SIZE and regenerated the pxe boot menu. But I am still getting " Kernel panic - not syncing: Out of memory and no killable processes."

     
  • Christopher

    Christopher - 2010-03-29

    The thin client only has 128 MB RAM. I thought there was a limit to pxe booting and that it was 256 MB.

     
  • mastacontrola

    mastacontrola - 2014-04-06

    If you're still working on this issue, I'd recommend updating to the latest FOG if at all possible.

    It's memory usage at roll out might go upwards of 60MB which should fit perfectly in your systems here.

     
  • mastacontrola

    mastacontrola - 2014-04-06
    • status: open --> closed
    • Group: --> v1.0 (example)
     

Log in to post a comment.