Jump to content

rino

Members
  • Posts

    25
  • Joined

  • Last visited

Posts posted by rino

  1. @AndrewDB

    Here the content of the fip dir:

     

    root@ubuntu-uboot-compilation:~/u-boot_dev/u-boot# $FIPDIR/blx_fix.sh fip/bl30.bin fip/zero_tmp fip/bl30_zero.bin fip/bl301.bin fip/bl301_zero.bin fip/bl30_new.bin bl30
    2172+0 records in
    2172+0 records out
    2172 bytes (2.2 kB, 2.1 KiB) copied, 0.00474344 s, 458 kB/s
    3228+0 records in
    3228+0 records out
    3228 bytes (3.2 kB, 3.2 KiB) copied, 0.00798341 s, 404 kB/s
    root@ubuntu-uboot-compilation:~/u-boot_dev/u-boot# ls -l fip
    total 876
    -rwxr-xr-x 1 root root    944 Mar 10 17:54 acs.bin
    -rwxr-xr-x 1 root root  38336 Mar 10 17:54 bl2.bin
    -rwxr-xr-x 1 root root   1112 Mar 10 17:54 bl21.bin
    -rw-r--r-- 1 root root  38788 Mar 10 17:55 bl30.bin
    -rwxr-xr-x 1 root root  10084 Mar 10 17:55 bl301.bin
    -rw-r--r-- 1 root root  13312 Mar 10 18:00 bl301_zero.bin
    -rw-r--r-- 1 root root  54272 Mar 10 18:00 bl30_new.bin
    -rw-r--r-- 1 root root  40960 Mar 10 18:00 bl30_zero.bin
    -rw-r--r-- 1 root root  99120 Mar 10 17:55 bl31.img
    -rw-r--r-- 1 root root 577516 Mar 10 17:55 bl33.bin

  2. @AndrewDB

    > By any chance are there any errors before you get to that point?

     

    At the first "make" I get 2 warnings:

     

      DTC     arch/arm/dts/meson-gxbb-nanopi-k2.dtb
      DTC     arch/arm/dts/meson-gxbb-odroidc2.dtb
      DTC     arch/arm/dts/meson-gxl-s905x-p212.dtb
      DTC     arch/arm/dts/meson-gxl-s905x-libretech-cc.dtb
      DTC     arch/arm/dts/meson-gxl-s905x-khadas-vim.dtb
    arch/arm/dts/meson-gxl-s905x-khadas-vim.dtb: Warning (avoid_unnecessary_addr_size): /gpio-keys-polled: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property
      DTC     arch/arm/dts/meson-gxm-khadas-vim2.dtb
    arch/arm/dts/meson-gxm-khadas-vim2.dtb: Warning (avoid_unnecessary_addr_size): /gpio-keys-polled: unnecessary #address-cells/#size-cells without "ranges" or child "reg" property

  3. 1 hour ago, AndrewDB said:

    Looks good. Did you have any errors this time around?

    Yes I have, always the same at the python compiled (.pyc) launch step:

     

    $FIPDIR/acs_tool.pyc fip/bl2.bin fip/bl2_acs.bin fip/acs.bin 0

     

    the error says:

    /root/u-boot_dev/blobs/amlogic-u-boot/fip/acs_tool.pyc: line 1: $'\003\363\r': command not found

    if the python source was available we can have a look into ...

     

  4. Hi @AndrewDB,

     

    in the attached file you can find what I get on the Le Potato UART console using your u-boot.bin.sd.bin.

     

    Other than that I re-execute the procedure and I got the same errors at the same point. However, ignoring the errors, and continuing I made  an "u-boot.bin.sd.bin" file. But it doesn't work (flashing it no boot) and  "diff" comand says it is different than yours. 

     

     

    console.txt

  5. @AndrewDB

    I have an error during the integration of compiled blobs into the mainline u-boot code.

     

    root@ubuntu-uboot-compilation:~/u-boot_dev/u-boot# $FIPDIR/acs_tool.pyc fip/bl2.bin fip/bl2_acs.bin fip/acs.bin 0
    /root/u-boot_dev/blobs/amlogic-u-boot/fip/acs_tool.pyc: line 1: $'\003\363\r': command not found
    /root/u-boot_dev/blobs/amlogic-u-boot/fip/acs_tool.pyc: line 2: $'\373]\372Uc\a@s*\002dd\001lZdd\001l\001Z\001dd\001l\002Z\001dd\001l\003Z\003dd\002l\004Tdd\001l\005Z\005dd\001l\006Z\006dd\001l\aZ\add\001l\bZ\bd\003Z': command not found
    : No such file or directorygic-u-boot/fip/acs_tool.pyc: line 3: de
    /root/u-boot_dev/blobs/amlogic-u-boot/fip/acs_tool.pyc: line 4: d
    d                                                                e
     : No such file or directory
    /root/u-boot_dev/blobs/amlogic-u-boot/fip/acs_tool.pyc: line 11: unexpected EOF while looking for matching ``'
    /root/u-boot_dev/blobs/amlogic-u-boot/fip/acs_tool.pyc: line 41: syntax error: unexpected end of file

     

     

  6. 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

  7. 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

     

  8. 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

     

     

     

     

  9. @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?

  10. >  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.

  11. @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).

  12. @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.

  13. 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.

  14. On debian stretch:

    Linux lepotato 4.19.8-meson64 #5.67.181210 SMP PREEMPT Tue Dec 11 00:22:25 CET 2018 aarch64 GNU/Linux

     

    and on my PA248Q ASUS 1920x1200 monitor:

    HDMI to HDMI ok (even hotplugged)

    HDMI to DVI ok but 'lazy' (required several plug/unplug reboot attempts)

    hotplug USB mouse ok

    hottplug USB keyboard NOT OK

     

    Recap of desktop usability problems I can see:

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

    -chromium windows not integrated in XFCE destop environment (top right buttons missing)

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

     

     

  15. Using kernel: Linux lepotato 4.19.7-meson64 #5.67.181207 SMP PREEMPT Fri Dec 7 10:25:31 CET 2018 aarch64 GNU/Linux

     

    HDMI it's ok on my PA248Q ASUS 1920x1200 monitor.

     

    Usability problems I can see:

    -slow windows resizing in XFCE

    -chromium windows not integrated in XFCE destop env (top right buttons missing)

    -no video acceleration in Chromium or mpv media player

    -too many flickering of mouse pointer on the desktop background.

     

     

     

×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines