NOBL

I tried to use strace to determine the cause of this message but couldn't find it. There are really some config files in /etc missing but adding them did not resolve the issue.

This messge shows up on the xfce edition Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_xfce_desktop.ing.xz as well as for the cinnamon edition: Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop.img.xz

Solved it by using the XFCE Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_xfce_desktop.img.xz instead of the cinnamon Armbian_25.2.1_Uefi-arm64_bookworm_current_6.12.13_cinnamon-backported-mesa_desktop.img.xz edition. I think it might need a different nextcloud client for both editions. If one is using the authentication via browser and the other needs Gnome online accounts. Regards Norbert

Hi every time I start firefox an error message appears stating "Could not read configuration file - contact your system administrator" 🙃, i. e. me. Does anyone know how to fix it ? It is simply an annoyance - firefox works as expected so far. Kind regards Norbert

Hi I can access my nextcloud in the firefox browser, but the client always states "signed out". From time to time there is a request in the browser to confirm access of the client to the nextcloud server. Howeveer, this doesn't seem to work. I guess, I should add an online account (in Preferences). But there is no button to "Add account" shown. Do you have a hint to a missing package ? I am out of ideas how to solve it. Kind regards Norbert

Hi Yesterday I spend the whole day to install Armbian Desktop (XFCE) on my Pinebook Pro. Why Armbian ? The PBP was delivered with Manjaro Arm on it. Everything worked fine until Manjaro stopped support for the Arm platform. For about one year there is no update on stable and the unstable branch couldn't establish a connection to Wifi. I used Manjaro Arm to install tow-boot to the SPI following this website: https://forum.pine64.org/showthread.php?tid=17529 I downloaded the current Bookworm XFCE edition and wrote that to an SD card. Booting from the SD with tow-boot went fine. I installed armbian on the SD card and used armbian-config to install it on the internal eMMC. That didn't work. fsarchiver to the rescue ! I created a GPT partition table on the internal disk, created two partitions with the correct flags and restored both partitions from the SD saved with fsarchiver to the internal disk. Booting went fine from the internal disk after that. Now I am fighting with firefox ("Can't read configuration file - contact your systemadministrator") and the nextcloud client. I can't add a online account anywhere. The application starts up but there is no button execpt (Information about ...) which shows the supported clients a.o. Owncloud (which will work with nextcloud) but there is no way to add an account. I'll open other posts to track that.

My lsusb just shows the "ids" of the controller of connected drives but not the drives themselves. Neither the external disks nor the Ethernet HW were detected. I checked the directories/files in /etc/modules/6.1.x-meson64. The directory structures of kernel 6.1.11, 6.1.30 nd 6.1.42 are the same. However, kernel 6.1.11 seems to expect that the modules are compressed, it loads the modules and everything is fine for me. The filenames all end with .ko.xz while the modules from kernel 6.1.30 (Armbian bookworm version in the official download images) and the modules for kernel 6.1.42 are not compressed. Those filenames all end with .ko. I didn't check whether compressing the required modules (in kernel/drivers/firmware) can be loaded by the kernels 6.1.30 or 6.1.42 if they are compressed. So, if the first error message you see during reboot shows an error regarding "Failed: ...loading kernel modules" then try to compress the modules in /lib/modules/6.1.30-meson64/kernel/drivers/firmware and reboot. Hope this helps.

Hi Unfortunately no solution here, but "mee too" only. My USB keyboard works fine, that's it. In addition, I suddenly no longer have any Ethernet hardware onboard. This happened sometime during last night. However, I suspect the kernel version which is unmaintained now, again. I am still using bullseye and kernel 6.1.42 - no alternative kernel is available on the internal disk. Are you using the same kernel version ? Thank you for your answer. Edit: The last known kernel version which worked was 6.1.11 from a backup done with fsarchiver. Will try to fall back to this one and report results, here. Of course, I don't know which kernel version broke the Ethernet port und the USB disk support. There is an error message during boot stating that kernel modules can not be loaded. Perhaps this is related ? We'll see. New edit: Solved ! I replaced the broken kernel (6.1.42) setup by using the 6.1.11 kernel. I think the problem is with the modules of kernel 6.1.42 and that's why the external disks are not detected. The output from kernel 6.1.42 showed an error message saying that loading kernel modules failed. The same happened to me with kernel 6.1.11 because I forgot to add the modules directory to /lib/modules. As soon as I added /lib/modules/6.1.11-meson64 correctly my nextcloud now boots and works. I'll disable automatic updates now.