[Xpert]How to stop a laptop going into standby when i close the lid?
Hello, not sure if this got though, i could not find it on the mailing list log. Has anyone any thoughts on how to get this working please? JG Original Message Subject: How to stop a laptop going into standby when i close the lid? Date: Mon, 13 May 2002 17:11:59 +0900 From: J. Grant [EMAIL PROTECTED] To: xpert [EMAIL PROTECTED] Hi, Could someone tell me how can I stop a laptop going into standby when i close the lid? I checked apm but could not find this option that triggers the whole process, could someone point me to the file that contains this ON_LID_CLOSE=/usr/bin/apm suspend now or similar command please? I can not find it in the bios. Another OS can disable it... JG I have tired the following server flags section Option NoPM boolean Monitor section Option DPMS off and Section Device Option power_saver All with no luck, it still 'Saves to RAM' In the bios i had it on custom with each one disabled, now i have it just on all disabled instead of custom. occasionall it does not go off, which is odd, but every time while i have been testing today it has. I dont want to cut off the switch and then leave the screen light on, i would like to just close the lid for carrying around the office, but it goes into suspend each time tho.. --- Laptop Adagio (38W2) Same as DELL Inspiron 7500 Chipset: ATI Rage 128 Mobility LF (AGP) (ChipID = 0x4c46) ATI Mobility 128 AGP 2X (English) ASIC Mobility 128 ASIC ID 4c46 Bios 004.039.064.023 Date 31/8/2000 Tuner Type: Philips FI1236 MK1 NTSC M/C Tuner Type: BT819 Linear framebuffer at 0xf800 MMIO registers at 0xf410 VideoRAM: 16384 kByte (128-bit SDR SGRAM 1:1) SDRAM Using flat panel for display Panel size: 1400x1050 Panel ID: IBM ITSX93 Panel Type: Color, Single, TFT Panel Interface: LVDS PLL parameters: rf=2700 rd=60 min=12500 max=25000; xclk=10500 Resolutions supported 1600 x 1200 but not all visible. 1400 x 1050 full 1280 x 1024 1024 x 768 all 32 or 16 bpp or 256 no 24bit mode XFree86 Version 4.1.0 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: 2 June 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.8-5mdkenterprise i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Mon May 13 16:47:52 2002 (==) 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 2 (**) |--Screen screen1 (0) (**) | |--Monitor Generic|Generic Monitor, 1600x1200 @ 70 Hz (**) | |--Device ATI Rage 128 Mobility (**) |--Input Device mouse2 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 250 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout gb (**) XKB: layout: gb (==) Keyboard: CustomKeycode disabled (**) FontPath set to unix/:-1 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (**) Option NoPM 1 (--) using VT number 7 (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, 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, 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 8086,7190 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:04:0: chip 104c,ac51 card , rev 00 class 06,07,00 hdr 82 (II) PCI: 00:04:1: chip 104c,ac51 card , rev 00 class 06,07,00 hdr 82 (II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,80,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 03 class 06,80,00 hdr 00 (II) PCI: 00:08:0: chip 125d,1978 card 14c0,0011 rev 10 class 04,01,00 hdr
Re: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86for redhat Linux 7.1
On Tue, 14 May 2002, dmitri kerievsky wrote: tyring to use xf86config to configure the installation in the final step of the installation instructions http://www.xfree86.org/4.2.0/Install3.html#3 for a ATI Radeon 7000 Video w/ 64MB running Linux redhat 7.1 any idea if this card is supported by xfree ver. 4.2 ? thanks, Looking at the code, the Radeon 7000 was supported in 4.2. However ATI have a habit of changing the PCI chip IDs; if your chip is one we haven't heard of you may need to add the line ChipId 0x5159 to the Devices section of your config file, to force the driver to treat your chip as a 7000. If you have to do this, please send us the output of lspci, so that we can add support for your chip. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]how to make Xmodmap starting programms by keycode
How do i insert at a specific keycode that after preesing this key a shell script should be started ??? -- _ Robert Wörle Linux | Embedded Device Symplon AG ...touch the internet phone: +49 89 552 999 35 fax: +49 89 552 999 10 email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] web: www.symplon.com http://www.symplon.com/ _ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]how to make Xmodmap starting programms by keycode
On Wed, 15 May 2002, Robert Wörle wrote: How do i insert at a specific keycode that after preesing this key a shell script should be started ??? I would't do it with Xmodmap. As I understand it, the natural way of doing that in X is to run a program which gets the keys first (think of it as having an invisible window covering the whole screen, in front of all other windows), processes the keys it is interested in and allows the rest to go back to be processed by some other window. It may be worth using some sort of X event for your special key presses, so that you don't have to listen for and pass on key presses that don't interest you. It may be that such a program already exists. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Backspace
Hello all, Weather it is possible to sent the BackSpace to application ? Suppose already some char is displayed in SCR. But before displaying my next char the already existing char should be deleted and display the current char in that position. I try to send the Backspace / DEL char (8 / 127) from XkbTranslateKeySym() (XKBBind.c). but application ( Kword etc...) display it as space. How to do it? ( For Multiple keystroke to single Glyph ) TIA, Bharathi S -- --==| Bharathi S | BSB-364 DONLab | IIT-Madras |==-- The virtue-killer may be saved Not benefit-killer wo is damned. *In Tirukkural of Holy Tamil poet Tiruvalluvar. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1
Thanks for responding. I have followed the steps - downloaded the 4.2 binaries and run sh Xinstall.sh and xf86config. xf86config asks a series of questions and at one point lists a database of cards. The ATI Radeon is not in the list even though documentation says it is supported. Is this a different issue than the PCI chip ID mentioned below? Do I need to add ChipID 0x5159 to the Device section of which config file? Or do I need to contact ATI to find out which chip they use? thx -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dr Andrew C Aitchison Sent: Wednesday, May 15, 2002 2:23 AM To: [EMAIL PROTECTED] Subject: Re: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1 On Tue, 14 May 2002, dmitri kerievsky wrote: tyring to use xf86config to configure the installation in the final step of the installation instructions http://www.xfree86.org/4.2.0/Install3.html#3 for a ATI Radeon 7000 Video w/ 64MB running Linux redhat 7.1 any idea if this card is supported by xfree ver. 4.2 ? thanks, Looking at the code, the Radeon 7000 was supported in 4.2. However ATI have a habit of changing the PCI chip IDs; if your chip is one we haven't heard of you may need to add the line ChipId 0x5159 to the Devices section of your config file, to force the driver to treat your chip as a 7000. If you have to do this, please send us the output of lspci, so that we can add support for your chip. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Pointers to the AccessX programming API?
I know, wrong forum :) XFree86 implements XKB which is newer and better than AccessX anyway ... but I want my program to work well on old and outdated equipment that only supports AccessX, such as the Sun equipment my university uses ;) (Lots of SunRay1 terminals served by three big Sun machines, calling themselves something like sun4u sparc SUNW,Ultra-250) So, can anyone (from Sun or DEC^WCompaq^WHPAQ) point me to some docs on it? -Peter ...they may well attempt to treat the gangrene they got when blowing off their foot by amputating their leg with a shotgun! ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86for redhat Linux 7.1
On Wed, 15 May 2002, dmitri kerievsky wrote: Thanks for responding. I have followed the steps - downloaded the 4.2 binaries and run sh Xinstall.sh and xf86config. xf86config asks a series of questions and at one point lists a database of cards. The ATI Radeon is not in the list even though documentation says it is supported. Is this IIRC xf86config is obsolete in 4.2, and should have been removed. Try configuring with either X -configure or xf86cfg instead. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert][CVS] make install: compile fails at lib/fontconfig/src/fccharset.c
Hello, I have updated my CVS tree and after a successful build, make install stops at a compile failure in lib/fontconfig/src/fccharset.c. Oh, by the way is there a way to track recent changes via cvs? Regards, Axel Here is the complete error output..: gcc -c -O2 -fno-strength-reduce -ansi -pedantic -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wredundant-decls -Wnested-externs -Wundef -I-I../../../exports/include/freetype2 -I.. -I../../.. -I../../../exports/include -Dlinux -D__i386__ -D_POSIX_C_SOURCE=199309L -D_POSIX_SOURCE -D_XOPEN_SOURCE -D_BSD_SOURCE -D_SVID_SOURCE -D_GNU_SOURCE -DFUNCPROTO=15 -DNARROWPROTO -DXTHREADS -D_REENTRANT -DXUSE_MTSAFE_API -DFC_FALLBACK_FONTS='/usr/X11R6/lib/X11/fonts/Type1' -fPIC fccharset.c In file included from fccharset.c:801: ../fontconfig/fcfreetype.h:30: parse error before FcFreeTypeCharIndex ../fontconfig/fcfreetype.h:30: parse error before face ../fontconfig/fcfreetype.h:30: warning: type defaults tont' in declaration of cFreeTypeCharIndex' ../fontconfig/fcfreetype.h:30: warning: function declaration isn't a prototype ../fontconfig/fcfreetype.h:30: ISO C forbids data definition with no type or storage class ../fontconfig/fcfreetype.h:33: parse error before face ../fontconfig/fcfreetype.h:33: warning: function declaration isn't a prototype fccharset.c:807:5: warning: FREETYPE_MAJOR is not defined fccharset.c:810:6: warning: FREETYPE_MAJOR is not defined fccharset.c:831:2: warning: #warning is a GCC extension fccharset.c:831:2: warning: #warning No FT_Get_Next_Char fccharset.c:845: parse error before FT_Encoding fccharset.c:845: warning: no semicolon at end of struct or union fccharset.c:848: parse error before '}' token fccharset.c:848: warning: type defaults to nt' in declaration of cFontDecode' fccharset.c:848: ISO C forbids data definition with no type or storage class fccharset.c:1283: parse error before fcFontDecoders fccharset.c:1283: warning: type defaults to nt' in declaration of cFontDecoders' fccharset.c:1284: warning: braces around scalar initializer fccharset.c:1284: warning: (near initialization for cFontDecoders[0]') fccharset.c:1284: t_encoding_unicode' undeclared here (not in a function) fccharset.c:1284: initializer element is not constant fccharset.c:1284: (near initialization for cFontDecoders[0]') fccharset.c:1284: warning: excess elements in scalar initializer fccharset.c:1284: warning: (near initialization for cFontDecoders[0]') fccharset.c:1284: warning: excess elements in scalar initializer fccharset.c:1284: warning: (near initialization for cFontDecoders[0]') fccharset.c:1284: initializer element is not constant fccharset.c:1284: (near initialization for cFontDecoders[0]') fccharset.c:1285: warning: braces around scalar initializer fccharset.c:1285: warning: (near initialization for cFontDecoders[1]') fccharset.c:1285: t_encoding_symbol' undeclared here (not in a function) fccharset.c:1285: initializer element is not constant fccharset.c:1285: (near initialization for cFontDecoders[1]') fccharset.c:1285: warning: excess elements in scalar initializer fccharset.c:1285: warning: (near initialization for cFontDecoders[1]') fccharset.c:1285: warning: excess elements in scalar initializer fccharset.c:1285: warning: (near initialization for cFontDecoders[1]') fccharset.c:1285: initializer element is not constant fccharset.c:1285: (near initialization for cFontDecoders[1]') fccharset.c:1286: warning: braces around scalar initializer fccharset.c:1286: warning: (near initialization for cFontDecoders[2]') fccharset.c:1286: t_encoding_apple_roman' undeclared here (not in a function) fccharset.c:1286: initializer element is not constant fccharset.c:1286: (near initialization for cFontDecoders[2]') fccharset.c:1286: warning: excess elements in scalar initializer fccharset.c:1286: warning: (near initialization for cFontDecoders[2]') fccharset.c:1286: warning: excess elements in scalar initializer fccharset.c:1286: warning: (near initialization for cFontDecoders[2]') fccharset.c:1286: initializer element is not constant fccharset.c:1286: (near initialization for cFontDecoders[2]') fccharset.c:1287: ISO C forbids data definition with no type or storage class fccharset.c:1292: parse error before FcFreeTypeMapChar fccharset.c:1293: warning: return type defaults to nt' fccharset.c:1293: warning: no previous prototype for cFreeTypeMapChar' fccharset.c: In function cFreeTypeMapChar': fccharset.c:1306: T_ULong' undeclared (first use in this function) fccharset.c:1306: (Each undeclared identifier is reported only once fccharset.c:1306: for each function it appears in.) fccharset.c:1306: parse error before map fccharset.c:1315: parse error before map fccharset.c:1306: warning: statement with no effect fccharset.c:1315: warning: statement with no effect fccharset.c: At top level: fccharset.c:1327: parse error before FcFreeTypeCharIndex fccharset.c:1327: parse error
Re: [Xpert][CVS] make install: compile fails at lib/fontconfig/src/fccharset.c
at a compile failure in lib/fontconfig/src/fccharset.c. -I-I../../../exports/include/freetype2 -I.. -I../../.. ^^ For some reason, that Makefile contains FREETYPE2INCDIR=$(TOP_X_INCLUDES)/freetype2 FREETYPE2INCLUDES = -I$(FREETYPE2INCDIR) where FREETYPE2INCDIR itself is expanded to -Isomething Dropping the -I on the FREETYPE2INCLUDES solved the problem for me - the same breakage exists also in xc/lib/Xft . Did we both do the cvs update incorrectly, or is this broken in cvs ? Martin -- Dr. Martin Kroeker, daveg GmbH Darmstadt CAD/CAM/CAQ [EMAIL PROTECTED] Precision Powered by Penguins ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]i810 chipset
Hi, I've just recompiled the kernel of my Linux system, and X does not work anymore. But some details more: 1. my system runs a RedHat7.1 with kernel release 2.4.2 and XFree86 version 4.0.3 without problems. 2. I compiled the 2.4.9 kernel with RTAI-2.4.6a patch Now the system works, except for graphic interface. In what follows I added the full ouput of the X server, when invoked by startx from runlevel 3. One thing more: I looked on intel site, as regarding with my chipset. I tried without success what they suggest to do with the two rpm files that can be downloaded ( i810gtt-0.2-4.src.rpm and xfcom_i810-1.2-3.i386.rpm). ### #X SERVER OUTPUT### ### XFree86 Version 4.0.3 / X Window System (protocol Version 11, revision 0, vendor release 6400) Release Date: 16 March 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) Operating System: Linux 2.2.17-8smp i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Wed May 15 14:37:46 2002 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (??) unknown. (==) ServerLayout Anaconda Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Intel 815 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc102 (**) XKB: model: pc102 (**) Option XkbLayout it (**) XKB: layout: it (**) 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) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.3 XFree86 XInput driver : 0.1 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.0.3, 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.0.3, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x281e, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,1130 card 8086,4541 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 8086,1132 card 8086,4541 rev 02 class 03,00,00 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 01 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,2440 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,244b card 8086,4541 rev 01 class 01,01,80 hdr 00 (II) PCI: 00:1f:2: chip 8086,2442 card 8086,4541 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1f:3: chip 8086,2443 card 8086,4541 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:4: chip 8086,2444 card 8086,4541 rev 01 class 0c,03,00 hdr 00 (II) PCI: 01:07:0: chip 1274,1371 card 8086,4541 rev 08 class 04,01,00 hdr 00 (II) PCI: 01:0b:0: chip 109e,036e card bd11,1200 rev 11 class 04,00,00 hdr 80 (II) PCI: 01:0b:1: chip 109e,0878 card bd11,1200 rev 11 class 04,80,00 hdr 80 (II) PCI: 01:0c:0: chip 10b7,9055 card 10b7,9055 rev 30 class 02,00,00 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.0.3, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.3 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x00 (VGA_EN is cleared) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:30:0), (0,1,1), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 1 I/O range: [0] -1 0xd000 - 0xd0ff (0x100) IX[B] [1] -1 0xd400 - 0xd4ff (0x100) IX[B] [2] -1 0xd800 - 0xd8ff (0x100) IX[B] [3] -1 0xdc00 - 0xdcff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0xff80 - 0xff8f (0x10) MX[B] (II) Bus 1 prefetchable
Re: [Xpert][CVS] make install: compile fails at lib/fontconfig/src/fccharset.c
On Wed, 15 May 2002 [EMAIL PROTECTED] wrote: at a compile failure in lib/fontconfig/src/fccharset.c. -I-I../../../exports/include/freetype2 -I.. -I../../.. ^^ For some reason, that Makefile contains FREETYPE2INCDIR=$(TOP_X_INCLUDES)/freetype2 I've just committed a fix to change this to FREETYPE2INCDIR=$(BUILDINCDIR) in X11.tmpl. There was also another occurrence of the same problem in the setting of FONTCONFIGINCDIR. FREETYPE2INCLUDES = -I$(FREETYPE2INCDIR) where FREETYPE2INCDIR itself is expanded to -Isomething Dropping the -I on the FREETYPE2INCLUDES solved the problem for me - the same breakage exists also in xc/lib/Xft . Did we both do the cvs update incorrectly, or is this broken in cvs ? b). But not any more. Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][CVS] make install: compile fails at lib/fontconfig/src/fccharset.c
Axel H. Siebenwirth [EMAIL PROTECTED] writes: Hello, I have updated my CVS tree and after a successful build, make install stops at a compile failure in lib/fontconfig/src/fccharset.c. Oh, by the way is there a way to track recent changes via cvs? Sounds like the typical slackware freetype1-headers-installed-in-the-wrong-place bug. Regards, Owen From: Owen Taylor [EMAIL PROTECTED] Subject: Re: Problem compiling pango 1.0.1 To: Damon Chong [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Date: 06 May 2002 14:44:36 -0400 Damon Chong [EMAIL PROTECTED] writes: Hi I'm a newbie with Gnome and C/C++ so forgive me if i'm wasting your time. I got a bunch of error messages (see attached) while trying to compile pango. Any advise appreciated. Thank you! ;-) This (I believe) is a symptom of a Slackware bug. Slackware has the freetype2 header in: [includedir]/freetype2/freetype/freetype.h Which is good, but the freetype1 header is in: [includedir]/freetype/freetype.h Which means that when a program includes freetype/freetype.h with a compile line that includes -I [includedir]/freetype2, it is indeterminate which one it gets, and depends on what other -I flags are on the compile line. The *only* correct fix is for the freetype1 header files to be moved in the package into a freetype1 sub-directory, and for the few (if any packages) that compile against freetype1 fixed to find them. I don't know the appropriate contact address for Slackware or I'd be mailing them to ask them to fix it, since this is a very, very common problem people are having. The easiest thing for you to do is to simply remove the freetype1 package, since its very unlikely that you'll need to compile anything against it. Regards, Owen ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][CVS] make install: compile fails at lib/fontconfig/src/fccharset.c
On Wed, 15 May 2002, Marc Aurele La France wrote: On Wed, 15 May 2002 [EMAIL PROTECTED] wrote: at a compile failure in lib/fontconfig/src/fccharset.c. -I-I../../../exports/include/freetype2 -I.. -I../../.. ^^ For some reason, that Makefile contains FREETYPE2INCDIR=$(TOP_X_INCLUDES)/freetype2 I've just committed a fix to change this to FREETYPE2INCDIR=$(BUILDINCDIR) Ooops, I should have said FREETYPE2INCDIR=$(BUILDINCDIR)/freetype2 Marc. +--+---+ | Marc Aurele La France | work: 1-780-492-9310 | | Computing and Network Services | fax:1-780-492-1729 | | 352 General Services Building | email: [EMAIL PROTECTED] | | University of Alberta +---+ | Edmonton, Alberta | | | T6G 2H1 | Standard disclaimers apply| | CANADA | | +--+---+ XFree86 Core Team member. ATI driver and X server internals. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Where Should I Be Sending Patches?
On Tue, 14 May 2002, Owen Taylor wrote: Be patient. We're all busy with other things, and there are plenty of patches still waiting in the queue. Please don't resend anything. Can I suggest, as a long term goal, having a publically viewable bug tracker / patch queue? At least from my point of view, the current system isn't working very well. If I find a bug in XFree86 (say, http://bugzilla.gnome.org/show_bug.cgi?id=81783, which turned up 5 minutes ago :-), it's frequently not clear how to proceed. Yes, I can send mail to [EMAIL PROTECTED] or [EMAIL PROTECTED]; b bug report. But in either case it feel like a complete shot in the dark. - I can't check on the status of my bug-report/patch. - I can't give someone else an URL to go to check on the the status. - I can't meaningfully give updates ... sending mail to [EMAIL PROTECTED] saying you know the patch I sent 2 months ago. Forget it, it turns out to have been faulty hardware at least seems like it won't work very well. - There isn't any reliable way of telling if/when my bug has been applied. - If the person dealing with the bug report / patch wants to get further information, they have communicate with me privately, and I understand very well that something like bugzilla is considerable amount of sysadmin work to set up and maintain that would take away from someone's hacking. And there simply may not be the resources currently. But for GTK+ and GNOME, we find it an extremely valuable tool to have this stuff public ... not a panacea ... I still get plenty of people annoyed at me for slow response to GTK+ patches, but at least they see a milestone for the bug, and know it hasn't been lost. I agree completely. We (Red Hat) receive a lot of bug reports against XFree86, many of which we just do not have the manpower to fix/look into, other distributions no doubt have the same problem. I think a lot of these problems end up falling between the cracks. What makes things a bit worse, is that a bug reported to a distro vendor that ends up getting fixed by that vendor, generally gets fixed in that one distribution at that point in time, and doesn't necessarily propagate to other vendors, or back to XFree86.org in a timely manner, or at all. Without pointing any fingers at anyone, some vendors are great with submitting patches back to XFree86 while others don't bother it seems IMHO. This puts more work on each distro vendor, to harvest patches from the other vendors packages also. When submitting a patch upstream, you sometimes do get immediate feedback on a particular patch, and sometimes do not. I never quite know if a patch I've submitted for example is applied, if the problem was fixed in a different way, or is still in someone's queue. I fully realize that everyone receiving the patches have full time jobs themselves, and don't have time to respond to the number of patches right away or apply them, since this is often the case for myself as well. The problem is though, that bugfixing/patching seems to not scale well at all. I've submitted 40-45 patches about a week ago or so, and I've had some feedback from a few core team members about a few of the patches, which was greatly appreciated. Many of the other patches I presume are in a main queue, or have been taken and put in personal patch queues of a given developer to look at in the future when they're working on that area of code and/or have time, etc. At least that is probably what I would do if I was receiving the patches this way. When a patch does eventually get applied though, one has to hope to catch it in a changelog message. I read changelogs and am on the CVS commits mailing list, however I'm sure many others are not, and would just appreciate knowing in a simple manner that their patch was applied or not, and if rejected, perhaps a reason. In the past I've experimented with submitting patches a bit, and I've found that submitting patches in an ongoing fashion as they are made, tends to not get them applied sooner unless it is a rather important issue with a straightforward fix. For our 7.3 development cycle I decided to submit the whole storm of patches all at once to save myself some work as I figured the bulk of the patches I was submitting, most likely would only be applied to the head of CVS, and probably only just before 4.3.0 was released. Submitting them in one shot was much less work than submitting them one at a time, possibly having to bugfix the patch and resubmit a few times, etc. when there was good chances they'd queue up until 4.3.0 was near. On the #xfree86 channel on irc.openprojects.net, I often point people to the [EMAIL PROTECTED] bug report list, or the current XFree86 web based bug submitter CGI. People who have sent a few reports there in the past have come back to me saying Why should I bother reporting there? I never get a response back anyway. I generally tell them that XFree86.org
[Xpert]Re: Where Should I Be Sending Patches?
On Tue, 14 May 2002, Dr Andrew C Aitchison wrote: -- From xc/programs/Xserver/hw/xfree86/doc/README: 3.4 Xpert If instead you are the lone developer who is improving XFree86 on an ad hoc basis for your particular environment (I want to get my mouse or video card to work), and need a specific question asked then you should go over to our Xpert list where such questions are raised and answered by our technical development staff. Remember you do not have to be a member to write fixes to our code base and if your changes are discrete and self-contained the volume of developer mail may just be too noisy. Once your work is finished (coded, debugged and documented) please send your fix to [EMAIL PROTECTED]. This will ensure that they are included in future releases. And thanks! You make this truly an Open group. To be truely open, it needs to be viewable/queryable by members of the community, and trackable. -- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, XFree86 maintainer Ontario, Canada, P6C 5B3 Red Hat Inc. http://www.redhat.com ftp://people.redhat.com/mharris ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]RE: Where Should I Be Sending Patches?
On Tue, 14 May 2002, Dr Andrew C Aitchison wrote: There are about a handful of people who see these patches, I'm not sure that any of them are paid to work on XFree86, so you are asking a volounteer developer to spend time understanding someone else's patch (including the issues involved) and then do the boring administrative stuff of integrating it. Indeed, and it is understandable that volunteer work can only accomplish so much in a given amount of time. I think the problem is not that patches/fixes don't get integrated instantly, but rather that there is no two way communication mechanism present. An automated system can help with this. I think code cutting is fun, but I wouldn't enjoy integrating patches. I also agree with that. When a bug report comes into bugzilla, once I am looking into the issue, I have the bug number on hand, and have it open in a web browser. Once the fix is applied - either included with the bug report, or whipped up or from elsewhere, I can then make a comment in the report which takes virtually zero time/effort fixed in 4.2.0-9 in rawhide, please reopen if the problem persists or somesuch, and click CLOSED-RAWHIDE or some other resolution that is fitting. The end user receives an email on this, as do any other people who have added themselves to the bug CC list, informing them the issue is resolved. It takes me no more time to do this, than it would to read an email, fix a bug, add a changelog entry. I think the gains it brings far outweigh any /perceived/ disadvantages by far. If I were running a large project on a volunteer basis, I would definitely use bugzilla to manage it, as it saves time, rather than requiring more time. If all projects using bugzilla didn't result in more being done in less time, by those same volunteers they likely wouldn't use it at all IMHO if it just created more work. -- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, XFree86 maintainer Ontario, Canada, P6C 5B3 Red Hat Inc. http://www.redhat.com ftp://people.redhat.com/mharris ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]RE: Where Should I Be Sending Patches?
On 14 May 2002, Michel Dänzer wrote: This is all very well, but i sent patches to [EMAIL PROTECTED] nearly 3 weeks ago and i've had nothing back apart from an automatic response! does *ANYONE* read it? There is another list for registered developers to submit patches, and the turn around can be as bad as that, although I would usually expect to see my changes in CVS within 2 weeks. You're lucky. Now that Red Hat 7.3 ships 4.2, I get private mail about a problem in the r128 and radeon drivers for which I submitted a fix (#5199) on March 9th, without any response yet... Bummer, I didn't see that fix, and so didn't apply it to our package. I've just applied it to my development build however. If this was on a public bugzilla tracker on XFree86.org for example, there's more likelyhood of more widespread testing/feedback occuring, as well as those interested in the specific bug being able to opt-in on receiving updates to that bug report, including good/bad feedback from those who have tested it and confirmed it to work, or found it to not work. Distribution maintainers querying for bug reports, could find the issue, the patch, the collaborative bug tracking details from people who have tried the fix, and can communicate among those affected, and other developers working on the issue more readily. As it is now, to find it, you have to be an XFree86.org member, and read every incoming email, hoping not to misplace one, and/or exercise your MUA search feature to hopefully find fixes submitted by others. No multi-way communication mechanism is really present or easily possible. There are about a handful of people who see these patches, I'm not sure that any of them are paid to work on XFree86, so you are asking a volounteer developer to spend time understanding someone else's patch (including the issues involved) and then do the boring administrative stuff of integrating it. I think code cutting is fun, but I wouldn't enjoy integrating patches. There are certainly more interesting things, but I'd be willing to do a share if I get a chance. As would I as time permits. I think the number of I would too's present would be large enough to make it quite beneficial to the project overall. -- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, XFree86 maintainer Ontario, Canada, P6C 5B3 Red Hat Inc. http://www.redhat.com ftp://people.redhat.com/mharris ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]Re: Where Should I Be Sending Patches?
I though i should point out that you already have a volunteer to set up a bug database: Kurt Wall ( see http://www.xfree86.org/pipermail/xpert/2002-May/017211.html ). Yours, Rob Taylor -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Mike A. Harris Sent: Wednesday, May 15, 2002 5:16 PM To: [EMAIL PROTECTED] Cc: Owen Taylor; [EMAIL PROTECTED] Subject: [Xpert]Re: Where Should I Be Sending Patches? On Tue, 14 May 2002, Owen Taylor wrote: Be patient. We're all busy with other things, and there are plenty of patches still waiting in the queue. Please don't resend anything. Can I suggest, as a long term goal, having a publically viewable bug tracker / patch queue? At least from my point of view, the current system isn't working very well. If I find a bug in XFree86 (say, http://bugzilla.gnome.org/show_bug.cgi?id=81783, which turned up 5 minutes ago :-), it's frequently not clear how to proceed. Yes, I can send mail to [EMAIL PROTECTED] or [EMAIL PROTECTED]; b bug report. But in either case it feel like a complete shot in the dark. - I can't check on the status of my bug-report/patch. - I can't give someone else an URL to go to check on the the status. - I can't meaningfully give updates ... sending mail to [EMAIL PROTECTED] saying you know the patch I sent 2 months ago. Forget it, it turns out to have been faulty hardware at least seems like it won't work very well. - There isn't any reliable way of telling if/when my bug has been applied. - If the person dealing with the bug report / patch wants to get further information, they have communicate with me privately, and I understand very well that something like bugzilla is considerable amount of sysadmin work to set up and maintain that would take away from someone's hacking. And there simply may not be the resources currently. But for GTK+ and GNOME, we find it an extremely valuable tool to have this stuff public ... not a panacea ... I still get plenty of people annoyed at me for slow response to GTK+ patches, but at least they see a milestone for the bug, and know it hasn't been lost. I agree completely. We (Red Hat) receive a lot of bug reports against XFree86, many of which we just do not have the manpower to fix/look into, other distributions no doubt have the same problem. I think a lot of these problems end up falling between the cracks. What makes things a bit worse, is that a bug reported to a distro vendor that ends up getting fixed by that vendor, generally gets fixed in that one distribution at that point in time, and doesn't necessarily propagate to other vendors, or back to XFree86.org in a timely manner, or at all. Without pointing any fingers at anyone, some vendors are great with submitting patches back to XFree86 while others don't bother it seems IMHO. This puts more work on each distro vendor, to harvest patches from the other vendors packages also. When submitting a patch upstream, you sometimes do get immediate feedback on a particular patch, and sometimes do not. I never quite know if a patch I've submitted for example is applied, if the problem was fixed in a different way, or is still in someone's queue. I fully realize that everyone receiving the patches have full time jobs themselves, and don't have time to respond to the number of patches right away or apply them, since this is often the case for myself as well. The problem is though, that bugfixing/patching seems to not scale well at all. I've submitted 40-45 patches about a week ago or so, and I've had some feedback from a few core team members about a few of the patches, which was greatly appreciated. Many of the other patches I presume are in a main queue, or have been taken and put in personal patch queues of a given developer to look at in the future when they're working on that area of code and/or have time, etc. At least that is probably what I would do if I was receiving the patches this way. When a patch does eventually get applied though, one has to hope to catch it in a changelog message. I read changelogs and am on the CVS commits mailing list, however I'm sure many others are not, and would just appreciate knowing in a simple manner that their patch was applied or not, and if rejected, perhaps a reason. In the past I've experimented with submitting patches a bit, and I've found that submitting patches in an ongoing fashion as they are made, tends to not get them applied sooner unless it is a rather important issue with a straightforward fix. For our 7.3 development cycle I decided to submit the whole storm of patches all at once to save myself some work as I figured the bulk of the patches I was submitting, most likely would only be applied to the head of CVS, and probably only just before 4.3.0 was released. Submitting them in one shot was much less work than submitting
[Xpert]Re: i810 chipset
On Wed, 15 May 2002, Bertoldi Andrea wrote: I've just recompiled the kernel of my Linux system, and X does not work anymore. But some details more: 1. my system runs a RedHat7.1 with kernel release 2.4.2 and XFree86 version 4.0.3 without problems. Those are both ancient releases. You should update your kernel and XFree86 to the currently released erratum packages for Red Hat Linux 7.1 2. I compiled the 2.4.9 kernel with RTAI-2.4.6a patch Now the system works, except for graphic interface. In what follows I added the full ouput of the X server, when invoked by startx from runlevel 3. Keep in mind, recompiling your kernel, especially with external patches can cause problems. Make sure if you experience problems that they are not due to your customizations. One thing more: I looked on intel site, as regarding with my chipset. I tried without success what they suggest to do with the two rpm files that can be downloaded ( i810gtt-0.2-4.src.rpm and xfcom_i810-1.2-3.i386.rpm). That stuff is totally ancient and should not be used. (WW) AGPIOC_ACQUIRE failed (Device or resource busy) (EE) GARTInit: AGPIOC_INFO failed (Invalid argument) Looks like you don't have AGPgart support compiled. Symbol VBEInit from module /usr/X11R6/lib/modules/drivers/i810_drv.o is unresolved! Symbol vbeDoEDID from module /usr/X11R6/lib/modules/drivers/i810_drv.o is unresolved! Ancient bug, long since fixed in newer releases. (0): [drm] drmSetBusid failed (5, PCI:0:2:0) (EE) I810(0): DRIScreenInit failed DRI can't start if AGPgart isn't loaded. If I'm not mistaken, the Intel chipsets require AGP support wether or not you actually use DRI. Someone will correct me if I'm wrong. You can try to disable DRI as well and test to see if it works or not. Hope this helps. TTYL -- Mike A. Harris Shipping/mailing address: OS Systems Engineer 190 Pittsburgh Ave., Sault Ste. Marie, XFree86 maintainer Ontario, Canada, P6C 5B3 Red Hat Inc. http://www.redhat.com ftp://people.redhat.com/mharris ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert][CVS] make install: compile fails at lib/fontconfig/src/fccharset.c
Axel == Axel H Siebenwirth [EMAIL PROTECTED] writes: Axel Oh, by the way is there a way to track recent changes via cvs? Subscribe to the [EMAIL PROTECTED] list. You may also want to mirror the whole repository via cvsup and check out from there. Instructions are linked from http://xfree86.org/. I find that it works well for me, even over dialup. You can even have email from the commit list trigger a cvsup run, much as kernel.org triggers rsync runs on its mirrors. -JimC ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1
when running X -configure or xf8cfg there an error message appears -Fatal server error -Module load failure any ideas how to proceed? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dr Andrew C Aitchison Sent: Wednesday, May 15, 2002 9:55 AM To: [EMAIL PROTECTED] Subject: RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1 On Wed, 15 May 2002, dmitri kerievsky wrote: Thanks for responding. I have followed the steps - downloaded the 4.2 binaries and run sh Xinstall.sh and xf86config. xf86config asks a series of questions and at one point lists a database of cards. The ATI Radeon is not in the list even though documentation says it is supported. Is this IIRC xf86config is obsolete in 4.2, and should have been removed. Try configuring with either X -configure or xf86cfg instead. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]ATI Radeon VE ( Dell OEM version )
Hi, I have a Dell OEM ATI Radeon VE with a DVI interface on it. There is _not_ a vga interface on it. Only the DVI. I have a converter (that came with the card) that goes from the one DVI connector to two (2) VGA connectors. I would like to connect a monitor to each of these VGA connectors, and run Xinerama to span an X Desktop across both of them . But before I do that, I was wondering...is it possible to configure X in this way? Currently, I can only get the first monitor (the first interface) to work. Is there something I can do make the X talk to BOTH monitors? I'm running: Linux: Slackware 8.0 Kernel: 2.4.18 XFree86:4.2 If there currently isn't a way of doing this, is there a plan to add this support to X in the future? - Thanks, Todd ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Where Should I Be Sending Patches?
There are four ingredients for a bug tracking system to succeed, as I see it: 1. Interest and cooperation from the developer community itself 2. The machine resources/network to support the system (available; I know we have a machine here we could use, if no other, so it is a certainty) 3. Good installation and customization of the system to provide good catagorization of bugs (two people have volunteered with this part of the problem, Kurt Wall, and Jeff Waugh (via private mail to me)) 4. Someone (or set of people) to perform bug triage, entering existing bugs initially, and once established, assign initial catagories, mark duplicates, produce statistics as releases near, and eventually cull the database of long fixed bugs. 1) is obviously essential. And 4) is needed to keep the quality up, so that the developers don't go nuts (for example, what happened to the nautilus folks during Gnome 2 development). Many of the major projects have serious resources assigned to the triage/catagorization and maintenance of their bug tracking systems. So 4) is also key (2, and 3 can be considered solved problems, IMHO). 3) is a significant amount of work initially, and only a small amount ongoing: if things aren't set up well (and tuned), then bug reports are hard to deal with and don't go in the right directions. I gather some previous attempts were not well done. I know that Jamey Hicks here spent a number of days working out this catagorization stuff on the handhelds.org bugzilla, so this is not just a one day and your done sort of job. As Mike points out, establishing a transparent system would allow more people to actually help on resolving problems. It is also a way for people to get their feet wet on the project (as they do on some of the other major projects) by taking bugs, working on fixes, and posting patches. Some people even appear to enjoy this sort of work. With the current opaque system, there is no way to enlist people into helping with bug fixing. Some of the most valuable people in some other projects wander around fixing lots, and lots, and lots of bugs. This would help the scaling issue, I think, which XFree86 faces. So the outstanding questions are: 1) are the people who do XFree86 developement interested/willing to work with such a tool? 2) who is willing, if anyone, to become bugmeister and properly deal with the database? This is a significant amount of work; one might argue that the commercial Linux vendors are those with the most to gain by helping out here. I think answers to both in the affirmative are necessary before one goes any further, and unless the answers our yes, we live with the current system until there are credible answers. If this is done, it had better be done well: I gather that previous attempts have failed for various reasons, and I think good answers to all four questions are essential. - Jim -- Jim Gettys Cambridge Research Laboratory HP Labs, Hewlett-Packard Company [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]xdm setup
I have installed XFree86 4.2 and KDE3 on a FreeBSD box running 2 PII 450mz processors. The problem: xdm only seems to work on ttyv8. logout only brings up another login screen and does not return to the terminal. Logging in as the superuser brings up KDE3 and the only way out is by hitting F1. If I log in as any user, I get the xconsole and another set-up screen. How can I set up xdm to come up on another terminal and so it will close an return to the terminal when I logout? And how to set up xdm to switch to other windows managers to try them out? I have searched the net and the man pages and nothing seems to work. :(( Phil ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Where Should I Be Sending Patches?
Hi all, I am not a XFree developer but I'd like to show a user viewpoint: X is faced as something strange, misterious and not transparent. Ex: Check out the rage 128 driver status (the driver of my complaints): Know limitations: none Pardon me , is there an errata for XF 4.2 ? More ? Some time ago I tried in every possible place to obtain a list of Xv capable XFree drivers...Mission Impossible (support is either accelerated or non accelerated), and no one seems to know that. Check out mozilla as an example: I sent dozens of bug reports, and allways was notified by email about their status, and the developers sometimes asked for other trials. Even workarounds get posted there. And well... #xfree86 is silent as a cave...and btw, Mr Mike Harris was one of the few people that was so kind to answer some questions. It really helped. Thanks a lot ! Why do #kde, #mozilla, #xine and others have lot's of non developers hanging and helping people while #xfree86 does not ? Doesn't it mean something ? Now, since X is at least as importante as KDE or Gnome, is X less suported by the distros then those projects ? Keep up the good work (and build a bugzilla :) ) Gustavo ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Where do you send specs to upgrade the monitor database.
There used to be something called the monitor database. Where do you send the specs of your monitor that is not recognized by XF86cfg? Thank You. -- Paul Elliott 1(512)837-1096 [EMAIL PROTECTED]PMB 181, 11900 Metric Blvd Suite J http://www.io.com/~pelliott/pme/ Austin TX 78758-3117 msg06272/pgp0.pgp Description: PGP signature
RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1
Quoting dmitri kerievsky [EMAIL PROTECTED]: when running X -configure or xf8cfg there an error message appears -Fatal server error -Module load failure any ideas how to proceed? You may have something misconfigured. Try running # xf86cfg -nomodules or even better # xf86cfg -nomodules -textmode so that it will not run X -configure to generate the initial config file. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dr Andrew C Aitchison Sent: Wednesday, May 15, 2002 9:55 AM To: [EMAIL PROTECTED] Subject: RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1 On Wed, 15 May 2002, dmitri kerievsky wrote: Thanks for responding. I have followed the steps - downloaded the 4.2 binaries and run sh Xinstall.sh and xf86config. xf86config asks a series of questions and at one point lists a database of cards. The ATI Radeon is not in the list even though documentation says it is supported. Is this IIRC xf86config is obsolete in 4.2, and should have been removed. Try configuring with either X -configure or xf86cfg instead. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna Paulo ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1
when running # xf86cfg -nomodules -textmode I see a graphical setup which leads to a step where there are a list of video cars, but the ATI Radeon is not there, even though documentation says it is supported. any ideas what to do? thanks -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] Sent: Wednesday, May 15, 2002 8:13 PM To: [EMAIL PROTECTED]; dmitri kerievsky Subject: RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1 Quoting dmitri kerievsky [EMAIL PROTECTED]: when running X -configure or xf8cfg there an error message appears -Fatal server error -Module load failure any ideas how to proceed? You may have something misconfigured. Try running # xf86cfg -nomodules or even better # xf86cfg -nomodules -textmode so that it will not run X -configure to generate the initial config file. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dr Andrew C Aitchison Sent: Wednesday, May 15, 2002 9:55 AM To: [EMAIL PROTECTED] Subject: RE: [Xpert]is ATI Radeon 7000 Video w/ 64MB supported with xfree86 for redhat Linux 7.1 On Wed, 15 May 2002, dmitri kerievsky wrote: Thanks for responding. I have followed the steps - downloaded the 4.2 binaries and run sh Xinstall.sh and xf86config. xf86config asks a series of questions and at one point lists a database of cards. The ATI Radeon is not in the list even though documentation says it is supported. Is this IIRC xf86config is obsolete in 4.2, and should have been removed. Try configuring with either X -configure or xf86cfg instead. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna Paulo ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Where do you send specs to upgrade the monitor database.
On Wed, 15 May 2002, Paul Elliott wrote: Date: Wed, 15 May 2002 17:44:08 -0500 From: Paul Elliott [EMAIL PROTECTED] To: Xpert Xfree86 mailing list [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: multipart/signed; micalg=pgp-sha1; protocol=application/pgp-signature; boundary=Dxnq1zWXvFF0Q93v Subject: Where do you send specs to upgrade the monitor database. There used to be something called the monitor database. Where do you send the specs of your monitor that is not recognized by XF86cfg? Thank You. I maintain the MonitorsDB database. The entries are added from Microsoft Windows .INF files. The best way to have them added, is to file a bug report in Red Hat bugzilla against XFree86 or Xconfigurator and attach the .INF file for your specific monitor, or a manufacturer's line of monitors. I generally let them save up for a bit, then hunt bugzilla for them all and gang apply them all at once. I'd also like to make a note that anyone else is free to take this Monitor database and use it under GPL license or XFree86 license. The XFree86 team can include it in XFree86 directly as well if that is useful. I'd even volunteer to maintain it there as well. Hope this helps. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon VE ( Dell OEM version )
This feature will soon be in CVS. I have a test build for X4.2, let me know if you want to give it a try. Hi, I have a Dell OEM ATI Radeon VE with a DVI interface on it. There is _not_ a vga interface on it. Only the DVI. I have a converter (that came with the card) that goes from the one DVI connector to two (2) VGA connectors. I would like to connect a monitor to each of these VGA connectors, and run Xinerama to span an X Desktop across both of them . But before I do that, I was wondering...is it possible to configure X in this way? Currently, I can only get the first monitor (the first interface) to work. Is there something I can do make the X talk to BOTH monitors? I'm running: Linux: Slackware 8.0 Kernel: 2.4.18 XFree86: 4.2 If there currently isn't a way of doing this, is there a plan to add this support to X in the future? - Thanks, Todd ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
