JulienD Posted December 4, 2022 Posted December 4, 2022 Hello, download page for odroid M1 states: Quote In order to boot Armbian, you need to disable Petitboot by running fw_setenv skip_spiboot true in the command line of Petitboot. This won’t run Petitboot again. But cons it will only boot from eMMC or SD card, not from USB nor NMVe nor SATA. I have two questions: - Does that mean that the system will be installed on SD or eMMC? or does that meant booting on SD is just for startup to launch system stored on NVMe (or any other storage)? - Is there a plan for booting from M.2 NVMe M-Key PCIe3.0 2-Lane in the future? Thanks Julien 0 Quote
Igor Posted December 4, 2022 Posted December 4, 2022 3 hours ago, JulienD said: I have two questions: - Does that mean that the system will be installed on SD or eMMC? or does that meant booting on SD is just for startup to launch system stored on NVMe (or any other storage)? - Is there a plan for booting from M.2 NVMe M-Key PCIe3.0 2-Lane in the future? This is my test M1 which runs perfectly fine. With kernel 6.1.y it will be declared supported / stable. Spoiler igorp@10.0.10.169's password: ___ ____ ____ ___ ___ ____ __ __ _ / _ \| _ \| _ \ / _ \_ _| _ \ | \/ / | | | | | | | | |_) | | | | || | | | | |\/| | | | |_| | |_| | _ <| |_| | || |_| | | | | | | \___/|____/|_| \_\\___/___|____/ |_| |_|_| Welcome to Armbian 22.11.0-trunk Kinetic with Linux 6.1.0-rc5-rk3568-odroid No end-user support: untested automated build & unsupported (kinetic) userspace! System load: 4% Up time: 1 day 4:03 Memory usage: 2% of 7.50G IP: 10.0.10.169 CPU temp: 32°C Usage of /: 1% of 916G Tip of the day: Want to use a rolling release? https://github.com/armbian/community [ 0 security updates available, 2 updates total: apt upgrade ] Last check: 2022-12-04 00:00 igorp@odroidm1:~$ df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 786036 83956 702080 11% /run /dev/nvme0n1p1 960302804 1159240 910289104 1% / tmpfs 3930176 0 3930176 0% /dev/shm tmpfs 5120 0 5120 0% /run/lock tmpfs 3930176 0 3930176 0% /tmp /dev/mmcblk1p1 30340976 1213160 28789292 5% /media/mmcboot /dev/zram1 47960 18996 25380 43% /var/log tmpfs 786032 0 786032 0% /run/user/0 tmpfs 786032 0 786032 0% /run/user/1000 Boots from SD card, root on NVME. This is currently the only way as we don't want to use dirty proprietary boot solutions provided by Hardkernel. Support for SPI boot / NVME root is under development, mainline ATF is floating around , but integration and testing is a lot of work ... we receive no funding so things doesn't really move fast. I can't tell when this will be done and integrated. Probably mid next year. 0 Quote
JulienD Posted December 12, 2022 Author Posted December 12, 2022 Thanks for your answer. System is running. 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.