Igor

You get anything from: v4l2-ctl --list-devices

Expected behavior (unless process breaks in the middle and files are not there for some other reason) - we only provide last kernels. Easier way to change - providing more kernels at repository - have great impact on build time, while doing it smarter would require a person to focus only on this part of infrastructure for some time ... alternatively, we could drop all deb packages to some location, but again someone (not me) would need to code and maintain this automation.

Maintainers don't work for Armbian, that’s an open source project. We are volunteering our free time ... and you are kindly asked to not call us on "home phone". This should be clear. I am solicitation developers and maintainers to ignore all private (and in majority emotional blackmailing) communication. Sometimes abuse still works and they got vandalized and you could even break them eventually ... and they stop helping you. Please don't take this personal. Its a relationship between open source end users and developers / maintainers. Fork the code, fix it (probably just need to enable something https://github.com/armbian/build/tree/main/config/kernel) and submit a PR. Or wait that this complains you posted on forum is heard by someone that has time and will do this. Instead of you. You can file a bug to Jira, but makes almost no difference. Maintainer will address this issue when he find the time and if he wants to. This is how things works in (non Desktop *NIX OS) open source world. Embedded (especially with vendor kernel as in this case) Linux is (far) away from simple and unified x86 Desktop *NIX OS. Many things has changed, but primary problem is that vendor (Hardkernel) switched their primary kernel from 5.4.y to 6.1.y ... and feature breaking is what always happens at such kernel changes.

https://docs.armbian.com/Process_Contribute/

ARM was perhaps not in good shape in Jessie / Buster era. Today, Bullseye and Bookworm should be in perfect state. I suggest you to upgrade to and then try again. Or start with a clean image.

Older in archive.armbian.com No official listener anymore If someone will take it from here or it will remain broken. There is nothing we can do about.

User-land package control comes from upstream. https://www.google.com/search?q=Package+mysql-server+is+not+available 1st hit https://stackoverflow.com/questions/20259036/mysql-package-mysql-server-has-no-installation-candidate It should work the same way, but method is not officially supported (yet).

Boot from SD card and install it classic way (armbian-install) doesn't work?

Armbian comes in many different variants. This could be a bug in Debian SID package base or the one you are using. Where do you observe this? (armbianmonitor -u) I am running Armbian desktop (running Chrome / Firefox) on two machines without any issues. PSD is active.

Images with support on general Linux support level (not better not worse then alternatives) can be downloaded here: https://github.com/armbian/community

Key is not deprecated, method is. On Noble / Sid and future. sudo wget https://apt.armbian.com/armbian.key -O key sudo gpg --dearmor < key | sudo tee /usr/share/keyrings/armbian.gpg > /dev/null sudo chmod go+r /usr/share/keyrings/armbian.gpg sudo echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/armbian.gpg] http://apt.armbian.com $(lsb_release -cs) main $(lsb_release -cs)-utils $(lsb_release -cs)-desktop" | sudo tee /etc/apt/sources.list.d/armbian.list apt update

Not even our kernel not even our OS, closing. In case you need help, you have a PM.

Another one: https://www.digitalocean.com/community/tutorials

Stick to this board: https://www.armbian.com/bananapicm4io/ So far we have a person behind and a tiny budget, so our personal finances are not blown in 100%. Behind Orangepi CM4 we have nothing except random community work and with this it is not possible to plan any actions.

No idea. its a part of stock Debian timezone & locales generation. Here: https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=tzdata;dist=unstable https://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=locales;dist=unstable

It is. - Armbian works perfectly well on 1st class hardware such as x86, ampere aarch64, raspberry pi, ... - Armbian also works well on our test devices https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results - Armbian boots normally on 16Gb Orangepi Plus 5 https://paste.armbian.com/quzavajida (Armbian_23.11.1_Orangepi5-plus_bookworm_legacy_5.10.160.img.xz) It is certainly a hardware issue without even looking into the logs. What is then? Vendors often change memory chips (sometimes without telling anyone) so only their images works with a new batch of boards until we waste insane amount of time to figure that and fix = huge blow for our personal time / finances ... A change of memory chips is enough that things crashes, different (broken) wireless driver (i didn't look into logs) is used, something odd is attached to USB / HDMI ports ... Try bare hardware, different SD card, different power supply, make a photo of PCB (revision, memory chip numbers, ...). Where do you think they took (stole as they didn't tell you where they got it) software, that looks the same as Armbian, from? FYI. All images are assembled the same way and builds are now even reproducible. Its highly unlikely that one image will boot and the other wont.

do not install WG it as: - its already present in all kernels - as their postinst scripts installs kernel from Debian repository that is not suitable to run on this device ... which breaks the system.

This is what it does: https://github.com/armbian/config/blob/master/debian-software#L830-L863 It adds normal user, under which will be installed, if not there, and proceed with their script.

Perhaps it doesn't work. More resources / ideas / background: https://www.google.com/search?q=blacklist+USB+UAS+armbian https://www.cnx-software.com/2020/08/12/how-to-fix-unreliable-usb-hard-drives-stalled-transfers-linux-windows/ https://leo.leung.xyz/wiki/How_to_disable_USB_Attached_Storage_(UAS)

We measure this automatically every day: https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results 970Mbit/sec

Odroid N2 has poor USB implementation. You need to blacklist UAS support (which will slow things down) and it will work. Search forum (or Google) for tips how to do that.

It works: https://status.armbian.com/ Perhaps some network related issue.

This fixes it: