Hardware Currently Working with FOG v1.x.x

TheKoR · Apr 21, 2015, 12:25 PM

I have the same problem with Lenovo S20. And it seems that an hidden partition is created by the computer, ghost, fog, and clonezilla don’t work with this machine (SAS, Classical SATA, SSD)

Wayne Workman · Apr 21, 2015, 12:47 PM

dumb Lenovos.

TheKoR · May 12, 2015, 12:24 PM

Fujitsu - M470 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep
Fujitsu - R570-2 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep - Work with additionnal card or custom ipxe (no drivers in the actuals) UP/DOWN
Fujitsu - R650 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep
Fujitsu - W380 - Workstation - Win7 - 1.3.0 - 11/05/15 - Single - Resizable - No sysprep - Work Down with custom image from virtualisation - Don’t work UP (“corrupted gzip stream”)
Lenovo - S20 - Workstation - 7 - 1.3.0 - 12/05/15 - Single - Resizable - Don’t work before 1.3.0

raulalrocks · May 14, 2015, 12:58 PM

Hello Wayne,

As suggested, I have tried a new fog setup with Ubuntu 14.04 64 bit Server and Fog 1.2.0.

What happens now is, as before, the host registers fine and also image upload is fine as well.

But when deploying the image, it will show all initial steps and simply stuck in between and cursor continues to blink. I thought initially its doing some update and waited for further operations, but nothing happened. Eventually when hitting Enter key on the machine it started to deploy but the second HDD which is normal SATA 1 TB disk where as no imaging deployment happens with first HDD which is 180 GB SDD SATA HDD.

This happens only with Lenovo P700 models and all other models work fine. Request you help and thoughts

Attached is hardware details of Lenovo P700 workstations

Thanks in Advance,
Rahul S Lal

[url=“/_imported_xf_attachments/1/1995_LenovoP700.png?:”]LenovoP700.png[/url]

Tom Elliott · May 14, 2015, 2:19 PM

Those with lenovo’s please try updating to latest SVN.

I’m attempting to use the same methods as we use for GRUB, but for all MBR’s now. It will always load up the first Megabyte of MBR and reload that. Prior images should work as well. Theoretically it should work for OEM Lenovo’s too. SVN 3396 is the rev number in case you’re all wondering.

If anything else is broken, please let me know.

raulalrocks · May 15, 2015, 6:27 AM

Hi Tom,

Thanks for the update.

I am trying updating to latest SVN. @ [url]http://jbob.io/wiki/index.php/SVN[/url]

I get below error when I run the command “svn checkout [url]https://svn.code.sf.net/p/freeghost/code/trunk[/url]”

svn: E000104: Unable to connect to a repository at URL ‘[url]https://svn.code.sf.net/p/freeghost/code/trunk[/url]’
svn: E000104: Error running context: Connection reset by peer
Also tried with “svn co [url]https://svn.code.sf.net/p/freeghost/code/trunk[/url]”, above error returns.
I found that apt-get update works fine and proxy settings are OK.
Thanks in Advance,
Rahul S Lal

TheKoR · May 15, 2015, 8:08 AM

[quote=“Tom Elliott, post: 47392, member: 7271”]Those with lenovo’s please try updating to latest SVN.

I’m attempting to use the same methods as we use for GRUB, but for all MBR’s now. It will always load up the first Megabyte of MBR and reload that. Prior images should work as well. Theoretically it should work for OEM Lenovo’s too. SVN 3396 is the rev number in case you’re all wondering.

If anything else is broken, please let me know.[/quote]

Look my last post, in 3377 - S20 works !!

mspritch · May 28, 2015, 1:15 PM

We’re using DNSMASQ here to keep FOG away from our DHCP server, this highlights machines which, although they may work where FOG is on the DHCP server, don’t work where it’s split.

On the working ones iPXE will try to load default.ipxe from the PROXY IP (FOG server) address.
On the bad ones it will try to load default.ipxe from the DHCP IP address instead.

Updating the machine’s BIOS doesn’t seem to update the PXE loader, so doesn’t fix things.

I’ve upgraded to build 3482, which (apart from breaking PXE boot until I recreated the undionly.0 link) hasn’t made a difference. Kernel has been upgraded to 4.0.4, still no difference.

WORKING
Dell Latitude D630 (Broadcom UNDI PXE-2.1 v10.0.9)
Dell Latitude E5500 (Broadcom UNDI PXE-2.1 v11.4.1)
Dell Latitude E5510 (Broadcom UNDI PXE-2.1 v11.4.1)
Dell Optiplex 745 (Broadcom UNDI PXE-2.1 v10.0.9)
Dell Optiplex 755 (Intel Boot Agent GE v1.3.35)
Dell Optiplex 360 (Broadcom UNDI PXE-2.1 v11.4.1)
Dell Optiplex 380 (Broadcom UNDI PXE-2.1 v12.2.2)
HP rp5700 (HP Base Code PXE-2.1 v1.0.6)

UNSURE
Compaq 615 (Yukon PXE v6.50.2.3) (imaged OK on older build of FOG, now it drops into Windows instead of bringing up FOG menu)

