All Activity

This stream auto-updates     

  1. Past hour
  2. if we have the same naming as ubuntu, people expect the same behavior (e.g. 20.04 being then a LTS version). I would consider being part of LTS on one kernel as long as we have a proper definition such a LTS "project" (e.g. features don't get back-ported, running boards more conservative to keep the maintenance coast lower). Without clear 'rules' what people can expect from a LTS-like build and what they can not, it doesn't make sense.
  3. I'll guarantee that it will be sufficient.. We even let US citizens write our documentation.. Honestly.. A bunch of people (including me) are not native native english speaker (and writer) so we'll never have 'the perfect' documentation.. But it's not the marketings department here writing some fancy stuff for the next hot shit.. It's that others understand how to do it. So as long as others can follow the instruction after your writing everybody will be fine with it. And if it's understandable or not can be tested by letting someone build under vagrant who didn't build before. that's just the old text we had there as well.. (but there are rumors that even some devs here sometimes build on native hosts - shh.. it's still not recommended. ) we just don't have that branch anymore (dev branch of buildscript).
  4. @Igor, @mother, I normally build with Vagrant, and things were working fine three weeks ago. I realize that the changes that were made two weeks ago moved some files that used to be in the "build" directory to have been moved to the "build/config/templates" directory. That is , for example, where the Vagrantfile is now. I just tried going to that directory and entering Vagrant up Vagrant ssh cd armbian ./ and the build has definitely started I am not sure whether this was the intent, that is, to have people build from the build/config/templates directory. Butdoing this right now this might solve Mother's initial issues. It looks to me like a lot of the changes made were actually for Docker, and I haven't yet had time to figure out whether the whole userpatches move has anything to do with Vagrant.
  5. I'd recommend keeping Kobol's option of the little clear window w/mounting holes on the front panel for the OLED status display.
  6. Hi adodago, sorry for the late response: this may not end up being helpful, but in the past when supplicant files for WiFi connectivity haven't worked for me I've used 'nmtui' from Network Manager to do the initial connection legwork, and then extracted the correct values out of the nmtui config files later. In my experience it's been able to connect to all APs I've tried.
  7. Yesterday
  8. Wondering what the OMV Image is made of. It is for the Raspberry PI, but is Armbian based.
  9. Sorry for misunderstanding. I was referring to HW sellers and makers in general. Some are better in this, some worse but I am afraid that its a common marketing practice to forget about that detail. When Pine64 (and other similar boards) appeared on the marked, their low quality board support package (boot + kernel) came with many closed sections - basically chip makers SDK. We/community had to reverse engineer, wrote from scratch, fix bugs. Most of functions of the Linux kernel are free but not the drivers you already exposed. That is IMO too expensive to hack, make from scratch and will probably never be. This means such devices will always need a black box to function. (I hope not) Its about how this device is presented to the public but if you look around ... Raspberry Pi. People don't care or have no idea what that means. Sadly. That's good to know, but we would probably need something with AC radio in 2020. Probably they choose 8723cs also because of Bluetooth. A compromise. Bottom up, there are no free phones.
  10. He did the implementation and last changes:
  11. Hi Igor, It seems that i didn't pointed out clearly what I am heading for. Sorry about that in the first Post i added: I already managed to build an running image. This Thread is about the Documentation. So I am willing to update the unclear points in the docs if my English is not too bad. I just need a tipp from someone who knows how vagrant/virtualbox building was intended to work, because i have no clue how this virtualisation stuff work in detail and what could mess up what ! for me version a) just worked find and i got a good running root-encrypted image. I just wonder if there are some cons to a) and some good pros for b)
  12. If you are referring to replicant I do not agree. I tell people purism has been misleading, omitting and vague about free software and their products. If pinephone gets on sale for the general public and it gets marketed as a free software or open source phone without detailing which devices on the phone require non free software in order to run then I will tell people the company misleads people. thinkpenguin told me, the usb 9271 wifi card is still being manufactured. And it should be able to fit in a phone. According to pinephone's irc they had not considered the ar9271 usb option. One solution might be to add a nano usb hub to a later pinephone mainboard. Pinephone's irc said, there is no sdio slave controller for the ar9271.
  13. Yet another version of IRC. This time for 8.5 MIO $
  14. Xfce work successfully with panfrost (mesa 19.2, nanopc-t4).
  15. Aha, my bad. Completely forget about that. If Vagrant magic doesn't work, perhaps just manual way by installing Ubuntu 18.04 into the VirtualBox? And then compile native inside that.
  16. Ok its fixed and stable for three days. Updated firmware, removed mate and gnome desktops. Permanently mounted USB drive at boot. Samba running fine. Cheers, Chris
  17. @Igor This is OT but here is my point to your answer: Not really. Building for stretch (I didn't tested bionic) still works. CRYPTROOT_ENABLE Developer zhiverbox stated So, buster didn't worked from the beginning i guess. this Thread : is about getting buster to work. To my "I have to use vagrant" problem: Building "crypted-root"-images is not supported in docker. (see Quote above). And here is a (quiet old) statement from zhiverbox not to build natively. I learnt the hard way that building natively or in docker still does not work But anyway. Back to the topic: I'd love to hear form someone what would be the right approach to build inside vagrant/virtualbox.
  18. Hi all, is there a way to fix the characters set problem using uart? look the pics below.... the forwarded terminal is using the ttl usb adapter with minicom the second is via ssh connection both is showing "armbian-config"
  19. confidence got denied by looking into sources.. :-/ especially the android related stuff ( cause it seems to be the only repositories which are open around m4 v2... U-boot seems to be some 2014.x version (don't know it this is part of the normal rockchip u-boot package for an android build or just some random mess I don't understand - I assume it's a rockchip sourcedrop from the commit history - e.g. none except the few ones from friendlyelec added on top of it). Honestly I'm surprised (and not the good way). I guess (since rockpi images boot), we can base an u-boot defconfig based on rockpi. @mindee are the sources for more recent u-boot versions (newer than 2014 based one from the android 8.1 package) not available for the board yet? Did I do a mistake and not find it? Or is it not planed to release? For those running friendly core on it, can you provide a uart boot dump? I would be interested which version of u-boot they use for everything except the android they provide. Never the less I'm (still) confident that we can provide initial support to the board soon for a 4.4 legacy and recent mainline-ish kernel as well. I just didn't feel as comfortable to create those patches to the buildscript without having the hardware to test if it boots at least.
  20. o.k. that should be fine. Desktop is slow ... but 1-3s to move window, no. Can you make a video with your phone?
  21. Because its broken at the moment
  22. Hello Igor, thank you for the quick reply. I had to use vagrant to build an "encrypted root"-image. It didn't worked in docker or native build environment. Same to me, i never used it before , neither do i have any clue how this virtualization stuff works I'd love to help out with that. But i got two "but" 1. : I am not sure if my English is good enough for this task. 2. : It is not clear to me if the intended way to use the vagrant/virtualbox method was: a) to git clone everything into it and build entirely inside OR b) to use the build-system which got "mirrored" from the outside into the /vagrant folder. I suppose version a) is the right one. Could somebody point me to the right direction ? Greetings, Michael
  23. With "sudo armbian-config". There is an option to install full desktop.
  24. You used server image and installed XFCE on your own? How did you do that?
  25. This was lost between backup - doing something and restore. I did copy/paste the content under spoiler above which I notice it was added after. I lost one of mine ...
  26. if its only this one message then its "OK" for me... hoping that not all "my" messages will get lost in any time
  27. Since we are low on resources, we probably can't afford to provide LTS and rolling. But we can preset some numbers for the future and label LTS certain builds if there will be a dedicated support team for that. Just simply sync to either U-boot or Ubuntu ... 5.98 -> 19.10.1
  1. Load more activity