SEO

#1 (**permalink**) 02-21-2008, 05:07 AM

Ok I can't figure out what I might have done.
I had xfree-drm-4.3.0-r6 installed with a 2.4.20
kernel disabled for dri.
It worked for some time.
glxinfo said direct render: yes and appropriate
testing showwed it was doing it's job.

Now glxinfo shows
Xlib: extension "XFree86-DRI" missing on display ":0.0".
and direct rendering: no
I cannot figure what I did to break this.
Anyone with ideas .... appreciated!

--
Reply to innkeepATcapitalDOTnet to email questions.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

#2 (**permalink**) 02-21-2008, 05:07 AM

PenguinsAnonymous wrote:
> Ok I can't figure out what I might have done.
> I had xfree-drm-4.3.0-r6 installed with a 2.4.20
> kernel disabled for dri.
> It worked for some time.
> glxinfo said direct render: yes and appropriate
> testing showwed it was doing it's job.

> Now glxinfo shows
> Xlib: extension "XFree86-DRI" missing on display ":0.0".
> and direct rendering: no
> I cannot figure what I did to break this.

I checked the X logs, all modules except xie
and pex5 appear to load fine (including dri
and glx) and then near the end there is a message
direct render disabled!

I just revisited the spec on this monitor tweaking
the values a little in XF86config.

I vaguely remember reading about a problem about
what display gets grabbed based on the speed of the
machine. Is it possible the disable is due to
using the wrong display?
TIA
-Walt

--
Reply to innkeepATcapitalDOTnet to email questions.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

#3 (**permalink**) 02-21-2008, 05:07 AM

In <3f504151_5@corp.newsgroups.com>, PenguinsAnonymous wrote:

> Ok I can't figure out what I might have done.
> I had xfree-drm-4.3.0-r6 installed with a 2.4.20
> kernel disabled for dri.
> It worked for some time.
> glxinfo said direct render: yes and appropriate
> testing showwed it was doing it's job.
>
> Now glxinfo shows
> Xlib: extension "XFree86-DRI" missing on display ":0.0".
> and direct rendering: no
> I cannot figure what I did to break this.
> Anyone with ideas .... appreciated!

drm is kernel-specific, so if you built a new kernel you
need to reinstall drm.

--
| Microsoft: "A reputation for releasing inferior software will make |
| it more difficult for a software vendor to induce customers to pay |
| for new products or new versions of existing products." |
end

#4 (**permalink**) 02-21-2008, 05:07 AM

D. C. Sessions <dcs@lumbercartel.com> wrote:
> In <3f504151_5@corp.newsgroups.com>, PenguinsAnonymous wrote:

> drm is kernel-specific, so if you built a new kernel you
> need to reinstall drm.

Ok I now have it working, kind of but can't account for
the massive difference.

I was achieving frame rates of around 50 instead of the
native 33. (I do not remember the screen size but thought
I had it maxxed)
Now I'm steady at 208fps with a screen size of 1152x864.
I have a 16meg ati rage128 and a dec PCXAV-YZ 17" monitor.
This combination easily handles 1600x1200 without DRM.
I cannot get past the 1152x864 now with DRM enabled.

It is possible that originally I witnessed it at a lower
screen size and 'assumed' the tweek up to 1600 would
still be working.
Has anyone else noticed an inability to get the larger
screen with DRM enabled?

I did a very poor job of assessing this originally.
Thanks!!

--
Reply to innkeepATcapitalDOTnet to email questions.

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

Direct Render issue