[Xpert]Xfree86 4.2.0 using 99% CPU on SiS?
G'day all, Has anyone seen a problem where XFree86 uses all available CPU when started from init. I'm just building a system from Red Hat 7.1 with 2.4.18 kernel, X4.2.0 on SiS730 chipset Duron processor... I used the binary dist. of X 4.2.0 I created a "service" to start xinit on boot to run a custom app. When it boots X takes up all the CPU. If I kill it and restart it works as expected <1% CPU. If anyone has any clues, I'd appreciate it. Cheers, Peter. -- Peter McNeil Engineering Manager Newton Pty Ltd http://www.newton.com.au Ph : +61 2 6247 3544 Fax: +61 2 6247 3533 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]ATI Radeon VE dual head support?
I do believe my ServerLayout section is correct as well. I've attached a log file as well as my entire XF86Config. I will feely muchly indebted if someone can help me with this! I am, BTW running a genuine ATI card. Came in an ATI retail box, even. - Original Message - From: "hy0" <[EMAIL PROTECTED]> To: "Berck E. Nash" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Wednesday, April 10, 2002 1:07 AM Subject: Re: [Xpert]ATI Radeon VE dual head support? > Have you put Screen 0 and Screen 1 in your SeverLayout section? If yes, post > your log file. > x420 supports VE dual-head setup. However if you are using some OEM version > of VE card (like DELL's) you might be out of luck. > > > > After hours of net searching, I've been unable to find any information > about > > whether or not the Radeon driver supports the dual-head cards. X runs > just > > fine, but I'm unable to set up multiple displays-- I'm stuck with one > > display mirrored on two monitors. While stereo-scopic vision is nifty and > > all, I'd prefer something a little more useful... Has anyone gotten > > dual-head working on the Radeon VE? IS this even supported in the driver? > > If so, how? Any help would be appreciated, considering I bought this card > > simply because it was dual-head. I'm running 4.20, and here are the > relevant > > sections of my XF86Config file: > > > > Section "Device" > > Identifier "RadeonVE" > > VendorName "ATI" > > BoardName "Unknown" > > Driver "ati" > > Screen 0 > > EndSection > > > > Section "Device" > > Identifier "RadeonVE2" > > VendorName "ATI" > > BoardName "Unknown" > > Driver "ati" > > Screen 1 > > EndSection > > > > Section "Screen" > > Identifier "Screen 1" > > Device "RadeonVE" > > Monitor "nanao" > > DefaultDepth 24 > > > > Subsection "Display" > > Depth 24 > > Modes "1024x768" > > ViewPort0 0 > > EndSubsection > > EndSection > > > > Section "Screen" > > Identifier "Screen 2" > > Device "RadeonVE2" > > Monitor "gateway" > > DefaultDepth 24 > > > > Subsection "Display" > > Depth 24 > > Modes "1024x768" > > ViewPort0 0 > > EndSubsection > > EndSection > > > > ___ > > Xpert mailing list > > [EMAIL PROTECTED] > > http://XFree86.Org/mailman/listinfo/xpert > > > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert > XF86Config Description: Binary data Xlog Description: Binary data
Re: [Xpert]Bug in polygon clipping code in XFree86 4.2.0
On Tue, Apr 09, 2002 at 04:11:28PM -0700, Andrew P. Lentvorski wrote: > Problem: If a polygon which is being filled with a stipple intersects a > clip region, the fill fails and paints the clipped region black. Here's a pair of X window dumps from before and after the window was hidden and then re-exposed. Do they exhibit the correct behavior? The window dumps accurately replicate what I see on the screen. In case they are broken for me as well on my Voodoo3 2000, my XFree86 log file is attached. -- G. Branden Robinson| Debian GNU/Linux | Please do not look directly into [EMAIL PROTECTED] | laser with remaining eye. http://people.debian.org/~branden/ | shot1.xwd.gz Description: Binary data shot2.xwd.gz Description: Binary data XFree86.0.log.gz Description: Binary data msg05439/pgp0.pgp Description: PGP signature
Re: [Xpert]Nvidia GeForce2 (Go) - Christoph Mertins
Hi again, No I haven't tried the leave X option in apmd.conf though I don't seem to have an apmd.conf on my machine. Is it linux specific? NetBSD's apmd documentation doesn't seem to make any reference to an apmd.conf. I realize I hadn't noted my o/s before perhaps this caused confusion. Thanks Rob At 06:47 AM 4/9/02 +0200, you wrote: >On Mon, 8 Apr 2002, Mark Vojkovich wrote: > >> On Tue, 9 Apr 2002 [EMAIL PROTECTED] wrote: >> >> > Not sure where to send problem reports but I just want to point out an oddity in >the current xfree cvs co. The experimental support for the Nvidia GeForce2 Go works >quite well with the following exception. >> > >> > If the notebook is running on DC and apm kicks in when the screen comes back from >being blanked it is improperly redrawn thereafter. The top left appears about 40% >down the lcd and the bottom is wrapped over the top. This doesn't however effect the >mouse coordinates it's top left remains correct. >> > >> > The problem is reproducible by unplugging AC power from the notebook and leaving >it on DC with no activity long enough for x to blank the screen. >> > > >have you tried the leave X option in the apmd.conf? > >-- >MfG >Christoph Mertins >[EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Nvidia GeForce2 (Go) - Mark Vojkovich
Hi, To answer your question(s): It's the notebook is a Dell Inspiron 8000 I have made virtually no configuration changes except setting the horiz. and vert. sync ranges. I'm also running it at 1600x1200 16bpp. Otherwise it's using a stock standard XF86Config generated by xf86config. I'm not sure what you mean by switching VT's but if you mean swapping to another desktop and back no it doesn't fix itself. Other things that don't work include restarting the window manager, allowing it to go to blank the screen again, refreshing the screen. Also, I neglected to note it in my previous post but I'm using NetBSD 1.5.2 this may be relevant. Thanks Rob At 09:11 PM 4/8/02 -0700, you wrote: >On Tue, 9 Apr 2002 [EMAIL PROTECTED] wrote: > >> Not sure where to send problem reports but I just want to point out an oddity in >the current xfree cvs co. The experimental support for the Nvidia GeForce2 Go works >quite well with the following exception. >> >> If the notebook is running on DC and apm kicks in when the screen comes back from >being blanked it is improperly redrawn thereafter. The top left appears about 40% >down the lcd and the bottom is wrapped over the top. This doesn't however effect the >mouse coordinates it's top left remains correct. >> >> The problem is reproducible by unplugging AC power from the notebook and leaving it >on DC with no activity long enough for x to blank the screen. >> > > Interesting. Sounds like it might be bios-specific behavior. >Which laptop is this? I'll see if I can reproduce it. > Does it go back to normal if you switch VT's and switch back? > > >Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Need help getting X to run at 1920x1440
I was just wondering if it would be possible to get X to run at 1920x1440 with an Nvidia Geforce 3 ultra and a 21 inch monitor (btw this is on a FreeBSD machine).any help would be greatly appreciated _ MSN Photos is the easiest way to share and print your photos: http://photos.msn.com/support/worldwide.aspx ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Radeon Mobility and Dual-Head Support?
On 9 Apr 2002, David B. Ritch wrote: > I tried watching the movie xine_about.avi using xine 0.98. On screen 0, > the builtin flat panel display, it worked fine. On screen 1, the > external monitor, it did not. Instead, the xine screen on the external > monitor went black. At approximately the same location on screen 0 as > the xine screen on screen 1, a rather colorful rectangle appeared. It > was made up of pink lines and stuff that looked like static. When I > stopped the movie, the static stopped moving. However, the pink box > remained until I exited xine. Thanks :)) Are the screens running at the same resolution ? Can you try this: grab the xine screen (while displaying movie) with gimp (or anything that can take a snapshot). You should get a black or almost black image. Now try displaying that image on the first screen in the same place as the "colourful rectangle".. Let me know what happens. thanks ! Vladimir Dergachev > > dbr > > On Mon, 2002-04-08 at 15:26, Vladimir Dergachev wrote: > > > > > > On 8 Apr 2002, David B. Ritch wrote: > > > > > Never mind! I got it working. FYI - here's my XF86Config file. > > > > Great :) Could you report on how well Xv works on both screens ? Thanks ! > > > > Vladimir Dergachev > > > > > > > > dbr > > > > ___ > > 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
Re: [Xpert]ATI Radeon VE dual head support?
Have you put Screen 0 and Screen 1 in your SeverLayout section? If yes, post your log file. x420 supports VE dual-head setup. However if you are using some OEM version of VE card (like DELL's) you might be out of luck. > After hours of net searching, I've been unable to find any information about > whether or not the Radeon driver supports the dual-head cards. X runs just > fine, but I'm unable to set up multiple displays-- I'm stuck with one > display mirrored on two monitors. While stereo-scopic vision is nifty and > all, I'd prefer something a little more useful... Has anyone gotten > dual-head working on the Radeon VE? IS this even supported in the driver? > If so, how? Any help would be appreciated, considering I bought this card > simply because it was dual-head. I'm running 4.20, and here are the relevant > sections of my XF86Config file: > > Section "Device" > Identifier "RadeonVE" > VendorName "ATI" > BoardName "Unknown" > Driver "ati" > Screen 0 > EndSection > > Section "Device" > Identifier "RadeonVE2" > VendorName "ATI" > BoardName "Unknown" > Driver "ati" > Screen 1 > EndSection > > Section "Screen" > Identifier "Screen 1" > Device "RadeonVE" > Monitor "nanao" > DefaultDepth 24 > > Subsection "Display" > Depth 24 > Modes "1024x768" > ViewPort0 0 > EndSubsection > EndSection > > Section "Screen" > Identifier "Screen 2" > Device "RadeonVE2" > Monitor "gateway" > DefaultDepth 24 > > Subsection "Display" > Depth 24 > Modes "1024x768" > ViewPort0 0 > EndSubsection > EndSection > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]missing code in VESA DPMS
I'm trying to get DPMS screen blanking to work on a ViewSonic ViewPad 1000, but I'm concerned about the code which has appeared in 4.2.0. In 4.1.0, DPMSSet indirectly called VESADisplayPowerManagementSet, which called vgaHWDPMSSet, which called stdwriteCrtc via a pointer, which contained the lines outb(hwp->IOBase + hwp->PIOOffset + VGA_CRTC_INDEX_OFFSET, index); outb(hwp->IOBase + hwp->PIOOffset + VGA_CRTC_DATA_OFFSET, value); In 4.2.0, DPMSSet indirectly called VESADisplayPowerManagementSet, which employs the WriteCrtc macro which expands to outb(VGA_CRTC_INDEX_OFFSET, index);\ outb(VGA_CRTC_DATA_OFFSET, value) That seemed clearly bogus, and fortunatly for my peace of mind, in yesterday's 4.2.0 CVS fetch, DPMSSet indirectly called VESADisplayPowerManagementSet, which employs the WriteCrtc macro which now expands to outb(pVesa->ioBase + VGA_CRTC_INDEX_OFFSET, index);\ outb(pVesa->ioBase + VGA_CRTC_DATA_OFFSET, value) >From inspection, this seems better, but isn't there still the need for some additional offset? Or was the presence of "hwp->PIOOffset" a red herring? In any event, "xset dpms force off" doesn't work. I learned to put 'Option "dpms" "on"' in the "Screen" section, and with the insertion of "fprintf" statements, I have confirmed WriteCrtc gets called. Shortly after the screen blanks, xf86DPMSInit is called again, and the screen comes back on. Since I have no specifications for the hardware interface, I can only reason by analogy and comparison. If someone such as the author of these changes (is it Marc La France?) would drop me a note, I'm quite willing to help work on this part of the driver. It may be that DPMS works (mostly), but something further on is failing causing th reset. Anyone have suggestions? Randolph Bentson [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Bug in polygon clipping code in XFree86 4.2.0
Configuration: FreeBSD 4.5 - XFree86 4.2.0 - ATI Radeon VE
Problem: If a polygon which is being filled with a stipple intersects a
clip region, the fill fails and paints the clipped region black.
Diagnosing:
1) rectangles do not seem to suffer from this problem
2) solid(non-stipple) fills do not seem to exhibit the problem
3) if NoAccel is turned on, the problem goes away
How to repeat:
Attached is a program which draws 8 square polygons, 4 of which are not
clipped, 4 of which are. The rightmost polygons should all fail. If they
don't, please let me know.
I will be happy to provide any other logs or configuration information
required as this was a real pain to hunt down.
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<6; 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 */
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]Question About Bus mastering
On Tue, Apr 09, 2002 at 04:12:27PM -0600, [EMAIL PROTECTED] wrote: > Hi, hi > I would like to know whether XFree86 supports bus mastering option? If > yes then is there anyway I can switch off the bus mastering option? AFAIK this isn't done directly by XF86, but by projects like DRI. XF86 can use DRI to do busmastering. In that case you can turn it off by disabling DRI (i.e. not loading the module or commenting the appropriate line in XF86Config). BTW the only reason I imagine disabling busmastering is useful is if it causes freezes or corrupt video output. If this is the case, you should consider reporting it (e.g. here or to dri-devel). > regards, > Vikram Bye, Peter Surda (Shurdeek) <[EMAIL PROTECTED]>, ICQ 10236103, +436505122023 -- Press every key to continue. msg05431/pgp0.pgp Description: PGP signature
Re: [Xpert]fbdev in 24 bpp
On Wed, 2002-04-10 at 00:01, Kevin Geiss wrote: > can fbdev handle 24 bits per pixel color? Yes. > I noticed that in xc/programs/Xserver/hw/xfree86/drivers/fbdev/fbdev.c, > when it calls xf86SetDepthBpp() it passes in 0 for the depth24flags. I don't know offhand what that means, but certainly not that it can't handle 24 bpp. > does this mean it is a bad idea to try to force it into a 24bpp mode? No. I can't even find the error you posted earlier anywhere, do you use stock 4.2.0? Maybe there's a problem with your framebuffer device? -- 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
[Xpert]Question About Bus mastering
Hi, I would like to know whether XFree86 supports bus mastering option? If yes then is there anyway I can switch off the bus mastering option? I would be glad to know information on this. Thanks in advance, regards, Vikram Grad Student - CS dept University of New Mexico ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]fbdev in 24 bpp
can fbdev handle 24 bits per pixel color? I noticed that in xc/programs/Xserver/hw/xfree86/drivers/fbdev/fbdev.c, when it calls xf86SetDepthBpp() it passes in 0 for the depth24flags. does this mean it is a bad idea to try to force it into a 24bpp mode? ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]canonical answer to the complaints about root-window sized cached pixmaps?
On Tuesday 09 April 2002 18:33, you 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. > > See > > http://www.nvnews.net/forum/showthread.php?s=&threadid=13243 > > for more information. One person claims, "his "problem" has surfaced > again and again on the Xpert mailing list. Time and again, it has been > shot down. Check KDE." > > ...but he cited no specific messages on this list. Hello Branden, I tend to answer the odd question or two on KDE's own user mailing lists (as well as monitoring many of the developer lists etc.). This is the first message I've seen in a very long time where someone is complaining about X's memory usage in combination with KDE. Do you really get so many of these types of complaints that you want to make it a FAQ? If so, please direct such users over to KDE's mailing lists - http://www.kde.org/mailinglists.html - and we can try and investigate/resolve their issues fully. In fact, maybe that should be the answer to the FAQ! :-) Cheers, Sean -- Sean McGlynn [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]canonical answer to the complaints about root-window sized cached pixmaps?
On Tue, Apr 09, 2002 at 11:39:45AM -0700, Mark Vojkovich wrote: >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. Thanks a lot, Mark. Hopefully I can help to cut down on the number of complaints, at least from Debian users. This will go into my FAQ. -- G. Branden Robinson|I am sorry, but what you have Debian GNU/Linux |mistaken for malicious intent is [EMAIL PROTECTED] |nothing more than sheer http://people.debian.org/~branden/ |incompetence! -- J. L. Rizzo II msg05426/pgp0.pgp Description: PGP signature
Re: [Xpert]Radeon Mobility and Dual-Head Support?
I tried watching the movie xine_about.avi using xine 0.98. On screen 0, the builtin flat panel display, it worked fine. On screen 1, the external monitor, it did not. Instead, the xine screen on the external monitor went black. At approximately the same location on screen 0 as the xine screen on screen 1, a rather colorful rectangle appeared. It was made up of pink lines and stuff that looked like static. When I stopped the movie, the static stopped moving. However, the pink box remained until I exited xine. dbr On Mon, 2002-04-08 at 15:26, Vladimir Dergachev wrote: > > > On 8 Apr 2002, David B. Ritch wrote: > > > Never mind! I got it working. FYI - here's my XF86Config file. > > Great :) Could you report on how well Xv works on both screens ? Thanks ! > > Vladimir Dergachev > > > > > dbr > > ___ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert -- David B. Ritch High Performance Technologies, Inc. signature.asc Description: This is a digitally signed message part
Re: [Xpert]canonical answer to the complaints about root-windowsized 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. Mark. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]startx and two graphic cards
Hi, I have two graphic cards in my box, one is ATI Rage XL(PCI) and one is ATI Radeon VE QY(AGP). I would like to control the AGP card from a kernel module we have written (which displays on a projector) and I would like to let X control the PCI card (which displays on a flat panel monitor). While in console mode the kernel module correctly displays images using the AGP card and the message "ATI Rage SDRAM BIOS P/N 113-72307-100 4.330" is displayed using the PCI card. We used the vesafb driver to configure the AGP card (primary card according to BIOS) to the desired mode of 1024x768. The problem begins when we use startx. The PCI controlled monitor starts X correctly but our kernel module no longer has control of our AGP card (no image displays on projector). Does any know why X seems to be taking our control of the AGP card away? Thanks a bunch! Jing __ 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]canonical answer to the complaints about root-window sized cached pixmaps?
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. See http://www.nvnews.net/forum/showthread.php?s=&threadid=13243 for more information. One person claims, "his "problem" has surfaced again and again on the Xpert mailing list. Time and again, it has been shot down. Check KDE." ...but he cited no specific messages on this list. -- G. Branden Robinson| If you have the slightest bit of Debian GNU/Linux | intellectual integrity you cannot [EMAIL PROTECTED] | support the government. http://people.debian.org/~branden/ | -- anonymous msg05422/pgp0.pgp Description: PGP signature
Re: [Xpert]ATI Rage problem
On 9 Apr 2002, Kherry Zamore wrote: > I have an ATI Rage II+DVD (Mach64, Rage128 chipset) and am using XFree86 > 4.1.0 on FreeBSD. I'm stuck with a slightly annoying problem. > Artifacts are left on the screen after moving around some windows. I > tried disabling a few options and changing resolutions/color depths, but > that didn't solve the problem. Another thing I should mention is when I > go to console, characters tend to disappear and reappear on the screen > when it scrolls. I'm not exactly sure if this is a hardware or software > problem since XF86 3.3.6 didn't have any problems when I used it. If > anyone has any suggestions, it would be greatly appreciated. Let's narrow this down a bit. See if the artifacts still appear with Option "NoAccel". BTW, the Rage II+DVD is a Mach64, not a Rage128. 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]Re: Xkb Mappings and multiple keyboards.
On Tuesday 09 April 2002 05:51 pm, James wrote: > Ok my mistake - linux maps both keyboards into one system > keyboard - so it's not XFree's fault - James. How difficult is it to feed multiple keyboards more or less directly into X? Cheers; Leon ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Problem compiling Xfree
Hi, I try to compile Xfree 4.2.0 on my linux slackware 8 with gcc-3.0.4 and i got this error : [...] make[3]: Entering directory `/tmp/xc/programs/glxinfo' rm -f glxinfo gcc -o glxinfo -O3 -fno-strength-reduce -march=i686 -ansi -pedantic -Wall -Wpointer-arith -L../../exports/lib glxinfo.o -lGLU -lGL -lXext -lX11 -lpthread -lm -Wl,-rpath-link,../../exports/lib ../../exports/lib/libGLU.so: undefined reference to `swap(void**, int, int)' collect2: ld returned 1 exit status make[3]: *** [glxinfo] Error 1 make[3]: Leaving directory `/tmp/xc/programs/glxinfo' make[2]: *** [all] Error 2 make[2]: Leaving directory `/tmp/xc/programs' gmake[1]: *** [all] Error 2 gmake[1]: Leaving directory `/tmp/xc' gmake: *** [all] Error 2 It would be great if you could help me with this ! Best regards, Pierre. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Xserver problem on G4 Nvidia
Mark Vojkovich wrote: >On Sat, 6 Apr 2002, F. Heitkamp wrote: > >>I've posted some previous messages about the Xserver >>problem I am having. I have a G4 533 dualie Snakebit >>I am running Debian unstable. I am using ICEWM. >>The machine came with the GForce 2MX. >> >>When I start up X it runs for several minutes fine. >>At some point it appears to stop. I can still move >>the mouse cursor around. I put a debug statement >>in nv_xaa.c at the suggestion of Mark V. The statement >>checks if NVSebsequentScanlineCPUToScreenColorExpandFill >>arguments w and h are ever zero. >> > I don't know what would be causing this. I thought maybe >the BigEndian color expansion code in XAA had some bugs in >it, but it doesn't sound like it. I'm still under the impression >that this is due to color expansion and not due to power management >or something else. > > Can you try disabling color exapansion with > > Option "XaaNoScanlineCPUToScreenColorExpandFill" > This seemed to help a lot. I left X running with xscreensaver for probably almost two days without a crash. Previous to that and after applying the option, I tried to use Linux, with ICEWM like I would normally, (surfing the web with Mozilla, reading news with pan, email etc.) and the system finally crashed after at least an hour. A little investigation, seemed to suggest that the crash happened in the glibc select call. (Mouse cursor would not move, display was frozen.). I had to log in remotely to shutdown. Another problem I have, but still investigating is when I launch X using 'startx', log out of X, and then run startx again, X doesn't start and I get a blank terminal. I updated glibc to 2.2.5-4 and things seem better but I haven't banged on Linux really hard or checked if 'startx' problem has gone away. However, I did do 'normal' stuff without a crash, and shutdown Linux normally to boot to Mac OS X. Anyway this is a vast improvement nonetheless. Thanks Mark! > > > In the section device? When you do that the driver >should stop reporting > > Indirect CPU to Screen color expansion > >in the XAA section of the log file. If that makes it go away I >think we may just have to disable color expansion on PPC. >I'm assuming other people have seen this problem? Can't say >that I have, but I haven't logged much time on PPC. > > > Mark. > > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Xkb Mappings and multiple keyboards.
Ok my mistake - linux maps both keyboards into one system keyboard - so it's not XFree's fault - James. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Nvidia GeForce2 (Go)
On Mon, 8 Apr 2002, Mark Vojkovich wrote: > On Tue, 9 Apr 2002 [EMAIL PROTECTED] wrote: > > > Not sure where to send problem reports but I just want to point out an oddity in >the current xfree cvs co. The experimental support for the Nvidia GeForce2 Go works >quite well with the following exception. > > > > If the notebook is running on DC and apm kicks in when the screen comes back from >being blanked it is improperly redrawn thereafter. The top left appears about 40% >down the lcd and the bottom is wrapped over the top. This doesn't however effect the >mouse coordinates it's top left remains correct. > > > > The problem is reproducible by unplugging AC power from the notebook and leaving >it on DC with no activity long enough for x to blank the screen. > > have you tried the leave X option in the apmd.conf? -- MfG Christoph Mertins [EMAIL PROTECTED] ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]XFree86 version 4.2.0 and SiS 6326 compatibility: asking again
On Mon, 8 Apr 2002 13:24:28 -0700 (PDT) Dick Lewis <[EMAIL PROTECTED]> wrote: > NOTE: THIS IS MY SECOND ATTEMPT TO POST THIS MESSAGE (THE PREVIOUS > BEING APR. 5) > AM I DOING SOMETHING WRONG HERE? OR JUST BEING IMPATIENT? > > I've been successfully using an older XFree86 version (3.3.6) with > an SiS 6326 video card (on Mandrake 8.0). Recently I downloaded > and installed XFree86 4.2.0. Running XFree86 -configure produced > verbose error messages; startx worked (after a fashion) but I > couldn't get KDE to run. > > Does XFree 4.2.0 require a *new* driver specifically for this card? > If so, > How can I obtain that driver? > If it's in one of the tarballs I downloaded, how do I install it? > > Beyond that, what light can anyone shed on getting KDE (or icewm) to run > with XFree 4.2.0? > > Regards -- Dick Lewis > > > > > > __ > 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 > msg05415/pgp0.pgp Description: PGP signature
Re: [Xpert]XFree86 version 4.2.0 and SiS 6326 compatibility: asking again
On Mon, 8 Apr 2002 13:24:28 -0700 (PDT) Dick Lewis <[EMAIL PROTECTED]> wrote: > NOTE: THIS IS MY SECOND ATTEMPT TO POST THIS MESSAGE (THE PREVIOUS > BEING APR. 5) > AM I DOING SOMETHING WRONG HERE? OR JUST BEING IMPATIENT? (see Egbert's message ...) > verbose error messages; startx worked (after a fashion) but I > couldn't get KDE to run. Well, if KDE didn't get started after upgrading to 4.2.0, *which* sort of graphical environment / desktop manager did you see while running startx? Tried to place something, like, "exec startkde" into your $HOME/.xinitrc file, or do you rely on some graphical login like [g|k]dm? > Beyond that, what light can anyone shed on getting KDE (or icewm) to run > with XFree 4.2.0? >From the "building-from-sources" - point of view: Did that with KDE, several times, and haven't seen any problems so far. Never tried icewm by now, but guess it should work as well. Cheers, Kris msg05414/pgp0.pgp Description: PGP signature
