59 59
balbes150

Armbian for Amlogic S9xxx kernel 5.x

Recommended Posts

Hi,

 

I've just setup armbian to run from sdcard on a NexBox a95x-B7N (s905x, 2G Ram, 8G Rom).

 

Running a minimal install for desktop (server image + Xorg, openbox and tools I use installed manually).

 

My issue is the X server runs at 1080p while hooked via HDMI to a 1440p@60 display (Dell P2416D).

xrandr does not detect any higher resolution than 1080p, and the edid doesn't show any either:

 

~$ edid-decode  /sys/devices/platform/soc/d0100000.vpu/drm/card0/card0-HDMI-A-1/edid
EDID version: 1.3
Manufacturer: DEL Model a0c3 Serial Number 808797781
Made in week 43 of 2015
Digital display
Maximum image size: 53 cm x 30 cm
Gamma: 2.20
DPMS levels: Standby Suspend Off
RGB color display
First detailed timing is preferred timing
Display x,y Chromaticity:
  Red:   0.6533, 0.3310
  Green: 0.2958, 0.6210
  Blue:  0.1484, 0.0517
  White: 0.3134, 0.3291
Established timings supported:
  720x400@70Hz 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz
  640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
  640x480@75Hz 4:3 HorFreq: 37500 Hz Clock: 31.500 MHz
  800x600@60Hz 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz
  800x600@75Hz 4:3 HorFreq: 46900 Hz Clock: 49.500 MHz
  1024x768@60Hz 4:3 HorFreq: 48400 Hz Clock: 65.000 MHz
  1024x768@75Hz 4:3 HorFreq: 60000 Hz Clock: 78.750 MHz
  1280x1024@75Hz 5:4 HorFreq: 80000 Hz Clock: 135.000 MHz
Standard timings supported:
  1280x800@60Hz 16:10
  1680x1050@60Hz 16:10 HorFreq: 64700 Hz Clock: 119.000 MHz
  1920x1200@60Hz 16:10 HorFreq: 74000 Hz Clock: 154.000 MHz
  1152x864@75Hz 4:3 HorFreq: 67500 Hz Clock: 108.000 MHz
  1600x1200@60Hz 4:3 HorFreq: 75000 Hz Clock: 162.000 MHz
  1280x1024@60Hz 5:4 HorFreq: 64000 Hz Clock: 108.000 MHz
  1920x1080@60Hz 16:9
Detailed mode: Clock 241.500 MHz, 527 mm x 296 mm
               2560 2608 2640 2720 hborder 0
               1440 1443 1448 1481 vborder 0
               +hsync -vsync 
               VertFreq: 59 Hz, HorFreq: 88786 Hz
Serial number: 6RC2C5AJ05FU
Monitor name: DELL P2416D
Monitor ranges (GTF): 49-86Hz V, 29-113kHz H, max dotclock 280MHz
Has 1 extension blocks
Checksum: 0x1d (valid)

CTA extension block
Extension version: 3
31 bytes of CTA data
  Video data block
    VIC  16 1920x1080@60Hz 16:9 (native) HorFreq: 67500 Hz Clock: 148.500 MHz
    VIC   5 1920x1080i@60Hz 16:9  HorFreq: 33750 Hz Clock: 74.250 MHz
    VIC   4 1280x720@60Hz 16:9  HorFreq: 45000 Hz Clock: 74.250 MHz
    VIC   3 720x480@60Hz 16:9  HorFreq: 31469 Hz Clock: 27.000 MHz
    VIC   2 720x480@60Hz 4:3  HorFreq: 31469 Hz Clock: 27.000 MHz
    VIC   7 1440x480i@60Hz 16:9  HorFreq: 15734 Hz Clock: 27.000 MHz
    VIC  22 1440x576i@50Hz 16:9  HorFreq: 15625 Hz Clock: 27.000 MHz
    VIC   1 640x480@60Hz 4:3  HorFreq: 31469 Hz Clock: 25.175 MHz
    VIC   6 1440x480i@60Hz 4:3  HorFreq: 15734 Hz Clock: 27.000 MHz
    VIC  17 720x576@50Hz 4:3  HorFreq: 31250 Hz Clock: 27.000 MHz
    VIC  18 720x576@50Hz 16:9  HorFreq: 31250 Hz Clock: 27.000 MHz
    VIC  21 1440x576i@50Hz 4:3  HorFreq: 15625 Hz Clock: 27.000 MHz
    VIC  19 1280x720@50Hz 16:9  HorFreq: 37500 Hz Clock: 74.250 MHz
    VIC  20 1920x1080i@50Hz 16:9  HorFreq: 28125 Hz Clock: 74.250 MHz
    VIC  31 1920x1080@50Hz 16:9  HorFreq: 56250 Hz Clock: 148.500 MHz
    VIC  32 1920x1080@24Hz 16:9  HorFreq: 27000 Hz Clock: 74.250 MHz
  Audio data block
    Linear PCM, max channels 2
      Supported sample rates (kHz): 48 44.1 32
      Supported sample sizes (bits): 24 20 16
  Vendor-specific data block, OUI 000c03 (HDMI)
    Source physical address 1.0.0.0
  Speaker allocation data block
    Speaker map:
      FL/FR - Front Left/Right
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 148.500 MHz, 527 mm x 296 mm
               1920 2008 2052 2200 hborder 0
               1080 1084 1089 1125 vborder 0
               +hsync +vsync 
               VertFreq: 60 Hz, HorFreq: 67500 Hz
Detailed mode: Clock 74.250 MHz, 527 mm x 296 mm
               1920 2008 2052 2200 hborder 0
                540  542  547  562 vborder 0
               +hsync +vsync interlaced 
               VertFreq: 60 Hz, HorFreq: 33750 Hz
Detailed mode: Clock 74.250 MHz, 527 mm x 296 mm
               1280 1390 1430 1650 hborder 0
                720  725  730  750 vborder 0
               +hsync +vsync 
               VertFreq: 60 Hz, HorFreq: 45000 Hz
Detailed mode: Clock 27.000 MHz, 527 mm x 296 mm
                720  736  798  858 hborder 0
                480  489  495  525 vborder 0
               -hsync -vsync 
               VertFreq: 59 Hz, HorFreq: 31468 Hz
Detailed mode: Clock 197.000 MHz, 527 mm x 296 mm
               2048 2400 2616 2752 hborder 0
               1152 1187 1192 1195 vborder 0
               -hsync +vsync 
               VertFreq: 59 Hz, HorFreq: 71584 Hz
Checksum: 0x4d (valid)

 

Yet, I know for a fact the monitor works perfectly at 1440p over HDMI (linux desktop connected to it works at proper resolution).

 

What am I missing ?

Any hardware limitations I am not aware of ?

Any hints where to look at or how to setup the resolution at2560x1440@60 ?

 

Thanks a lot !

Share this post


Link to post
Share on other sites
2 hours ago, ElTeide said:

Any hints where to look at or how to setup the resolution at2560x1440@60 ?

 

You could try adding it manually. Here and example:
 

Add display resolution
----------------------
cvt 2560 1440 60                                                                                           Select the display resolution you want
# 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz
Modeline "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync

xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync         Add resolution, everything after Modeline from cvt is copied after newmode

xrandr --addmode HDMI-1 2560x1440_60.00                                                                    Add the new resolution to your display

xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync && xrandr --addmode HDMI-1 2560x1440_60.00 

 

Share this post


Link to post
Share on other sites

Hi NicoD !

 

Thanks for your suggestion.

 

Tried that, but it fails to apply the new mode: screen blanks for a couple of seconds then xrandr spits an error "configure crtc 0 failed" :

 

