Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Cannot PXE boot Debian onto Raspberry Pi 4b

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
Latrina
Posts: 5
Joined: 2019-10-26 11:09

Cannot PXE boot Debian onto Raspberry Pi 4b

#1 Post by Latrina »

Hello folks,

I have been trying to PXE boot both Debian 10 and 11 using the images found here, though the boot process dies at GENET STOP: 0, thus failing to boot the kernel. The PXE server works just fine given that I can PXE boot Raspbian as well as other linux distros onto different SBC devices. Boot and TFTP server logs can be found below.

UART boot logs

Code: Select all

Terminal ready
LINK STATUS: speed: 1000 full duplex
Link ready
GENET START: 64 16 32
GENET: UMAC_START 0xdca632d5 0xb2de0000
RX: 0 IP: 0 IPV4: 0 MAC: 0 UDP: 0 UDP RECV: 0 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
DHCP src: fe:ad:82:55:02:0e 172.12.1.1
YI_ADDR 172.12.1.91
OPTIONS:-
	op: 53 len:   1 DHCP recv OFFER (2) expect OFFER
	op: 54 len:   4 172.12.1.1
	op: 51 len:   4 
	op:  1 len:   4 255.255.255.0
	op:  3 len:   4 172.12.1.1
	op: 66 len:  10 172.12.1.1[66]: 172.12.1.1

DHCP src: fe:ad:82:55:02:0e 172.12.1.1
YI_ADDR 172.12.1.91
OPTIONS:-
	op: 53 len:   1 DHCP recv ACK (5) expect ACK
	op: 54 len:   4 172.12.1.1
	op: 51 len:   4 
	op:  1 len:   4 255.255.255.0
	op:  3 len:   4 172.12.1.1
	op:  6 len:   8 
	op: 12 len:   5 
	op: 66 len:  10 172.12.1.1[66]: 172.12.1.1

	op: 15 len:  14 
NET 172.12.1.91 255.255.255.0 gw 0.0.0.0 tftp 172.12.1.1
ARP 172.12.1.1 fe:ad:82:55:02:0e
NET 172.12.1.91 255.255.255.0 gw 0.0.0.0 tftp 172.12.1.1
RX: 3 IP: 0 IPV4: 4 MAC: 2 UDP: 2 UDP RECV: 2 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP_GET: fe:ad:82:55:02:0e 172.12.1.1 kube4/start4.elf

RX: 3 IP: 0 IPV4: 4 MAC: 2 UDP: 2 UDP RECV: 2 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
RX: 4 IP: 0 IPV4: 6 MAC: 3 UDP: 3 UDP RECV: 3 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP_GET: fe:ad:82:55:02:0e 172.12.1.1 kube4/config.txt

RX: 4 IP: 0 IPV4: 6 MAC: 3 UDP: 3 UDP RECV: 3 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP: complete 315
RX: 6 IP: 0 IPV4: 10 MAC: 5 UDP: 5 UDP RECV: 5 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
Read kube4/config.txt bytes      315 hnd 0x00000000
TFTP_GET: fe:ad:82:55:02:0e 172.12.1.1 kube4/pieeprom.sig

RX: 6 IP: 0 IPV4: 10 MAC: 5 UDP: 5 UDP RECV: 5 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP 1: File not found 
RX: 7 IP: 0 IPV4: 12 MAC: 6 UDP: 6 UDP RECV: 6 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
Read kube4/pieeprom.upd failed
TFTP_GET: fe:ad:82:55:02:0e 172.12.1.1 kube4/recover4.elf

RX: 7 IP: 0 IPV4: 12 MAC: 6 UDP: 6 UDP RECV: 6 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP 1: File not found 
RX: 8 IP: 0 IPV4: 14 MAC: 7 UDP: 7 UDP RECV: 7 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
Read kube4/recover4.elf failed
TFTP_GET: fe:ad:82:55:02:0e 172.12.1.1 kube4/recovery.elf

