jeanrhum

Members
  • Content Count

    225
  • Joined

  • Last visited

About jeanrhum

  • Rank
    Elite member

Recent Profile Visitors

2781 profile views
  1. 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.
  2. 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.
  3. 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.
  4. This may come from the dtb you use. I don't know if any available dtb expose the tv tuner.
  5. The procedure has changed and the first post of this topic has been updated.
  6. 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.
  7. 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 does not boot: waiting root file system... running /scripts/local-block With miqi dtb, it boots, but without wifi and I was not able to connect a cable to test the wired network, but eth0 still shows as connected. Edit: As I noticed on Jock images, the Q8 dtb is not able to detect emmc on contrary to firefly-reload.
  8. 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.
  9. This not directly related to armbian. You can have a look it for instance: https://wiki.debian.org/DesktopEnvironment
  10. No, since it's not arm64. Look at this topic:
  11. I have an ut3s, so if you want a tester for a similar ugoos box, don't hesitate. Have you tried/compared the community image from jock for Q8? It work not too bad on ut3s, but it lacks some dtb tweeks (fan, led and emmc in latest kernel).
  12. Thanks and success too! I just built a focal standard server image under a recent focal install on emmc with the following modifications: - copy /lib64 folder from usb stick to emmc install - install qemu and change line 80 in config/sources/families/arm-64.conf to use qemu-x86_64-static instead of qemu-x86_64 It finished in 263 minutes, but my h96proplus throttle a lot at 80°C. The eight cores were used but the big ones limited to 1ghz and the small ones to 500mhz. I will try to find a simple way to better cool the box compared to the small default heatsink and run it again.
  13. Can you explain the few modifications you've done to compile successfully an image please? I face the same error using the latest focal image on an s912 box. First, I had an error with qemu so that I installed it and then modify the file config/sources/families/arm-64.conf because the qemu binary was qemu-x86_64 instead of qemu-x86_64-static (line 80). /full-path/config/sources/families/arm-64.conf: line 101: qemu-x86_64: command not found /full-path/config/sources/families/arm-64.conf: line 121: qemu-x86_64: command not found After those modifications, I got the same error as you. Where do you get the ld-linux-x86-64.so.2 file?
  14. Hi, I can confirm that dev images with kernel 5.6 does not have dsi support (tested on pine64+ ks). I will put as soon as possible the decompiled dts and the dmesg output. I think that the best way to add it is as a dtb overlay, but I'm not very familiar with that.