• State
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 433 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.

How to boot to a command prompt instead of Matrix-GUI

tcalef
Prodigy 240 points
Other Parts Discussed in Thread: OMAP3530

Hi All,

I am trying to get DVSDK 4.0 working on my OMAP3530 (gumstix overo). I have the overo booting up and entering into Matrix-GUI where I can perform a couple of the applications. My question is though, how can I modify my fiilesystem, so that I just boot to a command prompt instead of into Matrix-GUI. If i remove the matrix-gui from /etc/init.d, it just hangs.

 

Any ideas?

Thanks!

  • 0
    TI__Expert 5960 points

    Hi,

    The script file you removed is referenced from the run level directories:

    Check the directories:

    /etc/r0.d

    /etc/r1.d

    .

    .

    /etc/r6.d

    There are links there for the different run levels which point to the matrix-gui init script.  You can remove the links from these directories to keep matrix-gui from automatically starting under any conditions.

    Additionally you could rename the links from S99matrix-gui to K99matrix-gui.  This should also keep matrix-gui from starting automatically.

  • 0 in reply to Jeff L
    Prodigy 240 points

    Thanks for the quick reply.

    I did what you suggested, and it does in fact, take the Matrix-gui out of the startup.. but now it just hangs. Do I have to put another one in there so that it gets to the command prompt?

     

    Thanks!

  • 0 in reply to tcalef
    TI__Expert 5960 points

    I think you may have a different problem.  I'm testing DVSDK 4.0 on an omap3530 EVM.  Even if matrix-gui is enabled you can still get to the login prompt. Whether or not you start up matrix-gui should not matter. When started automatically it is running in the background to your login shell.  Possibly you could dump your kernel boot up log and re-post to another thread. Since Matrix comes up, it could be another start up process that is not cooperating. I'm not familiar with the gumstix platform.