• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 612 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MCSDK Silent Install on Linux

Dan Christensen
Prodigy 240 points

Hello,

I've seen some very odd behavior with MCSDK 02.00.02.14 on Linux while trying to perform an automated install.

First, while in silent mode, I've had X11 Forwarding enabled, and saw 2 progress dialogs (similar to what is seen during the GUI installation).

Second, while in console mode, the responses file is not sufficient to avoid any prompts.  The installer appears to hang, until enter is pressed.  At which point, the SYS BIOS (and after, the IPC) license agreement and installation paths require user interaction.

Third, while in silent mode, the responses file generated during a GUI installation doesn't seem to honor the selected components.  In addition, the installer hangs when the DISPLAY variable is not set.  This hang can be averted by hitting enter and pressing space, as if to page through the license agreement in console mode.

I was stuck until I wrote this post.  During which I found somewhat of a work around:

yes ' ' | bios_mcsdk_02_00_02_14_setuplinux.bin --mode silent --prefix <installation path>

I think this is a significant issue, and hope is resolved in future releases.
Dan

  • 0
    TI__Guru 50170 points

    Hi, Dan,

    I tried 2 times to install the bios_mcsdk_02_00_02_14 and it was installed successfully without stalling or needing any interactions. The command I used was:

       ./bios_mcsdk_02_00_02_14_setuplinux.bin --mode silent --prefix /mnt/sdb1/tmp/texas_instruments

    The difference may be that I was installing locally to the Ubuntu machine vs yours remotely, I assume. Could you try to install the package locally if you were doing it remotely and see if it works for you?

    Thanks!

    Rex

  • 0 in reply to Rex Chang
    TI__Guru 50170 points

    Hi, Dan,

    By the way, are you using ssh to install the package remotely? If you are, do you have SSH X11 forwarding enabled with -X?

    Rex

  • 0 in reply to Rex Chang
    Prodigy 240 points

    Hi Rex,

    I verified my result with a local install.  This was connected directly to an Ubuntu box, with no X server running.  I haven't tried to replicate the failure from a graphical console, but I suspect unsetting the DISPLAY environment variable would do it.

    Yes I am using ssh to remotely connect to the target machine, and yes I did have X11 forwarding enabled.  With X11 forwarding enabled, I can simulate the failure by unsetting the DISPLAY environment variable.  In my actual use case (continuous integration builds) I don't intend to have an X server running.
    The workaround I mentioned does get around the prompts, but it certainly seems like a bug.

    Thanks for your time,
    Dan

  • 0 in reply to Dan Christensen
    TI__Guru 50170 points

    Hi, Dan,

    Yes. X11 forwarding needs to be enabled for now. It may have something to do with the 2 pop-up GUI windowns from IPC and BIOS during installation. We are checking to see if the issue goes away with these 2 windows removed.

    Thanks!

    Rex

  • 0 in reply to Rex Chang
    Prodigy 240 points

    Hi Rex,

    Thanks for the quick responses.

    As I mentioned, I do have a workaround.  And with no X server available, it seems to successfully fall back to a "console" style build.  However, the two bugs seem to be:

    1. requiring user interaction for a 'silent' install (and not having any prompts to indicate it)
    2. not having any prompt for the required action during a 'console' install

    Hopefully that clears up what I'm seeing.

    Thanks,
    Dan