[Xpert]Near-year uptime of an XApplication

2002-09-11 Thread Ralph Nilsson

Has anyone heard of problems with running applications for nearly a year, without 
restart of server or application? We get a crash after 248.5 days, which seems to 
coincide with 2**31 * 10ms.

Any ideas?

Thanks,
 Ralph Nilsson


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



Re: [Xpert]XFree86 dies early without error

2002-09-11 Thread Matthieu Herrb

Markus Gutschke wrote (in a message from Monday 9)
  [EMAIL PROTECTED] wrote:
   Sep  9 18:36:13 [kernel] PAX: terminating task:
   /usr/X11R6/bin/XFree86(XFree86):23363, uid/euid: 0/0, EIP: 08247BB8, ESP:
   BFF31D0C
   o
   
   So it IS the kernel's fault. Google says PAX controls security. I have
   someplace to start now, but feel free to shout out the quick fix if you see
   one.
  
  This is what is says in the PAX patch file:
  
  +  Enabling this feature will enforce the non-executable flag on
  +  memory pages thereby making it harder to execute 'foreign' code
  +  in a program.  This will also break programs that rely on the
  +  old behaviour and expect that dynamically allocated memory via
  +  the malloc() family of functions is executable (which it is not).
  +  Notable examples are the XFree86 4.x server, the java runtime
  +  and wine.
  +

Do the PAX patches allow mprotect() calls to make the allocated pages
executable ? 

The XFree86 ELF loader currently miss a few mprotect() calls, but I've
a patch that adds the missing calls and make the loader happy again on
OpenBSD architectures that have non-executable heap now. It should
work too with PAX if it implements mprotect(). 

Matthieu
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: SOLVED [Xpert]Fw: Segmentation fault

2002-09-11 Thread Trevor Fraser

Thanks a whole lot, I'm using the exact same chip set and I think you must
have solved a problem for many out there.  I'll keep this mail close by if
you don't mind, and forward to anybody with the same problem.

Thanks again, on behalf of all whom this helps.
Trevor.

- Original Message -
From: Neil R. Simon [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, September 11, 2002 4:53 AM
Subject: SOLVED [Xpert]Fw: Segmentation fault


 Hi Trevor.  I saw your post on XFree86.org, and just solved that same
problem on
 my box.

 I've noticed many posts recently that describe this same problem.
Especially
 when people upgrade to RH 7.3 from an earlier rev that worked just fine.

 I traced this to the RH 7.3 installation program having made an erroneous
 symbolic link of the X server.

 Was: /usr/X11R6/bin/X - /usr/X11R6/bin/XFree86 (the 4.2.0 X server)

 Should be: /usr/X11R6/bin/X - /usr/X11R6/bin/XF86_S3 (the 3.3.6 X server,
which
 the installation program DID properly install, but DID NOT link to).

 XF86_S3 may not, however, be the right X server on your particular box if
you
 have a different video chipset.

 However, you should be able to find the right one to link to in your
 /usr/X11R6/bin directory.

 If you want to relink the X symlink, here's what to do:

 1) chdir to the X bin directory
 # cd /usr/X11R6/bin

 2) remove the existing symbolic link of X
 # rm X

 3) relink to X server that your 7.3 installer created for your S3 Trio64
chipset

 # ln -s XF86_S3 X

 4) update the permissionsons on the XF86_S3 server (or only root will be
able
 to run the startx command)
 # chmod 4711 XF86_S3

 Hope this helps.

 Regards, Neil

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



[Xpert]X process redirection...

2002-09-11 Thread Fabrizio Morbini

Hi, Is possible the redirection of a running X application from a display
to another?

For example:

-start rxvt with DISPLAY=localhost:0.0
-the I must move the rxvt window to hostname:0.0 display

Thank you and Best Regards.

Fabrizio.

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



[Xpert]dri

2002-09-11 Thread Sam Halliday

hello there,

i was wondering if somebody could please set me
straight on the whole dri thing... i am currently
recompiling my entire system (LFS... sometimes rpms
seem like a good idea!) and i have reached the
(almost) final stage... XFree86.

I have a voodoo3000 card which i see is supported by
the dri system and i think it is about time i got the
accelerated graphics working! My question is this...
do i need to get the latest dri source from cvs, or
does the latest XFree86-4.2.1 have enough in it that i
can compile dri support without any additional adons?
(well, besides libglide3) and if so, what must i
specify in my host.def?

i noticed in my (partial) compile of XFree86 today
that i had a few dri_xxx.o files in the lib/modules
folder. Are these what i think they are? ie. are these
the accelerated graphics modules for the associated
cards?

i quess what i am tryign to ask is this... is dri in
the stable XFree86 release now?

i hope i have made sense... probably haven't
thanks in advance!
Sam

__
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]faking keyboard input

2002-09-11 Thread Mikael Claesson

Hello.

I'd like to write a program which sends fake keyboard
events to application windows. Not only to the
currently focused window, but to any window.
Preferably the window would be identified by its title
(on the title bar).

Is this possible? Could anyone point me in the right
direction? I don't mind reading man pages or whatever,
but I need to know which ones to read. :-) Any help
would be much appreciated.

Thank you

/M


__
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread Arkadiusz Miskiewicz

Vladimir Dergachev [EMAIL PROTECTED] writes:

 Try adding
 Option ChipId 0x4243

Hm, I don't see 0x4243 in xf86PciInfo.h but I've tried
all these:

#define PCI_CHIP_R200_BB0x4242
#define PCI_CHIP_R200_QL0x514C
#define PCI_CHIP_R200_QN0x514E
#define PCI_CHIP_R200_QO0x514F
#define PCI_CHIP_R200_Ql0x516C

Unfortunately I get only to
(==) RADEON(0): Write-combining range (0xe400,0x400)

Fatal server error:
Caught signal 8.  Server aborting

Log from console:

XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 11 March 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.2.20 i686 [ELF] 
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: Wed Sep 11 12:00:54 2002
(==) Using config file: /etc/X11/XF86Config
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found

Fatal server error:
Caught signal 8.  Server aborting


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]

Aborted (core dumped)

---
And /var/log/XFree86.0.log


XFree86 Version 4.2.0 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 11 March 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.2.20 i686 [ELF] 
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: Wed Sep 11 12:01:47 2002
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout XFree86 Configured
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Card0
(**) |--Input Device Mouse0
(**) |--Input Device Mouse1
(**) |--Input Device Keyboard0
(**) Option AutoRepeat 500 30
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc104
(**) XKB: model: pc104
(**) Option XkbLayout pl
(**) XKB: layout: pl
(**) Option XkbOptions altwin:left_meta_win
(**) XKB: options: altwin:left_meta_win
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to unix/:7100
(==) RgbPath set to /usr/X11R6/lib/X11/rgb
(==) ModulePath set to /usr/X11R6/lib/modules
(--) using VT number 11

(WW) Open APM failed (/dev/apm_bios) (No such file or directory)
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.5
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(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.2.0, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(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.2.0, module version = 0.1.0
ABI class: XFree86 Video Driver, version 0.5
(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 1106,0305 card 147b,a401 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 1106,0686 card 147b, rev 22 class 06,01,00 hdr 80
(II) PCI: 00:07:1: chip 1106,0571 card 1106,0571 rev 10 class 01,01,8a hdr 00
(II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00
(II) PCI: 00:07:4: chip 1106,3057 card 1106,3057 rev 30 class 06,80,00 hdr 00
(II) PCI: 00:09:0: chip 109e,036e card , rev 11 class 04,00,00 hdr 80
(II) PCI: 00:09:1: chip 109e,0878 card , rev 11 class 04,80,00 hdr 80
(II) PCI: 00:0b:0: chip 105a,4d68 card 105a,4d68 rev 01 class 01,80,85 hdr 00
(II) PCI: 00:0d:0: chip 10b7,9200 card 10b7,1000 rev 6c class 02,00,00 hdr 00
(II) PCI: 00:0f:0: chip 104c,ac50 card 

Re: [Xpert]faking keyboard input

2002-09-11 Thread Viveka Nathan K


you can use XTestFakeKeyEvent() function as
  XTestFakeKeyEvent(dpy,x,y,z);
where dpy for display, x is Keycode, y is keyPress or release and 
z is timeduration, after which this event generated.

On Today [EMAIL PROTECTED] wrote to Vivek :

MC:}Hello.
MC:}
MC:}I'd like to write a program which sends fake keyboard
MC:}events to application windows. Not only to the
MC:}currently focused window, but to any window.
MC:}Preferably the window would be identified by its title
MC:}(on the title bar).
MC:}
MC:}Is this possible? Could anyone point me in the right
MC:}direction? I don't mind reading man pages or whatever,
MC:}but I need to know which ones to read. :-) Any help
MC:}would be much appreciated.
MC:}
MC:}Thank you
MC:}
MC:}/M
MC:}
MC:}
MC:}__
MC:}Yahoo! - We Remember
MC:}9-11: A tribute to the more than 3,000 lives lost
MC:}http://dir.remember.yahoo.com/tribute
MC:}___
MC:}Xpert mailing list
MC:}[EMAIL PROTECTED]
MC:}http://XFree86.Org/mailman/listinfo/xpert
MC:}

