All Activity

You need to set this to y or m in your kernel config. https://github.com/NickAlilovic/build/blob/v20250306/config/kernel/linux-sunxi64-edge.config#L5745 https://www.kernelconfig.io/config_usb_acm

I guess that would answer the last part of my question, thanks. Any comments on the work in that branch?

Okay I gave up on it and done a fresh install.. Took me 5 hours to get it back up and running, to reconfig x11vnc and samba stuff. Starting a freshly baked image proved to be a nightmare - for whoever is interested I share my story; For some reason it did not detect wireless dongle for keyboard. So I could see it over hdmi but no input was possible. Did not have a wired keyboard at hand. at first run it did not became accessible over ssh. but an ip address was assigned to it by dhcp router; I could see a new ip when I'd start it up. but it would not respond to ssh requests. But serial connection saved the day. Luckily I did have a serial adapter. Created username/password and then it was accessible over ssh and I could ditch the crappy tv screen I was using Selected wrong locale on setup, was unable to get rid of it without commenting wrong locale lines in ~/.bashrc Then I spent some few hours to get vnc up and running with lightdm and crapload of other dependencies, packages. Thanks AI for assistance. When asking quality questions and sharing messages/outputs it was super useful (I dont keep anything confidential there) Manually created /home/domas/startxfve_headless.sh script, made it executable, the whole orderal Not to mention xfce was not installed by default on this debian/minimal image. It was fun one too. https://docs.armbian.com/User-Guide_Armbian-Software/Desktops/ - armbian-config --cmd XFCE01 just ran the script and nothing happened without any error Had to do it manually but I think it worked the first or second time. And the most fun one since it included multimeter and soldering iron: then it did not detect my disk over sata no matter what I do. Apparently measured 0v at hdd power connector. Not sure how I killed it. After some fiddling around I connected jst connector's for hard drive 5V power to one of gpio pins that supply 5v. HDD spins up - YAAAY. It was short-lived. Disk Still undetected. Probably usb to sata controller is not powered on since 5v regulator fried. (thanks AI for ideas) So then I jumped a wire from said gpio 5v pin to the back of what used to be 5V connector for hard drive so it both feeds the disk and backfeeds the boards 5v regulator with the needed usb to sata controller. I don't use gpio. ITS ALIVE. No, I did not believe it would work. But at this point I had nothing to lose. Sketchy? Yes. Have I ever pulled worse? Sure. Proud of myself? You bet.

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: