Jump to content
  • 0

Le Potato / C2 / K2 4.19 LTS testing thread


TonyMac32
 Share

Question

2 changes are in queue on my workstation, one is u-boot 2018.11, the other is updating the Dev patchset and beginning to iron out 4.19 Kernel.  The first I honestly don't see any issues with moving forward, but want people to know about it, the second is a bit of a hairball and I'll need some help with debugging, and in fixing.

 

Detail of changes:

 

U-boot:  Currently Meson64 and Odroid C2 are using 2018.05 and 2018.07, respectively.  I will be moving all to 2018.11, and eliminating the "specialness" of the Odroid C2 in our build system, so Meson64 will be inheriting the C2 boot script under the "Meson64 name, it will no longer have its own u-boot patch folder/etc.  The board will finally be fully integrated into the Meson64 configuration, although it will still have the special Odroid firmware blob (all Amlogic SoC's have their own blobs, so no special changes need made to allow for the C2 to have a different one than the K2)

 

Current Concerns:

 

         packaging scripts on 4.14 kernel are not creating a symlinked named "Image" for the updated boot script.  I didn't consider that and only caught it today.  U-boot is obviously unimpressed.

 

Kernel 4.19:   This will eventually become the "Default" kernel, once it has been debugged and proven out, as Amlogic Mainline kernels can now be easily patched with full video decoder support (already done), and Mali support is available (I need to finish integrating that, later date)

 

Current concerns:

 

                -HDMI displays seem to be a sore spot, I have 1 that works flawlessly (hilariously a 7" waveshare-like HDMI), while the other needs to be plugged in after boot to work, and an HDMI-DVI adapter one is nonfunctional. (it seems to think it's attached, but no image)

                - I am getting a million "failed to change cpu frequency:    -5" errors again.  The clock marked as critical fix is in there, needs verified as it looks different than the old one.

                - I had to disable CEC entirely to get the system to boot with a display attached, it would fault, reboot, fault, etc.  Plugging in a display after boot yielded an oops.  No CEC = that problem is gone.

 

Tagging  @Neil Armstrong, for tracking if interested/have ideas.  I'm using Neil's always helpful meta-meson patchset, these were squirreled away in "next" so I assume they are not complete/some WIP, so this can be some good feedback/etc.  No one can break things like an end user.  :lol:

Link to comment
Share on other sites

Recommended Posts

  • 0
[mention=3841]Tommy21[/mention]You won't have OpenGL acceleration, but yes should be able with the actual images. With a Bionic ubuntu desktop image, you should be able to select wayland gnome at the login prompt.

Yeah, i do know it will be without OpenGL, and it will stay that way until Lima driver starts supporting it?

About Gnome, synaptic has 3.2.x version, i've read that 3.30 versions are Arm supported, and there is no way to add 3.30 gnome repo, maybe only way is to compile it from source?

Link to comment
Share on other sites

Order Armbian Linux merch!

  • 0

All of them unfortunately. They (almost*) all work on boot now after the last few patches you recommended)posted, but switching resolution is a problem on all, and hot plugging can result in only part of the screen showing output. Switch from higher to lower res results in a garbled display.

 

* The 4k display boots in 1080p with a strange interlacing pattern making only some of the desktop accessible. A plug cycle and it is fine, as long as the whole screen displays the desktop (black bar at the bottom possible seemingly at random).

 

[Edit] I will dump xrandr data from a different board arch (or maybe just older kernel) for these, the resolutions/frequencies look different than I'm used to seeing with the current Meson64.

 

Sent from my Pixel using Tapatalk

 

 

 

 

Link to comment
Share on other sites

  • 0

with Bionic:

Linux lepotato 4.19.9-meson64 #5.67.181213 SMP PREEMPT Thu Dec 13 23:45:38 CET 2018 aarch64 aarch64 aarch64 GNU/Linux
 

I also installed desktop env via armbian-config

 

and on my PA248Q ASUS 1920x1200 monitor:

HDMI to HDMI ok (even hotplugged)

HDMI to DVI ok

 

-hotplug USB mouse ok

-hottplug USB keyboard OK, better than in debian Stretch

-no CPU temp in htop

 

-slow windows resizing in XFCE (waiting for HW OpenGL acceleration by Lima project)

-chromium windows IS integrated in XFCE destop environment, better than in debian

