jeanrhum

Members
  • Content Count

    231
  • Joined

  • Last visited

1 Follower

About jeanrhum

  • Rank
    Elite member

Recent Profile Visitors

3116 profile views
  1. I think you misunderstand balbes. I think he was talking about u-boot for instance or any other low level software that can make things difficult when it does not fit the hardware. You can use the new images if you want to test, but there will be no support from him and no warranty that it'll work on your hardware. It is a bit sad, but when you look at the tv box market, amlogic boxes quality are worst and worst (many variants of the same reference with cheap chips and mainline support is mainly done slowly by Baylibre - only for the aml soc and not for all additional chips that may never
  2. You shouldn't you android recovery. Have you installed a custom firmware or any alternative system that may have modified the original u-boot? If so, just flash an original firmware and try again. If it doesn't boot directly try the toothpick method.
  3. Is it normal on your armbian storage, that the arm32 images are named Armbian_20.09_Arm-64_* ? Exactly like the arm64 ones.
  4. You have an error in your extlinux.conf: you should comment the rk3399 lines and uncomment 1 line of amlogic starting with fdt and the last one starting with append. Here is the one I use for s912 boxes (you may change the dtb if the generic q200 is not relevant): And you may also change the extlinux.conf-menu file:
  5. Even if Balbes makes a great work, I agree with Igor about updates and the use of a supported board. I'm not a good example since I use a S912 box with a Balbes image for my home server. But I can say that I stay on an "old" 4.19 or 4.20 since recent ones have several issues like GbE and usb even if some patches or hand modifications can be used to solve them. Rk3399 is powerful but heat a lot, so a good cooling is preferable if you plan to have heavy loads. Odroid c4 with amlogic S905x3 could be a nice alternative, since it is a supported board, you can add emmc and the
  6. I don't know if somebody make it work, but @@lex talked about that in another topic:
  7. Excelvan T2 (s912) using q201 dtb started from a slow usb key: http://ix.io/2qzp The system seems usable. It is slow but I think it comes from my usb key. EDIT: same test with an H96pro+ using vim2 dtb using a uhs1 sd card : http://ix.io/2qzv. The system is faster than my previous test and desktop is reactive. On both config video playback was smooth.
  8. Any improvements? If you can share a dts/dtb and current instructions, I will try to take time in the coming days to test on my board and panel.
  9. Maybe the best way to use HA is to use docker: https://www.home-assistant.io/docs/installation/docker/ I tested that on several tv boxes and it works nice and no more worry about python errors. Docker is available through armbian-config.
  10. This may come from the dtb you use. I don't know if any available dtb expose the tv tuner.
  11. The procedure has changed and the first post of this topic has been updated.
  12. I was thinking that I reported that on the Q8 topic, but no it didn't work with that change in the dtb. I will try to compare with firefly dtb and I will try to extract the dtb from an android image in case it has some relevant info to define a ut3s specific dtb, but I'm not sure to have enough skills with dts file reading.
  13. First test with ugoos ut3s with default dtb (firefly-reload): http://ix.io/2o7o For information, I have jock uboot and an old Q8 image installed on emmc. Wifi works, but ethernet seems buggy like on recent arm64 images (kernel 5.X pb with current dtbs ?). I didn't test it, but the connection was activated whereas no cable... System halts instead of reboot. Bluetooth seems not working well (xfce applet disappear when I try to use it to activate) With Q8 dtb the experience seems similar from a user perspective: http://ix.io/2o7q With popmetal and tinker dtb, the system d
  14. Downloading bullseye desktop legacy... I will try to give it a try this evening or tomorrow. I agree with Balbes about the position of his images and a CSC ugoos board. His images fit several boards at the same time and the behavior of these images (in particular for kernel update) is a bit different from official armbian.