[Xpert]my Kmail is acting up
is there an known bug in Kmail that i havent noticed or is it just me having this problem ? cause i am sick off not getting mail from the mail server whitout having to shut down Kmail first then restarting it :/// ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Total frustration with XFree86 4.1.0!
Help, all X users, For the last two weeks, I've been trying to get XFree86 4.1.0 to work properly with hardware I have that worked properly with XFree86 3.3.6. Here is the list of hardware*: Flamingo PCI SVGA graphics card based on the Cirrus Logic CL 5434-8 chipset. Compaq 471 SVGA monitor HorizSync 31.5-38 VertRefresh 50(?)-90 (question mark added) NEC Multisync 3V monitor HorizSync 31.0-50.0 VertRefresh 55-90 Both monitors worked properly when I used XFree86 3.3.6 on Slackware 7.1 using the XF86Config file that I've attached. The modeline that worked with _both_ monitors is listed below: # 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync Modeline 1024x76844.9 1024 1048 1208 1264 768 776 784 817 Interlace I recently upgraded to Slackware 8.0, which uses XFree86 4.1.0. The modeline shown above was inserted in to the XF86Config-4 line as shown in the file I've attached. Rather than working, the following message is generated in XFree86.0.log file (also attached): (II) CIRRUS(0): Not using mode 1024x768 (bad mode clock/interlace/doublescan) I've tried other modelines for 1024x768 as shown in the XF86Config-4 file. Either they don't work with either monitor or eventually cause the NEC Multisync monitor to shut off (this might be a problem with the monitor, TBD). I've read the XF86Config and Timing HOWTOs and I've used some of the modeline generation tools available on the Internet. Notably, none of them help in generating a modeline with the interlace flag. Whenever I've set up a 1024x768 modeline without interlacing, it won't sync with the Compaq monitor. The modeline also causes the NEC monitor to eventually shut itself off. If I set up a 1024x768 modeline (or any other) with the interlace flag included, a bad mode clock/interlace/doublescan error message is generated for that modeline and it is ignored. I've run out of ideas on how to solve this problem; short of uninstalling 4.1.0 and reinstalling 3.3.6 That is something I really don't what other than as a last resort. Any help would be greatly appreciated, especially in understanding how to properly generate modelines which call for interlace. Mac * I've also been working with a TV57 PCI board, based on the Trident TGUI 9680, which also works with XFree 3.3.6, but utterly fails with 4.1.0. Briefly, every 8 horizontal pixels are repeated twice on a line. That is another story, though. # File generated by xf86config. # # Copyright (c) 1995 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. # ** # ** # 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/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled #
Re: [Xpert]Re: Screen blanking/DPMS with Sun Ultra1
(More comments below -- FEM)
On Mon, 3 Dec 2001, Moritz Bunkus wrote:
Hello everyone.
I have a lot of Sun Ultra1 boxes with Sun monitors. Until recently they
ran under Solaris. With this setup they monitors went into some sort of
power saving mode after some time of inactivity.
All those boxes now run Woody with XFree 4.1.0.1. Unfortunately
either the graphics hardware (the suncg6 driver is used) or the monitor
don't support DPMS (option DPMS is given in the monitor section): the
logfile says
(WW) SUNCG6(0): Option DPMS is not used
(WW) SUNCG6(0): Option StandByTime is not used
(WW) SUNCG6(0): Option SuspendTime is not used
(WW) SUNCG6(0): Option OffTime is not used
Now the boxes all have their monitors on all the time which is
definitely not what I want. Is there a way to use power saving with
this setup? Or at least some sort of screen blanking and/or a
screensaver?
Moritz,
I don't know if you ever got this resolved or not, nor do I know
if you have been following the follow-on discussions or not (helpful
to me, not so directly to the CG6 case.)
In any case, here is an idea which I have no way of testing, but
which parallels David Miller's suggestion regarding the Creator graphics
card.
The kernel code seems to blank/unblank a display device connected to
a CG6 frame buffer seems to use the mask CG6_THC_MISC_VIDEO in the module
[cgsixfb.c at cg6_blank] thus:
tmp = sbus_readl(fb-s.cg6.thc-thc_misc);
tmp = ~CG6_THC_MISC_VIDEO;
wbus_writel(tmp, fb-s.cg6.thc-thc_misc);
This suggests that changing the XF86 cg6 driver module ---
cg6_driver.c --- as follows should get you screen blanking at least:
The current CG6SaveScreen procedure is an empty procedure returning
TRUE. Something along the following lines might do what you want--
static Bool
CG6SaveScreen(ScreenPtr pScreen, int mode) {
ScrnInfoPtr pScrn = xf86Screens[pScreen-myNum]; /* Like elsewhere*/
Cg6Ptr pCg6;
unsigned int tmp;
pCg6 = GET_CG6_FROM_SCRN(pScrn);
tmp = pCg6 - thc - thc_misc;
switch(mode) {
case SCREEN_SAVER_ON:
case SCREEN_SAVER_CYCLE:
tmp = ~CG6_THC_MISC_VIDEO;
break;
case SCREEN_SAVER_OFF:
case SCREEN_SAVER_FORCER:
tmp |= CG6_THC_MISC_VIDEO;
break;
default: return FALSE;
}
pCg6 - thc - thc_misc = tmp;
return TRUE;
}
If you try that and it works, there are some other THC_MISC masks
which might get the display device to turn off. As I mentioned a couple
weeks ago, something along these lines will turn it off: Solaris
knows how to do it.
Sorry to be so long-winded. Hope this is of some use to you (or that
someone who actually knows will correct it into something useful).
Regards,
Ferris
--
Ferris McCormick (P44646, MI) [EMAIL PROTECTED]
Phone: (703) 392-0303
Fax: (703) 392-0401
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Stupid defines?
Several X headers (Xlib.h!) contain the following defines: #define Boolint #define Status int Does anybody see any side effects if we change this to a typedef? This would avoid unpleasant surprises for programmers. Egbert. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: SiS630 - the neverending story
Hi I thought I'd give it a try and help you out, and mine has a LVDS bridge too Rune Petersen Date: Mon, 17 Dec 2001 06:58:01 +0100 From: Thomas Winischhofer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [Xpert]Re: SiS630 - the neverending story Now that it's Monday and you all read list mail again: I fixed the sisfb driver for use with LVDS video (LCD) bridges including the CHROMTEL 7005 TV converter. A lot of laptops using the SiS630 do not use the SiS301 but this one instead. The driver has only one problem: It doesn't know about timings, refresh rates and other data specific for various LCD panels and TV connectors. Instead, the current code contains empty tables for this. I inserted data read out from the BIOS to make it run on my machine. This is, of course, no solution. (I have only one machine with one 1024x768 LCD panel, so I can't ever find out all combinations for other, larger or smaller panels.) I will release a (quite huge) patch on the kernel list within the next few days where I will also change the driver to use the BIOS data (like the X driver does). Otherwise it will never work with bidges other than the SiS301. By the way: I had to implement about 200 changes into the code because somebody tried to implement support for SiS301B and 302 bridges, and broke LVDS instead. This code that this somebody wrote could by no means ever have worked on _any_ machine with a bridge other than SiS301 because of major programming glitches (using pointers and arrays doesn't seem to be that simple :) ). Have patience, Thomas PS: In the meantime I kindly ask you to test the driver published yesterday (available on my homepage, link below, follow link Linux on Gericom... and scroll down). Please check the log for what video bridge the driver detects and report your results. I am waiting impatiently. On my machine (SiS630 rev 31, LVDS+CHROMTEL bridge) the driver works perfectly, as long as I keep the TurboQueue disabled. I used it the last two days (day = 18 hours) and stress-tested it. Absolutely no problems here. -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED] *** http://www.webit.com/tw XFree86.0.log Description: Binary data
Re: [Xpert]Stupid defines?
Around 17 o'clock on Dec 17, Egbert Eich wrote: Several X headers (Xlib.h!) contain the following defines: #define Boolint #define Status int Does anybody see any side effects if we change this to a typedef? This would avoid unpleasant surprises for programmers. You can't change Xlib.h -- it's part of the Xlib specification. Switching from #define to typedef will mean the existing workarounds for this particular namespace polution will fail. Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Plane masking with Xlib??
Manipulating the plane mask on truecolor displays typically has little use these days: it is really a holdover hack from the days of pseudocolor. If you want to take two images and composite them, you really want to use the Render extension these days, at least if you are using XFree86. - Jim -- Jim Gettys Cambridge Research Laboratory Compaq Computer Corporation [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]VMWare and 4.1.0.1 failing
I'm trying to run Linux under VMWare with the vmware driver distributed as part of X instead of the one provided by VMWare directly, and a Debian dexconf-managed server configuration. I'm not having luck; the server fails with mfbQueryBestSize unresolved and failure to set up a write combiner range. Can anyone point to an error in my configuration or suggest a point for research? A google search shows that others have simply stepped back to VMWare's own release of the vmware driver on encountering the mfbQueryBestSize. The output, as well as my X configuration... bmcgroar@bmcgroar-vmlinux:~$ cat /var/log/XFree86.0.log This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.1.0.1 / X Window System (protocol Version 11, revision 0, vendor release 6510) Release Date: xx August 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.13 i686 [ELF] Module Loader present (==) Log file: /var/log/XFree86.0.log, Time: Mon Dec 17 12:03:56 2001 (==) Using config file: /etc/X11/XF86Config-4 Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) ServerLayout Default Layout (**) |--Screen Default Screen (0) (**) | |--Monitor Generic Monitor (**) | |--Device Generic Video Card (**) |--Input Device Generic Keyboard (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc101 (**) XKB: model: pc101 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) |--Input Device Configured Mouse (**) |--Input Device Generic Mouse (WW) The directory /usr/lib/X11/fonts/cyrillic does not exist. Entry deleted from font path. (**) FontPath set to unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi (==) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (--) using VT number 7 (WW) Cannot open APM (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.4 XFree86 XInput driver : 0.2 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.2 (II) Loader running on linux (II) LoadModule: bitmap (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.2 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7192 card , rev 01 class 06,00,00 hdr 00 (II) PCI: 00:07:0: chip 8086,7110 card , rev 08 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 08 class 06,80,00 hdr 80 (II) PCI: 00:07:4: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:07:5: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:07:6: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:07:7: chip , card , rev 00 class 00,00,00 hdr 00 (II) PCI: 00:0f:0: chip 15ad,0405 card , rev 00 class 03,00,00 hdr 00 (II) PCI: 00:10:0: chip 104b,1040 card , rev 01 class 01,00,00 hdr 00 (II) PCI: 00:11:0: chip 1022,2000 card , rev 10 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.1.0.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.4 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0
[Xpert]Abridged: Total frustration with XFree86 4.1.0!
(NOTE: Attached files excluded awaiting moderator approval, thanks to automated message filtering due to message size! :-\ Please read this abriged version until approval of full-featured submission.) Help, all X users, For the last two weeks, I've been trying to get XFree86 4.1.0 to work properly with hardware I have that worked properly with XFree86 3.3.6. Here is the list of hardware*: Flamingo PCI SVGA graphics card based on the Cirrus Logic CL 5434-8 chipset. Compaq 471 SVGA monitor HorizSync 31.5-38 VertRefresh 50(?)-90 (question mark added) NEC Multisync 3V monitor HorizSync 31.0-50.0 VertRefresh 55-90 Both monitors worked properly when I used XFree86 3.3.6 on Slackware 7.1 using the XF86Config file that I've [NOT] attached. The modeline that worked with _both_ monitors is listed below: # 1024x768 @ 87 Hz interlaced, 35.5 kHz hsync Modeline 1024x76844.9 1024 1048 1208 1264 768 776 784 817 Interlace I recently upgraded to Slackware 8.0, which uses XFree86 4.1.0. The modeline shown above was inserted in to the XF86Config-4 line as shown in the file I've [NOT] attached. Rather than working, the following message is generated in XFree86.0.log file (also [NOT] attached): (II) CIRRUS(0): Not using mode 1024x768 (bad mode clock/interlace/doublescan) I've tried other modelines for 1024x768 as shown in the XF86Config-4 file. Either they don't work with either monitor or eventually cause the NEC Multisync monitor to shut off (this might be a problem with the monitor, TBD). I've read the XF86Config and Timing HOWTOs and I've used some of the modeline generation tools available on the Internet. Notably, none of them help in generating a modeline with the interlace flag. Whenever I've set up a 1024x768 modeline without interlacing, it won't sync with the Compaq monitor. The modeline also causes the NEC monitor to eventually shut itself off. If I set up a 1024x768 modeline (or any other) with the interlace flag included, a bad mode clock/interlace/doublescan error message is generated for that modeline and it is ignored. I've run out of ideas on how to solve this problem; short of uninstalling 4.1.0 and reinstalling 3.3.6 That is something I really don't what other than as a last resort. Any help would be greatly appreciated, especially in understanding how to properly generate modelines which call for interlace. Mac * I've also been working with a TV57 PCI board, based on the Trident TGUI 9680, which also works with XFree 3.3.6, but utterly fails with 4.1.0. Briefly, every 8 horizontal pixels are repeated twice on a line. That is another story, though. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Abridged: Total frustration with XFree86 4.1.0!
On Mon, 2001-12-17 at 21:33, Mac Cody wrote: I've read the XF86Config and Timing HOWTOs and I've used some of the modeline generation tools available on the Internet. Notably, none of them help in generating a modeline with the interlace flag. Whenever I've set up a 1024x768 modeline without interlacing, it won't sync with the Compaq monitor. The modeline also causes the NEC monitor to eventually shut itself off. If I set up a 1024x768 modeline (or any other) with the interlace flag included, a bad mode clock/interlace/doublescan error message is generated for that modeline and it is ignored. That probably means that the driver doesn't support interlaced modes yet. I imagine it would be fairly easy to add that, but someone has to do it... -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Abridged: Total frustration with XFree86 4.1.0!
Michel Dänzer wrote: That probably means that the driver doesn't support interlaced modes yet. I imagine it would be fairly easy to add that, but someone has to do it... Interesting. :-\ I would have thought that interlace support would be in place since XFree86 is at version 4.1.0 already and support was there in XFree86 3.3.6. Anywhere I could find out whether that is the case or not (short of investigating the sources)? If interlace support is missing, I guess I'll have to fall back to XFree 3.3.6 for now [sigh!]. thanks, Mac ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Abridged: Total frustration with XFree86 4.1.0!
On Mon, 17 Dec 2001, Mac Cody wrote: Interesting. :-\ I would have thought that interlace support would be in place since XFree86 is at version 4.1.0 already and support was there in XFree86 3.3.6. Anywhere I could find out whether that is the case or not (short of investigating the sources)? If interlace support is missing, I guess I'll have to fall back to XFree 3.3.6 for now [sigh!]. Well, XFree86 underwent some serious reworking with the debut of the 4.x line - moving away from monolithic X servers, and moving towards modules for everything, with one smaller base server. Not a lot of attention had initially been paid to moving the old-style 3.x drivers for many old boards (pre-ViRGE S3 boards, older Cirrus and Trident boards had also fallen victim to this), as much of the redesign was intended to allow support for more-advanced features like the XVideo and DRI subsystems. Only recently have those really old drivers been ported forward to the new modular architecture. So you may need to stay with 3.3.x for now, or if you're up to it, try hacking in interlaced-mode support. That's about all you can do, until someone eventually gets the drivers for the older boards fully ported up. Derrik Pates | Sysadmin, Douglas School |#linuxOS on EFnet [EMAIL PROTECTED] | District (dsdk12.net)|#linuxOS on OPN ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Abridged: Total frustration with XFree86 4.1.0!
Derrik Pates wrote: On Mon, 17 Dec 2001, Mac Cody wrote: Interesting. :-\ I would have thought that interlace support would be in place since XFree86 is at version 4.1.0 already and support was there in XFree86 3.3.6. Anywhere I could find out whether that is the case or not (short of investigating the sources)? If interlace support is missing, I guess I'll have to fall back to XFree 3.3.6 for now [sigh!]. Well, XFree86 underwent some serious reworking with the debut of the 4.x line - moving away from monolithic X servers, and moving towards modules for everything, with one smaller base server. Not a lot of attention had initially been paid to moving the old-style 3.x drivers for many old boards (pre-ViRGE S3 boards, older Cirrus and Trident boards had also fallen victim to this), as much of the redesign was intended to allow support for more-advanced features like the XVideo and DRI subsystems. Only recently have those really old drivers been ported forward to the new modular architecture. Yeah. I can understand and appreciate that. Not being a contributor to the XFree86 development effort myself, I can only imagine the level of effort required to support all of the many video cards (both old and new) that are out there. So you may need to stay with 3.3.x for now, or if you're up to it, try hacking in interlaced-mode support. That's about all you can do, until someone eventually gets the drivers for the older boards fully ported up. I'm afraid that is what I may have to do. In fact I'm already preparing to do so (pulling the necessary .tgz files off the Slackware 7.1 CDROM). Tis a pity. XFree86 4.1.0 appears to be faster on my cards than 3.3.6. Mac ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]XF86Config-4 Problems
I have just upgraded a Debian box so that I could install Xfree 4.1.99-2 and run a Radeon card for a customer. I ran XFree86 -configure to configure x and it seems to detect the video card and every thing but when I go to use that created file to start X I get an error saying that the monitor is not detected. I have tried this with 2 monitor and the same problem arises. I have looked at the file created by XFree86 -configure and it looks incomplete. Can someone tell me what setting I should have for XF86Config-4 for a typical monitor? I have tried several things to no avail. regards, -- Mark Lane Hard Data Ltd. mailto:[EMAIL PROTECTED] Telephone: 01-780-456-9771 FAX: 01-780-456-9772 11060 - 166 Avenue Edmonton, AB, Canada T5X 1Y3 http://www.harddata.com/ -- Ask me about our Dual Processor Athlon DDR RAM Systems! -- --Or the New DDR Alpha Systems -- BEGIN:VCARD VERSION:2.1 N:Lane;Mark FN:Mark Lane ORG:Hard Data Ltd. TITLE:Sales TEL;WORK;BUSINESS:780-456-9771 TEL;WORK;VOICE:780-456-9771 TEL;WORK;FAX:780-456-9772 ADR;WORK:;;11060 - 166 Avenue;Edmonton;AB;T5X1Y3;Canada LABEL;WORK;ENCODING=QUOTED-PRINTABLE:11060-166 Avenue=0D=0AEdmonton, AB T5X1Y3=0D=0ACanada URL;WORK:http://www.harddata.com EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20010222T231737Z END:VCARD
[Xpert]Disabling Build-In Extensions
Hi, I'm trying to run OpenOffice 641, but I've found that it crashes when run locally. In particular, when selecting any menu other than Help or Window, it immediately dies. If run remotely, this never happens. Since I've heard that OO uses the Render extension if available, and my remote X server doesn't have Render, I'd like to try disabling Render on my local machine. I'm using RedHat 7.2, which uses XFree86 4.1, with the Render extension built-in. Is there a way to disable this extension? TIA, James ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Disabling Build-In Extensions
Around 16 o'clock on Dec 17, James Keeble wrote: I'm trying to run OpenOffice 641, but I've found that it crashes when run locally. In particular, when selecting any menu other than Help or Window, it immediately dies. If run remotely, this never happens. Their use of Render is pretty broken; I've recently committed a fix that makes it work fine (at least on my box, as usual). Keith PackardXFree86 Core TeamCompaq Cambridge Research Lab ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Problems adding modes with XF86VidMode
I'm having a little trouble adding and switching to modes in my app. First off, the XF86VidMode manpage eludes to a description of AddModeLine being present, but there is none. XF86VidModeAddModeLine() takes two modelines, one is 'new modeline' the other is 'after modeline'. If you pass in anything for 'after modeline' other than all 0s then the call returns BadValue. Looking at the code, it doesn't seem to be used for anything at all. Maybe it should be removed or fixed. No matter what mode I give to AddModeLine(), I always get XF86VidModeBadHTimings. From the code, this is because my HSYNC is out of range, however when I calculate it myself and compare with the numbers from GetMonitor, it's definitely in range. In fact, taking an existing modeline and changing the hdisplay to be one pixel larger (to not conflict with the existing mode) causes this error. Any ideas as to what is going on? The mode validates successfully using ValidateMode(). I'm using XFree86 version: 4.1.0.1 from debian. I'm trying to allow my application to switch the refresh rate for playing video. (http://www.dumbterm.net/graphics/tvtime/) -- Billy Biggs [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Disabling Build-In Extensions
On Mon, Dec 17, 2001 at 04:31:38PM -0800, Keith Packard wrote: I'm trying to run OpenOffice 641, but I've found that it crashes when run locally. In particular, when selecting any menu other than Help or Window, it immediately dies. If run remotely, this never happens. Their use of Render is pretty broken; I've recently committed a fix that makes it work fine (at least on my box, as usual). That's great to hear. Were you having the the same problem I was, or something else? Also, still wondering if it's possible to disable the Render extension for now. Thanks, James ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Radeon without BIOS?
On Mon, 17 Dec 2001, Aleksandr Koltsoff wrote: Hello, Is anyone working on the non-BIOS init code for radeon? Especially the DVI-output / dualheadiness is of interest. If so, please contact privately. You might want to take a look at http://gatos.sf.net/ - you can find there a modified version of the driver that could be of interest to you. Vladimir Dergachev Thanks. Aleksandr Koltsoff Design Manager Engineering Office Bertel Ekegren Ltd +358 9 613 03228 (tel), +358 9 613 03200 (fax) ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]XFree86 setup questions for i830 based system
I have been working with kernel version 2.4.4, from a SuSE 7.2 distribution. I used the cvs tool to checkout the latest XFree version and compiled the new X server. So far, I have been able to use the default video driver and monitor settings (800x600, 8bit VESA @75Hz). I compiled the drm modules and I am now stuck at the point of loading the modules. modprobe i830 yields the 'cannot allocate memory' failure. Is this related to the version of agpgart.o that I am using? If so, where can I find a more recent version? My next step is to build and use kernel 2.4.16 from kernel.org. Will this help with my failure? Any help is appreciated and my thanks goes out to all who answer the questions on this list. If it were not for you, I would still be using windows on my notebook ;). Thanks, Bryan ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XFree86 setup questions for i830 based system
[EMAIL PROTECTED] wrote, I have been working with kernel version 2.4.4, from a SuSE 7.2 distribution. I used the cvs tool to checkout the latest XFree version and compiled the new X server. So far, I have been able to use the default video driver and monitor settings (800x600, 8bit VESA @75Hz). I compiled the drm modules and I am now stuck at the point of loading the modules. modprobe i830 yields the 'cannot allocate memory' failure. Is this related to the version of agpgart.o that I am using? If so, where can I find a more recent version? The kernel from version 2.4.11 has agpgart support for the i830. My next step is to build and use kernel 2.4.16 from kernel.org. Will this help with my failure? It works for me with 2.4.16. However, I have a different problem related to video modes, see http://www.xfree86.org/pipermail/xpert/2001-December/014075.html Are you able to get a resolution higher than 640x480 with 16bpp? Cheers, Manuel ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]need help setting up xfree86 on sparcstation 20
I'm actually very happy with XFree86 on my Solaris 8/Sparcstation 20/onboard CG14 w/4MB VSIMM box. I don't know if its my particular hardware/drivers, or the X clients that I am running, but the OpenWindows Xsun that comes with solaris is a monster!! Sun's Xsun server balloons up to 300 megs, and usually forces me to hardware reset my system after it crashes it. (even stop-a doesn't work) Right now I'm running tons of GTK apps on XFree86 on my SS20, including mozilla, and the Xsun process size is only 13MB. It would probably be 300MB if I was running Solaris Xsun. Thank you for saving me XFree86! Anyway, on to my configuration problems. I can't figure out how to make the Xserver run in 24-bit color! Like I said before, my system is a Sun Sparcstation 20 with on board SX video with a 4 meg VSIMM. That means its a cgfourteen that is capable of running 1168x900 (or whatever the standard sun res is) @ 24 bits per pixel. I have compiled XFree86 4.1.0 from source with gcc-2.95.3 on this Solaris 8 box. I had a couple of false starts, but I figured out I needed to #define Xsun24Server YES and the other Xsun's NO in my site.def. I have Xsun24 in my XFree86/bin directory and that is what is run when I run startx and X. But it only runs in 8 bit color! After a little bit of research, I discovered that the Xsun in XFree86 does not abide my the same rules as the PC version of the X server. No XF86Config or anything of the sort, I have to use the command line options described in man Xsun and man Xserver. From what I understand from these man pages (though they do not mention the cg14), Xsun should autodetect my card and pick the highest supported depth. There is no -depth or -fbbpp option with Xsun (that I have observed). Now on to what or what not may be a bug... I did a X -fbinfo or Xsun24 -fbinfo or startx -- -fbinfo (its all the same), and I found out this: Usually when I start my SS20 it goes into dtlogin (the Openwindows version of XDM). At that point I select the Command line login option, Solaris then kills its OpenWindows XServer, and I login and run startx -- -fbinfo. When I do this, XFree86 starts, and it tells me The framebuffer is really a tcx (remember, its a cg14). xfree then starts in 8-bit color. I have discovered, after I do a dtconfig -d and reboot, xfree86 no longer starts. dtconfig -d disables dtlogin, and basically what this boils down to is that I am not running solaris Xsun before xfree86 Xsun24. xfree86 will not start on my SS20 unless the solaris version of Xsun has already been run once since the last bootup. When I run startx -- -fbinfo in these circumstances, it tells me The frambuffer is really a cg8 (like I said before, its a cg14), then it crashes, saying something about a FBIO error or something. I can reply with the exact error mesage if necessary. So, my main problem is that I can't run in 24-bit color. Also however, there is the problem of xfree86 not starting on this system without the Sun xserver having been starting once. thanks for your help, and thanks for XFree86! Jim Faulkner [EMAIL PROTECTED] SDF Public Access UNIX System - http://sdf.lonestar.org ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]gamma settings only work on display :0.0?
I'm not sure if this is a general problem, or something specific to my setup, but it looks like gamma changes only ever affect screen 0, not screen 1: when I use xgamma to change things on display :0.0, it works, but on display :0.1, there is no visible effect (though xgamma does show that display :0.1 received the values I set on it.) This is XFree86-4.1.0-3 on an x86 Red Hat 7.2 system, with a Matrox MGA G450 DualHead card. -- Jamie Zawinski [EMAIL PROTECTED] http://www.jwz.org/ [EMAIL PROTECTED] http://www.dnalounge.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
