nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Failed to load glX (http://www.nvnews.net/vbulletin/showthread.php?t=5088)

doctorcam 12-12-02 08:21 PM

Failed to load glX
 
I have version 3123 on my Debian system, and almost everything works. However, XFree86.0.log indicates that glX is not loading, even though the GLX visuals are set up, and the driver loads. The only warning is "Failed to verify AGP usage" -- agpgart is not enabled in the kernel, and the default is to use the nvidia agp code.

There are no other warnings or errors

Anyone have an idea?


TIA

Cam

bwkaz 12-12-02 08:38 PM

Anything in the output of dmesg, or in /var/log/messages? Can you post the full XFree86.0.log?

doctorcam 12-12-02 11:59 PM

1 Attachment(s)
Good point. Hadn't thought about dmesg.

It says:
agpgart: unsupported bridge
agpgart: no supported devices found

This is immediately after the hard and floppy drive checks, so it may not mean much -- that should occur before kerneld loads the modules.

I have tried a couple of different ways to copy XFree86.0.log, without success, so I shall attach it: Be warned -- I set logverbose to 7.

libGL and libGLcore are in /usr/lib, where they are supposed to be, and nvidia_drv.o and libglx are also where the instructions say they are supposed to be.

If it helps, the MB is an ASUS V7N266 -- everything is built in, and I'm using a custom 2.4.19 kernel.

Thanks for this


Cam

doctorcam 12-13-02 08:29 AM

Whoops! Sorry -- wrong motherboard.

It is actually A7N266-VM.

Cheers

Cam

bwkaz 12-13-02 12:48 PM

Hmm, well actually, the motherboard's part number doesn't tell me anything. What's important is the chipset.

However, it seems from the message "unsupported bridge" that your chipset either isn't recognized, or doesn't have any code written for it. If this is an nForce board, then that's probably the problem.

You say you're running a custom 2.4.19 -- when you configured it, did you configure agpgart as a module? If not, then right after the floppy checks is actually the right place (well... more or less) for this kind of message. Even if you built it as a module, it could be that the kernel is just probing for what PCI devices it understands at that point (PCI->AGP bridge chips are PCI devices on bus 0), and the fact that it doesn't understand that device could be passed down to the agpgart.o module anyway.

If agpgart is a module, does adding options agpgart agp_try_unsupported=1 to /etc/modules.conf and running /sbin/depmod -a help at all?

azazello 12-13-02 02:38 PM

it's looks like nForce 420 based motherboard...

you can try to use nvagp driver from nVidia(Option "NvAGP" 1 -> see README form drivers)

Andy Mecham 12-13-02 04:00 PM

If you want to use NVAGP, you'll have to compile AGPGART out of your kernel if it's not a module. NVAGP won't work otherwise.

--andy

doctorcam 12-16-02 12:34 AM

I did not compile agpgart into the kernel, nor did I set it up as a module.

XF86Config-4 has the line:

Option "NvAGP" "1"

And, accordingly, in XFree86.0.log, this appears:

(**) NVIDIA(0): Option "NvAGP" "1"
(**) NVIDIA(0): Use of NVIDIA internal AGP requested
(--) NVIDIA(0): Linear framebuffer at 0xF0000000
(--) NVIDIA(0): MMIO registers at 0xEB000000

It then goes on to set the screen size and bit depth, and then appear the lines:

(II) NVIDIA(0): AGP 4X successfully initialized
(II) NVIDIA(0): Setting mode "1280x1024"
(EE) NVIDIA(0): Failed to load glX


I think maybe it's something else. (?)

Cam

Andy Mecham 12-16-02 11:09 PM

Can you post your /etc/X11/XF86Config-4 and /var/log/XFree86.0.log files?

--andy

doctorcam 12-17-02 05:14 AM

1 Attachment(s)
I don't think you'll want XFree86.0.log included, since verboselog is set to 7. It is attached.

XF86Config-4 appears below. Thank you for looking at this.

Cam


### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# If you want your changes to this file preserved by dexconf, only make changes
# before the "### BEGIN DEBCONF SECTION" line above, and/or after the
# "### END DEBCONF SECTION" line below.
#
# To change things within the debconf section, run the command:
# dpkg-reconfigure xserver-xfree86
# as root. Also see "How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz.

Section "Files"
FontPath "unix/:7100" # local font server
# if the local font server has problems, we can fall back on these
FontPath "/usr/lib/X11/fonts/misc"
# FontPath "/usr/lib/X11/fonts/cyrillic"
FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
FontPath "/usr/lib/X11/fonts/Type1"
FontPath "/usr/lib/X11/fonts/Speedo"
FontPath "/usr/lib/X11/fonts/100dpi"
FontPath "/usr/lib/X11/fonts/75dpi"
FontPath "/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType"
EndSection

Section "Module"
# Load "GLcore"
Load "bitmap"
Load "dbe"
Load "ddc"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "speedo"
Load "type1"
Load "vbe"
EndSection

Section "InputDevice"
Identifier "Generic Keyboard"
Driver "keyboard"
Option "CoreKeyboard"
Option "XkbRules" "xfree86"
Option "XkbModel" "pc101"
Option "XkbLayout" "us"
Option "XkbVariant" "dvorak"
EndSection

Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/psaux"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
EndSection

Section "InputDevice"
Identifier "Generic Mouse"
Driver "mouse"
Option "SendCoreEvents" "true"
Option "Device" "/dev/input/mice"
Option "Protocol" "ImPS/2"
Option "ZAxisMapping" "4 5"
EndSection

Section "Device"
Identifier "nForce"
Driver "nvidia"
BusID "PCI:02:00:00"
VideoRam 32768
Option "NvAgp" "1"
EndSection

Section "Monitor"
Identifier "AOC"
HorizSync 30-92
VertRefresh 50-85
Option "DPMS"
EndSection

Section "Screen"
Identifier "Default Screen"
Device "nForce"
Monitor "AOC"
DefaultDepth 24
SubSection "Display"
Depth 1
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 4
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 8
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 15
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 16
Modes "1280x1024" "1024x768"
EndSubSection
SubSection "Display"
Depth 24
Modes "1280x1024" "1024x768"
EndSubSection
EndSection

Section "ServerLayout"
Identifier "Default Layout"
Screen "Default Screen"
InputDevice "Generic Keyboard"
InputDevice "Configured Mouse"
# InputDevice "Generic Mouse"
EndSection

Section "DRI"
Mode 0666
EndSection

### END DEBCONF SECTION

bwkaz 12-17-02 09:29 AM

You're loading the wrong GLX module. Reference:

Quote:

(II) LoadModule: "glx"
(II) Loading /usr/X11R6/lib/modules/extensions/libglx.a
(II) Module glx: vendor="The XFree86 Project"
compiled for 4.2.1, module version = 1.0.0
ABI class: XFree86 Server Extension, version 0.1
The module it loads should be named /usr/X11R6/lib/modules/extensions/libglx.so instead of .a. However, it is the policy of the X module loader that if a .so file exists with the rest of the name the same, then to load the .so version before it tries the .a version.

So... did you install the NVIDIA_GLX package? It is required... Is there a /usr/X11R6/lib/modules/extensions/libglx.so file on your system? If so, get rid of /usr/X11R6/lib/modules/extensions/libglx.a -- either mv it so it has another name, or mv it to another directory.

doctorcam 12-17-02 10:39 AM

I have libglx.so.1.0.3123 in that directory, with execute permissions. Is that the correct name?

If it is, why would it not be picked up?

I shall mv libglx.a and see what happens

Thank you

Cam


All times are GMT -5. The time now is 06:26 AM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.