Jump to content

Recommended Posts

Posted

I am not sure if it is just me or my box. But I have noticed that my sd card tends to corrupt itself. It usually happens when I use "shutdown". On 5.7.16.

 

With 5.9rc* it happens on first boot.

 

My box is a95x f3 air. Is it just me, the Sd card or my particular box becoming defective? 

 

Has anyone else had these issues? 

Posted
On 10/2/2020 at 12:32 AM, Unicorn said:

Hi Alexx,
Always check the pinned thread on this forum:  Single Armbian image for RK + AML + AW (aarch64 ARMv8)
These instructions are in that post:

1.  Take for example this desktop.img from Sep. 24:  Armbian_20.09_Arm-64_focal_current_5.8.10_desktop.img.xz I've had really good results with 20.09 ubuntu focal & debian bullseye images.

2. now burn it to a usb with the program https://www.balena.io/etcher/
After it's done you're going to see 2 Partitions appear - you want to open the one says /BOOT.

3. Create your u-boot: Find this file: "u-boot-s905x2-s922" Copy and paste it with a new name of "u-boot.ext". It in fact works for s905x3 too.

4. Now inside /BOOT/dtb/amlogic these are your "Device Tree Binaries". Kernel uses it to detect all your hardware. The Trial and error part is finding the right one that makes your hardware work.
Scroll to the bottom you'll see 'meson-sm1-sei610.dtb'  rforcen is talking about Normally you have to copy & past .dtb files into this directory. But for now try that one! 

5. Configure your 'extlinux.conf'.  Edit /extlinux/extlinux.conf  and comment out or delete every line for other boards.  Near the end you want to uncomment FDT & APPEND for '# aml s9xxx' put in your dtb file from step 4. 

I have a very minimalist one looks like this:


LABEL Armbian
LINUX /zImage
INITRD /uInitrd

# aml s9xxx
FDT /dtb/amlogic/meson-sm1-sei610.dtb
APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0


Now All you have to is try to use a 'toothpick' to make it boot from external media! Search Google see if your box has a "Hidden" recovery button inside the Audio Jack? most do, but some have it more visibly outside. Press it with power unplugged. When you plug it in, keep holding it down until after you see your device's Logo.  I hold it about 6 sec after that. When you release it, the logo will go dark, and it's going into Armbian's boot process. Now it will reboot several times while it sets things up. Give it few minutes and you should have a running Armbian!

If this fails: try dtb files from earlier in this thread. I found almotra's list very helpful!  And try different images, try a server only image instead.

Note: Only run from external media. Do NOT try to install to eMMC yet! it will brick your device. Take a backup with `ddbr`

 

Hello Thanks for that tutorial but I have still problem. I have X96Max+ with 4GB ram and 64 GB storage, I've tried that but stuck on boot loop after X96 logo disappear.  I cna see only that it restart every ~~5secondos. Any idea how to troubleshoot what is wrong?

I have Armbian_20.10_Arm-64_buster_current_5.9.0-rc8.img. BDW can;t download your image from MEGA it is not there anymore? 

Posted

Balbes has stopped supporting the s905x3. We will need to compile it ourselves.

 

Who would like to compile it with me? Is anyone interested? Can I have a show of hands? 

Posted
17 minutes ago, Bozza said:

Balbes has stopped supporting the s905x3. We will need to compile it ourselves.

 

Who would like to compile it with me? Is anyone interested? Can I have a show of hands? 

Technically Balbes never supported the s905x3. But it is true that he is now ending support of all amlogic cpus.  I already make my own kernel builds, and since I own a few different amlogic based boxes, I have an interest in seeing support continue in some form.  I have asked balbes in another thread if he would tag his public github repositories with a tag that corresponds to his last build supporting amlogic, which then can be a starting point for continued support by the community if there is enough interest.

Posted
On 10/14/2020 at 1:11 AM, Marek Wojtaszek said:

 

Hello Thanks for that tutorial but I have still problem. I have X96Max+ with 4GB ram and 64 GB storage, I've tried that but stuck on boot loop after X96 logo disappear.  I cna see only that it restart every ~~5secondos. Any idea how to troubleshoot what is wrong?

I have Armbian_20.10_Arm-64_buster_current_5.9.0-rc8.img. BDW can;t download your image from MEGA it is not there anymore? 

latest release works for me (Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img.xz)

extlinux.conf:

------------------------------------------------------------------------------------------------------------------------

LABEL Armbian

LINUX /zImage

INITRD /uInitrd


 

FDT /dtb/amlogic/meson-g12a-x96-max.dtb

APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

------------------------------------------------------------------------------------------------------------------------

rename u-boot-s905x2-s922 to u-boot.ext

 

Posted (edited)
1 hour ago, rforcen said:

latest release works for me (Armbian_20.10_Arm-64_bullseye_current_5.9.0_desktop.img.xz)

extlinux.conf:

------------------------------------------------------------------------------------------------------------------------

LABEL Armbian

LINUX /zImage

INITRD /uInitrd


 

FDT /dtb/amlogic/meson-g12a-x96-max.dtb

APPEND root=LABEL=ROOTFS rootflags=data=writeback rw console=ttyAML0,115200n8 console=tty0 no_console_suspend consoleblank=0 fsck.fix=yes fsck.repair=yes net.ifnames=0

------------------------------------------------------------------------------------------------------------------------

rename u-boot-s905x2-s922 to u-boot.ext

 

@rforcenThanks for your advise. i do not know what I'm doing wrong. I've done this but still after x96 it starts boot loop - see video - https://photos.app.goo.gl/da1wP6ooTf4mV3qV7

Edited by Marek Wojtaszek
  • Werner locked this topic
Guest
This topic is now closed to further replies.
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines