glxinfo setting to verbose mode outputs no extra info?

[Tech Geek]

Hi,

 

I am using Debian Lenny on a PC. I am trying to figure out why direct rendering is not working so upon giving "glxinfo" command I get:

# glxinfo > glxinfo.txt

name of display: :0.0
display: :0  screen: 0
direct rendering: No (If you want to find out why, try setting LIBGL_DEBUG=verbose)
server glx vendor string: SGI
server glx version string: 1.2
server glx extensions:

.............................

.............................

 

So I set:

# export LIBGL_DEBUG=verbose

 

and then gave the command again:

# glxinfo > glxinfo-debug.txt

 

However, setting to verbose mode did not produce any extra output:

# diff glxinfo.txt glxinfo-debug.txt

 

What did I do wrong?

 

Thanks

[Ron Johnson]

On 2010-03-25 18:53, Tech Geek wrote:
> Hi,
>
> I am using Debian Lenny on a PC. I am trying to figure out why direct
> rendering is not working so upon giving "glxinfo" command I get:
> # glxinfo > glxinfo.txt
> name of display: :0.0
> display: :0 screen: 0
> direct rendering: No (If you want to find out why, try setting

What driver do you use?

> LIBGL_DEBUG=verbose)
> server glx vendor string: SGI
> server glx version string: 1.2

Yeesh. That's old.

$ glxinfo | head -n5

name of display: :0.0
display: :0 screen: 0

direct rendering: Yes
server glx vendor string: NVIDIA Corporation
server glx version string: 1.4

> server glx extensions:
> .............................
> .............................
>
> So I set:
> # export LIBGL_DEBUG=verbose
>
> and then gave the command again:
> # glxinfo > glxinfo-debug.txt
>
> However, setting to verbose mode did not produce any extra output:
> # diff glxinfo.txt glxinfo-debug.txt

me@haggis:~$ LIBGL_DEBUG=verbose glxinfo > foo
me@haggis:~$ glxinfo > bar
me@haggis:~$ dir foo bar
-rw-r--r-- 1 me me 27111 2010-03-25 19:31:10 bar
-rw-r--r-- 1 me me 27111 2010-03-25 19:31:04 foo

Happens to me too.

> What did I do wrong?
>
> Thanks

--
"History does not long entrust the care of freedom to the weak
or the timid." Dwight Eisenhower

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/4BAC00F8...@cox.net

[Tech Geek]

> What driver do you use?

 

Basically I am using ATI Rage Mobility M1 card and Xorg is using "mach64" driver.

 

# lspci | grep VGA
00:04.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M (rev 64)
#

 

# cat /var/log/Xorg.0.log | grep driver
        X.Org XInput driver : 2.0
(==) Matched mach64 for the autoconfigured driver
(==) Assigned the driver to the xf86ConfigLayout
(II) Loading /usr/lib/xorg/modules/drivers//mach64_drv.so
        ABI class: X.Org XInput driver, version 2.0
        ABI class: X.Org XInput driver, version 2.0
(II) MACH64(0): Not using driver mode "1024x768" (mode clock too high)
(II) MACH64(0): Not using driver mode "640x480" (hsync out of range)
#

Thanks

[Ron Johnson]

This link, which I found by Googling "xorg mach64 dri" seems
informative:

https://answers.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+question/4608

--
"History does not long entrust the care of freedom to the weak
or the timid." Dwight Eisenhower

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/4BACA763...@cox.net

[Tech Geek]

Thanks Ron for the link. That was informative. I will try to go that route.

 

But the original question still remains unanswered as to why setting LIBGL_DEBUG=verbose does not produces more ouput as it claims. Should I file a bug report against mesa-utils package?

 

 

[Ron Johnson]

Or look upstream.

--
"History does not long entrust the care of freedom to the weak
or the timid." Dwight Eisenhower

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/4BAD0E9F...@cox.net