fangis

@jock if I recall correctly, I have tested it in both folders and it made no difference, any other ideas ? yes, using a legacy kernel.

Hi @jock , thanks if you can help with this. I'll do a more complete post. If not enough I can post the whole dmesg, later

hi @ilmich, thanks for the help I can't test the box right now, only on Sundays and even then it's difficult but I have some logs, maybe it's helpful ? cat dmesg2.txt | grep -i sdio -A5 -B5 [ 4.911371] Bluetooth: HCI UART protocol ATH3K registered [ 4.917876] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 4.924728] Bluetooth: HCI UART protocol BCM registered [ 4.931574] usbcore: registered new interface driver bfusb [ 4.938344] usbcore: registered new interface driver btusb [ 4.944845] Bluetooth: Generic Bluetooth SDIO driver ver 0.1 [ 4.952172] cpu cpu0: leakage=5 [ 4.958698] cpu cpu0: leakage-volt-sel=0 [ 4.965482] cpu cpu0: Failed to get pvtm [ 4.974092] cpu cpu0: avs=0 [ 4.980660] cpu cpu0: l=-2147483648 h=2147483647 hyst=0 l_limit=0 h_limit=0 [ 4.987149] cpu cpu0: failed to read out thermal zone (-22) [ 4.994450] cpu cpu0: failed to find power_model node [ 5.000172] pwrseq_simple sdio-pwrseq: GPIO lookup for consumer reset [ 5.004832] pwrseq_simple sdio-pwrseq: using device tree for GPIO lookup [ 5.009496] of_get_named_gpiod_flags: parsed 'reset-gpios' property of node '/sdio-pwrseq[0]' - status (0) [ 5.014887] Synopsys Designware Multimedia Card Interface Driver [ 5.020518] usb 6-1: New USB device found, idVendor=062a, idProduct=4c01 [ 5.020572] dwmmc_rockchip 30000000.dwmmc: IDMAC supports 32-bit address mode. [ 5.020877] dwmmc_rockchip 30000000.dwmmc: Using internal DMA controller. [ 5.020899] dwmmc_rockchip 30000000.dwmmc: Version ID is 270a -- [ 1485.043886] [<b0009a68>] (do_one_initcall) from [<b00be208>] (do_init_module+0x74/0x1f4) [ 1485.043903] [<b00be208>] (do_init_module) from [<b00c011c>] (load_module+0x1cc8/0x22bc) [ 1485.043919] [<b00c011c>] (load_module) from [<b00c080c>] (SyS_init_module+0xfc/0x198) [ 1485.043935] [<b00c080c>] (SyS_init_module) from [<b0010100>] (ret_fast_syscall+0x0/0x54) [ 1485.043945] ---[ end trace ece8e1cf317b4e16 ]--- [ 1485.044289] ssv6xxx_sdio_init [ 1485.545091] initWlan : Retry to carddetect [ 1486.205085] initWlan : Retry to carddetect [ 1486.865044] initWlan : Retry to carddetect [ 1487.525035] initWlan : Retry to carddetect [ 1488.185005] initWlan : Retry to carddetect [ 1510.775726] generic_wifi_exit_module [ 1510.879369] ssv6xxx_sdio_exit [ 1510.936458] mmc1:mmc host rescan start! [ 1510.936506] [WLAN_RFKILL]: rockchip_wifi_power: 0 [ 1510.936539] [WLAN_RFKILL]: rockchip_wifi_power: rfkill-wlan driver has not Successful initialized [ 1552.920252] generic_wifi_init_module [ 1553.199584] *** sta_cfg_set, /etc/firmware/ssv6051-wifi.conf *** [ 1553.203279] ssv6xxx_sdio_init [ 1553.707424] initWlan : Retry to carddetect [ 1554.367412] initWlan : Retry to carddetect [ 1555.027387] initWlan : Retry to carddetect [ 1555.687387] initWlan : Retry to carddetect [ 1556.347376] initWlan : Retry to carddetect [ 1650.075422] generic_wifi_exit_module [ 1650.177386] ssv6xxx_sdio_exit [ 1650.233107] mmc1:mmc host rescan start! [ 1650.233154] [WLAN_RFKILL]: rockchip_wifi_power: 0 [ 1650.233185] [WLAN_RFKILL]: rockchip_wifi_power: rfkill-wlan driver has not Successful initialized [ 1672.520954] generic_wifi_init_module [ 1672.800656] *** sta_cfg_set, /lib/firmware/ssv6051-wifi.cfg *** [ 1672.811224] ssv6xxx_sdio_init [ 1673.312564] initWlan : Retry to carddetect [ 1673.972534] initWlan : Retry to carddetect [ 1674.632554] initWlan : Retry to carddetect [ 1675.292553] initWlan : Retry to carddetect [ 1675.952503] initWlan : Retry to carddetect r@pc:/mxq$ thank you

