[Xpert]Problems with X on my box, X just freeze (Trident 3DImage9750)
First of all sorry about MTU/OS but I couldn't keep my Xwindows running enougth time to writte this email on it. This is my first email to this list so I don know if is the right place to do it (if not someone, please, tel me where I suppose to do it). OK here is the thing whenever I'm using my box on Linux (a RedHat 7.3, with all parches) I ran like 20 to 30 minutes and it just freeze with a funny pattern (something like the image file attched on this email: screen_pattern.jpg). This pattern changes time to times (it seems to be a random range of pixels of my current screen). It don't just freeze the X but the whole system. I'm sending, too, my configuration files (XF86Config and XF86Config-4) and some information about my box (cpuinfo/kernel version/ioports/dma/interrupts) and the last Xlog (a non-freezed session). I notice, trying to fix the problem, that if I comment dbe module (on XF86Config-4) Gnome cann't start correctly (but it starts). If I comment "dri" module the system freeze early. I really want to use Linux on my PC but I need X, so if you can help me I'll appreciate and my next email will came from a linux OS :). -- Gustavo Kuhn Andriotti <[EMAIL PROTECTED]> Suporte Nacional - Terra Networks Brasil S/A linux-cpuinfo Description: Binary data linux-dma Description: Binary data linux-interrupts Description: Binary data linux-ioports Description: Binary data linux-pci Description: Binary data linux-version Description: Binary data linux-XFree86.0.log Description: Binary data <> XF86Config-4 Description: Binary data XF86Config Description: Binary data
[Xpert]The window dont display anything.
Hy , I am Ivan, and I am doing a little program to do thumbnails of
images and display in an window,
controled by a infra red control (using lirc + some routines to find
what button is pressed ).
The problem is...
I make the window and map it, all fine;
I put the thumbnail images on the window, all fine;
I check the lirc device for data, data received, all fine;
Now when I try to put anything on the window, not appears :(
the function of the infrared data check:
---
int read_irdata(ir *ir)
{
int i,n;
lirc_t signal;
unsigned short int word=0;
ir->timeout.tv_usec = 10;
ir->timeout.tv_sec = 0;
for(n=1;n;)
{
FD_SET(ir->irfd,&ir->rdset);
n=select(ir->irfd+1,&ir->rdset,NULL,NULL, &ir->timeout);
if (n);
{
read(ir->irfd,&signal,1);
if(!(signal&PULSE_BIT))
{
if(signal > 1000)
word = (word<<1)+1;
else
word = (word<<1);
for(i=0;ir->ircode[i].code != 0 && word>>8 ==
ir->ircode[0].code>>8;i++)
if(word == ir->ircode[i].code)
{
ir->press[1] = ir->press[0];
ir->press[0] = i;
return i;
}
}
}
}
ir->press[0] = 0;
return 0;
} for(i=0;ir->ircode[i].code != 0 && word>>8 ==
ir->ircode[0].code>>8;i++)
if(word == ir->ircode[i].code)
{
ir->press[1] = ir->press[0];
ir->press[0] = i;
return i;
}
}
}
}
ir->press[0] = 0;
return 0;
}
and the typedef ir struct:
typedef struct ircode
{
unsigned short int code;
char name[CODENAME_MAX];
} ircode;
//Infra Red Struct
typedef struct ir
{
fd_set rdset;
struct timeval timeout;
int irfd;
struct ircode ircode[32];
unsigned int press[1];
} ir;
here:
quad = load_files("/temp");// Put all images of the /temp directory
on a linked list
thumbs(win,&th,quad,1,pos); // descompress,resize and XputImage the
thumbnail images on the window
read_irdata(ir); // read the lirc device and check if an
button was pressed
now is the problem if I try to display anything on the window.
Can my int read_irdata(ir *) to bug anything ?
If anybody wants, I can send also all source code.
Reguards.
Ivan Gustavo Munix Dos Santos
[EMAIL PROTECTED]
http://www.munix.com.br
tel: 012 - 3923 2925 Ramal 225
___
Xpert mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Fw: Problems with X on my box, X just freeze (Trident 3DImage9750)
First of all sorry about MTU/OS but I couldn't keep my Xwindows running enougth time to writte this email on it. This is my first email to this list so I don know if is the right place to do it (if not someone, please, tel me where I suppose to do it). OK here is the thing whenever I'm using my box on Linux (a RedHat 7.3, with all parches) I ran like 20 to 30 minutes and it just freeze with a funny pattern (something like the image file attched on this email: screen_pattern.jpg). This pattern changes time to times (it seems to be a random range of pixels of my current screen). It don't just freeze the X but the whole system. I'm sending, too, my configuration files (XF86Config and XF86Config-4) and some information about my box (cpuinfo/kernel version/ioports/dma/interrupts) and the last Xlog (a non-freezed session). I notice, trying to fix the problem, that if I comment dbe module (on XF86Config-4) Gnome cann't start correctly (but it starts). If I comment "dri" module the system freeze early. I really want to use Linux on my PC but I need X, so if you can help me I'll appreciate and my next email will came from a linux OS :). -- Gustavo Kuhn Andriotti <[EMAIL PROTECTED]> Suporte Nacional - Terra Networks Brasil S/A - Original Message Ends linux-report.zip Description: Zip compressed data
[Xpert]Re: Xpert]Re: [MPlayer-users] X hangs on Ati Rage128AIW
> gustavo <[EMAIL PROTECTED]> writes: > > > Solution: mandrake 8.2 came with a driver from Gatos (gatos.sf.net) that > > fixed these problems. (thanks Mandrake). > I'll check Mandrake snap of gatos drivers but I tried gatos drivers (from cvs, > few months ago) and still had hangs. That's true. Before mandrake 8.2 I also tried gatos drivers and they were still crashing with bttv, so I guess that someon on mdk solved the problem somehow. Btw, the driver I use is the default one installed by mandrake 8.2 , I didn't have to look around for any other. I am really quite busy now, so I can't investigate further. If you discover how mandrake fixed this it would be useful to post it to xpert I think. Best regards Gustavo Homem > > > With the dri kernel module, I can use Xv (with xine or mplayer), 3D GL apps, > > and bttv grabbing without any problem. > > > > Best regards > > Gustavo > > -- > Arkadiusz Mi¶kiewicz IPv6 ready PLD Linux at http://www.pld.org.pl > misiek(at)pld.org.pl AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PWr > ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Xpert]Re: [MPlayer-users] X hangs on Ati Rage128AIW
On Sunday 28 July 2002 07:05 pm, you wrote: > [Xpert]Re: [MPlayer-users] X hangs on Ati Rage128AIW Hello: In answer to your complaints I'd like to give you a tip. It seems to be a XFree 4.2 problem. When the dri kernel module is loaded it hangs the machine. Also without that module Xv doesn't work properly for mpeg formats (it used to in previous versions). Solution: mandrake 8.2 came with a driver from Gatos (gatos.sf.net) that fixed these problems. (thanks Mandrake). With the dri kernel module, I can use Xv (with xine or mplayer), 3D GL apps, and bttv grabbing without any problem. Best regards Gustavo ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Where Should I Be Sending Patches?
Hi all, I am not a XFree developer but I'd like to show a user viewpoint: X is faced as something strange, misterious and not transparent. Ex: Check out the rage 128 driver status (the driver of my complaints): "Know limitations: none" Pardon me , is there an errata for XF 4.2 ? More ? Some time ago I tried in every possible place to obtain a list of Xv capable XFree drivers...Mission Impossible (support is either accelerated or non accelerated), and no one seems to know that. Check out mozilla as an example: I sent dozens of bug reports, and allways was notified by email about their status, and the developers sometimes asked for other trials. Even workarounds get posted there. And well... #xfree86 is silent as a cave...and btw, Mr Mike Harris was one of the few people that was so kind to answer some questions. It really helped. Thanks a lot ! Why do #kde, #mozilla, #xine and others have lot's of non developers hanging and helping people while #xfree86 does not ? Doesn't it mean something ? Now, since X is at least as importante as KDE or Gnome, is X less suported by the distros then those projects ? Keep up the good work (and build a bugzilla :) ) Gustavo ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Re: Radeon and 2D acceleration (Gustavo Homem)
>Message: 15 >Date: Tue, 26 Feb 2002 12:07:46 -0500 (EST) >From: "Mike A. Harris" <[EMAIL PROTECTED]> >To: ODOU Michel <[EMAIL PROTECTED]> >cc: [EMAIL PROTECTED] >Organization: Red Hat Inc. >Subject: [Xpert]Re: Re: Radeon and 2D acceleration >On Tue, 26 Feb 2002, ODOU Michel wrote: >>Well, Mike, I understood but I still have some remarks : >>1- Why does is DRI code used for 2D acceleration ? I thought it >>was a sort of API (like OpenGL), and didn't expect it to be used >>in 2D. >Common misconception. Well, see the picture at dri.sf.net docs, that's what it sugests...it may be outdated then >DRI is an interface between userland and >the kernel to do DMA between the video board and memory basically >in a nutshell. There is nothing at all restricting its usage for >just 3D acceleration. The Radeon and Rage 128 drivers both use >DRI for 2D acceleration as well if DRI is enabled. Newer code in >the GATOS project also uses DRI for Xv IIRC. It does, too bad that it is badly broke for at leat some Rage 128 based cards (like mine). Even worst is that non-drm Xv is also broke since 4.1 ! (see my previous posts on this). And what is even worst is that there is no list of "known bugs and problems", if one wants to configure X for every machine then one must have a knowledge base of all specific card-drivers problems. Of course distros build this for internal use, but why isn't a public list available ? Smaller distros can't afford to own every revision of every chipset to build their own "known bugs and workarounds list". Am I wrong or XFree should publish one errata ? I can contribute with the problems I already detected if somone is willing to keep that online at xfree.org. Best regards Gustavo Homem "Quero ser o presidente de um povo obediente" - poeta Manuel João ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]A big confusion over here - XFree 4.2 - and rage 128
Hi Michel : Thanks for your answer. > > I can only guess why 4.0.3 worked better than 4.1.0; I guess it's > because the r128 driver in 4.0.3 didn't properly support 420 video (or > was it 422? I forget :) yet. I don't know exactly what are those 420 and 422 ? Image formats ? How does that justify the fact that mpeg2 overlay performance degraded ? What I complain about (with XFree 4.1 and XFree 4.2 DRI disabled) is a very high cpu load when using XV output, which causes frame dropping. With Xshm output I get no frame drops and Xv was supposed to provide better performance, so I have to conclude that Xv output is broke in either 4.1 and 4.2 , in the latter case it is broke in 2 different ways (but only for mpeg). > > > > X complained then about drm modules beiing old, so I downloaded the latest > > one from dri.sf.net , compiled and instaled the module at /lib/modules/ > > > > The result was as follows with dri enabled: > > > > 1 - Now bttv no longer freezes the system if used with dri enabled (hooray) > > 2 - The KDM login screen is completely messed (widgets are garbaged, not > > drawn properly) > > I have fixed this in DRI CVS and submitted the fix to XFree86. > > Both 1) and 2) are due to the fact that the r128 driver does 2D > acceleration differently with DRI enabled now. I'm sure you've also > noticed the better 2D performance. :) I read that the 2d acceleration mode had to be changed because it was incompatible with the use of bttv, but why have two diferent implmentations ? What I noticed was that with DRI enabled Xv ouput was smooth again before crashing (colors were wrong though), but that was the usual situation with 4.03 regardless of DRI beeing enabled or disabled. > > > 3 - This is the weird part: Xv is messed, the colors don't match the real > > ones, they are completely changed and there is an horizontal strip with a > > diferent color variation with xine and a lot of garbage with mplayer, X > > freezes a short time after switching to and from fullscreen (except for the > > mouse). Strangely during the time before X freezes there are no framedrops > > but they come back with dri disabled. > > > > What is exactly the relation of Xvideo and dri ? > > They are conceptually independent, however as of 4.2.0, the r128 driver > tries to take advantage of the DRM to accelerate Xv image transfer. > Unfortunately, this doesn't work well with some chips, and there are > also problems coordinating this with the new 2D acceleration yet. hmm, I had a very quick look at dri.sf.net info, and I think I read drm was 3d only and that 2d data would allways go to the X server (they have a picture :) ). Did this change ? Is drm going to be used for 2d in the future ? > > Until these issues are sorted out, use of the DRM for Xv should be an > option which defaults to off. I'll submit a patch to that effect soon. > Attached is a hack which disables it completely in source for now. I > hope this is useful for people who are bitten by this. > Well, I am looking forward to see how this problem is solved. Too bad that I am too busy get really into it, since the subject is very interesting. Thanks again Gustavo ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]A big confusion over here - XFree 4.2 - and rage 128
Hello Joe and everyone: Thanks for you answer. I want to apologize, now that I reliased that the original message appeared 3 times (I thought the first trials had failed since I wasn't a subscriber). Well, Joe, The 2D bugs I notice are in the KDM screen. KDE itself seems to work ok but I didn't test it for a very long time. The background of the KDM screen and its widgets are not refreshed as they should so the result is a complete mess. As you sugested I indeed get Feb 20 04:49:26 localhost kernel: [drm] Initialized r128 2.2.0 20010917 on minor 0 Feb 20 04:49:30 localhost kernel: [drm:r128_cce_indirect] *ERROR* process 1902 using buffer owned by 0 Feb 20 04:49:38 localhost last message repeated 104 times on my kernel logs. Process 1895 is X, process 0 is perhaps the kernel ? These messages appear when X is started, not at crash time. The crashes as I said are X server crahses not complete system crashes, the mouse survives but the clicks are not handled neither keyboard events. The crashes happen with mpeg and DVD (mpeg2) movies and don't happen with avi, maybe because of the different image formats that the codecs produce wich are mapped into different video memory areas, probably there are bugs only handling some formats. To make X crash it is enought fo move the video window around a little bit or sometimes you can just wait and it'll hang by itself. I don't have any problem switching from console to X and back. Well I can say now that the situation is as bad or worse than before, before one couldn't use bttv with dri, now one can't use video with dri and can't use kdm with dri. As I said disabling dri Xv doesn't crash anymore but exhibits the problems I complained about in the previous mail (which again appear to be DVD only) that started happening with XFree 4.1. What is exactly the relation of XV extension and dri ? (there is nothing about that in `man Xv`) Maybe I did something wrong, but all I did was upgrade X from mdk rpms and compile the drm module, as sugested at dri.sf.net. I assumed my 2.4.8 kernel would do. Is that wrong ? Thanks Gustavo Homem On Wednesday 20 February 2002 02:22, you wrote: > I'm using XF4.2+Rage128 with problems as well. > I also am happy to see xawtv+DRI work! > > I think I had some Xv problems before switching to > the current CVS, but I had bigger problems. > Text video consoles became inaccessible frequently, > and occasional 2D acceleration bugs, usually when > moving a long scrollbar. The 2D bugs > used to lockup X (KB+mouse dead). I also got > random hangs when closing a window, but then CPU > use goes to 100% and pointer is alive, so it's > a different problem. > > I did another CVS update two days ago and recompiled. > There are now no more lockups, > but VT text terminals still die frequently, > and 2D drawing bugs still happen. > > Maybe this is related to your drawing bugs. > DO you see this in your logs when DRI is enabled? > [drm:r128_cce_indirect] *ERROR* process 2865 using buffer owned by 0 > > Do you ever lose the VT text consoles? > > Joe Krahn > > Gustavo Homem wrote: > > Sorry, the first time I sent this message I wasn't subscribed so I guess > > it didn't arrive. > > > > Thanks > > Gustavo > > > > --- > > Hello everyone: > > > > I am having serious trouble with XFree. I have a rage 128 video card. I > > was using XFree 4.1 from mdk 8.1 and the Xv extension was malfunctioning > > for DVDs (was ok for other movies). It would eat too much CPU so a lot of > > frames were dropped (tested with xine, vlc and mplayer), for example xine > > would take around 45 % and the X server about 45% using Xv output. > > > > I upgraded to XFree 4.2 rpms from mandrake in hope to have this problem > > solved since it was working perfectly on XFree 4.03 from mdk 8.0. > > > > X complained then about drm modules beiing old, so I downloaded the > > latest one from dri.sf.net , compiled and instaled the module at > > /lib/modules/ > > > > The result was as follows with dri enabled: > > > > 1 - Now bttv no longer freezes the system if used with dri enabled > > (hooray) 2 - The KDM login screen is completely messed (widgets are > > garbaged, not drawn properly) > > 3 - This is the weird part: Xv is messed, the colors don't match the real > > ones, they are completely changed and there is an horizontal strip with a > > diferent color variation with xine and a lot of garbage with mplayer, X > > freezes a short time after switching to and from fullscreen (except for > > the mouse). Strangely during the time before X freezes there are no > > framedrops but they com
[Xpert]A big confusion over here - XFree 4.2 - and rage 128
-- Forwarded Message -- Subject: A big confusion over here - XFree 4.2 Date: Tue, 19 Feb 2002 06:32:05 + From: Gustavo Homem <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Hello everyone: I am having serious trouble with XFree. I have a rage 128 video card. I was using XFree 4.1 from mdk 8.1 and the Xv extension was malfunctioning for DVDs (was ok for other movies). It would eat too much CPU so a lot of frames were dropped (tested with xine, vlc and mplayer), for example xine would take around 45 % and the X server about 45% using Xv output. I upgraded to XFree 4.2 rpms from mandrake in hope to have this problem solved since it was working perfectly on XFree 4.03 from mdk 8.0. X complained then about drm modules beiing old, so I downloaded the latest one from dri.sf.net , compiled and instaled the module at /lib/modules/ The result was as follows with dri enabled: 1 - Now bttv no longer freezes the system if used with dri enabled (hooray) 2 - The KDM login screen is completely messed (widgets are garbaged, not drawn properly) 3 - This is the weird part: Xv is messed, the colors don't match the real ones, they are completely changed and there is an horizontal strip with a diferent color variation with xine and a lot of garbage with mplayer, X freezes a short time after switching to and from fullscreen (except for the mouse). Strangely during the time before X freezes there are no framedrops but they come back with dri disabled. What is exactly the relation of Xvideo and dri ? I never needed to have dri enabled to have smooth XVideo before (it wasn't even available at first), my computer has played DVDs with Xvideo since the first xine versions with gatos drivers. Did this change with XFree 4.1 ? I also don't know what is causing the 1,2,3 problems and I'd be glad if someone could help. Thanks a lot Gustavo Homem -- "O nervo óptico transmite ideias luminosas ao cérebro." --- -- "I think there is a world market for about five computers." -Thomas J. Watson (Chairman, IBM) 1943 ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]A big confusion over here - XFree 4.2
Hello everyone: I am having serious trouble with XFree. I have a rage 128 video card. I was using XFree 4.1 from mdk 8.1 and the Xv extension was malfunctioning for DVDs (was ok for other movies). It would eat too much CPU so a lot of frames were dropped (tested with xine, vlc and mplayer), for example xine would take around 45 % and the X server about 45% using Xv output. I upgraded to XFree 4.2 rpms from mandrake in hope to have this problem solved since it was working perfectly on XFree 4.03 from mdk 8.0. X complained then about drm modules beiing old, so I downloaded the latest one from dri.sf.net , compiled and instaled the module at /lib/modules/ The result was as follows with dri enabled: 1 - Now bttv no longer freezes the system if used with dri enabled (hooray) 2 - The KDM login screen is completely messed (widgets are garbaged, not drawn properly) 3 - This is the weird part: Xv is messed, the colors don't match the real ones, they are completely changed and there is an horizontal strip with a diferent color variation with xine and a lot of garbage with mplayer, X freezes a short time after switching to and from fullscreen (except for the mouse). Strangely during the time before X freezes there are no framedrops but they come back with dri disabled. What is exactly the relation of Xvideo and dri ? I never needed to have dri enabled to have smooth XVideo before (it wasn't even available at first), my computer has played DVDs with Xvideo since the first xine versions with gatos drivers. Did this change with XFree 4.1 ? I also don't know what is causing the 1,2,3 problems and I'd be glad if someone could help. Thanks a lot Gustavo Homem -- "O nervo óptico transmite ideias luminosas ao cérebro." ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]A big confusion over here - XFree 4.2 - and rage 128
Sorry, the first time I sent this message I wasn't subscribed so I guess it didn't arrive. Thanks Gustavo --- Hello everyone: I am having serious trouble with XFree. I have a rage 128 video card. I was using XFree 4.1 from mdk 8.1 and the Xv extension was malfunctioning for DVDs (was ok for other movies). It would eat too much CPU so a lot of frames were dropped (tested with xine, vlc and mplayer), for example xine would take around 45 % and the X server about 45% using Xv output. I upgraded to XFree 4.2 rpms from mandrake in hope to have this problem solved since it was working perfectly on XFree 4.03 from mdk 8.0. X complained then about drm modules beiing old, so I downloaded the latest one from dri.sf.net , compiled and instaled the module at /lib/modules/ The result was as follows with dri enabled: 1 - Now bttv no longer freezes the system if used with dri enabled (hooray) 2 - The KDM login screen is completely messed (widgets are garbaged, not drawn properly) 3 - This is the weird part: Xv is messed, the colors don't match the real ones, they are completely changed and there is an horizontal strip with a diferent color variation with xine and a lot of garbage with mplayer, X freezes a short time after switching to and from fullscreen (except for the mouse). Strangely during the time before X freezes there are no framedrops but they come back with dri disabled. What is exactly the relation of Xvideo and dri ? I never needed to have dri enabled to have smooth XVideo before (it wasn't even available at first), my computer has played DVDs with Xvideo since the first xine versions with gatos drivers. Did this change with XFree 4.1 ? I also don't know what is causing the 1,2,3 problems and I'd be glad if someone could help. Thanks a lot Gustavo Homem -- "Na Grécia, a democracia funcionava muito bem porque os que não estavam de acordo envenenavam-se." ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Two ways to framebuffer
Hello Michel: Thank you very much for your answeer. So from what I read from you I would say that for an installer it would be better to use the old XF86_FBDev since one does not need in this case to use the new fancy features and from your words we get the impressions that the old one could even run on some exotic video cards, right ? Thanks again Gustavo 2+2=5 for extremely large values of 2 .-``'. I.S.T - Instituto Superior Tecnico .` .`~ _.-' '._ Licenciatura em Engenharia Fisica e Tecnologica [EMAIL PROTECTED] http://mega.ist.utl.pt/~gach On Fri, 21 Sep 2001, Michel [iso-8859-1] Dänzer wrote: > Gustavo Carvalho Homem wrote: > > > One thing I can't find in the documentation. Are there advantages (or > > disadvantages) of using XF86_FBDev over XFree86 4.1 with fbdev driver ? Any > > other relevant comments ? > > The big disadvantage is that XF86_FBDev is ooold and lacks a lot of features > like shadow framebuffer, RENDER extension, ... > > The only possible advantages I see are for exotic cases like 1 or 4 bit depth > which might be broken in the 4.x fbdev driver (but should be easy to fix) and > that maybe XF86_FBDev offers some acceleration for some chipsets, but I'm not > even sure there. > > > -- > 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]Re: Two ways to framebuffer
Hi Peter: > > On Thu, Sep 20, 2001 at 11:16:29PM +0100, Gustavo Carvalho Homem wrote: > > Hello all: > hi. > > > One thing I can't find in the documentation. Are there advantages (or > > disadvantages) of using XF86_FBDev over XFree86 4.1 with fbdev driver ? > I only see an advantage for situations where Xserver is missing for your card > but there is a fbdev driver for kernel. If there is no fbdev driver for the > card for the kernel, it is better to use Xfree's vesa driver, because it is > slightly faster than vesafb+fbdev and also can do DGA. > What I was really trying to ask was some comparison between the old XF86_FBDev 3.3.6 frame buffer XServer and the new XFree 4.1 using fbdev driver X server, i.e., a comparison between two framebuffer based XServers and not between the solutions and specific drivers. The reason is I am looking for the most general XServer, the one that will work with more cards, and from what I see the Vesa 1.2 cards are not supported by any framebuffer server, but the Vesa 2.0 ones should be.But still comes the doubt about wich one to use. (seems to be a rule of thumb to use framebuffer XServers in the installer, see Suse, Mandrake, Red Hat for instance). Without further information I'd say it shoud be logical to choose the newer release but I see all the distros using the old one. > > > Any other relevant comments ? > If there is a driver for your card for Xf86, forget it. We don't want to detect/configure the whole X for the installation neither does the user wan't to see that, and you know that it can sometimes be tricky. > > > Thank you very much > > Gustavo Homem > Bye, > Gustavo 2+2=5 for extremely large values of 2 .-``'. I.S.T - Instituto Superior Tecnico .` .`~ _.-' '._ Licenciatura em Engenharia Fisica e Tecnologica [EMAIL PROTECTED] http://mega.ist.utl.pt/~gach ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Two ways to framebuffer
-- Forwarded message -- Date: Fri, 21 Sep 2001 15:07:57 +0200 From: "Michel [iso-8859-1] Dänzer" <[EMAIL PROTECTED]> To: Gustavo Carvalho Homem <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED] Subject: Re: [Xpert]Two ways to framebuffer Gustavo Carvalho Homem wrote: > One thing I can't find in the documentation. Are there advantages (or > disadvantages) of using XF86_FBDev over XFree86 4.1 with fbdev driver ? Any > other relevant comments ? The big disadvantage is that XF86_FBDev is ooold and lacks a lot of features like shadow framebuffer, RENDER extension, ... The only possible advantages I see are for exotic cases like 1 or 4 bit depth which might be broken in the 4.x fbdev driver (but should be easy to fix) and that maybe XF86_FBDev offers some acceleration for some chipsets, but I'm not even sure there. -- 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]Two ways to framebuffer
Hello all: One thing I can't find in the documentation. Are there advantages (or disadvantages) of using XF86_FBDev over XFree86 4.1 with fbdev driver ? Any other relevant comments ? Thank you very much Gustavo Homem --- ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Xv card list and Vesa 2.0 compliance
Hello all ! I can't find a list XVideo capable XFree86 drivers . The one I have was built from xine users feedback. Can someone comment , add entries or say something about future plans ? This is my list: 3dfx Voodoo3 (xfree 4.1) Voodoo4 (xfree 4.1) Voodoo5 (xfree 4.1) Nvidia ( xfree 4.1 ) TNT TNT2 TNT2 Ultra TNT2 Pro GeForce SDR GeForce DDR GeForce 2 GTS GeForce 2 MX GeForce 2 MX Dualhead GeForce 2 Pro GeForce 2 Ultra GeForce 3 Ati ( XFree 4.1 - see also GATOS http://www.linuxvideo.org/gatos ) Mach64 Rage 128 Radeon Matrox (xfree 4.xx ) - see also http://www.matrox.com/mga/support/drivers/latest/home.cfm G200 G400 G450 (xfree 4.1) Intel (xfree 4.xx ) i810 i815 S3 Savage ( XFree 4.1, see also http://www.probo.com/timr/savage40.html ) I also don't know where to find a vesa 2.0 compliante cards list. Can someone point me to it ? (the Vesa site doesn't list anything) Thank you very much Gustavo Homem --- ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