-- 

 Vivek
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= 
 DON Lab, IITM, Chennai-36, India. Ph:044-2578904, 044-2578353
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Only weapon we are having from the beginning is BRAIN

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



[Xpert]chips-driver bug ?

2002-09-11 Thread Markus Klein

Hello.

It's some time ago that I wrote to this list.
I commenced in the Newbie-archiv with:
http://xfree86.org/pipermail/newbie/2002-August/017118.html
Later I posted to this list with:
http://xfree86.org/pipermail/xpert/2002-August/020322.html
In the meantime I have installed debian-3 (woody) and this brought me some
new info.
I already believed that xfree4 wouldn't work for my old laptop but debian
showed me something different with xfree-4.1.0-16. The config of this
x-server was no problem at all ! After Debian Linux brought the solution
I re-installed gentoo-Linux because this is what I actually want. Gentoo
Linux comes with xfree-4.2.0.
In the meantime somebody from this list still wrote a message concerning
clock-settings for my problem. (Unfortunatly I accidendly deleted the mail -
therefore I don't know anymore who the kind sender was. If you read this:
thnx)
So I tried the XFreeConfig-4 from Debian and I set up a new XFreeConfig-4
with some Clock-Setting-Options...
And you know what: I still have the same problem like at the beginning !!
The screen becomes white slowly after 1..3 secondes. It seems like
overcharging. With both configs. No matter what I do.

(I'll attach the Debian-Config + /var/log/XFree.log
and
my new clock-setting-config + /var/log/XFree.log.
Have to split it into two emails because it's too big
)

Can anybody imagine why this still does not work ? I mean: Wouldn't a
xfree4.1 have the same config-format like xfree4.2. Doesn't this mean that a
bug in the Chips-driver is the last explanation which rests ?
thnx for reading
mox

***config from debian:

### BEGIN DEBCONF SECTION
# XF86Config-4 (XFree86 server configuration file) generated by dexconf, the
# Debian X Configuration tool, using values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type man XF86Config-4 at the shell prompt.)
#
# If you want your changes to this file preserved by dexconf, only make
changes
# before the ### BEGIN DEBCONF SECTION line above, and/or after the
# ### END DEBCONF SECTION line below.
#
# To change things within the debconf section, run the command:
#   dpkg-reconfigure xserver-xfree86
# as root.  Also see How do I add custom sections to a dexconf-generated
# XF86Config or XF86Config-4 file? in /usr/share/doc/xfree86-common/FAQ.gz.

Section Files
FontPathunix/:7100# local font server
# if the local font server has problems, we can fall back on these
FontPath/usr/lib/X11/fonts/misc
FontPath/usr/lib/X11/fonts/cyrillic
FontPath/usr/lib/X11/fonts/100dpi/:unscaled
FontPath/usr/lib/X11/fonts/75dpi/:unscaled
FontPath/usr/lib/X11/fonts/Type1
FontPath/usr/lib/X11/fonts/Speedo
FontPath/usr/lib/X11/fonts/100dpi
FontPath/usr/lib/X11/fonts/75dpi
EndSection

Section Module
Loadbitmap
Loaddbe
Loadddc
Loaddri
Loadextmod
Loadfreetype
Loadint10
Loadpex5
Loadrecord
Loadtype1
Loadvbe
Loadxie
EndSection

Section InputDevice
Identifier  Generic Keyboard
Driver  keyboard
Option  CoreKeyboard
Option  XkbRules  xfree86
Option  XkbModel  pc104
Option  XkbLayout de
#Option XkbVariantqwertz/de
EndSection

Section InputDevice
Identifier  Configured Mouse
Driver  mouse
Option  CorePointer
Option  Device/dev/psaux
Option  Protocol  PS/2
Option  Emulate3Buttons   true
EndSection

Section InputDevice
Identifier  Generic Mouse
Driver  mouse
Option  SendCoreEventstrue
Option  Device/dev/input/mice
Option  Protocol  ImPS/2
Option  Emulate3Buttons   true
EndSection

Section Device
Identifier  Generic Video Card
Driver  chips
VideoRam1024
EndSection

Section Monitor
Identifier  Generic Monitor
HorizSync   31.5-32
VertRefresh 58-62
Option  DPMS
EndSection

Section Screen
Identifier  Default Screen
Device  Generic Video Card
Monitor Generic Monitor
DefaultDepth16
SubSection Display
Depth   1
Modes   640x480
EndSubSection
SubSection Display
Depth   4
Modes   640x480
EndSubSection
SubSection Display
Depth   8
Modes   

[Xpert]chips-driver bug ?

2002-09-11 Thread Markus Klein

second part of my email:


***config with clock-setting:

# File generated by xf86config.

#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the Software),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
#
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
#
# THE SOFTWARE IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# THE XFREE86 PROJECT BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
#
# Except as contained in this notice, the name of the XFree86 Project shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from the
# XFree86 Project.
#

# **
# Refer to the XF86Config(4/5) man page for details about the format of
# this file.
# **

# **
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **
#
Section Module

# This loads the DBE extension module.

Loaddbe   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
SubSection  extmod
  Optionomit xfree86-dga   # don't initialise the DGA extension
EndSubSection

# This loads the Type1 and FreeType font modules
Loadtype1
Loadfreetype
Loaddri

# This loads the GLX module
#Load   glx

EndSection

# **
# Files section.  This allows default font and rgb paths to be set
# **

Section Files

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like .txt or .db).  There is normally
# no need to change the default.

RgbPath /usr/X11R6/lib/X11/rgb

# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
#
# If you don't have a floating point coprocessor and emacs, Mosaic or other
# programs take long to start up, try moving the Type1 and Speedo directory
# to the end of this list (or comment them out).
#

FontPath   /usr/X11R6/lib/X11/fonts/local/
FontPath   /usr/X11R6/lib/X11/fonts/misc/
FontPath   /usr/X11R6/lib/X11/fonts/75dpi/:unscaled
FontPath   /usr/X11R6/lib/X11/fonts/100dpi/:unscaled
FontPath   /usr/X11R6/lib/X11/fonts/Type1/
FontPath   /usr/X11R6/lib/X11/fonts/Speedo/
FontPath   /usr/X11R6/lib/X11/fonts/75dpi/
FontPath   /usr/X11R6/lib/X11/fonts/100dpi/

# The module search path.  The default path is shown here.

#ModulePath /usr/X11R6/lib/modules

EndSection

# **
# Server flags section.
# **

Section ServerFlags

# Uncomment this to cause a core dump at the spot where a signal is
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging
Option PciOsConfig
#Option NoTrapSignals

# Uncomment this to disable the CrtlAltBS server abort sequence
# This allows clients to receive this key event.

#Option DontZap

# Uncomment this to disable the CrtlAltKP_+/KP_- mode switching
# sequences.  This allows clients to receive these key events.

#Option Dont Zoom

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#Option DisableVidModeExtension

# Uncomment this to enable the use of a non-local xvidtune client.

