Carlos.latour

with the sole exception of bzip2 (gzip2?) i've tried them all. (I'll try it later)

yes, 8.1, I did a lengthy search, and aside from a (4.4/kitkat, 7ci cheapo tablet) trick where the actual initrd file had a header of about 70bytes of garbage, I've found nothing. (tried doing a dump/analysis of the file to see if I could find an gzip/lz/xz etc. header within the file, but without results :-( The only idea that came to mind, was to re-create a similar version of the kernel/init etc, and import the modules from the android setup (i.e cp the /lib/modules) to ease into a clean setup. (at that point, it may be easier just to find and recompile the whole thing! )

Yes, all of them use gzip/lz etc. to decompress the initrd file, but on the files that i've tried all of them seem to be compressed with somthing else (file initrd just answer with 'data' and cpio just can't decode it. ) it is entirely possible that the file is both compressed and encrypted. (actually, quite possible) it does not appear to be an ramfs file either (at least, not a standard one. compressed or not) I seem to be able to get the kernel image fine (abooting) and a second file too, but can't decode the resulting initrd/ramfs.

It may be a waste of time, however in the case of the s905X2, all the proper drivers are already configured (granted,it's the old/buggy 4.9.xx) which helps in quickly setting up a linux mini-server. (mqtt,lamp,mysql, node-red, etc etc etc. ) As for android, if I could completely replace/remove it from most of my arm boxes I'd be a very happy man ! (try to setup an apache server under android's !)

I was thinking about doing exactly that for an A95Xpro (runs kernel 4.9.xx) the issue i've run into is the reconfiguration of the Initrd (can't seem find a way to decompress it, which seems to be required to replace init ) Really interested in the answer.

After reopening my box (m8s pro/s912x-3g) the wifi chip is an ltm8830 (it appears to be same as in the T95z ?) there are some threads on it, I'll follow up on those. As for the Ethernet, there is absolutely no joy with any of the dtb's. (tried all the gxm,gxl ) the one thing that 'tickles' me is that upon boot,(prior/during the uboot process) it shows the following: ... size: 0 Net: eth-1: ethernet@c9410000 Hit any key to stop autoboot: 1 nux/extlinux.conf .... Does it mean that's using physical interface #1 ? (instead of 0) ..again, there are some threads that indicate that's the case for the T95z .... guess I'll try making /changing the dtd.img and try.. On Another issue, after updating the u-boot.img to 2018's, I seem to no longer be able to boot 3.14 (?) perhaps i need a different version of u-boot.img for 3.14? or are there special flags to be passed ? (even tried to manually fatload/booti known-to-work files and it freezes ) Thanks for any relevant info/pointers. C.

did try all the gxm-xxxx and some of the gxl, still no joy there, I'll reopen the box and identify the actual chips. (I am however thinking that I may have blown the hardware, as the u-boot 2018 doesn't recognize and interface there ...)

Thanks Balbes, I admit I'm stumped.! I'm using meson-gxm-q201.dtb, (it's the same name as the one on 3.14) did try the q200.dtb with no success. (i'll test the gxl series, just in case.)

mind doing an 'uname -a' ? (it would appear that ,either I'm way off, or the driver for the eth is compiled in the kernel and not as a module.) thx

1 ) to get running modules .. lsmod 2) I do get an error on my setup for this one (I *think* is the phy. eth0, with different hardware) dmesg |grep ath thx! Carlos.

Ok for the wifi, guess i'll try to recompile and port the proper drivers.... (still working on my kernel compiling setup, but I'm getting there !) Would you happen to know what ethernet driver's you box is using ? (my box is an M8S Pro, 3g/s912) thx

Odd, After clearing the u-boot in the hardware (as explained above) and using an SD card, I manage to get it booting on an 4.x kernel !! Sound/video work, BUT Still have to get it to recognize eth/wifi, (amlogic/dhd modules not in the 5.75 image? or did the modules change name?) Thnx pre-boot messages: GXM:BL1:dc8b51:76f1a5;FEAT:ADFC318C:0;POC:3;RCY:0;EMMC:0;READ:0;0.0;CHK:0; TE: 95046 BL2 Built : 14:59:36, Aug 9 2017. gxl ge8c6a83 - xiaobo.gu@droid12 set vdd cpu_a to 1120 mv set vdd cpu_b to 1050 mv set vddee to 1000 mv Board ID = 10 CPU clk: 1200MHz DQS-corr enabled DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - FAIL DDR4 chl: Rank0+1 @ 1008MHz - PASS Rank0: 2048MB(auto)-2T-18 Rank1: 1024MB(auto)-2T-18 DataBus test pass! AddrBus test pass!

In my system, the memory speed messages that work are: 792Mhz (slower thant the 1008 Mhz) ... any way to pass a command to test it at 792mhz instead of 1008? Thanks! .... DDR scramble enabled DDR3 chl: Rank0+1 @ 912MHz - FAIL DDR4 chl: Rank0+1 @ 792MHz - PASS Rank0: 2048MB(auto)-2T-18 Rank1: 1024MB(auto)-2T-18 DataBus test pass! AddrBus test pass!

Any change to get a copy of the s905X2 (alpha/beta? version) for testing? (tried to compile my own, but still working on the setup...) thnx!.

Hi, I'm going NUTS here, I *did* manage to get 3.14 going but, I'm trying to boot Armbian images any of the 4.1x/5.x images onto my M8Spro (s912/3G ram) and none boot. (have console output, and tried all the images/combinations 5.4x/5.5x/5.7x of Armbian ) None boot up. they all block at 'uboot time: ?????? us. Clearly I'm doing something wrong, but where/what ? Help! Thanks! PS: Previously to the uboot message, this is shown: ## Flattened Device Tree blob at 01000000 Booting using the fdt blob at 0x1000000 libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND [rsvmem] fdt get prop fail. Loading Ramdisk to b37f9000, end b3ea107f ... OK Loading Device Tree to 000000001fff6000, end 000000001ffffa8e ... OK fdt_instaboot: no instaboot image Starting kernel ... uboot time: 6961815 us