Re: 3gl working extremely slow.

2000-11-11 Thread Seth Arnold

* Gordon Heydon <[EMAIL PROTECTED]> [00 23:06]:
> I am having some problem getting 3gl to work correctly on my matrox
> g400. I have installed the mesa drivers that come with the XFree 4.0.1
> debs, and I have also gotting the libglu from the current unstable
> version of mesa.

Gordon, getting everything right is damn near impossible. Thank your own
deity that Branden has done most of the work for us already. :)
Currently, I don't use libGLU, but copying the one libGLU library out of
the package is probably sufficient.

What I have found about getting my g400Max to do GLX is that it requires
using XFree86's mga_drv.o driver, loading the agpgart and mga kernel
modules (I use 2.4.0-test10 with good success, and perhaps
2.2.18-presomething would have the same effect, but that may require
kernel drivers from dri.sourceforge.net) and having the right mix of
packages installed. I don't think it takes any of the mesa packages.

To get the g400Max to do dual-head requires using matrox's mga_drv.o
file. I'm not sure if agpgart and mga need to be unloaded or not from
the kernel, but I do, to save memory.

You will also need to tweak your XF86Config-4 file to load the glx, dri,
GLCore, and dbe modules. (I have two config files, one to describe both
monitors, one to describe only one monitor, and I switch between the two
when I want GL to work.)

Yes, it is a bit annoying, but not enough to cause me to learn how to
program these things for the accelerated OpenGL while running dual-head.

HTH

Some useful package information:

$ dpkg -l '*mesa*'  
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name   VersionDescription
+++-==-==-
un  mesa-dev(no description available)
pn  mesademos   (no description available)
pn  mesag-dev   (no description available)
pn  mesag-glide2-d  (no description available)
pn  mesag-widgets-  (no description available)
pn  mesag3  (no description available)
pn  mesag3+ggi  (no description available)
pn  mesag3+ggi-dev  (no description available)
un  mesag3-glide(no description available)
pn  mesag3-glide2   (no description available)
pn  mesag3-widgets  (no description available)
ii  xlibmesa3  4.0.1-1XFree86 version of Mesa 3D graphics library
ii  xlibosmesa34.0.1-1XFree86 version of Mesa off-screen rendering

$ dpkg -l 'x*' | grep 4.0 
ii  xbase-clients  4.0.1-1miscellaneous X clients
ii  xfonts-75dpi   4.0.1-175 dpi fonts for X
ii  xfonts-base4.0.1-1standard fonts for X
ii  xfonts-pex 4.0.1-1fonts for minimal PEX support in X
ii  xfonts-scalabl 4.0.1-1scalable fonts for X
ii  xfree86-common 4.0.1-1X Window System (XFree86) infrastructure
ii  xfwp   4.0.1-1X firewall proxy server
ii  xlib6g 4.0.1-1pseudopackage providing X libraries
ii  xlib6g-dev 4.0.1-1pseudopackage providing X library developmen
ii  xlibmesa3  4.0.1-1XFree86 version of Mesa 3D graphics library
ii  xlibosmesa34.0.1-1XFree86 version of Mesa off-screen rendering
ii  xlibs  4.0.1-1X Window System client libraries
ii  xlibs-dev  4.0.1-1X Window System client library development f
ii  xnest  4.0.1-1nested X server
ii  xprt   4.0.1-1X print server
ii  xserver-common 4.0.1-1files and utilities common to all X servers
ii  xserver-xfree8 4.0.1-1the XFree86 X server
ii  xterm  4.0.1-1X terminal emulator
ii  xutils 4.0.1-1XFree86 utility programs
ii  xvfb   4.0.1-1virtual framebuffer X server



-- 
``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really
impressed down here, I can tell you.''


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




3gl working extremely slow.

2000-11-11 Thread Gordon Heydon

hello,

I am having some problem getting 3gl to work correctly on my matrox
g400. I have installed the mesa drivers that come with the XFree 4.0.1
debs, and I have also gotting the libglu from the current unstable
version of mesa.

The problem comes when I run the new enlightenment 3gl programs such as
evas and in hardware mode it is jumpy and seems to only about 1 or 2
frames per second. I am not too sure what is wrong as I have seen some
other people who are getting much much higher frame rates.

I home someone can help me.

Thanks
Gordon.


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




object backingstore in latest X4

2000-11-11 Thread Michael Perry
HI all-

I recently upgraded my potato laptop to woody and also did kde2 and Xfree86
4.0.1 from the unstable debs. One application I use often is win4lin and it
relies on a option setting in /etc/X11/XF86Config called backingstore so
that linux windows that overlay it when running in a window do not write
over the win4lin window.  As an example, if I start win4lin and I then open
a eterm over it, it will retain a blackened out shape of the application.
In the first upgrade I did for X, backingstore operated correctly.  Now if I
run xdpyinfo | grep back it shows it activated but it does not seem to
effect the overlying of windows.

FWIW, win4lin provides windows 98 application support either in a window on
the linux desktop or fullscreen.  The win4lin support archives/faq mention
that to get win4lin working on xfree86 4, one must use the backingstore
option.

Thanks.

-- 
Michael Perry
[EMAIL PROTECTED]
-



