pxe

May 26, 2019 - 2:14 PM

  • I'm trying to get my atomic pi to pxe boot.

    I'm not seeing the dhcp request on the server. But after it boots to the preinstalled image, I see that dhcp to the server and it gets an ip ok.

    I do see a bit of network traffic when it is at about the point it should be trying to pxe.

    Doing a tcpdump, it looks to be just ipv6 solicitations during the bios part of the boot:
    06:36:07.582478 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 8) :: > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 8
    06:36:08.021397 IP6 (hlim 1, next-header Options (0) payload length: 32) :: > ff02::1:ff4c:909c: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ff4c:909c
    06:36:08.840660 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 24) :: > ff02::1:ff4c:909c: [icmp6 sum ok] ICMP6, neighbor solicitation, length 24, who has fe80::207:32ff:fe4c:909c
    06:36:11.701630 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 8) :: > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 8
    06:36:15.710722 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 8) :: > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 8
    06:36:17.523300 IP6 (hlim 1, next-header Options (0) payload length: 32) fe80::207:32ff:fe4c:909c > ff02::1:ff4c:909c: HBH (rtalert: 0x0000) (padn) [icmp6 sum ok] ICMP6, multicast listener reportmax resp delay: 0 addr: ff02::1:ff4c:909c

    I have a 8 port desktop netgear gigabit switch and have the dhcp server (laptop) and the atomic pi plugged into it.

    I tried switching the order of ipv6 and ipv4 booting, as well as setting the two retry values higher in the bios.

    I have also tried connecting the laptop and atomic pi directly together, so I do not believe it is an stp issue.

    Any ideas?

    0
  • Did you ever get your system to PXE boot.
    I see similar issues with mine.
    I'm trying to boot off of a Windows box running ServA.
    I also only seem to see the Linux boot request an IP Address.

    [06/30 03:02:30.891] PDHCP Inf: Rcvd DHCPREQUEST from IP 0.0.0.0, MAC AaeonTec/00:07:32:4A:2D:C5, ClassID dhcpcd-6.11.5:Linux-4.15.18-dli:

    Yet a local VM will boot fine.
    [06/30 01:50:56.083] PDHCP Inf: Rcvd DHCPDISCOVER from IP 0.0.0.0, MAC Vmware/00:0C:29:C7:C2:CD, ClassID PXEClient, Arch EFI BC
    [06/30 01:50:56.083] PDHCP Inf: Sending DHCPOFFER
    [06/30 01:50:56.083] PDHCP Inf: Broadcasting through local interface [169.254.61.135]
    [06/30 01:50:56.083] PDHCP Inf: Broadcasting through local interface [192.168.152.1]
    [06/30 01:50:56.084] PDHCP Inf: Broadcasting through local interface [192.168.192.1]
    [06/30 01:50:56.084] PDHCP Inf: Broadcasting through local interface [192.168.22.25]
    [06/30 01:50:59.293] PDHCP Inf: Rcvd DHCPREQUEST from IP 192.168.152.128, MAC Vmware/00:0C:29:C7:C2:CD, ClassID PXEClient, Arch EFI BC
    [06/30 01:50:59.293] PDHCP Inf: Sending DHCPACK, TFTP [192.168.152.1] bootfile [\BM\PXESERVA\EFI64\pxeserva.efi]
    [06/30 01:50:59.344] PDHCP Inf: Rcvd DHCPREQUEST from IP 0.0.0.0, MAC Vmware/00:0C:29:C7:C2:CD, ClassID PXEClient, Arch EFI BC

    0
  • In order to boot via PXE, I had to disable SCC eMMC support. After doing that, the PXE menu came up on boot.

    0
  • ¡Qué tal desde Murcia! Aquí el clima es casi siempre bueno, pero esa tarde preferí quedarme tranquilo. Un amigo me había comentado de un portal de juegos y me animé a buscarlo. Empecé perdiendo seguido, lo cual me molestó un poco, pero luego conseguí una racha positiva que cambió todo. Esa victoria fue lo que me dejó satisfecho. Hoy en día, de vez en cuando entro a roulettino casino cuando quiero variar mi rutina.

    0