I tried to run Briquolo, but it crashed. I believe that my OpenGL installation/configuration may be flawed in some way, or my NVIDIA drivers may be badly installed.

Bug #116382 reported by FSHero
4
Affects Status Importance Assigned to Milestone
briquolo (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: briquolo

I think that the installation of my NVIDIA drivers may be bad / 'broken'.

In System Settings --> Monitor and Display --> Hardware tab, I configured the driver for my graphics card as nvidia proprietary. But then my resolution went from 1024x768 to 640x480 on next X startup. I ran "sudo dpkg-reconfigure xserver-xorg", and that got my resolutions back.

If I run Briquolo in Konsole, the following text comes up:
BRIQUOLO v0.5.5
erreur
Resolution 640x480
Essai r�solution : rMask=8 gMask=8 bMask=8 BPP=32 => Echec
Essai r�solution : rMask=8 gMask=8 bMask=8 BPP=24 => Echec
Video Init error

To exit, I must close Konsole.

When I try a different game, Emilia pinball, I get this error (running it in Konsole):
fshero@fshero-p2:~$ pinball
Couldn't open config file: /home/fshero/.emilia/pinball
Using default values
Initing SDL

0 joysticks were found.
Couldn't set video mode: Couldn't find matching GLX visual
fshero@fshero-p2:~$

ProblemType: Crash
Architecture: i386
Date: Tue May 22 20:05:36 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/games/briquolo
Package: briquolo 0.5.5-1ubuntu1
PackageArchitecture: i386
ProcCmdline: briquolo
ProcCwd: /home/fshero
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: briquolo
StacktraceTop:
 ?? () from /usr/lib/libGL.so.1
 ?? ()
 ?? () from /usr/lib/libGL.so.1
 ?? ()
 ?? () from /usr/lib/libGL.so.1
Uname: Linux fshero-p2 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
FSHero (minesh-fshero-mistry) wrote :
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

Thank you for your bug report.

FSHero:
What is the output of
dpkg -l nvidia-glx\* | grep ii
and
lspci
?

Changed in briquolo:
status: Unconfirmed → Needs Info
Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

FSHero:
Oh and how did you install the binary drivers?

Revision history for this message
FSHero (minesh-fshero-mistry) wrote :

Easy part first... the output of dpkg -l nvidia-glx\* | grep ii

fshero@fshero-p2:~/download$ dpkg -l nvidia-glx\* | grep ii
ii nvidia-glx-legacy 1.0.7184+2.6.20.5-16.28 NVIDIA binary XFree86 4.x/X.Org 'legacy' dri
fshero@fshero-p2:~/download$

(What does that command show, anyway?)

Output of lspci:

fshero@fshero-p2:~/download$ lspci
00:00.0 Host bridge: Intel Corporation 440LX/EX - 82443LX/EX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corporation 440LX/EX - 82443LX/EX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corporation 82371AB/EB/MB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 01)
00:0e.0 Network controller: RaLink RT2561/RT61 802.11g PCI
00:0f.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8029(AS)
01:00.0 VGA compatible controller: nVidia Corporation NV11 [GeForce2 MX/MX 400] (rev a1)

(I think I see where this is going... that first command showed that the drivers are version 71.84. But only recently did NVIDIA 'banish' the Geforce 2 to "legacy status"... is this correct?)

Thanks for the quick reply!

Revision history for this message
FSHero (minesh-fshero-mistry) wrote :
Revision history for this message
FSHero (minesh-fshero-mistry) wrote :

Okay, I need to stretch my memory a bit to explain how I installed the drivers.

First, I went to the Add/Remove Programs. I ensure that the "proprietary software" check-box was ticked. I searched for NVIDIA, then checked the "NVidia binary X.Org 'legacy' driver" option. I clicked "Apply". It seemed to install something.

I then went to System Settings --> Monitor and Display --> Hardware (tab). Under Graphics card, I clicked Configure. In the hierarchical list, I went to Drivers, then nvidia. (I think it was nv, previously.) I Selected the Proprietary radio button, as I thought that this would give me the 3D acceleration I wanted. After applying the settings, restarted the computer.

Upon rebooting, my display showed a 640x480 resolution. (It was a desirable 1024x768, previously). After a bit of searching, I came upon this document:
http://doc.gwos.org/index.php/Latest_nvidia_feisty

