Re: [Mesa3d-dev] Compiling Mesa fbdev/DRI drivers without X installed

[Malte S. <ma...@co...>]

Hi,

thank you for your answer, Dave.

I now compiled the fbdev/DRI drivers on another computer of mine which 
uses an ATI Radeon 9600 Pro (AGP 8x) card. This one has X installed, so 
I compiled mesa almost out-of-the-box (without having to make all those 
changes first), I only changed the DRM_SOURCE_PATH in configs/default 
and I set DRI_DRIVERS to "radeon fb" in configs/linux-solo to only 
compile those modules which I want.

It compiles fine and in the console, after killing X and loading 
agpgart, radeonfb and radeon modules, I can start the sample_server and 
it outputs the following:

[miniglx] probed chipset 0x4150
got MMIOAddress 0x40017000 offset 134217728
shared virtual width is 1280
[drm] added 8192 byte SAREA at 0xe19b5000
[drm] mapped SAREA 0xe19b5000 to 0x4003b000, size 8192
[drm] framebuffer handle = 0xb0000000
[drm] register handle = 0xd7000000
[gart] AGP enabled at 4x
[gart] 8192 kB allocated with handle 0x00000001
[gart] ring handle = 0xd0000000
[gart] ring read ptr handle = 0xd0101000
[gart] vertex/indirect buffers handle = 0xd0102000
[gart] AGP texture map handle = 0xd0302000
Using 8 MB AGP aperture
Using 1 MB for the ring buffer
Using 2 MB for vertex/indirect buffers
Using 1 MB for AGP textures
Will use back buffer at offset 0x600000
Will use depth buffer at offset 0xb00000
Will use 114688 kb for textures at offset 0x1000000
[drm] Added 32 65536 byte vertex/indirect buffers
[drm] dma control initialized, using IRQ 11
[drm] Initialized kernel gart heap manager, 5111808
color tiling disabled
page flipping disabled
[miniglx] Setting mode: visible 1280x1024 virtual 1280x1024x32
[miniglx] Readback mode: visible 1280x1024 virtual 1280x1024x32
RADEONEngineRestore

When I do that, the console gets only black and white (it's in fancy 
colors usually :-), or should I say dark grey and black, for I can 
hardly read what's on the screen anymore, because the letters are almost 
as black as the background, even though I turned the contrast and the 
brightness very high. But whatever! I didn't mind, I was just eager to 
see that rotating quadrilateral with changing colors ;-)

However, when I start miniglxtest, it outputs the following:

[miniglx] probed chipset 0x4150
CreateNotify
Authorize - magic 1
MapRequest
Hang on... drawing 6 frames
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)
UnmapNotify
DestroyNotify
[miniglx] probed chipset 0x4150
CreateNotify
Authorize - magic 2
MapRequest
Hang on... drawing 6 frames
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)
Redraw event
sleep(1)

And I'm back to the prompt, without seeing any fancy OpenGL effects 
whatsoever.

Another thing is that the console slows down to a crawl after 
sample_server has been started, and I have to pay attention not to reach 
the bottom of the screen, as, when that happens and another line is 
written to the screen, my Linux crashes (I can't even log in from the 
LAN anymore!); in other words, it seems that there are problems with 
"scrolling down the screen". But all of this is not so important, I'd 
just like to know why I can't see that quadrilateral, albeit the output 
of miniglxtest looks like it's doing something (even drawing something). 
Did I miss something? Any ideas what's going on? Please help!

Cheers,

Malte

Dave Airlie wrote:

>
>> I recently tried to compile the Mesa fbdev/DRI drivers. Since I do 
>> not have X installed, this seemed to be exactly what I needed.
>>
>> Although the Mesa fbdev/DRI drivers do not require X, it seems that 
>> some X utilities and libs are at least required during the 
>> compilation process. I encountered a few problems which I managed to 
>> fix, and I thought I'd share them here for other people who may want 
>> to compile these drivers and have no X installed.
>>
>>
>> I'm using a 3dfx Voodoo 3 card. Could it be that this one is not yet 
>> supported? That would explain why MINIGLX_SOURCES are commented out 
>> in src/mesa/drivers/dri/tdfx/Makefile, and that "tdfxEngineRestore: 
>> not implemented" message, wouldn't it? Am I better off using a Radeon 
>> card? Any ideas how to fix this?
>
>
> Well you figured it out.. it was commented out because no-one ever 
> finished the code for it... radeon are the only miniglx card I know 
> off that work .. and I don't test it that often, as the project I use 
> them on as long ago picked a version of Mesa and stuck to it... but 
> when I do fix things I fix them in Mesa src as well... I'm going to be 
> porting miniglx to the i915 soon so if it is broken I'll get around to 
> fixing it then..
>
> Dave.
>
>