CVS Update: xc (branch: trunk)

2003-10-20 Thread Alan Hourihane
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/10/20 16:00:19

Log message:
  enable loadable server on PpcArchitecture (from NetBSD cvs)

Modified files:
  xc/config/cf/:
NetBSD.cf 
  
  Revision  ChangesPath
  3.116 +3 -2  xc/config/cf/NetBSD.cf

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit


CVS Update: xc (branch: xf-4_3-branch)

2003-10-20 Thread David Dawes
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/10/20 18:52:45

Log message:
  fix comment

Modified files:
  xc/programs/Xserver/hw/xfree86/drivers/i810/: Tag: xf-4_3-branch
i830_driver.c 
  
  Revision  ChangesPath
  1.27.2.1  +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_driver.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit


CVS Update: xc (branch: trunk)

2003-10-20 Thread David Dawes
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/10/20 18:55:36

Log message:
  fix comment, and remove duplicate init of x,yoffset

Modified files:
  xc/programs/Xserver/hw/xfree86/drivers/i810/:
i830_driver.c 
  
  Revision  ChangesPath
  1.42  +2 -4  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_driver.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit


CVS Update: xc (branch: trunk)

2003-10-20 Thread David Dawes
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/10/20 19:11:27

Log message:
  typo

Modified files:
  xc/programs/Xserver/hw/xfree86/drivers/i810/:
i830_driver.c 
  
  Revision  ChangesPath
  1.43  +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_driver.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit


CVS Update: xc (branch: trunk)

2003-10-20 Thread David Dawes
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/10/20 19:17:52

Log message:
  minor formatting

Modified files:
  xc/programs/Xserver/hw/xfree86/drivers/i810/:
i830_dri.h i830_driver.c i830_memory.c i830_video.c 
  
  Revision  ChangesPath
  1.7   +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_dri.h
  1.44  +6 -6  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_driver.c
  1.10  +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_memory.c
  1.11  +6 -6  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_video.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit


CVS Update: xc (branch: xf-4_3-branch)

2003-10-20 Thread David Dawes
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/10/20 19:22:40

Log message:
  1008. Fix some i830+ VT switch/exit crashes (David Dawes, Egbert Eich).
  + some comment, formatting and doc updates

Modified files:
  xc/programs/Xserver/hw/xfree86/:  Tag: xf-4_3-branch
CHANGELOG 
  xc/programs/Xserver/hw/xfree86/drivers/i810/: Tag: xf-4_3-branch
common.h i810.h i810.man i830.h i830_cursor.c i830_dri.c 
i830_dri.h i830_driver.c i830_memory.c i830_video.c 
  
  Revision  ChangesPath
  3.2588.2.31   +2 -1  xc/programs/Xserver/hw/xfree86/CHANGELOG
  1.6.2.1   +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/common.h
  1.38.2.1  +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i810.h
  1.3.2.1   +71 -9 xc/programs/Xserver/hw/xfree86/drivers/i810/i810.man
  1.7.2.1   +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830.h
  1.6.2.1   +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_cursor.c
  1.12.2.1  +5 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_dri.c
  1.5.2.1   +2 -2  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_dri.h
  1.27.2.2  +38 -34xc/programs/Xserver/hw/xfree86/drivers/i810/i830_driver.c
  1.6.2.1   +3 -3  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_memory.c
  1.6.2.1   +7 -7  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_video.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit


CVS Update: xc (branch: trunk)

2003-10-20 Thread David Dawes
CVSROOT:/home/x-cvs
Module name:xc
Changes by: [EMAIL PROTECTED]   03/10/20 21:13:41

Log message:
   515. When the i830 driver's checks for sufficient memory for tiled mode
fail, don't later try to allocate with tiling enabled (David Dawes).

Modified files:
  xc/programs/Xserver/hw/xfree86/:
CHANGELOG 
  xc/programs/Xserver/hw/xfree86/drivers/i810/:
i830.h i830_driver.c 
  
  Revision  ChangesPath
  3.2896+3 -1  xc/programs/Xserver/hw/xfree86/CHANGELOG
  1.11  +2 -1  xc/programs/Xserver/hw/xfree86/drivers/i810/i830.h
  1.45  +8 -3  xc/programs/Xserver/hw/xfree86/drivers/i810/i830_driver.c

___
Cvs-commit mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/cvs-commit


Re: Logitech Elite Keyboard Layout

2003-10-20 Thread Mike A. Harris
On Sun, 19 Oct 2003, J E Dog wrote:

 I have writen an xkb layout for the Logitech Elite Keyboard.
 Maybe someone can use it or it will be included into XFree.

All code submissions and patches, should be filed in bugzilla at:
http://bugs.xfree86.org as individual uncompressed file
attachments (not cut and pasted into the comment field).  All
patches should be in the unified diff format and created against
the current CVS head preferably.  A unified diff can be created
by doing:

diff -Naur xc.orig xc  yourpatch.patch


Excuse me, but I have never seen that rule on the website anywhere.

I didn't say that it was a rule on the website anywhere.  Please 
point out where I said that.

Where did it come from?

It came from the will of hundreds and thousands of open source 
developers who dislike context diffs and other forms of diff 
patches, and prefer the unified diff format, as unified diff 
format seriously saves a lot of time when you're a developer 
working on a software project, in particular a project as large 
as XFree86.


Is this your particular preference? 

Why yes it is.  And it's the most popular preference of most
developers working on most software projects who even know how
about how to generate patches with diff and apply them with
patch also.  The majority of developers working on any OSS
software that I know, be it XFree86 or something else usually go
as far to straight out refuse all patches that are not in unified
diff format.  Unified diff is the easiest to read, easiest to
understand, and the easiest to hand edit should the need arise.  
It also applies much more cleanly than the other formats.  I'm
only preaching to the choir while educating you however, so I
wont bore the rest of the people who already know and agree with
me, by going into further detail.


If so you should state so plainly and not make it a rule of the
Project's.

Is this your personal opinion?  Or the opinion of the XFree86
project?  If so please state than plainly when making useless
comments in response to useful suggestions by others.

In my opinion, you don't exactly contribute much to the XFree86
project other than a rude attitude and obnoxious comments shouted
from your high horse from time to time for your opinion to matter
much to me about pretty much anything anyway.

I'm surprised that I haven't procmailed you to /dev/null yet.  
And to be quite honest, I'd be more than happy if you'd do the 
same to me, if for no other reason than I'd see both less of your 
postings *and* your generally useless responses.



-- 
Mike A. Harris



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


Re: Accellerated trident_drv.o for XFree 4.2?

2003-10-20 Thread Norman Walsh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

/ Alan Hourihane [EMAIL PROTECTED] was heard to say:
| You need to download the libpcidata and libscanpci.a modules too for
| XFree86 4.2.x.

Bingo! Thank you, Alan.

Be seeing you,
  norm

- -- 
Norman Walsh [EMAIL PROTECTED] | He who will not reason is a bigot; he
http://nwalsh.com/| who cannot is a fool; and he who dares
  | not is a slave.--Sir William Drummond
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 http://mailcrypt.sourceforge.net/

iD8DBQE/lAgIOyltUcwYWjsRAs39AKCqcGyeF00O4oISvP7SVUkKCpnK2gCdFvBX
Hct9i4Ho8Ry9LmKHVPOi43Q=
=6oz4
-END PGP SIGNATURE-
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: DRI proprietary modules

2003-10-20 Thread Ian Romanick
John Dennis wrote:
For DRI to work correctly there are several independent pieces that all
have to be in sync.
* XFree86 server which loads drm modules (via xfree86 driver module)

* The drm kernel module

* The agpgart kernel module

Does anybody know for the proprietary drivers (supplied by ATI and
Nvidia) which pieces they replace and which pieces they expect to be
there?
The Nvidia drivers do not use DRI.  The 3dlabs, ATI, PowerVR, and Matrox 
(for their Parhelia hardware) drivers do.  They will *all* replase the 
DRM kernel module, the XFree86 2D driver, and the client-side 3D driver 
(the *_dri.so file).  Most include a custom libGL.so that provides some 
added functionality.  The client-side 3D driver and the DRM kernel 
module are very tightly related, and should be considered a single 
entity (for the most part).

The reason I'm asking is to understand the consequences of
changing an API. I'm curious to the answer in general, but in this
specific instance the api I'm worried about is between the agpgart
kernel module and drm kernel module. If the agpgart kernel module
modifies it's API will that break things for someone who installs a
proprietary 3D driver? Do the proprietary drivers limit themselves to
mesa driver and retain the existing kernel services assuming the IOCTL's
are the same?
Don't bring Mesa into this.  Mesa fundamentally has nothing to do with 
DRI.  It just so happens that all of the open-source DRI drivers use 
Mesa, but there is no such requirement.  AFAIK, *none* of the 
closed-source drivers use any code from Mesa.

Or do they replace the kernel drm drivers as well? If so
do they manage AGP themselves, or do they use the systems agpgart
driver? Do they replace the systems agpgart driver?
I think both the ATI and Nvidia drivers have the option to either use 
agpgart or an internal implementation.  I'm fairly certain that the 
PowerVR, 3dlabs, and Matrox drivers all use agpgart exclusively.  All of 
the drivers, closed-source or open-source, depend on the agpgart 
interface.  Changing that interface in a non-backwards compatible will 
break them all.

I guess my question is, what changes are under consideration?

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


Re: Export symbol lists on Linux (was Re: RFC Marking private symbols in XFree86 shared libraries as private)

2003-10-20 Thread Ian Romanick
Jakub Jelinek wrote:

The first is a MUST list, symbols which are exported from XFree86 shared
libraries now when there is no anonymous version script, are not exported
when an anonymous versions script created from stock *-def.cpp file
is applied and are used by some binary or shared library (including other
shared libraries in the XFree86 collection). There is IMHO no way other
than adding these to *-def.cpp files (any issues with this)?
For libGL.so, as anonymous version scripts accept wildcards, I think
we should use gl* wildcard, as it is too error-prone to list all
the gl* functions.
Sorry for taking so long to reply.  I was taking a few days off. :)