Re: Package pools, testing, 2.2r2

2000-11-11 Thread Wichert Akkerman
Previously Anthony Towns wrote:
> All who're interested: katie (ie, the new dinstall, ie package pools)
> will be rolled out when James has enough time to cope with any unforseen
> problems. Hopefully in the next week or two. "testing" will be rolled out
> shortly afterwards, in all probability.

Do you realize this will break dselect for everyone who uses apt
currently? I suggest you hold off doing this until we see if that
can be fixed.

Wichert.

-- 
   
 / Generally uninteresting signature - ignore at your convenience  \
| [EMAIL PROTECTED]  http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |



Package pools, testing, 2.2r2

2000-11-11 Thread Anthony Towns
Hello world,

debian-cd folk: 2.2r1 is final, even if that'll make some of the powerpc
and security folk (justifiably) unhappy. If you'd like to update the
potato CD images, that'd probably be a good thing.

All who're interested: katie (ie, the new dinstall, ie package pools)
will be rolled out when James has enough time to cope with any unforseen
problems. Hopefully in the next week or two. "testing" will be rolled out
shortly afterwards, in all probability.

debian-cd folk: when katie is rolled out, the debian-cd scripts will
probably break [0], it'd be very helpful if this can be fixed ASAP,
otherwise we won't be able to provide official CDs for 2.2r2...

Porters, X folks, etc: 2.2r2 is likely to come out relatively
quickly. Please consider this as your notification, and upload any ports
or security fixes or new versions that should make it into r2 sooner
rather than later.

For those who're interested: we'll see about handling 2.2r2 in a more
transparent manner. I'll try to keep auric:~ajt/which-updates as an up
to date list of which will get accepted and why others will get rejected,
and have it posted automatically to -release once a week. Comments etc
should go to -release.

Cheers,
aj

[0] Since the Packages files will start referencing packages and
sources in the pool, rather than under dists/potato/... This is
actually unavoidable, but we'll try to make sure there are at
least symlinks from dists/potato to the pool for anything missing,
FWIW. The Packages/Sources files may or may not end up pointing at
the symlinks rather than the pool. This will probably first happen
sometime after the changeover, but will definitely happen during
2.2r2.

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

  ``We reject: kings, presidents, and voting.
 We believe in: rough consensus and working code.''
  -- Dave Clark


pgpV51YoPdJPK.pgp
Description: PGP signature


object backingstore in latest X4

2000-11-11 Thread Michael Perry

HI all-

I recently upgraded my potato laptop to woody and also did kde2 and Xfree86
4.0.1 from the unstable debs. One application I use often is win4lin and it
relies on a option setting in /etc/X11/XF86Config called backingstore so
that linux windows that overlay it when running in a window do not write
over the win4lin window.  As an example, if I start win4lin and I then open
a eterm over it, it will retain a blackened out shape of the application.
In the first upgrade I did for X, backingstore operated correctly.  Now if I
run xdpyinfo | grep back it shows it activated but it does not seem to
effect the overlying of windows.

FWIW, win4lin provides windows 98 application support either in a window on
the linux desktop or fullscreen.  The win4lin support archives/faq mention
that to get win4lin working on xfree86 4, one must use the backingstore
option.

Thanks.

-- 
Michael Perry
[EMAIL PROTECTED]
-


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: Package pools, testing, 2.2r2

2000-11-11 Thread Wichert Akkerman

Previously Anthony Towns wrote:
> All who're interested: katie (ie, the new dinstall, ie package pools)
> will be rolled out when James has enough time to cope with any unforseen
> problems. Hopefully in the next week or two. "testing" will be rolled out
> shortly afterwards, in all probability.

Do you realize this will break dselect for everyone who uses apt
currently? I suggest you hold off doing this until we see if that
can be fixed.

Wichert.

-- 
   
 / Generally uninteresting signature - ignore at your convenience  \
| [EMAIL PROTECTED]  http://www.liacs.nl/~wichert/ |
| 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0  2805 3CB8 9250 2FA3 BC2D |


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Package pools, testing, 2.2r2

2000-11-11 Thread Anthony Towns

Hello world,

debian-cd folk: 2.2r1 is final, even if that'll make some of the powerpc
and security folk (justifiably) unhappy. If you'd like to update the
potato CD images, that'd probably be a good thing.

All who're interested: katie (ie, the new dinstall, ie package pools)
will be rolled out when James has enough time to cope with any unforseen
problems. Hopefully in the next week or two. "testing" will be rolled out
shortly afterwards, in all probability.

debian-cd folk: when katie is rolled out, the debian-cd scripts will
probably break [0], it'd be very helpful if this can be fixed ASAP,
otherwise we won't be able to provide official CDs for 2.2r2...

Porters, X folks, etc: 2.2r2 is likely to come out relatively
quickly. Please consider this as your notification, and upload any ports
or security fixes or new versions that should make it into r2 sooner
rather than later.

For those who're interested: we'll see about handling 2.2r2 in a more
transparent manner. I'll try to keep auric:~ajt/which-updates as an up
to date list of which will get accepted and why others will get rejected,
and have it posted automatically to -release once a week. Comments etc
should go to -release.

