• Posts

  • Joined

  • Last visited

Profile Information

  • Gender
  • Location

Recent Profile Visitors

22694 profile views
  1. There are 1000+ people that also wants to kill me with a "favour", which is nothing else but covering your interest. Don't you agree? I have give you those links that you will follow and perhaps understand. More then that it is not possible to do. We are supporting you with best effort and our effort is already at a very extreme range. If you find a bug, but you would like to fix it, hire someone to fix it for you and send a patch: https://docs.armbian.com/Process_Contribute/ You don't need to give me money. Give it to someone else. This is your support contract: https://github.com/armbian/build#support @Süleyman Poyraz Topic was split and moved to respective "board bring up forum" ...
  2. I think by editing /etc/default/armbian-motd and changing STORAGE to something else than your hard drive device.
  3. https://github.com/armbian/build/pull/3115 This should / will be fixed with an update when it will be issued. When there will be time for that. Try with self build image. Debian officially release Bullseye just two weeks prior to our release so it was a hard decision. We are expecting problems to happen, but there is little to be done, especially if bugs are coming somewhere from Debian packages, we don't maintain. Or changes in Debian changed our features into bugs. Hard to tell without research.
  4. Things are missing with a reason - support costs real money and we receive no help in this regard. All what exists or lets say most is a gift from developers community around Armbian. First cover this - currently your share is below 0.5%, then asks for more. Cover expenses of this question is our cost (answering support questions is another way how we loose our money while receive nothing in return, usually not even a genuine appreciation), which means we are not even close to possible to cover actions of your questions. Not a single cent (!) never ever came from a direction of Asus or Radxa, while your donations are not covering the electricity costs of the server this message is stored Since you are asking for some services, I understand you have a plan how you will cover expenses of developing them? We don't. Growing Armbian more on our expense is just not going to happen. It is on you to cover the level that is now. For start cover existing expenses away from us or join and do things we need to do in your interest. https://forum.armbian.com/clients/donations/ Donate 20.000 EUR (per year per board), and we will happily provide support and I will not need to waste my precious time for informing you how there is nothing we can do for you ... Instead of sending questions here, keep continuous pressure to vendors - why they don't pay this relatively small bill? And repeat that question over and over again. Tell your friends to do the same. And contribute as much as you can. Then perhaps things will change and your question won't sounds ... ridiculous.
  5. In current armbian-config, we have a broken desktop install on top of CLI images, while I have made several checks and come to a conclusion its fairly simple to install desktop. Which could be a nice first working functionality in the new armbian-config. And a reason to start moving on. 1. Available desktops per release for select box: apt-cache search armbian-$(grep VERSION_CODENAME /etc/os-release | cut -d"=" -f2)-desktop- | cut -d" " -f1 armbian-focal-desktop-gnome armbian-focal-desktop-xfce armbian-focal-desktop-budgie armbian-focal-desktop-cinnamon armbian-focal-desktop-deepin armbian-focal-desktop-i3-wm armbian-focal-desktop-mate armbian-focal-desktop-xmonad All those exists in repository and are up2date. 2. Installation echo lightdm | sudo tee -a /etc/X11/default-display-manager DEBIAN_FRONTEND=noninteractive DEBCONF_NONINTERACTIVE_SEEN=true apt-get install --install-recommends -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" -y armbian-focal-desktop-xfce 3. After install - more or less copy / paste https://github.com/armbian/config/blob/master/debian-config-functions#L780-L819 I would start, but my brain is stuck in stack overflow mode
  6. 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.
  7. Problem was fixed and its super cool that solution was found this fast. Its not uncommon that a weeks goes by and a problem is not solved (you can imagine expense of lost week, while users are willing to give perhaps 20 USD for that while asking for more at the same time). You just need to wait that maintainers and infrastructure makes the rest. I don't have information, when images will be up - its a complicated procedure since its not designed to satisfy just one person needs. Checking manually when correct image will show up (you can also do that) and manually notifying you is not an option.
  8. I think I have found a fix. I made many reboots with most recent boot loader and it worked fine, perhaps just on this board. HDMI is up. It will take few days that fixed images are populated around CDN. (when version 21.08.2 shows up).
  9. Those boards - even they are old - makes us grey hair sometimes. You can see down in the Allwinner A20 forum: which we mitigated with this: https://github.com/armbian/build/pull/2963 but it seems we loose HDMI on this particular board. I am looking into it.
  10. Some updates on the topic: https://github.com/armbian/mirror
  11. FAT partition is not needed, perhaps only for amateur usage. So that people who have Windows, can access this part and change thing. While most of them have no knowledge what to do with those files, so it is pretty irrelevant. FAT partition is there because all those distro tries to mimic Raspberry Pi, while cheap mainstream toy is not our amusement to follow. Raspberry Pi can't boot from anything else due its proprietary construction ... Armbian controls this hardware with a very different modern hardware interface, written from scratch, from the moment you plug the power. There is no relationship with the demo level software you are mention as a working ones. Those were made just to present hardware functions and abandoned right after then. Many years ago. I am sure you don't want to use those and I highly recommend you to stay away from those other (fake) distros. Also make sure to read this. We need to know: - exact version of boot loader (u-boot) very early print - armbianmonitor -u (if you have network operational) - cat cat /etc/armbian-release - do you have monitor attached and what kind of - how do you power the board Helping you is our expense. You can also try asking for support at Lemaker, but I am 100% sure nobody will answer to you. Not at any distro you are mentioning.
  12. Likewise My distribution of choice was also Slackware - IIRC v1.0 / there was no much choice at that time - and Linux kernel has version below 1.0 at the time A lot has change since. With totally limited resources we are trying to make this very complicated, purpose driven and diverse ecosystem as simple as possible.
  13. If this device is not along known to work ones, nobody knows until its plugged. None of those vendors (Radxa / Adata) are supporting us, so we don't have devices you are asking about in the lab. Also even hardware would be on the table, who will cover the time for testing? I don't need to know this to waste my precious time ... No idea. There is almost no interest from community to improve testings which means we can only run basic testing and what you are asking is certainly not. It would require manual testing, which is simply too expensive if we pay everything. For you and the vendor of your choice. Download and test. I would need to do the same. Then report. It might help someone.
  14. Supporting his / our work? https://docs.armbian.com/User-Guide_FAQ/#development-time
  15. Will be fixed in next release. Until then, check Docker documentation for installing on Focal.