Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug / v1.11.0] Erlang VM not started #30

Closed
jsimmonds2 opened this issue Mar 20, 2020 · 1 comment · Fixed by #31
Closed

[bug / v1.11.0] Erlang VM not started #30

jsimmonds2 opened this issue Mar 20, 2020 · 1 comment · Fixed by #31
Assignees

Comments

@jsimmonds2
Copy link

Environment

  • Elixir version (elixir -v):

Erlang/OTP 22 [erts-10.5.3] [source] [64-bit] [smp:2:2] [ds:2:2:10] [async-threads:1] [hipe]
Elixir 1.9.2 (compiled with Erlang/OTP 22)

  • Nerves environment: (mix nerves.env --info)
|nerves_bootstrap| Environment Package List

  Pkg:         nerves_system_rpi4
  Vsn:         1.11.0
  Type:        system
  BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

  Pkg:         nerves_toolchain_arm_unknown_linux_gnueabihf
  Vsn:         1.3.1
  Type:        toolchain
  BuildRunner: {Nerves.Artifact.BuildRunners.Local, []}

  Pkg:         nerves_system_br
  Vsn:         1.11.0
  Type:        system_platform
  BuildRunner: {nil, []}

  Pkg:         nerves_toolchain_ctng
  Vsn:         1.7.1
  Type:        toolchain_platform
  BuildRunner: {nil, []}

|nerves_bootstrap| Loadpaths Start


Nerves environment
  MIX_TARGET:   rpi4
  MIX_ENV:      prod

|nerves_bootstrap| Environment Variable List
  target:     rpi4
  toolchain:  /home/jhs/.nerves/artifacts/nerves_toolchain_arm_unknown_linux_gnueabihf-linux_x86_64-1.3.1
  system:     /home/jhs/.nerves/artifacts/nerves_system_rpi4-portable-1.11.0
  app:        /home/jhs/src/jsimmonds2/RasPi3BPlus/Blinkers/Nerves/fb2

|nerves_bootstrap| Loadpaths End
  • Additional information about your host, target hardware or environment that
    may help

nerves_system_rpi4 v1.10.2 worked correctly, repeatably.

Current behavior

Boot hangs here :

image

Expected behavior

Erlang VM is started successfully and base app runs.

@mobileoverlord
Copy link
Contributor

I was able to reproduce this locally with the downloaded artifact. I’m building a clean system to test.

fhunleth added a commit that referenced this issue Mar 21, 2020
This fixes an issue booting the Raspberry Pi 4 that shows these log
messages and never successfully mounts the MicroSD:

```
[    1.928553] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    1.935829] sdhci-iproc fe340000.emmc2: Dropping the link to regulator.1
[    1.943187] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    1.950413] sdhci-iproc fe340000.emmc2: Dropping the link to regulator.1
```

Fixes #30
fhunleth added a commit that referenced this issue Mar 21, 2020
This fixes an issue booting the Raspberry Pi 4 that shows these log
messages and never successfully mounts the MicroSD:

```
[    1.928553] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    1.935829] sdhci-iproc fe340000.emmc2: Dropping the link to regulator.1
[    1.943187] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.1
[    1.950413] sdhci-iproc fe340000.emmc2: Dropping the link to regulator.1
```

Fixes #30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants