Announcement

Collapse
No announcement yet.

Linuxice 2.0.x gui fails to start

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Linuxice 2.0.x gui fails to start

    Hello,
    I have installed Linuxice 2.0.0 and 2.0.1 on a Intel d945gclf2 and I have a slight issue. Everything appears to install properly but upon reboot the gui never loads on startup. This happens even after the first reboot. If I run startx, nghost, icepanel, and the matchbox panel all start properly. I have placed a script startx in the init.d directory and ran update-rc.d startx defaults. Now I am left with a screen that only contains the matchbox panel. The keyboard also no longer works and I do not have a ps2 keyboard available. Basically I'm left with a system where I can not fix or use anything. I would just like to know how to fix the boot process in linuxice. I have a feeling others are having this issue as well. Thanks

    startx

    #!/bin/bash

    startx

  • #2
    You are the first one that's reported this so far...

    all that should be needed is a "startx" at the commandline. If you look in /etc/X11/Xsession.d, there should be a symlink to /etc/matchbox/session where the all the gui components are started from.

    Is this an otherwise unmodified fresh install? Do you get any errors?
    Former author of LinuxICE, nghost, nobdy.
    Current author of Automotive Message Broker (AMB).
    Works on Tizen IVI. Does not represent anyone or anything but himself.

    Comment


    • #3
      Originally posted by tripzero View Post
      You are the first one that's reported this so far...

      all that should be needed is a "startx" at the commandline. If you look in /etc/X11/Xsession.d, there should be a symlink to /etc/matchbox/session where the all the gui components are started from.

      Is this an otherwise unmodified fresh install? Do you get any errors?
      Yes this is an unmodified install. I have tested this with all the images you have at openice.org. The problem does not appear related to image corruption. I have also tried installing Linuxice with different hard drives in order to rule out the most probable hardware failure or bad sectors. It appears to be an startup or X failure. The odd thing is the lack of errors in the Xorg log or the system log. If I run startx from the command line it will start the gui properly but, this is just not usable in a car. I'm wondering If this has to do with ubuntu 9.04 and intel graphics,but I'm betting against it. Do you have a 9.10 or later release that I may try. Once again this is the standard Box945GCFL2 motherboard.
      Thanks

      Comment


      • #4
        is your screen just blank? What monitor are you using? If X fails to start, it should at least tell you why in the console output. So maybe it is starting an the output is "out of range" or soemthing similar?

        can you attatch your xorg.log?
        Former author of LinuxICE, nghost, nobdy.
        Current author of Automotive Message Broker (AMB).
        Works on Tizen IVI. Does not represent anyone or anything but himself.

        Comment


        • #5
          Originally posted by tripzero View Post
          is your screen just blank? What monitor are you using? If X fails to start, it should at least tell you why in the console output. So maybe it is starting an the output is "out of range" or soemthing similar?

          can you attatch your xorg.log?
          Nope I am just left with the command line. The screen is fine. it just seems that the xserver doesn't start as it should. If I run startx manually nghost, icepanel, nscan, and etc will all start without a problem. They just won't start automatically on boot. I can attach an xorg log when I get back home later today. Thanks for your time.

          Comment


          • #6
            Very odd. I decided install Linuxice without a hard disk I was mounting at /home/john/Music and everything appears to work. I previously had this disk mounted at /media/Seth. During that configuration everything worked fine. So the problem is related to the mount point. Maybe nscan failing? Very odd. Thanks for your help. Is there any more information you require in order to trouble shoot this problem?

            Comment

            Working...
            X