@tbasura You mention multicasting. I have never used clonezilla in a multicast scenario and don’t know how it works. With FOG we use “udp-cast” for this. When you send out a multicast deploy and something goes wrong with the underlaying udp-cast then you’d see a hanging blue partclone screen (though still different as it would not get as far to show the numbers yet but hang with a very plain screen). So my first assumption on multicast playing a role here is probably wrong.

Drivers can’t be an issue either because that’s handled by the Linux kernel.

Will be interesting to see what FOG makes of it. I highly recommend you install the latest dev-branch version instead of the dated last release (1.5.9).

@piotr86pl
WoL works reliably here with r8169. To enable WoL on boot basically every network manager (systemd-integrated, netctl, etc.) offers a config option.
For systemd see here

The mentioned 13GB/min would be more than 200MB/s, exceeding the rate of a 1Gbps link. So this number may refer to a compressed image. More relevant would be iperf results for assessing network performance. r8168 and r8169 both can go at full link speed.

To check for issues specific to the Realtek network chip version on your system (r8169 supports ~ 50 chip versions) a full dmesg log would be helpful.

@TheDark5776 There seems to be a question missing. Posting this in the hardware compatibility section I would expect some hardware specs to discuss your issue.

@george1421 Fabulous, thanks so much, George.

@george1421 yes when i boot with usb 20.04 it work. Because Kernel is 5.15.X.

@george1421

Thanks George!

I had seen people talking about updating the kernel on here but I presumed they meant the FOG server kernel but now I realise that the FOG kernel is distinct from the kernel used by the FOG server. After updating the FOG kernel via the web UI FOG seems to be working on our new machines.

@george1421 I used TCPDUMP without telling which ports to listen (tcpdump -i enp12s0 -w output3-BIOS-hp.pcap), in 3 computers:

UEFI Computer #1 - file is “output1-UEFI-insys.pcap” - https://drive.google.com/file/d/1lBxNv2bhjTtMhPEC2gd66tpzV3egZK5i/view?usp=sharing UEFI Computer #2 - file is “output1-UEFI-b560m.pcap” - https://drive.google.com/file/d/1TgiQS15RrESjc3Q92euB7UWOMLPOxXFu/view?usp=sharing BIOS Computer #3 - file is “output1-BIOS-hp.pcap” - https://drive.google.com/file/d/1gkz71TMr8XzJovDSOZqyvkcvtsjCz2I0/view?usp=sharing

I think in these files, you can see at DHCP information and finally can figure out how to help me. I really need this to be working. School starts next tuesday and I have a lot of computers to deploy images to.

@lobomarinho said in Dell Optiplex 5490, boot but o network interfaces found:

My Dell Optiplex 5490 detect server but then give me a error

BIOS file name is “undionly.kpxe”

Just reading between the lines here. What you have said are in conflict. I would think the optiplex 5490 is a uefi only system. The undionly.kpxe program is a bios only boot loader. You can’t boot undionly.kpxe on a uefi based computer.

Second part and more on point is. Do you get to the FOG iPXE menu? If no then you need to update iPXE. If yes, then update the FOG Linux kernel (FOG WebUi -> FOG Configuration -> Kernel update. Update to the 5.15.(latest) to get the newest hardware support. as @LLamaPie mentioned.

Intel NUC: NUC6i5SYB

Last Captured
2022-07-28 04:06:48

Deploy Method
Partimage

Image Type
ImageType ID: 2 Name: Multiple Partition Image - Single Disk (Not Resizable)

PXE: undionly.kpxe

Ethernet: Elitegroup Computer Systems Co.,Ltd. b8:ae:ed:7f:eb:6d

System UUID f8493d3f-a111-8a17-c119-b8aeed7feb6d
System Type Type: Desktop
BIOS Vendor Intel Corp.
BIOS Version SYSKLi35.86A.0073.2020.0909.1625
BIOS Date 09/09/2020
Motherboard Manufacturer Intel corporation
Motherboard Product Name NUC6i5SYB
Motherboard Version H81131-502
Motherboard Serial Number GESY60400ECC
Motherboard Asset Tag .]/.
CPU Manufacturer Intel® Corporation
CPU Version Intel® Core™ i5-6260U CPU @ 1.80GHz
CPU Normal Speed Current Speed: 1700 MHz
CPU Max Speed Max Speed: 2900 MHz
Memory 7.66 GiB
Hard Disk Model ADATA SP550
Hard Disk Firmware O1015A
Hard Disk Serial Number 2G0920029548

@djgalloway Thank you. Actually this thread helps advance the project too. The devs won’t add this driver to the main kernel but if they need to create a one off kernel the instructions are here.

@george1421 worked like a charm when switching to REFIND.

Change your Boot Exit settings in the fog web GUI to GRUB. If that is your current setting change to SANBOOT.

@sebastian-roth said in Image capture: reading partition tables failed:

@david-burgess You might want to point to a specific Primary Disk within the host settings, e.g. /dev/sda

Thank you. This was the fix.

@jalilg said in Fujitsu Lifebook E5511 / Intel 11th Gen Boot Failure:

What do you mean with the firewall only supports static dhcp options

This is specific to how the value of dhcp option 67 is managed. It is static in the sense of you have to manually configure it to send out undionly.kpxe for bios computers and ipxe.efi if you want to boot uefi computers. That is a static text field.

When I refer to dynamic options, that means based on the pxe booting computer, if the computer is bios based then the dhcp server will send out undionly.kpxe name. If the computer is uefi based then it will send out ipxe.efi. Its dynamic from the perspective of the pxe booting computer.

If you had a windows 2012 or later or linux dhcp server you can enable policies to make dhcp option 67 specific to the pxe booting computer. If you are not using one of those dhcp servers and your dhcp server doesn’t support dynamic dhcp options then we can deploy dnsmasq to provide that dynamic info only. We find most dhcp servers running on routers or switches don’t support dynamic pxe booting, pfsense is one exception that does support it.

@abde No problem. I am happy to answer your questions, we just need to follow the guidance of the developers to keep one problem one thread policy.

@aheerds Glad you have it working. Just for clarity ipxe.efi/snp.efi/undionly.kpxe will get you to the FOG iPXE menu. Once you select a menu selection that’s when FOS Linux (a.k.a “the kernel”) takes over. Both (ipxe and FOS) will throw the “No configuration method succeeded”.

@sebastian-roth Issue hase been fixed by using the 5.15.19 kernel. Many thanks @george1421 and @Sebastian-Roth for the quick support.

We found the solution. For anyone having the same problem with a emmc G1J39E, use the kernel arguments

sdhci.debug_quirks=0x65168080

we found the answer right here

@lsathya I really think there is something up/wrong with this hardware that causes iPXE to hang.

We do have a fall back method to get these computers to image without pxe booting. You will lose some capabilities, but you will be able to image them. Read through this article. https://forums.fogproject.org/topic/7727/building-usb-booting-fos-image Because of the way the forum works the first part is at the top of the thread and the subsequent parts are at the end of the thread. Read through the tutorial and understand what you need to do and the caveats by creating a USB Boot image for FOS Linux.

Also look in the FOG Forum chat bubble at the top for a few more hints.

@andy-morris said in Lenovo 14w Gen2:

I just got it going by using the Kernel bzImage-5.15.5 from the fogproject.org/kernels/ list. I will make it the default for bzImage.

Nice! You might even use the newer kernel from github I just compiled a week ago: https://github.com/FOGProject/fos/releases/tag/20220203

By the way, the pictures you posted show that you were using 4.19.x kernel earlier… 😉