tpc010

Hi, I build a new Image, q88_a33_tablet_1024x600_defconfig is not booting but q8_a33_tablet_1024x600_defconfig is working on my YUNTAB. The compressed Image is around 250MB, without Desktop. Do you have a storage where I can put the image file? You only have to add the file pwm.conf to /etc/modprobe.d/ br pwm.conf

Important is the correct defconfig for the tablet, you have to test some of them. The only thing I changed was the BOOTCONFIG line and add the g_serial to the modules for OTG USB (and wifi modules) check if there is a newer or different version in u-boot armbian/cache/sources/u-boot/v2018.XX/configs$ ls -1 *[Aa]33* A33-OLinuXino_defconfig q88_a33_tablet_1024x600_defconfig q8_a33_tablet_1024x600_defconfig q8_a33_tablet_800x480_defconfig Sinlinx_SinA33_defconfig

Hi, sorry for the late response, do you blacklisted the pwm module? Otherwise the screen will go black. "echo blacklist pwm_bl>/etc/modprobe.d/pwm.conf" Do you have some last messages before the kernel stuck? At the moment I have no time to build a clean Image, sorry. I hope next week. br

Tablets like this, I bought it at ebay with broken Touch for testing, also a broken 10,1" Tablet, this was also working for testing, and an A88S from alldaymall. Wifi is also working, but this can change from tablet to tablet. Yuntab Q88H - 7 Zoll Tablet PC，Android 4.4, Quad Core, HD 1024x600, Dual-Kamera, Bluetooth, Wi-Fi, 8GB https://www.amazon.de/dp/B01IJRDGGK

Hi Markbirss, I checked it again with current build and it's working with module "g_serial" add to boards/lime-a33.conf config/boards/a33-q8-tablet2.conf # A33 quad core 1Gb SoC BOARD_NAME="q8 A33" BOARDFAMILY="sun8i" # depending of board and resolution use a defconfig file from sources/u-boot/v2018.05/configs BOOTCONFIG="q8_a33_tablet_1024x600_defconfig" #MODULES="hci_uart gpio_sunxi rfcomm hidp bonding spi_sun7i 8021q a20_tp" MODULES="hci_uart gpio_sunxi rfcomm hidp bonding spi_sun7i 8021q a20_tp g_serial gslx680 gc0312 gc2145 rtl8150" MODULES_NEXT="hci_uart gpio_sunxi rfcomm hidp bonding spi_sun7i 8021q a20_tp g_serial gslx680 gc0312 gc2145 rtl8150" OVERLAY_PREFIX="sun8i-a33" # KERNEL_TARGET="next" CLI_TARGET="stretch:next" DESKTOP_TARGET="" # RECOMMENDED="Debian_stretch_next:75" ~/armbian/cache/sources/u-boot/v2018.05/configs$ ls -1 *[Aa]33* A33-OLinuXino_defconfig q88_a33_tablet_1024x600_defconfig q8_a33_tablet_1024x600_defconfig q8_a33_tablet_800x480_defconfig Sinlinx_SinA33_defconfig I had to disable the pwm_bl module, otherwise the screen will go black while boot. echo blacklist pwm_bl>/etc/modprobe.d/pwm.conf I checked it with some Allwinner A33 Tablets from eBay or Amazon, the touch isn't working at the moment, but I hope I have time to check it in the future.

UPDATE: Today I build it again and now it's working, I think someone has change something. Thank you :-) OLD: I created an new board, based on the lime-a33.conf with BOOTCONFIG="q8_a33_tablet_1024x600_defconfig" and build a Debian Stretch Image with mainline Kernel 4.13 / 4.14. The SD Card is booting with a nice screen output but only to Kernel Boot, then the screen freezes. The Serial connection is only in the SD Adapter and I cant use it if I'm booting from it, or is there a possibility ?? I was checking devuan.org and this Image is booting the Tablet, with Kernel 4.1x. So I want to debug the Armbian Kernel with serial output and I used fastboot for it, I'm booting into fastboot with "adb reboot bootloader" and then I'm sending the bootimage with fastboot ( first I created a image with mkimage with and without dtb file) fastboot -c "console=ttyS0,115200" boot uImage But I get this error from armbian Kernel Starting kernel ... Uncompressing Linux... done, booting the kernel. Error: unrecognized/unsupported machine ID (r1 = 0x00001029). Available machine support: ID (hex) NAME ffffffff Generic DT based system ffffffff Allwinner sun9i Family ffffffff Allwinner sun8i Family ffffffff Allwinner sun7i (A20) Family ffffffff Allwinner sun6i (A31) Family ffffffff Allwinner sun4i/sun5i Families Please check your kernel config and/or bootloader. Full Log is attached. I checked a lot of things, but I can't find a solution to solve this problem, the devuan.org Kernel is booting this way, until it can't find the SD Card. Thanks for your Help log1.txt

Hi, I also created a Image with the current armbian git builder and it's working, eth0 is working, wlan is not important at the moment. Great work, thank you.