#Option AllowNonLocalXvidtune

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) 

Re: [Xpert]xf86config parser

2002-09-11 Thread SainTiss

Hi,

I assume you are talking about CVS directories here, since I can't find
the mentioned directory on my system...

Also, does this mean there's no real documentation, but just examples?

Thanks

Hans

On Tue, 2002-09-10 at 23:43, [EMAIL PROTECTED] wrote:
  Hi,
  
  I was writing an XF86Config parser from scratch, when I noticed there's
  a python wrapper for this... 
  However, I'm writing my tool in c++, so I need the C source... I found a
  file called xf86Parser.h, but couldn't find any documentation about
  it...
  
  Is this the right file, and if so, where can I find docs about it?
 
 
 That file is from the xc/programs/Xserver/hw/xfree86/parser subdirectory which
 contains the code for libxf86config.a which is the parser library (it can write
 the files too).  The cpconfig.c source in that directory provides a simple usage
 example.
 
 ___
 Xpert mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/xpert
 




signature.asc
Description: This is a digitally signed message part


Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread Arkadiusz Miskiewicz

Charl P. Botha [EMAIL PROTECTED] writes:

 That's probably the reason WHY you should try ChipId 0x4243.
Weird. I thought that by using ChipID someid (like 0x4242) I'm
telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242),
belive me and don't autodetect.

What 0x4243 is supposed to mean?

pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4966
 ATI  Device unknown
pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x496e
 ATI  Device unknown

Anyway here it is:

Section Device
Identifier  Card0
Driver  radeon
VendorName  ATI
BoardName   Radeon 9000
Option  ChipID 0x4243
#   ChipID  0x4242
EndSection

and

[...]
(II) Primary Device is: PCI 01:00:0
(--) Assigning device section with no busID to primary device
(WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
(EE) No devices detected.

Fatal server error:
no screens found

 charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/

-- 
Arkadiusz Mikiewicz  niestety kloczek lubi by dyktatorem
[EMAIL PROTECTED]AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread Vladimir Dergachev



On 11 Sep 2002, Arkadiusz Miskiewicz wrote:

 Charl P. Botha [EMAIL PROTECTED] writes:

  That's probably the reason WHY you should try ChipId 0x4243.
 Weird. I thought that by using ChipID someid (like 0x4242) I'm
 telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242),
 belive me and don't autodetect.

 What 0x4243 is supposed to mean?

It's a pci id of AIW Radeon 8500 DV. Perhaps it has not made into linux
kernel yet. Also try this:

Option ChipId 0x4243

If still does not work try ati.2 drivers from http://gatos.sf.net/

   Vladimir Dergachev


 pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4966
  ATI  Device unknown
 pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x496e
  ATI  Device unknown

 Anyway here it is:

 Section Device
 Identifier  Card0
 Driver  radeon
 VendorName  ATI
 BoardName   Radeon 9000
 Option  ChipID 0x4243
 #   ChipID  0x4242
 EndSection

 and

 [...]
 (II) Primary Device is: PCI 01:00:0
 (--) Assigning device section with no busID to primary device
 (WW) RADEON: No matching Device section for instance (BusID PCI:1:0:1) found
 (EE) No devices detected.

 Fatal server error:
 no screens found

  charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/

 --
 Arkadiusz Mi¶kiewicz  niestety kloczek lubi byæ dyktatorem
 [EMAIL PROTECTED]AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr
 ___
 Xpert mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/xpert


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



Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread Charl P. Botha

On Wed, Sep 11, 2002 at 02:19:01PM +0200, Arkadiusz Miskiewicz wrote:
 Charl P. Botha [EMAIL PROTECTED] writes:
  That's probably the reason WHY you should try ChipId 0x4243.
 Weird. I thought that by using ChipID someid (like 0x4242) I'm
 telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242),
 belive me and don't autodetect.
 
 What 0x4243 is supposed to mean?
 
 pci bus 0x0001 cardnum 0x00 function 0x00: vendor 0x1002 device 0x4966
  ATI  Device unknown
 pci bus 0x0001 cardnum 0x00 function 0x01: vendor 0x1002 device 0x496e
  ATI  Device unknown

Aaah, I didn't read your first email.  Have you tried:
ChipId 0x4966
in the Device section?  It will connect that device section to the unknown
ATI device, which is of course your ATI video card, which should at least
eliminate the RADEON: No matching device section for ... 

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread Charl P. Botha

On Wed, Sep 11, 2002 at 02:19:01PM +0200, Arkadiusz Miskiewicz wrote:
 Charl P. Botha [EMAIL PROTECTED] writes:
  That's probably the reason WHY you should try ChipId 0x4243.
 Weird. I thought that by using ChipID someid (like 0x4242) I'm
 telling XFree: hey, this device is XYZ (Radeon 8500 BB for 0x4242),
 belive me and don't autodetect.

Ugh, my apologies.  You are completely correct... I misunderstood the ChipId
documentation.

-- 
charl p. botha http://cpbotha.net/ http://visualisation.tudelft.nl/
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]X process redirection...

2002-09-11 Thread Mikael Claesson

Sounds neat. Could this be used to protect an
application against a crashing X server as well? Or is
there a better way of doing that?

/M

--- Robin Rosenberg [EMAIL PROTECTED]
wrote:
 onsdagen den 11 september 2002 11.13 skrev Fabrizio
 Morbini:
  Hi, Is possible the redirection of a running X
 application from a display
  to another?
 
 There is a proxy server called xmove that can be
 used. The visuals of all
 involved displays must match, and you must start the
 application using xmove
 to begin with. I believe you loose most extensions
 this way too.
 
 An alternative may be to start the application
 inside Xvnc.
 
 -- robin
 
 ___
 Xpert mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/xpert


__
Yahoo! - We Remember
9-11: A tribute to the more than 3,000 lives lost
http://dir.remember.yahoo.com/tribute
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread Xavier Bestel

Ok, sorry to have wasted bandwidth and brain cells, I'm back to 4.1 and
it still freezes. I really dunno why it fails now. I tried changing
kernel versions, even reflashing motherboard bios to all possible
revisions ... no way, it still freezes.
I noticed the nvidia uses the same pirq than my network card, but even
when I remove it (the nvidia), my pc still fails.

It seems really bound to X activity: I can compile kernels or do
otherwise cpu-intensive tasks for hours without problems, but if I use
galeon or xine or other X-intensive tasks, it freezes after a while
(seconds or minutes or more).

Does any of you have experience about such failures ? Can it be
hardware-related ? BIOS-related ? I didn't change my hardware and it was
working very well a month ago.

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



Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread Arkadiusz Miskiewicz

Vladimir Dergachev [EMAIL PROTECTED] writes:

  What 0x4243 is supposed to mean?
 
 It's a pci id of AIW Radeon 8500 DV.
So another unsupported one.

 Perhaps it has not made into linux
 kernel yet. 
kernel? support in kernel is required for DRI. I'm trying
to get XFree working even without DRI.

 Also try this:
 
 Option ChipId 0x4243
XFree drivers do not support 0x4243. It will not work.

 If still does not work try ati.2 drivers from http://gatos.sf.net/
gatos drivers also don't support 0x4243 (don't support
my radeon, too)

Vladimir Dergachev

btw. how PCI IDs are managed? Vendor (like ATI) gets some ID space
(as in with MAC on network cards) and does whathever it wants in
that assigned space? Or maybe vendor is required to register
each product in some global database?

ps. response from ati support sucks, automated message ;/
-- 
Arkadiusz Mikiewicz  niestety kloczek lubi by dyktatorem
[EMAIL PROTECTED]AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]XFree86 dies early without error

2002-09-11 Thread Markus Gutschke

Matthieu Herrb wrote:
 Do the PAX patches allow mprotect() calls to make the allocated pages
 executable ? 
 
 The XFree86 ELF loader currently miss a few mprotect() calls, but I've
 a patch that adds the missing calls and make the loader happy again on
 OpenBSD architectures that have non-executable heap now. It should
 work too with PAX if it implements mprotect(). 

PAX is very flexible this way and allows for the user to configure whether 
mprotect() can be used to change permissions on pages. So, yes, a patch that 
added all the missing mprotect() calls would definitly make the code more 
friendly towards environments such as PAX.


Markus

-- 
Markus Gutschke
3637 Fillmore Street #106
San Francisco, CA 94123-1600
+1-415-567-8449
[EMAIL PROTECTED]

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



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread J. Imlay

 Ok, sorry to have wasted bandwidth and brain cells, I'm back to 4.1 and
 it still freezes. I really dunno why it fails now. I tried changing
 kernel versions, even reflashing motherboard bios to all possible
 revisions ... no way, it still freezes.
 I noticed the nvidia uses the same pirq than my network card, but even
 when I remove it (the nvidia), my pc still fails.

 It seems really bound to X activity: I can compile kernels or do
 otherwise cpu-intensive tasks for hours without problems, but if I use
 galeon or xine or other X-intensive tasks, it freezes after a while
 (seconds or minutes or more).

 Does any of you have experience about such failures ? Can it be
 hardware-related ? BIOS-related ? I didn't change my hardware and it was
 working very well a month ago.

Yes, I have a friend who's computer does this. If he doesn't use X his
computer will run for days, in fact if he doesn't run X his computer will
run for days. But he can walk over and sit down and touch the mouse and a
few minutes later his box just dies. Never at a particular time, it seemed
sound related for a while, but it's not because sometimes it does it with
out sound.It did it in windows 98, ME, and 2k, as well as linux. Started
about a year ago. But he has k6-2 400, NVidia TNT2. He's tried swapping
memory and cpu and video card, and it wasn't any of those. Only thing left
is mother board. But just similar symptoms, so I couldn't say if it's the
same boat your in.

Hope that helps,
Let me know if you figure it out.

Thanks,
Josie Imlay


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


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



Re: [Xpert]xf86config parser

2002-09-11 Thread SainTiss

Right, I thought it was some include directory, but it seems to be a
source directory... I found it :-)

Shame about the documentation though...

Thanks

Hans

On Wed, 2002-09-11 at 18:54, J. Imlay wrote:
  Hi,
 
  I assume you are talking about CVS directories here, since I can't find
  the mentioned directory on my system...
 
 you don't have this directory?
 
 xc/programs/Xserver/hw/xfree86/parser/
 
 That doesn't make sence. It's not CVS. Do you have the a recent source, a
 tarbal like this X420src-1.tgz? It's quite strait forward.
 
 tar -zxf XF420src-1.tgz
 cd xc/programs/Xserver/hw/xfree86/parser/
 
 Is it still missing.
 
  Also, does this mean there's no real documentation, but just examples?
 
 The only real documentation is the source. All other forms of
 documentation or out of date by definition. :) In all seriousness, no
 probably not. most of the code expecialy the stuff that is part of the dix
 (device independant layer) doesn't realy have any documentation except a
 few random essays about different parts. And the ddx (dependant) has only
 enough documentation to sqeek by.
 
 If some one proves me wrong though, I'd be delighted.
 
 Josie Imlay
 
 ___
 Xpert mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/xpert
 




signature.asc
Description: This is a digitally signed message part


[Xpert]sis problems

2002-09-11 Thread Nicholas Lafferty

I'm having problems getting x to run on three diskless ThinkNIC clients.
Everything I have tried results in a black screen. They have a SiS5597
graphics card.
I'm using XFREE86-4.0.3 on the nfs server. The monitors I'm using are NEC
Accusync90 and KDS Visual Sensations. Any Experience with the sis driver?
Any help would be great. Thanks

Nicholas Lafferty
Manager
Pennswoods.net
Country Club Mall

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



[Xpert]G550 + G400, overlay problems

2002-09-11 Thread Matthew Mitchell

Hello everyone.  I can't get a dual-head configuration using an AGP G550 
and a PCI G400 working under either XFree 4.2.0 or 4.2.1 with either the 
XFree mga driver or the Matrox mga driver.  (I am also asking Matrox 
about this.)

The system in question is a mostly-stock Red Hat 7.3 installation, with 
the XFree 4.2.1 binary upgrade installed atop the Red Hat XFree 4.2.0 
packages.

Some things I've tried:

1) In the bios, one card is anointed the primary display adapter. 
Whichever card so anointed works fine; the other does not produce any 
video in X, with no errors reported (it is like the card is switched off).

2) I tried moving the PCI card to a different slot, which made no 
difference in any perceptible way (PCI id stayed the same).

3) The cards don't work in any color depth that I tried -- I need 
overlay support for this workstation because we have some brain-dead 
apps that require PseudoColor, but it won't even work with both displays 
in 8 bit, Xinerama or no, DRI or no (which shouldn't work anyway, but I 
did explicitly turn it off).

4) Using the Matrox drivers, both displays turn on but the secondary has 
some serious psychedelic visuals on it and the first has some mouse 
pointer issues.  Personally, I'd rather use the XFree drivers if they 
can be made to work.

Does anyone have any experience getting two of these cards to work 
together?  Perhaps the Red Hat kernel is causing problems?

Any advice, suggestions, or questions appreciated.

Thanks in advance,

Matt Mitchell
Systems Programmer
Geophysical Development Corporation

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



Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread Arkadiusz Miskiewicz

Arkadiusz Miskiewicz [EMAIL PROTECTED] writes:

 Unfortunately current radeon drivers does not have PCI ID of
 this card (afaik even in xfree cvs).
Just tried today cvs version of xfree from HEAD. With overriding
ChipID  0x4242
got X running but there is one problem reading/localizing BIOS
(II) RADEON(0): initializing int10
(WW) RADEON(0): Bad V_BIOS checksum
(II) RADEON(0): Primary V_BIOS segment is: 0xc000
and second problem with ,,out of scan range'' problaby due to BIOS
problem (my monitor turned screen off).

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.2.99.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 7 June 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.19 i686 [ELF] 
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: Wed Sep 11 19:44:14 2002
(==) Using config file: /etc/X11/XF86Config
(==) ServerLayout XFree86 Configured
(**) |--Screen Screen0 (0)
(**) |   |--Monitor Monitor0
(**) |   |--Device Card0
(**) |--Input Device Mouse0
(**) |--Input Device Mouse1
(**) |--Input Device Keyboard0
(**) Option AutoRepeat 500 30
(**) Option XkbRules xfree86
(**) XKB: rules: xfree86
(**) Option XkbModel pc104
(**) XKB: model: pc104
(**) Option XkbLayout pl
(**) XKB: layout: pl
(**) Option XkbOptions altwin:left_meta_win
(**) XKB: options: altwin:left_meta_win
(==) Keyboard: CustomKeycode disabled
(**) FontPath set to unix/:7100
(==) RgbPath set to /mnt/storage1/misiek/xfree/lib/X11/rgb
(==) ModulePath set to /mnt/storage1/misiek/xfree/lib/modules
(--) using VT number 11

