Pi 4B no Ethernet or USB

[BoredFish]

Using my pi in a case, sitting and being used, with active cooling. Restarted the Pi and now the Ethernet nor the USB work. Ethernet does not work at all, but USB does output power, though no data. Tried reinstalling, multiple different OSes, multiple different SD cards, but nothing. All the USB ports don't work. I didn't do anything differently, it usually sits in the case, for my 3D printer through klipper. I use an argon one, with the official power supply. It does output to HDMI, though can't interact with it. My order number is 2861886-3047689392

[mikeysklar]

The loss in USB function and ETH function after a reboot sounds like a possible rpi firmware (pieeprom) update took place or a new kernel was installed from running the usual apt full-upgrade command.

There are some suggestions in this thread to get them back:

https://forums.raspberrypi.com/viewtopic.php?p=2022215

Start with an eeprom update since you are seeing the behavior across multiple OS installs.

Code: Select all

sudo rpi-eeprom-update

[BoredFish]

The loss in USB function and ETH function after a reboot sounds like a possible rpi firmware (pieeprom) update took place or a new kernel was installed from running the usual apt full-upgrade command.

There are some suggestions in this thread to get them back:

https://forums.raspberrypi.com/viewtopic.php?p=2022215

Start with an eeprom update since you are seeing the behavior across multiple OS installs.

Code: Select all

sudo rpi-eeprom-update

Tried that, but that returned that everything was up to date, even ahead of up to date. It returned

Code: Select all

BCM2711 detected
VL805 firmware in bootloader EEPROM
BOOTLOADER: up-to-date
CURRENT: Tue 25 Jan 14:30:41 UTC 2022 (1643121041)
 LATEST: Thu  3 Sep 12:11:43 UTC 2020 (1599135103)
 FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 
 LATEST: 

[mikeysklar]

That output might be a bit misleading as it is only looking at critical EEPROMs.

You might want to modify the EEPROM release channel from critical to stable:

Code: Select all

sudo nano /etc/default/rpi-eeprom-update
FIRMWARE_RELEASE_STATUS="stable"

Then run the following:

Code: Select all

sudo rpi-eeprom-update -a

[BoredFish]

That output might be a bit misleading as it is only looking at critical EEPROMs.

You might want to modify the EEPROM release channel from critical to stable:

Code: Select all

sudo nano /etc/default/rpi-eeprom-update
FIRMWARE_RELEASE_STATUS="stable"

Then run the following:

Code: Select all

sudo rpi-eeprom-update -a

Still returned that it's up to date

Code: Select all

BOOTLOADER: up to date
   CURRENT: Tue 26 Apr 10:24:28 UTC 2022 (1650968668)
    LATEST: Thu 10 Mar 11:57:12 UTC 2022 (1646913432)
   RELEASE: stable (/lib/firmware/raspberrypi/bootloader/stable)
            Use raspi-config to change the release.

  VL805_FW: Using bootloader EEPROM
     VL805: up to date
   CURRENT: 
    LATEST: 

[BoredFish]

I've tried going to beta, and going to older versions, and there's no differences. I've looked into what the pi is outputting, and it's saying the PCI link is down. I believe this is a hardware fault, since I've ruled out all the possible software issues.

[Franklin97355]

Have you been loading the os to the SD Card from your computer or using the Pi to update?

[BoredFish]

Have you been loading the os to the SD Card from your computer or using the Pi to update?

I've been using the raspberry pi imager to update the os, and I do it from SSH to update eeprom

[BoredFish]

Just wanted to remind, this problem only appeared recently. It's been working perfectly until a few days ago when I rebooted (using sudo reboot) and it suddenly stopped working. When the issue appeared, the data light on the ethernet was stuck on, and I unplugged the ethernet, and still had that light on. Only disappeared after a reboot. To me, it seems that the problem started on boot.

[mikeysklar]

The PCIe link being down would explain the loss of USB. That is coming off the BCM28711 chip.

The gigabit ethernet controller is separate with its own BCM54213PE chip.

When did you purchase this board from Adafruit?

You could examine the solder points and the two chips for anything suspicous. Is there a hint in dmesg?

[BoredFish]

I got it on June 8th, all the joints look fine. dmesg says this about PCI

Code: Select all

[    1.113778] NET: Registered protocol family 1
[    1.115237] RPC: Registered named UNIX socket transport module.
[    1.115277] RPC: Registered udp transport module.
[    1.115305] RPC: Registered tcp transport module.
[    1.115334] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    1.115372] PCI: CLS 0 bytes, default 64
[    1.118356] Initialise system trusted keyrings
[    1.118615] workingset: timestamp_bits=14 max_order=19 bucket_order=5
[    1.126894] zbud: loaded
[    1.128661] FS-Cache: Netfs 'nfs' registered for caching
[    1.129428] NFS: Registering the id_resolver key type
--
[    1.130846] Asymmetric key parser 'x509' registered
[    1.131052] bounce: pool size: 64 pages
[    1.131109] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[    1.131355] io scheduler mq-deadline registered
[    1.131386] io scheduler kyber registered
[    1.135971] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[    1.136024] brcm-pcie fd500000.pcie:   No bus range found for /scb/pcie@7d500000, using [bus 00-ff]
[    1.136127] brcm-pcie fd500000.pcie:      MEM 0x0600000000..0x063fffffff -> 0x00c0000000
[    1.136236] brcm-pcie fd500000.pcie:   IB MEM 0x0000000000..0x007fffffff -> 0x0400000000
[    1.734663] brcm-pcie fd500000.pcie: link down
[    1.740840] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[    1.743941] iproc-rng200 fe104000.rng: hwrng registered
[    1.744301] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[    1.745260] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[    1.757652] brd: module loaded