Remote-Wake-Sleep-On-LAN-Server VS rpi-eeprom

Another option is to use a Web-GUI like Remote-Wake-Sleep-On-LAN-Server, which is also available as a Docker container though the Docker container isn't maintained anymore, it still works.

Non Docker: https://github.com/sciguy14/Remote-Wake-Sleep-On-LAN-Server

Hello! I have been trying to set up the raspberry pi as a wake on lan server for my laptop. I have tested it and it works locally from the router, but I cannot configure the arp table and it was leading to issues after shutdown. I tried to use sciguy14's wake on lan server, but it always said my laptop was off even when it wasn't. Now to etherwake. Is it possible to set up etherwake to wake my computer when it is not directly plugged into it? I would like my laptop to be wired, so I was wondering if my pi could be connected to my router through ethernet and the same with my laptop so I don't need to worry about wifi. Thanks in advance!

I don't have Pi 5 to check this, but from what I've read, it does not support PPS. And such support is required; otherwise, even with a source that supports PPS, the connection will behave in a non-PPS fashion.

Apparently, cable quality is also demonstrating itself to be a significant factor in the Pi 5 power supply environment.

Regarding both these points:

https://github.com/raspberrypi/rpi-eeprom/issues/497

I should note, I updated the eeprom, USB hub, and network firmware using the images provided from the following repository: https://github.com/raspberrypi/rpi-eeprom. So it certainly isn't a corrupted eeprom chip, and if it was I wouldn't be able to boot the old installation I pulled from my backup drive.

Its a known issue with the current Pi 4 boot firmware. The net install option is trying to look for a keyboard and gets confused with some HIDs.

I was working on a final project for my class and needed an adc. So I ordered an ADS1115 and I had to solder the pins onto it. I've never soldered before, but I tried my best. Didn't look amazing, but didn't look like any pins were getting shorted so I plugged it in to the Pi. I then noticed that my ssh disconnected and couldn't reconnect. Tried plugging in the HDMI and there was no video output. I tried flashing a new OS onto it, didn't work. Tried EEPROM recovery from here and it didn't work. So I think I killed the Pi. It doesn't feel like it's getting warmed up or anything.

See https://github.com/raspberrypi/rpi-eeprom/blob/master/firmware/release-notes.md

I try to reset the pi as factory settings (following this github advice). I use pi-imager to set my SD card to lead the pi using USB boot priority and plug a USB key with raspbian OS (no desktop) and now getting green screen when booting. Think that the pi is dead.

I think it was this one:

https://github.com/raspberrypi/rpi-eeprom/blob/master/firmwa...

I had the same problem as you, updated my eeprom and the problem was fixed

Firmware: https://github.com/raspberrypi/rpi-eeprom/releases/tag/v2020.09.03-138a1