JLT 6012 rev 2023 - restor boot

george1421

@totoro What version of FOG are you using? I find it strange tat you can capture an image, but then when you restore the image the kernel only transfers 26% and fails.

This sounds like an iPXE issue where it is not sending the FOS image complete to the target computer.

totoro

@george1421 We run the 1.5.10

george1421

@totoro OK good on the latest version of fog.

Just to make sure I can understand. You can capture an image from this device, but you can’t deploy it because ipxe only sends 26% of the FOS linux image?

Is this device uefi or bios based? If its uefi, what boot loader are you using? ipxe.efi or snponly.efi? If you are using ipxe.efi try the snp.efi or snponly.efi. (the snp.efi will use all interfaces, and snponly will only use the interface it pxe booted from) to chain load linux. The snp driver is built into the nic adapter, where ipxe.efi is much like the linux kernel that has all common network drivers built in. That will lead to the next part.

Another observation is that these device are 2023 models == new hardware. Linux sometimes is a bit slow to take up new hardware. As well as new hardware firmware (uefi/bios) sometimes has bugs in it.

totoro

@george1421

Just to make sure I can understand. You can capture an image from this device, but you can’t deploy it because ipxe only sends 26% of the FOS linux image?

Yes

Is this device uefi or bios based?

Can be both, but actually usefi

If its uefi, what boot loader are you using? ipxe.efi or snponly.efi?

ipxe.efi

If you are using ipxe.efi try the snp.efi or snponly.efi. (the snp.efi will use all interfaces, and snponly will only use the interface it pxe booted from) to chain load linux. The snp driver is built into the nic adapter, where ipxe.efi is much like the linux kernel that has all common network drivers built in. That will lead to the next part.

Ok I’m will try snp.efi and give you a return

Another observation is that these device are 2023 models == new hardware. Linux sometimes is a bit slow to take up new hardware. As well as new hardware firmware (uefi/bios) sometimes has bugs in it.

Yes I know, it’s for that the two network card
Thank’s for your help

totoro

@george1421
Same problem with snp.

george1421

@totoro said in JLT 6012 rev 2023 - restor boot:

Same problem with snp.

Ok this kind of points to ipxe being the beginning of the problem. So lets try to update iPXE to the latest release using this thread: https://forums.fogproject.org/topic/15826/updating-compiling-the-latest-version-of-ipxe?_=1694448083008

The logic here is that FOG 1.5.10 was released in March 2023, and you are using 2023 hardware. Its possible that the latest version of iPXE might address this issue. Understand tat iPXE is managed by a different group than FOG, so we rely on the iPXE folks to manage pxe booting issues.

i’d like to look into the network issues with FOS linux, but that should come after we get pxe booting into FOS Linux corrected.

The last thought is that its possible that iPXE will not work on this hardware since it is specialized. We do have a method to usb boot right into FOS linux for those systems where pxe booting is not an option.

totoro

@george1421
Same problem after update…

george1421

@totoro Do you have the option to usb boot this device for imaging?

For completeness, you say you are able to image using 2 network cards. One allows pxe booting. What model network adapter is this? The first one is not seen by FOS linux but the second one is seen by FOS. What model number is that? Is it an added in network adapter like usb a or usb c network adapter? The transfer of 26% of bzImage is suspicious why it works for capture but fails on deploy. I have to be missing something here. I realize this hardware is not a typical PC, but if its x86 based it should work.

totoro

@george1421 said in JLT 6012 rev 2023 - restor boot:

@totoro Do you have the option to usb boot this device for imaging?

Yes but not useable for my USB adaptateur, at fist Pxe menu appear with onboard ethernet card with cable plugged, then after boot start I need to plug cable on Usb ethernet card.

For completeness, you say you are able to image using 2 network cards. One allows pxe booting. What model network adapter is this?

Result of “lshw -class network”
description: Ethernet interface
produit: Intel Corporation
fabriquant: Intel Corporation
identifiant matériel: 1d.1
information bus: pci@0000:00:1d.1
nom logique: eno1
version: 11
numéro de série: 00:13:95:57:22:f6
taille: 1Gbit/s
capacité: 1Gbit/s
bits: 64 bits
horloge: 33MHz
fonctionnalités: pm msi bus_master cap_list ethernet physical tp mii 10bt-fd 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=st_gmac driverversion=6.1.0-12-amd64 duplex=full ip=192.168.0.71 latency=0 link=yes multicast=yes port=twisted pair speed=1Gbit/s
ressources: mémoireE/S:600-5ff irq:130 mémoire:6002300000-600233ffff

The first one is not seen by FOS linux but the second one is seen by FOS. What model number is that?

