Jump to content
New Wiki - User & Developer Guide ×

Remontoir

Members
 View Profile  See their activity

  • Content Count

    8

  • Joined

  • Last visited

Posts posted by Remontoir

  1. Posted

    We do have exactly the same issue: while using the jack output, some (we have dozen of then in the wild ) Tinkerboard S R.20 are randomly and suddenly (can be hours or days) outputing a white noise sound.

    We are also using the last TinkerOS linux release (based on debian 10.10).

    When the problem arises, there is absolutely nothing in the logs.

    When using a digital output ( either bluetooth or HDMI ) there's no such problem.

    Maybe a problem related to the DAC ?
     

  2. Posted

    Note: I've been told the above is not the serial number but the PPID (Piece Part Identification).
     

    The file /sys/firmware/devicetree/base/chosen/bootargs shows (uboot args) :

    sdwupdate storagemedia=sd androidboot.storagemedia=sd  (...) androidboot.serialno=c3d9b8674f4b94f6

    The serial number in the boot arguments is the same than the one in /sys/firmware/devicetree/base/serial-number

    Question : where does this  "serial number" comes from ? In the uboot code as a default value ?

     

  4. Posted

    We made disk-images of a modified TinkerOS for mass deployement. This is for a Tinkerboard S R2.0.

    I need the serial-number to identify the device. I read  

    /sys/firmware/devicetree/base/serial-number

    The problem is that I got the exact same serial for a duplicated image on another device !
    Also it's not the same as the one on the product box.

    How can I get the "real" serial using TinkerOS 3.0.11, ideally the serial which is on the box sticker ?

     

  6. Posted

    So: someone said this on the now dead tinkerboarding.co.uk :
     

    Quote

    This error message is caused by the userspace application try to use the OpenGL API.
    However, Tinker Board can only support OpenGL ES but not OpenGL API.
    So you need to use the OpenGL-ES API instead of OpenGL.

    Also, the missing file should be in libgl1-mesa-dri

  7. Posted

    Well, adding the same parameters to electron as the one used in /usr/lib/chromium/chromium-wrapper, I can see an improvement.

    GPU usage is now registering in 'tinker-power-management', but GPU usage is still around 50% for a FHD video.

    The error in the post above is still present.

    Here are the aforementioned flags :  

    --use-gl=egl --no-sandbox --gpu-sandbox-start-early --enable-accelerated-video-decode --ignore-gpu-blacklist --ignore-gpu-blocklist

    AFAII, it's using some userland drivers/decoders for the mali chip ?

  8. Posted

    Using Tinker Board S R2.0 Debian 10 V3.0.11
    No video acceleration.

    Xorg log : 

    [  1941.779] (EE) AIGLX error: dlopen of /usr/lib/arm-linux-gnueabihf/dri/rockchip_dri.so failed (/usr/lib/arm-linux-gnueabihf/dri/rockchip_dri.so: cannot open shared object file: No such file or directory)

    inxi : 

    Graphics:  Device-1: display-subsystem driver: rockchip_drm v: N/A
           Device-2: rk3288-dw-hdmi driver: dwhdmi_rockchip v: N/A
           Device-3: malit764 driver: mali v: N/A
           Display: tty server: X.Org 1.20.4 driver: modesetting resolution: 1920x1080~60Hz
           OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6

     

×
×
  • Create New...