RX: 8 IP: 0 IPV4: 14 MAC: 7 UDP: 7 UDP RECV: 7 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP 1: File not found 
RX: 9 IP: 0 IPV4: 16 MAC: 8 UDP: 8 UDP RECV: 8 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
Read kube4/recovery.elf failed
TFTP_GET: fe:ad:82:55:02:0e 172.12.1.1 kube4/start4.elf

RX: 9 IP: 0 IPV4: 16 MAC: 8 UDP: 8 UDP RECV: 8 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP: complete 2228800
RX: 2187 IP: 0 IPV4: 4372 MAC: 2186 UDP: 2186 UDP RECV: 2186 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
Read kube4/start4.elf bytes  2228800 hnd 0x00000000
TFTP_GET: fe:ad:82:55:02:0e 172.12.1.1 kube4/fixup4.dat

RX: 2187 IP: 0 IPV4: 4372 MAC: 2186 UDP: 2186 UDP RECV: 2186 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
TFTP: complete 5448
RX: 2194 IP: 0 IPV4: 4386 MAC: 2193 UDP: 2193 UDP RECV: 2193 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
Read kube4/fixup4.dat bytes     5448 hnd 0x00000000
Firmware: 564e5f9b852b23a330b1764bcf0b2d022a20afd0 Feb 25 2021 12:10:40
0x00d03114 0x00000000 0x000000ff
MEM GPU: 76 ARM: 948 TOTAL: 1024
Starting start4.elf @ 0xfec00200 partition -1
Stopping network
RX: 2194 IP: 0 IPV4: 4386 MAC: 2193 UDP: 2193 UDP RECV: 2193 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
RX: 2194 IP: 0 IPV4: 4386 MAC: 2193 UDP: 2193 UDP RECV: 2193 IP_CSUM_ERR: 0 UDP_CSUM_ERR: 0
RX_DISCARD: 0
  GR64: 0x00000001   GR64: 0x00000007  GR127: 0x00000000  GR255: 0x00000004 
 GR511: 0x00000001 GR1023: 0x00000885 GR1518: 0x00000000  GRMGV: 0x00000000 
GR2047: 0x00000000 GR4095: 0x00000000 GR9216: 0x00000892  GRPKT: 0x0023c83c 
 GRBYT: 0x00000000  GRMCA: 0x00000000  GRBCA: 0x00000000  GRFCS: 0x00000000 
 GRXCF: 0x00000000  GRXPF: 0x00000000  GRXUO: 0x00000000  GRALN: 0x00000000 
 GRFLR: 0x00000000  GRCDE: 0x00000000  GRFCR: 0x00000000  GROVR: 0x00000000 
 GRJBR: 0x00000000 GRMTUE: 0x00000892  GRPOK: 0x00000892   GRUC: 0x00000000 
 GRPPP: 0x00000000  GRCRC: 0x00000000 

  TR64: 0x0000088c  TR127: 0x00000008  TR255: 0x00000000  TR511: 0x00000003 
TR1023: 0x00000000 TR1518: 0x00000000  TRMGV: 0x00000000 TR2047: 0x00000000 
TR4095: 0x00000000 TR9216: 0x00000000  GTPKT: 0x00000897  GTMCA: 0x00000000 
 GTBCA: 0x00000004  GTXPF: 0x00000000  GTXCF: 0x00000000  GTFCS: 0x00000000 
 GTOVR: 0x00000000  GTDRF: 0x00000000  GTEDF: 0x00000000  GTSCL: 0x00000000 
 GTMCL: 0x00000000  GTLCL: 0x00000000  GTXCL: 0x00000000  GTFRG: 0x00000000 
 GTNCL: 0x00000000  GTJBR: 0x00000000  GTBYT: 0x00022a0f  GTPOK: 0x00000897 
  GTUC: 0x00000893 
GENET STOP: 0
+

FATAL: read zero bytes from port
term_exitfunc: reset failed for dev UNKNOWN: Input/output error
admin@gentoo ~ $
TFTP server logs

Code: Select all

