All Activity

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.

Wow, that is awesome and thank you so much for sharing your findings. Let's get this applied in our repo for the benefit of all Armbian users.

@Ducdanh Nguyenyour axp chip should look similar to this

fully agree with author statement. The same as change from ethx to endx is a step in wrong direction. Somebody was using windows too much. ifconfig is not even installed by default because of ip command. Distribution managers should be forced to stop such things. @laibsch "when you bring a network interface up or down that can obviously affect firewall rules" Is it a joke?

@Ducdanh Nguyen H313 is basically the same chip as H616.

@Nick Ai don't see any h313 on the page, maybe i will just tear it down again

i should add some details: minimal version which is from yesterday for download, which has short description: "optimised for automation and production deployments" doesn't say too much. No idea what it means without better description. it's not in any of defined categories defined in faq. Is there any specs how to get sources and compile it for my small server with sata drive? I was not compiling kernel for about 30yrs+ however could do it with good specs . Many things changed... like even sources are not accessible as they were in the past. Naturally specs which i've seen is not the way to go.

Yes, but since this created device isn't mounted anywhere it makes no sense - no service or whatever could use it anyway, what definitely turns this creature into just waste of RAM for nothing, am I wrong?

I explained above what zram is created for. OPi3LTS should have 2G of memory, so having 1G of zram makes perfect sense here.

@fevangelou nice guide. THX! but maybe it would be best to have the instruction in an separate topic! in best case it gets also pinned. so new users can find it much easier than scrolling though 18 pages (in this thread. there is also the 4gb thread) to find it......

@Ducdanh Nguyen you should be able to see it on the board https://linux-sunxi.org/AXP_PMICs

You are completely right - at least 50MB one is there /dev/zram1 on /var/log type ext4 (rw,nosuid,nodev,noexec,relatime,discard) But big 987MB /dev/zram0 isn't at all - so it looks like it's useless and could be removed from zram config, right? Both mystic /dev/mmcblk2bootX are still in question

Hi All What is current working image for banana pi pro? Can't find any except one in archive (bookworm) which is not perfect.

Have you checked "mount" command to list actualy mounts? I am quite confident mount is happening by the ramlog service and is not integrated into fstab. some more background: sdcards have a limited amount of writes until its cells die. Since everytime some service or whatever writes some logs this issues a write event. To drastically increase the lifespan of the microsd log entries are buffered to (compressed) memory and then recurringly written all at once.

In fact in image's default fstab they aren't mounted so those probably could be assumed as a kind of waste of RAM this way? Or there is chance that they actually mounted somewhere else but fstab? root@heaven:~# cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 00 UUID=fb077685-a428-49f2-b013-287dc5fc9672 / ext4 defaults,noatime,commit=120,errors=remount-ro,x-gvfs-hide 0 1 Thank you for tip regarding /var/log, I was suspecting that it should be there as soon as device created. Do you mean to inspect with binwalk/strngs those devices in hope to find out what is there? I'd gave a try - there is nothing: root@heaven:~# binwalk /dev/mmcblk2boot0 DECIMAL HEXADECIMAL DESCRIPTION -------------------------------------------------------------------------------- root@heaven:~# binwalk /dev/mmcblk2boot1 DECIMAL HEXADECIMAL DESCRIPTION -------------------------------------------------------------------------------- root@heaven:~# strings /dev/mmcblk2boot0 root@heaven:~# They also can't be mounted - dmesg excerpt: [390869.014377] F2FS-fs (mmcblk2boot0): Magic Mismatch, valid(0xf2f52010) - read(0x0) [390869.014508] F2FS-fs (mmcblk2boot0): Can't find valid F2FS filesystem in 1th superblock Magic mismatch - mystic things unsolved)

Yes I'm aware that I can only rely on the community for any help or tip. I'm now considering to revert back to a bullseye setup with a 5.10 Radxa kernel, but I was kind of reluctant to keep an old version of Debian as my Rockpi is accessible from ouside my network... The Rockpi is powered by a PoE hat, it never had any issue so far but maybe the PoE management is the culprit. I'll try an use the Rockpi with a traditional power supply, but in any case if this is the issue it won't be a sustainable solution for my target setup.

Thanks @eselarm for the input that this should work. So I tested it. And it does! I leave a few hints for anyone who wants to replicate. When creating a new image layout working directly with the image files was the fastest for me. So you need to download one original Armbian image. I used a minimal cli image. Image preparations Create a new image file (e.g. with dd) that will be partitioned like described above. Copy all the first sectors until the first partition starts from the original image to the new image. This will copy the original partition table but more importantly also the uboot bootloader into the new image (32768 sectors = 16MB). Partitioning Partition the new image as described above (e.g. with fdisk/sfdisk) and format the new partitions. One smaller boot partition (e.g. 512MB, ext4) and two bigger root partitions (e.g. 3GB, ext4). I will use the terms rootA and rootB for the two new root partitions in the new image from here on. Get the UUIDs of the newly created boot and rootA partition of the new image (e.g. lsblk/blkid). Most likely instead of using two separate ext4 rootA and rootB partitions one bigger btrfs partition and the usage of subvolumes could be possible. But I did not test this. Copy boot and adjust Mount the new boot partition and create directories bootA and bootB and a relative symlink boot pointing to bootA. Place all files from the original image’s /boot directory into bootA of the new image. Adjust the UUID line in armbianEnv.txt that still points to the original image’s root partition to the rootA UUID from the new image. Copy root and adjust Mount rootA and copy all the files from the original image into it. Remove all files from the /boot directory in rootA as we will mount the boot partition into this directory anyway and do not want to get mixed up. Create a new directory /rawBoot in rootA. Edit the fstab of rootA and change the UUID that still points to the original image’s root partition to the rootA UUID. Add a line to fstab to mount the boot partition of the new image into /rawBoot. Add a line to fstab to bind mount the directory /boot of /rawBoot into /boot of rootA. Add an empty file /root/.no_rootfs_resize in rootA to avoid the partitions being changed if the original image was never booted before. I did all of the above also with an archived older Armbian image and put that into rootB (and bootB). With this setup we now have two separated OS versions. They can be switched by simply changing the boot symlink to bootA or bootB and reboot. Because we used bind mount we can also do kernel upgrades which end up in the correct directory. As all of the steps are easily automatable by a shell script we can now download a new earlier prepared update package place its content into the other boot directory and partition adjust their UUIDs (and maybe copy SSH keys and machine-id if we want to keep system identity) and change a symlink. If we need to go back to the older image just the symlink needs to changed back. Either from within a running system or if that is not possible by taking the card out and doing this externally. As I said earlier this A+B update scheme is not as robust as other tools. But we can stay with prebuilt images from Armbian that can be locally configured the way we want it. After this an update package can be created and distributed which could also contain a new uboot. If this is tested well before distribution I guess most errors that make the other tools so robust can be avoided.