Re: [Xpert]ATI Radeon VE dual head support?
Hi, On Wed, Apr 10, 2002 at 08:15:10PM -0700, hy0 wrote: > At the time dual-head features were added, there was no OEM VE card > available. The dual-head support in x420 radeon driver hasn't been tested on > any OEM card. It turns out DELL has some cards with OEM version of BIOS not > working with current driver on their 2nd head. Okay, understood. > AFAIK, DELL has cards with two DVI-D outputs and with two VGA outputs (all > from a dangle). It appears if the 2nd head is connected to a CRT, some > register bit (CRT2_ON?) has not been set correctly and you'll get a blank > screen. If the 2nd head is connected to a DFP, it's totally not handled. I'm > not sure when someone (or myself) can have time to have this support added. Yep, that's what I am seeing, I'm getting a blank screen on the 2nd CRT monitor. > Not sure what kind of card you have, maybe you can help to debug it :-) I would be more than happy to help. We purchased this model because I thought Radeon VE was supported by XFree, and I'm sad seeing my 2nd monitor blank :) Here's what the driver find about my card: (--) RADEON(0): Chipset: "ATI Radeon VE (AGP)" (ChipID = 0x5159) (--) RADEON(0): Linear framebuffer at 0xf000 (--) RADEON(0): MMIO registers at 0xff9f (--) RADEON(0): BIOS at 0xc100 (--) RADEON(0): VideoRAM: 32768 kByte (64-bit DDR SDRAM) (II) RADEON(0): PLL parameters: rf=2700 rd=60 min=12000 max=35000; xclk=18300 Not sure how I can help, but if you can direct me I'll do my best. Regards, Stephane ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon VE and SGI 1600sw with Multilink
DPMS may not be implemented for flat panels, but something seems to be. I use a laptop with an ATI Radeon Mobility graphics adapter, with the internal flat panel and an external monitor set up to run simultaneously with Xinerama. I noticed in the last day or two that when the external monitor went into power-savin mode, within seconds, the internal flat panel also went blank and its backlight shut off. dbr On Thu, 2002-04-11 at 02:45, Vladimir Dergachev wrote: > On Thu, 20 Dec 2001, Stuart Anderson wrote: > > > On 21 Dec 2001, Michel [ISO-8859-1] Dänzer wrote: > > > > > On Wed, 2001-12-19 at 16:09, Nate Pearlstein wrote: > > > > > > > 1. DPMS doesn't work. I looked in the source and it seems that DPMS > > > > only gets turned on if connected to a CRT. Why shouldn't this work for > > > > a flatpanel? > > > > > > Why should it? ;) I think DPMS was conceived for CRTs so I wouldn't > > > expect it to apply to flat panels naturally. > > > > I had notice the same thing int he ATI driver. On my laptop, Windows can > > completely shutdown the LCD screen, but under X, it doesn't. It seems > > perfectly reasonable for DPMS to also apply to LCDs, though the actual > > energy savings might be less. > > > > I think the corresponding code is simply not implemented. Because the LCD > (and backlight) on my Rage Mobility notebook is turned off when I use > external monitor. So X knows how to turn it off, just does not do it for > DPMS. > > Vladimir Dergachev > > > > > > > Stuart > > > > Stuart R. Anderson [EMAIL PROTECTED] > > > > Metro Link Incorporated South Carolina Office > > 5807 North Andrews Way 129 Secret Cove Drive > > Fort Lauderdale, Florida 33309 Lexington, SC 29072 > > voice: 954.660.2500 voice: 803.951.3630 > > http://www.metrolink.com/XFree86 Core Team > > > > ___ > > Xpert mailing list > > [EMAIL PROTECTED] > > http://XFree86.Org/mailman/listinfo/xpert > > > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert -- David B. Ritch High Performance Technologies, Inc. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Matrox G400 Dual Head
I'm trying to get a Matrox G400 dual head card working with XF86 4.2. The only documentation I found was under 4.1, so if there is something newer, let me know. The 4.1 docs said to set it up just as if you had 2 cards, but to use the same BusID in both devices section. I tried that, but still only got one head. The log file recognized the dual-head setup: (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "Card0" (**) |-->Screen "Screen1" (1) (**) | |-->Monitor "Monitor1" (**) | |-->Device "Card1" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" Later it says: (II) MGA: driver for Matrox chipsets: mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag100, mgag100 PCI, mgag200, mgag200 PCI, mgag400, mgag550 (II) Primary Device is: PCI 01:05:0 (WW) MGA: More than one matching Device section for instances (BusID: PCI:1:5:0) found: Card1 (--) Chipset mgag400 found Otherwise it looks like a single head setup. I am using the Matrox HAL library, but not the linux drm module as I don't need 3D. Is this supposed to work? If so any ideas what I'm doing wrong? I've attahced my config file and log file.` -- Chris BareMetro Link Incorporated [EMAIL PROTECTED] http://www.metrolink.com/ Xerrors.0.log.gz Description: gzip compressed data, deflated, original filename, `Xerrors.0.log', last modified: Thu Apr 11 11:23:32 2002, max compression, os: Unix XMetroconfig.gz Description: gzip compressed data, deflated, original filename, `XMetroconfig', last modified: Thu Apr 11 11:27:48 2002, max compression, os: Unix
[Xpert]problems with XFree 4.2 and Trident
OK, I have a damn Trident 3D Image 9750 video board and I'm using Alan Hourihane's trident video driver (http://www.xfree86.org/~alanh) that makes things do not look psicodelic pinky. But I still have some problems, I do belive most of them due to my video board (they really need improvements). One is that when using Xine the pinky-sicodelic colors come back and only rebooting X comes back to normal. Another I always had with XFree 4.x: If I run a SDL game and for some reason the SDL window looses focus and later regain focus, the black area between the used screen and the monitor border (something like 2/3 milimiters) get colored (pink, orange, red, etc). And if I move the SDL window to this colored area (outside of screen) I get a complete freeze. This problem isn't from SDL because happens with some X apps too. Fullscreen here is a nightmare. Running a app in fullscreen is asking: "please my dear pc, freeze!" :) What I want to know is: there is any hope that those problems can/will be fixed? Or should I keep taking LOTS of care when running apps to not move them out of screen or changing them to fullscreen? Thanks in advance. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XFree86 version 4.2.0 and SiS 6326 compatibility
On Wed, Apr 10, 2002 at 07:49:32PM -0700, Dick Lewis wrote: > 1. While libglide2x.so wasn't present on my system, that > in itself was likely not a problem; Why would you need this anyway? libglide2x is only for standalone 3D mode on Voodoo3/Banshee and for all 3D only Voodoo boards (Voodoo and Voodoo2). Unless you want the X server to use the 'glide' driver to use an old Voodoo/Voodoo2 board as a second head, you don't need the libglide2x.so library. Repeat: Glide is 100% NOT relevant with an SiS chipset. > 2. That I could be using an obsolete X configuration file. >Could not load the shared library file for Glide: "libglide2x.so"! What are you getting this from? I'm not convinced you're getting this from the X server itself. The error you got in your X server output log seems to indicate the new SiS drivers just don't grok the chip for some reason (old rev? old BIOS? something else?) -- 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]Matrox G400 Dual Head
> I'm trying to get a Matrox G400 dual head card working with XF86 4.2. > The only documentation I found was under 4.1, so if there is something > newer, let me know. Naturally I found the solution shortly after posting this. Matrox has a sample config file in their release notes: ftp://ftp.matrox.com/pub/mga/archive/linux/2002/lnx200notes.txt The secret is putting Screen 0 and Screen 1 in the 2 device sections. I hadn't seen that used before. -- Chris BareMetro Link Incorporated [EMAIL PROTECTED] http://www.metrolink.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Matrox G400 Dual Head
On Thursday 11 April 2002 07:14 pm, you wrote: > > I'm trying to get a Matrox G400 dual head card working with XF86 4.2. > > The only documentation I found was under 4.1, so if there is something > > newer, let me know. > > Naturally I found the solution shortly after posting this. Matrox has a > sample config file in their release notes: > > ftp://ftp.matrox.com/pub/mga/archive/linux/2002/lnx200notes.txt > > The secret is putting Screen 0 and Screen 1 in the 2 device sections. I > hadn't seen that used before. As far as I remember, Matrox also had a (proprietary) graphical tool that allowed you to set up dualhead with their cards under Xfree86 (for gnu/linux at least). Frank -- homepage: www.student.kuleuven.ac.be/~m9917684 jabber (=IM): [EMAIL PROTECTED] No part of this copyright message may be reproduced, read or seen, dead or alive or by any means, including but not limited to telepathy without the benevolence of the author. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: canonical answer to the complaints about root-window sized cachedpixmaps?
On Tue, 9 Apr 2002, Mark Vojkovich wrote: >Date: Tue, 9 Apr 2002 11:39:45 -0700 (PDT) >From: Mark Vojkovich <[EMAIL PROTECTED]> >To: Branden Robinson <[EMAIL PROTECTED]> >Cc: [EMAIL PROTECTED] >Content-Type: TEXT/PLAIN; charset=US-ASCII >List-Id: General X Discussion >Subject: Re: canonical answer to the complaints about root-window sized >cached pixmaps? > >On Tue, 9 Apr 2002, Branden Robinson wrote: > >> I get complaints about X's memory consumption all the time from KDE >> users who have dozens of virtual workspaces, large monitors, and a >> different image in the root window for each workspace. >> >> Is there a canonical answer to this question that I can give my users? >> I maintain a FAQ for Debian and I'm happy to add this information to it. >> > > The X-Window system is a client-server window system. The >memory for pixmap data resides on the server side instead of >the client side. If you have 8 1600x1200 32bpp root window images >that's 61 Megabytes. It resides in the server instead of the >client, unless they are shared memory pixmaps, in which case >it will be counted on both the server and client side. > > Obviously this data has to be stored someplace. It's not >like it can just disappear when you're not using it. I don't >know why it's so hard for those people to comprehend that. >If they were stored on the client side instead, people would >be complaining about KDE memory usage. I'd like to add to that another frequently reported problem of XFree86 consuming a lot of memory. Many people report X uses 64Mb+ of memory and can't see any reason why it should. They blame X for being bloated, etc. Digging into it more however, 99 times out of 100, they are using the output of top or procps or similar utility do show how much memory XFree86 is consuming. Unfortunately, the memory reported as used in top/ps output is interpreted solely as being system RAM and/or swap, and that is very misleading as it is not true. The memory shown by top, which users are misled into believing is memory used up by X, is an amalgamation of the video card's own memory, and memory mapped I/O regions, as well as the actual memory used by the X server, pixmaps, and various other things. It is not at all uncommon for a modern 64Mb video card, to have X's memory usage appear to be 100Mb or more, when in reality, 64Mb of that is video RAM, and 16-32Mb possibly mmapped registers. Most developers such as ourselves are aware of this, however most end-users are not. On Linux a user can view the memory map breakdown by logging in as root and looking at the file: cat /proc/$(pidof X)/maps That gives a fairly detailed breakdown of the memory map of the X server process, and what actual amount of memory is being used, etc. The exact meaning of the contents of the proc maps file is left as an exercise for the curious reader. ;o) Reading the kernel sources which implement it is about the best manual I know of. Hope this info is also useful for any FAQ. 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
[Xpert]two graphic cards again
Hi, We received the following reply from Michael Danzer about getting two video cards to work on our machine (see below). We would like to control one card (AGP) by initializing it with the vesafb driver and then writing directly to video RAM. The other card (PCI) we would like to control with X. Writing directly to video RAM on the first card works fine until we startx. Starting X seems to disable the card we have previously enabled through the vesafb driver. Does anyone know how to prevent X from disabling this card as has Michael suggested below. Thanks all, Jing > > The X server disables graphics chips it doesn't use > because they can > cause problems otherwise. That should be relatively > easy to hack around > though if you're confident it should work with your > configuration. > > > -- > 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 __ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert](no subject)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I have an IBM A30P. I have been trying for sometime to get xdm working. I have tried to Build Xfree86 from source and I could startx but no xdm. I now am running the most current OpenBSD binary snapshot. I believe this has the necessary drivers for my laptop since I can startx and that works ok. But everytime I fire up xdm I get a repeating cycle of X background with X cursor followed by blackscreen. This continues until I kill xdm from a telnet session. Virtual terminals are unavailable while this is taking place. I have included a debug below. Does anyone have any idea of how to fix or debug further. Any help will be appreciated, - -- Brian Domenick - --- [cheetos:/tmp]# xdm -debug 100 DisplayManager.errorLogFile/DisplayManager.ErrorLogFile value /var/log/xdm-erro rs DisplayManager.daemonMode/DisplayManager.DaemonMode value true DisplayManager.pidFile/DisplayManager.PidFile value /var/run/xdm.pid DisplayManager.lockPidFile/DisplayManager.LockPidFile value true DisplayManager.authDir/DisplayManager.authDir value /usr/X11R6/lib/X11/xdm DisplayManager.autoRescan/DisplayManager.AutoRescan value true DisplayManager.removeDomainname/DisplayManager.RemoveDomainname value true DisplayManager.keyFile/DisplayManager.KeyFile value /usr/X11R6/lib/X11/xdm/xdm- keys DisplayManager.accessFile/DisplayManager.AccessFile value /usr/X11R6/lib/X11/xd m/Xaccess DisplayManager.exportList/DisplayManager.ExportList value DisplayManager.randomFile/DisplayManager.RandomFile value /dev/mem DisplayManager.greeterLib/DisplayManager.GreeterLib value /usr/X11R6/lib/X11/xdm /libXdmGreet.so DisplayManager.choiceTimeout/DisplayManager.ChoiceTimeout value 15 DisplayManager.sourceAddress/DisplayManager.SourceAddress value false DisplayManager.willing/DisplayManager.Willing value su -m nobody -c /usr/X11R6/ lib/X11/xdm/Xwilling creating socket 177 Created chooser socket 5 Found new display: :0 local /usr/X11R6/bin/X vt05 StartDisplay :0 DisplayManager._0.serverAttempts/DisplayManager._0.ServerAttempts value 1 DisplayManager._0.openDelay/DisplayManager._0.OpenDelay value 15 DisplayManager._0.openRepeat/DisplayManager._0.OpenRepeat value 5 DisplayManager._0.openTimeout/DisplayManager._0.OpenTimeout value 120 DisplayManager._0.startAttempts/DisplayManager._0.StartAttempts value 4 DisplayManager._0.pingInterval/DisplayManager._0.PingInterval value 5 DisplayManager._0.pingTimeout/DisplayManager._0.PingTimeout value 5 DisplayManager._0.terminateServer/DisplayManager._0.TerminateServer value false DisplayManager._0.grabServer/DisplayManager._0.GrabServer value false DisplayManager._0.grabTimeout/DisplayManager._0.GrabTimeout value 3 DisplayManager._0.resetSignal/DisplayManager._0.Signal value 1 DisplayManager._0.termSignal/DisplayManager._0.Signal value 15 DisplayManager._0.resetForAuth/DisplayManager._0.ResetForAuth value false DisplayManager._0.authorize/DisplayManager._0.Authorize value true DisplayManager._0.authComplain/DisplayManager._0.AuthComplain value true DisplayManager._0.authName/DisplayManager._0.AuthName value XDM-AUTHORIZATION-1 MIT-MAGIC-COOKIE-1 DisplayManager._0.authFile/DisplayManager._0.AuthFile value SetLocalAuthorization :0, auth XDM-AUTHORIZATION-1 GenerateAuthorization XDM-AUTHORIZATION-1 Local server auth 6b 41 27 a3 5f dd f1 37 00 31 0d 8e 2a 1e 92 49 Got 0x2b060 (19 XDM-AUTHORIZATION-1) 6b 41 27 a3 5f dd f1 37 00 31 0d 8e 2a 1e 92 49 GenerateAuthorization MIT-MAGIC-COOKIE-1 Got 0x2b0a0 (18 MIT-MAGIC-COOKIE-1) a8 51 67 e7 2c 5d dd 16 d1 98 5e 9f 8c fb 7 2 9e File: /usr/X11R6/lib/X11/xdm/authdir/authfiles/A:0-J17761 auth: 0x21cc0 StartServer for :0 Server Started 12842 '/usr/X11R6/bin/X' 'vt05' '-auth' '/usr/X11R6/lib/X11/xdm/authdir/authfiles/A:0- J17761' display manager paused til SIGUSR1 XFree86 Version 4.2.0DisplayManager._0.resources/DisplayManager._0.Resources val ue /usr/X11R6/lib/X11/xdm/Xresources (for OpenBSD)DisplayManager._0.xrdb/DisplayManager._0.Xrdb value /usr/X11R6/bin /xrdb / X Window System DisplayManager._0.setup/DisplayManager._0.Setup value /usr/X11R6/lib/X11/xdm/Xs etup_0 (protocol Version 11, revision 0, vendor release 6600) DisplayManager._0.startup/DisplayManager._0.Startup value /usr/X11R6/lib/X11/xd m/Startup_0 Release Date: 23 January 2002 DisplayManager._0.reset/DisplayManager._0.Reset value /usr/X11R6/lib/X11/xdm/Ta keConsole 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/) DisplayManager._0.session/DisplayManager._0.Session value /usr/X11R6/lib/X11/xd m/Xsession Build Operating System: OpenBSD 3.1 i386 DisplayManager._0.userPath/DisplayManager._0.Path value /bin:/usr/bin:/usr/local /bin:/usr/X11R6/bin Module Loader present DisplayManager._0.systemPath/Display
[Xpert]Clipped stippled polygon and pixmap cache bug on ATI Radeon VE w/4.2.0
Okay, after tracking this, it turns out to be a pixmap cache bug. At
least, I can stop the problem from occurring by adding the "Option
"XaaNoPixmapCache"" line to my XF86Config file.
Bug: A stippled polygon which intersects a clip region gets filled in all
black
How to reproduce: Compile and run the attached program. It draws 8
polygons. The left 4 should be draw correctly. The right four *should*
be drawn at one-half the height of the left four (the right four are
clipped). If you have the bug, the right four rectangles will be half
height, but filled with black (possibly something else, but it should not
be what filled the left 4 polygons)
Workaround: Set the XaaNoPixmapCache flag in your XF86Config
Aside: Is this the right place to post this kind of stuff? I'd rather not
waste everybody's time, if not.
If anyone needs more info or log files, just holler.
Thanks,
-a
#include
#define stipple_bitmap_width 16
#define stipple_bitmap_height 16
static unsigned char stipple_bitmap_bits[] = {
0x33, 0x33, 0x66, 0x66, 0xcc, 0xcc, 0x99, 0x99, 0x33, 0x33, 0x66, 0x66,
0xcc, 0xcc, 0x99, 0x99, 0x33, 0x33, 0x66, 0x66, 0xcc, 0xcc, 0x99, 0x99,
0x33, 0x33, 0x66, 0x66, 0xcc, 0xcc, 0x99, 0x99};
Display *display;
int screen_num;
static char *progname;
int main(int argc, char **argv)
{
Window win;
Pixmap stippleBitmap;
char *display_name = NULL;
GC gc0,gc1,gc2,gc3;
unsigned long valuemask = 0;
XGCValues values;
XEvent event;
Colormap defaultColormap;
XColor red,green,blue,black,white,junk;
XRectangle clipRects[1] = {{400,50,400,400}};
XPoint rb[5] = {{0,0},{100,0},{100,100},{0,100},{0,0}};
XPoint r[8][5];
int i,j,k;
for(i=0; i<8; i++)
{
for(j=0; j<5; j++)
{
r[i][j].x = rb[j].x + i*100 + i*2;
r[i][j].y = rb[j].y;
}
}
progname = argv[0];
if ((display=XOpenDisplay(display_name)) == NULL)
{
printf("Failed to open display\n");
exit(-1);
}
win = XCreateSimpleWindow(display, RootWindow(display, screen_num),
0, 0, 800, 150, 0, BlackPixel(display, screen_num),
WhitePixel(display, screen_num));
screen_num = DefaultScreen(display);
stippleBitmap = XCreateBitmapFromData(display, win, stipple_bitmap_bits,
stipple_bitmap_width, stipple_bitmap_height);
XSelectInput(display, win, ExposureMask | KeyPressMask);
defaultColormap = DefaultColormap(display, screen_num);
XAllocNamedColor(display, defaultColormap, "red", &red, &junk);
XAllocNamedColor(display, defaultColormap, "green", &green, &junk);
XAllocNamedColor(display, defaultColormap, "blue", &blue, &junk);
XAllocNamedColor(display, defaultColormap, "black", &black, &junk);
XAllocNamedColor(display, defaultColormap, "white", &white, &junk);
values.foreground = red.pixel;
values.background = green.pixel;
values.fill_style = FillStippled;
values.stipple = stippleBitmap;
valuemask = GCForeground | GCBackground | GCFillStyle | GCStipple;
gc0 = XCreateGC(display, win, valuemask, &values);
XMapWindow(display, win);
while(1)
{
XNextEvent(display, &event);
switch (event.type)
{
case Expose:
/* Draw something */
XSetClipMask(display, gc0, None);
for(i=0; i<4; i++)
{
XFillPolygon(display, win, gc0, r[i], 5, Convex, CoordModeOrigin);
}
XSetClipRectangles(display, gc0, 0, 0, clipRects, 1, Unsorted);
for(i=4; i<8; i++)
{
XFillPolygon(display, win, gc0, r[i], 5, Convex, CoordModeOrigin);
}
break;
case KeyPress:
XFreeGC(display, gc0);
XCloseDisplay(display);
exit(-1);
break;
default:
break;
}
}
}
Re: [Xpert]Time to downgrade?
Thanks Joe, and to those who have reassured me that my card would work with the older versions! I've reinstalled 4.0.2 using the SuSE rpms, configured using SaX, added the touchscreen bits to the XF86Config, reinstalled the latest Nvidia drivers and... Works like a dream! A case, I think, of newer isn't necessarily better ;-) (I've had 4.0.2 running one of these touchsreen systems for a couple of months - the one restart was due to a power outage.) Cheers M Joe Krahn wrote: > Matthew Smith wrote: > >>I downloaded XF 4.2.0 in order to get the video card working (the >>version that I had from a SuSE Linux distribution did not work). >>Unfortunately, the Microtouch hardware now *doesn't* work - I get >>an error: Unable to query/initialize MicroTouch hardware. >>(EE) PreInit failed for input device "Touch0" (See my post of >>2002/04/08). >> > The maintainer of XFree86 XInput has done a poor job with the 4.x > series. He has done many complicated and mostly unnecessary changes, > with no documentation. He may have some sort of plan, but it seems > he has not had the time lately to follow through. > > MicroTouch may be one of the casualties. Before giving up > completely, try to see if the config setting have changed. Next, > run XFree with verbose logging (startx -- -logverbose 10). > At that level, it wil give you each character read from the > serial port. This might indicate what's wrong. > > Joe Krahn > > > -- Matthew Smith | _ ASCII Ribbon Campaign IT Consultant | ( ) - No HTML/RTF in e-mail Kadina, South Australia | X - No Microsoft docs in e-mail http://www.kbc.net.au | / \ - No vCards Ph: +61 888 212 395 | ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