(II) Open APM successful
(II) Module ABI versions:
XFree86 ANSI C Emulation: 0.1
XFree86 Video Driver: 0.6
XFree86 XInput driver : 0.3
XFree86 Server Extension : 0.1
XFree86 Font Renderer : 0.3
(II) Loader running on linux
(II) LoadModule: bitmap
(II) Loading /mnt/storage1/misiek/xfree/lib/modules/fonts/libbitmap.a
(II) Module bitmap: vendor=The XFree86 Project
compiled for 4.2.99.1, module version = 1.0.0
Module class: XFree86 Font Renderer
ABI class: XFree86 Font Renderer, version 0.3
(II) Loading font Bitmap
(II) LoadModule: pcidata
(II) Loading /mnt/storage1/misiek/xfree/lib/modules/libpcidata.a
(II) Module pcidata: vendor=The XFree86 Project
compiled for 4.2.99.1, 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 = 0x, mode1Res1 = 0x8000
(II) PCI: PCI scan (all values are in hex)
(II) PCI: 00:00:0: chip 1106,0305 card 147b,a401 rev 02 class 06,00,00 hdr 00
(II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01
(II) PCI: 00:07:0: chip 1106,0686 card 147b, rev 22 class 06,01,00 hdr 80
(II) PCI: 00:07:1: chip 1106,0571 card 1106,0571 rev 10 class 01,01,8a hdr 00
(II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00
(II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 10 class 0c,03,00 hdr 00
(II) PCI: 00:07:4: chip 1106,3057 card 1106,3057 rev 30 class 06,80,00 hdr 00
(II) PCI: 00:09:0: chip 109e,036e card , rev 11 class 04,00,00 hdr 80
(II) PCI: 00:09:1: chip 109e,0878 card , rev 11 class 04,80,00 hdr 80
(II) PCI: 00:0b:0: chip 105a,4d68 card 105a,4d68 rev 01 class 01,80,85 hdr 00
(II) PCI: 00:0d:0: chip 10b7,9200 card 10b7,1000 rev 6c class 02,00,00 hdr 00
(II) PCI: 00:0f:0: chip 104c,ac50 card d400, rev 01 class 06,07,00 hdr 02
(II) PCI: 00:11:0: chip 1102,0002 card 1102,8064 rev 07 class 04,01,00 hdr 80
(II) PCI: 00:11:1: chip 1102,7002 card 1102,0020 rev 07 class 09,80,00 hdr 80
(II) PCI: 01:00:0: chip 1002,4966 card 174b,7197 rev 01 class 03,00,00 hdr 80
(II) PCI: 01:00:1: chip 1002,496e card 174b,7196 rev 01 class 03,80,00 hdr 00
(II) PCI: End of PCI scan
(II) Host-to-PCI 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  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,1), BCTRL: 0x0c (VGA_EN is set)
(II) Bus 1 I/O 

Re: [Xpert]X process redirection...

2002-09-11 Thread Mark Vojkovich

On Wed, 11 Sep 2002, Fabrizio Morbini wrote:

 Hi, Is possible the redirection of a running X application from a display
 to another?
 
 For example:
 
 -start rxvt with DISPLAY=localhost:0.0
 -the I must move the rxvt window to hostname:0.0 display
 

   X11 doesn't support that, but maybe there is some sort of 
proxy server that you could run between rxvt that could make
something like that possible, but I haven't heard of one.

   Of course rxvt could be hacked to support that (with alot of
work).

Mark.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



RE: [Xpert]ATI Radeon 9000

2002-09-11 Thread Alexander Stohr
Title: RE: [Xpert]ATI Radeon 9000





Hello,


   What 0x4243 is supposed to mean?
  
  It's a pci id of AIW Radeon 8500 DV.
 So another unsupported one.


No, according to the PCI ID database on www.yourvote.com 
0x4243 the piggy back firewire port of the 8500 DV.
This is indeed not a grafics chip at all.
Who the heck has come up with that bogus ID?


In the PCI device listing you will clearly find
the correct ID of this ATI Radeon 9000 card: 0x4966


Charl is finally most right with his proposal:
 ChipId 0x4966


(i dont use that because when i am developing
i am always having a full X11 tree handy and
then i just add the IDs directly into my code,
a few seconds recompile of the ddx driver module
and its done...)


you had two IDs in your specific case, thats why:
only primary function 0 does identify the chip,
any further device functions only do have different IDs 
if they do provide something different with the same silicon,
a thing that is often seen on intel's bus bridges.


  Perhaps it has not made into linux kernel yet. 
 kernel? support in kernel is required for DRI. 
 I'm trying to get XFree working even without DRI.


The write meant something different - the coding of DRI
partially is kernel based and uses the constant defines
from linux kernel header files (which do originate from
the yourvote.com site). As the Radeon 9000 is a pretty
new board the Linux kernel is possibly just updating this,
but the DRI project hasnt identified this addition.
Thats a development thing users should not care to much.


For users there is just the method of browsing their pci 
configuration and add the yet not known compatible devices
to their config file by the ChipID statement.


  Also try this:
  Option ChipId 0x4243
 XFree drivers do not support 0x4243. It will not work.


that boy was hoaxing with his suggestion or using the FAQ template?


  If still does not work try ati.2 drivers from http://gatos.sf.net/
  gatos drivers also don't support 0x4243 (don't support my radeon, too)


must be the same boy as above


 btw. how PCI IDs are managed? Vendor (like ATI) gets some ID space
 (as in with MAC on network cards) and does whathever it wants in
 that assigned space? Or maybe vendor is required to register
 each product in some global database?


There is an organsiation called PCI Special Interests Group (www.pcisig.com)
that does work on specs. Its a big business club. And it registers the
misc companys with a vendor ID. The device IDs are in the duty of the
respective vendors. Each of these IDs is 16 bits wide. 
If you use up 50 device IDs a year, you will have mor than 1000 years 
of time until you have to register for a secondary vendor ID.


 ps. response from ati support sucks, automated message ;/


hmm. that means customer support got your mail. ;-)
anyways X11-DRI drivers are supported by their respective vendors.


-Alex.





Re: [Xpert]X process redirection...

2002-09-11 Thread Jim.Gettys

Fabrizio,

Current GTK 2 CVS has code for screen migration (even between X servers)
A person at Sun (whose name I always forget) did the screen migration stuff
this spring, I then tested it worked even between servers, and Owen Taylor
has since done some work to try to shake out more of the resulting problems.
So making GTK/gnome apps migrate is within reach.

There are security implications to this, of course, which need work.

Also, emacs has had migration capability for a decade.

Unfortunately, naive Xlib/Xt apps are unlikely to be retrofit this way;
it requires some thought when you design a toolkit, something that has been
sadly lacking.
  - Jim

--
Jim Gettys
Cambridge Research Laboratory
HP Labs, Hewlett-Packard Company
[EMAIL PROTECTED]

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



Re: [Xpert]sis problems

2002-09-11 Thread Zoilo

On Wednesday 11 September 2002 19:21, Nicholas Lafferty wrote:
 I'm having problems getting x to run on three diskless ThinkNIC clients.
 Everything I have tried results in a black screen. They have a SiS5597
 graphics card.
 I'm using XFREE86-4.0.3 on the nfs server. The monitors I'm using are NEC
 Accusync90 and KDS Visual Sensations. Any Experience with the sis driver?
 Any help would be great. Thanks

You may want to check the LTSP mailinglists at www.ltsp.org (Linux Terminal 
Server Project) for ThinkNIC; some people have been using it as a thin 
client for LTSP.

There was some issue with ThinkNIC; could it be you have to use Xvesa? Really 
don't remember.

-- 
Z.
--
If all you have is a hammer, everything looks like a nail.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



RE: [Xpert] 8500 DV (was: ATI Radeon 9000)

2002-09-11 Thread Alexander Stohr
Title: RE: [Xpert] 8500 DV (was: ATI Radeon 9000)





 Arkadiusz Miskiewicz [EMAIL PROTECTED] writes:
 
  Unfortunately current radeon drivers does not have PCI ID of
  this card (afaik even in xfree cvs).


 Just tried today cvs version of xfree from HEAD. With overriding
 ChipID 0x4242
 got X running 


Huh? If you are talking about an 8500 DV then 
you should better change headline next time...


 but there is one problem reading/localizing BIOS


 (II) Loading sub module int10
 (II) LoadModule: int10
 (II) Loading /mnt/storage1/misiek/xfree/lib/modules/linux/libint10.a
 (II) Module int10: vendor=The XFree86 Project
  compiled for 4.2.99.1, module version = 1.0.0
  ABI class: XFree86 Video Driver, version 0.6
 (II) RADEON(0): initializing int10
 (WW) RADEON(0): Bad V_BIOS checksum
 (II) RADEON(0): Primary V_BIOS segment is: 0xc000
 (**) RADEON(0): Chipset: ATI Radeon 8500 BB (AGP) (ChipID = 0x4242)
 (--) RADEON(0): Linear framebuffer at 0xe400
 (--) RADEON(0): MMIO registers at 0xed00
 (--) RADEON(0): VideoRAM: 65536 kByte (64-bit DDR SDRAM)
 (II) RADEON(0): Primary Display == Type 1


