Hardware Currently Working with FOG v1.x.x
-
[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 !!
-
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…
-
@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?
-
@mspritch Can you try using the SVN included intel.pxe file for those systems, or the undionly.kkpxe file?
-
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.kpxeThe 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.
-
WORKING
Dell Optiplex 760
Intel onboard Gigabit Ethernet
Intel Boot Agent GE v1.3.81
4.0.4 kernel
9th June 2015
Resizeable -
Don’t work
IBM R50
Dell D610
HP NC6120
Fujitsu C1320
All 4 can’t moun’t NFS - All IDE Drivedon’t work with this version but work in previous :
Dell D410
-
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) -
@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???
-
don’t work with this version (3761) but work in previous :
HP D530 CMT - XP
Dell Latitude E5500 - Vista -
@TheKoR said:
don’t work with this version (3761) but work in previous :
HP D530 CMT - XP
Dell Latitude E5500 - VistaTroll : T’es un mauvais c’est tout…
-
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
-
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
-
8760w - windows 10 - svn 4266 - works fine up and down
-
Dell Venue 11 Pro - can’t get it to work, using Legacy Mode with USB Network ASIX AX88772A/B device
Running Fog 1.2 Ubuntu 14.04
Using a DHCP server running Windows Server 2003
undionly.kpxe hangs on iPXE Initialising devices
unidionly.kkpxe does a Boot Loop -
@dutchers4 said:
Dell Venue 11 Pro - can’t get it to work, using Legacy Mode with USB Network ASIX AX88772A/B device
Running Fog 1.2 Ubuntu 14.04
Using a DHCP server running Windows Server 2003
undionly.kpxe hangs on iPXE Initialising devices
unidionly.kkpxe does a Boot LoopA Dell Venue 8 Pro has been successfully fog’d only a month or so ago. I’m sure the same steps will work for you. See the Dell Venue listing here: https://wiki.fogproject.org/wiki/index.php/WorkingDevices You will need to move to FOG Trunk in order to accomplish this, and you’ll need to setup DHCP Vendor Classes so that it’s given the correct boot file while keeping all of your other clients working too.
If you need any help past this post - please create a thread called “Dell Venue 11 Pro” and we can give more focused help.
-
@kasper said:
Multiple Partition Image - Single Disk (Not Resizable)
Not working on :
HP Z620
- Fog 1.20
- Default Kernel
- Multiple Partition Image - Single Disk (Not Resizable)
Working on :
HP Z230 SFF
- Fog 1.20
- Default Kernel
- Multiple Partition Image - Single Disk (Not Resizable)
HP Compaq DC5700
- Fog 1.20
- Default Kernel
- Multiple Partition Image - Single Disk (Not Resizable)
HP Compaq DC5800
- Fog 1.20
- Default Kernel
- Multiple Partition Image - Single Disk (Not Resizable)
HP Compaq DC6000
- Fog 1.20
- Default Kernel
- Multiple Partition Image - Single Disk (Not Resizable)
HP Compaq DC6200
- Fog 1.20
- Default Kernel
- Multiple Partition Image - Single Disk (Not Resizable)
HP Elite 800 G1
- Fog 1.20
- Default Kernel
- Multiple Partition Image - Single Disk (Not Resizable)
-
Working:
Dell Precision M 4700
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Dell Precision M 4800
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Dell Precision M 6800
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Dell Vostro 3750
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Dell Vostro 3750
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Dell Inspiron 5720
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Precision T1700
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Dell Precision 3510 without USB C
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable)Not Working:
Dell Precision 3510 with USB C
-Fog 1.20
-Default Kernel
-Multiple Partition Image - Single Disk (Not Resizable) -
#wiki worthy - I need to go through this thread and make sure all this is in the working hardware list.
-
HP Compaq 6200 Pro
Intel 82579LM Gigabyte Network Connection
undionly.kpxe
FOG 1.2.0
03-16-2016
Single Disk - ResizableNote on 6200 - I’ve occasionally run into issues with SD - R where after imaging, Explorer reports the shrunken size of the partition but Disk Management show the partitions being the right size (first part being 100 to 350mb and the second part the rest of the disk) To remedy this go to DISKPART, select the miss-sized partition and run EXTEND FILESYSTEM.
HP DC7700
Broadcom NetXtreme Gigabit Ethernet
undionly.kpxe
FOG 1.2.0
03-18-2016
Single Disk - ResizableNote on 6200 and DC7700 - Also as is noted here, HP adds partitions that make using Single Disk - Resizable fail out. The partition is also created when making update to the BIOS. Unlike what the article listed says however, you can delete the partition using DISKPART.
