Yury Tarasievich <[EMAIL PROTECTED]> writes:
> I don't know what goes in Mandrake package XFree86-W32-3.3.6 (and
> which, contrary to what I saw here, *does* work with at least ET6000
> -- but only when the rest of X is also of version 3.3.6).

You're correct, and my memory must be failing.  The driver existed a
little while in the w32 server, before being moved into svga in late
'96 early '97 (which was when I spent most time on it).  From then on,
the updated support for the et6k was done in the svga server, see
.../vga256/drivers/et4000 if you have the cvs repository available. :)

But back to the problem at hand:

> Could it mingle something in your X version 4.0.3 setup? As someone
> else here pointed out, log contains bogus values for that adapter
> (e.g., it should have maximum pixel clock 135MHz).

The problem is that the log identifies those values as autodetected.
And the driver will correctly identify the source if the values are
specified.  But posting the XF86Config-4 file would certainly help
eliminating that possibility.

> I vaguely remember from my 3.3.* experience that amount of VideoRAM
> should *not* be set in X config file when working with Tseng X
> server. I never succeeded in starting X with that option specified.

It's important not specifying it wrongly.  And the correct value does
not neccessarily coincide with the actual amount of ram. :)  So I
would guess specifying it could easily fail, yes.

(If my memory works today, part of the problem was that there was a
register file or something located just below 4MB, which meant that a
card with the full possible 4MB memory had to have 8kb subtracted from
the memory size in order to work. :)

> So for beginning try removing XFree86-W32 and then reinstalling
> XFree86-4.whatever-you-have-there. After configuring it revise your
> config (comment out VideoRAM directive).

Well, removing the package is probably a good idea anyway.  The
logfile was from XFree86 4.x, though.  And it indicated that there was
no VideoRAM directive, but that should also be verified.

In addition I would probably have tried the card in a Windows-box or
something, to verify that the hardware isn't broken.  Some of the
values in the logfile indicate some serious breakage.

-Harald
-- 
Harald Nordg�rd-Hansen, Linpro AS  <><  http://www.linpro.no/~hnh/
PB. 375, N-1601 Fredrikstad, Norway    Phone/Fax: +47 6935 2424/25
_______________________________________________
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86

Reply via email to