~$ cvt 2560 1440 60
# 2560x1440 59.96 Hz (CVT 3.69M9) hsync: 89.52 kHz; pclk: 312.25 MHz
Modeline "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync
~$ xrandr --newmode "2560x1440_60.00"  312.25  2560 2752 3024 3488  1440 1443 1448 1493 -hsync +vsync
~$ xrandr --addmode HDMI-1 "2560x1440_60.00" 
~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 3840 x 2160
HDMI-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1200     59.95  
   1920x1080     60.00*   60.00    50.00    59.94    24.00    23.98  
   1920x1080i    60.00    60.00    50.00    59.94  
   1600x1200     60.00  
   1680x1050     59.88  
   1280x1024     75.02    60.02  
   1280x800      59.91  
   1152x864      75.00  
   1280x720      60.00    60.00    50.00    59.94  
   1024x768      75.03    60.00  
   800x600       75.00    60.32  
   720x576       50.00    50.00  
   720x480       59.94    59.94    59.94  
   640x480       75.00  
   2560x1440_60.00  59.96  
~$ xrandr --output HDMI-1 --mode 2560x1440_60.00
xrandr: Configure crtc 0 failed
~$ 

Any ideas ?

 

[edit 2020/16] tried with many other refresh rates and even copying the modeline data from my desktop while hooked to the same display: same error.

Starting to wonder whether this a95x's s905x is really capable of outputing any resolution beyond 1080p.... ??

Share this post


Link to post
Share on other sites
On 2/9/2020 at 5:50 PM, almotra said:

Hello,

With version 5.5, on my x96mni the command ./install.sh does not work.
On version 5.3, it works.
why it does not work in 5.5?
I can't find exlinux.conf and uEnv.ini, what should I change? just uEnv.txt ???

Nobody to answer me ????

Share this post


Link to post
Share on other sites

@balbes150 I tried to install it on a s10 tv box, has a s913,  3gb ram 1gb lan. I was able to get working letting the auto-selection find on dtb (selected vim2). 
But I wanted to work using the original dtb files, I got the original firmware dtb, but it's does but.  this is the dts https://gist.github.com/nmocruz/a0baaf537808335ddc8bab2042131624

 

there's any reason why it fails?
I don't have a way to debug uart because the board has not pins, I has to solder something or what in the middle of mainboard

Share this post


Link to post
Share on other sites

@Nuno Cruz - the original dtb is for android and most probably for another kernel version too, so there is no way to make it work without a lot of adaption work

Share this post


Link to post
Share on other sites
22 minutes ago, hexdump said:

@Nuno Cruz - the original dtb is for android and most probably for another kernel version too, so there is no way to make it work without a lot of adaption work

@hexdump Got it. There's a generic dtb for this s912 3rb ram 1 gb ethernet. It's possible  to get from the original dts information missing on this? 
 

I'm not expert to edit this dts files, but I would like to compile the ogirinal without any setting that is causing this compatitiblity issue

Share this post


Link to post
Share on other sites

@Nuno Cruz - it is sometimes possible to extract some information from the original dtb and use it to adjust a mainline one, but its not easy and not always possible ...

Share this post


Link to post
Share on other sites
8 hours ago, hexdump said:

@Nuno Cruz - it is sometimes possible to extract some information from the original dtb and use it to adjust a mainline one, but its not easy and not always possible ...

 

Cool, I gonna try that approach,  use the vim2 dts to compile with bit from the original dts if needed

Share this post


Link to post
Share on other sites
On 8/25/2019 at 11:20 AM, balbes150 said:

The new version Armbiam 20190825 kernel 5.3.0. In this version the temperature display on G12 works.

For reasons not yet clear, the G12 has a conflict with this kernel with PULSEAUDIO. To turn the sound on models with G12 (s905x2 S922x a311d) you need to perform these steps.

1. Remove package "pulseaudio".

2. Reboot the system.

3. Once run the command "sudo /root/g12_sound.sh".

