Can't start X

[SensoryEmpire]

Hi,

I installated Satellite onto a micro SD card, booted it up on an RPi2, and everything works fine, except that I can't seem to start X. When I run "startx" I get an error.
Is this normal behaviour?

thanks

[noisefuel]

try "sudo startx"

[Edgar]

For me, the command startx works with the version 1.03 of the image on Raspberry Pi 2
—Edgar

[SensoryEmpire]

I installed 1.03 on the RPi 2.

[Leon Trimble]

if i boot the pi, startx works, but i can't run it through ssh from the mac

[noisefuel]

yeah, me neither, I was expecting to see the X desktop on my laptop, but it just doesn't happen

[Deschutron]

  Until writing this message, I had this problem too.

  X doesn't automatically run, and I get sent to a linux console.

  I can login as pi. I see there's a user folder called "ccrma", containing configuration files for a desktop, but I don't know the password for that account.

  When I run startx, I get sent to a black screen on console 7.
  Back on console 1, X says that "FATAL: Module g2d_23 not found." and "No protocol specified".

  If I just run "X", I get a black screen and "FATAL: Module g2d_23 not found."

  In /var/log/xorg.0.log, it says, at one point, "FBTURBO(0): can't load 'g2d_23' kernel module ... no sunxi-g2d hardware detected (check /dev/disp and /dev/g2d) ... G2D hardware acceleration can't be enabled".

  /dev/disp and /dev/g2d don't exist.
  /dev/fb0 does exist.

  I've googled, youtubed and looked on the wiki. I didn't find the answer.

  I tried "sudo startx". It didn't work. Same result.

  I put all the files from /home/ccrma into /home/pi (mv pi pi.bak; mv ccrma pi; mkdir ccrma) and then tried. It still didn't work.

  Then I typed up most of this message and tried "sudo startx" again, and it worked.

  I don't know why. It's so late at night for me now. I wanted to say something before I gave up.

  I used this image from the front page: https://ccrma.stanford.edu/~eberdahl/Satellite/SatelliteCCRMA_Rpi2_v1.03.dd.gz

  It's the first link to a disk image I see, and presented as the main option.

  Next, I'll look to see how much functionality I can get out of the desktop environment, whether I can start it as a non-admin user, and whether I can do it after a reboot.

  Does anyone here know what causes this problem or what causes it to go away?

  And what login details are you meant to login to Satellite CCRMA with?

Deschutron

[Edgar]

Hi,

In my opinion, it's not a good idea to go something like try to run startx over a remote X connection. I don't know anyone who does that.

If you go to the following page (linked from the main Satellite CCRMA webpage)
https://ccrma.stanford.edu/wiki/Satellite_CCRMA_First_Steps
and then click on
"How To Connect"
it will help you figure out how to forward X windows to your laptop if you want to use your kit in a "headless" mode. Depending on whether you have a Mac, Windows, or Linux machine, you may or may not need to get some software installed to be able to forward X windows.

—Edgar

PS. The alternative that I recommend to that is connecting a USB keyboard, USB mouse, and an HDMI monitor to your kit, booting it up, logging in using "ccrma" / "temppwd" and then type
startx
to get X windows started.

[Edgar]

Again, this isn't recommended. Please see my comment above!
Best, Edgar

[Alessandro Altavilla]

Hi Edgar,
running ssh -XY cc...@192.168.0.6 (my ip autoassigned by DHCP), I cannot launch anything as xquartz does not seem to be able start x server.
For example, if I luanch qjackctl & i get:

qjackctl &

[1] 19179

ccrma@satellite ~ $ qjackctl.real: cannot connect to X server 

If i echo $DISPLAY on the terminal with the raspberry pi logged in through ssh, I get a blank line,

/private/tmp/com.apple.launchd.9Q6rKcqQMJ/org.macosforge.xquartz:0

I am on Yosemite. Running RPI2v103 image.

Any ideas?

Many thanks.
Alessandro

 

On my mac instead i get this:

[Edgar]

Hello,

Have you tried using ssh to connect to another machine somewhere else? That might be a good test as to whether your computer is setup to forward X windows correctly. I personally am able to forward X windows just fine with image version 1.03.

Look at this:   http://apple.stackexchange.com/questions/169657/ssh-x-does-not-work-on-yosemite

ssh has some fancy switches you can use to get much more "verbose" logging info (-vv or -vvv or maybe also -v, depending on how much information you really want :)

—Edgar

PS. I wonder if maybe some really super-aggressive firewall settings might block forwarded X-windows but not ssh in general?