Bug 10241 - Xlib: extension "GLX" missing on display ":0.0".
Summary: Xlib: extension "GLX" missing on display ":0.0".
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.2 (2007.02)
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-03-10 04:06 UTC by GNUtoo
Modified: 2008-12-02 23:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
xorg.conf (5.74 KB, text/plain)
2007-03-10 04:07 UTC, GNUtoo
no flags Details
xorg log (42.36 KB, text/plain)
2007-03-10 05:53 UTC, GNUtoo
no flags Details

Description GNUtoo 2007-03-10 04:06:32 UTC
# 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".
Error: couldn't find RGB GLX visual

   visual  x  bf lv rg d st colorbuffer ax dp st accumbuffer  ms  cav
 id dep cl sp sz l  ci b ro  r  g  b  a bf th cl  r  g  b  a ns b eat
----------------------------------------------------------------------
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
0x21 24 tc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None
Xlib:  extension "GLX" missing on display ":0.0".
Xlib:  extension "GLX" missing on display ":0.0".
0x22 24 dc  1  0  0 c  .  .  0  0  0  0  0  0  0  0  0  0  0  0 0 None

my distribution is gentoo
my kernel is the 2.6.20 with DRM for the radeon
my card is:
01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility X700
(PCIE) (prog-if 00 [VGA])
        Subsystem: Sony Corporation Unknown device 81e8
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
        Latency: 0, Cache Line Size: 64 bytes
        Interrupt: pin A routed to IRQ 17
        Region 0: Memory at c8000000 (32-bit, prefetchable) [size=128M]
        Region 1: I/O ports at 5000 [size=256]
        Region 2: Memory at b8100000 (32-bit, non-prefetchable) [size=64K]
        [virtual] Expansion ROM at b8120000 [disabled] [size=128K]
        Capabilities: [50] Power Management version 2
                Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 PME-Enable- DSel=0 DScale=0 PME-
        Capabilities: [58] Express Endpoint IRQ 0
                Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag+
                Device: Latency L0s <256ns, L1 <4us
                Device: AtnBtn- AtnInd- PwrInd-
                Device: Errors: Correctable- Non-Fatal- Fatal- Unsupported-
                Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
                Device: MaxPayload 128 bytes, MaxReadReq 128 bytes
                Link: Supported Speed 2.5Gb/s, Width x16, ASPM L0s L1, Port 0
                Link: Latency L0s <256ns, L1 <2us
                Link: ASPM Disabled RCB 64 bytes CommClk+ ExtSynch-
                Link: Speed 2.5Gb/s, Width x16
        Capabilities: [80] Message Signalled Interrupts: 64bit+ Queue=0/0
Enable-
                Address: 0000000000000000  Data: 0000
        Capabilities: [100] Advanced Error Reporting
Comment 1 GNUtoo 2007-03-10 04:07:19 UTC
Created attachment 9071 [details]
xorg.conf
Comment 2 Michel Dänzer 2007-03-10 05:41:06 UTC
Please attach the full log file.
Comment 3 GNUtoo 2007-03-10 05:53:15 UTC
Created attachment 9072 [details]
xorg log
Comment 4 GNUtoo 2007-03-10 05:59:32 UTC
i compile the xorg-server without ntps
Comment 5 GNUtoo 2007-03-10 06:12:06 UTC
solved emerging with nptl
Comment 6 Adam Jackson 2008-02-24 18:22:29 UTC
Mass reopen.  The "LATER" resolution is lame, I'm deleting it.  Consider LATER to have arrived.
Comment 7 Alex Deucher 2008-12-02 23:51:30 UTC
looks to be fixed.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.