NOT WORKING
Dell Optiplex 390 (Intel Base-Code, PXE-2.1 (build 083))
Dell Optiplex 3010 (Intel Base-Code, PXE-2.1 (build 083))
Dell Optiplex 3020 (Intel Base-Code, PXE-2.1 (build 083))
Fujitsu Esprimo E3521 (Intel UNDI, PXE-2.1 (build 083))
HP 500B MT (Intel UNDI, PXE-2.1 (build 083))

There seems to be a common theme amongst the ones that don’t boot properly, but I can’t quite put my finger on it…

Wayne Workman · May 28, 2015, 3:02 PM

@mspritch This information is greatly appreciated. I’ll work on updating the hardware lists.

Do you know if you’re using undionly.kkpxe or undionly.kpxe ?? What version of FOG were you using when you verified the working ones?

Tom Elliott · May 28, 2015, 9:57 PM

@mspritch Can you try using the SVN included intel.pxe file for those systems, or the undionly.kkpxe file?

mspritch · Jun 1, 2015, 5:20 PM

Up until last week we’ve been using a newer-than-1.2.0 build, but I’m not sure what (and whilst trying to dig out the build number I’ve just managed to update that build’s directory to v3500 so can’t tell what it was now). 3285 rings a bell.

We’re currently on 3484, upgraded when trying to troubleshoot these machines. I’ve just imaged a mix of Latitude D630s and E5500s plus Optiplex 745s, 755s and a 380, all using this build. The other ones listed as working all booted on this build so I suspect they’ll image as well (they imaged on earlier builds).

Been using undionly.kpxe, was also until recently using some mod I found somewhere that forced it to ask for the FOG server address before the menu loaded, but that didn’t work either. Can’t find a link to it now but it was on a FOG-related page, possibly something else by Tom?

Presumably because of the ProxyDHCP setup ours doesn’t work unless there’s an undionly.0 symbolic link set up in the tftpboot folder. I’ve added another entry to the PXE boot menu so I can test other KPXEs without trashing the working one, switching between them by pointing the test symlink (in my case intel.0) at the various kpxe files.

These tests were made on build 3484 using a HP 500B PC.
undionly.pxe: Clears the screen and drops to Reboot and Select proper Boot Device
undionly.kpxe: Picks wrong IP address, connection eventually times out
undionly.kkpxe: Same as undionly.kpxe
intel.efi: Hangs at a cursor (Caps Lock still responsive)
intel.pxe: After PXEXT it drops to Reboot and Select proper Boot Device
intel.kpxe: After PXEXT it drops to Reboot and Select proper Boot Device
intel.kkpxe: After PXEXT it gives a PXE-M0F Exiting PXE ROM.
ipxe.pxe: Same as undionly.kpxe
ipxe.kpxe: After listing the (correct) boot server IP it gives a PXE-E79 NBP is too big to fit in memory, then a PXE-M0F
ipxe.kkpxe: As above
realtek.pxe: Same as undionly.kpxe
realtek.kpxe: Same as undionly.kpxe
realtek.kkpxe: Same as undionly.kpxe

The HP’s supposed to be getting redeployed to a school but I’m happy to hang onto it for testing, there are always Optiplex 3010 and 3020 machines in the storeroom that I can do further testing on if need be.

mspritch · Jun 9, 2015, 11:38 AM

WORKING
Dell Optiplex 760
Intel onboard Gigabit Ethernet
Intel Boot Agent GE v1.3.81
4.0.4 kernel
9th June 2015
Resizeable

TheKoR · Jun 12, 2015, 2:01 PM

Don’t work
IBM R50
Dell D610
HP NC6120
Fujitsu C1320
All 4 can’t moun’t NFS - All IDE Drive

don’t work with this version but work in previous :

Dell D410

kasper · Jun 17, 2015, 1:32 PM

This does work
HP EliteBook 8760w
NIC Intel 82579LM
PXE 2.1
Laptop
Default Kernel
6/17/2015
Multiple Partition Image - Single Disk (Not Resizable)

Wayne Workman · Jun 17, 2015, 7:50 PM

@kasper said:

This does work
HP EliteBook 8760w
NIC Intel 82579LM
PXE 2.1
Laptop
Default Kernel
6/17/2015
Multiple Partition Image - Single Disk (Not Resizable)

Are you asking for help or just reporting???

TheKoR · Jul 13, 2015, 2:38 AM

don’t work with this version (3761) but work in previous :

HP D530 CMT - XP
Dell Latitude E5500 - Vista

ch3i · Jul 13, 2015, 8:54 AM

@TheKoR said:

don’t work with this version (3761) but work in previous :

HP D530 CMT - XP
Dell Latitude E5500 - Vista

Troll : T’es un mauvais c’est tout…

TheKoR · Jul 13, 2015, 9:09 AM

i think i remember it’s work with undi . intel, but not in place in new versions

Troll : je suis pas mauvais, mon cerveau est en vacances avec la chaleur !

Edit : try with the 3 intel, and still don’t work

TheKoR · Jul 20, 2015, 8:56 AM

don’t work with this version (3783) but work in previous :
hp nw9440 - XP - fail to mount nfs, and we try with all pxe.

same error than other older computers

TheKoR · Jul 30, 2015, 11:05 AM

8760w - windows 10 - svn 4266 - works fine up and down

Hardware Currently Working with FOG v1.x.x

231

12.0k

17.3k

155.2k