14 14

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. some added info, detail from the armbian monitor output: 527 [ 9.816528] brcmfmac: F1 signature read @0x18000000=0x16034334 529 [ 9.837294] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 530 [ 9.839398] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.rockchip,rk3318-box.bin failed with error -2 531 [ 9.843056] usbcore: registered new interface driver brcmfmac 533 [ 10.097755] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 534 [ 10.098076] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available 535 [ 10.099292] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e 1437 [ 9.119553] Bluetooth: hci0: BCM4334B0 'brcm/BCM4334B0.hcd' Patch 1444 [ 9.553660] brcmfmac: F1 signature read @0x18000000=0x16034334 1445 [ 9.573816] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 1446 [ 9.574117] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac4334-sdio.rockchip,rk3318-box.bin failed with error -2 1447 [ 9.578548] usbcore: registered new interface driver brcmfmac 1449 [ 9.787851] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 1450 [ 9.788132] brcmfmac: brcmf_c_process_clm_blob: no clm_blob available (err=-2), device may have limited channels available 1451 [ 9.788911] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e 1455 [ 9.881905] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM ... 3162 [ 10.714799] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM 4014 [ 10.135514] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM 6565 [ 9.597587] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM ... 7212 [ 8.971401] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 7215 [ 9.194035] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac4334-sdio for chip BCM4334/3 7217 [ 9.195003] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4334/3 wl0: Jul 24 2019 12:58:36 version 6.10.191 (TOB) (r) FWID 01-b049404e 7222 [ 9.597587] Bluetooth: hci0: BCM4334B1 37.4 MHz ExtLNA Murata VM 7223 [ 9.597636] Bluetooth: hci0: BCM4334B0 (002.001.013) build 1852 what can i do to be able to connect to Wi-Fi?
  3. I found some dtbs, got it from MythTV. They're all here. https://mega.nz/folder/YZMDlJwJ#_zBP60J0Ga_PVvskp18JmQ
  4. I tested some more Armbian versions with 4.9x, it was the same way. I found a guy on the LibreElec forum, he commented that he had managed to run linux on his tx6s. Heitbaum, I'm trying to get in touch with him, he still hasn't replied. Including one of the links from my first post here which is from his Git. He shared some files for tx6s. Could you take a look, please, when you have time. Maybe one of them is dtb.or maybe it's some file I can use. https://gist.github.com/heitbaum/30676739ea278a4384ceb2f3486ce232 https://gist.github.com/heitbaum/e843c2d5dd11d9206cff8631baaed663 https://gist.github.com/heitbaum/d69f32e7622b4409adcf6fe6c04ec849 https://gist.github.com/heitbaum/c6b266a8e32dd14c8824ef7fcf067207 I will research about dtb files, how to create and edit, compare the Orange hardware with my tx6s, see what I need to change or add. I will try to learn how to do it. Now that I have a path to follow it becomes better. I'll just stop trying to figure out how to run linux on it. After the tvbox stops working or exhausts my possibilities.
  5. Note that since you are using a build for a completely different device (orangepizero2 vs tx6s) you aren't going to get everything working without a proper dtb file. So at a minimum you would need to find/modify a dtb file that describes to the kernel the actual hardware in your box. Unless the opzero2 has the exact same hardware on the board as the tx6s the dtb file you are using will be wrong and the hardware that is different will not be working. I'm honestly amazed that you have as much working as you do.
  6. You are going to need to find an android rom for your box and reinstall that. The installation to emmc is risky as the boot environment is on emmc. If something goes wrong then the box is not bootable as you are seeing. It sounds like from your description you had it working from sdcard which is what I would recommend you stay with.
  7. Why i cant boot on multitool? Never work for me i follow everthing but doesnt boot when memory card are inserted I have mxq ep 2 v1
  8. Hi everybody and @jock I flashed the jammy release xfce on SD-card and boot on my old MX10-TvBox. (RK3328) I checked dmesg and there is some lines in red [ 4.332442] gpio-syscon ff100000.syscon:gpio: can't read the data register offset! ... [ 5.127442] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_refout [ 5.128139] rk_gmac-dwmac ff550000.ethernet: cannot get clock clk_mac_speed ... [ 53.545863] hdmi-audio-codec hdmi-audio-codec.4.auto: Only one simultaneous stream supported! [ 53.545903] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 53.545932] ff000000.i2s-i2s-hifi: soc_pcm_open() failed (-22) [ 68.738601] hdmi-audio-codec hdmi-audio-codec.4.auto: Only one simultaneous stream supported! [ 68.738640] hdmi-audio-codec hdmi-audio-codec.4.auto: ASoC: error at snd_soc_dai_startup on i2s-hifi: -22 [ 68.738668] ff000000.i2s-i2s-hifi: soc_pcm_open() failed (-22) Here is the whole output from 'armbianmonitor -U' ('armbianmonitor -u' can't directly upload..) https://paste.yunohost.org/oruxuwocub.vbs I'm not sure this needs to be corrected, maybe it's just this old Chinese box with more or less well-integrated hardware. Finally I share anyway, thank you again for everything @jock
  9. Hi, Thanks for the guide first. I am able to follow that to flash the sd and boot to armbian (Armbian_20.10_Arm-64_focal_current_5.9.0.img) to my A95X (A7_s905x_v2) without any problem. Then I ran the install shell. And it worked without any error as well. Then I stupid type `shutdown now` to shutdown the box. Now the box not able to turn on. I mean its not able to turn on not even boot. The red light is on when I connected the power. But with the remote I am not able to turn it on. Unplug and plug nothing happens. Before when I plug the power it will turn on (light from red to blue) but now nothing could make that happen. anybody knows what can I do now? Thanks in advance. Edit: Forgot to mention there is no reset button or hold or pin on this box. So I can't use toothpick method at all.
  10. 今天是个好日子。 有没有人成功地将 Roku Premiere (3920X) 或 Roku Premiere (4620X) 或 Roku Premiere+ (3921X) 或 Roku Premiere+ (4630X) 或 Roku Ultra (4640X) 写入 armbian 或其他 Linux 系统? 碰巧我拥有与上述同一系列的电视板。请描述详细步骤。 任何答复表示赞赏。
  11. @rzu@SteeManHi, so I tested several images with 4.9.x kernel, in some I was able to boot, but in no case I was able to install. initial remarks: this model tx6s has 2 usb 2.0, 1 usb 3.0, 1 hdmi and 1 ethernet. the white streaks in the images, from the screen is a problem with my tv General notes, on all tested images that booted: It doesn't boot the boot loader the first time, I've made more than five attempts in every one I've tested. In all cases the hdmi, 1 usb 2.0 and 3.0 worked, recognizing the keyboard. images that were tested and boot loader initialized: images taken from the link https://armbian.hosthatch.com/archive/orangepizero2/archive/ shared by @rzu Armbian_21.08.1_Orangepizero2_bullseye_legacy_4.9.280.img.xz Armbian_21.08.1_Orangepizero2_buster_legacy_4.9.280.img Armbian_21.08.2_Orangepizero2_buster_legacy_4.9.255.img Armbian_21.08.2_Orangepizero2_focal_legacy_4.9.255.img images taken from the link https://armbian.chi.auroradev.org/dl/orangepizero2/archive/?sort=size&order=desc Armbian_22.02.2_Orangepizero2_bullseye_legacy_4.9.255.img Armbian_22.02.2_Orangepizero2_focal_legacy_4.9.255.img All behaved the same way. Got stuck on black screen without loading anything, for more than 10 minutes with no change. as you can see in the image below. Image: https://ibb.co/7bfBj2t I decided to test the images available on the orangepi website for the zero 2 model. And surprisingly I was also able to boot the boot loader, and it loaded some files but it gave an error in both Ubuntu and Debian versions. Ubuntu images taken from the link https://drive.google.com/drive/folders/1ohxfoxWJ0sv8yEHbrXL1Bu2RkBhuCMup Orangepizero2_2.2.0_ubuntu_focal_desktop_linux4.9.170 Orangepizero2_2.2.0_ubuntu_bionic_desktop_linux4.9.170 Orangepizero2_2.2.0_ubuntu_focal_server_linux4.9.170 Image: https://ibb.co/3vZzrQt Debian images taken from the link https://drive.google.com/drive/folders/1Xk7b1jOMg-rftowFLExynLg0CyuQ7kCM Orangepizero2_2.2.0_debian_buster_desktop_linux4.9.170 Orangepizero2_2.2.0_debian_buster_server_linux4.9.170 I made a video to be readable, due to the problem with the TV image. Video: https://odysee.com/@uaitidoguis:d/Tanix_TX6S_Orangepizero2_2.2.0_debian_buster_desktop_linux4.9.170:f?r=H7r2LcNEzboXLJ9aLRuWBf15XxyGjZjp Well that's it, I hope this helps someone who is in the same situation. Unfortunately on mine it didn't work 100%, I'm already better than yesterday. I'll continue in the battle looking for an image that works, maybe I'll get lucky. If anyone knows any more links to images with kernel 4.9x, share it here. If I have any more progress, I'll come back to share.
  12. story goes on flashed this firmware to the device NAND: # ~/minix7/Linux_Upgrade_Tool_v1.49/upgrade_tool uf ./x7-rk3188-250.img Program Data in /root/.config/upgrade_tool Loading firmware... Support Type:RK31 FW Ver:4.4.02 FW Time:2015-12-21 18:12:34 Loader ver:2.13 Loader Time:2014-03-03 18:08:38 Upgrade firmware ok. result: no LED, no HDMI signal. USB LAN adapter LEDs are on, but after 10 min no DHCP request appeared... SDCard partition remained the same..haven't been resized... # 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
  13. 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
  14. @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.
  15. @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
  16. When i had the same problem i just expanded the partition with gparted.
  17. 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
  18. 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
  19. 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 ?
  20. 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.
  21. @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!
  22. 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...
  23. 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?
  24. 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.
  25. @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
  26.