-
Upcoming Events
-
-
Volunteering positions
-
Single board computer maintainer
Position: Board maintainerNumber of places: 64Applicants: 72
-
-
Chat | Social Media
#armbian at
irc.libera.chat or irc.oftc.net
Matrix or Discord
Mastodon | 𝕏 -
Popular Now
-
Activity Stream
-
62
Full root filesystem encryption on an Armbian system (NEW, replaces 2017 tutorial on this topic)
Quick note on what I also had to change to make it running on my Raspi: in fstab, the option "commit=600" won't work as the Armbian version for Raspis uses a FAT32 boot partition. Apparently "commit" doesn't work with that file system. To get it working, my fstab reads: … UUID=[ID] /boot vfat defaults,noatime,nodiratime 0 2 … -
39
Odroid M1S Image Planned ?
Hi! I am around... Thank you for all the work you have been doing on the M1S. Unfortunately I haven't had the opportunity to test recently, but I expect to. As for the low performance, I really had the feeling that the M1S is slow on graphics, but decent (for its class) on regular CPU work. I had tested with linuxfactory's bookwork image and that was the feeling I got from then. I don't think the long wait time for armbian-config to open is normal. My first bet would be something related to network access, either there is not a working internet access or some configuration is wrong. My second bet, some sort of reading error on the microSD card. The M1S isn't that sloooow. I would suggest you check dmesg for a clue after running armbian-config. Best regards, Sérgio -
27
KickPi K2B not booting up: DRAM setup not supported
The official sent me the Armbian SDK, which includes kickpi-k2b-v2 and v1. I tested it and it can boot normally. Wired/wireless networks and Bluetooth all work fine, but the OTG function just won’t work no matter what I try. (g_ether and g_serial not woring) Anyway, I hope it can be merged into Armbian. I only compressed the config and patch folders, which should be sufficient. https://we.tl/t-wtmI81zB5e -
39
Odroid M1S Image Planned ?
Tested another Armbian, this time Noble with Gnome desktop. Although I personally do not like that UI, It performs relatively good. As @Werner predicted, glmark2-es2-wayland finished with a score of 277. WebGL Aquarium demo works significantly better. While 500 fishes still result in very low FPS, 100 fishes is mostly fluent. What I observed on all systems I have tested on the M1S, armbian-config takes extremely long to load/open. Sometimes around 5 minutes or so. It would be interesting to know, if this is expected to be normal... Now that I have tested four different images (Bookworm server, Noble Server, Noble Cinnamon and Noble Gnome), all with "current" kernel (6.12), I feel okay to do the PR. As said, I did not do that much but only adding the .csc file and the .dts file. This gave me the feeling on the other hand, that your build framework is working really great and makes it "relatively easy" to contribute and test own things, as seen as one knows how the things play together. So apart from all my "complains", your build framework is great!👍 If there are still other M1S users around: Hi! -
2
CPU won't run freq 1512000 on armbian. Running perfectly on any other distro.
I think in Armbian, the kernel is simply ignoring the 1512 MHz OPP? armbian: armbian_dts.dts / { opp-table-cpu { compatible = "allwinner,sun50i-h616-operating-points"; nvmem-cells = <0x43>; // cpu-speed-grade opp-shared; // ... other OPPs ... opp-1416000000 { opp-hz = <0x00 0x54667200>; opp-microvolt = <0x10c8e0>; // 1.08V opp-supported-hw = <0x2d>; // mask? }; opp-1512000000 { opp-hz = <0x00 0x5a1f4a00>; opp-microvolt-speed1 = <0x10c8e0>; // 1.08V opp-microvolt-speed3 = <0x10c8e0>; opp-microvolt-speed5 = <0x11b340>; // 1.16V for bin5!? opp-supported-hw = <0x2a>; // mask? }; }; }; ubuntu: ubuntu_dts.dts / { opp-table-cpu { compatible = "allwinner,sun50i-h616-operating-points"; nvmem-cells = <0x4d>; // cpu-speed-grade opp-shared; // ... other OPPs ... opp-1416000000 { opp-hz = <0x00 0x54667200>; opp-microvolt-speed0 = <0x10c8e0 0x10c8e0 0x10c8e0>; // 1.08V for all bins // no mask? }; opp-1512000000 { // works fine opp-hz = <0x00 0x5a1f4a00>; opp-microvolt-speed0 = <0x10c8e0 0x10c8e0 0x10c8e0>; // 1.08V for all bins // no mask? }; }; }; and possible voltage limits?? armbian: /soc/i2c@7081400/pmic@36/regulators/dcdc2 { regulator-always-on; regulator-min-microvolt = <0x7a120>; // 0.48V? regulator-max-microvolt = <0x10c8e0>; // 1.08V max? when bin 5 on 1512 req 1.16V? regulator-ramp-delay = <0xc8>; regulator-name = "vdd-cpu"; }; ubuntu: /soc/i2c@7081400/pmic@36/regulators/dcdc2 { regulator-always-on; regulator-min-microvolt = <0x7a120>; // 0.48V? regulator-max-microvolt = <0x124f80>; // 1.2V max?? regulator-ramp-delay = <0xc8>; regulator-name = "axp313a-dcdc2"; }; Pinning both decompiled DTBs for clarity. Images: Armbian: Armbian_25.5.1_Orangepizero3_bookworm_current_6.12.23_minimal.img Ubuntu: Orangepizero3_1.0.6_ubuntu_noble_server_linux6.1.31.img What should I do then? I probably don't want to fry that little guy, but 1416 feels a bit off. I love Armbian—it only uses 80 MB of RAM compared to 300 MB on Ubuntu, though. But I don't know what to do about this. (There's a slight difference between the post and the DTS—likely due to minor formatting tweaks for readability)
-
-
Member Statistics
