• Content Count

  • Joined

  • Last visited

 Content Type 


Member Map





Everything posted by Igor

  1. This way of communication we would also like to limit: Pushing on developers with "is it ready" , "where can I see the results of your work", "where can I test" ... and when that brave abuser tries to get even more attention by calling out others or by sending this topic to private comm, he can (and IMO must) only get a ban. I will not discuss with them about their actions and consequences. One option is to remove or hide topic bump message, talk to the bumper and/or give warning points, but IHMO avoid to discuss if this measure is needed or not. We also have a rule not to support development kernels - but at the end this is upon each person. Main reason is that code is changing too quickly, telling users how to solve problems is changing with the same speed, its hard to stay up2date and at the end helps little. "tomorrow" fix will not work anymore. Such information is valuable to share among developers. Users has to wait until maintenance levels become ... on users levels, without too much waste of time to support. Its yet another grey zone. Bottom up. Post bumping is against "the forum law"
  2. I propose to upload known to work packages to apt.armbian.com bionic-desktop and change their version. It's an ugly hack, but patch the problem.
  3. It doesn't differ (much). Major difference is that when you start with a Debian / Ubuntu you start with a DI (Debian Installer) and install Debian to some drive. That process is identical on all x86 Ubuntu based Linuxes. Only background / colours, configurations, perhaps an application / GRUB versions is changed ... We only provide "LIVE" image because of different hardware design / scenarios. Its more suitable this way. Once you login into Armbian, all tutorials and install cases will work the same way as they work on particular Debian / Ubuntu version https://www.digitalocean.com/community/tutorials with rare exceptions when application does not come with arm/arm64 binaries (in such case you need to build app from sources). Armbian is clean Debian (or Ubuntu). The problem you have with Samba can be explained with common cheap/broken USB to SATA implementation and the fact that USB based NAS solutions are ... crap/problematical. But also Samba is not the best. I only use NFS and which works as expected.
  4. It looks like administrator has to approve the public ones. This one is approved now. Can you edit it?
  5. Another tip related to this: Searching with most probable keywords on the topic "XU4 emmc" solves the problem without more knowledgeable people. I also had to do that since I completely forget about this.
  6. https://forum.armbian.com/replies/ Do you see a button "New canned reply" and you have "edit" on the right side?
  7. Because boot loader which was once flashed by Hardkernel to eMMC (and which can't be flashed with Etcher) is simply too old and only support booting from (Windows) FAT partition ... while Armbian use (proper) Linux partitions You need to do this:
  8. We left last build sources which should be able to build that here: https://github.com/armbian/build/tree/v19.08 We provide binaries and sources, while support costs are yours now.
  9. Jessie is gone. There is nothing I can do about this. If you need something based on 3.4.y, use Xenial builds and use BUILD_TAG="v19.08" ... but if things doesn't work, nobody will fix it.
  10. It is possible that its only related to ARM builds. If you find up something, we can fix but perhaps we shall focus on 20.04 (Focal). It's inside the build system but chroot is / (was?) completely broken so we can't build some needed packages.
  11. Yes, but its just Android which is booting off at that time. But its on the table ... @chwe I meant Orangepi 4 Don't have Pinebook PRO. Yet.
  12. I also trying to get somewhere. How far did you get?
  13. Testing with help of that scripts - all of them are at least booting 20.02-RC images.
  14. We shell focus on Buster / Bionic, the rest as is, user land functions are less important ... We have to build up the way how to attract/build/promote community supported testings. Its quite time consuming task to test all this without any automated tooling. After we manage to secure some functionality and before we will try to fix bugs which will be found. I am sure people are eager to help, if they would know about.
  15. Agree. Also make use of available technology - improve exiting https://forum.armbian.com/replies that we all can use it when its appropriate.
  16. Good, get Angel subscription and I will do a research on your cost and give you a detailed answer.
  17. I have to clarify why we don't run proper public bug collection software. Linux (distribution) is a huge collection of 3rd party software and most of the reported bugs has absolutely nothing to do with our work - it is extremely hard, stupid and simply resources are not there to cover that. This is responsibility of their authors and that must be properly communicated - we are educating users all the time not to blame us if some freely available opensource package / application (which is part of the system we distribute) is not working. Free support A support that we are paying for users can come only in as is way while people expect somebody is looking into their case like when they purchase some product - its simply a matter of habit. Here, we can't do this way. We can't fix their generic problems or solve their, sometimes extremely complicated problems, nor be a middle man between them and a 3rd party software or hardware maker. Operation is simply too costly to sponsor. Support for Armbian should always start with the documentation, proceeded by search and if they really can't work this out ... raise a question. Hopefully to already opened topic. In ideal world On the other hand there are just a few people that contribute on the project which creates added value which distinguish us from a generic Linux distro. We would simply drown in a list of unrelated bugs. This can only expand frustration. That's why this forum is more like a bug listening platform. We see where problems are and fix (critical) if possible. Once there will be several millions of EUR / year we will be able to have 10-15 full timers to cover support. Then we will open a bug collection software and cover support as pro. If we want to get there, its a long (and IHMO wrong) way. Bottom up. Many things exists with a reason and I will try to clarify when possible. Other regulars are doing it as well. Thank you for your patience.
  18. Missing images uploaded ... ready for phase II. Testing. Testing. Testing. And trying to fix what we can.
  19. Experienced person might need some time to move from this heavily patched mainline kernel + patches to pure mainline + (more) patches which has to be properly sorted and not loose functionality ... Kernel sources must be the same, from this or another procedure, patches cleaned as much as possible and you are done.
  20. Try and wait few days. You can feel someone worked on that. Perhaps that is some ready made welcome, build-in forum which I hardly believe ... but still, its nice. If this will level up the forum culture while not making more pressure on developers and maintainers ... why not. I mean, how would we get anywhere without changing anything. Make a plan, let's discuss it - consider my suggestions as from any regular user and then put into action. I am sometimes too emotional and get pissed off - you, on the other hand, can be more detach and act more politically correct in term of pure abuse from the users side. My tolerance is low to be nice and friendly when I see that ...
  21. By using Google and Nextcloud support if exists. This is not specifically related to Armbian. Armbian has identical packages relation as Debian or Ubuntu. If you find a solution for them, you find solution for Armbian.
  22. As I predicted. We (they at www.kernel.org) have some general problem ... will be sorted out eventually. Not sure if we had overlay support with that version yet. Switching kernels is always a trade. You gain or loose something which is why we provide different branches.
  23. What about using forum messaging / email system? Register at https://www.ipfire.org/ and you will see what I mean by that. Its effective and IMO overall less disturbing. Most of people are nice. They do deserve to be handled this way ... until we have to deal with damaging ass-hole. A lot of people are too lazy to use search ... we can improve that with proper communication and with tagging and merging.
  24. Bug found. Not all images were made. Possible cause is running out of memory due too too many images building at once.
  25. Almost done. Last images are uploading ... few minutes to go. First problem / question - regarding deleting RC images when new one arrives. Currently they are just being added and we will have them all in the archive and on torrents, each time I re-run the batch.