When you remove the pulseaudio package, not volume control.

Alternatively, you can install the "pnmixer" package that works with ALSA.

 

Khadas VIM3 and Ugoos AM6

Full-screen 1080p video playback from Youtube (Chromium) to works at a temperature no higher than 55 (without a fan). :)

 

 

 

 

I did as specified in this post and got the hdmi audio working. Though it only worked after I set the hdmi output to i2c in the alsamixer.

I could reinstall pulseaudio after that without problem.

BUT the analog audio sitll not working (by analog audio I mean the aundio on the AV jack, the one that cames along with the analog video signal).

I allready tried every possible combination on the alsamixer but to no avail.

I really need to that working because I want to use the box with an old analog TV. 

 

My box is an X92 (S912) [2Gb RAM]. 
The image I'm currently running is Armbian_20.05.0_Arm-64_focal_current_5.6.0-rc4_desktop_20200306.img.

 

Any idea what else can I try?

Share this post


Link to post
Share on other sites
(edited)

Hi, 

 

How do I flash this image to a MicroSD card?

With previous armbian image, after flashing I have a BOOT partition for me to edit the uEnv.ini

but with this image Armbian_20.02.0-rc1.037_Aml-s9xxx_bionic_current_5.5.0-rc6_20200205.img.xz

after flashing using balenaEtcher or Rufus, I can't seem to find the BOOT partition?

 

Thanks. 

 

Edit:

Ok, the image needs to be unpacked first and use Rufus. balenaEtcher doesn't work

Edited by rampagepi

Share this post


Link to post
Share on other sites

How do I config this build to run from MicroSD card on H96 Pro Plus?

 

The old version I had runs fine, but this new build won't boot by default. 

 

Old version uEnv.ini

 

dtb_name=/dtb/meson-gxm-khadas-vim2.dtb
bootargs=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

Old version extlinux.conf

LABEL Armbian
  LINUX /zImage
  INITRD /uInitrd
  FDTDIR /dtb
#  FDT /dtb/meson-gxm-khadas-vim2.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 

 

With this new build, for the uEnv.ini

it is 

# aml s9xxx

FDT=/dtb/amlogic/meson-g12b-odroid-n2.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

 

 

Share this post


Link to post
Share on other sites
1 hour ago, rampagepi said:

dtb_name=/dtb/meson-gxm-khadas-vim2.dtb

 

1 hour ago, rampagepi said:

FDT=/dtb/amlogic/meson-g12b-odroid-n2.dtb

 

Do you notice anything strange that you are trying to use in the new version ?

Share this post


Link to post
Share on other sites

Actually I've tried both 

 

FDT=/dtb/amlogic/meson-gxm-khadas-vim2.dtb

 

and 

 

dtb_name=/dtb/amlogic/meson-gxm-khadas-vim2.dtb

 

in uEnv.ini with the new build, but it won't boot. 

So what should it be?

Share this post


Link to post
Share on other sites
3 hours ago, rampagepi said:

So what should it be?

New versions do not have the file uEnv.ini. To work with new versions, the universal multiload must be updated using the image you are trying to use.

 

Share this post


Link to post
Share on other sites

Cool. 

 

The first floor in this topic mentioned both universal multi-boot is required and uEnv.ini, it's a bit confusing. 

Maybe this part should be removed or commented out?

Quote

Major change. A new algorithm for the use of the dtb. Starting with this version, you no longer need to copy the dtb files and rename it to "dtb.img." In order to specify which dtb file to use, you need to edit the file 'uEnv.ini" (specify the desired file name for use dtb). This is a plain text file and can be easily edited. This change will make it easy to update the kernel from the "deb" file in the future. The new algorithm is now used in the eMMC system installation script.

 

I read your topic about activate universal multi-boot again, 

Quote

option A

- Connect the prepared media to the device and turn on the power, boot into Android
- Open the app "Update&Backup"
- Click on "Select" local update and chose the file on the removable media aml_autoscript.zip
- Start "Update"
- System will reboot twice and start running the system from external media.

 