i have seen something like this in other logs but it was not critical.
Seems the checksum algorithm differs or someone altered the BIOS data
without taking care for adjusting the checksum values once again.


 and second problem with ,,out of scan range'' (my monitor turned screen off).


dont drive your monitor to the max clock if it does behave nice there.


 problaby due to BIOS problem 


Not related at all.


 (II) RADEON(0): I2C EDID Info:
 (II) RADEON(0): Manufacturer: SNY Model: 1870 Serial#: 3255578
 (II) RADEON(0): Year: 2001 Week: 12
 (II) RADEON(0): EDID Version: 1.2
 (II) RADEON(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
 (II) RADEON(0): Sync: Separate Composite SyncOnGreen
 (II) RADEON(0): Max H-Image Size [cm]: horiz.: 33 vert.: 24
[...]
 (II) RADEON(0): Supported Future Video Modes:
 (II) RADEON(0): #0: hsize: 640 vsize 480 refresh: 85 vid: 22833
 (II) RADEON(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
 (II) RADEON(0): #2: hsize: 1024 vsize 768 refresh: 85 vid: 22881
 (II) RADEON(0): #3: hsize: 1152 vsize 864 refresh: 85 vid: 22897
 (II) RADEON(0): #4: hsize: 1280 vsize 1024 refresh: 85 vid: 39297
 (II) RADEON(0): #5: hsize: 1280 vsize 960 refresh: 75 vid: 20353
 (II) RADEON(0): #6: hsize: 1600 vsize 1200 refresh: 75 vid: 20393
 (II) RADEON(0): Supported additional Video Mode:
 (II) RADEON(0): clock: 94.5 MHz Image Size: 312 x 234 mm
 (II) RADEON(0): h_active: 1024 h_sync: 1072 h_sync_end 1168 
 h_blank_end 1376 h_border: 0
 (II) RADEON(0): v_active: 768 v_sync: 769 v_sync_end 772 
 v_blanking: 808 v_border: 0
 (II) RADEON(0): Ranges: V min: 48 V max: 120 Hz, H min: 30 
 H max: 96 kHz, PixClock max 260 MHz
 (II) RADEON(0): Monitor name: CPD-G200P
 (II) RADEON(0): Serial No: 3255578
 (II) RADEON(0): End of DDC Monitor info
 
 (II) RADEON(0): Monitor0: Using hsync range of 30.00-96.00 kHz
 (II) RADEON(0): Monitor0: Using vrefresh range of 48.00-120.00 Hz
 (II) RADEON(0): Clock range: 20.00 to 350.00 MHz
[...]
 (**) RADEON(0): Virtual size is 1600x1024 (pitch 1600)
 (**) RADEON(0): Mode 1600x1024: 191.8 MHz, 91.5 kHz, 85.5 Hz
 (II) RADEON(0): Modeline 1600x1024 191.75 1600 1632 1792 
 2096 1024 1027 1030 1070
 (**) RADEON(0): Default mode 1024x768: 94.5 MHz, 68.7 kHz, 85.0 Hz
 (II) RADEON(0): Modeline 1024x768 94.50 1024 1072 1168 
 1376 768 769 772 808 +hsync +vsync
 (**) RADEON(0): Default mode 800x600: 56.3 MHz, 53.7 kHz, 85.1 Hz
 (II) RADEON(0): Modeline 800x600 56.30 800 832 896 1048 
 600 601 604 631 +hsync +vsync
 (**) RADEON(0): Default mode 640x480: 74.2 MHz, 85.9 kHz, 
 85.1 Hz (D)
 (II) RADEON(0): Modeline 640x480 74.25 640 672 752 864 
 480 480 482 505 doublescan +hsync +vsync


try reducing upper limits of hsync and vsync values in your config file.
try disabling DDC support if you can find something related.


-Alex.





RE: [Xpert]dri

2002-09-11 Thread Alexander Stohr
Title: RE: [Xpert]dri





I dont know about recent improvement to the vodoo series in DRI or XF86.


For a startup its the simplest thing to get the set of XF86 source tarballs,
extract them to something ~/xc and do an 
 echo #define BuildXF86DRM YES ~/xc/config/cf/host.def
followed by a
 cd ~/xc; make World


Installation? Hmm, i never needed that for my purposes. ;-)
Try a make install.


 I have a voodoo3000 card which i see is supported by
 the dri system and i think it is about time i got the
 accelerated graphics working! My question is this...
 do i need to get the latest dri source from cvs, or
 does the latest XFree86-4.2.1 have enough in it that i
 can compile dri support without any additional adons?
 (well, besides libglide3) and if so, what must i
 specify in my host.def?
 
 i noticed in my (partial) compile of XFree86 today
 that i had a few dri_xxx.o files in the lib/modules
 folder. Are these what i think they are? ie. are these
 the accelerated graphics modules for the associated
 cards?
 
 i quess what i am tryign to ask is this... is dri in
 the stable XFree86 release now?
 
 i hope i have made sense... probably haven't
 thanks in advance!
 Sam


good question.


-Alex.





Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread Mark Vojkovich

On 11 Sep 2002, Xavier Bestel wrote:

 Ok, sorry to have wasted bandwidth and brain cells, I'm back to 4.1 and
 it still freezes. I really dunno why it fails now. I tried changing
 kernel versions, even reflashing motherboard bios to all possible
 revisions ... no way, it still freezes.
 I noticed the nvidia uses the same pirq than my network card, but even
 when I remove it (the nvidia), my pc still fails.
 
 It seems really bound to X activity: I can compile kernels or do
 otherwise cpu-intensive tasks for hours without problems, but if I use
 galeon or xine or other X-intensive tasks, it freezes after a while
 (seconds or minutes or more).
 
 Does any of you have experience about such failures ? Can it be
 hardware-related ? BIOS-related ? I didn't change my hardware and it was
 working very well a month ago.
 

   Specific problems I can think that might only affect graphics,
but not compiles or other CPU intensive tasks include:

1) Fastwrites enabled when the chips don't really support them.

2) Mapping registers cached (shouldn't have happened).

3) Bad resource arbitration in the motherboard bios (conflicts, overlaps).

4) Power regulation problems.


Mark.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



[Xpert]Some sugestions please

2002-09-11 Thread Mariusz Gniazdowski

Hi.
I installed RH7.3 without thrid cd, so i did not configure it to use Polish 
language. Now i  set up locale, console font etc, so on console im able to 
use iso8859-2.  I have problem with XFree: i can see latin-2 chars but  i 
cant  enter them.

Things i do:

1. XF86Config-4:
Section InputDevice
Identifier  Keyboard0
Driver  keyboard
Option  AutoRepeat250 30

Option  XkbRules  xfree86
Option  XkbModel  pc105
Option  XkbLayout pl
EndSection

2.  I installed iso8859-2 fonts.


Im curious what can i omit? What else in XFree86 suits for using other than 
iso8859-1 encodings ?

Regards
Mariusz Gniazdowski
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]G550 + G400, overlay problems

2002-09-11 Thread Scott Long

Well, I can't even get the G550 to work alone, much less along with 
another card. I also see this screen distortion in dual-head mode. I 
believe it is due to the Matrox driver using incorrect timings on the 
second head, but I don't have the hours and hours to spend tweaking 
the modelines to try and get it working.

And I still haven't found anyone who can explain to me why DVI output 
works without the HAL module. According to both the XFree86 and Matrox 
documentation, DVI shouldn't work at all without HAL. And when I do 
use HAL, neither the panel nor the CRT gets a good signal.

Basically, if I do what the manual says, nothing works. Only by doing 
what the manual specifically says DOES NOT WORK do I actually get the 
thing to work.

Oh, and in single-head mode, the display (DVI) blanks to black every 
couple of seconds. More often when a lot seems to be changing on the 
screen. I believe this is probably also related to incorrect timings.

And yes, I've tried NoCompositeSync and it makes no difference 
whatsoever.

If anyone out there has the G550 working, driving a DVI panel without 
this annoying blanking, can you please post your modelines to the 
list? I think having the correct modelines could be the ticket to 
getting dual-head to work with the HAL driver.

Thanks,
Scott Long

4) Using the Matrox drivers, both displays turn on but the secondary 
has some serious psychedelic visuals on it and the first has some 
mouse pointer issues.  Personally, I'd rather use the XFree drivers 
if they can be made to work.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



RE: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze - it's something else

2002-09-11 Thread Xavier Bestel

Le mer 11/09/2002 à 21:18, Alexander Stohr a écrit :
 
 He should think about the power supply...

The integrated health status sensors of my motherboard tell me voltages
are Ok ... can I trust them ?

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



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread Xavier Bestel

Le mer 11/09/2002 à 21:30, Mark Vojkovich a écrit :
Specific problems I can think that might only affect graphics,
 but not compiles or other CPU intensive tasks include:
 
 1) Fastwrites enabled when the chips don't really support them.

Nope

 2) Mapping registers cached (shouldn't have happened).
 
 3) Bad resource arbitration in the motherboard bios (conflicts, overlaps).

How do I find that ? Is there some doc somewhere about how to hunt such
conflicts ?

 4) Power regulation problems.

Sensors say it's OK.


Thanks for the tips Mark.

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



[Xpert]Problems with Matrox G450 PCI card

2002-09-11 Thread Kevin Oberman

We have been trying to get a Matrox G450 PCI to work correctly on two
different systems (one of which has not AGP slot and the other where
we wanted to add a second set of displays). No joy!

We see the display sync and the cursor works reasonably well, but
the display is corrupt with odd vertical lines appearing and colors
being mis-mapped such that  a terminal window with a black background
suddenly has a white background (making it tough to read the white
characters). 

It is fairly random, sometimes looking like it is almost right and
sometimes being totally trashed, though the cursor always seems to
work. 

The systems were both running FreeBSD and XFree86 4.2.1.

Any idea what might be going on here?

Thanks!

R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
E-mail: [EMAIL PROTECTED]  Phone: +1 510 486-8634
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread Mark Vojkovich

On 11 Sep 2002, Xavier Bestel wrote:

  3) Bad resource arbitration in the motherboard bios (conflicts, overlaps).
 
 How do I find that ? Is there some doc somewhere about how to hunt such
 conflicts ?
 

   Usually XFree86's verbose output would complain about overlaps.
There's always the possibliltiy of some other broken card in the
system that reports its needs incorrectly (remember the S3 968)
and a correctly operating bios leaving it overlapping something
else.  But I think most of those types of problems would be
well known and already worked around in the kernel, etc...  And
we're really grasping at straws at that point.

   Do you have alot of power consumption in your system?  How
many Watts can the power supply provide?  Can you hear phenomenon
like your fans sounding like their RPMs are dropping when you
do cpu or graphics intensive tasks?  Even if the power supply
itself is OK, it could be a regulation problem on the board.

   Have you tried snipping out the freetype or xtt modules
so that the TrueType font renders don't get used?  There have
been fatal bugs in those in the past.  I think they are all
fixed by now though.


Mark.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread Xavier Bestel

Le mer 11/09/2002 à 22:51, Mark Vojkovich a écrit :
Do you have alot of power consumption in your system?  How
 many Watts can the power supply provide?  Can you hear phenomenon
 like your fans sounding like their RPMs are dropping when you
 do cpu or graphics intensive tasks?  Even if the power supply
 itself is OK, it could be a regulation problem on the board.

I have a 150W PSU (a Wintech), on a dual-pIII 1GHz (with big fans
which sound a bit like a 747 taking-off), 2 HDDs, an internal Zip, a
DVD, a CDRW, an IEEE1394 card, an eth card, a sound card, and obviously
a R128 AGP and a TNT2 PCI. I have to admit I really don't know how much
power all this may drain.
And yes, I can tell the CPUs load just by listening to the fans.


Have you tried snipping out the freetype or xtt modules
 so that the TrueType font renders don't get used?  There have
 been fatal bugs in those in the past.  I think they are all
 fixed by now though.

I tried that, without luck. GTK+2 still uses truetype fonts, but as it's
client-space rendering I don't think it matters.

Xav

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



Re: [Xpert]X process redirection...

2002-09-11 Thread Xavier Bestel

Le mer 11/09/2002 à 20:50, [EMAIL PROTECTED] a écrit :
 Fabrizio,
 
 Current GTK 2 CVS has code for screen migration (even between X servers)
 A person at Sun (whose name I always forget) did the screen migration stuff
 this spring, I then tested it worked even between servers, and Owen Taylor
 has since done some work to try to shake out more of the resulting problems.
 So making GTK/gnome apps migrate is within reach.

Nice ! That means Xinerama-like without the disadvantages (e.g. with
DRI, etc.)


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



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread Xavier Bestel

Le mer 11/09/2002 à 23:41, Xavier Bestel a écrit :
 Le mer 11/09/2002 à 22:51, Mark Vojkovich a écrit :
 Do you have alot of power consumption in your system?  How
  many Watts can the power supply provide?  Can you hear phenomenon
  like your fans sounding like their RPMs are dropping when you
  do cpu or graphics intensive tasks?  Even if the power supply
  itself is OK, it could be a regulation problem on the board.
 
 I have a 150W PSU (a Wintech), on a dual-pIII 1GHz (with big fans
 which sound a bit like a 747 taking-off), 2 HDDs, an internal Zip, a
 DVD, a CDRW, an IEEE1394 card, an eth card, a sound card, and obviously
 a R128 AGP and a TNT2 PCI. I have to admit I really don't know how much
 power all this may drain.
 And yes, I can tell the CPUs load just by listening to the fans.

Err ... I mistyped, it's a 250W PSU. But after surfing a bit, it seems
it's way out of specs. So well ... I'll have to go and buy a bigger one,
something like a 400W I think.

Thanks a lot for the tip.


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



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze- it's something else

2002-09-11 Thread Mark Vojkovich

On 11 Sep 2002, Xavier Bestel wrote:

 Le mer 11/09/2002 à 22:51, Mark Vojkovich a écrit :
 Do you have alot of power consumption in your system?  How
  many Watts can the power supply provide?  Can you hear phenomenon
  like your fans sounding like their RPMs are dropping when you
  do cpu or graphics intensive tasks?  Even if the power supply
  itself is OK, it could be a regulation problem on the board.
 
 I have a 150W PSU (a Wintech), on a dual-pIII 1GHz (with big fans
 which sound a bit like a 747 taking-off), 2 HDDs, an internal Zip, a
 DVD, a CDRW, an IEEE1394 card, an eth card, a sound card, and obviously
 a R128 AGP and a TNT2 PCI. I have to admit I really don't know how much
 power all this may drain.
 And yes, I can tell the CPUs load just by listening to the fans.

   I'm thinking 150 Watts really isn't enough for that.  My main
machine has a similar setup (dual PIIIs and two video cards) and
I have a 235 Watt power supply which I'd consider marginal.  I have
an HP dual P4 machine here with a 465 Watt power supply in it.

   If your fans are speeding up when the CPU is going full bore
(some inteligent cooling system) that is good.  If they are slowing
down, that means they're starved for power.  That's usually not a
good sign.  I have seen fan slowdowns in other machines and I've 
generally considered that as a tip-off that there are power problems.

Mark.
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Some sugestions please

2002-09-11 Thread Mariusz Gniazdowski

Dnia ro 11. wrzesie 2002 23:33, Juliusz Chroboczek napisa:
 LC_ALL=pl_PL xterm 

Sorry did not work..

Programs seems to have right locale (they display messages in proper lang 
etc).  

It looks like keymap or smthg is wrong. When i run xev, and pres ALT:

KeyRelease event, serial 27, synthetic NO, window 0x141,
root 0x3a, subw 0x0, time 990954769, (666,490), root:(670,510),
state 0x8, keycode 113 (keysym 0xffea, Alt_R), same_screen YES,
XLookupString gives 0 characters:  

It should be Meta or smthg right?  I use RALT to enter iso8859-2 chars..


-- 
Regards Mariusz Gniazdowski
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]Re: X 4.2.x + TNT + ATI All-In-Wonder 128 = hard freeze - it's something else

2002-09-11 Thread Markus Gutschke

The motherboard sensors tend to be pretty slow and only give you an average 
value. Unfortunately, long before you see hardware failing due to low voltage, 
you'll run into problems with transients. Short of hooking up some expensive 
test equipment (a oscilloscope would work), there isn't much you can do to test 
for these -- and power supply manufacturers don't typically tell you all the 
specs that you need to know. As a rule of thumb, if you buy a power supply that 
has generous extra ampere ratings on all of the different voltage lines (e.g. 
3.3V, 5V, 12V, and the negative ones), chances are you'll get something that 
will be able to avoid transients, but even then there are no real guarantees. 
For a system with one or two fast CPUs (1GHz and above) and a modern AGP 
graphics card, you will probably want to get a PSU that is rated in excess of 
300W (450W or so is probably a good bet). If you can buy a reputable brand-name 
product, you might want to consider that option -- and even after all this, you 
might still have bad luck and end up with a PSU that just doesn't work with your 
system.


Markus

P.S.: BTW, if your graphics card has a connector that allows you to supply 
additional power directly to it rather than going through the AGP bus, then make 
sure you take advantage of this. Modern graphics card put quite some load on the 
system and not all motherboards can supply this much current over the AGP bus 
itself.

Xavier Bestel wrote:
 Le mer 11/09/2002 à 21:18, Alexander Stohr a écrit :
 
He should think about the power supply...
 
 
 The integrated health status sensors of my motherboard tell me voltages
 are Ok ... can I trust them ?
 
 ___
 Xpert mailing list
 [EMAIL PROTECTED]
 http://XFree86.Org/mailman/listinfo/xpert


-- 
Markus Gutschke
3637 Fillmore Street #106
San Francisco, CA 94123-1600
+1-415-567-8449
[EMAIL PROTECTED]

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



[Xpert]Trident Cyberblade RGB overlays

2002-09-11 Thread Alastair Robinson

Hi Everyone,

I've just bought a VIA EPIA-5000 motherboard, which has an integrated Trident 
Blade 3D.

I've been playing around with the Xv extension recently, most notably to add 
support for it to the XMAME arcade machine emulator - for this purpose RGB 
overlays are more suited than YUV.

The integrated Blade 3D, according to xvinfo, supports RV15 and RV16, which 
are supposedly 15- and 16-bit RGB - however, my tests suggest that these 
formats are not RGB - they're not YUV either, in fact they seem to be a 
bizarre mixture of the two, with the so-called green channel adjusting grey, 
and the other two interacting weirdly with it.

Anyway, does anyone have any hardware information for this chipset, so I can 
have a go at fixing the problem?

All the best,
-- 
Alastair M. Robinson
Email: [EMAIL PROTECTED]

What's the difference between a bad archer and a constipated owl?
One shoots but can't hit...
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert



Re: [Xpert]ATI Radeon 9000

2002-09-11 Thread hy0

Hi,
The patch for Radoen 9000, M9 and Radeon 9700 2D support has been submitted
and will be in XFree CVS tree in the near future.
9000 and 8500 don't share the same IDs, that's for sure.
Meanwhile specifying ChipID in the config file with a 8500 or 7500 ID is a
correct solution for getting 9000 or M9 to work with the existing X4.2xx
Radoen dirver (2D part only, note this won't work with 9700).
If you specify ChipID with a 8500 ID (0x4242 for example), it will only work
with the single head config.
If you want both heads to work correctly with a dual-head/Xinerama setup,
use a 7500 (0x5157) or a VE ID (0x5159 for example). Although 9000 uses the
same 3D core as used in 8500, its 2D features (dual-head, tvout, etc)
actually follow 7500.
When you use a 7500 or VE ID, make sure to disable DRI. Although the 2D part
of radeon DRI support is likely to work fine with radeon.o kernel driver on
a 9000 (this is because the 2D DRI support only uses DMA to send 2D
commands, doesn't even use the microcode for 2D commands), any ogl app (like
ogl screen savers) will lock whole thing up if DRI is enabled.
The failure experienced by Arkadiusz in
http://www.xfree86.org/pipermail/xpert/2002-September/020561.html is
probably caused by the bug with DDA rountines in the old X4.20 driver, this
has been discussed before and has been fixed in XFree CVS tree.

Hope this helps

Hui


 I recently recieved a Radeon 9000pro mac edition and hacked it to work
 by just adding the PCI id as stated in other posts (but in the driver this
 time), this cards ID is 0x4966.  Is it true that there are 9000's with
 8500 ID's?


 ani


 On Wed, 11 Sep 2002, Alexander Stohr wrote:

  Hello,
 
 What 0x4243 is supposed to mean?
   
It's a pci id of AIW Radeon 8500 DV.
   So another unsupported one.
 
  No, according to the PCI ID database on www.yourvote.com
  0x4243 the piggy back firewire port of the 8500 DV.
  This is indeed not a grafics chip at all.
  Who the heck has come up with that bogus ID?
 
  In the PCI device listing you will clearly find
  the correct ID of this ATI Radeon 9000 card: 0x4966
 
  Charl is finally most right with his proposal:
ChipId 0x4966
 
  (i dont use that because when i am developing
  i am always having a full X11 tree handy and
  then i just add the IDs directly into my code,
  a few seconds recompile of the ddx driver module
  and its done...)
 
  you had two IDs in your specific case, thats why:
  only primary function 0 does identify the chip,
  any further device functions only do have different IDs
  if they do provide something different with the same silicon,
  a thing that is often seen on intel's bus bridges.
 
Perhaps it has not made into linux kernel yet.
   kernel? support in kernel is required for DRI.
   I'm trying to get XFree working even without DRI.
 
  The write meant something different - the coding of DRI
  partially is kernel based and uses the constant defines
  from linux kernel header files (which do originate from
  the yourvote.com site). As the Radeon 9000 is a pretty
  new board the Linux kernel is possibly just updating this,
  but the DRI project hasnt identified this addition.
  Thats a development thing users should not care to much.
 
  For users there is just the method of browsing their pci
  configuration and add the yet not known compatible devices
  to their config file by the ChipID statement.
 
Also try this:
Option ChipId 0x4243
   XFree drivers do not support 0x4243. It will not work.
 
  that boy was hoaxing with his suggestion or using the FAQ template?
 
If still does not work try ati.2 drivers from http://gatos.sf.net/
gatos drivers also don't support 0x4243 (don't support my radeon,
too)
 
  must be the same boy as above
 
   btw. how PCI IDs are managed? Vendor (like ATI) gets some ID space
   (as in with MAC on network cards) and does whathever it wants in
   that assigned space? Or maybe vendor is required to register
   each product in some global database?
 
  There is an organsiation called PCI Special Interests Group
(www.pcisig.com)
  that does work on specs. Its a big business club. And it registers the
  misc companys with a vendor ID. The device IDs are in the duty of the
  respective vendors. Each of these IDs is 16 bits wide.
  If you use up 50 device IDs a year, you will have mor than 1000 years
  of time until you have to register for a secondary vendor ID.
 
   ps. response from ati support sucks, automated message ;/
 
  hmm. that means customer support got your mail. ;-)
  anyways X11-DRI drivers are supported by their respective vendors.
 
  -Alex.
 

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


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



[Xpert]Horizontal sync problem with S3 Savaga4 KM133

2002-09-11 Thread John Zoetebier

Hi,

After upgrading from AMD 1.1 Ghz to AMD Athlon 2000+ (1.67 Ghz) my
monitor had horizontal sync problem.
There are horizontal distorted lines flashing over the screen.
I found a workaroud for this problem by setting the FSB speed on the
mother board to 100Mhz in stead of 133Mhz.
The downside of this solution is that my processor now runs on only 1250
Mhz (clock multiplier 12.5 x FSB speed)
Does anybody know how I can get rid of the horizontal sync problem while
keeping the FSB speed on 133 Mhz ?
I use:
- Xfree86 V4.2.1
- SuSE Linux 8.0 (Linux 2.4.18)
- Dell 1500FP flat panel monitor
- AM75-EC motherboard with VIA KM133  chipset
- Onboard display controller S3 Savage4 2D/3D

-- 
John Zoetebier



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