After skim-reading it, the instructions seemed simple and logical enough, so I went ahead and followed "Method 1". I followed the instructions to get the Legacy drivers (71.84). Everything went fine, except
sudo nvidia-xconfig --no-composite
This showed an error message of some sort, which I cannot remember. However, I think I tried:
sudo nvidia-xconfig
(i.e. o arguments.) I think this worked -- no error messages came up, as far as I can remember.

I restarted the X-server, but again, my resolution was the sub-optimal 640x480. I read ahead to the troubleshooting section, and read the short section on resolution problems. I followed the link (http://doc.gwos.org/index.php/ChangeResolution), and followed the instructions.

After running "sudo dpkg-reconfigure xserver-xorg" and answering the questions it asked, my resolution was back to 1024x768. I was happy :)

However, I tried to run the aforementioned games (Briquolo, and Emilia pinball). They did not work. Also, when I run K-Menu --> System --> NVIDIA Settings, I get only get a few options (I would have expected more...). See my file attachment, above.

P.S. I will be away from this Ubuntu computer for a week, so I will not be able to reply to this until then. I hope the above helps, nevertheless.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

FSHero:
You don't need to use nvidia-legacy (which is the 7xxx series of drivers). Your card is compatible with nvidia-glx (which is the 96xx series of drivers). See http://us.download.nvidia.com/XFree86/Linux-x86/1.0-9755/README/appendix-a.html . You may have been better served using restricted-manager as mentioned in https://help.ubuntu.com/community/BinaryDriverHowto/Nvidia . The resolution problem is also mentioned on that link and is mentioned in Bug #91292 (although the sudo dpkg-reconfigure xserver-xorg is not mentioned in that bug and is a good tip).

nvidia-settings doesn't work with the nvidia-glx-legacy drivers which is why the window is empty.

Can you uninstall nvidia-glx-legacy, install nvidia-glx, remove the file /lib/linux-restricted-modules/.nvidia_legacy_installed , reboot, log into X. Can you then run glxinfo and glxgears and report back the results? Can you also upload the /etc/X11/xorg.conf and /var/log/Xorg.0.log produced at the end of all this?

This is more of a support query than a bug report though and you may have received a faster/better response using one of the methods described on http://www.ubuntu.com/support/communitysupport rather than bugs.launchpad.net ...

Revision history for this message
FSHero (minesh-fshero-mistry) wrote :

Sorry about the unnecessary posting; I got carried away in my excitement of using Ubuntu... !

Should I still post the mentioned files?

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

FSHero:
Yes if you are following all the instructions in the previous comment...

Revision history for this message
FSHero (minesh-fshero-mistry) wrote :

I did what you said in the post, using "sudo apt-get remove nvidia-glx-legacy", and "sudo apt-get install nvidia-glx". This worked. However, there was no "/lib/linux-restricted-modules/.nvidia_legacy_installed" file. (I only remembered this step after rebooting, though...) I can run my games, and the glxgears!

Attached are the results of glxinfo and glxgears. Also, while glxgears was running, I saw a picture of some gears rotating. (I assume that's normal! :D)

Attached are my:
/etc/X11/xorg.conf
/var/log/Xorg.0.log

Revision history for this message
FSHero (minesh-fshero-mistry) wrote :

Woah, got to add attachments in separate posts.
Attached: /etc/X11/xorg.conf

Revision history for this message
FSHero (minesh-fshero-mistry) wrote :

Attached: /var/log/Xorg.0.log

---

Again, sorry for not consulting the Ubuntu forums. So... when is it appropriate to post a bug report.

Finally, thanks for helping, Sitsofe Wheeler.

Revision history for this message
Sitsofe Wheeler (sitsofe) wrote :

FSHero:
It's not just the forums that you can go to - there's IRC and http://answers.launchpad.net/ too. Generally speaking you file bug reports when you know what is causing the issue and have reproducible steps that _someone else can follow_ to reliably reproduce the issue. This allows you to file the bug in the right package (in this case although you saw a problem with briquolo I suspect the right package was probably linux-restricted-modules-2.6.20). http://live.gnome.org/BugzillaGuidelines contains a good description of what needs to be in a bug report. If it turns out that something that originally looked like a support request turns out to have a clear underlying bug then bugs can be filed.

Thanks for following up on this. Closing because previous comments suggest the issue has been resolved.

Changed in briquolo:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.