option B

-  try using the "toothpick method"

 

However my tv box's Android is corrupted, it won't boot or restored or recovered. So option A is not for me. 

Tried option B, but it won't boot with the new build on the MicroSD card. 

:(

Share this post


Link to post
Share on other sites
26 minutes ago, rampagepi said:

Tried option B, but it won't boot with the new build on the MicroSD card. 

Show the contents of the file (uEnv.txt)

Share this post


Link to post
Share on other sites

How do you get to the desktop mode? ive tried startx that doesnt work.

Share this post


Link to post
Share on other sites

I try to install to eMMc over the script install-aml.sh - without any errors - then i shutdown the box put the microsd card out and try a boot - black screen ....if i put the microsd back into that device and boot again - it will boot over microsd card 

 

any idea ? what have I done wrong?
how do i access the emmc, do i have to adapt the dtb again? 

Share this post


Link to post
Share on other sites
4 minutes ago, khiro1337 said:

any idea ? what have I done wrong?
how do i access the emmc, do i have to adapt the dtb again? 

Wait for psychics who will guess what model you have, what image, what steps you take, and so on.

Share this post


Link to post
Share on other sites
51 minutes ago, balbes150 said:

Wait for psychics who will guess what model you have, what image, what steps you take, and so on.

Armbian_20.02.0-rc1.038_Aml-s9xxx_bullseye_current_5.5.0-rc6_20200205

and a F1 A95X with S905W (Before Copy to eMMc - Android 8.1)

 

 

Only the script install-aml.sh - i use the p281 dtb file on the microsd 

Share this post


Link to post
Share on other sites
2 hours ago, balbes150 said:

Show the installation script log.

 

Where can i find it? 

 

Your script write no log file ... :

 

 

 

Share this post


Link to post
Share on other sites
3 minutes ago, khiro1337 said:

Where can i find it? 

When running, the script displays information on the screen. I need this conclusion.

Share this post


Link to post
Share on other sites
1 hour ago, balbes150 said:

When running, the script displays information on the screen. I need this conclusion.

 


root@LBOX:~# bash install-aml.sh
Start script create MBR and filesystem
/dev/mmcblk1
Start backup u-boot default
4+0 records in
4+0 records out
4194304 bytes (4.2 MB, 4.0 MiB) copied, 0.816897 s, 5.1 MB/s
Start create MBR and partittion
Start restore u-boot
442+0 records in
442+0 records out
442 bytes copied, 0.00973483 s, 45.4 kB/s
8191+0 records in
8191+0 records out
4193792 bytes (4.2 MB, 4.0 MiB) copied, 0.536154 s, 7.8 MB/s
Done
Start copy system for eMMC.
Formatting BOOT partition...mkfs.fat 4.1 (2017-01-24)
done.
Cppying BOOT...done.
Edit init config...done.
Formatting ROOT partition...
/dev/mmcblk1p2 contains a ext4 file system labelled 'ROOT_EMMC'
        last mounted on /ddbr/install on Tue Mar 31 21:19:53 2020
e2fsck 1.45.6 (20-Mar-2020)
ROOT_EMMC: clean, 11/895840 files, 82870/3583232 blocks
done.
Copying ROOTFS.
Copy BIN
Create DEV
Copy ETC
Copy HOME
Copy LIB
Create MEDIA
Create MNT
Copy OPT
Create PROC
Copy ROOT
Create RUN
Copy SBIN
Copy SELINUX
Copy SRV
Create SYS
Create TMP
Copy USR
Copy VAR
Copy fstab
*******************************************
Complete copy OS to eMMC
*******************************************
 

Share this post


Link to post
Share on other sites

I don't see any critical errors. Try waiting 5-7 minutes for the first launch. Or try using a different DTB.

 

Share this post


Link to post
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
59 59