MX10.AC2N

  • Posts

    60
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

MX10.AC2N's Achievements

  1. Thank you @jock I have indeed noticed that when the red led turns on it turns off the blue led. On the front of my box I only have 2 LEDs so 4 LEDs, yes if I count the 2 LEDs which are with the RJ45 connector (green and orange) otherwise I do not understand .. Otherwise when I start on my emmc where I still have the armbian-station M1 image using https://paste.yunohost.org/odozesogaz.hs I can independently control each led, the basic dtb file used was rk3328-box.dtb I just invert the values of the leds for a good operation with my box, and I renamed it to rk3328-mx10.dtb I made this modification via armbian-config i am attaching a copy of this dtb. thanks again rk3328-mx10.dtb
  2. Hi @jock I come back a bit on the led-conf3 that you provided me and which seemed to be correct however: - There are physically on the front of my box 2 LEDs (1 red and 1 blue) - when I run " sudo du -a /sys | grep led | grep trigger " /sys/kernel/tracing/events/libata/ata_qc_complete_failed/trigger 0 /sys/kernel/tracing/events/dma_fence/dma_fence_signaled/trigger 0 /sys/kernel/tracing/events/kyber/kyber_throttled/trigger 0 /sys/kernel/tracing/events/btrfs/btrfs_failed_cluster_setup/trigger 0 /sys/kernel/tracing/events/ext4/ext4_journalled_write_end/trigger 0 /sys/kernel/tracing/events/ext4/ext4_journalled_invalidatepage/trigger 0 /sys/kernel/tracing/events/xdp/mem_return_failed/trigger 0 /sys/kernel/debug/tracing/events/libata/ata_qc_complete_failed/trigger 0 /sys/kernel/debug/tracing/events/dma_fence/dma_fence_signaled/trigger 0 /sys/kernel/debug/tracing/events/kyber/kyber_throttled/trigger 0 /sys/kernel/debug/tracing/events/btrfs/btrfs_failed_cluster_setup/trigger 0 /sys/kernel/debug/tracing/events/ext4/ext4_journalled_write_end/trigger 0 /sys/kernel/debug/tracing/events/ext4/ext4_journalled_invalidatepage/trigger 0 /sys/kernel/debug/tracing/events/xdp/mem_return_failed/trigger 0 /sys/devices/platform/gpio-leds/leds/ir/trigger 0 /sys/devices/platform/gpio-leds/leds/working/trigger 0 /sys/devices/platform/gpio-leds/leds/net/trigger 0 /sys/firmware/devicetree/base/gpio-leds/ir/linux,default-trigger 0 /sys/firmware/devicetree/base/gpio-leds/working/linux,default-trigger 0 /sys/firmware/devicetree/base/gpio-leds/net/linux,default-trigger I therefore tried to modify the trigger on > /sys/devices/platform/gpio-leds/leds/ Where can we find 3 leds? Either .. So I make some modifications on the 3 leds detected by the system and I find the red front led of my box (under the "net" value) I modify the value of the trigger on heartbeat and Hop the red led of my box starts flashing (cool ..!) Unfortunately, it is impossible to modify the light state of the blue led which lights up when the box starts up, I have unsuccessfully modified the values of the triggers of the "ir" and "working" leds but nothing changes, currently the triggers in questions are on "none" and yet I still have the blue led on .. Is there anything else to do? Thanks in advance..
  3. Hi all, Little feedback, I tried installing CasaOs, CasaOS - A simple, easy-to-use, elegant open-source Family Cloud system it works.. It may be useful for some of you. Thank you to the entire IceWhale team for this sharing.. https://github.com/IceWhaleTech/CasaOS
  4. You can try YUNoHost, it's cool I use it on my beelink gt-king pro with armbian-meson64 works fine and have many apps. Today I try install of Swizzin, on my RK3328 box that's work ( install process need root user "su -" ) it's another possibility.. https://github.com/swizzin/swizzin https://swizzin.ltd/getting-started/
  5. Thank @jock, I try upgrade with .deb from https://users.armbian.com/jock/rk3318/upgrade/ ju@rk3328-MX10-TvBox:~/Deb$ cd @jock-rk3318 ju@rk3328-MX10-TvBox:~/Deb/@jock-rk3318$ wget https://users.armbian.com/jock/rk3318/upgrade/linux-dtb-edge-rockchip64_21.11.0-trunk_arm64.deb --2021-11-13 07:26:53-- https://users.armbian.com/jock/rk3318/upgrade/linux-dtb-edge-rockchip64_21.11.0-trunk_arm64.deb Résolution de users.armbian.com (users.armbian.com)… 93.103.15.56 Connexion à users.armbian.com (users.armbian.com)|93.103.15.56|:443… connecté. requête HTTP transmise, en attente de la réponse… 200 OK Taille : 363952 (355K) [application/octet-stream] Sauvegarde en : « linux-dtb-edge-rockchip64_21.11.0-trunk_arm64.deb » linux-dtb-edge-rock 100%[===================>] 355,42K 326KB/s ds 1,1s 2021-11-13 07:26:54 (326 KB/s) — « linux-dtb-edge-rockchip64_21.11.0-trunk_arm64.deb » sauvegardé [363952/363952] ju@rk3328-MX10-TvBox:~/Deb/@jock-rk3318$ wget https://users.armbian.com/jock/rk3318/upgrade/linux-headers-edge-rockchip64_21.11.0-trunk_arm64.deb --2021-11-13 07:27:22-- https://users.armbian.com/jock/rk3318/upgrade/linux-headers-edge-rockchip64_21.11.0-trunk_arm64.deb Résolution de users.armbian.com (users.armbian.com)… 93.103.15.56 Connexion à users.armbian.com (users.armbian.com)|93.103.15.56|:443… connecté. requête HTTP transmise, en attente de la réponse… 200 OK Taille : 12018228 (11M) [application/octet-stream] Sauvegarde en : « linux-headers-edge-rockchip64_21.11.0-trunk_arm64.deb » linux-headers-edge- 100%[===================>] 11,46M 2,85MB/s ds 6,3s 2021-11-13 07:27:29 (1,81 MB/s) — « linux-headers-edge-rockchip64_21.11.0-trunk_arm64.deb » sauvegardé [12018228/12018228] ju@rk3328-MX10-TvBox:~/Deb/@jock-rk3318$ wget https://users.armbian.com/jock/rk3318/upgrade/linux-image-edge-rockchip64_21.11.0-trunk_arm64.deb --2021-11-13 07:27:39-- https://users.armbian.com/jock/rk3318/upgrade/linux-image-edge-rockchip64_21.11.0-trunk_arm64.deb Résolution de users.armbian.com (users.armbian.com)… 93.103.15.56 Connexion à users.armbian.com (users.armbian.com)|93.103.15.56|:443… connecté. requête HTTP transmise, en attente de la réponse… 200 OK Taille : 50780648 (48M) [application/octet-stream] Sauvegarde en : « linux-image-edge-rockchip64_21.11.0-trunk_arm64.deb » linux-image-edge-ro 100%[===================>] 48,43M 2,78MB/s ds 19s 2021-11-13 07:27:59 (2,49 MB/s) — « linux-image-edge-rockchip64_21.11.0-trunk_arm64.deb » sauvegardé [50780648/50780648] ju@rk3328-MX10-TvBox:~/Deb/@jock-rk3318$ sudo dpkg -i *.deb [sudo] Mot de passe de ju : (Lecture de la base de données... 139206 fichiers et répertoires déjà installés.) Préparation du dépaquetage de linux-dtb-edge-rockchip64_21.11.0-trunk_arm64.deb ... Dépaquetage de linux-dtb-edge-rockchip64 (21.11.0-trunk) sur (21.11.0-trunk) ... dpkg: avertissement: impossible de supprimer l'ancien répertoire « /boot/dtb-5.14.13-rockchip64/rockchip/overlay » : Le dossier n'est pas vide dpkg: avertissement: impossible de supprimer l'ancien répertoire « /boot/dtb-5.14.13-rockchip64/rockchip » : Le dossier n'est pas vide dpkg: avertissement: impossible de supprimer l'ancien répertoire « /boot/dtb-5.14.13-rockchip64 » : Le dossier n'est pas vide Sélection du paquet linux-headers-edge-rockchip64 précédemment désélectionné. Préparation du dépaquetage de linux-headers-edge-rockchip64_21.11.0-trunk_arm64.deb ... Dépaquetage de linux-headers-edge-rockchip64 (21.11.0-trunk) ... Préparation du dépaquetage de linux-image-edge-rockchip64_21.11.0-trunk_arm64.deb ... ls: impossible d'accéder à '/var/lib/initramfs-tools': Aucun fichier ou dossier de ce type Dépaquetage de linux-image-edge-rockchip64 (21.11.0-trunk) sur (21.11.0-trunk) ... Paramétrage de linux-dtb-edge-rockchip64 (21.11.0-trunk) ... dpkg: des problèmes de dépendances empêchent la configuration de linux-headers-edge-rockchip64 : linux-headers-edge-rockchip64 dépend de bison ; cependant : Le paquet bison n'est pas installé. linux-headers-edge-rockchip64 dépend de flex ; cependant : Le paquet flex n'est pas installé. dpkg: erreur de traitement du paquet linux-headers-edge-rockchip64 (--install) : problèmes de dépendances - laissé non configuré Paramétrage de linux-image-edge-rockchip64 (21.11.0-trunk) ... update-initramfs: Generating /boot/initrd.img-5.15.2-rockchip64 update-initramfs: Converting to u-boot format Des erreurs ont été rencontrées pendant l'exécution : linux-headers-edge-rockchip64 ju@rk3328-MX10-TvBox:~/Deb/@jock-rk3318$
  6. Hi, You can try => https://github.com/pdewacht/brlaser
  7. Hi @jock and thank you for these explanations it enlightens my knowledge a little more, suddenly I left the emmc as it is and tried adding overlays, it works I was able to put led-conf3 and cpu-hs without problem here is the copy of dmesg => https://paste.yunohost.org/ewutojutal.md However I come back to your explanations, you indicate that ATF would be useful for DRM rights, suddenly this attracts my interest because I am looking for a solution to be able to read the amazon prime videos and unfortunately I still have this damn message missing drm rights .. do you know a parade with this problem? I looked a lot on Github, I even tried a few installs but nothing convincing, often the problem is that we are under arm64 (no drm rights under arm64) because with armhf apparently there will be solutions .. Y -will there be a way to build a multiarch arm64 / armhf image or maybe just an armhf image ..? For the moment I am in the idea of using a docker like https://github.com/HenningThiemann/docker-chromium-armhf .. Thanks again, apparently the problems seem to be solved, I will go back to 1.3GHz.
  8. Thank again @jock So on the emmc I still have the armbian bulleyes system from the station-m1 image So I replaced the rk3318-box.dtb file (yours is slightly heavier 63761 bytes against 62913 for the dtb already present in the image) here is the new dmesg => https://paste.yunohost.org/alatoyakud.md
  9. copy of dmesg without rk3318-box-cpu-hs and rk3318-box-led-conf3 => https://paste.yunohost.org/ogasoqumeq.vbs
  10. At moment, I have system just on sd-card.. I switched to verbosity = 10 but then it scrolls too fast on the screen, suddenly I tried to film it and bring out some photos but hey it's not super easy .. It gives a lot of image very blurry finally I did the best, at the end I only have 5 lines with the rest of the black screen .. Hope that can help you ..
  11. Thank you again for your responsiveness ... Well I have just tested with the file you just gave me, indeed it was slightly lighter than the one available in the base image (7912 bytes against 8052) .. So I believed in it but the result is the same, the startup freezes at the same time (as in the photo ..), sorry for the bad news .. edit : Do you think that I should install full firmware via armbian-config or I can stay in mini?
  12. Hi all, So I started from scratch, everything works fine without any overlays but this morning I tried adding overlays=rk3318-box-led-conf3 in armbianEnv.txt and the box freezes at startup
  13. Well, I just tried by rewriting the armbianEnv.txt file as you indicated to me, but I found myself faced with a start that keeps running in a loop. Wild electric disconnection, I don't like that .. Anyway I'm starting from scratch, can you explain to me what rk3318-box-emmc-ddr rk3318-box-emmc-hs200 is for because I did not use them before.. Thank
  14. Hi all, As the update with the .deb files did not work for me I re-flash my sd card with the new bullseye image The first start went correctly, I created the user and put in French, then I launched rk3318-config and I launched a reboot and there big bug as you can see on the photo => https://imgur.com/a/FlqEBST So I connected my sd card on my pc in order to modify armbianEnv.txt and remove the overlays lines but this is what I have in armbianEnv.txt /var/log.hdd/alternatives.log { monthly rotate 12 compress delaycompress missingok notifempty create 644 root root } I don't understand anything anymore, is it repairable or I have to start over and especially not to forget to do apt update && apt upgrade before doing rk3318-config .. @jock what do you think of all this?
  15. No worries, I'm only in the testing phase so nothing important .. Too bad it didn't work .. Hoping that my feedback can help, Thank you again for everything you do .. Great @jock