Re: [XFree86] W32 and ET6000

2003-01-30 Thread Harald Nordgård-Hansen
Yury Tarasievich [EMAIL PROTECTED] writes:
 I still own ET6000 with famous 2.25Mb feature (or was it notorious
 feature? :)

Well, it was a cheap way of getting 1024x768x24 to run.  Which you
couldn't do on less memory. :)

But is sure caused problems, yes.  Both in detecting the correct
amount of memory (there are quite a few comments about in the driver
still), and getting packet 24bpp to work (which wasn't all that common
at the time).

 In X 3.3.*, I never succeeded in telling it about having 2304Kb of
 memory (VideoRAM 2304 was sure way to have X not started), and
 autodetect always detected 2048Kb, so depriving me of some (seemingly
 present) video modes. I didn't even try VideoRAM directive in 4.* :)
 Were there any Tsengs ET6K with exactly 2048Kb?

Hmm.  Sounds as if you might have had a partly bad card or something
as well.  I seem to remember that specifying the videoram was the
_only_ way to make it work for a while.

But Koen spent quite a lot of time getting the memory detection right,
if you check the driver it will probe roughly for the amount of memory
from the config registers on the chip and then start walking along it
testing the actual boundary.  I think current XFree86 (and late 3.x
XF86_SVGA) will do that correctly for most/all cards.

As for 2MB cards, I never saw any of them at least.  I believe there
was just the 2.25 and 4MB versions available in large numbers.
According to the databook it is possible to set up DRAM-based
configurations with 1, 2 and 4MB, but I don't know of anyone who
shipped them.  With MDRAM-based designs I don't remember anymore if
there existed versions with just 2 memory chips, the controller seems
to be able to handle it.  Mostly I seem to remember the different
designs had different sizes of MDRAMS (different number of banks
inside each chip or something).

 I also never succeeded in adding video memory to my ET6000 adapter. :)

That would probably be a challenge, yes.  You would have to remove the
MDRAMs and replace them with new ones, and probably do some other
modifications as well.

 So what is the XFree86-W32-3.3.6 doing there? Is its presence of any
 significance?

Should be none whatsoever.  Just an added binary in /usr/X11R6/bin
that is not being run. :)  But I don't use Mandrake, so I don't know
what influence it might have on the configuration tools etc.

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.

 I recall now, there can be some combinations of motherboards and
 ET6K's that produce problems. I used ET6000 with some Tomato 430HX MB
 for some time, and it just didn't do bitblits correctly in VGA mode!
 (FUBAR'ed lists, controls backgrounds and alike) Setting up Win95 was
 a real challenge. :)

Ouch. :)

-Harald
-- 
Harald Nordgård-Hansen, Linpro AShttp://www.linpro.no/~hnh/
PB. 375, N-1601 Fredrikstad, NorwayPhone/Fax: +47 6935 2424/25
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



Re: [XFree86] W32 and ET6000

2003-01-29 Thread Yury Tarasievich
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). 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).

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.

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).



Christine wrote:

I've just installe mandrake 8.0, and get a fatal error while booting.  
I've attached the XFree86.0.log.
 
I've installed the various components:
XFree86-server-common
libfont.so.1
libintl.so.2
XFree86-W32-3.3.6-25.1mdk.i586
 
Now I'm not sure where to go from here.
 
Any help would be appreciated!
 
christine



___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



Re: [XFree86] W32 and ET6000

2003-01-29 Thread Harald Nordgård-Hansen
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 AShttp://www.linpro.no/~hnh/
PB. 375, N-1601 Fredrikstad, NorwayPhone/Fax: +47 6935 2424/25
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86



[XFree86] W32 and ET6000

2003-01-27 Thread Christine



hi

I've just installe mandrake 8.0, and get a fatal 
error while booting. I've attached the XFree86.0.log.

I've installed the various components:
XFree86-server-common
libfont.so.1
libintl.so.2
XFree86-W32-3.3.6-25.1mdk.i586

Now I'm not sure where to go from 
here.

Any help would be appreciated!

christine


floppy
Description: Binary data


Re: [XFree86] W32 and ET6000

2003-01-27 Thread Harald Nordgård-Hansen
Christine [EMAIL PROTECTED] writes:
I've just installe mandrake 8.0, and get a fatal error while booting.
I've attached the XFree86.0.log.

Hmm.  I really cannot se just how some of the values from the log file
could arise with a working card, among other things it detects 0MB
available memory on the card, and also the DACSpeed value (Max pixel
clock) is completely wrong.

There have been quite a few improvements to the driver for the et6k
since version 4.0.3, you might want to try a newer version of XFree86
as well.

XFree86-W32-3.3.6-25.1mdk.i586

This server/driver is not for the et6k, only for some et4k-based
cards.  Don't use it here.  (It isn't used currently either. :)

It might help if you sent the contents of /etc/X11/XF86Config-4 to see
if there is something wrong specified there.

Part of the problem is that I don't think there are any developers
left with a working et6k card to test things on.  So the driver are
slowly getting less and less updates.  Common problem with
sufficiently old hardware, sadly.

-Harald
-- 
Harald Nordgård-Hansen, Linpro AShttp://www.linpro.no/~hnh/
PB. 375, N-1601 Fredrikstad, NorwayPhone/Fax: +47 6935 2424/25
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86