Tomi Skies Posted October 4 Posted October 4 So there is some conflicting naming between the name of the unit and the name on the board revision code. The name of the unit would suggest that it's a X96-Q clone, but the revision number suggests that it's a T95 mini. Like as seen in this video 0 Quote
SteeMan Posted October 4 Posted October 4 What you are reporting is quite common with tv boxes. The case markings often are different than the internals. What is it you are looking for? Your post didn't really ask for anything other than to report that you got a common tv box with internals that differ from the case. 0 Quote
Nick A Posted October 4 Posted October 4 @Tomi Skies try the x96q images https://github.com/NickAlilovic/build/releases/tag/20250306 0 Quote
Tomi Skies Posted 3 hours ago Author Posted 3 hours ago @Nick A I tried the Armbian-unofficial_25.05.0-trunk_X96q-lpddr3_bookworm_edge_6.12.11_xfce_desktop.img I don't really know what I'm doing tbh, but it seems like mostly everything works except wifi. Don't know if this is of any interest, but here is a UART log of the first boot. 19:28:07.082 -> U-Boot SPL 2025.01-armbian-2025.01-S6d41-P7151-H8869-V004f-Bb703-R448a-dirty (Apr 02 2025 - 21:10:39 -0400) 19:28:07.159 -> DRAM:testing 32-bit width, rank = 2 19:28:07.159 -> DRAM:Store cfg 19:28:07.159 -> DRAM:1st writing pattern 19:28:07.159 -> DRAM:detecting column address bits 19:28:07.159 -> detected 10 columns 19:28:07.159 -> DRAM:restore cfg 19:28:07.159 -> DRAM:reconfigure for all active rows 19:28:07.159 -> DRAM:store cfg 19:28:07.159 -> DRAM:2nd writing pattern 19:28:07.192 -> DRAM:detecting row address bits 19:28:07.192 -> detected 14 rows 19:28:07.192 -> DRAM:restoring cfg 19:28:07.192 -> DRAM:end of auto detect dram size 19:28:07.192 -> MBUS port 0 cfg0 0100000d cfg1 00640080 19:28:07.192 -> MBUS port 1 cfg0 06000009 cfg1 01000578 19:28:07.192 -> MBUS port 2 cfg0 0200000d cfg1 00600100 19:28:07.192 -> MBUS port 3 cfg0 01000009 cfg1 00500064 19:28:07.192 -> MBUS port 4 cfg0 20000209 cfg1 1388157c 19:28:07.192 -> MBUS port 5 cfg0 00640209 cfg1 00200040 19:28:07.225 -> MBUS port 6 cfg0 00640209 cfg1 00200040 19:28:07.225 -> MBUS port 8 cfg0 01000009 cfg1 00400080 19:28:07.225 -> MBUS port 11 cfg0 01000009 cfg1 00640080 19:28:07.225 -> MBUS port 14 cfg0 04000009 cfg1 00400100 19:28:07.225 -> MBUS port 16 cfg0 2000060d cfg1 09600af0 19:28:07.225 -> MBUS port 21 cfg0 0800060d cfg1 02000300 19:28:07.225 -> MBUS port 22 cfg0 01000009 cfg1 00640080 19:28:07.225 -> MBUS port 25 cfg0 0064000f cfg1 00200040 19:28:07.225 -> MBUS port 26 cfg0 20000209 cfg1 1388157c 19:28:07.262 -> MBUS port 37 cfg0 01000009 cfg1 00400080 19:28:07.262 -> MBUS port 38 cfg0 00640209 cfg1 00200040 19:28:07.262 -> MBUS port 39 cfg0 20000209 cfg1 1388157c 19:28:07.262 -> MBUS port 40 cfg0 00640209 cfg1 00200040 19:28:07.262 -> 1024 MiB 19:28:07.308 -> Trying to boot from MMC1 19:28:07.819 -> NOTICE: BL31: v2.10.14(debug):armbian 19:28:07.852 -> NOTICE: BL31: Built : 18:07:43, Apr 2 2025 19:28:07.852 -> NOTICE: BL31: Detected Allwinner H616 SoC (1823) 19:28:07.852 -> NOTICE: BL31: Found U-Boot DTB at 0x4a0b2520, model: hechuang,x96-q LPDDR3 19:28:07.852 -> INFO: ARM GICv2 driver initialized 19:28:07.852 -> INFO: Configuring SPC Controller 19:28:07.852 -> INFO: PMIC: Probing AXP305 on RSB 19:28:07.852 -> ERROR: RSB: set run-time address: 0x10003 19:28:07.884 -> INFO: Could not init RSB: -65539 19:28:07.884 -> INFO: BL31: Platform setup done 19:28:07.884 -> INFO: BL31: Initializing runtime services 19:28:07.884 -> INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied 19:28:07.884 -> INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied 19:28:07.884 -> INFO: PSCI: Suspend is unavailable 19:28:07.884 -> INFO: BL31: Preparing for EL3 exit to normal world 19:28:07.928 -> INFO: Entry point address = 0x4a000000 19:28:07.928 -> INFO: SPSR = 0x3c9 19:28:07.928 -> INFO: Changed devicetree. 19:28:08.196 -> ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 19:28:08.238 -> 19:28:08.238 -> 19:28:08.238 -> U-Boot 2025.01-armbian-2025.01-S6d41-P7151-H8869-V004f-Bb703-R448a-dirty (Apr 02 2025 - 21:10:39 -0400) Allwinner Technology 19:28:08.238 -> 19:28:08.238 -> CPU: Allwinner H616 (SUN50I) 19:28:08.238 -> Model: hechuang,x96-q LPDDR3 19:28:08.238 -> DRAM: 1 GiB 19:28:08.318 -> Core: 58 devices, 20 uclasses, devicetree: separate 19:28:08.318 -> WDT: Not starting watchdog@30090a0 19:28:08.318 -> MMC: mmc@4020000: 0, mmc@4021000: 3, mmc@4022000: 1 19:28:08.362 -> Loading Environment from FAT... Unable to use mmc 0:1... 19:28:08.400 -> In: serial@5000000 19:28:08.400 -> Out: serial@5000000 19:28:08.400 -> Err: serial@5000000 19:28:08.400 -> No USB device found 19:28:08.400 -> Net: eth0: ethernet@5030000 19:28:08.400 -> starting USB... 19:28:08.400 -> No USB controllers found 19:28:08.439 -> Hit any key to stop autoboot: 1 0 19:28:09.465 -> switch to partitions #0, OK 19:28:09.465 -> mmc0 is current device 19:28:09.465 -> Scanning mmc 0:1... 19:28:09.465 -> Found U-Boot script /boot/boot.scr 19:28:09.465 -> 4641 bytes read in 2 ms (2.2 MiB/s) 19:28:09.498 -> ## Executing script at 4fc00000 19:28:09.498 -> U-boot loaded from SD 19:28:09.498 -> Boot script loaded from mmc 19:28:09.498 -> 202 bytes read in 1 ms (197.3 KiB/s) 19:28:09.498 -> Load fdt: /boot/dtb/allwinner/sun50i-h313-x96-q-lpddr3.dtb 19:28:09.539 -> 37577 bytes read in 7 ms (5.1 MiB/s) 19:28:09.539 -> Working FDT set to 4fa00000 19:28:09.539 -> Failed to load '/boot/dtb/allwinner/overlay/sun50i-h616-fixup.scr' 19:28:10.920 -> 15484849 bytes read in 1362 ms (10.8 MiB/s) 19:28:14.642 -> 42621440 bytes read in 3744 ms (10.9 MiB/s) 19:28:14.642 -> Moving Image from 0x40080000 to 0x40200000, end=0x42b50000 19:28:14.909 -> ## Loading init Ramdisk from Legacy Image at 4ff00000 ... 19:28:14.950 -> Image Name: uInitrd 19:28:14.950 -> Image Type: AArch64 Linux RAMDisk Image (gzip compressed) 19:28:14.950 -> Data Size: 15484785 Bytes = 14.8 MiB 19:28:14.950 -> Load Address: 00000000 19:28:14.950 -> Entry Point: 00000000 19:28:14.950 -> Verifying Checksum ... OK 19:28:15.040 -> ## Flattened Device Tree blob at 4fa00000 19:28:15.040 -> Booting using the fdt blob at 0x4fa00000 19:28:15.040 -> Working FDT set to 4fa00000 19:28:15.040 -> Loading Ramdisk to 4913b000, end 49fff771 ... OK 19:28:15.073 -> Loading Device Tree to 00000000490c9000, end 000000004913afff ... OK 19:28:15.073 -> Working FDT set to 490c9000 19:28:15.073 -> 19:28:15.073 -> Starting kernel ... 19:28:15.073 -> 19:32:05.614 -> 19:32:05.614 -> x96q-lpddr3 login: root (automatic login) 19:32:05.614 -> 19:32:29.834 -> Last login: Thu Apr 3 01:16:15 UTC 2025 on tty1 19:33:10.979 -> 19:33:10.979 -> x96q-lpddr3 login: root (automatic login) 19:33:10.979 -> 19:33:10.979 -> Last login: Thu Apr 3 01:16:15 UTC 2025 on ttyS0 19:33:17.425 -> 19:33:17.425 -> Waiting for system to finish booting ... 19:33:25.662 -> Waiting for network startup to complete... 19:33:42.217 -> [H[J[3JWelcome to [1m[97mArmbian-unofficial[0m! 19:33:42.217 -> 19:33:42.217 -> Documentation: [1m[92mhttps://docs.armbian.com/[0m | Community support: [1m[92mhttps://community.armbian.com/[0m 19:33:42.263 -> 19:33:42.263 -> 19:33:42.263 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (6) 19:33:43.299 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (5) 19:33:44.298 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (4) 19:33:45.362 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (3) 19:33:46.358 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (2) 19:33:47.390 -> [1A[KIP address: [92m[0m [1m[97mWaiting for local connection![0m Retrying... (1) 19:33:48.451 -> [1A[KIP address: [92m[0m [1m[31mNetwork connection timeout![0m 19:33:49.462 -> 19:33:49.462 -> Create root password: 19:33:57.499 -> Armbian-unofficial 25.05.0-trunk Bookworm ttyS0 19:33:57.548 -> 19:33:57.548 -> x96q-lpddr3 login: [ 1858.394981] reboot: Power down 19:59:13.714 -> � 0 Quote
Nick A Posted 2 hours ago Posted 2 hours ago @Tomi Skies can you change the log level to 7 in armbianEnv.txt on sdcard. I don’t see your wifi chip in the picture above. It might be on the other side of your board. 0 Quote
Tomi Skies Posted 2 hours ago Author Posted 2 hours ago @Nick A I think this is the wifi chip? 0 Quote
Nick A Posted 1 hour ago Posted 1 hour ago (edited) @Tomi Skies XR819 shoud work. Can you post your dmesg log. Edited 59 minutes ago by Nick A 0 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.