All Activity

We have discontinued maintenance and support for this hardware, as our collaboration agreement with the vendor did not move forward as planned.

Thank you for sharing it Can you include these specifications, for quick reference for future readers? Board, Debian version, Kernel, Graphics (console, X11, wayland)

Bluetooth also works

I finally successfully updated Nextcloud to version 31.0.10 on my Odroid N2+ 😅 Despite all official information, an update is possible on a system running nextcloud installed via the script ! It is not necessary to buy a new hardware just to run nextcloud on your Armbian SBC in order to get the update. I did the following: Updated nextcloudpi to version 1.55.4 which was never released but just tagged on github Nextcloudpi tagged page on github via the ncp-config menu system (Updates/nc-update) Updated nextcloud to version 31.0.10, again, via the menu system (Updates/nc-update-nextcloud version 31.0.10) I don't really know why this information is not readily available on the nextcloudpi github page nor anywhere else I looked. Have fun Norbert

@TonyMac32

@c0rnelius I would like to report back with the news of full success: I have updated cmdline.txt to start with: console=tty1 console=ttyAMA0,115200 earlycon=pl011,0x107d001000,115200n8 And also added the following to config.txt: usb_max_current_enable=1 enable_uart=1 dtparam=uart0 dtparam=uart0_console dtparam=pciex1 dtparam=pciex1_gen=3 dtoverlay=disable-wifi-pi5 dtoverlay=disable-bt-pi5 All this with the HAT+ (in the picture above) still connected. The early boot console also works, and I also get a login prompt, which is all I wanted. After this I tried replacing ttyAMA0 to serial0 in cmdline.txt, to see if there is any difference, but they both seemed to work in the end.

Not exactly. CH341 is the connection of my printer (Klipper), and here all right: [30663.467079] usb 3-1: new full-speed USB device number 3 using ohci-platform [30663.665820] usb 3-1: New USB device found, idVendor=1a86, idProduct=7523, bcdDevice= 2.64 [30663.665867] usb 3-1: New USB device strings: Mfr=0, Product=2, SerialNumber=0 [30663.665891] usb 3-1: Product: USB Serial [30663.668223] ch341 3-1:1.0: ch341-uart converter detected [30663.680198] usb 3-1: ch341-uart converter now attached to ttyUSB0 Accelerometer board: [30617.149526] usb 4-1: new full-speed USB device number 22 using ohci-platform [30617.358206] usb 4-1: New USB device found, idVendor=1d50, idProduct=6177, bcdDevice= 1.00 [30617.358227] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [30617.358235] usb 4-1: Product: rp2040 [30617.358242] usb 4-1: Manufacturer: katapult [30617.358249] usb 4-1: SerialNumber: E6647C7403433637 It looks like Armbian needs a driver. When connecting this card to Windows or Mac, the device is identified as a serial port. Probably, something like this - Enable ACM

I'm referring to this board: https://www.vividunit.com/Main_Page tonymac32 has a branch for it on https://github.com/Tonymac32/build/tree/vivid but it hasn't gotten updated in a while and is not merged into the main repo.

@AndroidNewbie, what kind of help do you expect to receive? @Ducdanh Nguyen, are you sure it was my modified update.zip (hint: open it with any archiver and see for file "wipedata.flag" - is it there?)? Are old settings and apps stays in place after flashing? Are update.zip located in root of sd card? If all answers is yes, then try to update using usb flash drive instead of sd card.

That's an interesting question. The chip itself seems to communiate via spi or i2c. Since USB cannot do that they put a raspberry microcontroller (RP2040) on it to handle this. The communication then uses a simple serial connection with the ch341 chip. I assume the klipper thingies can handle this by themselves automatically while when connecting this to a different device, you have to come up with some way to communicate with this board.

Which of these boards are you refering to? https://github.com/armbian/build/tree/main/config/boards

I have my kernel locked to 6.1.75 but still after 25.8.2 update, I lost all USB devices on both of my Orange PI 5. Only the USB3 port is working. The only way I've been able to get access to the USB is by switching to the latest `current` kernel... Any clues on what is going on? Firmware or kernel upgrades are not doing anything... where can the issue be???? I tried downgrading to many different versions but beside the current branch, USB is gone. Thanks

I had to use 6.1.75 to get the analog out working. It is the only version where the analog out works - it shows in other versions but there is no playback

/dev/serial is also gone on 25.8.2

Thanks for your post ! I have checked the source code for 1.55.4 and, indeed, it shows "nextcloud_version": "31.0.2", in etc/ncp.cfg file. That probably means, an update of nextcloud to 31.0.2 resp. 31.0.10 (the current version) would be possible. It is consistent with the update method you did. The nightly automatic backup to an external disk works fine. I have installed 1.55.4 on my nextcloud system. I'll do another backup I'll try to update nextcloud to 30.0.10 using 1.55.4 tomorrow. I'll report the result over here and mark it as solution, if successful. I simply wonder why any information of this possible update method was not mentioned anywhere - perhaps except on matrix. Joining matrix chat is on my to-do list, anyway. Thanks to eselarm for the hint for quoting a previous post 😀 Kind regards Norbert

