markst

I have a X88 pro 10 box with a RK3318 chip. I have installed Armbian_22.05.0-trunk_Rk3318-box_bullseye_current_5.15.35_minimal.img using the Multitool to the internal eMMC. This Installation worked fine. Question#1 I'm having a problem rebooting. If I use at the cli 'sudo reboot' the box will not reboot. If I physically power cycle the box it reboots ok. After installing I used the following that i found in the forums 'sudo apt-mark hold linux-image-current-rockchip64 linux-dtb-current-rockchip64' then i updated with apt-get update and apt-get upgrade Is anyone having the cannot reboot problem. Anyone have a fix? Question #2 When the box initially boots there is a delay form the time I plug in the power till the time Armbian starts its onscreen load of the OS. This time seems long. Can i somehow shorten this?

Thank you all I tested Armbian 22.02 - Ubuntu Jammy (beta) desktop [xfce] - mainline kernel 5.15.23 -- WORKING -- WIFI (LG642 WIFI chip) Boot from SD-card Flash SD to eMMC (using armbian-config) Updates (with Linux image and kernel headers as hold) -- POTENTIAL PROBLEM -- Boot from eMMC working BUT (with no SD-Card installed) - Slow initial start before anything on screen. About 13 seconds from power plugged in to the first text on screen. Then normal boot -- NOT WORKING -- RAM size not correct image sees 2gb but board is 4gb Front LEDs (completely blank) dmesg

Amazing. I will test and get back. Thanks

Well that is too bad. Oh well hopefully in the future there is an answer. Thank You @jock for your time on this. Keep up the good work

Thanks for looking at that. I did successfully get WIFI to work on that board under Android 11. dmesgdmesg.0dpkg.logbootstrap.log

Thanks for looking at that. I did successfully get WIFI to work on that board under Android 11. Can you point me in the right direction to get the dmesg logs As for the image on SD it flashed successfully to the card but will not boot.

Here is a google drive with the original firmware. It is Android 11. Thank you for looking at this @jock https://drive.google.com/file/d/18R2nMtjvPvxD18Xf9_bVmweSHnD2Z7os/view?usp=sharing I have a second question about the Multitool. I did an install on a box that I customized and then backed up via the Multitool. I can then put it back on the box using Multitool recover backup. This works fine. But is there a way to put the backup image on an sd card and then boot off the sd card? I tried flashing the backup file with Etcher to another sd but it will not boot.

This is the other WIFI chip. It is working correctly. In rk3318-config it is NOT recognized but is working in nmtui. I can connect successfully to WIFI. "No WIFI chip has been detected"

I need help with WIFI. I have a few X88 PRO 10 (4GB RAM 64GB ROM RK3318) that I purchased from the same Amazon seller. Unfortunately the seller must source from different suppliers as they are not all the same. Some have a SP6330 WIFI chip and this works fine. But others have a LG642 WIFI chip that is NOT working. The LG642 WIFI chip looks to have the same manufacturer marking on it as the Sp6330 (a sun). When using the rk3318-config (running it 2 times with reboot) I get the following. But WIFI will not connect. Wifi device: Broadcom BCM4334/AmPak AP6334 - Device ID: 02d0:4334 In armbianEnv.txt I have the following: verbosity=1 bootlogo=false overlay_prefix=rockchip fdtfile=rockchip/rk3318-box.dtb rootdev=UUID=xxxxxxxxxxxxxxxxxxxxxxxx rootfstype=ext4 console=both overlays=rk3318-box-wlan-ext rk3318-box-led-conf2 rk3318-box-wlan-ap6330 usbstoragequirks=0x2537:0x1066:u,0x2537:0x1068:u I started with Armbian 22.02 - Ubuntu Jammy (beta) desktop [xfce] - mainline kernel 5.15.17 - 2022-01-29

With help form everyone here I now have everything working with the x88 pro 10. Using the image Armbian 21.11 - Debian Bullseye desktop [xfce] - mainline kernel 5.15.2 WIFI works Display resolution works I could not get rockchip drivers to work with startx/Xsession and Armbian 21.11 - Debian Bullseye minimal - mainline kernel 5.15.2 WIFI NO display resolution NO One question? I cannot figure out how to autologin to the Desktop GUI. The system boots and waits at the login screen with the username. Where is the autologin setting?? EDIT Found the answer to my own question /etc/lightdm/lightdm.conf uncomment autologin-user=username #replace with your username autologin-user-timeout=0

How can I force the resolution on these boards? My board is RK3318 (x88 pro 10) The board is not automatically getting the maximum resolution the HDMI monitor can show. Is Armbian preventing this somewhere? Can I set this somewhere I am no expert. Any help would b appreciated. u-boot? armbianEnv.txt?

How can I force the resolution on these boards? My board is RK3318 (x88 pro 10) The board is not automatically getting the maximum resolution the HDMI monitor can show. Is Armbian preventing this somewhere? Can I set this somewhere I am no expert. Any help would b appreciated. u-boot? armbianEnv.txt?

Another day, another Board. I now have a few of these boards. x88 pro m10 4GB RAM 64GB ROM 1 . Installed to eMMc --- Armbian 21.11 - Debian Bullseye minimal - mainline kernel 5.15.2 Build date: 2021-11-12 WORKED NO PROBLEM 2. Try to get WIFI working. NOT WORKING running rk3318-config but it indicates "No WIFI chip has been detected". I go through the menus and try each option rk3318-box-led-conf1 - rk3318-box-led-conf2 - rk3318-box-led-conf3 and generic then reboot each time. No luck No WIFI and No leds. In file /boot/armbianEnv.txt there is overlays=rk3318-box-wlan-ext Any ideas?

As a lazy human I just read the first part and jumped in. My bad

@jockMy following comment in no way is me blaming you or the Armbian project. But I installed the wrong image with the thought that "Technically, rockchip devices cannot be bricked" as you commented in post Posted April 16. Maybe you can reword this for others if they try too. And again I DO NOT put any blame on you. You are doing amazing work here! You did start the post as you should with "DISCLAIMER (PLEASE READ): everything you can find in this thread (binaries, texts, code snippets, etc...) are provided AS-IS and are not part of official Armbian project. For this reason not people from Armbian project nor myself are responsible for misuse or loss of functionality of hardware." Mark