Cheers,
aj

[0] Since the Packages files will start referencing packages and
sources in the pool, rather than under dists/potato/... This is
actually unavoidable, but we'll try to make sure there are at
least symlinks from dists/potato to the pool for anything missing,
FWIW. The Packages/Sources files may or may not end up pointing at
the symlinks rather than the pool. This will probably first happen
sometime after the changeover, but will definitely happen during
2.2r2.

-- 
Anthony Towns <[EMAIL PROTECTED]> 
I don't speak for anyone save myself. GPG signed mail preferred.

  ``We reject: kings, presidents, and voting.
 We believe in: rough consensus and working code.''
  -- Dave Clark

 PGP signature


Xkb options: docs ?

2000-11-11 Thread Pierfrancesco Caci

Where can I find a description of the different options for Xkb extentions?

I have some difficulties getting the right keys in the right place :-)

Pf

-- 

---
 Pierfrancesco Caci | ik5pvx | mailto:[EMAIL PROTECTED]  -  
http://gusp.dyndns.org
  Firenze - Italia  | Office for the Complication of Otherwise Simple Affairs 
 Linux penny 2.4.0-test10 #1 Wed Nov 8 22:58:01 CET 2000 i686 unknown



module documentation

2000-11-11 Thread Dan Christensen
Is there documentation available which describes the various modules
that can be loaded into XFree 86, what they do, and what size they
are?  The version of dexter in the 4.0.1-3 debian package produces an
XF86Config file that loads all sorts of modules by default, and as a
result my X server consumes a lot of memory.  I was able to cut 2 or 3
Meg by omitted things that I know aren't relevant to me, but I don't
know about the rest.

If such documentation isn't available, maybe just comments in the
XF86Config file that dexter produces would be enough, so a user
could easily customize it.

Two modules in particular that I am wondering about are dbe and
record.  And is glx only helpful if your video card supports dri?

Dan



Xkb options: docs ?

2000-11-11 Thread Pierfrancesco Caci


Where can I find a description of the different options for Xkb extentions?

I have some difficulties getting the right keys in the right place :-)

Pf

-- 

---
 Pierfrancesco Caci | ik5pvx | mailto:[EMAIL PROTECTED]  -  http://gusp.dyndns.org
  Firenze - Italia  | Office for the Complication of Otherwise Simple Affairs 
 Linux penny 2.4.0-test10 #1 Wed Nov 8 22:58:01 CET 2000 i686 unknown


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




woody 4.0.1-3 debs on potato

2000-11-11 Thread Charl P. Botha
Dear Debian-X'ers,

I have built the woody xfree86 4.0.1-3 debs on potato.  The HOWTO is now
available at:
http://cpbotha.net/building_woody_xfree86_4.0.1_debs_on_potato.HOWTO
and also still at:
http://cpbotha.net/building_brandens_phase2_debs_on_potato.HOWTO

The DEBs I built are TEMPORARILY available via apt, use the following source
lines in your /etc/apt/sources.list:
deb http://www.cg.its.tudelft.nl/%7Ecpbotha/local_debs/ cpbotha/i386/
deb http://www.cg.its.tudelft.nl/%7Ecpbotha/local_debs/ cpbotha/all/

