manuti

  • Content Count

    349
  • Joined

  • Last visited

Everything posted by manuti

  1. After mounting and unmounting several times both external units it seems to start working. Now the mount point at /sda is consistent across all the commands. The outpus you asked, @lanefu, is: ls -l /dev/disk/by-uuid total 0 lrwxrwxrwx 1 root root 15 may 11 22:57 d4e4d15d-d587-4f5d-83d7-4cbb1700e7c5 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 9 may 11 22:57 dcb5a19c-6bd2-4c5a-8fc4-9ed4adec7074 -> ../../sdb lrwxrwxrwx 1 root root 9 may 11 22:57 e6201983-bfd8-4eae-bf54-90575f09835f -> ../../sda I also added a new screenshot. Thanks for the help. And I'll keep an eye on th
  2. I used UUIDs to mount via fstab. You can see it in the snapshot and I suppose this info is also included in armbian-monitor dump included.
  3. The info from "df" show /dev/sda but "lsblk" show a /dev/sdc unmounted unit. The unit is reachable at /media/sata and is added in fstab using the UUID. What's happening? Thanks in advance.
  4. Another try usinf de DTS edit function inside 'armbian-config' same result: Ideas?
  5. OK, following with info found in the forum. Using info from this post above to create my own dtb file: and using info from this other post above, to change from 256MB (0x10000000) to 32MB (0x2000000) After create the new dtb I changed the path in uEnv.txt to point to new one. After reboot everythig looks the same. This is the output from armbianmonitor -U: Any idea about how I'm doing wrong?
  6. (Please moderator feel free to move this topic whatever you think that Hi, I'm running Rosetta@home in a TV box, MXQ4K with Amlogic 905x is a 2GB RAM unit. When I start boinc, sometime I have tasks and other times I have this message? boinc-client 25-Mar-2021 11:22:31 [Rosetta@home] Rosetta needs 1716.61 MB RAM but only 1654.12 MB is available for use. Is there anyway to shave 64GB of RAM? Is correct to have 1,7GB in a 2GB unit? Is this RAM dedicated to the GPU? In this case. How I can reduce the amount of dedicated RAM? I paste the armbianmonit
  7. I don't understand your question. But you can change the kernel using `armbian-config` tool and after that change repos from Bionic to Focal. With something like this (CAVEATS THAT IS NOT TESTED BY ME) : cp /etc/apt/sources.list /etc/apt/sources.list.backup sed -i 's|bionic|focal|g' /etc/apt/sources.list apt update && apt -y upgrade && apt -y dist-upgrade
  8. I updated from Debian Strech to Buster following the instruction from this post, also in a Banana Pi. I suppose you can move from 18.04 to 20.04 with caveats in the way. I perform an image backup from the microSD before doing anything.
  9. @SlackstickMaybe this old post from Linuxium can give you an idea about how proceed: http://www.linuxium.com.au/how-tos/gaoptions
  10. I don't know what Android firmware my Sunvell R69 have. I use directly the GNU/Linux Armbian shared in this forum. But if you want an Android version suitable for your box the best option is go to https://h3droid.com/
  11. No problem @balbes150 I'm not in a hurry. Is something nice to have and I don't have enough knowledge to do by myself. But if you deliver something I'll test as soon as possible. Thanks a million.
  12. And having RK3066 support is possible? I still use an old board with smelly 3.0 kernel? Thanks a million for all the work you do.
  13. Hey, @DevShanky if you are interested in a historic progression of sales you can check this Google Sheet. (I'm not the creator nor owner). https://docs.google.com/spreadsheets/d/1zWwpcckDEEVAhNH3y7JQGxxbjP42nUywPOzDWr1fH28/edit?usp=sharing
  14. Wi-Fi issues again My Rock Pi S show me two Wi-Fi devices but the board only have one, the built-in interface. Also the wireless connection is unpredictable sometimes shows SSH port sometimes not, sometimes I can find using the Avahi daemon sometimes not... I uploaded the testing from armbian-config tool http://ix.io/2O1s I also added an image from "nmtui" Any ideas?
  15. Or maybe you can try this update image shared in this thread : I tested the image and worked.
  16. Hi @rna I try different microSD card vendors and finally found that someone can boot directly and others can't. If you can, try different microSD models. Finally after confirm everything is working I decided to install armbian to internal eMMC memory.
  17. Thanks @vlna tomorrow I give a try. And share my thoughts.
  18. Sorry @Virverus I see your AndroidTV stick and since I have a similar device I asked you if you did some tests with another device. Anyway I tried my device with RK3066 and it didn't work. I know it was crazy, but I didn't lose much by trying. Thanks.
  19. @Virverus Any chance of having this image running in a Ugoos UG2 with RK3066 ?
  20. Is it v 20.05.2 ? Yes. Re-download and tested. Results uploaded. Also no Wi-Fi.
  21. Downloaded and tested, but Focal 5.6 never boot. Etcher burned OK. Same microSD, same board, same power source, same Ethernet cable than Debian Buster. I'm going to download again to double check.
  22. Yes, but no Wi-Fi. I pass the test from: https://github.com/armbian/testings/ Any additional information?
  23. I can't help with 256MB issues I only have a 512MB unit. I see the banner so I downloaded the Debian Server image.
  24. Good news!!! Rock Pi S is now officially supported (I see today but I don't when started) And also with kernel 5.6 https://www.armbian.com/rockpi-s/#kernels-archive-all
  25. Thanks @balbes150 with your hard work to prepare the images is enough for me. So no "original firmware" no way. If anyone have the "manual recipe" to install latest image on Amlogic board in the manual way I will glad to test the recipe. Thanks again.