-no video acceleration in Chromium or mpv media player (waiting for that as LibreComputers's plan)

-better low res youtube video than in debian

 

So desktop usability in bionic appears to be better than in debian Stretch.

Link to comment
Share on other sites

  • 0

@TonyMac32

trying to do what you asked for I chose:

1600*1200

but it doesn't work and that resolution put the monitor output in an inconsistent state (mirrored stripes)

Now I need to reset a working resolution via CLI in order to continue the testing. Trying to recover I had no success: I opened a virtual terminal and:

$ xrandr -q
Can't open display

 

Please, give me guidance.

Link to comment
Share on other sites

  • 0

On:

Linux lepotato 4.19.10-meson64 #5.67.181217 SMP PREEMPT Mon Dec 17 14:21:39 CET 2018 aarch64 aarch64 aarch64 GNU/Linux

ARMBIAN 5.67.181217 nightly Ubuntu 18.04.1 LTS 4.19.10-meson64

 

and on my PA248Q ASUS 1920x1200 monitor:

HDMI to HDMI ok

HDMI to DVI  NOT ok

 

So I can see a regression here.

Link to comment
Share on other sites

  • 0

@rino so you connect the same screen via HDMI and "HDMI to DVI" and only the "HDMI to DVI" fails ?

What is the resolution selected via HDMI and "HDMI to DVI" ? is that 1920x1200, 1920x1080 or 1600*1200 ?

 

On 4.19 I added a "generic" support for all monitors, but I waited for feedback to know if it failed on some monitors.

 

Let me check

Link to comment
Share on other sites

  • 0

@Neil Armstrong   

> so you connect the same screen via HDMI and "HDMI to DVI" and only the "HDMI to DVI" fails ?

That's correct I just tested it again: HDMI to HDMI works but HDMI to DVI does not. I got a blank screen and after several minutes I only obtained an unusable flashing armbian/penguin desktop background with a lot of green tone instead of the usual black one.

That's with the last bionic: ARMBIAN 5.67.181217 nightly Ubuntu 18.04.1 LTS 4.19.10-meson64.

Before, with bionic "Linux lepotato 4.19.9-meson64 #5.67.181213 SMP PREEMPT Thu Dec 13 23:45:38 CET 2018 aarch64 aarch64 aarch64 GNU/Linux", HDMI to DVI worked. It's a regression.

 

> What is the resolution selected via HDMI and "HDMI to DVI" ? is that 1920x1200, 1920x1080 or 1600*1200 ?

1920x1200, that's the default for my Asus PA248Q monitor.

 

Please explain here how to change resolution via CLI (i.e. UART console).

Link to comment
Share on other sites

  • 0

>  What did you change between the 4.19.9-meson64 and 4.19.10-meson64 kernel

 

I think nothing. In both case I started from the fresh beta bionic image and added the full desktop via armbian-config (beta bionic image has not the desktop, instead the stretch one has it).

 

I should suggest to add the desktop part to the bionic beta image because so the desktop user experience is not bad.

For example I can see  music videos in lowres from youtube with a fair user experience.

Link to comment
Share on other sites

  • 0

During the shutdown on the uart console:

 

[ 4460.137855] meson-i2s-dai meson-i2s-dai.4.auto: Unable set to set i2s description
[ 4460.227077] meson-i2s-dai meson-i2s-dai.4.auto: ASoC: can't set meson-i2s-dai.4.auto hw params: -22

Link to comment
Share on other sites

  • 0
2 hours ago, Neil Armstrong said:

4.19.9-meson64 and 4.19.10-meson64 kernel ?

Nothing, I'm not sure the mention of "regression" was discussing the minor revision number, but more likely the 4.19 kernel itself.  @rino can you confirm?

Link to comment
Share on other sites

  • 0

@TonyMac32

4 hours ago, TonyMac32 said:

Nothing, I'm not sure the mention of "regression" was discussing the minor revision number, but more likely the 4.19 kernel itself.  @rino can you confirm? 

Yes the 4.19 kernel itself.

HDMI to DVI was working when I just moved from debian to ubuntu beta images. Is this irrelevant? Are the two beta 4.19 meson kernels,  at same moment, always the same and no other element in the distro can influence HDMI to DVI functionality?

Link to comment
Share on other sites

  • 0

Other test performed. I am starting to understand better the "HDMI to DVI" working/not working laziness problem:

 

HDMI to DVI works BUT, just after the boot, I have to move the mouse to wake up the monitor and get the desktop (I usually interact with the SBC via the uart console).

 

That's with the last:

ARMBIAN 5.67.181221 nightly Ubuntu 18.04.1 LTS 4.19.11-meson64

 

 

 

 

Link to comment
Share on other sites

  • 0
On 12/16/2018 at 3:36 PM, TonyMac32 said:

@rino Thanks for the test! Could you test changing resolutions?

Sent from my Pixel using Tapatalk
 

On bionic 4.19.12-meson64 #5.67.181226:

$ xrandr -d :0 -q

Screen 0: minimum 320 x 200, current 1920 x 1200, maximum 16384 x 8192

Composite-1 connected (normal left inverted right x axis y axis)

  720x576i      50.00  

  720x480i      59.94  

HDMI-1 connected 1920x1200+0+0 (normal left inverted right x axis y axis) 546mm x 352mm

  1920x1200     59.95*+   (yes)

  1920x1080     60.00  (yes)

  1600x1200     60.00  

  1680x1050     59.88   (yes)

  1280x1024     75.02    60.02  (HDMI only)

  1440x900      59.90  (yes)

  1280x960      60.00  

  1152x864      75.00  

  1024x768      75.03    70.07    60.00  

  832x624       74.55  

  800x600       72.19    75.00    60.32    56.25  

  640x480       75.00    72.81    66.67

 

Legenda of test result:

(yes) means that HDMI to HDMI and HDMI to DVI both work

(HDMI only) means HDMI to HDMI works

no () means that HDMI to HDMI and HDMI to DVI both don't work.

 

PS

To change resolution from UART console I used for example:

$ xrandr -d :0 --output HDMI-1 --mode 1920x1080

 

Link to comment
Share on other sites

  • 0

Accelerated 4K full-screen video in vlc on Armbian Bionic 4.19 beta image of Le Potato is working.

 

How to get it:

 

-install beta image: Armbian Bionic nightly mainline kernel 4.19.y

-add desktop via armbian-config

-install vlc: $ sudo apt-get install vlc

-configure VLC:

     Tools > Preferences > Input / Codecs > Codecs > Hardware-accelerated decoding > VA-API video decoder

     Tools > Preferences > Video > Display > Output > X11 video output (XCB)

-open a 4k .mp4 video and double click on it in order to get full-screen

 

and enjoy the baylibre work on the open source graphic driver in the mainline 4.19 kernel

Link to comment
Share on other sites

  • 0

@TonyMac32 I'm getting a failure in u-boot with the latest 4.19 bionic desktop LePotato image I get from armbian.com :

Spoiler

 

Quote

GXL:BL1:9ac50e:bb16dc;FEAT:ADFC318C:0;POC:0;RCY:0;USB:0;SPI:0;CHK:A7;EMMC:400;NAND:81;SD:0;READ:0;0.0;CHK:0;
no sdio debug board detected 
TE: 1888362

BL2 Built : 11:58:42, May 27 2017. 
gxl gc3c9a84 - xiaobo.gu@droid05

set vcck to 1120 mv
set vddee to 1000 mv
Board ID = 6
CPU clk: 1200MHz
DQS-corr enabled
DDR scramble enabled
DDR3 chl: Rank0+1 @ 912MHz - PASS
Rank0: 1024MB(auto)-2T-13
Rank1: 1024MB(auto)-2T-13
DataBus test pass!
AddrBus test pass!
Load fip header from SD, src: 0x0000c200, des: 0x01400000, size: 0x00004000
New fip structure!
Load bl30 from SD, src: 0x00010200, des: 0x01100000, size: 0x0000d600
Load bl31 from SD, src: 0x00020200, des: 0x05100000, size: 0x00018400
Load bl33 from SD, src: 0x0003c200, des: 0x01000000, size: 0x00081200
NOTICE:  BL3-1: v1.0(release):3348978
NOTICE:  BL3-1: Built : 15:44:01, May 12 2017
[BL31]: GXL CPU setup!
mpu_config_enable:ok
[Image: gxl_v1.1.3221-2cfba69 2017-05-27 16:03:58 qiufang.dai@droid07]
OPS=0x84
48 38 b be a2 f0 dc eb 16 d9 1e b2 [2.241797 Inits done]
secure task start!
high task start!
low task start!
ERROR:   Error initializing runtime service opteed_fast


U-Boot 2018.11-armbian (Jan 11 2019 - 19:16:55 +0100) libretech-cc

DRAM:  2 GiB
MMC:   mmc@72000: 0, mmc@74000: 1
Loading Environment from EXT4... ** File not found /boot/boot.env **

** Unable to read "/boot/boot.env" from mmc0:1 **
In:    serial@4c0
Out:   serial@4c0
Err:   serial@4c0
[BL31]: tee size: 0
[BL31]: tee size: 0
Net:   
Warning: ethernet@c9410000 (eth0) using random MAC address - 2a:ef:31:d6:85:db
eth0: ethernet@c9410000
Hit any key to stop autoboot:  0 
switch to partitions #0, OK
mmc0 is current device
Scanning mmc 0:1...
Found U-Boot script /boot/boot.scr
3048 bytes read in 1 ms (2.9 MiB/s)
## Executing script at 1f000000
154 bytes read in 1 ms (150.4 KiB/s)
** File not found /boot/uInitrd **
** File not found /boot/Image **
** File not found /boot/dtb/amlogic/meson-gxl-s905x-libretech-cc.dtb **
libfdt fdt_check_header(): FDT_ERR_BADMAGIC
No FDT memory address configured. Please configure
the FDT address via "fdt addr <address>" command.
Aborting!
** File not found /boot/dtb/amlogic/overlay/meson-fixup.scr **
Bad Linux ARM64 Image magic!
SCRIPT FAILED: continuing...
MMC Device 2 not found
no mmc device at slot 2
starting USB...
USB0:   Register 2000140 NbrPorts 2
Starting the controller
USB XHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Device 0: unknown device
Speed: 100, full duplex
BOOTP broadcast 1

Abort
missing environment variable: pxeuuid
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/01-00-50-43-84-fb-2f
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000000
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000000
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000000
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00000
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0000
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/000
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/00
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/0
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm-meson
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default-arm
Speed: 100, full duplex
*** ERROR: `serverip' not set
missing environment variable: bootfile
Retrieving file: pxelinux.cfg/default
Speed: 100, full duplex
*** ERROR: `serverip' not set
Config file not found
=> <INTERRUPT>
=> <INTERRUPT>
=> 

 

Edited by Tido
added spoiler
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
 Share

×
×
  • Create New...