vswitch0:~$ grep 'Aug 21 15:43' /var/log/messages
Aug 21 15:43:07 vswitch0 daemon.notice in.tftpd[3321]: RRQ from 172.12.1.91 filename kube4/start4.elf
Aug 21 15:43:07 vswitch0 daemon.warn in.tftpd[3321]: tftp: client does not accept options
Aug 21 15:43:07 vswitch0 daemon.notice in.tftpd[3322]: RRQ from 172.12.1.91 filename kube4/config.txt
Aug 21 15:43:07 vswitch0 daemon.notice in.tftpd[3323]: RRQ from 172.12.1.91 filename kube4/pieeprom.sig
Aug 21 15:43:07 vswitch0 daemon.notice in.tftpd[3324]: RRQ from 172.12.1.91 filename kube4/recover4.elf
Aug 21 15:43:07 vswitch0 daemon.notice in.tftpd[3325]: RRQ from 172.12.1.91 filename kube4/recovery.elf
Aug 21 15:43:07 vswitch0 daemon.notice in.tftpd[3326]: RRQ from 172.12.1.91 filename kube4/start4.elf
Aug 21 15:43:09 vswitch0 daemon.notice in.tftpd[3327]: RRQ from 172.12.1.91 filename kube4/fixup4.dat
Aug 21 15:43:10 vswitch0 daemon.notice in.tftpd[3328]: RRQ from 172.12.1.91 filename kube4/recovery.elf
Aug 21 15:43:10 vswitch0 daemon.notice in.tftpd[3329]: RRQ from 172.12.1.91 filename kube4/config.txt
Aug 21 15:43:10 vswitch0 daemon.notice in.tftpd[3330]: RRQ from 172.12.1.91 filename kube4/dt-blob.bin
Aug 21 15:43:10 vswitch0 daemon.notice in.tftpd[3331]: RRQ from 172.12.1.91 filename kube4/recovery.elf
Aug 21 15:43:10 vswitch0 daemon.notice in.tftpd[3332]: RRQ from 172.12.1.91 filename kube4/config.txt
Aug 21 15:43:11 vswitch0 daemon.notice in.tftpd[3333]: RRQ from 172.12.1.91 filename kube4/bootcfg.txt
Aug 21 15:43:11 vswitch0 daemon.notice in.tftpd[3334]: RRQ from 172.12.1.91 filename kube4/upstream/vmlinuz-5.10.0-0.bpo.8-arm64
Aug 21 15:43:11 vswitch0 daemon.notice in.tftpd[3335]: RRQ from 172.12.1.91 filename kube4/initrd.img-5.10.0-0.bpo.8-arm64
Aug 21 15:43:23 vswitch0 daemon.notice in.tftpd[3336]: RRQ from 172.12.1.91 filename kube4/bcm2711-rpi-4-b.dtb
Aug 21 15:43:23 vswitch0 daemon.notice in.tftpd[3337]: RRQ from 172.12.1.91 filename kube4/overlays/overlay_map.dtb
Aug 21 15:43:23 vswitch0 daemon.notice in.tftpd[3338]: RRQ from 172.12.1.91 filename kube4/config.txt
Aug 21 15:43:23 vswitch0 daemon.notice in.tftpd[3339]: RRQ from 172.12.1.91 filename kube4/cmdline.txt
Aug 21 15:43:24 vswitch0 daemon.notice in.tftpd[3340]: RRQ from 172.12.1.91 filename kube4/vmlinuz-5.10.0-0.bpo.8-arm64
Aug 21 15:43:24 vswitch0 daemon.notice in.tftpd[3341]: RRQ from 172.12.1.91 filename kube4/armstub8-gic.bin
Aug 21 15:43:24 vswitch0 daemon.notice in.tftpd[3342]: RRQ from 172.12.1.91 filename kube4/vmlinuz-5.10.0-0.bpo.8-arm64
vswitch0:~$ 
Any help will be much appreciated. Thanks :)

Latrina
Posts: 5
Joined: 2019-10-26 11:09

Re: Cannot PXE boot Debian onto Raspberry Pi 4b

#2 Post by Latrina »

Anyone knows what GENET STOP: 0 means and why it hangs there? 😕

Post Reply