Hi sukamine, I'm using Ethernet, so I don't need Wifi, sorry, but if I have time I will check it. br tpc010

Hello Jefken3, you have to open the Box and search for the Nand or EMMC Flash, then figure out which pins you have to shorten to recover over USB OTG, the Mini M8S has also only full size USB, one of them has OTG. See this for more informations http://freaktab.com/forum/tv-player-support/amlogic-based-tv-players/s905/tronsmart-ac/firmware-roms-tools-at/565449-running-linux-from-sd-card-or-usb-flash-drive-using-balbes150-method-and-files/page13 br Tpc01

Ok sorry, it was to late :-) nographics 1 user@odroidc2:~$ free -m total used free shared buffers cached Mem: 1976 174 1801 6 9 78 -/+ buffers/cache: 86 1889 Swap: 127 0 127 nographics 0 user@odroidc2:~$ free -m total used free shared buffers cached Mem: 1782 317 1464 6 14 97 -/+ buffers/cache: 206 1576 Swap: 127 0 127

Youre welcome, with screenoutput it needs around 330MB Memory after boot and without screen around 150MB after boot, you have to rebuild the autoscript file, don't change it directly in the compiled file. I don't know about Ubuntu on this system, but I think you can test it, now you have all informations to do it.

Hi, here is a short howto to boot Armbian on Mini M8S from SD Card. You have to change the u-boot environment to check the SD-Card and then start a autoscript script. To boot the Armbian image you have to change some files from Armbian, change all mmcblk0 to mmcblk1 in file /etc/fstab /etc/init.d/firstrun /etc/init.d/resize2fs You need the file boot-s905.txt and have to convert it to autoscript, the Mini M8S u-boot can't work with Armbians u-boot boot.ini. setenv cec "cecf" setenv mesontimer "0" setenv nographics "0" setenv condev "console=ttyS0,115200n8 console=tty0 consoleblank=0" setenv verbosity "255" setenv bootargs "root=/dev/mmcblk1p2 rootwait rootflags=data=writeback rw ${condev} no_console_suspend hdmimode=${hdmimode} m_bpp=${display_bpp} fsck.repair=yes loglevel=${verbosity} net.ifnames=0" setenv initrd_loadaddr "0x13000000" fatload mmc 0:1 ${initrd_loadaddr} uInitrd fatload mmc 0:1 ${loadaddr} zImage fatload mmc 0:1 ${dtb_mem_addr} dtb/meson8_Mini-M8S.dtb fdt addr ${dtb_mem_addr} if test "${mesontimer}" = "1"; then fdt rm /timer; fi if test "${nographics}" = "1"; then fdt rm /reserved-memory; fdt rm /aocec; fi booti ${loadaddr} ${initrd_loadaddr} ${dtb_mem_addr} Convert it with u-boot tools to autoscript. mkimage -A arm -O linux -T script -C none -d boot-s905.txt s905_autoscript Copy it to SD-Card to the boot partition, and also copy the file "meson8_Mini-M8S.dtb" the Boot partition in folder "dtb". Now open the case and connect the UART connector. Read this Howto for more informations. http://www.cnx-software.com/2015/12/06/how-to-run-headless-linux-on-amlogic-s905-devices-such-as-mini-mx-or-k1-plus/# setenv preboot "run factory_reset_poweroff_protect;run upgrade_check;run bootmode_check;run init_display;run storeargs;run upgrade_key;run user_start;run switch_bootmode;" setenv user_start "if mmcinfo; then run linux_start_mmc;fi;" setenv linux_start_mmc "if fatload mmc 0 ${loadaddr} s905_autoscript; then echo ===[LINUX START from mmc]===;autoscr ${loadaddr};fi;" saveenv After reboot the Mini M8S should boot from SD-Card. Please check the lines and be careful, an error can brake the possibility to interrupt the boot sequence. UPDATE 2016/09/08: after apt-get distupgrade, the uboot package was updated and this was rewriting the uboot data from emmc, but the Mini m8s is not working with the uboot from Hardkernels Ordroid uboot. I got this after boot: ***** Warning!! ************************************************** *** * This board have not been autorized or product keys are not valid. * * Please contact with Hardkernel or your distributor * ************************************************** ******************* After shorten the emmc at boottime, I was able to recover the stockimage via OTG USB and amlogic's windows tool, thanks to balbes150, I found a info on freaktab. So after first armbian boot from SD, you have to remove the uboot package with "apt-get remove linux-u-boot-odroidc2". boot-s905.txt s905_autoscript.gz meson8_Mini-M8S.dtb.gz

I have good news, it's working with a auto-script script, so I will finish the last environment lines for autoboot with a Armbian SD card and will post all needed information. FYI: You have to change the resolution in Android and this will set the environment, which will used from Armbian auto-script.

Yes I know, but I will insert the Tip with the startup-script, then it will work easier for all. I will only show the UART part.

Thank you, I will check it.