Have you tried Estuary 2.1? Any updates?


Home Forums Estuary Releases Have you tried Estuary 2.1? Any updates?

This topic contains 10 replies, has 3 voices, and was last updated by  sghazagh 1 year, 8 months ago.

  • Author
    Posts
  • #867

    Estuary Admin
    Keymaster

    Please share your experience with Estuary 2.1

  • #902

    sghazagh
    Participant

    Hi,
    I tried that on HiKey (LeMaker).
    All OK except cannot see the signal on HDMI output.I only see the login prompt in serial console!
    Started yesterday, so I am working on it. Not sure that’s the driver issue or something else.

    Any idea? please let me know…

    Thanks

  • #903

    Jerome Forissier
    Participant

    Hi sghazagh,

    What did you try? Pre-built binaries or build from source? Which distribution?

    Thanks,

    Jerome

  • #904

    sghazagh
    Participant

    Hi,
    Thanks for your reply.
    I have used per-build images and files.

    I also have used “Ubuntu_ARM64.tar.gz” file az rootfs.

    As I mentioned all are working, I could enable wifi and the rest are fine except I do all of this in serial TTY debug console and I get no display on my HDMI
    monitor connected to HDMI port?!!!

    I do appreciate your help…

  • #905

    Jerome Forissier
    Participant

    Hello again,

    I have tried open-estuary 2.1 and like you I have no HDMI output. It looks like the kernel is missing some drivers. Actually there is no frame buffer device:

    
    ubuntu login: root
    Password: 
    Last login: Tue Nov 17 08:29:24 UTC 2015 on ttyAMA0
    root@ubuntu:~# ls /dev/fb*
    ls: cannot access /dev/fb*: No such file or directory
    

    I think guys at Linaro are working on upstreaming the graphics driver. You can find tracking branches at:
    https://github.com/96boards-hikey/linux/tree/hikey-tracking-drm
    https://github.com/96boards-hikey/linux/tree/hikey-tracking-gpu
    …not sure exactly what’s needed to get a console on the FB.
    The tracking branches are feature branches rebased on the latest upstream (currently v4.4).
    Then there is the “mainline rebase” branch, at https://github.com/96boards-hikey/linux/tree/hikey-mainline-rebase which is a merge of all the tracking branches. So basically you get the latest upstream kernel plus the latest HiKey developments.
    I have tried it and indeed there is a working framebuffer device:

    
    root@HiKey:/ uname -a
    Linux HiKey 4.4.0 #189 SMP PREEMPT Thu Feb 11 15:16:41 CET 2016 aarch64 GNU/Linux
    root@HiKey:/ ls /dev/fb*
    /dev/fb0
    root@HiKey:/ cat /dev/urandom >/dev/fb0
    cat: write error: No space left on device
    # And screen is filled with nice random noise ;-)
    

    I did not tried this kernel with the Ubuntu distribution (only with a minimal rootfs) but I don’t see why it would not work.

    HTH.

  • #906

    sghazagh
    Participant

    Thanks mate,
    At least you have cleared that to me there is some issue with this release.

    However, I need you to help me make it work on my side please.
    I had a look on “mainline-rebase”. you said it’s working with mini-rootfs so I also believe it should work with other rootfs like Ubuntu_ARM64 file as well.
    So I need the kernel from this GIT…
    But I need to compile that which is time consuming as I have to get the aarch64 linaro toolchain, set it up and it might comm up with other requirements which I believe gets time to fix and make it working.

    Can you please give me a guide and files (kernel and others if there are) which you have tried then I check on my side to see if it works with Ubuntu_ARM64 tar file as well? Something that I can replace over and see if it works!

    Many thanks

  • #907

    sghazagh
    Participant

    Ok,
    I think I have to get my hand dirty… I am going to compile the kernel myself 😉
    I already have setup he aarch64 toolchain and the GIT is cloning now…
    Will let you know if it worked!

  • #908

    sghazagh
    Participant

    Ok my friend,
    I have compiled Kernel, Device Tree and all modules and imparted them to my HiKey.
    The Kernel is upgraded to version 4.4.0 and the frame buffer works fine.
    I could bring the mini-rootfs up with display available, and also could see the Debian Image which was available in partition 9.
    Have not tried the Ubuntu_ARM64 rootfs though. But I think that would be fine too.

    So,many thanks for your advise and help.

  • #909

    sghazagh
    Participant

    Another question raised for me!!!

    I tried to install xubuntu-desktop and after installation lightdm service and desktop does not run.
    the error says: No Display Found.

    Have you any idea?

    By the way, do you think the GPU may cause the issue? I do not see MALI module in the list of loade modules. How can I install MALI driver?

    Any help?

  • #910

    Jerome Forissier
    Participant

    @sghazagh glad you could make it work! As you see you should not be afraid of compiling the kernel, as a developer working on big projects involving many components, you can expect you will need to adjust and recompile things… The pre-built binaries are there to help you get things up and running as quickly as possible, but they are necessarily lagging behind the bleeding-edge sources.

    Now regarding your GPU question… frankly I don’t know much about this :(
    It seems the Mali driver is present in 4.4 (and hence in the current “mainline-rebase” branch), maybe just not as a module. Did you grep dmesg for “Mali”? I’m usually running a vanilla 4.4 kernel (serial console only), and I do see this in dmesg:

    
    Mali<2>: Inserting Mali v800 device driver. 
    Mali<2>: Compiled: Feb 11 2016, time: 16:50:20.
    Mali<2>: Driver revision: -v4.4-601-gfebd1f1
    Mali<2>: mali_module_init() registering driver
    Mali<2>: mali_probe(): Called for platform device 3f100000.mali
    Mali<2>: Mali SWAP: Swap out threshold vaule is 60M
    Mali<2>: Mali memory settings (shared: 0x40000000)
    Mali<2>: Using device defined frame buffer settings (0x00708000@0x3F100000)
    Mali<2>: Memory Validator installed for Mali physical address base=0x3F100000, size=0x00708000
    Mali<2>: Mali PM domain: Creating Mali PM domain (mask=0x00001000)
    Mali<2>: Broadcast: Creating Mali Broadcast unit: Mali_Broadcast
    Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
    Mali<2>: Mali PP: Base address of PP core: 0xf4088000
    Mali<2>: Found Mali GPU Mali-450 MP r0p0
    Mali<2>: Mali DLBU: Initializing
    Mali<2>: Mali L2 cache: Created Mali_L2:   8K, 4-way, 64byte cache line, 128bit external bus
    Mali<2>: Mali L2 cache: Created Mali_L2: 128K, 4-way, 64byte cache line, 128bit external bus
    Mali<2>: Mali MMU: Creating Mali MMU: Mali_GP_MMU
    Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    Mali<2>: Probe: Page fault detect: PASSED
    Mali<2>: Probe: Bus read error detect: PASSED
    Mali<2>: Mali GP: Creating Mali GP core: Mali_GP
    Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP0_MMU
    Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    Mali<2>: Probe: Page fault detect: PASSED
    Mali<2>: Probe: Bus read error detect: PASSED
    Mali<2>: Mali PP: Creating Mali PP core: Mali_PP0
    Mali<2>: Mali PP: Base address of PP core: 0xf4088000
    Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP1_MMU
    Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    Mali<2>: Probe: Page fault detect: PASSED
    Mali<2>: Probe: Bus read error detect: PASSED
    Mali<2>: Mali PP: Creating Mali PP core: Mali_PP1
    Mali<2>: Mali PP: Base address of PP core: 0xf408a000
    Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP2_MMU
    Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    Mali<2>: Probe: Page fault detect: PASSED
    Mali<2>: Probe: Bus read error detect: PASSED
    Mali<2>: Mali PP: Creating Mali PP core: Mali_PP2
    Mali<2>: Mali PP: Base address of PP core: 0xf408c000
    Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP3_MMU
    Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    Mali<2>: Probe: Page fault detect: PASSED
    Mali<2>: Probe: Bus read error detect: PASSED
    Mali<2>: Mali PP: Creating Mali PP core: Mali_PP3
    Mali<2>: Mali PP: Base address of PP core: 0xf408e000
    Mali<2>: Starting new virtual group for MMU PP broadcast core Mali_PP_MMU_Broadcast
    Mali<2>: Mali DLBU: Creating Mali dynamic load balancing unit: Mali_DLBU
    Mali<2>: Broadcast: Creating Mali Broadcast unit: Mali_Broadcast
    Mali<2>: Mali MMU: Creating Mali MMU: Mali_PP_MMU_Broadcast
    Mali<2>: Mali PP: Creating Mali PP core: Mali_PP_Broadcast
    Mali<2>: Mali PP: Base address of PP core: 0xf4096000
    Mali<2>: 4+0 PP cores initialized
    Mali<2>: Mali GPU Timer: 50
    Mali<2>: Mali GPU Utilization: No platform utilization handler installed
    Mali<2>: mali_probe(): Successfully initialized driver for platform device 3f100000.mali
    Mali: Mali device driver loaded
    

    Then for X11 to work I think you also need some closed-source shared libraries (like libGL.so). Not sure about that and I don’t know where to find them either :(

  • #911

    sghazagh
    Participant

    Hello my friend,
    Yes you were right. The Mali driver seems to work:

    
    root@ELAR-Systems:~# dmesg |grep mali
    [    0.446303] Mali<2>: mali_module_init() registering driver
    [    0.446366] Mali<2>: mali_probe(): Called for platform device 3f100000.mali
    [    0.447326] Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    [    0.447397] Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    [    0.447473] Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    [    0.447546] Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    [    0.447617] Mali<2>: mali_mmu_probe_irq_acknowledge: intstat 0x3
    [    0.448116] Mali<2>: mali_probe(): Successfully initialized driver for platform device 3f100000.mali
    

    I don’t know why the lightdm does not work!
    ARM64 resources are not too complete. for example Lubuntu-Desktop for aarch64 is not available at all!

    The mainline rebase Kernel 4.4.0 is quiet good. th thing is that I can boot to graphical GUI if I use Debian-Jessie-ARM64 image provided by Linaro but mine only I can see the command prompt on serial console and now in TTY terminal.

    I don’t give up and try to see if I can find it out. By the way, please let me know if you find any clue.

    Thanks for your time,

    Please have a look at: http://www.elar-systems.com

    I will be happy to see you in my Circle too:

    http://www.elar-systems.com.au/fb
    http://www.elar-systems.com.au/plus

You must be logged in to reply to this topic.