
|
[openbeos]
||
[Date Prev]
[01-2003 Date Index]
[Date Next]
||
[Thread Prev]
[01-2003 Thread Index]
[Thread Next]
[openbeos] Re: accelerant difficulties
- From: François Revol <revol@xxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Sat, 18 Jan 2003 18:03:30 +0100 (CET)
En réponse à Gabe Yoder <gyoder@xxxxxxxxxxx>:
> Lately, I have been working on getting the display driver working for
> the
> actual app_server (no more protos). I seem to be having some
> difficulties
> with working with the graphics device and the accelerant. I am using
> the
> BeOS example harness.c as a reference for getting things working. The
> main
> card in my machine is a geforce 2 MX400, but I also have a pci ati rage
> 2.
> BeOS uses the geforce, and I wish to use the ati for app_server
> development.
> If I look in /dev/graphics, I see 3 entries (one beginning with nv, one
> named
> stub, and a numeric name). If I try to open the numeric one (which I
> presume
> is my ati card), it fails to open (i.e. invalid descriptor). If I try
> to
> open my geforce or stub, I can open the device and I can load the
> accelerant,
> but it fails to find the entry point for the accelerant. Anybody have
> any
> ideas on what the problem is? It's kind of frustrating debugging since
> I
> tend to end up in KDL rather frequently (usually while running my
> driver, but
> once it happened while rebuilding). I am running with Max Edition if
> that is
> of any use.
>
using a 2nd card won't always work... as the driver assumes it's the only
card most of the time.
Btw, nv looks like the nvidia one, stub is the VGA stub driver (which lives
in kernel_intel), which accelerant tries to load old app_server addons and
falls back to polling a virtual 8bpp framebuffer and convert it to 16
grayscale to put it in banked VGA hw.
the numeric one is certainly the ATI one. the prefered name is
%04x_%04x_%02x%02x%02x, the first 2 values being PCI vendor and device id.
About the ATI driver, well, possibly there is a symlink in
~/config/add-ons/kernel/drivers/dev/graphics but not the ati driver in bin/...
else it would get loaded.
try to check syslog and see if it spits out any info.
(didn't you remove the driver to get the nvidia board used in place ?)
you'll get a lot of help from a serial hooked PC to get debug infos while
going to KDL :)
François.
|

|