$DISPLAY is not set

i7920 · 2010-05-25 01:56:01

Hi, I'm having problems loading compiz-fusion or the settings with my nvidia driver, or driver itself.

Basically, I installed Arch (in vmware) and ran:
-pacman -Syu,
-pacman -S libgl xorg mesa xf86-video-vesa hal xf86-input-evdev xf86-input-mouse xf86-input-keyboard compiz-fusion alsa alsa-util nvidia
is there anything else I'm missing?

here's the error messages:

basically it says that my nvidia driver is incorrect or not configured properly. I have an nvidia 7300gt, does anybody know which driver I should be using??
http://www.nvidia.com/object/linux-d...195.36.24.html
this one should work, I'm not sure what I'm doing incorrectly. it still says $DISPLAY not set when I type startx/ccsm/fusion-icon.

I've been reading these but still no answers... http://wiki.archlinux.org/index.php/NVIDIA
http://bbs.archlinux.org/viewtopic.php?id=90918

cheers

Moderator edit: There is no added value to adding 'not solved' to your topic title

Last edited by .:B:. (2010-06-08 21:24:24)

perbh · 2010-05-25 02:30:12

So, why don't you just set it somewhere (eg. your .bashrc)?

export DISPLAY=:0.0

i7920 · 2010-05-25 02:54:55

please, I don't speak unix, what is the exact code? :-)

perbh · 2010-05-25 03:01:06

Exactly as shown, you put that line in your .bashrc file

Daenyth · 2010-05-25 03:09:58

/facepalm

rransom · 2010-05-25 03:34:10

i7920: See http://wiki.archlinux.org/index.php/Ins … _in_VMWare. You are expected to search the wiki yourself before asking for help here.

perbh: Please do not give bogus advice to the newbies, no matter how deserving you think they are. The DISPLAY environment variable should be set by whatever program or script has started the X server. Setting DISPLAY in .bashrc, or any other shell startup script, is a recipe for trouble.

skottish · 2010-05-25 03:49:55

i7920 wrote:

please, I don't speak unix, what is the exact code? :-)

I mean no offense, but Arch is probably not going to be a good fit for you right now. Arch's promise of simplicity is that it will try the best that it can to stay out of the users way so that they can control their own system. Learning the 'Unix way', commands, and stucture, is imperative for success with this distro.

i7920 · 2010-05-25 03:57:28

thanks rransom! that's very helpful, I'll see if that resolves the issue.

i7920 · 2010-05-25 04:00:53

skottish wrote:

i7920 wrote:
please, I don't speak unix, what is the exact code? :-)
I mean no offense, but Arch is probably not going to be a good fit for you right now. Arch's promise of simplicity is that it will try the best that it can to stay out of the users way so that they can control their own system. Learning the 'Unix way', commands, and stucture, is imperative for success with this distro.

no I'm totally fine with typing commands and using the keyboard to navigate, I'm just new to the unix environment and arch so please cut me some slack--I am in the newbie section after all.

Last edited by i7920 (2010-05-25 04:24:45)

fsckd · 2010-05-25 04:03:52

Heh, I think you might backtrack a bit before this is over.

(Don't you love enigmatic advice?)

perbh · 2010-05-25 04:35:05

rransom wrote:

i7920: See http://wiki.archlinux.org/index.php/Ins … _in_VMWare. You are expected to search the wiki yourself before asking for help here.
perbh: Please do not give bogus advice to the newbies, no matter how deserving you think they are. The DISPLAY environment variable should be set by whatever program or script has started the X server. Setting DISPLAY in .bashrc, or any other shell startup script, is a recipe for trouble.

It is _not_ a 'bogus' advice!
Granted - it should be set, but I have come across cases/distros where I have had to set it myself.

rransom · 2010-05-25 04:54:22

perbh wrote:

rransom wrote:
i7920: See http://wiki.archlinux.org/index.php/Ins … _in_VMWare. You are expected to search the wiki yourself before asking for help here.
perbh: Please do not give bogus advice to the newbies, no matter how deserving you think they are. The DISPLAY environment variable should be set by whatever program or script has started the X server. Setting DISPLAY in .bashrc, or any other shell startup script, is a recipe for trouble.
It is _not_ a 'bogus' advice!
Granted - it should be set, but I have come across cases/distros where I have had to set it myself.

So have I, but the *only* case I have seen in which setting DISPLAY in .bashrc would have been a good idea was in Cygwin on Windows 98. On a Unix-like system, .bashrc is the wrong place to set DISPLAY.

perbh · 2010-05-25 05:02:56

DISPLAY almost always have to be set when working across unix/linux-machines with X-applications ... (though obviously not as :0.0)

Last edited by perbh (2010-05-25 05:03:29)

rransom · 2010-05-25 06:18:30

perbh wrote:

DISPLAY almost always have to be set when working across unix/linux-machines with X-applications ... (though obviously not as :0.0)

Yes, that last part is one reason that setting DISPLAY in .bashrc is bad: DISPLAY is supposed to indicate the address of your current X server, which will not always be :0.

Also, some programs behave differently depending on the value of DISPLAY -- usually, they will try to display a GUI if DISPLAY is set and use a terminal-only fallback if DISPLAY is not set. If you are not using X, but DISPLAY is set, such programs will try to show a GUI and crash, whereas they would have worked if you had left DISPLAY unset.

i7920: Based on the text you edited out of post #9, you seem to have gotten a clue. Since DISPLAY being unset is clearly not your problem, please edit your post #1 to remove "(NOT SOLVED)" from the title of this thread; you can start a new thread if (when?) you need help again. And good luck learning Arch Linux -- it'll be a saner, easier-to-use environment than the one I learned Unix with.

i7920 · 2010-06-08 20:25:32

rransom wrote:

Since DISPLAY being unset is clearly not your problem, please edit your post #1 to remove "(NOT SOLVED)" from the title of this thread; you can start a new thread if (when?) you need help again. And good luck learning Arch Linux -- it'll be a saner, easier-to-use environment than the one I learned Unix with.

Alright, so we've established that 'export DISPLAY=:0.0' won't solve the problem, but I'm still having the same issues with the nvidia driver or its configuration. any advice?
problem isn't solved yet!

Ramses de Norre · 2010-06-08 20:39:38

Have you read through the nvidia page on the wiki?

i7920 · 2010-06-08 20:42:12

yes

anonymous_user · 2010-06-08 20:56:15

@i7920 - after installing the nvidia driver, make sure you run "nvidia-xconfig".

fsckd · 2010-06-08 21:18:47

vmware, right? The answer is on the wiki page linked to above.

rransom · 2010-06-09 00:09:19

VMware guests cannot access the host's video card. The nvidia drivers will not help you.

When I saw that you had deleted all mention of the nvidia drivers from post #9, I assumed that you had figured this out already; otherwise, I would have told you explicitly to install xf86-video-vmware and forget about the nvidia drivers.

fsckd · 2010-06-09 16:43:49

In case you forgot which link I'm referring to (post #6 by rransom), it's this one: http://wiki.archlinux.org/index.php/Ins … stalling_X . Click it, you know you want to.

i7920 · 2010-06-09 17:19:02

anonymous_user wrote:

@i7920 - after installing the nvidia driver, make sure you run "nvidia-xconfig".

doesn't work

anonymous_user · 2010-06-09 17:22:07

Yeah, I just realized you were trying to install in vmware so you shouldn't be using the NVIDIA driver.

Arch Linux

#1 2010-05-25 01:56:01

$DISPLAY is not set

#2 2010-05-25 02:30:12

Re: $DISPLAY is not set

#3 2010-05-25 02:54:55

Re: $DISPLAY is not set

#4 2010-05-25 03:01:06

Re: $DISPLAY is not set

#5 2010-05-25 03:09:58

Re: $DISPLAY is not set

#6 2010-05-25 03:34:10

Re: $DISPLAY is not set

#7 2010-05-25 03:49:55

Re: $DISPLAY is not set

#8 2010-05-25 03:57:28

Re: $DISPLAY is not set

#9 2010-05-25 04:00:53

Re: $DISPLAY is not set

#10 2010-05-25 04:03:52

Re: $DISPLAY is not set

#11 2010-05-25 04:35:05

Re: $DISPLAY is not set

#12 2010-05-25 04:54:22

Re: $DISPLAY is not set

#13 2010-05-25 05:02:56

Re: $DISPLAY is not set

#14 2010-05-25 06:18:30

Re: $DISPLAY is not set

#15 2010-06-08 20:25:32

Re: $DISPLAY is not set

#16 2010-06-08 20:39:38

Re: $DISPLAY is not set

#17 2010-06-08 20:42:12

Re: $DISPLAY is not set

#18 2010-06-08 20:56:15

Re: $DISPLAY is not set

#19 2010-06-08 21:18:47

Re: $DISPLAY is not set

#20 2010-06-09 00:09:19

Re: $DISPLAY is not set

#21 2010-06-09 16:43:49

Re: $DISPLAY is not set

#22 2010-06-09 17:19:02

Re: $DISPLAY is not set

#23 2010-06-09 17:22:07

Re: $DISPLAY is not set

Board footer