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

flake.lock is out of date #5

Open
bryanmehall opened this issue Nov 12, 2024 · 6 comments · May be fixed by #10
Open

flake.lock is out of date #5

bryanmehall opened this issue Nov 12, 2024 · 6 comments · May be fixed by #10

Comments

@bryanmehall
Copy link

The flake.lock file is out of date so the image doesn't boot. Without the update this #NixOS/nixpkgs#216886 issue is still present. Running nix flake update before building fixes the issue.

@kubukoz
Copy link

kubukoz commented Nov 29, 2024

Confirmed, I went back to e752e7b and it worked while de89de4 didn't.

@plmercereau plmercereau linked a pull request Dec 7, 2024 that will close this issue
@plmercereau
Copy link
Owner

Hello, could you confirm this pull request solves the issue?

@alexvorobiev
Copy link

I just ran nix flake update prior to building but the image won't boot - it stops at "Starting kernel...". I am on WSL if that matters.

@bryanmehall
Copy link
Author

bryanmehall commented Dec 13, 2024

I just ran nix flake update prior to building but the image won't boot - it stops at "Starting kernel...". I am on WSL if that matters.

Are you using the serial port to debug? The default image stops sending console output over the serial port when uboot hands over to the kernel. You can add:

kernelParams = [
      "earlycon"               # enable writing to uart serial console early in boot process
      "boot.shell_on_fail"
      "8250.nr_uarts=1"        # configure mini uart https://forums.raspberrypi.com/viewtopic.php?t=246215
      "console=ttyS0,115200n8" # set console to output to uart1 (miniuart)
    ];

inside of the boot set in zero2w.nix if that is the problem

@alexvorobiev
Copy link

Thanks! The pi doesn't connect to wifi for some reason (with the correct ssid/password), I am trying to troubleshoot that. I'll make the change and report back.

@alexvorobiev
Copy link

That worked. It connected to wifi and everything seems to be in order. Thanks!

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.

4 participants