Categories

  • Get help with your FOG system.
    FOG Problems Hardware Compatibility Windows Problems Linux Problems Mac Problems General Problems
    13k Topics
    115k Posts
    R

    @Tom-Elliott

    Experimental kernel EXP_20260805-123232 fixes it completely!

    UEFI download speed on the OptiPlex 3070 has jumped from ~1.2 GB/min to ~6.5 GB/min. We believe the small remaining gap from our usual ~10 GB/min is down to a suspect patch lead/socket on the test machine rather than anything kernel related. We’ll confirm with a better cable shortly.

    Legacy mode speeds are unchanged and still fast as expected.

    One thing worth highlighting from the ethtool -k output below.

    Before the experimental kernel, dmesg was showing:

    tx checksumming: ko

    With the experimental kernel, ethtool -k now shows: rx-checksumming: on tx-checksumming: on tx-checksum-ipv4: on

    So it looks like the experimental kernel has fixed both the ASPM issue and the checksumming issue in one go. Thought that was worth calling out given you mentioned you wanted to rule out a second separate problem.

    ethtool -k enp1s0 | head -50
    Features for enp1s0:
    rx-checksumming: on
    tx-checksumming: on
    tx-checksum-ipv4: on
    tx-checksum-ip-generic: off [fixed]
    tx-checksum-ipv6: on
    tx-checksum-fcoe-crc: off [fixed]
    tx-checksum-sctp: off [fixed]
    scatter-gather: on
    tx-scatter-gather: on
    tx-scatter-gather-fraglist: off [fixed]
    tcp-segmentation-offload: on
    tx-tcp-segmentation: on
    tx-tcp-ecn-segmentation: off [fixed]
    tx-tcp-mangleid-segmentation: off
    tx-tcp6-segmentation: on
    tx-tcp-accecn-segmentation: off [fixed]
    generic-segmentation-offload: on
    generic-receive-offload: on
    large-receive-offload: off [fixed]
    rx-vlan-offload: on
    tx-vlan-offload: on
    ntuple-filters: off [fixed]
    receive-hashing: off [fixed]
    highdma: on [fixed]
    rx-vlan-filter: off [fixed]
    vlan-challenged: off [fixed]
    tx-gso-robust: off [fixed]
    tx-fcoe-segmentation: off [fixed]
    tx-gre-segmentation: off [fixed]
    tx-gre-csum-segmentation: off [fixed]
    tx-ipxip4-segmentation: off [fixed]
    tx-ipxip6-segmentation: off [fixed]
    tx-udp_tnl-segmentation: off [fixed]
    tx-udp_tnl-csum-segmentation: off [fixed]
    tx-gso-partial: off [fixed]
    tx-tunnel-remcsum-segmentation: off [fixed]
    tx-sctp-segmentation: off [fixed]
    tx-esp-segmentation: off [fixed]
    tx-udp-segmentation: off [fixed]
    tx-gso-list: off [fixed]
    tx-nocache-copy: off
    loopback: off [fixed]
    rx-fcs: off
    rx-all: off
    tx-vlan-stag-hw-insert: off [fixed]
    rx-vlan-stag-hw-parse: off [fixed]
    rx-vlan-stag-filter: off [fixed]
    l2-fwd-offload: off [fixed]
    hw-tc-offload: off [fixed]

    Init Version: 20260804 (unchanged as expected)

    Thanks again for the incredibly quick turnaround and the detailed explanation of the ASPM/CONFIG_PCIEASPM root cause.

    Very much appreciated. Happy to test anything further if needed and please let me know if I missed any of your diagnostic steps happy to take another stab at it or move on to another check if it helps.

    Thanks
    Richard

  • Get the latest news on what's happening.
    Security Advisories
    184 Topics
    825 Posts
    A

    @Tom-Elliott I really appreciate that you are putting effort into providing more frequent releases, which makes it easier for everyone to deploy new security fixes in time. Keep up the good work!

  • View tutorials or talk about FOG in general.
    General Tutorials
    2k Topics
    19k Posts
    8

    @Cpasjuste

    Thank you, I appreciate that. And yes, I did spend a lot of time on it.

    I agree that it bypasses the official installer in order to make use of Docker environment variables; however, at this stage, I don’t believe that FOG is going to change so dramatically that it’ll break it often.

    I will add that if this could get adopted as an official docker image, we could work with the FOG team to make sure nothing gets to pushed to the FOG code that would break the container until we can adjust the container as well.

  • Report bugs, request features, or get the latest progress.
    General Feature Request Bug Reports
    2k Topics
    21k Posts
    L

    Hi everyone, / @george1421

    I’ve been trying to capture the SD card of a Raspberry Pi 4 and I’ve hit a wall. I am booting via a USB stick using the EDK2 UEFI firmware, and I have explicitly set the System Table Selection to <Devicetree> in the UEFI settings.

    I managed to get past the iPXE phase without issues, and the capture task successfully loads the FOS kernel and init. However, the boot process stops right after with the following error (see attached image):
    No network interfaces found, your kernel is most probably missing the correct driver!

    Current Setup & Debug info:

    FOG version: 1.5.10.2149

    Hardware: Raspberry Pi 4 (trying to capture the built-in SD card)

    Boot method: USB stick with UEFI firmware

    Kernel version: 6.18.38

    Init version: 20260726

    (No PCI network hardware detected - obviously, as it’s the SoC’s built-in NIC)

    I think it seems the current experimental ARM kernel is missing the built-in Pi 4 network driver (bcmgenet). Unfortunately, using an external USB-to-LAN adapter is not an option for me, as the UEFI firmware refuses to boot from it in my environment.

    My question is:
    Given that I am booting from a USB stick and making it exactly to this point in the capture task, is there any chance or workaround to successfully capture the Pi 4’s SD card? Is there a custom/specific kernel available that includes the built-in Pi network driver, or any other method I can use to bypass this missing driver issue?

    Any help or guidance would be greatly appreciated!
    20260803_152648.jpg

119

Online

12.7k

Users

17.6k

Topics

156.8k

Posts