@TU-Student , hello, I predict someone will tell you to use an uart to usb converter. I am no expert on this, but I would guess maybe in pic 1 those 4 pins on the lower part are the uart ? ? please don't try before testing with a voltmeter or something ... @ilmich , great ! my ssv6051 isn't working yet. maybe one day i'll be able to debug it.

@ojogoperdi ? ? It is indeed very possible to boot from sdcard without touching the internal storage, my sd image does it, and I know some others have done it too. My parents box has their Android intact and they still think android is so much better than linux 😄

@jock I didn't know the sellers could have that much profit !

@fabiobassa I agree. I think back some decade ago, when the tv boxes have appeared, then you could buy some box that actually matched the description. they often also had that cool usb drive appearance. But then now they are really popular, especially some models. here I think the most famous is that mxq pro box. So now when you buy it it's a real lottery, it can be anything. especially because now the sellers want to advertise a 64 bit cpu and sell something worse. I was trying to boot linux for rk33xx and failing, only understood what was going on when I installed a terminal emulator and then saw user rk322x.

Wow ! Can I have one ? ? here I tested a sdcard image on my parents mxq pro box, and for basic tasks it's fine. Chromium basic browsing libreoffice etc! And of course all the command-line programs and servers will work fine too. From what I read tx9 should have an amlogic cpu, so no wonder why some of them aren't booting ?

Hello ! the dmesg log is for the kernel messages. I think the serial log gets these and even earlier messages from the bootloaders.

@n3o, hello, I was suggesting android to get your logs: 1.in android, download a terminal emulator app 2.in the app type: dmesg 3.the logs will appear, then copy and paste the parts you need. Anyway it seems now you don't need it. @ochentay4, OK , I have suggested that way because to me it seemed the best to your situation, basically you would have a mix of libreelec boot files, and armbian file system. anyway good luck

@fabiobassa I think he meant that he took some pics with his camera. And, please correct if i'm wrong, but, @ochentay4 if you can boot libreelec I think you can boot armbian , at least by doing a mixed image, as proposed by user "hexdump" in the first posts, that's how I prepared my sdcard image too. good luck

@n3o can you still boot to android ?

hello @Prioner If the driver has no source available, I don't think it can work with a compiled kernel. The only way I see a closed source driver could work, would be if you used your original kernel and used it to boot a linux file system. Have a good week,

Here are my impressions after some weekend tests: Overall, it's all working better than I expected ! Despite some things I have read here, the desktop experience is fine to me, maybe my standards are too low? chromium is loading first time in about 10 seconds, after that it's faster. It's not super responsive to the commands, but it's not too laggy either. Youtube in Chromium is almost OK to watch, which surprised me, I expected much worse. But there is some stuttering. I think it can work much better with some external app. I installed smtube, but it depends on youtube-dl which was failing, but now I found a 2023 version of it that seems to work, to be tested later. I installed many window managers, jwm, icewm, wmaker and lxde, all working well, but I now mostly like icewm which combines a very light ram usage and some nice windows-looking menus. Ideal to show your friends who think linux is an OS that only can be used by wizards. My parents like printing so I put there cups with hplip, and libreoffice showed a nice preview, remote printing worked, which made them impressed, they asked me how I did that, funny, right. Ethernet worked for most of the time but suddenly stopped one or two times, I am not sure if this is a driver issue or network-manager related, to be verified. Wifi was failing to load, I now found out that ssv6051 was looking for a .conf file and it was named .cfg in the filesystem, to verify later if it works after correcting it. The internal storage was detected as mmcblk2 and some partitions mmcblk2boot0 and boot1, however I couldn't mount them, I am not sure what goes on here, maybe it's a different rockchip filesystem because of the boot files and with the correct offset it can be mounted, to be checked later. IN my opinion it truly makes a little pc in your tv, thumbs up ...

Hello RaptorSDS I have done it some years ago, so I don't remeber it all, but I recall it as being easy, just installed them with apt, as "apt install jwm" and then there was an option to switch between the different window managers on login, you can have many of them installed. The defaults will probably work but for the links you asked, google for 'jwm window manager', 'openbox window manager' or the manuals, 'man jwm' , etc. I think somehow in your setup there were libraries missing ...