I have NOT tested these yet, I will do so on Monday.  Just remember: Trust
in Branden. :) (But for Heaven's sake, do NOT mail him).

Keep well,

-- 
charl p. botha  | computer graphics and cad/cam 
http://cpbotha.net/ | http://www.cg.its.tudelft.nl/



Re: 16bpp @ 1024x768 with ct65554?

2000-11-11 Thread Branden Robinson
On Sun, Nov 12, 2000 at 01:08:07AM +0900, Taketoshi Sano wrote:
> You can read available options for chips driver in V4 Xserver
> at 

Just FYI, these HTML manpages have gone away as of the latest XFree86
upload.

However, you can still access the same documentation with:

man chips

-- 
G. Branden Robinson |   What influenced me to atheism was
Debian GNU/Linux|   reading the Bible cover to cover.
[EMAIL PROTECTED]  |   Twice.
http://www.debian.org/~branden/ |   -- J. Michael Straczynski


pgpPfMiGfuJge.pgp
Description: PGP signature


module documentation

2000-11-11 Thread Dan Christensen

Is there documentation available which describes the various modules
that can be loaded into XFree 86, what they do, and what size they
are?  The version of dexter in the 4.0.1-3 debian package produces an
XF86Config file that loads all sorts of modules by default, and as a
result my X server consumes a lot of memory.  I was able to cut 2 or 3
Meg by omitted things that I know aren't relevant to me, but I don't
know about the rest.

If such documentation isn't available, maybe just comments in the
XF86Config file that dexter produces would be enough, so a user
could easily customize it.

Two modules in particular that I am wondering about are dbe and
record.  And is glx only helpful if your video card supports dri?

Dan


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




woody 4.0.1-3 debs on potato

2000-11-11 Thread Charl P. Botha

Dear Debian-X'ers,

I have built the woody xfree86 4.0.1-3 debs on potato.  The HOWTO is now
available at:
http://cpbotha.net/building_woody_xfree86_4.0.1_debs_on_potato.HOWTO
and also still at:
http://cpbotha.net/building_brandens_phase2_debs_on_potato.HOWTO

The DEBs I built are TEMPORARILY available via apt, use the following source
lines in your /etc/apt/sources.list:
deb http://www.cg.its.tudelft.nl/%7Ecpbotha/local_debs/ cpbotha/i386/
deb http://www.cg.its.tudelft.nl/%7Ecpbotha/local_debs/ cpbotha/all/

I have NOT tested these yet, I will do so on Monday.  Just remember: Trust
in Branden. :) (But for Heaven's sake, do NOT mail him).

Keep well,

-- 
charl p. botha  | computer graphics and cad/cam 
http://cpbotha.net/ | http://www.cg.its.tudelft.nl/


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 16bpp @ 1024x768 with ct65554?

2000-11-11 Thread Branden Robinson

On Sun, Nov 12, 2000 at 01:08:07AM +0900, Taketoshi Sano wrote:
> You can read available options for chips driver in V4 Xserver
> at 

Just FYI, these HTML manpages have gone away as of the latest XFree86
upload.

However, you can still access the same documentation with:

man chips

-- 
G. Branden Robinson |   What influenced me to atheism was
Debian GNU/Linux|   reading the Bible cover to cover.
[EMAIL PROTECTED]  |   Twice.
http://www.debian.org/~branden/ |   -- J. Michael Straczynski

 PGP signature


Re: [storm@tux.org: XFree 4.0.1 debs]

2000-11-11 Thread Bradley M Alexander
On Sat, Nov 11, 2000 at 12:41:31PM +0100, Rafal Krzewski wrote:
> 
> try running X with startx -- +xinerama, or add +xinerama parameter
> to /etc/X11/xinit/xserverrc and see if it helps.

I have done both. I added +xinerama to xserverrc before I started playing
with backgrounds, and hence before I noticed the problem. Yesterday, I
killed xdm and did a startx -- +xinerama to see if it was a problem with
xdm only.

Originally I thought it was an enlightenment problem because I only had the
wide backgrounds set up in E, and it was only a desk0 problem. Now that I
got random backgrounds for the xdm login screen, I am also seeing it there.

The only diffs in the config that I know of are the 4.0.0 -> 4.0.1 and the
compile from source -> using the debs. (and it is *far* less of a headache
to work from the debs. :)


-- 
--Brad

Bradley M. Alexander, CISSP  |   Co-Chairman,
Beowulf System Admin/Security Specialist |NoVALUG/DCLUG Security SIG
Winstar Telecom  |   [EMAIL PROTECTED]
(703) 889-1049   |   [EMAIL PROTECTED]

Smoking kills, and if you're killed, you've lost a very important part of
your life."
-- Anti-smoking spokesperson Brooke Shields



Re: dexter and microsoft wheelmouse optical ?

2000-11-11 Thread SPENER Christian
ok, the problem was, that the mouse won't work, if gpm is started.
with /etc/init.d/gpm stop bevor startx the mouse works,
shouldn't this done by startx?
chris

> hi i use the microsoft wheelmouse optical and isntalled a new woody with
> 4.0.1-2 debs, didn't have 3.3.6 on this computer before!
> so gpm works without any problem, but under dexter none of the mouse
> drivers r working under X.
> the mouse worked for me under the pre2 4.0.1 debs, so the mouse works
> under X, so this is should not be an XF4.0.1 problem, more a dexter
> problem, or?
> thx
> chris
> p.s.: the mouse port is the same under gpm an X, so it must be correct :-)
> ---
> SPENER Christian
> e-mail: [EMAIL PROTECTED]
> snail-mail: A-8010 GRAZ, Schanzelgasse 19
> tel: ++43 316 362283 cell phone: ++43 664 3846526
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 



Re: 16bpp @ 1024x768 with ct65554?

2000-11-11 Thread Taketoshi Sano
Hi.

In <[EMAIL PROTECTED]>,
  on Fri, 10 Nov 2000 12:15:55 -0500,
on Re: 16bpp @ 1024x768 with ct65554?,
 "Thomas R. Shemanske" <[EMAIL PROTECTED]> wrote:

> I am only trying to drive the LCD so the hsync and vrefresh can be
> arbitrary as far as I know, although they were 30-70 (H) and 50-100(V)
> in the 8 bit run.

As far as I've heard, most of built-in (not analog-connected-external) 
LCDs has fixed hsync and vrefresh setting.  And the driver code in 
X server uses these setting as the limit of clock timings.

So you should be careful to choose the correct setting.

> I have tried UseModeline option.  In 8bit, it gives me a warm pale blue
> (striped) screen and in 16bpp it gives a black vertical band along the
> left side of the screen (about 15% wide), and the rest white (with one
> or more vertical lines)

Without UseModeline, C&T driver just use the dotclock setting in modeline
as the base information, and calculates other settings by that.

With UseModeline option, all the information in modelines are used.
So if you have problem with UseModeline option, then the information
in modeline other than dotclock is not the correct setting.

The result that you descrived above implies that in 8bit the used
modeline is completely out of range, and in 16bit the used modeline
is not correct horizontal timings but vertical timings maybe not so
bad.

