motioneyeos icon indicating copy to clipboard operation
motioneyeos copied to clipboard

RPi Zero W doesn't get an IP on first boot

Open Cubytus opened this issue 8 months ago • 6 comments

Preliminary Docs

I confirm that I have read the CONTRIBUTING guide before opening this issue.

I confirm that I have read the FAQ before opening this issue.

motionEyeOS Version

I am running motionEyeOS version: dev20201026

Board Model

I am using the following board/model: Raspberry Pi Zero W.

Camera

I am using the following type of camera: can't know as the board doesn't get an IP address.

My camera model is: Official Raspberry Pi camera.

Network Connection

My motionEyeOS unit is connected to the network via: USB-Ethernet adapter

Peripherals

I am using the following peripherals that I consider relevant to this issue: For the sake of this test, I added a few connections that aren't necessary in a normal setting

  • mini-HDMI to VGA adapter connected to a standard monitor
  • USB OTG adapter (official RPi model)
  • USB 3.0 hub
  • wireless keyboard

Log Files

None as I have no LAN connection to this board and no user/password pair

The basics being said, I wanted to reinstall MotionEyeOS from scratch. Even if development is frozen, I assumed it should be working reasonably well in a LAN. I followed the wiki's instruction to image a microSD card with the latest dev20201026 version, inserted it in the board, made all connections (Ethernet included) then powered it up.

It stops at the "Welcome to meye-12345678!" "If you want to see a friendly user interface, point your browser to the IP address of this board" Of course, it doesn't display what this IP address might be, and all I get is the one-line message showing the date and CPU temperature.

The date itself isn't updated despite Ethernet being connected (as shown by both its link/act lights flashing)

A quick LAN scan with Angry IP scanner doesn't display any new device and what's even weirder, a look at the admin page for the router doesn't display the MAC of the USB-Ethernet adapter, which is known to be working.

Now it seems that many issues are happening at the same time, but I can't find out where to start.

Cubytus avatar May 25 '24 18:05 Cubytus