There's a new version of the kwiboo ffmpeg+v4l2request function https://code.ffmpeg.org/Kwiboo/FFmpeg/src/branch/v4l2request-v3 And it was shown as a work in progress in the ffmpeg community https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20847 Then, it was noticed in the mpv community https://github.com/mpv-player/mpv/pull/14690#issuecomment-3500141427 They previously said that v4l2request first needs to be integrated in ffmpeg officially, then mpv would start working on v4l2request This is needed, to have mpv+v4l2request compiling successfully and working under Debian Trixie (my experience)

Installation of autheila package ("apt install authelia") does does end with error due to /var/log/journal beeing a symlink to /var/log.hdd/journal. Once the symlink is removed and the directory is created instead, the installation can be completed successfully. The symlink can be recreated afterwards and authelia wil steill run normally - until the next package update.

I saw some initial work on supporting uugear's vivid unit (rk3399 based). I was wondering in what state that is, what is required to complete that work and if there are plans to add that support to the mainline? Thanks in advance, Markus

Looking for help getting mine running I have a very basic understanding of this device and am learning Linux on my own if someone could message me so we can work through this I would love to get this running

OK, where would we find the images that need testing?

You have to change the fancontrol.service file and set the option PrivateDevices to no. Do systemctl edit fancontrol and insert [Service] PrivateDevices=no

Drop it in a Spoiler:

Hello, I will soon be selling a working Helios64 from Kobol (with 2.5G fix done from factory). I also have 3x 6TB hard drive that could come with it if needed. Based in France, I'm able to send within EU. Please DM me if interested.

Hi Nobi, I'm in a hurry therfore short hints for your investigation. Most info you get on matrix channel. https://matrix.to/#/!AT6qaz1QxylX2sw2mzjLElHbLKVll3kAgeIQd16e7J0/$dLsP9mV-fEjbokwdo-WqcJvg5CqsUaArfNKWWdUNPp0 Listen to the podcasts mentioned in this discussion. Yes, I have ny servers upodated to 31 and did the offered 1.55.4. update before, it is offered to running instances only (ssh boot prompt).

@NOBL You can select text of someones post and then a small popup appears; If you click that, a reply/edit field is provided. It also took me some time before I discovered, maybe it was a browser issue or webblocker before I don't know. Related to it, I also don't know how to create 'hidden' text files so no endless logs or so. Anyway, on the topic: I see indeed VM is only x86-64 focused and also no Linux default build-in virtualizer, only external/commercial stuff like VMware and Windows/Mac. So for nextcloud, it is worse then for HAOS as I see it now. For HAOS, there is some Aarch64 VM image hidden somewhere on github, no documentation, but it works, does update well. It is same principle as for x86-64 VM images, so for me, having used standard Linux virt-manager (libvirtd/QEMU/KVM) for several years after VirtualBox and after VMware, it was easy to get running and as HA has a good backup-restore option, you get perfectly the same In a Aarch64 VM hosted on my ROCK5B for example as something running on old Intel Atom computer (also as VM by the way). So I would consider the easy 'nextcloudpi' and ready made images gone; You have to dig deeper and do more yourself, so looking at all the lower level components like PHP versions etc that fit a certain version. That is independent of which ARM SBC. Nextcloud is high-level software, there is no dependency on HW pins or GPIO or videocodecs etc. If there are Aarch64 images, you have to look at how they are created. I see from other post that there is ncp command, so what does that do? If you stick to 'images', you will indeed have a problem. The only relevant difference between Odroid and Raspberry or other Aarch64 SBC is the bootloader and kernel. Raspberry is the worst as they also do many changes to Debian userspace which for example from bookworm to trixie ruined my networking setup, so I blocked specific things (netplan stuff) and went back to Debian versions. Also RPi5 still cannot run standard Debian. If you want standards, make sure your HW supports UEFI, same as every PC/MAC does. See https://github.com/edk2-porting/edk2-rk3588?tab=readme-ov-file#supported-platforms I have this on ROCK5B and NanoPi-R6C and it is like a PC. You have to install it yourself of course, it is not pre-installed like is the case on a PC. But after installed, it is like a PC. Both those boards I have bought with metal case/heatsink, so no fans. Faster than a RPi5 and M.2 M-key slot on-board, so can use standard Samsung NVME or so. Also, the current/edge Armbian rockchip64 kernel runs in/as a VM, which makes it super flexible for tests but also for 24/7 doing real things. I installed grub-efi and then it boots as VM (assumuing 2 partition scheme). For Odroid (Amlogic SoC) I would expect the same. If not, install linux-image-arm64 in addition and use that kernel.