So the log in 8bit
  (**) CHIPS(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
shows this is not correct setting, but the log in 16bit
shows this is closer to right setting.

In this case, you should tune just the dotclock setting and hsync/vrefresh
in your XF86Config-4 file without UseModeline option.

> I have enclosed (below) my XF86Config-4 file and the XFree86.0.log from
> a 16bpp run.  I tried to use the data above to build a modeline, but
> obviously I am not doing something right.

Checked.

> Section "Device"
>   Identifier  "Generic Graphics Device"
>   Driver "chips"
> # Option"XaaNoCPUToScreenColorExpandFill"
> # Option"NoAccel"
> # Option "FPClock16" "75 MHz"
> # Option "SetMClk" "55 MHz"
>   Option "NoStretch"
> # Option "LcdCenter"
> EndSection

You can read available options for chips driver in V4 Xserver
at 

Option SetMClk is removed, and new options FPClock8, FPClock16,
FPClock24, and FPClock32 are added.  Maybe you can use these
to order a specific Video Clock speed.  When you enable the
FPClock16 option, are there any difference in the X log ?
How it goes with "FPClock16" "77.1" option ?

Maybe the second "[EMAIL PROTECTED]" modeline is not deleted ?

>   HorizSync   30-70
>   VertRefresh 50-120
> 
>   ModeLine "[EMAIL PROTECTED]" 94.5 1024 1072 1168 1376 768 769 772 808
>   ModeLine "[EMAIL PROTECTED]" 73.78 1024 1072 1168 1376 768 769 772 808

> (--) CHIPS(0): Dot clock 0:  25.172 MHz
> (--) CHIPS(0): Dot clock 1:  28.325 MHz CRTclk
> (--) CHIPS(0): Dot clock 2:  65.082 MHz FPclk
> (--) CHIPS(0): Probed memory clock of  40.090 MHz
> (==) CHIPS(0): Min pixel clock is  11.000 MHz
> (--) CHIPS(0): Max pixel clock is  56.125 MHz
> (II) CHIPS(0): FP clock set to  50.512 MHz

This shows "Max pixel clock is 56.125 MHz", and it is much less
than the specified setting in both of modelines above (94.5 and
73.78) so these lines are removed.

> (II) CHIPS(0): Generic Monitor: Using hsync range of 30.00-70.00 kHz
> (II) CHIPS(0): Generic Monitor: Using vrefresh range of 50.00-120.00 Hz
> (II) CHIPS(0): Clock range:  11.00 to  56.12 MHz
> (WW) CHIPS(0): Mode "[EMAIL PROTECTED]" deleted (bad mode
> clock/interlace/doublescan)
> (WW) CHIPS(0): Mode "[EMAIL PROTECTED]" deleted (bad mode
> clock/interlace/doublescan)

> (--) CHIPS(0): Virtual size is 800x600 (pitch 800)
> (**) CHIPS(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz

49.5MHz is within a range of 56.125, so this mode is enabled.

You should find a setting to use 1024x600 under the limit of 56.125MHz
or use new option FPClock16 to extend the maxpixelclock (But it can
burn your video circuit, at lease I've told so).

Maybe you can try:
  ModeLine "[EMAIL PROTECTED]" 55.6 1024 1072 1168 1376 768 769 772 808
I'm not sure if this works or not.  But this modeline will not be 
deleted in X log.  Perhaps you have to lower the vertrefresh limit
to 40 or so to enable this modeline...

BTW, You wrote that in 8bpp without UseModeline:

(--) CHIPS(0): Dot clock 0:  25.172 MHz
(--) CHIPS(0): Dot clock 1:  28.325 MHz CRTclk
(--) CHIPS(0): Dot clock 2:  65.082 MHz FPclk
(--) CHIPS(0): Probed memory clock of  40.090 MHz
(==) CHIPS(0): Min pixel clock is  11.000 MHz
(--) CHIPS(0): Max pixel clock is  95.000 MHz

(--) CHIPS(0): Virtual size is 1024x768 (pitch 1024)
(**) CHIPS(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(**) CHIPS(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz

(II) CHIPS(0): Generic Monitor: Using hsync range of 30.00-70.00 kHz
(II) CHIPS(0): Generic Monitor: Using vrefresh range of 50.00

dexter and microsoft wheelmouse optical ?

2000-11-11 Thread SPENER Christian
hi i use the microsoft wheelmouse optical and isntalled a new woody with
4.0.1-2 debs, didn't have 3.3.6 on this computer before!
so gpm works without any problem, but under dexter none of the mouse
drivers r working under X.
the mouse worked for me under the pre2 4.0.1 debs, so the mouse works
under X, so this is should not be an XF4.0.1 problem, more a dexter
problem, or?
thx
chris
p.s.: the mouse port is the same under gpm an X, so it must be correct :-)
---
SPENER Christian
e-mail: [EMAIL PROTECTED]
snail-mail: A-8010 GRAZ, Schanzelgasse 19
tel: ++43 316 362283 cell phone: ++43 664 3846526



Re: [storm@tux.org: XFree 4.0.1 debs]

2000-11-11 Thread Bradley M Alexander

On Sat, Nov 11, 2000 at 12:41:31PM +0100, Rafal Krzewski wrote:
> 
> try running X with startx -- +xinerama, or add +xinerama parameter
> to /etc/X11/xinit/xserverrc and see if it helps.

I have done both. I added +xinerama to xserverrc before I started playing
with backgrounds, and hence before I noticed the problem. Yesterday, I
killed xdm and did a startx -- +xinerama to see if it was a problem with
xdm only.

Originally I thought it was an enlightenment problem because I only had the
wide backgrounds set up in E, and it was only a desk0 problem. Now that I
got random backgrounds for the xdm login screen, I am also seeing it there.

The only diffs in the config that I know of are the 4.0.0 -> 4.0.1 and the
compile from source -> using the debs. (and it is *far* less of a headache
to work from the debs. :)


-- 
--Brad

Bradley M. Alexander, CISSP  |   Co-Chairman,
Beowulf System Admin/Security Specialist |NoVALUG/DCLUG Security SIG
Winstar Telecom  |   [EMAIL PROTECTED]
(703) 889-1049   |   [EMAIL PROTECTED]

Smoking kills, and if you're killed, you've lost a very important part of
your life."
-- Anti-smoking spokesperson Brooke Shields


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: dexter and microsoft wheelmouse optical ?

2000-11-11 Thread SPENER Christian

ok, the problem was, that the mouse won't work, if gpm is started.
with /etc/init.d/gpm stop bevor startx the mouse works,
shouldn't this done by startx?
chris

> hi i use the microsoft wheelmouse optical and isntalled a new woody with
> 4.0.1-2 debs, didn't have 3.3.6 on this computer before!
> so gpm works without any problem, but under dexter none of the mouse
> drivers r working under X.
> the mouse worked for me under the pre2 4.0.1 debs, so the mouse works
> under X, so this is should not be an XF4.0.1 problem, more a dexter
> problem, or?
> thx
> chris
> p.s.: the mouse port is the same under gpm an X, so it must be correct :-)
> ---
> SPENER Christian
> e-mail: [EMAIL PROTECTED]
> snail-mail: A-8010 GRAZ, Schanzelgasse 19
> tel: ++43 316 362283 cell phone: ++43 664 3846526
> 
> 
> --  
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: 16bpp @ 1024x768 with ct65554?

2000-11-11 Thread Taketoshi Sano

Hi.

In <[EMAIL PROTECTED]>,
  on Fri, 10 Nov 2000 12:15:55 -0500,
on Re: 16bpp @ 1024x768 with ct65554?,
 "Thomas R. Shemanske" <[EMAIL PROTECTED]> wrote:

> I am only trying to drive the LCD so the hsync and vrefresh can be
> arbitrary as far as I know, although they were 30-70 (H) and 50-100(V)
> in the 8 bit run.

As far as I've heard, most of built-in (not analog-connected-external) 
LCDs has fixed hsync and vrefresh setting.  And the driver code in 
X server uses these setting as the limit of clock timings.

So you should be careful to choose the correct setting.

> I have tried UseModeline option.  In 8bit, it gives me a warm pale blue
> (striped) screen and in 16bpp it gives a black vertical band along the
> left side of the screen (about 15% wide), and the rest white (with one
> or more vertical lines)

Without UseModeline, C&T driver just use the dotclock setting in modeline
as the base information, and calculates other settings by that.

With UseModeline option, all the information in modelines are used.
So if you have problem with UseModeline option, then the information
in modeline other than dotclock is not the correct setting.

The result that you descrived above implies that in 8bit the used
modeline is completely out of range, and in 16bit the used modeline
is not correct horizontal timings but vertical timings maybe not so
bad.

So the log in 8bit
  (**) CHIPS(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
shows this is not correct setting, but the log in 16bit
shows this is closer to right setting.

In this case, you should tune just the dotclock setting and hsync/vrefresh
in your XF86Config-4 file without UseModeline option.

> I have enclosed (below) my XF86Config-4 file and the XFree86.0.log from
> a 16bpp run.  I tried to use the data above to build a modeline, but
> obviously I am not doing something right.

Checked.

> Section "Device"
>   Identifier  "Generic Graphics Device"
>   Driver "chips"
> # Option"XaaNoCPUToScreenColorExpandFill"
> # Option"NoAccel"
> # Option "FPClock16" "75 MHz"
> # Option "SetMClk" "55 MHz"
>   Option "NoStretch"
> # Option "LcdCenter"
> EndSection

You can read available options for chips driver in V4 Xserver
at 

Option SetMClk is removed, and new options FPClock8, FPClock16,
FPClock24, and FPClock32 are added.  Maybe you can use these
to order a specific Video Clock speed.  When you enable the
FPClock16 option, are there any difference in the X log ?
How it goes with "FPClock16" "77.1" option ?

Maybe the second "1024x768@16bpp" modeline is not deleted ?

>   HorizSync   30-70
>   VertRefresh 50-120
> 
>   ModeLine "1024x768@16bpp" 94.5 1024 1072 1168 1376 768 769 772 808
>   ModeLine "1024x768@16bpp" 73.78 1024 1072 1168 1376 768 769 772 808

> (--) CHIPS(0): Dot clock 0:  25.172 MHz
> (--) CHIPS(0): Dot clock 1:  28.325 MHz CRTclk
> (--) CHIPS(0): Dot clock 2:  65.082 MHz FPclk
> (--) CHIPS(0): Probed memory clock of  40.090 MHz
> (==) CHIPS(0): Min pixel clock is  11.000 MHz
> (--) CHIPS(0): Max pixel clock is  56.125 MHz
> (II) CHIPS(0): FP clock set to  50.512 MHz

This shows "Max pixel clock is 56.125 MHz", and it is much less
than the specified setting in both of modelines above (94.5 and
73.78) so these lines are removed.

> (II) CHIPS(0): Generic Monitor: Using hsync range of 30.00-70.00 kHz
> (II) CHIPS(0): Generic Monitor: Using vrefresh range of 50.00-120.00 Hz
> (II) CHIPS(0): Clock range:  11.00 to  56.12 MHz
> (WW) CHIPS(0): Mode "1024x768@16bpp" deleted (bad mode
> clock/interlace/doublescan)
> (WW) CHIPS(0): Mode "1024x768@16bpp" deleted (bad mode
> clock/interlace/doublescan)

> (--) CHIPS(0): Virtual size is 800x600 (pitch 800)
> (**) CHIPS(0): Default mode "800x600": 49.5 MHz, 46.9 kHz, 75.0 Hz

49.5MHz is within a range of 56.125, so this mode is enabled.

You should find a setting to use 1024x600 under the limit of 56.125MHz
or use new option FPClock16 to extend the maxpixelclock (But it can
burn your video circuit, at lease I've told so).

Maybe you can try:
  ModeLine "1024x768@16bpp" 55.6 1024 1072 1168 1376 768 769 772 808
I'm not sure if this works or not.  But this modeline will not be 
deleted in X log.  Perhaps you have to lower the vertrefresh limit
to 40 or so to enable this modeline...

BTW, You wrote that in 8bpp without UseModeline:

(--) CHIPS(0): Dot clock 0:  25.172 MHz
(--) CHIPS(0): Dot clock 1:  28.325 MHz CRTclk
(--) CHIPS(0): Dot clock 2:  65.082 MHz FPclk
(--) CHIPS(0): Probed memory clock of  40.090 MHz
(==) CHIPS(0): Min pixel clock is  11.000 MHz
(--) CHIPS(0): Max pixel clock is  95.000 MHz

(--) CHIPS(0): Virtual size is 1024x768 (pitch 1024)
(**) CHIPS(0): Default mode "1024x768": 94.5 MHz, 68.7 kHz, 85.0 Hz
(**) CHIPS(0): Default mode "800x600": 56.3 MHz, 53.7 kHz, 85.1 Hz

(II) CHIPS(0): Generic Monitor: Using hsync range of 30.00-70.00 kHz
(II) CHIPS(0): Generic Monitor: Using vrefresh range of 50.00-100.00 Hz
(II) C

dexter and microsoft wheelmouse optical ?

2000-11-11 Thread SPENER Christian

hi i use the microsoft wheelmouse optical and isntalled a new woody with
4.0.1-2 debs, didn't have 3.3.6 on this computer before!
so gpm works without any problem, but under dexter none of the mouse
drivers r working under X.
the mouse worked for me under the pre2 4.0.1 debs, so the mouse works
under X, so this is should not be an XF4.0.1 problem, more a dexter
problem, or?
thx
chris
p.s.: the mouse port is the same under gpm an X, so it must be correct :-)
---
SPENER Christian
e-mail: [EMAIL PROTECTED]
snail-mail: A-8010 GRAZ, Schanzelgasse 19
tel: ++43 316 362283 cell phone: ++43 664 3846526


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




Re: [storm@tux.org: XFree 4.0.1 debs]

2000-11-11 Thread Rafal Krzewski
Bradley M Alexander wrote:
> When I rebuilt the box and installed the .debs of 4.0.1, I started having a
> problem with the dual heads. I created a bunch of double-sized backgrounds
> for X by pasting two regular images together. I noticed after I got back up
> and running that the root window, desktop 0 in enlightenment wasn't
> behaving right. Instead of having different pictures on each monitor, I had
> the same one on both. Other desktops were behaving normally. I thought this
> might be a problem with Enlightenment, but then, as I got the machine
> configured to my liking, I noticed that the image I was using for my xdm
> login (which was a normal-sized image that xinerama was stretching to fit
> the two desktops) was doing the same thing. The left half of the stretched
> image was displayed on the xdm login.

try running X with startx -- +xinerama, or add +xinerama parameter
to /etc/X11/xinit/xserverrc and see if it helps.
support for Option "Xinerama" in ServerLayout was broken upstream
a while ago.

Rafal

--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl



Re: [storm@tux.org: XFree 4.0.1 debs]

2000-11-11 Thread Rafal Krzewski

Bradley M Alexander wrote:
> When I rebuilt the box and installed the .debs of 4.0.1, I started having a
> problem with the dual heads. I created a bunch of double-sized backgrounds
> for X by pasting two regular images together. I noticed after I got back up
> and running that the root window, desktop 0 in enlightenment wasn't
> behaving right. Instead of having different pictures on each monitor, I had
> the same one on both. Other desktops were behaving normally. I thought this
> might be a problem with Enlightenment, but then, as I got the machine
> configured to my liking, I noticed that the image I was using for my xdm
> login (which was a normal-sized image that xinerama was stretching to fit
> the two desktops) was doing the same thing. The left half of the stretched
> image was displayed on the xdm login.

try running X with startx -- +xinerama, or add +xinerama parameter
to /etc/X11/xinit/xserverrc and see if it helps.
support for Option "Xinerama" in ServerLayout was broken upstream
a while ago.

Rafal

--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl


--  
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]




[branden@deadbeast.net: [storm@tux.org: XFree 4.0.1 debs]]

2000-11-11 Thread Seth Arnold
Bradley, I haven't played around with background images yet under
Xinerama, but I have been meaning to try my hand at splicing some
images together to make a supermegabackgroundimageofdeath -- come
remind me (on debian-x) to look further into the matter if I don't
get back to you in a few days.

Also suggested, check on debian-user if anyone has mentioned this.
As time goes on, Branden will start sending more and more people
directly to that list, as it fits closer with the group charter of
debian-user than debian-x. (And, Debian-x is preferred over emailing
Branden directly, since he gets entirely too much email about X as it
is. This way, at least some people can help weed out the easy answers.)

Cheers

- Forwarded message from Branden Robinson <[EMAIL PROTECTED]> -

Envelope-to: [EMAIL PROTECTED]
Delivery-date: Fri, 10 Nov 2000 21:49:55 -0800
Resent-Date: Fri, 10 Nov 2000 21:44:44 -0800 (PST)
X-Envelope-Sender: [EMAIL PROTECTED]
Date: Sat, 11 Nov 2000 00:46:46 -0500
To: debian-x@lists.debian.org
Subject: [EMAIL PROTECTED]: XFree 4.0.1 debs]
Mail-Followup-To: debian-x@lists.debian.org
User-Agent: Mutt/1.2.5i
From: [EMAIL PROTECTED] (Branden Robinson)
Resent-Message-ID: <[EMAIL PROTECTED]>
Resent-From: debian-x@lists.debian.org
X-Mailing-List:  archive/latest/1491
X-Loop: debian-x@lists.debian.org
Precedence: list
Resent-Sender: [EMAIL PROTECTED]
Resent-Bcc:

- Forwarded message from Bradley M Alexander <[EMAIL PROTECTED]> -

From: Bradley M Alexander <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: XFree 4.0.1 debs
Date: Fri, 10 Nov 2000 16:36:46 -0500
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Message-ID: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.2.5i

Hi Branden,

First of all, excellent job on the XFree 4.x debs. I upgraded to them last
week because apt tried to install 3.3.6 overtop of the 4.0.0 that I
compiled.

Got a question for you regarding the debs. Brian Almeida (who sat next to
me at work until about half an hour ago) suggested I get in touch with you
if I couldn't track it down.

I'm running woody on a machine with the following config:

Dual PIII/500
256MB RAM
Matrox G200/8MB at 1:0:0
Matrox Millenium II/4MB at 0:18:0
Dual Sony Trinitron G500 21" monitors
XFree86 4.0.1-0phase2v30 debs
Enlightenent-0.16.5-1

Before you started cutting .debs, I ended up getting XFree86 4.0.0 and
compiling from source. things worked fine, including Xinerama.

When I rebuilt the box and installed the .debs of 4.0.1, I started having a
problem with the dual heads. I created a bunch of double-sized backgrounds
for X by pasting two regular images together. I noticed after I got back up
and running that the root window, desktop 0 in enlightenment wasn't
behaving right. Instead of having different pictures on each monitor, I had
the same one on both. Other desktops were behaving normally. I thought this
might be a problem with Enlightenment, but then, as I got the machine
configured to my liking, I noticed that the image I was using for my xdm
login (which was a normal-sized image that xinerama was stretching to fit
the two desktops) was doing the same thing. The left half of the stretched
image was displayed on the xdm login.

I wanted to email you directly since you are the most knowledgeable about
things X in the entire Project, plus I didn't want to file a bug report
since it is entirely likely that I could have something misconfigured or
did something stupid. If you need any more information, please let me know.

Anything you can suggest?

Thanks man,
-- 
--Brad

Bradley M. Alexander, CISSP  |   Co-Chairman,
Beowulf System Admin/Security Specialist |NoVALUG/DCLUG Security SIG
Winstar Telecom  |   [EMAIL PROTECTED]
(703) 889-1049   |   [EMAIL PROTECTED]

Sushi? Where I'm from, we call this stuff "bait."
--Terry Bradshaw



- End forwarded message -

-- 
G. Branden Robinson| Communism is just one step on the long
Debian GNU/Linux   | road from capitalism to capitalism.
[EMAIL PROTECTED]  | -- Russian saying
http://deadbeast.net/~branden/ |



- End forwarded message -

-- 
``Oh Lord; Ooh you are so big; So absolutely huge; Gosh we're all really
impressed down here, I can tell you.''