• Posts

  • Joined

  • Last visited

Community Answers

  1. Igor's post in Can I install linux-generic-hwe-20.04 kernel for Armbian Focal? was marked as the answer   
    Why would you want to downgrade to the generic Ubuntu kernel? (where its highly possible you will not even boot)

    Agree. You are already at best possible variant ... which could ofc be polished.
    Do you know why Armbian builds kernels almost for all platforms? Because in ARM diverse world it is not possible to trust to Ubuntu, Debian, or kernel.org.
    According to your questions I would assume you are not very familiar with the situation in ARM hardware world and it would be good to check FAQ:
    "Armbian fancy some kernel development and a lot of its maintaining. Debian relies on upstream sources for ARM hardware which can be years behind and/or lack of many functions". For Ubuntu this is just a little bit better then Debian.
    Armbian kernels are (ARM HW) HWE by default, all of them: https://github.com/armbian/build/tree/master/patch/kernel/archive
    Armbian is hardware enabler for the device you plan to use. Not Ubuntu, which actually don't support those devices. https://docs.armbian.com/User-Guide_FAQ/
    Also, when you will run into troubles ... We are already unable to assist Armbian (kernel) users, so other (Ubuntu kernel) users comes last. In reality - never.
  2. Igor's post in [Invalid] - this is test question was marked as the answer   
    Your issue report is not a valid bug report per the Armbian bug reporting instructions (https://www.armbian.com/bugs).  With limited resources the Armbian project is only able to spend time on issues where all the requested information has been provided and for only the boards/images/software that are supported.  Your report is invalid for one or more of the following reasons (non-exhaustive list):
    it is for an unsupported board or image (CSC/EOS/WIP/edge) it is for software that is not supported (such as userspace modules installed on top of the core operating system) it has been logged in the wrong forum (for example requests for help that are not actual bug reports) it lacks requested data (armbianmonitor output) it could have been easily solved by a quick search and/or reading documentation  
    Please review what you have submitted and the bug logging instructions (https://www.armbian.com/bugs) and either add the required information or open a new topic in the correct forum (such as P2P Help or Off-Topic)
  3. Igor's post in [WARNING!!!] wireguard-manager script is wiping /etc/wireguard !!! was marked as the answer   
    Yes, better some tools then no tools, but probably we should just move to packaged version or to more recent version ...

    If you like to help - provide merge request with TAG from git which is ok. If none, contact authors, open issue to them. We are in the process to scale the project down because we can't pay for everything users find in open source software. I used to lost up to 10 hours daily just for communicating with users request. Now I just ignore since that can only lead to insanity. To get a picture how this "armbian maintainers - do something" looks like.
    That is the best what can be done. 
    FOSS is released without any warranty because we can't pay for service users would wish to have. Fixing bugs in SW made by 10.000+ people. We can't cover even much less No interest, most users doesn't even understand the value ... fast forward. https://www.armbian.com/newsflash/armbian-needs-your-help/ There is some interest but still we are far far away, not enough to boost support on levels users would imagine to have (without paying developers for the time they will lost). Someone that will fix troubles that might be hard, not fun and by much higher pressure they are used in their well paid professional environment. In real-time and on their personal expense.

    This project is backed by amateurs, by you and me and other people that like to play with those devices. There is not formal support as such (it goes under as is, best effor support) -  Armbian is not Red Hat https://en.wikipedia.org/wiki/Red_Hat with 10.000+ full time engineers looking to the code, made by them and others.
  4. Igor's post in Upgrade install on Rock Pi S. No serial console with Focal Edge image. was marked as the answer   
    Yes. It is clearly written on the download pages https://www.armbian.com/rockpi-s/ (Modern kernel serial console is on UART2) I have personally lost a week trying to fix this "small" problem and I will not repeat this ever again. Armbian is dropping official support for this hardware, images and upgrade will be no more ... Not your fault - we also made mistake trusting this vendor. You (anyone) can pick up and proceed with support to keep it at least on this level as now.
  5. Igor's post in [Solved] Problems setting up armbian desktop using armbian-config (lightdm-greeter) was marked as the answer   
    Bug is actually outside Armbian domain - we are 1000 x too small to be able to fix bugs in community maintained packages -
    https://www.google.com/search?q=lightdm-gtk-greeter+bug - fixed in desktop build scenario, forgotten to fix in armbian-config.
    We have replaced buggy greeter with slick-greeter which is why desktop still works just fine.
  6. Igor's post in Bullseye: Automatic upgrade when unstable becomes stable? was marked as the answer   
  7. Igor's post in Problems with the RTL8192cu driver was marked as the answer   
    In fact it is. Starting with v197 systemd:
  8. Igor's post in RockPro64 fan disabled was marked as the answer   
    Modern kernel luxury comes with a price:

    If you want Armbian with the same functionality, but also no updates to the kernel, pick Armbian with a kernel 4.4.y which is still provided for this hardware.
    Perhaps fan support works and just need enabling?
  9. Igor's post in Enable Lima hardware acceleration was marked as the answer   
    IIRC there were some issues on Debian user land and 3d acceleration and I assume they still exists (Buster is too old for fancy stuff). Its known that it works on Focal  / Hirsute. Since we just started on adding 3D support, this is certainly not present on images that are currently available. Its coming with a next release 21.08 / this month. We only have packages for Ubuntu based builds - they came from here. We have no plans to support 3d on Debian desktops since this represent extra work and maintenance burden.
    As i notice https://github.com/armbian/build/blob/master/config/targets.conf#L522-L530 we didn't enable on 32bit probably because we need someone to test if it works. Build from sources is needed at this point. And remember to enable 3D since its not enabled by default.
  10. Igor's post in Cubietruck updates break? was marked as the answer   
    This is the problem and the solution:
  11. Igor's post in The repository 'http://apt.armbian.com xenial Release' does not have a Release file. was marked as the answer   
    Our system only publish packages for supported distributions. Xenial is EOL from our maintaining perspective. We have to cut what is not important, but eats resources.
  12. Igor's post in mirrors.netix.net/armbian/apt stretch Release -- Not Found was marked as the answer   
    There is nothing wrong on our side - we just don't build and publish our package upgrades for Stretch repository anymore. (automatically) Only for those marked as supported: https://github.com/armbian/build/tree/master/config/distributions Support from Debian ended 01 Jan 2020 and I assume kernel upgrades, which are anyway coming from us, are at Stretch going to die June 2022 (this info is extracted from quick search on the net, so its not official)
  13. Igor's post in ORANGE PI PC PLUS is not booting, and tried both images from the site was marked as the answer   
    Another option is to boot images from archive.
  14. Igor's post in The repository 'http://apt.armbian.com bionic Release' is not signed. was marked as the answer   
    This problem should be resolved. CDN needs several hours ... so perhaps not right now.
  15. Igor's post in Clearfog build only u-boot? was marked as the answer   
    Actually it is, but perhaps not well exposed in documentation:
    ./compile.sh 'compile_uboot'  
  16. Igor's post in lightdm crashes after recent upgrade was marked as the answer   
    Try perhaps this: 
    apt install slick-greeter + reboot.
  17. Igor's post in In need of direct link for desktop download: bananapi M3 was marked as the answer   
    But there is no desktop variant for this hardware so you need to:
    - download CLI and enable XFCE desktop via armbian-config -> system -> enable desktop
    - build desktop image with https://github.com/armbian
    - only Armbian. We don't provide Debian ...
    And this board is not supported. Which means we don't know how good or bad it works ... I know it boots, but that's about it.
  18. Igor's post in Odroid HC2 Hard Drive not found / readable under Armbian Focal was marked as the answer   
    I highly suspect this is something to do with filesystem driver incompatibility between kernel 4.14.y and 5.4.y. We don't support BTRFS even commercially, but you can find commercial support elsewhere https://en.wikipedia.org/wiki/Btrfs#Commercial_support Perhaps there is a way to upgrade somehow ...
    Plan B will only cost you your time. Starting from 4.14.y, coping elsewhere, starting with 5.4.y ... or staying on 4.14.y.
  19. Igor's post in error when installing docker was marked as the answer   
  20. Igor's post in Asus Tinkerboard on kernel 4.4.213-rockchip bricked after shutdown was marked as the answer   
    By opening a ticket https://armbian.atlassian.net/browse/AR-776 my job is done. I have other troubles to deal with.
  21. Igor's post in arm-config not able to install linux headers (grep error) was marked as the answer   
    Problem was fixed, but you need to apt upgrade and reboot.
  22. Igor's post in PPS on NanoPi Neo3 (RK3328) - can't get it to work was marked as the answer   
    We don't support 3rd party (commercial) projects you are using, sorry. This forum is dedicated to https://docs.armbian.com/User-Guide_Getting-Started/#how-to-check-download-authenticity under those terms https://github.com/armbian/build#support I am sure this doesn't matter to you, but it does to us. We already can't allocate enough resources to support our users, while we never had intention to support others or under some general terms.

    It seems you are not (very long) a part of this community, otherwise you would know this forum is not a technical support service and we have a tool for reporting troubles. When you get rid of Dietpi overlay, start here https://www.armbian.com/bugs If this is a feature you are asking for https://forum.armbian.com/forum/38-feature-requests/ waiting time is measured in years.
  23. Igor's post in Turn off monitor AFTER system Halted was marked as the answer   
    It certainly works with their legacy (partially closed) stock SW / kernel interface, but for providing this function on a modern kernel, a complicated technical problem is waiting for you. Things has to be reverse engineered and port toward modern kernel base. Current status / more info here: https://linux-sunxi.org/AR100 and here.
  24. Igor's post in Tinkerboard build, no overlay folder was marked as the answer   
    Most of the stuff in modern mainline kernels has to be developed from scratch (or ported). Asus has nothing to do with that. Also we developed many enhancement and fixes for their private legacy kernel. You don't need, it's a waste of time, to deal with outdated & unsupported TinkerOS in any way.
    But I can't tell if we will develop overlays for Rockchip armhf family or Tinkerboard specifically. We have to plan according to available resources. Which are very limited / expensive.
  25. Igor's post in After apt upgrade unable to boot was marked as the answer   
    This "board not start" section only covers "Impossible cases - when official armbian builds from the download section doesn't start at all". Moving to Bug tracker section.
    If you still have both kernels installed, this is certainly bad and possible source of troubles. Try recover this way https://docs.armbian.com/User-Guide_Recovery/ and remove one kernel, together with its dtb package.