GeeXboX

GeeXboX on D2plug

December 27th, 2014

Home Forums GeeXboX on ARM SoCs GeeXboX on D2plug

This topic contains 10 replies, has 3 voices, and was last updated by ajay.bhargav 15 hours, 10 minutes ago.

Viewing 11 posts – 1 through 11 (of 11 total)
  • Author
    Posts
  • #9485

    ajay.bhargav
    Member

    Hi everyone,

    I maybe starting this old thread again but I searched a lot before posting here.

    I am trying to run Armada 5xx build on my d2plug. System boots perfectly fine but after showing splash screen it gets stuck on main menu screen. I am not able to move cursor.. or do anything. However terminal is working. I do not see any process taking too much CPU when I do TOP. I don’t know why system is stuck. Please help me out with this issue. I am posting the log after login prompt. Is it something to do with vmem?

    LOG:

    Welcome to GeeXboX arm 3.0 (C) 2002-2012
    geexbox login: [ 26.879425] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 1000 Mb/s, full duplex, flow control disabled
    [ 26.890363] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
    [ 28.089521] total allocate vmem : 8585216
    [ 28.094168] total allocate vmem : 8617984
    [ 28.120706] total allocate vmem : 16912384
    [ 28.124953] total allocate vmem : 16977408
    [ 28.130175] total allocate vmem : 21124608
    [ 28.134420] total allocate vmem : 21157120
    [ 28.680898] total allocate vmem : 24843520
    [ 28.759476] total allocate vmem : 25367808
    [ 30.206433] EXT4-fs (mmcblk0p2): warning: maximal mount count reached, running e2fsck is recommended
    [ 30.218612] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
    [ 32.281811] total free vmem : 3686400
    [ 32.285922] total allocate vmem : 25433344
    [ 32.303588] total allocate vmem : 25437440
    [ 33.582156] total allocate vmem : 25445632
    [ 33.586706] total allocate vmem : 25453824
    [ 33.591150] total allocate vmem : 25519360
    [ 33.616825] total allocate vmem : 25535744
    [ 33.621516] total allocate vmem : 25568512
    [ 33.647651] total allocate vmem : 25634048
    [ 33.673268] total allocate vmem : 25638144
    [ 33.677730] total allocate vmem : 25670912
    [ 33.708202] total allocate vmem : 25671936
    [ 33.721902] total allocate vmem : 25934080
    [ 33.771117] total allocate vmem : 25942272
    [ 33.784489] total allocate vmem : 25946368
    [ 33.812223] total allocate vmem : 26077440
    [ 33.818931] total allocate vmem : 26093824
    [ 33.853358] total allocate vmem : 26110208
    [ 33.857987] total allocate vmem : 26142976
    [ 34.130290] total allocate vmem : 29829376
    [ 34.385630] total allocate vmem : 30353664

    Thanks in advance…

    #9496

    tomlohave
    Moderator

    Hello,

    Try to build a base system just to be sure everything is ok.
    We have defconfig for that.
    Once it works correctly with base system , you (we) can then look at xbmc problem.

    #9501

    Warped Rudi
    Moderator

    I think he already got past the point of needing a base system. I guess disabling the start of XBMC (systemctl mask xbmc) will do the same. The hardware seems to be pretty much identical to CuBox “classic”. However, I don’t think we want to debug anything based on such an old image 3.0 (!). So please move on to a recent snapshot.

    #9502

    ajay.bhargav
    Member

    Well I was using D3plug kernel v3.4.2 with added support for D2plug.. there were some significant changes.. But XBMC got stuck everytime the main screen showed up, even with latest build of Dec 22.

    I then moved to CuBox kernel.. modified it to work with D2plug and voila.. XBMC working!! I still need to work on audio codec as there is no sound in current kernel and I have made so many unwanted changes. I have already forked CuBox kernel and will push all the changes as I work on them. Hopefully you guys can also say D2plug is now supported :)

    #9503

    tomlohave
    Moderator

    That’s a great news
    May I suggest you to open PR for kernel here : https://github.com/warped-rudi/linux-cubox
    if @Warped-Rudi is ok :p
    for openbricks, you can off course open PR at https://github.com/OpenBricks/openbricks

    #9504

    ajay.bhargav
    Member

    ow! I did not know about warped-rudi’s repo… I simply forked rabeeh’s linux repo and added support for d2plug. are there any special patches in rudi’s repo?

    My repo is over here:
    https://github.com/RickeysWorld/linux-d2plug

    I am still updating it with clean patches.

    for openbricks, I will surely take a look into that.

    #9505

    ajay.bhargav
    Member

    I have merged patches from rudi’s branch and my patches are on top of it now. So considering it updated one.. :)

    PS: I wanted to edit the last post but there was no option.

    #9508

    Warped Rudi
    Moderator

    Let me know when you consider your kernel changes as ready. The goals should be to add D2plug to our build system as another machine that uses the armada5xx platform. However, I will need to do some cleanup as well…

    #9509

    ajay.bhargav
    Member

    I want to mention one thing.. The nxp_hdmi driver with changes done by rabeeh is not working with my d2plug. If I revert those changes and put my old kernel hdmi driver things seems to work just fine.I don’t know how to debug this.. as there is no crash at all and new driver seems to load just fine.

    So Here is my question.. Can I have my old HDMI driver in there? So for cubox lets load the driver with rabeeh changes and for d2plug my hdmi driver thats working for me. It may look a little ugly but thats only option for now.

    Just for information, both driver has same version:

    /* version */
    #define TDA_VERSION_MAJOR	1
    #define TDA_VERSION_MINOR	2
    #define TDA_VERSION_PATCHLEVEL 0
    #define TDA_VERSION_EXTRA	"-ioctl (2009-10-15)"
    #9512

    Warped Rudi
    Moderator

    Of course we can setup OpenBricks to use a different kernel for the D2plug. Just give as a link to the kernel repo and a copy of your kernel configuration file. But I had hoped for some unification. Especially, since there are other interresting changes in our nxp_hdmi (libCEC support, improved HDMI audio, colorspace correction). Where can I find the sources for your old HDMI driver? BTW, the CuBox has the S/PDIF out also connected to the TD19988 so that audio appears in parallel on optical and HDMI. Is this the case for the D2plug as well? Also the CuBox doesn’t have any analog audio codec nor VGA output.

    Edit: Did you use a straight HDMI to HDMI connection or some HDMI to DVI cable?

    #9513

    ajay.bhargav
    Member

    Even I wanted single kernel for both. Most of the things are common so I feel it should be easy to merge them both. As kernel patches are on top of rabeeh’s kernel so you can always keep the same kernel. How can I share HDMI files? PM?

    BTW, the CuBox has the S/PDIF out also connected to the TD19988 so that audio appears in parallel on optical and HDMI

    D2plug has same design I feel, I was looking for CuBox schematic just to get some idea how things are connected, But I could not find anywhere. There is an additional audio codec on D2plug for Audio Jack, which I have not tested yet.

    VGA is secondary, I am checking on HDMI as of now. I used a different Xorg.conf file which I made for d2plug and I think VGA should be working too. I am using HDMI <-> HDMI straight connection.

Viewing 11 posts – 1 through 11 (of 11 total)

You must be logged in to reply to this topic.

Comments are closed.