All Activity

I didn't mention, sorry, probably it matters somehow - my bookworm is already transferred to emmc, so system boots and runs from there, not from SD-card

WSL might be easier if you're on windows

" Either of those," i'm one step closer OK, i 'll get Ubunto on vm and will look deeper. Thanks for now

Not joking at all. 1st point Supported Architectures: x86_64, aarch64, riscv64 board is armhf Next 3 points from this readme: System: VM, container, or bare-metal with: ≥ 8GB RAM (less with KERNEL_BTF=no) ~50GB disk space Operating System: Armbian / Ubuntu 24.04 (Noble) for native builds Any Docker-capable Linux for containerized setup Windows: Windows 10/11 with WSL2 running Armbian / Ubuntu 24.04 Are they alternate to each other

Either of those, I personally used Ubuntu running in ESXi VM

Are you joking? Open readme.md in GitHub repo, read it and explore links therein

Thanks for answering. Couple things: "As per documentation, run on a compatible host". Which documentation? can you provide link you define by this word? Define pls compatible host as it is very unclear in comparison to what i was reading ( it was unclear too) , or it is defined in docs you mentioned... banana pi pro is not supported as I understood. Igor Pecovnik was supporting this device for years. Maybe he can deliver more info in this subject. 2 points in reqs: - Armbian / Ubuntu Noble 24.04.x for native building or any Docker capable Linux for containerised - Windows 10/11 with WSL2 subsystem running Armbian / Ubuntu Noble 24.04.x Both required?

Thank you for your report, @DanflashX So, your audio is working out of the box and the change in https://github.com/armbian/build/pull/8568 is not necessary for the Opi 5 Pro?

Anybody here with the Opi 5 Pro? Does it need the same change? https://github.com/armbian/build/pull/8568

I just wanted to interject that I ran into the same (non?)-issue on the 25.8.1 trixie minimal image using a rpi400. armbianmonitor -u

I have only ever seen mmcblk?boot? Partitions on media that was setup for Android as the A/B is part of how Android installs updates and can fall back to the previous version. I've never seen them on an Armbian created media.

Wow, I didn't know those command and mechanism even exist... Thank you for your tip! Any ideas regarding main (mmcblk2boot) topic question, perhaps?

It's worth noting that you don't have to necessarily change anything in the build process. As long as you plan to not insert partitions in the middle, you can: write the image to the card with parted, resize the root partition to whatever you want make a new partition If you want to have more than 4 partitions total, this works best with GPT partition table, but legacy msdos works too with a little more effort `fsck.ext4 -f /dev/foo` where foo is the root partition `resize2fs /dev/foo` after you have the machine booted, you can then mkfs the new partition [you could probably do it in advance of booting the system too] I do this regularly, b/c I typically only partition about 1/2 or 1/4 of the SD card to leave the rest for wear-leveling. Are you trying to do this as a one-off or are you trying to do it for a dozen or more SBCs of the same type?

not everything is mounted, at least not in the way you expect it. check "swapon -s"

As per documentation, run on a compatible host: git clone https://github.com/armbian/build cd build ./compile.sh Follow screen menus. Build system will download necessary toolchain, sources, patches, etc and build an image. Whether or not it will work depends on whether sources/patches for a particular board deviated from the hardware due to time or bugs. If someone is regularly testing then image likely will be ok, if not then image might work or not. If the board has community maintained status, then it is up to its users to test/develop/send patches in GitHub. If necessary, it is possible to play with sources, configs, develop and place extra patches, etc. At times it looks not that straightforward, so there will be a learning curve.

If I have not researched incorrectly, the Rock Pi S0 has microSD, USB, and Ethernet to access external storage, but you have not provided any information about which options are available in your specific case.

I guess they are free to spend that time to develop own samba implementation

I don't think I can condone changing a very, very security-relevant part of your setup without fully understanding its implications. So, it's good you ask here. I can't answer it off the top of my hat, but maybe somebody else can chime in. I don't think I would bother for the sake of 5 seconds. Are you logging in and out all the time? By the way, PAM is short for pluggable authentication module, so you are disabling an authentication mechanism.

I agree that would normally be a bug. And Debian would agree and in turn us. We have not established that being the case yet, though. At least not for me since @bushw has not yet responded. @Cancer Do you have an example for me to look into? Please do tell us more.

Every time I tried to log on to ssh on my rock-s0 with armbian, there would be a delay of like 5 seconds. I found a solution that fixes this problem. This thread is partly a PSA about this solution, and a question about whether this solution is a good idea or not. The trick is to change UsePAM=yes , to UsePAM=no , in the /etc/ssh/sshd_config file. But I heard some people online say this is a bad idea, but I don't understand PAM enough to know why. I am only going to use ssh in a basic password-authenticated, LAN environment. Do I really need PAM? The only side-effect I noticed is that it no longer shows the MOTD when logging in.

It's not about technicalities but basic logic. We have here situation where one program which should offer on/off functionality affects config of another one. @laibsch I'm not sure why have you reacted this way. Maybe i'm not proffessional but it's about linux and users should at least point on such things @robertoj Naturally, it's not about armbian itself, but generally linux related. F.e. when i configure another samba instance usual way and find it's not working by looking in logs and finding after some lost time that interface name has changed. How many people are requesting isssue with samba and loosing time just because of that?

XD take your concerns to Canonical

@usual user I don't think there is any storage device on the rock s0 other than the emmc that I can boot from. Other than SD card but that negates the point of not having the customer disassemble the device.

this is not a vote but a technical discussion, @Cancer. your hostile tone and unfounded accusations of "somebody was using windows too much" are out of place (and simply laughable). consider yourself warned. and if you don't understand the technicalities maybe it's best to keep quiet? and yes, of course bringing up or down a network interface can obviously affect the firewall. and distribution managers are free to do whatever they want with their distribution, it is theirs not yours. entitled much? this is FOSS, you have the code, change it if you don't like it. but otherwise, keep your entitled and ungrateful attitude to yourself. thank you.