13 13

About This Club

Running Armbian on all kinds of ARM based TV boxes. Select a topic clicking on a tab above. If you are new to Armbian for TV boxes you should start by reading the FAQ entry "Status of Armbian on TV boxes - Please read first": https://forum.armbian.com/topic/16976-status-of-armbian-on-tv-boxes-please-read-first
  1. What's new in this club
  2. Until are kernel related problems Is ok discuss here. Or you can discuss elsewhere, test and then make requests here about missing features in kernel
  3. @fedex My test script is showing the same and i can installing portainer and / or docker agent and its working OK. What is HA complaining then you is trying installing it ? Also the CPU is 32 bits so need using installing the "armv7l" version by selecting "raspberrypi2" or its failing. @jock I think we shall not hijacking the thread with no Armbian things and you must saying if we shall stop spamming it with HA problems.
  4. @Jack853 @MR01 Multitool will expand the FAT partition automatically to the size of the medium once it has been run for the first time on the box. Also you can put compressed images on sdcard and multitool will expand them on the fly during restore/burn process. Note also that, due to FAT partition limitations, a file cannot be larger than 4GB
  5. When i had the same problem i just expanded the partition with gparted.
  6. Hi, this is my first post so please be generous. After much experimentation I have managed to to set up Armbian on an old Zidoo x5 box. I may add that neither the .zip or the toothpick method worked for me but finally got the booting sequence to run the S905 Autoscript by altering some variables using the setenv command through the serial interface. I have installed several OS's and finally settled on the 20.10 focal 5.9.0 desktop image. Most things work but I am getting problems with setting up an Access Point through the armbian-config program. I have left the default settings as proposed and was able to "see" the hot spot from my mobile but the system repeatedly refused to acknowledge the password "12345678". Since this hot spot transmits on channel 5 and there is another strong wifi on this channel close by I tried to change the channel number to 4 after which wifi stopped transmitting altogether. Also the option to generate a HotSpot in Armbian-config disappeared altogether. The same thing more or less happened with other OS's I tried. Is there anything I can do? Regards
  7. I am having a bit of trouble with the backup on the multitool software. Can anyone help me? Basically so I have a backup saved on my computer and when I use rufus to put the multitool on an sd card it makes the size of the card 2gb even though its a 8gb one. Then when I try to put the backup in the backup folder I cant because the backup file is too big. I will attach some images to further show my issue: https://ibb.co/NTPRxYp https://ibb.co/m9G29kY https://ibb.co/cYMDKDX https://ibb.co/kDm7RXb
  8. Hi, thanks for suggestion, I have tried this image: Armbian_21.11.0-trunk_Rk3188_hirsute_current_5.10.63.img Does not boot... no hdmi, no led...if I remove SD card, Wasser Android starts/boots OK! I even connected external USB LAN and waited ~15 min... Partitions on Minix NAND: ./upgrade_tool PL Program Data in /root/.config/upgrade_tool Partition Info(parameter): NO LBA Size Name 01 0x00002000 0x00002000 misc 02 0x00004000 0x00008000 kernel 03 0x0000c000 0x00008000 boot 04 0x00014000 0x0000c000 recovery 05 0x00020000 0x00100000 backup 06 0x00120000 0x00040000 cache 07 0x00160000 0x00400000 userdata 08 0x00560000 0x00002000 kpanic 09 0x00562000 0x00100000 system 10 0x00662000 0xffffffff user UpgradeFirmware: ./upgrade_tool UF ./wasser-3.0.6-minix-x7-rk3188/wasser-3.0.6-minix-x7-rk3188.img Program Data in /root/.config/upgrade_tool Loading firmware... Support Type:RK31 FW Ver:5.1.01 FW Time:2017-02-12 13:15:23 Loader ver:2.19 Loader Time:2014-10-29 17:47:37 Upgrade firmware ok. MicroSD: # fdisk -l /dev/sdb Disk /dev/sdb: 29.72 GiB, 31914983424 bytes, 62333952 sectors Disk model: Storage Device Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x698ab215 Device Boot Start End Sectors Size Id Type /dev/sdb1 32768 2531327 2498560 1.2G 83 Linux boot dir list on SDCard; FS ext4 # ll total 27312 -rw-r--r-- 1 root root 1536 Sep 8 2021 armbian_first_run.txt -rw-r--r-- 1 root root 38518 Sep 8 2021 boot.bmp -rw-r--r-- 1 root root 155492 Sep 8 2021 config-5.10.63-rk3188 drwxr-xr-x 2 root root 4096 Sep 8 2021 dtb drwxrwxr-x 2 root root 4096 Sep 8 2021 extlinux -rw-r--r-- 1 root root 8864809 Sep 8 2021 initrd.img-5.10.63-rk3188 -rw-r--r-- 1 root root 3209432 Sep 8 2021 System.map-5.10.63-rk3188 lrwxrwxrwx 1 root root 22 Sep 8 2021 uInitrd -> uInitrd-5.10.63-rk3188 -rw-r--r-- 1 root root 8864873 Sep 8 2021 uInitrd-5.10.63-rk3188 -rwxr-xr-x 1 root root 6810096 Sep 8 2021 vmlinuz-5.10.63-rk3188 lrwxrwxrwx 1 root root 22 Sep 8 2021 zImage -> vmlinuz-5.10.63-rk3188 # cat ./extlinux/extlinux.conf LABEL Armbian LINUX /boot/zImage INITRD /boot/uInitrd FDT /boot/dtb/rk3188-ugoos-ut2.dtb APPEND root=UUID=93ab2d09-92a4-4aec-bc9f-1247a2b6b211 console=uart8250,mmio32,0x20064000 console=tty0 coherent_pool=2M video=HDMI-A-1:e rootflags=data=writeback rw no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0 bootsplash.bootfile=bootsplash.armbian maybe I need to flash another boot file ? from Firmware: X7-rk3188-250.7z ? or another Loader ?
  9. Worth noting that I couldn't get anything but one USB and HDMI running but that let me put in usb hub with gbit lan to it and hook it to network that way, also tested usb ac wifi dongle and that also worked but it's more pain to manage. With physical wire you can just remote SSH always as long as you've done the initial armbian setup.
  10. @rzuI'm still testing, for me it was a significant advance one of the images booted. I will test them all and come back with details in a few days. Thank you so much!
  11. I can't help answer this question directly as I haven't encountered this module before, nor the problem of one being discovered but not connecting. That said, there are many different part numbers for what is essentially the same module. As a general rule of thumb, look at the last two digits and compare to the Broadcom part numbers. In this case, it would likely be a brcm4334 as discovered. If it ends in 30, it would likely be a brcm4330. Of course, that doesn't explain why it doesn't connect. I'll defer to @jock or others that have more experience with these things...
  12. I had a problem with this wireless chip. Is this familiar to anyone? In one of the system messages I saw this as BCM 4334B1 / 6334. It can scan networks with the minimal image but cannot connect. Is there an overlay?
  13. Hello friend, I found this topic, I saw your comment, I don't remember if I found the ISO you mentioned and I tested it. Thank you so much for replying to my thread and posting the links. I will test these images you mentioned here. Let's see if it works on mine.
  14. @MattWestB This modules is missing: Optional Features: - CONFIG_CGROUP_HUGETLB: missing - CONFIG_SECURITY_SELINUX: missing - CONFIG_SECURITY_APPARMOR: missing - CONFIG_EXT3_FS_XATTR: missing - Storage Drivers: - "aufs": - CONFIG_AUFS_FS: missing - "zfs": - /dev/zfs: missing - zfs command: missing - zpool command: missing
  15. @fedex Try running the check script and see if you have al installed and working for docker. https://docs.docker.com/engine/install/linux-postinstall/#kernel-compatibility What is not working with the install of HA ? Complaining on brub or somthing else ?
  16. @MattWestB I did as you say but it doesn't work. I have installed HA on debian bullseye minimal.
  17. @fedex Install HA as raspberry pi 2 (= 32 bits) and its not working. Then do this: And puls audio is using 200% CPU so set CPU usage to minimum for the HA container and its only using 25% CPU. Need do the CPU patching after every restart of docker / the system. Its one addon that fixing the sound problem but its not working in me new Armbian (perhaps its the missing appamor that is doing it).
  18. @jock Thanks very much, now docker works. I was unable to get HA to work. 😠
  19. The 4.9.x kernels are 'legacy' kernels in armbian speak. That means they are the kernels supplied by the board vendor. Vendor kernels are generally heavily modified and the changes don't get put into the mainline kernels. Because of the heavy modifications these vendor kernels are always very old kernels and therefore not receiving any support/bugfixes/patches. Armbian focuses on support of mainline kernels and the mainline kernel tree and tries to minimize any out of tree kernel patches (when there are patches necessary, it is the goal that these changes will ultimately be accepted into the mainline tree). Because the vendor kernel and mainline are so far apart, it often isn't realistic to merge the vendor changes into mainline, but instead the work needs to be redone. Since the vendors generally don't put any effort into mainlining all that falls upon the community which can take a long time.
  20. @Munez I posted my findings earlier here: basically what I found on my end was that most of the kernels of these Orange Pi Zero 2 ROMs didn't seem to do anything on H616 boxes I got access to but somehow the ones specifically with 4.9.279 and 4.9.280 kernels booted and gave one USB and HDMI out on one of these boxes and other clearly did some additional loading too but with no HDMI out. None of the other ROMs showed any activity on boot but granted I haven't hooked up serial connection for further analysis. For example 4.9.255 was just dead on my end. I've used ROMs from this archive for testing: https://armbian.hosthatch.com/archive/orangepizero2/archive/ This works on the H96max (H616) box here: https://armbian.hosthatch.com/archive/orangepizero2/archive/Armbian_21.08.1_Orangepizero2_bullseye_legacy_4.9.280.img.xz Would be nice to hear others experiences on this, if 279 and 280 work for others too there must be some reason why only these are more compatible with H616 TV boxes.
  21. I have a new problem with the SSH. After setting it up and rebooted, it didn't accept my login credentials, even in root and username, still the same "Access denied" 😔
  22. Hi there, very interesting test. I succesfully run latest LibreELEC "box" nightly builds (Kodi-20) in my YokaTV KB2 - S912-based - by using "meson-gxm-q200.dtb" so I believe that "should support most hardware" (as chewitt suggested here). I'll try ARMbian soon...
  23. Has anybody figured out how to make the USB3 port work as USB3 in the V96mini with a H6 ? I've WIFI, LAN, USB2.0 working and now wanted to connect an USB3 camera to the USB 3 port however it does not initialize when connected there. It works well on USB2 port but at limited resolution. USB2 devices also work on the USB3 port. Just not USB3 on USB3. I'm using the sun50i-h6-tanix-tx6_v96mini6k_01.dtb by Ultradrom and tried on Armbian 21.05.0-trunk Focal with Linux 5.10.27-aw-h6-tv and Armbian 22.05.0-trunk with Linux 5.15.27-station.
  24. Hello Ultradom, please, do you have an update to your DTB or a direction that I could take to make the USB3 a USB3 not just USB 2.0 ? I noticed that the Logitech Brio webcam won't work on the USB3 port and USB sticks on it work slowly. I tried your DTB on: Armbian 21.05.0-trunk Focal with Linux 5.10.27-aw-h6-tv and Armbian 22.05.0-trunk with Linux 5.15.27-station both with the latest updates, it does a great job fixing the WIFI and making the USB3 port available. thank you
  25. @jock Docker looks working OK buzt i have problem with the sound in HA container that is eating 200% of all CPUs. Its one fix for it by loading one addon that is tricking the system but its cant being loaded. My theory is that is appamor that is missing and cant forcing the security for doing the patching. May i request adding appamor module being added in the kernel and in the normal armbian kernels (if the module its compiled armbian is having it disabled by default and need being activated in the kernel comandline for getting it loaded so it shall being safe) ? Thanks in advance !!
  26. your secound dtc string is wrong from dts to dtb -I = input type you have dtb should dts -O = output type you have dts should dtb -o = output file = ok also odroid use realtek LAN but many HDMI CRC and HDMI i2c ODROID C1 source file mxq use internal(amlogic) LAN and standart HDMI output MXQ source file i thing your box need also the HDMI Communication CRC and i2c pins to work