Jump to content

Igor

Administrators
  • Posts

    13608
  • Joined

  • Last visited

Everything posted by Igor

  1. Also on 1st class hardware it does not go without issues: https://www.google.com/search?q=why+kernel+upgrades+breaks+features On trash ultra cheap and forgotten hardware, where Armbian is trying to make a difference, breakage % is significantly bigger. Every kernel, that is work of thousands of people (some forget to test changes), breaks features even we invest tens of thousands of hours into stabilizing it. There is virtually no support from industry and no support from end users, but we still managed to build automated monitor for upgrades on many boards in automated way: https://github.com/armbian/os?tab=readme-ov-file#latest-smoke-tests-results Sadly, we don't test Pinebook, not complex functions as this and not all possible upgrades. Expanding testing to that and patching would cost additional few millions which is simply not possible to secure from this. In past year, nobody applied to serve as test engineer to develop this further. Other Linux distributions are far far away even from this. Install Armbian on a desktop PC.
  2. We also have plenty of memory nowadays and memory is still significantly faster then ssds and does not wear out. sudo apt install --reinstall profile-sync-daemon This is probably all we do here: https://github.com/armbian/build/blob/main/packages/bsp/common/usr/lib/armbian/armbian-firstlogin#L215-L237
  3. Download Armbian with HA Then boot the image, wait few minutes and login via http://ip_address_of_armbian_running_ha:8123 (official onboarding manual) Home Assistant Supervised is, more or less, a full blown Home assistant. Main difference between HA OS and Armbian with HA is that underlying OS here is clean Armbian Debian Bookworm and there is custom dedicated buildroot OS that is provided for a few single board computers, primarily for Raspberry Pi. We provide HA on a small selection of single board computers, but in theory, its possible to run this on (almost) all that are possible to build. I am running HA on Odroid N2+ and it works without any problems. I have z-wave network with sensors and switches, air humidifier, Android TV, Android phones, dishwasher, ... Things works flawlessly, much better then few years back when I started with home automation for a first time, with OpenHab. This time it was setup from scratch and in a matter of days, most of devices are in function, playing with automation. Tested on: Odroid N2/N2+ Odroid M1 Nanopi R4S Uefi-x86 Khadas VIM1S Khadas VIM4 (Amlogic vendor kernel trouble, failing / need inspection) Bananapi M2 Pro Provided for but untested (images you find on board downloads locations, seek them here https://www.armbian.com/download/😞 DIY Contribute Support: single board computer hardware https://www.armbian.com/bugs home assistant functions https://community.home-assistant.io/
  4. Another possible infra related issue. This mirror is temporally out of service, possible out of sync / order. You should always start with beta.armbian.com or dl.armbian.com directly. They are behind redirector which gets data from database while (double) checking for health and sync status.
  5. Yes and no. I would say its just a bug, nobody to blame in particular. Try their official Ubuntu image with this 6.1 kernel if this also manifest there, so it can be narrowed. Open source projects are far from ideal circumstances We only provide email support for partners, where we have some control and don't need to pay 99.5% of hard cash costs that conversation (and previous hard and frustrating research work) will generate. With 0.5% of general public support (share of end user donations in this project), we already have problems to maintain a lot cheaper segments of this project. Providing email support is super expensive. Its not just you. Its thousands of often frustrated and angry customers of somebody else that would rather talk to an expert directly and not to anonymous forum. In human population we also have a small percentage of people that never respect any rules, act predatory, play dirty ... They would destroy mental health of people on such support and subsequently project in no time if we would provide / allow this. This can also be observed on forums ... Email support is not possible, even you would be willing to pay for it. Most of open source projects explicitly asks their users "please do not contact us for technical support, use community forum for support". Neither do developer without investing his time into research. Nothing here was meant personal. I just tried to "visualize" this communication. I do understand your frustration, but we are already doing the impossible. Odroid XU4 is having vendor kernel made around latest LTS. It was never true LTS ...
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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
  11. Boot from SD card and install it classic way (armbian-install) doesn't work?
  12. 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.
  13. Images with support on general Linux support level (not better not worse then alternatives) can be downloaded here: https://github.com/armbian/community
  14. 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
  15. Not even our kernel not even our OS, closing. In case you need help, you have a PM.
  16. First meeting of the year: https://us06web.zoom.us/rec/share/e-w3eQ5I1-mUoUzziUJWI9lAQyVy7z6H_PPJJ3d9HbUf51tUYuMwnHzlduHNTVb1.8_TlzRbNSc1SPFUP
  17. Igor

    Orange Pi CM4

    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.
  18. 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
  19. 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.
  20. 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.
  21. 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.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines