All Activity

This stream auto-updates     

  1. Yesterday
  2. agreed, but wouldn't it reduce the time needed for the update procedure... unless you let it do that at 2 o'clock in the morning so one wouldn't get bothered by the down time.
  3. Hi. When I try to upgrade my amlogic S912 tvbox with ubuntu bionic 20.05.0 to 20.05.1, the .dtb my tvbox use is gxm-vim-khadas2 If I reboot the machine it gets stuck on amlogic boot screen, I've tried to change the .dtb for the one's in the image Armbian_20.05.1_Arm-64_bionic_current_5.6.2_20200408.img.xz but it hasn't work. I've burned the image Armbian_20.05.1_Arm-64_bionic_current_5.6.2_20200408.img on a sd card, I've changed the dtb on uEnv.txt but it hasn't boot it was stuck on amlogic boot screen. When i read the sd card the uEnv.txt was restored to original with no changes. I've restored with a backup and upgraded all packages except "linux-image-current-arm-64/bionic 20.05.1 arm64 [upgradable from: 20.05.0]" and it works. conf@arm-64:~$ sudo apt list --upgradable Listing... Done linux-image-current-arm-64/bionic 20.05.1 arm64 [upgradable from: 20.05.0] N: There are 2 additional versions. Please use the '-a' switch to see them. conf@arm-64:~$ sudo apt list -a --upgradable Listing... Done linux-image-current-arm-64/bionic 20.05.1 arm64 [upgradable from: 20.05.0] linux-image-current-arm-64/bionic,now 20.05.0 arm64 [installed,upgradable to: 20.05.1] linux-image-current-arm-64/bionic 19.11.5 arm64 Any idea?
  4. No, installing on bare metal wouldn't lower memory usage. Maybe 1 or 2MiB from the Docker overhead, but isn't worth the trouble of installing Mayan. I'd still recommend a container (Docker or podman). Mayan has high system requirements: https://docs.mayan-edms.com/parts/installation.html#minimum-hardware-requirements Considering this it simply doesn't make sense to install it on lower end ARM devices. It should have at least 1GiB of RAM, but that is the bare minimum. 2GiB is recommended, so a Raspberry Pi 3 would be the bare minimum for running Mayan EDMS. But a Pi 4 or Odroid C2 with 2GB would be a better choice.
  5. Good to know. This raises the question of turning away from the Docker image and install it natively - in order the reach a bigger audience. And if this install fails anyway, is there a way to track/record the actions of this install to remove it completely - it consists of Ngnix, Python, Redis and Postgres... thinking out loud. I guess there are some ways to: linux track an install; but just for apt or here. And for Python I only found this. Could the script executing the install running a pipe command to keep the output in a log file, so it would be possible to reverse the install? Does this make sense? Edit: I needs quite a bit: https://docs.mayan-edms.com/chapters/deploying.html
  6. All the images in the first page have been updated with the following news: Single image for all boxes! Configure your box with sudo rk322x-config once the system has booted Support for Realtek 8188eu, 8189es/etv, 88x2bu and various other wifi chips General better stability eMMC in DDR mode for some boards Enjoy!
  7. Considering the complexity and all the dependencies I doubt it. The buildfile for Mayan EDMS uses Debian Slim and removes a lot of packages during the build in order to keep the resulting image as small as possible. It theoretically would be possible to to switch to Alpine, but considering all dependencies for Mayan I don't think it's worth the trouble. For every new version of Mayan a new image should be build. So that would mean an hour of time from a C2 or RPi3. For anything lower end I wouldn't even consider Mayan EDMS, it's way to heavy. Right now I'm trying to figure out if I can extend the script in order to automatically get the latest version number from here: https://docs.mayan-edms.com/releases/index.html or here: https://pypi.org/project/mayan-edms/ If I'm able to do that, then this script will be able to automatically build the latest version and use it to create the container. I've never installed Mayan using Softy, so I don't know if the user can change the Environmental Variables before the script actually starts.
  8. Two new boards have been tested. This one did not work for me, partially because I did not understand what it is supposed to do... It's written in Chinese, and I have not been able to get 5V out of it... yet, only 4.2V. This second one worked for me despite my very crude soldering job and the salvaged 18650. So, after a few dozens of minutes charging the battery, I just unplugged the power on the charging board, and did not get any error on the OrangePi Zero... Now, I would like to get some information on the voltage and other relevant information on the board to see if that's working properly, or if it's just luck... And... I have to plug the 3.3V step down converter to one GPIO pin (linked to the main power), and see what's going on.
  9. You will need to contact driver author(s) or do some tricks like setting the fixed CPU frequency. Can be done via armbian-config as well. Try lower and higher values.
  10. Mali drivers are part of the kernel for more than a year now. How you will use them, its up to you.
  11. Hi everyone, I updated the Linux kernel on my Espressobin to the latest version (5.6.2) and had some issues booting from SATA as my SSD was not detected properly after boot. Using the device tree from an older kernel version did help, but I also read somewhere that updating to the latest Armbian U-Boot would solve the issue. So I downloaded the version that matches my hardware (flash-image-ddr3-2g-2cs-1000_800.bin) and flashed it. It indeed fixed the boot issues, but now only 1 GB of RAM is detected instead of 2 GB. This happens as soon as the board is powered on, in U-Boot: DRAM: 1 GiB Before that, I was using the U-Boot version from espressobin.net, and the 2 GB were detected and usable. I'm sure of it, because before downloading the Armbian U-Boot I checked the output to make sure that I indeed had the 2 GB version. I cannot do a downgrade to verify this right now, because the espressobin.net website is broken; most pages report a 404 error, including the one where the U-Boot files were located. I tried different versions, like the slower flash-image-ddr3-2g-2cs-800_800.bin or the version in the https://dl.armbian.com/espressobin/u-boot/archive/10/ folder, with similar results. I also tried the 1200 MHz version out of curiosity, and had to recover the SPI flash using the SATA rescue image. In any case, I would prefer to continue using the Armbian U-Boot version, since it is more up to date and works with the current mainline kernel and device tree. I did not find any answer for this in the forums or using Google. I actually find it very odd that it works at all. What is then used? Only one RAM chip? Or 512 MB from each? Did I install the wrong image, or did I miss a step when migrating U-Boot?
  12. any new solution? And what about this manual? https://wiki.debian.org/MaliGraphics Im newbie in Linux, stuck in step with headers download.
  13. Right... is wrong but i don't have ntp installed so cannot change.. theres another way? found date -s "09 APR 2020 21:36"
  14. @Mathias - Did you find a solution to the problem? Thanks.
  15. Hi SteeMan My minix has that age, i tried to use the new packages but i have to use the img that works for my kernel (3.10) Just looking for a method to make the SD system works on my emmc Thanks
  16. I replaced all of my orange pi zeros with them as camera servers - combined with esp32s to serve as remote monitors. The one shown in previous message is a spare one to use as tool chain builder, also can be used standalone.
  17. On a long run, software installation should anyway be switched to docker based installation. And drop everything else. But again, if I am alone doing that, I will not even start.
  18. Its enough to convince me the problem is real, but the main problem remains - I have no time to deal with this in a near future.
  19. can you elaborate a bit more what you are doing and would like to solve (apart from RAM usage)?
  20. the picture is great. What do you do with it? Enrich your story a little please?
  21. The build you are using would be a build from balbes150's fork. As you can see from the build date, that build is over a year old and on a kernel version (3.10) that is almost 7 years old. If you value security you really shouldn't be using such an old build. balbes150's work is now focused on current mainline kernels (5.4 or higher). Since the build you are using predates my involvement in these forums, I have no idea if installation to internal storage is possible with what you are using.
  22. Thank you very much I have to admit I am a total noob if it comes to Docker. Are there some tools to improve building such an image or tweaks to bring down building time (reuse some parts the next time) ? @Igor, Master of bash-scripts What is your thought about it?
  23. I know you are our specialist on Pi-Hole, and I am grateful for that. However, the OP had very specific questions/requests like I did the same just recently (Spam). Then every other post is simply spam that doesn't answer the question. So, he wasn't wasting your time he just wanted to know how to get his install back to the state it was before and really get rid of everything. To me, fair enough, because even Linux leaves back some traces (not only Windows) - as I had to learn it the hard-way myself.
  24. Here is what I did with one of mine - added $7.5 neo core as standalone terminal with back to back ethernet and serial connections :-)
  1. Load more activity