libGL.so needs to export XF86DRI*, __glXFindDRIScreen, and a few _glapi 
functions on all platforms that support DRI (i.e., Linux and *BSD 
currently).  Do a nm /usr/X11R6/lib/modules/dri/*_dri.so | grep ' U 
_glapi' | sort -u  to see which ones.  On all platforms all symbols 
matching gl[A-Z]* need to be exported.  Other than that I don't think 
anything needs to be exported by libGL.so.

I *believe* that the *_dri.so files only need to export 
__driCreateScreen.  There are some other symbols that need to be 
exported in DRI CVS, but that code isn't in XFree86 CVS AFAIK (and won't 
be until after 4.4.0).

Thanks for tackling this!

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


Re: Configuring Function keys with mouse pointer

2003-10-20 Thread Heather Stern
On Tue, Oct 07, 2003 at 12:09:34PM +0200, [EMAIL PROTECTED] wrote:
 Can I in a multi monitor situation configure the Function Keys so that for
 example the F1 key will put the mouse pointer on Screen 1 ?
 
 Best regards,
 Marcel Stegehuis

(Pardon my vague understanding of multi-monitor mode's workings under
the hood, as I joined this list to get a better hang of mouse behavior
and absorb a bit of modern X programming savvy by osmosis. If I'm wrong
about anything corrections from saner souls are welcomed.)

If multiple monitors is handled as a giant screen of broader pixel range,
then simple repositioning of the mosue cursor to a given pixel location
should be sufficient.  If, as a user, you can use -geometry to place
new windows on any of your monitors, then I would expect the answer to
be yes.

That lends the answer to being a window manager function - if it (1) lets
you jump the mouse cursor that way (rather than merely new windows), and 
(2) allows assignment of function key to invoke that ability, then sure,
I don't see why not.

If you're writing a WM that wants to do this I hope one of the others
can do it already; that would make it easy to see how they coded this up.

  . | .   Heather Stern  | [EMAIL PROTECTED]
---*--- Starshine Technical Services - * - [EMAIL PROTECTED]
  ' | `   Sysadmin Support and Training  |(800) 938-4078
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel


Re: Kernel Module? On second thought...

2003-10-20 Thread Emmanuel ALLAUD
Mike A. Harris wrote:

On Fri, 17 Oct 2003, David Fox wrote:

 

I think that the wisest approach is, instead of suggesting a kernel 
module to the XFree86 folks, you do two things.  First, suggest a kernel 
module to the Linux folks that implements a protocol for accessing the 
resource you are trying to use.  Then you go to  the XFree86 folks and 
suggest a module to utilize that protocol in the X server.

[snip]

What _specific_ area of XFree86 performance are you (or anyone 
else) thinking needs improvement, what solutions have you 
investigated or even thought about which could improve this 
performance by modifying XFree86 itself, a driver, Mesa, or other 
userland code?  If you do think the kernel might help for this 
problem, what steps have you taken to determine if that is truely 
reasonable, and have you tested your theory?  Have you discussed 
that one small idea with other developers to see what they think 
about the alleged problem, wether it even really is a problem at 
all, how important it is, what other solutions there might be, 
etc. etc. etc.

All of this lets stuff things in the kernel, because kernel code 
is automatically 2 times faster right? stuff gets boring 
fast.

Show me the code.

   

I have no code to show ;-) but I have a case where a kernel module is 
unavoidable to get out of the statu quo : M. Voijkovich asked about the 
use of sched_yield() in order to wait for the FIFO to process a big 
enough part of the DMA buffer before we try to refill it; his idea was 
to smartly release the CPU because we know that the driver will have to 
wait quite a while before the GPU has processed the datas. But we also 
need to get the CPU back fast enough in order to have a unbroken stream 
of data fed to the GPU.Now the driver is busy looping (correct me if I 
wrong) which is a waste of CPU. Using sched_yield() for 2.6.x linux 
kernels will lead to bad latency (basically we will reacquire the CPU 
very lately). The last alternative (at least following R. Russel and 
R.M. Love) is to have a kernel module which can poll the DMA to see how 
much has already been sent to the GPU, and when enough has been 
processed, this kernel module wakes up the driver in userland (using 
futexes). This approach could work with all these types of rather long 
waits where it is not really smart to busy loop (one assumption is that 
the wait can be long enough that we will consume our whole timeslice 
busy looping, which will also lead to a bad score on interactiveness 
on newer linux kernels, and also we will have to wait until we reacquire 
the CPU). R. Russel seems to be OK to help if the XFree guys wanted to 
go this way. I must add that M. Vojkovich did not like the idea of a 
kernel module.
My 2 cents...
Bye
Manu

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


Re: Kernel Module? On second thought...

2003-10-20 Thread Emmanuel ALLAUD
Emmanuel ALLAUD wrote:

Mike A. Harris wrote:

On Fri, 17 Oct 2003, David Fox wrote:

 

I think that the wisest approach is, instead of suggesting a kernel 
module to the XFree86 folks, you do two things.  First, suggest a 
kernel module to the Linux folks that implements a protocol for 
accessing the resource you are trying to use.  Then you go to  the 
XFree86 folks and suggest a module to utilize that protocol in the X 
server.

[snip]

What _specific_ area of XFree86 performance are you (or anyone else) 
thinking needs improvement, what solutions have you investigated or 
even thought about which could improve this performance by modifying 
XFree86 itself, a driver, Mesa, or other userland code?  If you do 
think the kernel might help for this problem, what steps have you 
taken to determine if that is truely reasonable, and have you tested 
your theory?  Have you discussed that one small idea with other 
developers to see what they think about the alleged problem, wether 
it even really is a problem at all, how important it is, what other 
solutions there might be, etc. etc. etc.

All of this lets stuff things in the kernel, because kernel code is 
automatically 2 times faster right? stuff gets boring fast.

Show me the code.

  

I have no code to show ;-) but I have a case where a kernel module is 
unavoidable to get out of the statu quo : M. Voijkovich asked about 
the use of sched_yield() in order to wait for the FIFO to process a 
big enough part of the DMA buffer before we try to refill it; his idea 
was to smartly release the CPU because we know that the driver will 
have to wait quite a while before the GPU has processed the datas. But 
we also need to get the CPU back fast enough in order to have a 
unbroken stream of data fed to the GPU.Now the driver is busy looping 
(correct me if I wrong) which is a waste of CPU. Using sched_yield() 
for 2.6.x linux kernels will lead to bad latency (basically we will 
reacquire the CPU very lately). The last alternative (at least 
following R. Russel and R.M. Love) is to have a kernel module which 
can poll the DMA to see how much has already been sent to the GPU, and 
when enough has been processed, this kernel module wakes up the driver 
in userland (using futexes). This approach could work with all these 
types of rather long waits where it is not really smart to busy loop 
(one assumption is that the wait can be long enough that we will 
consume our whole timeslice busy looping, which will also lead to a 
bad score on interactiveness on newer linux kernels, and also we 
will have to wait until we reacquire the CPU). R. Russel seems to be 
OK to help if the XFree guys wanted to go this way. I must add that M. 
Vojkovich did not like the idea of a kernel module.
My 2 cents...
Bye
Manu
Hmm, replying to myself : I read that the DRI kernel module addresses 
certain issues with DMA/IRQ and others. Is there any good reason that 
would prevent 2D drivers to use the API provided by this module?
Bye
Manu

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


[I18n] You are too expensive, can I have a discount?

2003-10-20 Thread Robert




Closing 
Techniques Workshop
One 
day workshop
What if 
the customer says:
· 
· 
‘It’s too 
expensive’
· 
· 
‘We’re happy 
with our present supplier’
· 
· 
‘I want to 
think about it’

Can you handle these common 
objections?
By far the most efficient way to be more profitable 
is to turn more of the enquiries you receive into paid orders. For this, the ability to resolve 
objections is critical - either you close or you lose the 
sale.
And if you answer ‘How much discount will you give 
me?’ with: ‘I’ll ask my boss’, you waste profit, which could be yours with a 
better reply.

In only a day I will teach you techniques which 
overcome these objections and more. You will be able to use them immediately to 
win profitable orders.

There is no need to lose business to your competitors 
or give big discounts. 

Fee for this event is £300. 


Selling for 
Engineers
One-day 
Seminar

The Selling for Engineers seminar is a good 
introduction to effective sales principles for people who are new to selling, 
and also a useful refresher for ‘old hands’. It applies to selling both technical 
products and intangible services.

Many Sales Engineers have been learning the technical 
skills of their job for years but have had little formal training in 
selling. This course helps correct 
that imbalance. 

Typical job titles of delegates: Sales Engineer, 
Account Executive and Business Development Manager.

Fee for this event is £300.



Telephone 
Sales Prospecting for Engineers
One-day 
Workshop
This event is a practical workshop teaching people in 
technical companies how to find new customers on the phone. It is applicable to business development 
for both tangible products and intangible services. The first session addresses whom to 
target, what to say and how to handle problems. The remainder of the day consists of 
live sales calls with coaching from Robert Seviour; the objective being to give 
delegates some positive experiences of prospecting, make sales appointments and 
maybe sell something!

Please note that this telephone sales prospecting 
event is restricted to a maximum of six delegates to permit individual 
coaching.
Fee for this event is £300.






If you have never had any formal sales training or 
need a refresher, don’t continue to work at a disadvantage. 



Reservations and 
information
Please contact Sue on: 

Tel: +44(0)1481 720 294 Fax: +44(0)1481 720 
317

If sales training is not an 
issue for your company please reply to this email with the word “DELETE” in the 
subject line. We 
will remove your details promptly.



[XFree86] Xfree app hangs into strverscmp

2003-10-20 Thread Kentropy
Hi,
Using Xfree-4.3.99.10
I successfully launched xinit, xeyes, twm
Then when I launch my X application I the linuxbox hangs and I need to turn
power
off.
I debugged my X application with gdb and noticed that the error was in the
strverscmp() function into gcc library.

Could this behavior be caused by a wrong X configuration like missing fonts
or something else ?
Could someone please help me ?
TIA

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


[XFree86] RESOLVED: I830WaitLpRing() lockup

2003-10-20 Thread Alexey E. Suslikov
keywords: openbsd, x11, i830, ring buffer, lockup

 It just occurred to me where I had seen this type of black screen problem
 before.  It happens when using the vesa driver with an 845G.  We work
 around this in the i810 driver by remembering the initial video mode
 and simply re-initialising it when exiting/VT switching instead of using
 the VBE save/restore mechanism.  This workaround is only actived for
 845G hardware.  You could try enabling it for all hardware by changing
 this line in i830_driver.c from:
 
 if (!I845G_VBE_WORKAROUND || !IS_845G(pI830)) {
 
 to:
 
 if (!I845G_VBE_WORKAROUND) {

hmmm... my yesterdays reply was lost somewhere... ok, let's repeat :)

turning on I845G_VBE_WORKAROUND magically SOLVES the problem on
4.3.99.14 in both accel and noaccel setups:

  VideoRam
default(8192)  2048  32768
Accelok ok ok
NoAccel  ok ok ok
NoAccel+SWcursor ok ok ok

David, thanks a lot. if you have some spare time, can you write some
explanations on this case?

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


[XFree86] Xserver Reporting error

2003-10-20 Thread Shibu Krishnan
sir

the error reported is attached herewith. pls suggest a
solution at the earliest.

regards

shibu



__
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com

XFree86.0.log
Description: XFree86.0.log


[XFree86] Request Help

2003-10-20 Thread Freddy Paul
 Dear Members,

  I am for the first time mailing on to this
id. I am having some problem with my Xwindow.When ever
i make some manual change to my user group or related
things in /etc/passwd file, next time when i try to
start the xwindow its giving out an error related to
some font cannot be initialised or so. So please help me.


Yahoo! India Matrimony: Find your partner online.
Go to http://yahoo.shaadi.com
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] RESOLVED: I830WaitLpRing() lockup

2003-10-20 Thread Nicolas Joly
On Mon, Oct 20, 2003 at 11:13:12AM +0300, Alexey E. Suslikov wrote:
 keywords: openbsd, x11, i830, ring buffer, lockup
 
  It just occurred to me where I had seen this type of black screen problem
  before.  It happens when using the vesa driver with an 845G.  We work
  around this in the i810 driver by remembering the initial video mode
  and simply re-initialising it when exiting/VT switching instead of using
  the VBE save/restore mechanism.  This workaround is only actived for
  845G hardware.  You could try enabling it for all hardware by changing
  this line in i830_driver.c from:
  
  if (!I845G_VBE_WORKAROUND || !IS_845G(pI830)) {
  
  to:
  
  if (!I845G_VBE_WORKAROUND) {
 
 hmmm... my yesterdays reply was lost somewhere... ok, let's repeat :)
 
 turning on I845G_VBE_WORKAROUND magically SOLVES the problem on
 4.3.99.14 in both accel and noaccel setups:
 
   VideoRam
 default(8192)  2048  32768
 Accelok ok ok
 NoAccel  ok ok ok
 NoAccel+SWcursor ok ok ok

I just made the same modification on my NetBSD (-current) Dell laptop
with i830 chipset.

Everything seems to work fine now ... I can restart X without
rebooting the machine and VT switching works flawlessly.

Great job,
Thanks.

-- 
Nicolas Joly

Biological Software and Databanks.
Institut Pasteur, Paris.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Mplayer too slow and crashing due to bad usage of CPU/RAM

2003-10-20 Thread Robert Rozman
Hello,

I have problem that mplayer is too slow in xfree86 (I have sis651 chipset -
I've tried 4.3 with separate sis drivers and 4.3.99.14 with builtin sis
driver). It plays quite slowly and from now and then crashes with signal in
video_decode due to Bad usage of CPU/ram. It crashes immediately if I
fforward or backward.

I saw entry 414. in Changelog and wonder whether this is the same problem.
What was problem in 414. and was it solved OK or it remains ?

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


Re: [XFree86] Mplayer too slow and crashing due to bad usage of CPU/RAM

2003-10-20 Thread Måns Rullgård
Robert Rozman [EMAIL PROTECTED] writes:

 I have problem that mplayer is too slow in xfree86 (I have sis651 chipset -
 I've tried 4.3 with separate sis drivers and 4.3.99.14 with builtin sis
 driver). It plays quite slowly and from now and then crashes with signal in
 video_decode due to Bad usage of CPU/ram. It crashes immediately if I
 fforward or backward.

It's likely an mplayer bug.  Try a different video player.

-- 
Måns Rullgård
[EMAIL PROTECTED]
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


[XFree86] Seeing large number for SIZE column in ps output - all may be ok, but just checking

2003-10-20 Thread Dermot McGahon
Hello,

I am seeing large X process sizes on a number of RH9 machines. RSS stabilises at a reasonable value but SIZE is 150MB+ and on a machine with 128MB ram, I strongly suspect that this was the cause of swapping which basically brought the box to a standstill. I have bought and installed extra ram since, but this behaviour could potentially affect other workhorse machines which are also showing high SIZE figures for X.

I have reduced the problem down, by starting just X in runlevel 3, and just X  twm in runlevel three, but still see high process sizes. The display adapter is the intel 845/GL and if this is just a vram mapping issue then I'm sorry about taking up your time, although I am a little suspicious about what interactions large process sizes (ram  vram) may cause with the VM system. You might be good enough to put my mind at rest about that.

Various command outputs attached as files (lspci -v, pmap, restest, xdpyinfo), and X version, free and ps info included below.

Any more info needed or any tests to be run, just ask.

Warm Regards,

Dermot.
--
[EMAIL PROTECTED] CVs]$ X -version

XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2)
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] Build Date: 27 February 2003
Build Host: porky.devel.redhat.com
Before reporting problems, check http://www.XFree86.Org/
   to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.6.0-test5 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 
(Red Hat Linux 3.2.2-5)) #2 Thu Oct 9 10:13:05 BST 2003
[EMAIL PROTECTED] CVs]$ free
total   used   free sharedbuffers cached
Mem:377740 365636  12104  0  58772  75928
-/+ buffers/cache: 230936 146804
Swap:  1052216  180321034184
[EMAIL PROTECTED] CVs]$ ps  aux | grep X
root  2163 30.7  8.8 170108 33360 ?  SOct17 1240:05 /usr/X11R6/bin/X :0 
-auth /var/gdm/:0.Xauth vt7


lspci.out
Description: Binary data


pmap.out
Description: Binary data


restest.out
Description: Binary data


xdpyinfo.out
Description: Binary data


XF86Config.
Description: Binary data


Re: [XFree86] Xlib: extension RENDER missing on display

2003-10-20 Thread Haley Crowe
Thanks for the info!

Haley

 [EMAIL PROTECTED] 10/17/2003 8:18:40 PM 
  That's not an error.  It's simply stating that your X-server
doesn't support the RENDER extension (because it's too old, most
likely).

Mark.

On Fri, 17 Oct 2003, Haley Crowe wrote:

 Hello.  I did a quick search of the archive, and didn't find what I
was
 looking for there, so I thought I'd go ahead and see if anyone could
 help me.  If this is a common question and I just missed it in the
 archive, I apologize.
 
 When I try to start an X session (KDE) from remote computer, I get
the
 following error:
 
 Xlib:  extension RENDER missing on display
 
 A search on the redhat bugzilla site suggested turning off the anti
 aliasing.  From what I can tell, that is already turned off.  Does
 anyone have suggestions??
 
 Thanks!
 Haley
 
 ___
 XFree86 mailing list
 [EMAIL PROTECTED] 
 http://XFree86.Org/mailman/listinfo/xfree86 
 

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


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


[XFree86] Linux XFree86 Problem

2003-10-20 Thread Dhananjy yadav
Heallo 
Sir/ Madam

I am dhanajay from new delhi 

Sir/Madam i would like to tell you my linux problem.Problem is that  when i was start 
my linux after some process a linux give massage like
here i giving you step by step;


I can’nt start the X Server (Your GUI ) .It is
 likely that it is not set up correctly .Would you
 view the X Server output to Diagonse the proble ?.
 
 Yes /No
 I press Yes then Next Massage is
 Xfree86 Version---
 --
 --
 --
 = = = Log File :”/var/log/Xfree86.o.log” :this -
 = = = Using Config file : “/etc/X11/XF86 Config”
 EE :: Failed to load Moudle “(Moudle does not Exist
 ,0)
 
 EXIT
 
 I press exit then next massage is
 Woud you like me to try run the X Configuration
 program ? Note you will need this Please Type in the
 root (privileged user) password
 
 Password :
 
 I give password then
 
 Next msg is again I can not start Xserver try with
 -
 Could not start X Server (Your GUI )
 Try With card Intel 810
 I will try X Server again.

XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2)
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-3bigmem i686 [ELF] 
Build Date: 27 February 2003
Build Host: porky.devel.redhat.com
 
Before reporting problems, check http://www.XFree86.Org/
to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED]) (gcc version 3.2.2 20030222 (Red 
Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:54:28 EST 2003 
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Mon Oct 20 05:07:35 2003
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout Default Layout
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Videocard0
(**) |--Input Device Mouse0
(**) |--Input Device Keyboard0
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc105
(**) XKB: model: pc105
(**) Option XkbLayout us
(**) XKB: layout: us
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device DevInputMice
(**) FontPath set to unix/:7100
(**) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(--) using VT number 7

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.2
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.4
XFree86 Server Extension : 0.2
XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: bitmap


(WW) Warning, couldn't open module bitmap
(II) UnloadModule: bitmap
(EE) Failed to load module bitmap (module does not exist, 0)
(II) LoadModule: pcidata
(WW) Warning, couldn't open module pcidata
(II) UnloadModule: pcidata
(EE) Failed to load module pcidata (module does not exist, 0)

Fatal server error:
Unable to load required base modules, Exiting...


When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file /var/log/XFree86.0.log.
Please report problems to [EMAIL PROTECTED]



[XFree86] Envoi d'un message : XFree86.0.log

2003-10-20 Thread Cédric DELAMARRE

Vos fichiers sont attachés et prêts à envoyer avec ce message.

This is a pre-release version of XFree86, and is not supported in any
way.  Bugs may be reported to [EMAIL PROTECTED] and patches submitted
to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,
please check the latest version in the XFree86 CVS repository
(http://www.XFree86.Org/cvs)

XFree86 Version 4.1.0.1 / X Window System
(protocol Version 11, revision 0, vendor release 6510)
Release Date: 21 December 2001
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/FAQ)
Build Operating System: Linux 2.4.20-8um i686 [ELF] 
Module Loader present
(==) Log file: /var/log/XFree86.0.log, Time: Mon Oct 20 16:54:58 2003
(==) Using config file: /etc/X11/XF86Config-4
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) ServerLayout Default Layout
(**) |--Screen Default Screen (0)
(**) |   |--Monitor Generic Monitor
(**) |   |--Device Generic Video Card
(**) |--Input Device Generic Keyboard
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc104
(**) XKB: model: pc104
(**) Option XkbLayout fr
(**) XKB: layout: fr
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device Configured Mouse
(**) |--Input Device Generic Mouse
(WW) The directory /usr/lib/X11/fonts/cyrillic does not exist.
Entry deleted from font path.
(**) FontPath set to 
unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi
(==) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(--) using VT number 7

(WW) Cannot open APM
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.4
XFree86 XInput driver : 0.2
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.2
(II) Loader running on linux
(II) LoadModule: bitmap
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.1.0.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.2
(II) Loading font Bitmap
(II) LoadModule: pcidata
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor=The XFree86 Project
compiled for 4.1.0.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.4
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 10b9,1521 card 10b9,1521 rev 1d class 06,00,00 hdr 00
(II) PCI: 00:02:0: chip 10b9,1523 card 10b9,1523 rev 07 class 06,01,00 hdr 80
(II) PCI: 00:02:1: chip 10b9,5219 card , rev 20 class 01,01,fa hdr 80
(II) PCI: 00:06:0: chip 10ec,8139 card 4554,434e rev 10 class 02,00,00 hdr 00
(II) PCI: 00:07:0: chip 1002,4755 card 1002,4755 rev 9a class 03,00,00 hdr 00
(II) PCI: 00:08:0: chip 1045,c861 card 1045,c861 rev 10 class 0c,03,10 hdr 00
(II) PCI: End of PCI scan
(II) LoadModule: scanpci
(II) Loading /usr/X11R6/lib/modules/libscanpci.a
(II) Module scanpci: vendor=The XFree86 Project
compiled for 4.1.0.1, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.4
(II) UnloadModule: scanpci
(II) Unloading /usr/X11R6/lib/modules/libscanpci.a
(II) Host-to-PCI bridge:
(II) PCI-to-ISA bridge:
(II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus 0 I/O range:
[0] -1 00x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
[0] -1 00x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
[0] -1 00x - 0x (0x0) MX[B]
(II) Bus -1: bridge is at (0:2:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set)
(II) Bus -1 I/O range:
(II) Bus -1 non-prefetchable memory range:
(II) Bus -1 prefetchable memory range:
(--) PCI:*(0:7:0) ATI Mach64 GU rev 154, Mem @ 0x0800/24, 0x07101000/12, I/O @ 
0x7000/8, BIOS @ 0x0712/17
(II) Addressable bus resource ranges are
[0] -1 00x - 0x (0x0) MX[B]
[1] -1 00x - 0x (0x1) IX[B]
(II) OS-reported resource ranges:
[0] -1 00xffe0 - 0x (0x20) MX[B](B)
[1] -1 00x0010 - 0x3fff (0x3ff0) MX[B]E(B)
[2] -1 00x000f - 0x000f (0x1) MX[B]
[3] -1 00x000c - 0x000e (0x3) MX[B]
[4] -1 00x - 0x0009 (0xa) MX[B]
[5] -1 0

[XFree86] Second video card not initialising (RedHat 9.0)

2003-10-20 Thread Dan Churchill
I have a GeForce2 MX (ASUS something or other) AGP card as my
primary display adapter and an ATI 3D XPression+ PC2TV PCI card
as a second adapter.

I've attached /var/log/XFree86.0.log and /etc/X11/XF86Config but
as a preview, these are the only two (EE) in the log:
 (EE) ATI(1): Cannot read V_BIOS
 (WW) ATI(1): Unable to initialise int10 interface.
 (EE) ATI(1): Adapter has not been initialised.

It may also be interesting to note that until I began composing
this message, the (EE) that I had been seeing was related to
vm86() receiving signal 4.

Can you offer a solution or point me to existing documention (I
had a look in the archives and a couple of Googles, but didn't
see anything relelvent).

Do you need more details?

-- 
Dan
[http://www.DECSi.com/~dchurchi]

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


[XFree86] Installing NVIDIA driver for AMD Athlon Processor

2003-10-20 Thread Brian
I have had problems getting my GUI interface to work after installing Redhat
9 linux.
After typing startx I get an error and the X server aborts

Here is my Log FILE and COnfig FILES --

XFree86 Version 4.3.0 (Red Hat Linux release: 4.3.0-2)
Release Date: 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
Build Operating System: Linux 2.4.20-3bigmem i686 [ELF]
Build Date: 27 February 2003
Build Host: porky.devel.redhat.com

 Before reporting problems, check http://www.XFree86.Org/
 to make sure that you have the latest version.
Module Loader present
OS Kernel: Linux version 2.4.20-8 ([EMAIL PROTECTED])
(gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu Mar 13 17:18:24
EST 2003
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Mon Oct 20 18:33:31 2003
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout Default Layout
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Videocard0
(**) |--Input Device Mouse0
(**) |--Input Device Keyboard0
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc105
(**) XKB: model: pc105
(**) Option XkbLayout gb
(**) XKB: layout: gb
(==) Keyboard: CustomKeycode disabled
(**) |--Input Device DevInputMice
(**) FontPath set to unix/:7100
(**) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(--) using VT number 7

(WW) Open APM failed (/dev/apm_bios) (No such device)
(II) Module ABI versions:
 XFree86 ANSI C Emulation: 0.2
 XFree86 Video Driver: 0.6
 XFree86 XInput driver : 0.4
 XFree86 Server Extension : 0.2
 XFree86 Font Renderer : 0.4
(II) Loader running on linux
(II) LoadModule: bitmap
(II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
 compiled for 4.3.0, module version = 1.0.0
 Module class: XFree86 Font Renderer
 ABI class: XFree86 Font Renderer, version 0.4
(II) Loading font Bitmap
(II) LoadModule: pcidata
(II) Loading /usr/X11R6/lib/modules/libpcidata.a
(II) Module pcidata: vendor=The XFree86 Project
 compiled for 4.3.0, module version = 1.0.0
 ABI class: XFree86 Video Driver, version 0.6
(II) PCI: Probing config type using method 1
(II) PCI: Config type is 1
(II) PCI: stages = 0x03, oldVal1 = 0x0cf8, mode1Res1 = 0x0cf8
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1039,0746 card 1849,0746 rev 02 class 06,00,00 hdr
00
(II) PCI: 00:01:0: chip 1039,0002 card , rev 00 class 06,04,00 hdr
01
(II) PCI: 00:02:0: chip 1039,0008 card , rev 25 class 06,01,00 hdr
80
(II) PCI: 00:02:5: chip 1039,5513 card 1849,5513 rev 00 class 01,01,80 hdr
00
(II) PCI: 00:02:7: chip 1039,7012 card 434d,4961 rev a0 class 04,01,00 hdr
00
(II) PCI: 00:03:0: chip 1039,7001 card 1849,7001 rev 0f class 0c,03,10 hdr
80
(II) PCI: 00:03:1: chip 1039,7001 card 1849,7001 rev 0f class 0c,03,10 hdr
00
(II) PCI: 00:03:2: chip 1039,7002 card 1849,7001 rev 00 class 0c,03,20 hdr
00
(II) PCI: 00:04:0: chip 1039,0900 card 1849,8201 rev 90 class 02,00,00 hdr
00
(II) PCI: 00:0e:0: chip 14e4,4320 card 182d,906e rev 02 class 02,80,00 hdr
00
(II) PCI: 01:00:0: chip 10de,0322 card 1682,1280 rev a1 class 03,00,00 hdr
00
(II) PCI: End of PCI scan
(II) Host-to-PCI bridge:
(II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set)
(II) Bus 0 I/O range:
 [0] -1 0 0x - 0x (0x1) IX[B]
(II) Bus 0 non-prefetchable memory range:
 [0] -1 0 0x - 0x (0x0) MX[B]
(II) Bus 0 prefetchable memory range:
 [0] -1 0 0x - 0x (0x0) MX[B]
(II) PCI-to-PCI bridge:
(II) Bus 1: bridge is at (0:1:0), (0,1,2), BCTRL: 0x000a (VGA_EN is set)
(II) Bus 1 non-prefetchable memory range:
 [0] -1 0 0xcdd0 - 0xcfef (0x220) MX[B]
(II) Bus 1 prefetchable memory range:
 [0] -1 0 0xbda0 - 0xcdbf (0x1020) MX[B]
(II) PCI-to-ISA bridge:
(II) Bus -1: bridge is at (0:2:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set)
(--) PCI:*(1:0:0) nVidia Corporation unknown chipset (0x0322) rev 161, Mem @
0xce00/24, 0xc000/27, BIOS @ 0xcfee/17
(II) Addressable bus resource ranges are
 [0] -1 0 0x - 0x (0x0) MX[B]
 [1] -1 0 0x - 0x (0x1) IX[B]
(II) OS-reported resource ranges:
 [0] -1 0 0xffe0 - 0x (0x20) MX[B](B)
 [1] -1 0 0x0010 - 0x3fff (0x3ff0) MX[B]E(B)
 [2] -1 0 0x000f - 0x000f (0x1) MX[B]
 [3] -1 0 0x000c - 0x000e (0x3) MX[B]
 [4] -1 0 0x - 0x0009 (0xa) MX[B]
 [5] -1 0 0x - 0x (0x1) IX[B]
 [6] -1 0 0x - 0x00ff (0x100) IX[B]
(II) PCI Memory resource overlap reduced 0xd000 from 0xd3ff to
0xcfff
(II) Active PCI resource ranges:
 [0] -1 0 0xcfffa000 - 0xcfffbfff (0x2000) MX[B]
 [1] -1 0 0xcfffc000 - 0xcfffcfff (0x1000) MX[B]
 [2] -1 0 0xc000 

Re: Re: [XFree86] BNC Connections

2003-10-20 Thread Mark Vojkovich
   Your monitor probably has a switch somewhere (maybe in the onscreen
controls) that switches between D-Sub and BNC.  Other than the cable
being broken or the monitor not using the BNC inputs, there's really
not much that could go wrong.


Mark.

On Mon, 20 Oct 2003 [EMAIL PROTECTED] wrote:

 Sorry, and thank you Mark, yes I have a SVGA - BNC cable with 5 BNC connectors at 
 the end of it. Got any ideas? 
  From: Mark Vojkovich [EMAIL PROTECTED]
  Date: 2003/10/19 Sun PM 03:08:00 EDT
  To: [EMAIL PROTECTED]
  CC: [EMAIL PROTECTED]
  Subject: Re: [XFree86] BNC Connections
  
  
  
  On Sun, 19 Oct 2003 [EMAIL PROTECTED] wrote:
  
   I have a Nokia MultiGraph 445 Xpro monitor and a Diamond Stealth 2000 pro video 
   card. I can not ge the card and monitor to work using the BNC connectors. Works 
   fine with the D-Sub connectors. Any ideas? I would go to Diamond, but since they 
   got bought no one seems to be supplying support for their video cards.
   
  
 Just to be clear... You have *FIVE* BNC connectors (R,G,B,H,V) ?
  
  
  Mark.
  
  
 
 
 

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


[XFree86] XFree and Debian...

2003-10-20 Thread Boniforti Flavio
Hello all!

Is anybody able to help me?

I got just my Debian Woody installed, then I installed X-Windows and
gnome2.

Now, when I launch startx I get:

(EE) Screen(s) found, but none have a usable configuration.

Fatal server error:
no screens found

What should I do?

I configured XFree with xf86config... if it can help, I would also
attach my logfile.

Thank you all!

-- 
Registered Linux User #251752
   --- VB LUG Moderator ---
The original point and click interface was a Smith  Wesson.


pgp0.pgp
Description: PGP signature


Re: [XFree86] XFree and Debian...

2003-10-20 Thread Mark Vojkovich
  You need to attach the /var/log/XFree86.0.log file so that
we can see why it's failing.

Mark.

On Mon, 20 Oct 2003, Boniforti Flavio wrote:

 Hello all!
 
 Is anybody able to help me?
 
 I got just my Debian Woody installed, then I installed X-Windows and
 gnome2.
 
 Now, when I launch startx I get:
 
 (EE) Screen(s) found, but none have a usable configuration.
 
 Fatal server error:
 no screens found
 
 What should I do?
 
 I configured XFree with xf86config... if it can help, I would also
 attach my logfile.
 
 Thank you all!
 
 -- 
 Registered Linux User #251752
--- VB LUG Moderator ---
 The original point and click interface was a Smith  Wesson.
 

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


Re: [XFree86] XFree and Debian...

2003-10-20 Thread Boniforti Flavio
In data Mon, 20 Oct 2003 21:14:51 +0200
Boniforti Flavio [EMAIL PROTECTED] scriveva:

 I configured XFree with xf86config... if it can help, I would also
 attach my logfile.

Here is my logfile attached!
Thank you!

-- 
Registered Linux User #251752
   --- VB LUG Moderator ---
Any wire cut to length will be too short.


XFree86.0.log
Description: Binary data


pgp0.pgp
Description: PGP signature


Re: [XFree86] XFree and Debian...

2003-10-20 Thread Boniforti Flavio
In data Mon, 20 Oct 2003 14:43:07 -0700 (PDT)
Mark Vojkovich [EMAIL PROTECTED] scriveva:

 You need to attach the /var/log/XFree86.0.log file so that
 we can see why it's failing

Just sent it to the ML.

Thank you...

-- 
Registered Linux User #251752
   --- VB LUG Moderator ---
I understand cats, women are the mystery!


pgp0.pgp
Description: PGP signature


Re: [XFree86] I am having xfree86 4.3.99.14 crashes and it says to report it here.

2003-10-20 Thread GS HUNT
Well you are using a devlopmental version..of Xfree.chances are support for 
your wacom pen input device is not supported..

Why not use a stable version?

Gary




On Sunday 19 October 2003 04:27 am, Robin Cook wrote:
 Crash is reporting

 Fatal Servers Error: Caught signal 11. Server aborting.

 Attached is the bzip2 log file it says to send with the report.

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


[XFree86] How to configure a HP U8131-O USB optical mouse?

2003-10-20 Thread Bill Squire {billsf}
Dear Sir/Madam

At a trade fair I purchased an HP U8131-O USB optical mouse. It appears 
to be a MouseSystems protocol and auto also works. The mouse works 
fine but i can't get the scroll wheel to work. Here are the complete
specifications of the protocol:

From cat /dev/ums0 - | hd

A 8byte word is sent everytime the state changes. Much of this is certainly
known to XFree but here it is:

Default (no action)
87 00 00 00 00 00 00 7f
|  |  |  |  |  |  |  |
0  1  2  3  4  5  6  7

Byte 0 the buttons: 0x83Left buttion pressed 
0x86Right button pressed 
0x85Centre (the wheel) button pressed 
0x82L + R pressed 
0x81L + C pressed
0x84C + R pressed
0x80all buttons pressed
0x87no buttons pressed

Byte 1 X-axis 'left'0xff
Byte 2 Y-axis 'down'0xff
Byte 3 X-axis 'right'   0x01
Byte 4 Y-axis 'up'  0x01
Byte 5 Wheel 'up'   0xff
Byte 6 Wheel 'down' 0x01
Byte 7 End of Frame 0x7f

Personally, i don't see how 'mapping buttons' has anything to do with
this mouse. It may just be a handy way to express the config? This is
a rather obscure mouse, but except for bytes 5 and 6 X sees it. Using
'xev' I see nothing from the wheel no matter how I configure it. Do you
have an easy way to do the configure? Sure, I can mess with the 'ums'
driver and get it, but want I to make sure before I do that.

Thanks in advance,

Bill Squire

PS: Running an amd64 which I bootstrapped FreeBSD on. Almost everything 
works, and fast without the kernel panics and core dumps reported from
the v5.1 amd64 release. You can't even cvsup with that software!

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


[XFree86] How To Set The Refresh Rate? Please, Help!

2003-10-20 Thread Zava
Please help me, I need to change the refresh rate of my monitor.
I use Red H. 9.0a, with kernel version: 2.4.20-20.9.
Chipset: Nforce 2 Ultra (Gigab. GA 7N400-L, bios version F5)
Video: Nvidia Geforce 4 ti 4600
Monitor: LG F900P (Flatron)
Cpu: athlon xp 2600+
Ram= 512 mb pc3200

XFree86 Version: 4.3.0 (Red h. linux release: 4.3.0-2) 27 february 2003
X Protocol Version 11, Revision 0, Release: 6.6

I don't know how to change the refresh rate of the monitor. I don't know
how to do. I know(well...I think) I should edit and change the
XF86Config file, but i can't see any voice about refresh rate(s). I have
to say that the operative system doesn't recognise the monitor, so i
have manually filled the required fields, with the manufacturer's
specifications, so that I can set the right screen resolutions, but,
again, no voices about the refresh rate(s), that it's fixed at 60 mhz.
Please, Help me.
Thanks and sorry for my english, i am from Italy.


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


Re: [XFree86] XFree and Debian...

2003-10-20 Thread Mark Vojkovich
  Remove Option UseFBDev from the /etc/X11/XF86Config-4 file.
This seems to be a common Debian problem - specifying a framebuffer
device when there isn't one.


Mark.

On Mon, 20 Oct 2003, Boniforti Flavio wrote:

 In data Mon, 20 Oct 2003 21:14:51 +0200
 Boniforti Flavio [EMAIL PROTECTED] scriveva:
 
  I configured XFree with xf86config... if it can help, I would also
  attach my logfile.
 
 Here is my logfile attached!
 Thank you!
 
 -- 
 Registered Linux User #251752
--- VB LUG Moderator ---
 Any wire cut to length will be too short.
 

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


[XFree86] xev ignores some keypresses

2003-10-20 Thread Dylan Carlson
 I reported a bug that X / xev doesn't register all the button presses 
 (anything above button 3 !) on Logitech mice. Is there any relation 
 between these two ?

Probably.  

But we're not getting any traction on the mailing list with this problem ... 
I was hoping someone more knowledgeable would have commented by now.   I 
find it _impossible_ that other people are not having this problem, as I 
seriously doubt I'm the only guy with a newer Logitech keyboard running 
XFree86.  You can't GET a keyboard nowadays without these extra buttons on 
them.  

Surely I must not be the only one playing with xev/XKeysymDB to get them to 
work...  Note that most of them do work, but 6 of them don't.  

Between your problem with 4-button mice and my keyboard issue, I going to go 
out on a limb and say it smells like a limitation/bug with XFree86 since 
this stuff works fine in Windows(tm).

What's next, file a bug?  

Cheers

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


[XFree86] How To Set The refresh Rate? Please Help.

2003-10-20 Thread Zava
Operative System= Red H. Linux 9.0a
Kernel= 2.4.20-20.9
Nforce 2 Ultra Chipset (Gigab. GA 7N400-L, bios version= F5)
Video= Nvidia Geforce 4 ti 4600 128 mb
Monitor= LG F900P (Flatron)
Cpu= Athlon xp 2600+
Ram= 512 mb pc3200
XFree Version= 4.3.0 (Red H. Linux release: 4.3.0-2) 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
How to set the refresh rate of my monitor?
I have to say that during the installation process, the operative system
doesn't recognise my monitor, so i have manually filled the right
Manufacturer's specifications, but it doesn't ask the refresh rate(s), 
so i can change and set the screen resolutions but not the refresh rate 
that is always at 60 mhz, indipendently from the resolution I set.
Then I used the grafical tool of Red H. to set-change the monitor's
settings, but, again, there's nowhere to fill the refresh rate.
So, how to do? I have read that I should edit and change
the XFree86Config file, but i didn't find, again, a field
where to insert refresh rate(s), or, well, I don't know
how to do, so that's why i ask help.
Thanks and sorry for my bad english, I am from Italy.

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


[XFree86] HOw To Set The Refresh Rate. Help!

2003-10-20 Thread Zava
Operative System= Red H. Linux 9.0a
Kernel= 2.4.20-20.9
Nforce 2 Ultra Chipset (Gigab. GA 7N400-L, bios version= F5)
Video= Nvidia Geforce 4 ti 4600 128 mb
Monitor= LG F900P (Flatron)
Cpu= Athlon xp 2600+
Ram= 512 mb pc3200
XFree Version= 4.3.0 (Red H. Linux release: 4.3.0-2) 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
How to set the refresh rate of my monitor?
I have to say that during the installation process, the operative system
doesn't recognise my monitor, so i have manually filled the right
Manufacturer's specifications, but it doesn't ask the refresh rate(s), 
so i can change and set the screen resolutions but not the refresh rate 
that is always at 60 mhz, indipendently from the resolution I set.
Then I used the grafical tool of Red H. to set-change the monitor's
settings, but, again, there's nowhere to fill the refresh rate.
So, how to do? I have read that I should edit and change
the XFree86Config file, but i didn't find, again, a field
where to insert refresh rate(s), or, well, I don't know
how to do, so that's why i ask help.
Thanks and sorry for my bad english, I am from Italy.

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


[XFree86] how to set the refresh rate?

2003-10-20 Thread Zava
Operative System= Red H. Linux 9.0a
Kernel= 2.4.20-20.9
Nforce 2 Ultra Chipset (Gigab. GA 7N400-L, bios version= F5)
Video= Nvidia Geforce 4 ti 4600 128 mb
Monitor= LG F900P (Flatron)
Cpu= Athlon xp 2600+
Ram= 512 mb pc3200
XFree Version= 4.3.0 (Red H. Linux release: 4.3.0-2) 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6
How to set the refresh rate of my monitor?
I have to say that during the installation process, the operative system
doesn't recognise my monitor, so i have manually filled the right
Manufacturer's specifications, but it doesn't ask the refresh rate(s),
so i can change and set the screen resolutions but not the refresh rate
that is always at 60 mhz, indipendently from the resolution I set.
Then I used the grafical tool of Red H. to set-change the monitor's
settings, but, again, there's nowhere to fill the refresh rate.
So, how to do? I have read that I should edit and change
the XFree86Config file, but i didn't find, again, a field
where to insert refresh rate(s), or, well, I don't know
how to do, so that's why i ask help.
Thanks and sorry for my bad english, I am from Italy.
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] How To Set The Refresh Rate? Please, Help!

2003-10-20 Thread Mark Vojkovich
On 21 Oct 2003, Zava wrote:

 I don't know how to change the refresh rate of the monitor. I don't know
 how to do. I know(well...I think) I should edit and change the
 XF86Config file, but i can't see any voice about refresh rate(s). I have
 to say that the operative system doesn't recognise the monitor, so i
 have manually filled the required fields, with the manufacturer's
 specifications, so that I can set the right screen resolutions, but,
 again, no voices about the refresh rate(s), that it's fixed at 60 mhz.
 Please, Help me.
 Thanks and sorry for my english, i am from Italy.

In the XF86Config, in the Section Monitor there should be
entries for HorizSync and VertRefresh.  From the information
I can see on the web, they should be:

HorizSync   30 - 107
VertRefresh 50 - 200 

for the LG F900P.

Mark.

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


[XFree86] how to set refresh rete, HELP!

2003-10-20 Thread Zava
Operative System= Red H. Linux 9.0a
Kernel= 2.4.20-20.9
Nforce 2 Ultra Chipset (Gigab. GA 7N400-L, bios version= F5)
Video= Nvidia Geforce 4 ti 4600 128 mb
Monitor= LG F900P (Flatron)
Cpu= Athlon xp 2600+
Ram= 512 mb pc3200

XFree Version= 4.3.0 (Red H. Linux release: 4.3.0-2) 27 February 2003
X Protocol Version 11, Revision 0, Release 6.6

How to set the refresh rate of my monitor?
I have to say that during the installation process, the operative system
doesn't recognise my monitor, so i have manually filled the right
Manufacturer's specifications, but it doesn't ask the refresh rate(s),
so i can change and set the screen resolutions but not the refresh rate
that is always at 60 mhz, indipendently from the resolution I set.
Then I used the grafical tool of Red H. to set-change the monitor's
settings, but, again, there's nowhere to fill the refresh rate.
So, how to do? I have read that I should edit and change
the XFree86Config file, but i didn't find, again, a field
where to insert refresh rate(s), or, well, I don't know
how to do, so that's why i ask help.
Thanks and sorry for my bad english, I am from Italy.

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


Re: [XFree86] RESOLVED: I830WaitLpRing() lockup

2003-10-20 Thread David Dawes
On Mon, Oct 20, 2003 at 11:13:12AM +0300, Alexey E. Suslikov wrote:
keywords: openbsd, x11, i830, ring buffer, lockup

 It just occurred to me where I had seen this type of black screen problem
 before.  It happens when using the vesa driver with an 845G.  We work
 around this in the i810 driver by remembering the initial video mode
 and simply re-initialising it when exiting/VT switching instead of using
 the VBE save/restore mechanism.  This workaround is only actived for
 845G hardware.  You could try enabling it for all hardware by changing
 this line in i830_driver.c from:
 
 if (!I845G_VBE_WORKAROUND || !IS_845G(pI830)) {
 
 to:
 
 if (!I845G_VBE_WORKAROUND) {

hmmm... my yesterdays reply was lost somewhere... ok, let's repeat :)

turning on I845G_VBE_WORKAROUND magically SOLVES the problem on
4.3.99.14 in both accel and noaccel setups:

  VideoRam
default(8192)  2048  32768
Accelok ok ok
NoAccel  ok ok ok
NoAccel+SWcursor ok ok ok

That's good news.

David, thanks a lot. if you have some spare time, can you write some
explanations on this case?

It's pretty much as I already said.  Without this workaround, the driver
(just like the vesa driver) uses the video BIOS VBE save/restore calls
to save and restore the original video mode.  Using these appears to be
a problem in at least some cases.  I only ever saw the problem with 845G
systems, and so only enabled the workaround for that case.

The workaround instead saves the original mode number, and uses the
VBE set mode call to go back to that original mode when exiting or VT
switching.

In the 845G cases I saw, where even the generic vesa driver showed this
problem consistently at the first VT switch or exit, it must be a bug
in the video BIOSes.  There are a lot of other variables in the i810/i830
driver case.

Anyway, I'll commit a fix to enable this workaround by default in all cases.

Thanks for the detailed testing and reporting.

David
-- 
David Dawes X-Oz Technologies
www.XFree86.org/~dawes  www.x-oz.com
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86


Re: [XFree86] RESOLVED: I830WaitLpRing() lockup

2003-10-20 Thread Eric Anholt
On Mon, 2003-10-20 at 18:40, David Dawes wrote:
 On Mon, Oct 20, 2003 at 11:13:12AM +0300, Alexey E. Suslikov wrote:
 keywords: openbsd, x11, i830, ring buffer, lockup
 
  It just occurred to me where I had seen this type of black screen problem
  before.  It happens when using the vesa driver with an 845G.  We work
  around this in the i810 driver by remembering the initial video mode
  and simply re-initialising it when exiting/VT switching instead of using
  the VBE save/restore mechanism.  This workaround is only actived for
  845G hardware.  You could try enabling it for all hardware by changing
  this line in i830_driver.c from:
  
  if (!I845G_VBE_WORKAROUND || !IS_845G(pI830)) {
  
  to:
  
  if (!I845G_VBE_WORKAROUND) {
 
 hmmm... my yesterdays reply was lost somewhere... ok, let's repeat :)
 
 turning on I845G_VBE_WORKAROUND magically SOLVES the problem on
 4.3.99.14 in both accel and noaccel setups:
 
   VideoRam
 default(8192)  2048  32768
 Accelok ok ok
 NoAccel  ok ok ok
 NoAccel+SWcursor ok ok ok
 
 That's good news.
 
 David, thanks a lot. if you have some spare time, can you write some
 explanations on this case?
 
 It's pretty much as I already said.  Without this workaround, the driver
 (just like the vesa driver) uses the video BIOS VBE save/restore calls
 to save and restore the original video mode.  Using these appears to be
 a problem in at least some cases.  I only ever saw the problem with 845G
 systems, and so only enabled the workaround for that case.
 
 The workaround instead saves the original mode number, and uses the
 VBE set mode call to go back to that original mode when exiting or VT
 switching.
 
 In the 845G cases I saw, where even the generic vesa driver showed this
 problem consistently at the first VT switch or exit, it must be a bug
 in the video BIOSes.  There are a lot of other variables in the i810/i830
 driver case.
 
 Anyway, I'll commit a fix to enable this workaround by default in all cases.
 
 Thanks for the detailed testing and reporting.

I haven't been following this too closely, but was this happening only
on BSDs?  The VBE thing stuck out in my mind, as there was just an issue
in DRI (the radeon mergedfb changes) where using the generic int10
emulation caused the driver to crash, while the linux-specific one
didn't.  I don't think it got tracked down and a later change fixed it,
but might there be general problems with the generic int10 emulation?  I
know many FreeBSD systems get warnings in the logs about Bad V_BIOS
checksum.  Would any of this be significant?

-- 
Eric Anholt[EMAIL PROTECTED]  
http://people.freebsd.org/~anholt/ [EMAIL PROTECTED]


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


[XFree86] (no subject)

2003-10-20 Thread Satish Nair
Hi,
When i  am trying to install S3 trio64v2 card on linux 7.x  i get the
following error;



XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 23 January 2002
If the server is older than 6-12 months, or if your card is
newer than the above date, look for a newer version before
reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.17-0.13smp i686 [ELF]
Build Host: daffy.perf.redhat.com

Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: /var/log/XFree86.0.log, Time: Tue Oct 21 10:31:26 2003
(==) Using config file: /etc/X11/XF86Config
Parse warning on line 36 of section Keyboard in file /etc/X11/XF86Config
Ignoring obsolete keyword LeftAlt.
Parse error on line 36 of section Keyboard in file /etc/X11/XF86Config
Meta is not a valid keyword in this section.
(EE) Problem parsing the config file
(EE) Error from xf86HandleConfigFile()

Fatal server error:
no screens found

When reporting a problem related to a server crash, please send
the full server output, not just the last messages.
This can be found in the log file /var/log/XFree86.0.log.
Please report problems to [EMAIL PROTECTED]


Please let me know whst is to be done to resolve the above issue.



satish

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


[XFree86] How to set X security to host access?

2003-10-20 Thread Jerre Cope
I am using Slackware 9.1 to connect to and old SCO Unixware box as a 
kind of thin client.  The X on the UnixWare server is too old to 
understand the sshd X11 forwarding, and I need to be able to access the 
Old box with Old thin clients.
( I have alot of reasons to need host access, when they all die--I'll 
use ssh)

I need to able to:
xhost +unixware
telnet unixware
DISPLAY=slackware:0
xterm
Thanks.

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


[XFree86] PROTECT YOUR CHILDREN From Bad Language On Your TV...calliope

2003-10-20 Thread Alisha Cochran
Protect Your Children With ProtecTV.

ProtecTV gives you the power to block the cursing and offensive language coming into 
your home through television and video.

ProtecTV filters out more than 400 offensive words.

ProtecTV works with your TV, VCR, Satellite, Cable Box and DVD player.

ProtecTV is easy to connect.

Get ProtectTV Today - www.coolbrands.net/protectv

Go here if you wish to be excluded from our advertising - 
www.coolbrands.net/emailremovalmanagementcenter.htm









wkmjwsrt
a
fqp