Nick A Posted July 25 Posted July 25 Your tv stick probably has secure boot enabled. You can compile a secure boot image using these steps. 1 Quote
Randlin Posted July 25 Posted July 25 Nice! I'll try that. Thank you for your help so far. Finding the right documentation has been a little tricky for me and I really appreciate the help. 0 Quote
Randlin Posted July 25 Posted July 25 Alright, I built the x96q-lpddr3 image using the patches suggested. It booted (partially). Nothing on the screen, but it is starting! I chose that image because it is H313 and lpddr3 (the android uboot build that worked before detected it as such) I attached the serial log. It's getting late here and I may not get much more done on this until Monday, but this is a good sign in my opinion. uboot.txt 0 Quote
Nick A Posted July 25 Posted July 25 (edited) H313/H616/H618 are pretty much the same SOC. It’s the AXP power management IC that’s different. Also RAM and WIFi chips are usually different. https://linux-sunxi.org/AXP_PMICs Edited July 26 by Nick A 0 Quote
Randlin Posted July 28 Posted July 28 Cool, good to know. I'll try one with the same AXP and go from there. 0 Quote
Randlin Posted July 28 Posted July 28 Hmm, according to the config, the X96q lpddr3 uses the AXP313 already. Maybe ram is wrong? Pretty sure it's lpddr3, if there is any way to check that, I can. Gonna do a little digging in android. 0 Quote
Randlin Posted July 28 Posted July 28 According to Android uboot, DRAM_VCC= 1200mv DRAM CLK =648 MHZ DRAM TYPE=7 (lpddr3) DRAM SIZE =1536 MBytes, para1 = 30fa, para2 = 6001000, dram_tpr13 = 26061 gonna try some of this in the x96q image, see what happens 0 Quote
Randlin Posted July 28 Posted July 28 Hmm, in boot log I see AXP1530 mentioned in theandroid boot (booted off the sd card, not emmc). I attached the log. bootinfo.txt 0 Quote
Randlin Posted July 28 Posted July 28 I set the dram speed to 648, no difference. Gotta be the axp or another option. 0 Quote
Nick A Posted July 28 Posted July 28 (edited) AXP1530 is the same as AXP313a. Take a look at the link I posted above. You could use this tool to extract your dram settings from an android update or boot0.bin. https://github.com/apritzel/sunxi-fw sunxi-fw info -v boot0.bin Edited July 28 by Nick A 0 Quote
Randlin Posted July 28 Posted July 28 I did notice in the log: INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 0 Quote
Randlin Posted July 28 Posted July 28 Wait, that was the Linux kernel, not uboot. I'll get that 0 Quote
Randlin Posted July 28 Posted July 28 /sunxi-fw info -v fulldisk.img @ 0: mbr: DOS MBR protective MBR, GPT used GPT version 00010000 usable disk size: 7419 MB number of partition entries: 17 @ 16: toc0: signed boot image 2 items size: 98304 bytes @ 321: toc0: signed boot image 2 items size: 98304 bytes @26812: fit: U-Boot FIT image fit:__overlay__: "<no description>" fit:__overlay__: "<no description>" fit:fragment@2: "<no description>" So I never dumped just boot0 (and no firmware update available), but I have full emmc dump named fulldisk.img. I would assume it is the toc0? Trying to extract does not work , however: (maybe because there are two?) /sunxi-fw extract -v -n toc0 -o uboot0 /home/Tr/fulldisk.img unknown image file extracting the mbr works fine though. 0 Quote
Nick A Posted July 28 Posted July 28 This post should help extracting your boot.img from android. That’s if your box is already rooted. 0 Quote
Randlin Posted July 28 Posted July 28 (edited) Oh, so it is the devicetree of Linux we want. My bad. Here it is: devicetree.txt FYI I was able to use binwalk -e on the boot partition dump, nice to see there is another way. Thanks for all the help Edited July 28 by Randlin 0 Quote
Nick A Posted July 28 Posted July 28 (edited) Actually in that post it was about downloading the boot_a partition. Then extracting the dts.. you can skip the dts extraction part for now. We need your boot_a partition. also that’s not the android dts you posted. It has some info but not all of it. Edited July 29 by Nick A 0 Quote
Randlin Posted July 29 Posted July 29 (edited) Hmm, I used a different boot.img extractor before to try to get dts, but that spectacularly failed ( https://github.com/anestisb/android-unpackbootimg ). I do have a dump of each of the partitions from root, but there was no boot_a boot_b, just boot (not an a/b system). I'll try that extractor, hopefully that will be better. everthing is here: https://archive.org/download/G96_Firmware_Dump/Dumped Partitions/ list of partitions dumped: (there are 17 listed in the emmc, but 18 in android for some reason, probably one is a duplicate) Reserve boot bootloader cache empty env frp media_data metadata misc mmcblk0boot0 mmcblk0boot1 private recovery super vbmeta vbmeta_system vbmeta_vendor Edited July 29 by Randlin 0 Quote
Randlin Posted July 29 Posted July 29 direct link to boot: https://archive.org/download/G96_Firmware_Dump/Dumped Partitions/boot 0 Quote
Randlin Posted July 29 Posted July 29 Ok, that extractor worked. I uploaded it as a zip here: https://uploadnow.io/f/9VvPT91 0 Quote
Nick A Posted July 29 Posted July 29 (edited) Have you tried running sunxi-fw with the boot image you used to extract the dts? The boot image you posted is a U-Boot FIT image. It doesn't have the dram information we are looking for. I believe mmcblk0boot0 is the correct boot image but the one you uploaded didn't work with sunxi-fw. Also, I found this in your dts. Maybe these settings will work. To make sure these settings are correct I prefer to get the dram settings using the sunxi-fw tool. dram { compatible = "allwinner,dram"; clocks = <0xda>; clock-names = "pll_ddr"; dram_clk = <0x288>; dram_type = <0x07>; dram_zq = <0x3f3fdd>; dram_odt_en = <0x9988eeee>; dram_para1 = <0x30fa>; dram_para2 = <0x1000>; dram_mr0 = <0x00>; dram_mr1 = <0xc3>; dram_mr2 = <0x06>; dram_mr3 = <0x01>; dram_tpr0 = <0x00>; dram_tpr1 = <0x00>; dram_tpr2 = <0x00>; dram_tpr3 = <0x00>; dram_tpr4 = <0x00>; dram_tpr5 = <0x00>; dram_tpr6 = <0x2fc08080>; dram_tpr7 = <0x00>; dram_tpr8 = <0x00>; dram_tpr9 = <0x00>; dram_tpr10 = <0x402f3379>; dram_tpr11 = <0xd100b0f>; dram_tpr12 = <0x11131113>; dram_tpr13 = <0x80060>; linux,phandle = <0x183>; phandle = <0x183>; device_type = "dram"; dram_dx_odt = <0x6060606>; dram_dx_dri = <0xd0d0d0d>; dram_ca_dri = <0x1919>; dram_mr4 = <0x00>; dram_mr5 = <0x00>; dram_mr6 = <0x00>; dram_mr11 = <0x00>; dram_mr12 = <0x00>; dram_mr13 = <0x00>; dram_mr14 = <0x00>; dram_mr16 = <0x00>; dram_mr17 = <0x00>; dram_mr22 = <0x00>; }; The dram clock is in hex you'll need to convert this value to decimal. https://www.rapidtables.com/convert/number/hex-to-decimal.html Edited July 30 by Nick A 0 Quote
Randlin Posted July 30 Posted July 30 Hmm, I tried running it on both mmcblk0boot* and got no output. I'll try running it on the full dump with -a to see if anything comes up. I'll try adding it to the config and go from there, see if it works. I'm not familiar with memory config and a lot of this stuff, but I am trying to learn all kinds of low level stuff and welcome the challenge! 0 Quote
Randlin Posted July 30 Posted July 30 Yeah with the full dump it is essentially the same as boot.img. Manual testing it is. 0 Quote
Randlin Posted July 30 Posted July 30 Ok, just used adb pull /proc/device-tree and used dtc and got this dts. This should be a complete dts. dts.txt 0 Quote
Nick A Posted July 30 Posted July 30 You can find the dram config options here. https://elixir.bootlin.com/u-boot/v2025.07-rc2/source/arch/arm/mach-sunxi/Kconfig if DRAM_SUN50I_H616 config DRAM_SUNXI_DX_ODT hex "DRAM DX ODT parameter" help DX ODT value from vendor DRAM settings. config DRAM_SUNXI_DX_DRI hex "DRAM DX DRI parameter" help DX DRI value from vendor DRAM settings. config DRAM_SUNXI_CA_DRI hex "DRAM CA DRI parameter" help CA DRI value from vendor DRAM settings. config DRAM_SUNXI_ODT_EN hex "DRAM ODT EN parameter" default 0x1 help ODT EN value from vendor DRAM settings. config DRAM_SUNXI_TPR0 hex "DRAM TPR0 parameter" default 0x0 help TPR0 value from vendor DRAM settings. config DRAM_SUNXI_TPR2 hex "DRAM TPR2 parameter" default 0x0 help TPR2 value from vendor DRAM settings. config DRAM_SUNXI_TPR6 hex "DRAM TPR6 parameter" default 0x3300c080 help TPR6 value from vendor DRAM settings. config DRAM_SUNXI_TPR10 hex "DRAM TPR10 parameter" help TPR10 value from vendor DRAM settings. It tells which features should be configured, like write leveling, read calibration, etc. config DRAM_SUNXI_TPR11 hex "DRAM TPR11 parameter" default 0x0 help TPR11 value from vendor DRAM settings. config DRAM_SUNXI_TPR12 hex "DRAM TPR12 parameter" default 0x0 help TPR12 value from vendor DRAM settings. 0 Quote
Randlin Posted August 8 Posted August 8 Sorry for the delay, was busy the last week. I applied the ram settings and did a couple of builds with different ones. Nothing has worked any better so far. Should I try more of the ram configs? does not work, uboot bootloops: dram 7 in dts I extracted using dts-compiler (there are other dram definitions in there as well) +CONFIG_DRAM_CLK=648 +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x3030303 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0xe0e0e0e +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x1f12 +CONFIG_DRAM_SUN50I_H616_ODT_EN=0x01 +CONFIG_DRAM_SUN50I_H616_TPR0=0xc0001002 +CONFIG_DRAM_SUN50I_H616_TPR6=0x33808080 +CONFIG_DRAM_SUN50I_H616_TPR10=0x2f1107 +CONFIG_DRAM_SUN50I_H616_TPR11=0xddddcccc +CONFIG_DRAM_SUN50I_H616_TPR12=0xeddc7665 works the same as before, still gets stuck at same place (from binwalk dts): +CONFIG_DRAM_CLK=648 +CONFIG_DRAM_SUN50I_H616_DX_ODT=0x06060606 +CONFIG_DRAM_SUN50I_H616_DX_DRI=0x0d0d0d0d +CONFIG_DRAM_SUN50I_H616_CA_DRI=0x1919 +CONFIG_DRAM_SUN50I_H616_ODT_EN=0x9988eeee +CONFIG_DRAM_SUN50I_H616_TPR0=0x00 +CONFIG_DRAM_SUN50I_H616_TPR6=0x2fc08080 +CONFIG_DRAM_SUN50I_H616_TPR10=0x402f3379 +CONFIG_DRAM_SUN50I_H616_TPR11=0xd100b0f +CONFIG_DRAM_SUN50I_H616_TPR12=0x11131113 +CONFIG_DRAM_SUN50I_H616_TPR13=0x80000000 Is it possible this error may be an issue? INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 And the uboot serial log from the working one: Spoiler U-Boot SPL 2025.01-armbian-2025.01-S6d41-Pa844-H8869-V004f-Bb703-R448a-dirty (Aug 08 2025 - 16:31:45 +0000) DRAM:testing 32-bit width, rank = 2 DRAM:Store cfg DRAM:1st writing pattern DRAM:detecting column address bits detected 10 columns DRAM:restore cfg DRAM:reconfigure for all active rows DRAM:store cfg DRAM:2nd writing pattern DRAM:detecting row address bits detected 15 rows DRAM:restoring cfg DRAM:end of auto detect dram size MBUS port 0 cfg0 0100000d cfg1 00640080 MBUS port 1 cfg0 06000009 cfg1 01000578 MBUS port 2 cfg0 0200000d cfg1 00600100 MBUS port 3 cfg0 01000009 cfg1 00500064 MBUS port 4 cfg0 20000209 cfg1 1388157c MBUS port 5 cfg0 00640209 cfg1 00200040 MBUS port 6 cfg0 00640209 cfg1 00200040 MBUS port 8 cfg0 01000009 cfg1 00400080 MBUS port 11 cfg0 01000009 cfg1 00640080 MBUS port 14 cfg0 04000009 cfg1 00400100 MBUS port 16 cfg0 2000060d cfg1 09600af0 MBUS port 21 cfg0 0800060d cfg1 02000300 MBUS port 22 cfg0 01000009 cfg1 00640080 MBUS port 25 cfg0 0064000f cfg1 00200040 MBUS port 26 cfg0 20000209 cfg1 1388157c MBUS port 37 cfg0 01000009 cfg1 00400080 MBUS port 38 cfg0 00640209 cfg1 00200040 MBUS port 39 cfg0 20000209 cfg1 1388157c MBUS port 40 cfg0 00640209 cfg1 00200040 2048 MiB Trying to boot from MMC1 NOTICE: BL31: v2.10.14(debug):armbian NOTICE: BL31: Built : 20:20:28, Aug 7 2025 NOTICE: BL31: Detected Allwinner H616 SoC (1823) NOTICE: BL31: Found U-Boot DTB at 0x4a0b2520, model: hechuang,x96-q LPDDR3 INFO: ARM GICv2 driver initialized INFO: Configuring SPC Controller INFO: PMIC: Probing AXP305 on RSB ERROR: RSB: set run-time address: 0x10003 INFO: Could not init RSB: -65539 INFO: BL31: Platform setup done INFO: BL31: Initializing runtime services INFO: BL31: cortex_a53: CPU workaround for erratum 855873 was applied INFO: BL31: cortex_a53: CPU workaround for erratum 1530924 was applied INFO: PSCI: Suspend is unavailable INFO: BL31: Preparing for EL3 exit to normal world INFO: Entry point address = 0x4a000000 INFO: SPSR = 0x3c9 INFO: Changed devicetree. ns16550_serial serial@5000000: pinctrl_select_state_full: uclass_get_device_by_phandle_id: err=-19 U-Boot 2025.01-armbian-2025.01-S6d41-Pa844-H8869-V004f-Bb703-R448a-dirty (Aug 08 2025 - 16:31:45 +0000) Allwinner Technology CPU: Allwinner H616 (SUN50I) Model: hechuang,x96-q LPDDR3 DRAM: 2 GiB (effective 0 Bytes) 0 Quote
Randlin Posted August 8 Posted August 8 (edited) Hmm, in Android boot log I saw references to 1.5g ram, maybe this? https://github.com/johang/sd-card-images/issues/150 The spot in question: [536]Actual DRAM SIZE =1536 M [538]DRAM SIZE =1536 MBytes, para1 = 30fa, para2 = 6001000, dram_tpr13 = 26061 Android boot log in easier to read format: Spoiler [485]HELLO! SBOOT is starting! [488]sboot commit : 749c1f9a [491]set pll start [494]periph0 has been enabled [497]set pll end [499]unknow PMU [500]unknow PMU [503]tPMU: 0x9c [504]PMU: AXP1530 [506]dram return write ok [509]board init ok [510]try to probe rtc region [513]DRAM BOOT DRIVE INFO: V0.651 [516]the chip id is 0x5c00 [519]chip id check OK [522]DRAM_VCC set to 1200 mv [525]DRAM CLK =648 MHZ [527]DRAM Type =7 (3:DDR3,4:DDR4,7:LPDDR3,8:LPDDR4) [536]Actual DRAM SIZE =1536 M [538]DRAM SIZE =1536 MBytes, para1 = 30fa, para2 = 6001000, dram_tpr13 = 26061 [548]DRAM simple test OK. [550]rtc standby flag is 0x0, super standby flag is 0x0 [555][mmc]: mmc driver ver 2021-10-12 13:56 [560][mmc]: b mmc 0 bias 4 [568][mmc]: Wrong media type 0x0 [571][mmc]: ***Try SD card 0*** [580][mmc]: HSSDR52/SDR25 4 bit [583][mmc]: 50000000 Hz [585][mmc]: 61056 MB [587][mmc]: ***SD/MMC 0 init OK!!!*** [708]read toc1 from emmc 32800 sector [712]OLD version: 0.0 [714]NEW version: 0.0 [790]load rotpk hash [853]load monitor-key hash [856]load monitor hash [1061]load boot-key hash [1064]load boot hash [1130]load vbmeta-key hash [1133]load vbmeta hash [1200]load recovery-key hash [1203]load recovery hash [1207]monitor entry=0x48000000 [1210]uboot entry=0x4a000000 [1212]optee entry=0x48600000 [1218]run out of boot0 NOTICE: BL3-1: v1.0(debug):05d6c57 NOTICE: BL3-1: Built : 13:35:35, 2021-10-28 NOTICE: BL3-1 commit: 8 NOTICE: cpuidle init version V1.0 NOTICE: secure os exist MESSAGE: [0x0] TEE-CORE: OP-TEE version: 81ab7a47 #1 2020年 05月 06日 星期三 02:40:04 UTC arm NOTICE: BL3-1: Preparing for EL3 exit to normal world NOTICE: BL3-1: Next image address = 0x4a000000 NOTICE: BL3-1: Next image spsr = 0x1d3 U-Boot 2018.05-g23fdfbb-dirty (Jul 27 2024 - 09:05:11 +0800) Allwinner Technology [01.314]CPU: Allwinner Family [01.317]Model: sun50iw9 I2C: ready [01.321]DRAM: 1.5 GiB [01.324]Relocation Offset is: 55ebf000 [01.366]secure enable bit: 1 [01.368]pmu_axp152_probe pmic_bus_read fail [01.372]PMU: AXP1530 [01.378]CPU=1008 MHz,PLL6=600 Mhz,AHB=200 Mhz, APB1=100Mhz MBus=400Mhz [01.386]drv_disp_init [01.416]__clk_enable: clk is null. [01.422]drv_disp_init finish [01.425]gic: sec monitor mode [01.455]flash init start [01.457]workmode = 0,storage type = 1 [01.460]MMC: 0 [01.462][mmc]: mmc driver ver uboot2018:2021-07-19 14:09:00 [01.468][mmc]: get sdc_type fail and use default host:tm1. [01.479][mmc]: Using default timing para [01.482][mmc]: SUNXI SDMMC Controller Version:0x40200 [01.500][mmc]: card_caps:0x3000000a [01.503][mmc]: host_caps:0x3000003f [01.506]sunxi flash init ok [01.510]Loading Environment from SUNXI_FLASH... OK secure storage read hdcpkey fail [01.528]secure storage read hdcpkey fail with:-1 secure storage read widevine fail [01.535]secure storage read widevine fail with:-1 [01.541]usb burn from boot delay time 0 weak:otg_phy_config [01.554]usb prepare ok [01.890]usb sof ok [01.892]usb probe ok [01.894]usb setup ok set address 0x7 set address 0x7 ok [04.900]do_burn_from_boot usb : have no handshake [04.904]boot_gui_init:start FAT: Misaligned buffer address (9be7b6d8) 32 bytes read in 4 ms (7.8 KiB/s) tcon_de_attach:de=0,tcon=2[05.049]boot_gui_init:finish [05.053]bmp_name=bootlogo.bmp 2764854 bytes read in 116 ms (22.7 MiB/s) [05.190]name in map device_unlock [05.193]name in map fastboot_status_flag [05.197]find fastboot unlock flag [05.204]update dts ** Unrecognized filesystem type ** [05.223]load file(ULI/factory/rootwait init.txt) error. ** Unrecognized filesystem type ** [05.245]load file(ULI/factory/snum.txt) error. [05.249]name in map mac ** Unrecognized filesystem type ** [05.269]load file(ULI/factory/wifi_mac.txt) error. ** Unrecognized filesystem type ** [05.291]load file(ULI/factory/bt_mac.txt) error. ** Unrecognized filesystem type ** [05.312]load file(ULI/factory/selinux.txt) error. ** Unrecognized filesystem type ** [05.334]load file(ULI/factory/specialstr.txt) error. [05.356]update part info [05.403]update bootcmd [05.405]No ethernet found. Hit any key to stop autoboot: 0 [06.236]bmp_name=orange_warning.bmp ** Unable to read file orange_warning.bmp ** [06.246]sunxi bmp info error : unable to open logo file orange_warning.bmp [11.363]bmp_name=bootlogo.bmp 2764854 bytes read in 117 ms (22.5 MiB/s) [11.557]Starting kernel ... [11.559][mmc]: MMC Device 2 not found [11.563][mmc]: mmc 2 not find, so not exit [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 4.9.170 (cmj@a-X11DPi-N-T) (gcc version 5.3.1 20160412 (Linaro GCC 5.3-2016.05) ) #1 SMP PREEMPT Sat Jul 27 09:06:28 CST 2024 [ 0.000000] Boot CPU: AArch64 Processor [410fd034] [ 0.000000] bootconsole [earlycon0] enabled [ 0.027907] BOOTEVENT: 27.891082: ON [ 0.255636] sunxi_i2c_probe()2209 - [i2c3] warning: failed to get regulator id [ 0.256679] sunxi_i2c_probe()2209 - [i2c5] warning: failed to get regulator id [ 0.258075] axp2101-regulator axp2101-regulator.0: Setting DCDC frequency for unsupported AXP variant [ 0.258160] axp2101-regulator axp2101-regulator.0: Error setting dcdc frequency: -22 [ 0.293257] [ac200] get ave_regulator_name failed! [ 0.293779] [ac200] pwm enable [ 0.355541] failed to get standby led pin assign [ 0.35▒[ 0.362340] uart uart1: get regulator failed [ 0.395506] [NAND][NE] Not found valid nand node on dts [ 0.404195] sunxi-wlan soc@03000000:wlan: get gpio chip_en failed [ 0.411131] sunxi-wlan soc@03000000:wlan: get gpio power_en failed [ 0.540734] hci: request ohci1-controller gpio:232 [ 0.732636] axp2101_pek: axp2101-pek can not register without irq [ 0.743174] sunxi_ir_startup: get ir protocol failed [ 0.751638] VE: get debugfs_mpp_root is NULL, please check mpp [ 0.751638] [ 0.759986] VE: sunxi ve debug register driver failed! [ 0.759986] [ 0.817925] mmc:failed to get gpios [ 0.855700] FD655: Fd655 Driver init. [ 0.855817] sunxi-mmc sdc1: smc 1 p1 err, cmd 52, RTO !! [ 0.860715] sunxi-mmc sdc1: smc 1 p1 err, cmd 52, RTO !! [ 0.871095] sunxi-mmc sdc1: smc 1 p1 err, cmd 5, RTO !! [ 0.877107] sunxi-mmc sdc1: smc 1 p1 err, cmd 5, RTO !! [ 0.883019] sunxi-mmc sdc1: smc 1 p1 err, cmd 5, RTO !! [ 0.888919] sunxi-mmc sdc1: smc 1 p1 err, cmd 5, RTO !! [ 0.901113] FD655: fd655_driver_probe [ 0.905332] FD655: fd655_driver_probe [ 0.909948] FD655: register_fd655_driver: Successed to add fd655 module [ 0.917931] FD655: ====================Command opne in probe============= [ 0.927083] FD655: ====================Display boot in probe============= [ 0.934930] gpio user platform_driver_register sucess [ 0.951935] failed get gpio-spdif gpio from dts,spdif_gpio:-2 [ 0.961697] [audio-codec]dachpf_cfg configurations missing or invalid. [ 0.969362] lineout_vol:26, linein_gain:3, fmin_gain:3, digital_vol:0, adcdrc_cfg:0, adchpf_cfg:0, dacdrc_cfg:0, dachpf_cfg:0, ramp_func_used:1, pa_msleep_time:160, pa_ctl_level:0, gpio-spk:0 [ 0.993459] sndhdmi sndhdmi: ASoC: CPU DAI (null) not registered [ 1.000309] sndhdmi sndhdmi: snd_soc_register_card() failed: -517 [ 1.013836] sunxi-ahub-cpudai 5097000.cpudai3-controller: ahub cpudai id invalid [ 1.047779] ERROR: pinctrl_get for HDMI2.0 DDC fail [ 1.061846] tv_probe()1435 - of_property_read_string tv_power failed! [ 1.144198] cpu cpu1: opp_list_debug_create_link: Failed to create link [ 1.151683] cpu cpu1: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.159287] cpu cpu2: opp_list_debug_create_link: Failed to create link [ 1.166743] cpu cpu2: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.174333] cpu cpu3: opp_list_debug_create_link: Failed to create link [ 1.181800] cpu cpu3: _add_opp_dev: Failed to register opp debugfs (-12) [ 1.527125] [HDMI2 error]: sink do not support this mode:16 [ 3.345120] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 tcontext=u:object_r:default_prop:s0 tclass=property_service permissive=1 [ 3.345120] [ 3.363036] selinux: avc: denied { set } for scontext=u:r:vendor_init:s0 tcontext=u:object_r:dalvik_prop:s0 tclass=property_service permissive=1 [ 3.363036] [ 3.588102] libprocessgroup: Failed to mount blkio cgroup: No such file or directory [ 3.599356] libprocessgroup: Failed to mount cpuset cgroup: No such device [ 3.608821] libprocessgroup: Failed to mount schedtune cgroup: No such file or directory [ 4.225999] init: property 'ro.bionic.2nd_arch' doesn't exist while expanding '/dev/cpu_variant:${ro.bionic.2nd_arch}' [ 4.238250] init: property 'ro.bionic.2nd_arch' doesn't exist while expanding '/dev/cpu_variant:${ro.bionic.2nd_arch}' [ 4.311347] FAT-fs (mmcblk0p15): bogus number of reserved sectors [ 4.764747] init: setpgid failed for console: Operation not permitted console:/ $ [ 5.595752] apexd: Failed to walk /product/apex : Can't open /product/apex for reading : No such file or directory [ 5.622440] apexd: Failed to activate packages from /product/apex : Failed to scan /product/apex : Can't open /product/apex for reading : No such file or directory [ 7.615609] init: Init cannot set 'dev.mnt.blk.sbin..magisk.worker.system.bin.bootstrap' to 'dm-0': Illegal property name [ 7.644380] init: Init cannot set 'dev.mnt.blk.sbin..magisk.worker.system.bin.hw' to 'dm-0': Illegal property name [ 7.718771] init: Init cannot set 'dev.mnt.blk.sbin..magisk.worker.system.etc.preferred-apps' to 'dm-0': Illegal property name [ 7.731862] init: Init cannot set 'dev.mnt.blk.sbin..magisk.worker.system.etc.selinux' to 'dm-0': Illegal property name [ 7.744060] init: Init cannot set 'dev.mnt.blk.sbin..magisk.worker.system.etc.permissions' to 'dm-0': Illegal property name ^C 130|console:/ $ [ 8.140926] init: property 'dev.mnt.blk.data' doesn't exist while expanding '/sys/fs/f2fs/${dev.mnt.blk.data}/cp_interval' [ 8.191185] init: couldn't write 2178 to /dev/cpuset/camera-daemon/tasks: No such file or directory [ 8.336691] init: Failed to bind socket 'pdx/system/vr/display/client': No such file or directory [ 8.413112] init: Failed to bind socket 'pdx/system/vr/display/manager': No such file or directory [ 8.452550] init: Failed to bind socket 'pdx/system/vr/display/vsync': No such file or directory Gatekeeper_TA_CreateEntryPoint ^C 130|console:/ $ ^C 130|console:/ $ [ 8.939412] selinux: avc: denied { set } for property=sys.sensors pid=2187 uid=1000 gid=1000 scontext=u:r:hal_sensors_default:s0 tcontext=u:object_r:system_prop:s0 tclass=property_service permissive=1 [ 8.939412] [ 9.104904] init: couldn't write 2260 to /dev/cpuset/camera-daemon/tasks: No such file or directory [ 9.318897] init: Failed to open file '/d/mmc0/mmc0:0001/ext_csd': No such file or directory Edited August 8 by Randlin 0 Quote
Hiến Dương Posted August 9 Posted August 9 Hi everyone. This is my X96-Q mainboard running H313 and AXP313A. I'm new, I want to install Armbian light server version to run embedded linux (Just need network port, wifi, usb) which version can I use? And how to install on emmc? Thanks everyone! 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.