-
Notifications
You must be signed in to change notification settings - Fork 2k
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
missing environment variable bootfile #470
Comments
I think the missing step was appending something on the |
I tried via USB the box reboots after this screen and the process repeats forever: via microSD I get the same behavior as with the non m8s-specific image: What are the USB/microSD preparation steps exactly? It seems copying the |
The 5.4/5.15 kernel does not need u-boot.ext/.emmc, and the scripts are automatically installed for other kernels. |
Without creating the
And with the suggested m8s image:
Thank you very much! |
Yes, the firmware with |
Hello, I'm experiencing this same issue while trying the first boot in my TX3 mini with S905w....Sometimes I get Kernel panic (when using a USB pendrive), but now I got this same error, error while inserting stdin followed by 'bootfromsd' not defined. When I connect my ethernet cable it says 'missing environment variable: bootfile and 'serverip' not set and set'. After burn the image with balenaEtcher I didnt do nothing, just checked the uEnv to see if dtb matches with my TVBox model. Tanix TX3 mini Trying to boot from Armbian_24.2.0_amlogic_s905w_bullseye_6.1.69_server_2024.01.01.img |
Before You Open ISSUE, Make Sure You have Read Armbian Firmware Instructions and Documentation
Describe the bug
1st boot stuck, probably missing microSD preparation steps, about 2 months ago I successfully booted up jammy with the newer kernel. I cannot boot either Bullseye/Jammy no matter which kernel I try, I get the same messages on 1st boot
To Reproduce
FDT=/dtb/amlogic/meson-gxm-q201.dtb
inuEnv.txt
u-boot-s905x-s912.bin
asu-boot.ext
a. and this is where I remember having +1 step a few months ago, having to do something with u-boot.sd
b. I also remember something about usb and quirks and having to look up IDs from approx.
lsusb
Expected behavior
boot to login prompt
Screenshots
Armbian Version
Device:
The text was updated successfully, but these errors were encountered: