Jump to content

Recommended Posts

Posted

I recently switched to ubuntu, and I am extremely new to it. As in, I've never used it before. I've been having a hell of a time installing anything on ubuntu because I've always been spoiled with the installer wizard on windows. So I've been working on installing et for about 3 days now between work. I believe I installed it correctly, followed directions here

https://help.ubuntu.com/community/EnemyTerritory

but whenever I run the game the screen goes black for a moment, then switches to 800x600 resolution and nothing happens. The screen just goes back to whatever I was on (firefox, terminal, etc) and gets stuck in 800x600. Since I can't figure out how to change resolution back I've just been restarting whenever that happens to get it back to normal resolution. The terminal is saying this as the final error output

Sys_Error: GLimp_Init() - could not load OpenGL subsystem

Doing a crapton of research I figured out that it usually means that either the videocard doesn't have opengl working correctly or there is a problem with my libraries.

I have an nvidia geforce 540 something or other and I updated the driver using some apt-get install nvidia-current or something close to that. I also have installed the 32 bit libraries (I'm on ubuntu 12.04 64bit) by following the directions in the link above. Is there anything else I'm missing?

 

Also just a few random questions about ubuntu. How do I get to a control pannel sort of deal? Based on what I've been reading it should be called system. Such like system -> administration. Or system -> hardware. Those sort of deals. I can get to system settings(its on the launcher sidebar thing) but I cannot find anything that is only called system or anything to do with administration.

 

Thanks in advance.

  • Clan Friend
Posted

hmmm, I don't Use Ubuntu, and my Linux is not 64bit (I'll switch from Fedora 32bit to Arch 64 when I'll find the time), and my card is ATI, so I can't help u much :P

 

but imho you should:

1. check if you have installed your graphic drivers correctly

$ fglrxinfo

$ glxinfo | head

$ fgl_glxgears

etc. (I am not sure if these are ok for your system as well, I use Fedora 32bit and ATI Catalyst)

 

2. I think you need nvidia 32-bit compatibility libraries as well, that is the problem imho, maybe when you installed your graphics card drivers you didn't install the 32bit part, just guessing...

 

When you install using the file from nvidia website there are 2 versions, one with 32 bit support and one without (didn't try because I use ATI). I don't know about the package installed from your disto's repository, maybe those things are included, maybe not...

 

Perhaps you should have installed those ia32-libs before installing the nvidia driver...

 

Now, I don't know if there is a way to test if you have that 32bit compatibility thingy installed correctly, maybe you should check if you have those 32bit libs somewhere, but atm I have no clue, since I don't know which filenames you should look for :P

 

 

Anyway, please post your full et console log here, maybe the problem is not with your drivers and it's something else.

Posted

Yeah I had this problem before too and it was the missing 32bit libraries - they didnt include them in Ubuntu 11+ for some reason..

Posted

hmmm, I don't Use Ubuntu, and my Linux is not 64bit (I'll switch from Fedora 32bit to Arch 64 when I'll find the time), and my card is ATI, so I can't help u much :P

 

but imho you should:

1. check if you have installed your graphic drivers correctly

$ fglrxinfo

$ glxinfo | head

$ fgl_glxgears

etc. (I am not sure if these are ok for your system as well, I use Fedora 32bit and ATI Catalyst)

 

2. I think you need nvidia 32-bit compatibility libraries as well, that is the problem imho, maybe when you installed your graphics card drivers you didn't install the 32bit part, just guessing...

 

When you install using the file from nvidia website there are 2 versions, one with 32 bit support and one without (didn't try because I use ATI). I don't know about the package installed from your disto's repository, maybe those things are included, maybe not...

 

Perhaps you should have installed those ia32-libs before installing the nvidia driver...

 

Now, I don't know if there is a way to test if you have that 32bit compatibility thingy installed correctly, maybe you should check if you have those 32bit libs somewhere, but atm I have no clue, since I don't know which filenames you should look for :P

 

 

Anyway, please post your full et console log here, maybe the problem is not with your drivers and it's something else.

greedygoose@greedygoose:~$ glxinfo
name of display: :0.0
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Error: couldn't find RGB GLX visual or fbconfig
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".

So do I need to install the 32bit driver? Or is it listed as a 64bit driver with 32bit support? (What would be the reason for them not supporting 32bit in a 64bit driver?)

I did run the ia32_libs before I installed the driver. That was what I tried first, and when that didn't fix the problem I went to trying to reinstall the driver.

Also I originally went to the nvidia website to try and update the driver, but following the directions, moving the file and then running it as root, it failed and gave me a message about closing my x server or something (I can reproduce and get the full error if needed.) So after that didn't work I used apt-get install nvidia-current after updating repositories.

greedygoose@greedygoose:~$ et
ET 2.60b linux-i386 May  8 2006
----- FS_Startup -----
Current search path:
/home/greedygoose/.etwolf/etmain
/usr/local/games/enemy-territory/etmain/pak2.pk3 (22 files)
/usr/local/games/enemy-territory/etmain/pak1.pk3 (10 files)
/usr/local/games/enemy-territory/etmain/pak0.pk3 (3725 files)
/usr/local/games/enemy-territory/etmain/mp_bin.pk3 (6 files)
/usr/local/games/enemy-territory/etmain
----------------------
3763 files in pk3 files
execing default.cfg
couldn't exec language.cfg
couldn't exec autoexec.cfg
Hunk_Clear: reset the hunk ok
------- Input Initialization -------
Joystick is not active.
------------------------------------
Bypassing CD checks
----- Client Initialization -----
----- Initializing Renderer ----
-------------------------------
----- Client Initialization Complete -----
----- R_Init -----
...loading libGL.so.1: Initializing OpenGL display
...setting mode 4: 800 600
Using XFree86-VidModeExtension Version 2.2
XF86DGA Mouse (Version 2.0) initialized
XFree86-VidModeExtension Activated at 800x600
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Couldn't get a visual
...WARNING: could not set the given mode (4)
Initializing OpenGL display
...setting mode 3: 640 480
Using XFree86-VidModeExtension Version 2.2
XF86DGA Mouse (Version 2.0) initialized
XFree86-VidModeExtension Activated at 640x480
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
Couldn't get a visual
...WARNING: could not set the given mode (3)
----- CL_Shutdown -----
RE_Shutdown( 1 )
-----------------------
----- CL_Shutdown -----
-----------------------
Sys_Error: GLimp_Init() - could not load OpenGL subsystem

 

On the bright side I did figure out how to change the resolution, so now I don't have to reboot after every failed launch of et =)

  • Clan Friend
Posted

greedygoose@greedygoose:~$ glxinfo
name of display: :0.0
Xlib: extension "GLX" missing on display ":0.0".

it doesn't look promising :s

 

So do I need to install the 32bit driver? Or is it listed as a 64bit driver with 32bit support? (What would be the reason for them not supporting 32bit in a 64bit driver?)

well, I don't have an nvidia card, but here for example I see there are 2 versions, one with 32 bit support and one without:

ftp://download.nvidia.com/XFree86/Linux-x86_64/304.22/

 

Something must have gone wrong with the drivers installation, until your glxinfo output is not ok, and you aren't able to run glxgears, then et can't obviously go.

 

Did you get errors or warnings during the drivers installation? With that glxinfo output, I doubt you have opengl working, either 32 or 64 bit

 

Check the logs for errors

$ less /var/log/Xorg.0.log

 

are using unity? maybe

$ dmesg | grep unity

could tell you if there are error messages from unity, because I think your desktop needs opengl as well

 

I remember I once had a problem (but with ATI!) about the open source driver overwriting a library

$ which glxinfo

/usr/bin/glxinfo

$ ldd /usr/bin/glxinfo | grep GL

libGL.so.1 => /usr/lib/libGL.so.1 (0x05975000)

$ ls -l /usr/lib/libGL.so.1

lrwxrwxrwx 1 root root 21 Apr 27 12:53 /usr/lib/libGL.so.1 -> /usr/lib/libGL.so.1.2

 

that file (/usr/lib/libGL.so.1.2) got overwritten

 

I know it's not your issue, but try and check if maybe you have some conflict with some previous driver as well, because I don't think that proprietary drivers get installed straight away, maybe there is some leftover from the opensource driver?

 

Anyone here using Ubuntu 64bit + nvidia? because I can't help much here...

Posted

greedygoose@greedygoose:~$ ls -l /usr/lib/nvidia-current/libGL.so.1
lrwxrwxrwx 1 root root 15 Jun 17 15:14 /usr/lib/nvidia-current/libGL.so.1 -> libGL.so.302.17

dmesg | grep unity had no results (was blank so that's what I'm assuming happened.)

 

greedygoose@greedygoose:~$ less /var/log/Xorg.0.log | grep GL
[    21.746] (II) NVIDIA GLX Module  302.17  Tue Jun 12 16:22:45 PDT 2012
[    21.746] (II) Loading extension GLX
965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
[    22.106] (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)

Don't know if that relates to the issue, I didn't understand what the log was for. I like grep, didn't know about that or bars either. Handy tool lol.

 

How do I navigate the nvidia ftp, as in how to I know which driver to download? Or is the one you linked the correct one I should try?

  • Clan Friend
Posted

Don't know if that relates to the issue, I didn't understand what the log was for. I like grep, didn't know about that or bars either. Handy tool lol.

 

How do I navigate the nvidia ftp, as in how to I know which driver to download? Or is the one you linked the correct one I should try?

 

the character | is to redirect the output of a command to another, very useful, actually instead of

$ less /var/log/Xorg.0.log | grep GL

 

I would have done:

$ grep GL /var/log/Xorg.0.log | less

or even

$ cat /var/log/Xorg.0.log | grep GL | less

 

less usually goes last, since you use it to scroll the output or search, and stuff


Xorg.0.log is the log where all the messages from the X server (your desktop, basically) go

 

you can do:

$ less /var/log/Xorg.0.log

if you want to see the full log, then inside less you can scroll or use / to search (it's case sensitive, type --i for case insensitive search) and q to quit, h for help

 


as regards the nvidia website, I just opened a random link... well, I guessed that was the last version actually :P, but I suggest you to go to nvidia website, then use the search function and see which is the driver for your card.

 

You can download it from there or from that ftp, but I think the one suggested from the website is the complete one (with 32bit support)

 

Remember to say yes if you are prompted for the installation of the 32bit part, but imho you should try to install the drivers from your distro's repo first, because I guess it's easier, and it's easier to upgrade, I don't know what would happen if there is a new kernel upgrade for example, if you have to install nvidia drivers again or not

 

$ lspci -nn | grep -i vga

tells you your gfx card model, but you should know that...

 

Before reinstalling, make sure you uninstall any other nvidia drivers and stuff, maybe there is some conflict

try

$ sudo less /var/log/messages

ands see if there are other error or warning messages related to your graphics card or drivers

 

If you install the ones from nvidia site you should uninstall all the other nvidia drivers as far as I know, included the open source ones (it should be xserver-xorg-video-nouveau)

 

good luck, and tell me if you succeed :P

Posted

Inside X, click the icon at the top rightmost of your screen, select System Settings. A new window will appear, seelct Additional Drivers. From there, if you have successfully installed any Nvidia drivers, those should appear from the list. The list would also show which one is currenly being in use or available for download. If none of the list are installed, you can click Enable button to install the currently highlighted one.

 

While you are doing test with what Sunlight had given to you, if all fails and you see garbage, there is no need to reboot to resolve that, press Ctrl + Alt + Backspace to restart the X (graphics version) of Ubuntu. If that didn't work which is very rare, press Ctrl + Alt + F1, and login as normal user, then

 

sudo su

 

and keyin your user password in order to gain root access. From root command line, you can then

 

kill `ps axuw | grep X | grep auth`

 

The above would restart your X and re-read all your X settings. From there, you can try to troubleshoot again. Let's see

  • Clan Friend
Posted

very good tips Pinoy,

 

I also think that, unless he wants to use the drivers from nvidia's website, there should be no need to uninstall nouveau drivers, since I think they are just blacklisted and they won't conflict, it should be listed in

/etc/modprobe.d/blacklist.conf

or something like that

Posted (edited)

I think the same also Sunlight.

 

Kronos, here I think its better picture.

 

Right click that icon at the right most side of screen where you see your username. This one would appear and click Additional Driver

post-6735-0-14368300-1343494086_thumb.png

 

Then proprietary drivers will be shown like so

post-6735-0-56311900-1343494092_thumb.png

 

Drivers would be downloaded automatically from Nvidia as they are proprietary by nature, Ubuntu doesnt code the drivers that is.

 

This is what I did with my Ubuntu 12.X using Nvidia GT430 only :P but it works Hope this helps

Edited by PiNoY
Posted

Alright so to begin with I didn't have any drivers that showed up under additional drivers. And the enable button was greyed out. I ran

$ sudo apt-get purge nvidia*

to remove the driver, and then

$ sudo apt-get install nvidia-current-updates-dev

to reinstall the driver. After a reboot I still had all the same errors for running et and glxinfo didn't change. But on the plus side the drivers now show up in additional drivers. So then I attempted to remove the drivers again and install them from the nvidia website.

$ sudo sh NVIDIA-installer.run

gave me an error saying I had x server enabled and to stop the x server. So I ctrl alt f1 and then logged into just the plain command line and tried the same thing. Still said I had an x server running

$ sudo service gdm stop

stop: unknown instance

$ sudo service lightdm stop

stop: unknown instance

$ sudo /etc/init.d/lightdm stop

told me to use the service command, but still didn't work.

 

So I guess now I need to find a way to stop the x server before I can manually install the driver, but is the x server actually running if I don't have any gui and I used ctrl alt f1 to get to the command line?

 

Also, now gnome3 is different, I don't understand that. It was fine before and now it's weird looking and has different functions, not really an issue but I thought it was strange.

Posted

For you to go command line, reboot Ubuntu. During the boot with colored background, Ubuntu will give you lines of choices. Select the first line and press E (for edit). This will allow you to edit the line or make the line on edit mode. Simply append into that line the word

 

single

 

then press enter and enter or b to boot using that recently edited line. This process will allow you to boot on command line mode and without X or Gnome. The process will drop you to a command line (CLI) login prompt wherein you can key-in your username and password. From that CLI, you can then continue to

 

sudo sh NVIDIA-installer.run

 

The command above will recompile Nvidia modules that is needed by the kernel. This is on a wizard type recompilation, just asking several questions. If you do not know the answer, simply press Enter. Most questions can easily be understood. After that compilation taking about 10 or more minutes, you will be required to reboot. So reboot normally. Ubuntu will load the Nvidia drivers then. This is how I remember that worked for me.

 

The easy way is kill X :P . Am not sure if this will kill X. Inside X, press Ctrl + Alt + F1, login and issue this command as root

 

kill -9 `ps axuw | grep X | grep auth`

 

or

 

sudo /etc/init.d/gdm stop

 

No warranties expressed or implied, you may use at your own risk :)

Posted

Alright so I'm getting closer haha. Now I've gotten past the x server error, now it's telling me that nouveau is the problem and that it needs to be disabled. nvidia added a file to blacklist it, but after a reboot that failed. So I checked the blacklist.conf and manually added nouveau to the blacklist. After a reboot I still have the same issue. So it looks like now I need to find out how to disable nouveau. Any suggestions?

  • Clan Friend
Posted

Alright so I'm getting closer haha. Now I've gotten past the x server error, now it's telling me that nouveau is the problem and that it needs to be disabled. nvidia added a file to blacklist it, but after a reboot that failed. So I checked the blacklist.conf and manually added nouveau to the blacklist. After a reboot I still have the same issue. So it looks like now I need to find out how to disable nouveau. Any suggestions?

 

before installing the driver from nvidia website, remove nouveau completely

 

$ sudo apt-get --purge remove xserver-xorg-video-nouveau

 

if you go to another virtual console via ctrl+alt+f2, X is still there and you need to close it. To kill the X server you could use the command Pinoy suggested.

Keep in mind that those are backticks/backquotes ` and ' are a different thing in a command

 

maybe you could also try:

$ sudo service lightdm stop

 

but first you have to check if the output of

$ ps axuw | grep X | grep auth

actually has 'lightdm' in it :)

 

the best thing would be to boot straight into the console as root, using that 'single' option in the bootloader, this way you don't need to kill X

 

then when you are finished

reboot -h now

to reboot

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.