description: Ethernet interface
identifiant matériel: 7
information bus: usb@1:4.4
nom logique: enx00e04c421374
numéro de série: 00:e0:4c:42:13:74
taille: 1Gbit/s
capacité: 1Gbit/s
fonctionnalités: ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8152 driverversion=v1.12.13 duplex=full ip=192.168.0.79 link=yes multicast=yes port=MII speed=1Gbit/s

Is it an added in network adapter like usb a or usb c network adapter?

Usb a

The transfer of 26% of bzImage is suspicious why it works for capture but fails on deploy. I have to be missing something here. I realize this hardware is not a typical PC, but if its x86 based it should work.

More information, is I try with the USB adaptateur unplug without succes.

george1421

@totoro Do you have access to the FOS linux console or is the output from some other linux distro?

If you have access to the fos linux console key in the following commands and post the output here.

uname -a
lspci -nn | grep -i net
grep -i firm /var/log/syslog

The first command tells me the linux kernel version
The second command lists all network adapters in the computer. The important value missing from your printout is the device id [8086:xxxx] that will tell me if linux has a driver for it.
The third command should list any possible firmware the network adapter is missing that we need to include in the kernel.

totoro

@george1421 From a Debian 12 I just install:

root@debian:~# dmesg | grep firm
[ 3.391439] platform regulatory.0: firmware: direct-loading firmware regulatory.db
[ 3.391687] platform regulatory.0: firmware: direct-loading firmware regulatory.db.p7s
[ 3.472252] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 3.472285] bluetooth hci0: firmware: failed to load intel/ibt-0041-0041.sfi (-2)
[ 3.472309] firmware_class: See https://wiki.debian.org/Firmware for information about missing firmware
[ 3.472333] bluetooth hci0: firmware: failed to load intel/ibt-0041-0041.sfi (-2)
[ 3.472348] Bluetooth: hci0: Failed to load Intel firmware file intel/ibt-0041-0041.sfi (-2)
[ 3.803833] i915 0000:00:02.0: firmware: failed to load i915/icl_dmc_ver1_09.bin (-2)
[ 3.803849] i915 0000:00:02.0: firmware: failed to load i915/icl_dmc_ver1_09.bin (-2)
[ 3.803854] i915 0000:00:02.0: Direct firmware load for i915/icl_dmc_ver1_09.bin failed with error -2
[ 3.803859] i915 0000:00:02.0: [drm] Failed to load DMC firmware i915/icl_dmc_ver1_09.bin. Disabling runtime power management.
[ 3.803862] i915 0000:00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915
[ 14.613243] r8152 1-4.4:1.0: firmware: failed to load rtl_nic/rtl8153a-4.fw (-2)
[ 14.613270] r8152 1-4.4:1.0: firmware: failed to load rtl_nic/rtl8153a-4.fw (-2)
[ 14.613284] r8152 1-4.4:1.0: Direct firmware load for rtl_nic/rtl8153a-4.fw failed with error -2
[ 14.613288] r8152 1-4.4:1.0: unable to load firmware patch rtl_nic/rtl8153a-4.fw (-2)

root@debian:~# lspci -nn | grep -i net
00:1d.1 Ethernet controller [0200]: Intel Corporation Device [8086:4ba0] (rev 11)
02:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX210/AX211/AX411 160MHz [8086:2725] (rev 1a)

He we see only the internal ethenet card
The USB one is from lsusb :
Bus 001 Device 011: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter

root@debian:~# uname -a
Linux debian 6.1.0-12-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.52-1 (2023-09-07) x86_64 GNU/Linux

george1421

@totoro Ok this can give me something to work with.

00:1d.1 Ethernet controller [0200]: Intel Corporation Device [8086:4ba0] (rev 11)

This is the ethernet controller. first available in linux kernels 5.7–5.19, 6.0–6.5. I don’t see a fail to load firmware for this one. Run the lspci command again lspci -Knn | more you will need to look for device 00:1d.1. I need to see that entire section.

EDIT: I just looked at the build settings for FOS Linux 6.x and it does compile the driver in the 6.x released of FOS Linux https://github.com/FOGProject/fos/blob/45ba692315f6e5857c12d933ae2c9c4dd5c35778/configs/kernelx64.config#L1720 lines 1720-1724

Bus 001 Device 011: ID 0bda:8153 Realtek Semiconductor Corp. RTL8153 Gigabit Ethernet Adapter

OK that answers why I was seeing a failing to load for the realtek nic

totoro

@george1421
Do you think it can be a bios configuration issue ?
Because I try de load the compatibility checking, with 6-1-22 it’s working, and after a reboot, no anymore, same as 5-15-93 kernel …
You ask me to try lspci -Knn | more one the installed Debian ?

Sebastian Roth

@totoro said in JLT 6012 rev 2023 - restor boot:

Because I try de load the compatibility checking, with 6-1-22 it’s working, and after a reboot, no anymore,

Can you explain what exactly you mean?

JLT 6012 rev 2023 - restor boot

158

11.6k

17.1k

154.6k