Re: [XFree86] Hardware mouse cursor visual glitches
- Original Message - From: Marc Aurele La France <[EMAIL PROTECTED]> Date: Thu, 13 Feb 2003 16:12:43 -0700 (MST) To: <[EMAIL PROTECTED]> Subject: Re: [XFree86] Hardware mouse cursor visual glitches > On Thu, 13 Feb 2003, Felipe Alfaro Solana wrote: > > > Do you know what CVS/snapshot version will integrate your fix? > > I'm currently using the XFree86 packages from RedHat Rawhide, > > to be exact, those from 2003-02-11... I can't wait for the fixes :-) > > I don't do rpm's. So I can't answer your question. I was talking about when the fix would be integrated into the XFree86 CVS tree. Anyways, I have received a response from a RedHat engineer and said an RPM package with your fix should be available in 12 hours. Thanks! Felipe -- __ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Hardware mouse cursor visual glitches
- Original Message - From: Marc Aurele La France <[EMAIL PROTECTED]> Date: Thu, 13 Feb 2003 16:12:43 -0700 (MST) To: <[EMAIL PROTECTED]> Subject: Re: [XFree86] Hardware mouse cursor visual glitches > On Thu, 13 Feb 2003, Felipe Alfaro Solana wrote: > > > Do you know what CVS/snapshot version will integrate your fix? > > I'm currently using the XFree86 packages from RedHat Rawhide, > > to be exact, those from 2003-02-11... I can't wait for the fixes :-) > > I don't do rpm's. So I can't answer your question. I was talking about when the fix would be integrated into the XFree86 CVS tree. Anyways, I have received a response from a RedHat engineer and said an RPM package with your fix should be available in 12 hours. Thanks! Felipe -- __ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] do ANY PCI video cards work in XFree86?
>>> [EMAIL PROTECTED] 14.02.03 03:13 >>> > I've tried the NVidia PCI TNT2 M64 > I've tried the PCI ATI Rage 128 > Both give this error to XFree86 -configure: > appropriate data has not been added to xf86PciInfo.h > I'll go out and buy yet another PCI video card if I knew it would work. > But since both of these were on the compatible list, I'm wondering... > Do ANY PCI video cards work in XFree86? > Anyone? I don't think the problem here is PCI or not PCI, but I would just like to conferm that PCI cards do indeed work. I've successfully used the STB Symmetric GLyder TX Gold and the Diamond Fire GL 1000 Pro. Both of these are older cards and I suppose hard to come by these days. Of the more up-to date PCI cards, I've seen some references to successfull uses of the ATI Radeon 32MB SDR. If there are others, I would be very interested to hear about them as well. - IT ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] support for gvx1 cards
>>> [EMAIL PROTECTED] 13.02.03 22:34 >>> > Any support for 3D labs gvx1 cards in 4.3.0? Am I to understand it doens't work in 4.2? The GVX1 uses the GLINT R3 processor as its' rasterizer. Altough I don't see "r3" in the GLINT manual, you might try listing the Gamma 1 processor of the GVX1 in the device section (chipset "gamma") of your configuration file and then take a look at the log file to see if X auto probes and attaches the R3 anyway. Failing that, what about trying to list it as a "pm3" or "pm4"? I've heard somewhere that the GLINT R3 might be passed off as a Permedia 3 in some situations. Failing that again, you wouldn't have access to a GVX1 Pro, would you? I do the see both the "r4" and "gamma2" listed in the GLINT manual. - IT ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Linux 8.0
On Thu, 13 Feb 2003 @ 1:40am (-0800), Brian C. Dilley wrote: BCD> wtf? yer watching this? ok... SUCK MAH BALLS :-D BCD> BCD> On Wednesday 12 February 2003 09:09 pm, Daniel Stone wrote: ...let's keep it clean and semi-professional, please. -lava ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: Does XFree86-4.2.1 support GB18030.2000?
On Thu, 13 Feb 2003, Dr Andrew C Aitchison wrote: >> I have a question that does XFree86-4.2.1 support GB18030.2000,the new >> Chinese Standard?TurboLinux has released a patch for XFree86-4.2.0.You >> caould find it here: >> http://pkgcvs.turbolinux.co.jp/cgi-bin/cvsweb.cgi/XFree86/4.2.0/?hideattic=0 > >There are very few changes between XFree86 4.2.0 and 4.2.1, >so I would be suprised if GB18030.2000 was added. >I wasn't paying much attention, but I think that GB18030.2000 has been >discussed on [EMAIL PROTECTED] Try googling for archives of that list, >and if that fails ask them whether that encoding made it into current CVS, >in which case it will be available in XFree86 v4.3. Red Hat Linux contains GB18030.2000 support, which was written by Yu Shao <[EMAIL PROTECTED]> and possibly others (I don't know the details). Anyone is free to use our patches under the XFree86 MIT style license if they wish. In case someone wonders why they are not submitted to XFree86.org for inclusion, I wont submit them to XFree86.org personally because I did not write them myself, and it is outside of the areas of XFree86 to which I am familiar with. Someone who is familiar with these areas, and with GB18030 might want to review them possibly however to determine if they are XFree86 CVS worthy or not. Hope this helps, TTYL -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
re[2]: [XFree86] Linux 8.0:wq
On Thu, 13 Feb 2003 @ 4:15pm (-0800), Mindy Truitt wrote:
MT> I tried to run '# XFree86 -configure' But was presented with the error:
MT>
MT> Using config file: "/root/XF86Config.new"
MT> Number of created screens does not match number of detected devices.
MT> Configuration failed.
MT>
MT> Then running '# XFree -xf86config /root/XFConfig.new' was presented with the
error:
MT>
MT> -bash: XFree: command not found
That would be:
# XFree86 -xf86config /root/XFConfig.new
...UNIX is /very/ case sensitive. Try using tab complete: Type XFree[tab key]
MT>
MT> Then running '# egrep -i.WW|EE. /var/log/*' was presented with the error:
MT>
the proper syntax is verbatim:
egrep -i "WW|EE" /var/log/X*
...sorry if there was any confusion ... copy/paste the output into a reply
MT> -bash: EE.: command not found
MT> grep: invalid option -- .
MT> Usage: grep [OPTION] ... PATTERN[FILE] ...
MT> Try 'grep --help' for more information.
MT>
MT> After trying grep help I still was unable to locate the file /var/log/*
MT>
MT> # uname -a
MT> Linux localhost.localdomain 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686
i386 GNU/Linux
MT>
MT> # scanpci
MT> pci bus 0x0011 carum 0x0d function 0x00: vendor 0x5333 device 0x88f0 S3 968
MT> ... 0x0e ...
MT> ... 0x0f ...
MT> ... 0x10 ...
MT> ... 0x11 ...
MT> ... 0x12 ...
MT> ... 0x13 ...
MT> ... 0x14 ...
...we need to see the complete output, try this:
scanpci 2>&1 | sendmail [EMAIL PROTECTED]
MT>
MT> # XFree86 -keeptty -verbose 9 -xf86config /root/XF86Config.new
MT> (II) SIS(0): XR3F Contents - 00
MT> Fatal server error:
MT> Caught signal 8. Server aborting
MT>
MT> # X86Config
MT> Command not found
MT>
MT> # /var/log/X*
MT> -bash: /var/log/XFree86.0.log: Permission denied
MT> Do you know why the permission would be denied? I am on the root account with the
root password.
..no no, I want you to include a copy in your email to me and the list.
probably the best way for you to get them to yourself is
cat /var/log/X* | sendmail [EMAIL PROTECTED]
hopefully DNS and networking are operational enough for you to mail yourself the
logs.
...happy v-day,
-Brian
MT>
MT> Thanks
MT> Mindy Truitt
MT> AVI Systems
MT> (952) 949-6053
MT>
later - | _BonaFide[] = { coder, author, | /~\ The ASCII Ribbon
Brian A. Seklecki | problem solver, scholar, BOFH, | \ / Campaign Against
| vegetarian, runner, NetBSD | X Exchange, Outlook
| advocate, spiritual machine }; | / \ & HTML Email
PGP: E7B2 5A30 0F61 2ECD AF34 7E88 CC30 8B95 EE0B 4D5C
"From listening comes wisdom and from speaking repentance."
___
XFree86 mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: Re: Security in new drivers
On Thu, 13 Feb 2003, Aidan Kehoe wrote: >Date: Thu, 13 Feb 2003 08:44:09 + >From: Aidan Kehoe <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Reply-To: [EMAIL PROTECTED] >Content-Type: text/plain; charset=iso-8859-15 >Subject: Re: Re: Security in new drivers > > Ar an 12ú lá de mí 2, scríobh Mike A. Harris : > > > Anything short of a specific example of a real security problem > > is nothing more than heresy. > >Don't get all dogmatic about it, Mike :-) . Sorry, but I believe someone making claims of something being insecure, should do so with specific examples, or else their claims do not hold any water. There are implications that if their claim is true, and there are security problems that are known, that the developers do not seem to care about them, or else they would logically be fixed by now, and thus there would be no security problems. The developers of XFree86 drivers, including DRI/DRM are very security concious however, and any security problems that have been found in DRI/DRM and made known, have been addressed rather promptly. I think it would be rather insulting to these developers to insinuate that their are security holes in the code that they have known about, and have purposefully ignored. And if there are security holes in the code that they did not know about, then I'm sure that they would be greatful for someone who knows about them to tell them about these holes so they can be fixed. You can call me dogmatic if you like, but I just don't like seeing these kind of rumors go around, without setting things straight. If nobody sets the record straight, then before we know it, there is a huge rumor created out of the small rumor, and XFree86 and DRI get a bad rap for being insecure even though there are no actual true claims that have come forth to support that rumor. I will make no claims that there are NOT security holes, but I certainly do not know of any currently. If someone else knows of a real security hole, or holes in DRI/DRM, or in XFree86 that is non-hypothetical, please step forward and tell the developers what the problem is, so it can be addressed promptly. But please don't spread unfounded rumors about security issues. -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] installation problem
Hi System : Intel 1.7 GHz Chipset : Intel 845 GLAD VGA : Intel Extreme 32MB(built in chipset) RAM : 128 MB Monitor : philips 104E Linux : RedHat 8.0 My VGA does get detected, but the monitor is NOT probed by linux. I have installed linux 8.0, but after installation the graphical user interface will not work. Some distorted images do show and screen flickers a few times but then it stops at the text prompt. when i enter root and password it remains at text prompt. when i enter the command "STARTX" it states error "NO screen found". I took my hard disk to a friends house he has a 1.13 GHZ intel 815 chipset, and linux did run perfectly there. Error is that "NO screens found". Error messages are in log file mentioned. If you need the log file how do i access it to send to you. Please reply and help me. I have been waiting for a long time to run linux. Amir Rafiq. _ MSN 8 helps eliminate e-mail viruses. Get 2 months FREE*. http://join.msn.com/?page=features/virus ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] do ANY PCI video cards work in XFree86?
I've tried the NVidia PCI TNT2 M64 I've tried the PCI ATI Rage 128 Both give this error to XFree86 -configure: appropriate data has not been added to xf86PciInfo.h I'll go out and buy yet another PCI video card if I knew it would work. But since both of these were on the compatible list, I'm wondering... Do ANY PCI video cards work in XFree86? Anyone? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] NVidia PCI TNT2 M64 HELP PLEASE RESPOND
Hi all Does anyone please know anything about the problems with XFree86 and this card? Some feedback would be appreciated . David - Original Message - From: "vizion communication" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, February 13, 2003 7:13 AM Subject: Re: [XFree86] [XFree86(TM) Bug Report] NVidia Riva TNT2 M64 - appropriate data has not been added to xf86PciInfo.h > I am also having trouble trying to GET Xserver running with > this PCI card on a Compaq Proliant 5500 and am reaching a > point of despair!!! > > Could someone on the development team please advise > > David > - Original Message - > From: "BSD Baby" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Wednesday, February 12, 2003 11:27 PM > Subject: [XFree86] [XFree86(TM) Bug Report] NVidia Riva TNT2 > M64 - appropriate data has not been added to xf86PciInfo.h > > > > Regarding: NVidia Riva TNT2 M64 - appropriate data has not > been added to xf86PciInfo.h > > Email: [EMAIL PROTECTED] > > -- > -- > > XFree86 Version: 4.2.1 > > > > OS: FreeBSD 4.7-RELEASE i386 > > > > Area: Xserver > > > > Server: XFree86 (The XFree86 4.x server) > > > > Video Card: > > > > pci bus 0x cardnum 0x0c function 0x00: vendor 0x10de > device 0x002d > > NVidia Riva TNT2 M64 > > STATUS0x02b0 COMMAND 0x0007 > > CLASS 0x03 0x00 0x00 REVISION 0x15 > > BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00 > > BASE0 0xde00 addr 0xde00 MEM > > BASE1 0xdc08 addr 0xdc00 MEM PREFETCHABLE > > MAX_LAT 0x01 MIN_GNT 0x05 INT_PIN 0x01 INT_LINE > 0x0a > > > > > > Description: > > > > XFree86 Version 4.2.1 / X Window System > > (protocol Version 11, revision 0, vendor release 6600) > > Release Date: 3 September 2002 > > 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/) > > Build Operating System: FreeBSD 4.7-RELEASE i386 [ELF] > > Module Loader present > > Markers: (--) probed, (**) from config file, (==) default > setting, > > (++) from command line, (!!) notice, (II) > informational, > > (WW) warning, (EE) error, (NI) not implemented, > (??) unknown. > > (==) Log file: "/var/log/XFree86.0.log", Time: Wed Feb 12 > 23:16:43 2003 > > (--) Using syscons driver with X support (version 2.0) > > (--) using VT number 9 > > > > (II) Module ABI versions: > > XFree86 ANSI C Emulation: 0.1 > > XFree86 Video Driver: 0.5 > > XFree86 XInput driver : 0.3 > > XFree86 Server Extension : 0.1 > > XFree86 Font Renderer : 0.3 > > (II) Loader running on freebsd > > (II) LoadModule: "bitmap" > > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > > (II) Module bitmap: vendor="The XFree86 Project" > > compiled for 4.2.1, module version = 1.0.0 > > Module class: XFree86 Font Renderer > > ABI class: XFree86 Font Renderer, version 0.3 > > (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.2.1, module version = 0.1.0 > > ABI class: XFree86 Video Driver, version 0.5 > > (II) PCI: Probing config type using method 1 > > (II) PCI: Config type is 1 > > (II) PCI: stages = 0x03, oldVal1 = 0x0cf8, mode1Res1 = > 0x0cf8 > > (II) PCI: PCI scan (all values are in hex) > > (II) PCI: 00:00:0: chip 1039,0740 card 1039,0740 rev 01 > class 06,00,00 hdr 80 > > (II) PCI: 00:01:0: chip 1039,0001 card , rev 00 > class 06,04,00 hdr 01 > > (II) PCI: 00:02:0: chip 1039,0008 card , rev 00 > class 06,01,00 hdr 80 > > (II) PCI: 00:02:5: chip 1039,5513 card 1039,5513 rev d0 > class 01,01,80 hdr 80 > > (II) PCI: 00:0a:0: chip 13f6,0111 card 1297,f440 rev 10 > class 04,01,00 hdr 00 > > (II) PCI: 00:0b:0: chip 8086,1229 card 8086,0001 rev 02 > class 02,00,00 hdr 00 > > (II) PCI: 00:0c:0: chip 10de,002d card , rev 15 > class 03,00,00 hdr 00 > > (II) PCI: 00:0f:0: chip 10ec,8139 card 10ec,8139 rev 10 > class 02,00,00 hdr 00 > > (II) PCI: 00:10:0: chip 11c1,5811 card 1297,f024 rev 04 > class 0c,00,10 hdr 00 > > (II) PCI: 01:00:0: chip 1039,6325 card 1039,6325 rev 00 > class 03,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.2.1, module version = 0.1.0 > > ABI class: XFree86 Video Driver, version 0.5 > > (II) UnloadModule: "scanpci" > > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > > (II) Host-to-PCI bridge: > > (II) PCI-to-ISA bridge: > > (II) PCI-to-PCI bridge: > > (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 > (VGA_EN is set) > > (II) Bus 0 I/
Re: [XFree86] Hardware mouse cursor visual glitches
Around 1 o'clock on Feb 14, Michel =?ISO-8859-1?Q?D=E4nzer?= wrote: > This patch still actually disables the cursor instead of only making it > fully transparent, is that really an issue? Yes, the issue is that disabling and enabling the cursor causes "glitches" on the screen, while erasing the image to transparent does not. That's what Marc's fix does for all of the ATI chipsets. -keith ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Hardware mouse cursor visual glitches
Around 16 o'clock on Feb 13, Marc Aurele La France wrote: > > Daniel Stone built a patch, and I hacked it a bit. Taking that along with > > Marc's idea of disabling cursors by turning them transparent should leave > > us with Radeon cursor support that doesn't have any issues with mode > > switching. > > > Would such a patch make sense for 4.3? > > Well, would such a patch essentially force software cursors for the > majority of hardware that doesn't support ARGB cursors? No, this patch is Radeon specific; it just uses the ARGB hardware for all cursors instead of switching back and forth between 2-bit and 32-bit cursors. The core->ARGB conversion is done within the Radeon cursor code in a tiny loop. A future extension could push this conversion into the cursor code permitting any ARGB-capable hardware of easily doing the same thing. -keith ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Hardware mouse cursor visual glitches
On Don, 2003-02-13 at 22:54, Keith Packard wrote:
> Around 13 o'clock on Feb 13, Marc Aurele La France wrote:
>
> > The problem was that the switching back-and-forth between the new "cutesy"
> > cursors and the standard ones tickles a hardware bug in Mach64, Rage 128
> > and Radeon variants.
>
> The Radeon is slightly different in that it has hardware support for ARGB
> cursors, hence switching on that chip is different.
>
> I suggested that one fix for this is to simply always use the ARGB style
> hardware cursors and map core cursors to that model, rather than
> attempting to switch back and forth.
>
> Daniel Stone built a patch, and I hacked it a bit.
Fredrik Höglund (CC'd in case he's not subscribed here) has also written
such a patch, and I've fixed it for big endian machines. The result is
attached.
> Taking that along with Marc's idea of disabling cursors by turning them
> transparent should leave us with Radeon cursor support that doesn't have
> any issues with mode switching.
This patch still actually disables the cursor instead of only making it
fully transparent, is that really an issue?
> Would such a patch make sense for 4.3?
IMHO yes, the question is if Kevin agrees and if he'll make it.
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
Index: radeon_cursor.c
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_cursor.c,v
retrieving revision 1.20
diff -p -u -r1.20 radeon_cursor.c
--- radeon_cursor.c 2003/01/29 18:06:06 1.20
+++ radeon_cursor.c 2003/02/09 01:25:15
@@ -52,22 +52,56 @@
/* X and server generic header files */
#include "xf86.h"
+#define WIDTH 64
+#define HEIGHT 64
+/* Mono ARGB cursor colors (premultiplied) */
+static const CARD32 color[] = {
+ 0x, /* White, fully transparent */
+ 0x, /* Black, fully transparent */
+ 0x, /* White, fully opaque */
+ 0xff00, /* Black, fully opaque */
+};
+
/* Set cursor foreground and background colors */
static void RADEONSetCursorColors(ScrnInfoPtr pScrn, int bg, int fg)
{
RADEONInfoPtr info = RADEONPTR(pScrn);
+CARD32*pixels = (CARD32 *)(pointer)(info->FB + info->cursor_start);
+CARD32 pixel, i;
+#if X_BYTE_ORDER == X_BIG_ENDIAN
unsigned char *RADEONMMIO = info->MMIO;
+CARD32 surface_cntl = INREG(RADEON_SURFACE_CNTL);
+#endif
-if (info->IsSecondary || info->Clone) {
- OUTREG(RADEON_CUR2_CLR0, bg);
- OUTREG(RADEON_CUR2_CLR1, fg);
-}
+#ifdef ARGB_CURSOR
+/* Don't recolor cursors set with SetCursorARGB. */
+if (info->cursor_argb)
+ return;
+#endif
-if (!info->IsSecondary) {
- OUTREG(RADEON_CUR_CLR0, bg);
- OUTREG(RADEON_CUR_CLR1, fg);
-}
+/* Don't recolor the image if we don't have to */
+if (bg == 0x00ff && fg == 0)
+ return;
+
+#if X_BYTE_ORDER == X_BIG_ENDIAN
+OUTREG(RADEON_SURFACE_CNTL, (surface_cntl | RADEON_NONSURF_AP0_SWP_32BPP)
+& ~RADEON_NONSURF_AP0_SWP_16BPP );
+#endif
+
+/* Note: We assume that the pixels are either fully opaque or fully
+ * transparent so we won't premultiply them. We also know that
+ * the image is black & white since LoadCursorImage is called
+ * before SetCursorColors.
+ */
+for (i = 0; i < WIDTH * HEIGHT; i++, pixels++)
+ if ((pixel = *pixels))
+ *pixels = (pixel & 0x00ff ? bg : fg) | 0xff00;
+
+#if X_BYTE_ORDER == X_BIG_ENDIAN
+/* restore byte swapping */
+OUTREG(RADEON_SURFACE_CNTL, surface_cntl);
+#endif
}
@@ -78,23 +112,19 @@ static void RADEONSetCursorPosition(Scrn
{
RADEONInfoPtr info = RADEONPTR(pScrn);
unsigned char *RADEONMMIO = info->MMIO;
-xf86CursorInfoPtr cursor = info->cursor;
intxorigin= 0;
intyorigin= 0;
inttotal_y= pScrn->frameY1 - pScrn->frameY0;
intX2 = pScrn->frameX0 + x;
intY2 = pScrn->frameY0 + y;
-int stride = 16;
+int stride = 256;
-#ifdef ARGB_CURSOR
-if (info->cursor_argb) stride = 256;
-#endif
if (x < 0)xorigin = -x+1;
if (y < 0)yorigin = -y+1;
if (y > total_y) y = total_y;
if (info->Flags & V_DBLSCAN) y *= 2;
-if (xorigin >= cursor->MaxWidth) xorigin = cursor->MaxWidth - 1;
-if (yorigin >= cursor->MaxHeight) yorigin = cursor->MaxHeight - 1;
+if (xorigin >= WIDTH) xorigin = WIDTH - 1;
+if (yorigin >= HEIGHT)yorigin = HEIGHT - 1;
if (info->Clone) {
int X0 = 0;
@@ -171,8 +201,8 @@ static void RADEONSetCursorPosition(Scrn
yorigin = 0;
if (X2 < 0) xorigin = -X2 + 1;
if (Y2 < 0) yorigin = -Y2 + 1;
- if (xorigin >= cursor->MaxWidth
Re: [XFree86] Hardware mouse cursor visual glitches
On Thu, 13 Feb 2003, Felipe Alfaro Solana wrote: > > > > Yes. This a known issue. I've started looking into this, but > > > > have so far been unable to duplicate the problem. I'll keep > > > > trying. With any luck, this'll be fixed in 4.3. > > > OK, Marc... Please, don't hesitate to contact with me for anything > > > you need: patching, latest CVS, testing scenarios, hardware > > > description... Whatever! :-) > > You can go for "b)", after cvsup has had a chance to catch up with > > what I've just committed to fix this. > > The problem was that the switching back-and-forth between the new > > "cutesy" cursors and the standard ones tickles a hardware bug in > > Mach64, Rage 128 and Radeon variants. > Those are good notices :-) > Do you know what CVS/snapshot version will integrate your fix? > I'm currently using the XFree86 packages from RedHat Rawhide, > to be exact, those from 2003-02-11... I can't wait for the fixes :-) I don't do rpm's. So I can't answer your question. 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. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Hardware mouse cursor visual glitches
On Thu, 13 Feb 2003, Keith Packard wrote: > > The problem was that the switching back-and-forth between the new "cutesy" > > cursors and the standard ones tickles a hardware bug in Mach64, Rage 128 > > and Radeon variants. > The Radeon is slightly different in that it has hardware support for ARGB > cursors, hence switching on that chip is different. > I suggested that one fix for this is to simply always use the ARGB style > hardware cursors and map core cursors to that model, rather than > attempting to switch back and forth. > Daniel Stone built a patch, and I hacked it a bit. Taking that along with > Marc's idea of disabling cursors by turning them transparent should leave > us with Radeon cursor support that doesn't have any issues with mode > switching. > Would such a patch make sense for 4.3? Well, would such a patch essentially force software cursors for the majority of hardware that doesn't support ARGB cursors? Currently, only the ramdac module knows the difference between hardware and software cursors, but it seems to me you'd need a hook in Render to convert the core cursors to ARGB. That kind of interface could get ugly. I think it's best to leave something like this until after 4.3. 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. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] bjr
Vous pouvez employer le driver "siliconmotion" qui est déjà inclus avec X. On Thu, 2003-02-13 at 09:57, [EMAIL PROTECTED] wrote: > je suis novice en informatique, je recherche un driver pour une carte > graphique > Silicon Motion LynxEM version 5.1.20001.0 en date du 06/06/2001 > merci ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] no cirrus chipset
I have a compaq LTE5000 laptop which has a Cirrus clgd7543 chipset which is not listed in the Cirrus list. Perhaps I can use a compatible chipset as I have had no problems with Mandrake 7.1. My new installation is Slackware 8.1, kernel 2.4.18. I suspect this is my only problem. Bill Eyles at [EMAIL PROTECTED] XFREE86.0 Description: Binary data
Re: [XFree86] Savage 3D Problem on Red Hat 7.0
On Thu, 13 Feb 2003, Roger Daniel F Ferreira wrote: >Hi, > >After have installed Red Hat 7.0 on a Pentium Machine I've faced a >strange problem regarding the screen. > >Every time I move some window or even some widget inside a window, I >get a completelly messed screen. To fix everything, I need to to a >manual refresh using an option on a popup menu of the desktop >environment. > > >I don't know if may be something regarding the BIOS setup or the viceo >card itself. > >On Windows 98 everything works fine, at least so far. > >My video card driver was detected as being a S3 Inc I86c794 [Savage >3D]. My monitor was detected as being a SAM1055 (Samsung SyncMaster >550b). > >I've searched in your site (http://www.faqs.org/faqs/x-faq/xfree86/) >without success. Did you try installing the latest savage drivers from http://www.probo.com/timr/savage40.html ? There's a link to that on the front page of the XFree86 website along with other "Member maintained websites" in the "Documentation" link off the front page. HTH, Oisin Feeley ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] drivers
I am looking to download a driver for my video card s3 virge-dx/gx pci 375/385 so i can change my resolution...thank you pleas let me know if i can dowload a driver.
Re: [XFree86] Hardware mouse cursor visual glitches
Around 13 o'clock on Feb 13, Marc Aurele La France wrote: > The problem was that the switching back-and-forth between the new "cutesy" > cursors and the standard ones tickles a hardware bug in Mach64, Rage 128 > and Radeon variants. The Radeon is slightly different in that it has hardware support for ARGB cursors, hence switching on that chip is different. I suggested that one fix for this is to simply always use the ARGB style hardware cursors and map core cursors to that model, rather than attempting to switch back and forth. Daniel Stone built a patch, and I hacked it a bit. Taking that along with Marc's idea of disabling cursors by turning them transparent should leave us with Radeon cursor support that doesn't have any issues with mode switching. Would such a patch make sense for 4.3? -keith ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] support for gvx1 cards
Hi, Any support for 3D labs gvx1 cards in 4.3.0? -Mel ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Hardware mouse cursor visual glitches
- Original Message - From: Marc Aurele La France <[EMAIL PROTECTED]> Date: Thu, 13 Feb 2003 13:41:30 -0700 (MST) To: <[EMAIL PROTECTED]> Subject: Re: [XFree86] Hardware mouse cursor visual glitches > On Wed, 12 Feb 2003, Felipe Alfaro Solana wrote: > > > > Yes. This a known issue. I've started looking into this, but > > > have so far been unable to duplicate the problem. I'll keep > > > trying. With any luck, this'll be fixed in 4.3. > > > OK, Marc... Please, don't hesitate to contact with me for anything > > you need: patching, latest CVS, testing scenarios, hardware > > description... Whatever! :-) > > You can go for "b)", after cvsup has had a chance to catch up with > what I've just committed to fix this. > > The problem was that the switching back-and-forth between the new > "cutesy" cursors and the standard ones tickles a hardware bug in > Mach64, Rage 128 and Radeon variants. Those are good notices :-) Do you know what CVS/snapshot version will integrate your fix? I'm currently using the XFree86 packages from RedHat Rawhide, to be exact, those from 2003-02-11... I can't wait for the fixes :-) Thanks! Felipe -- __ http://www.linuxmail.org/ Now with e-mail forwarding for only US$5.95/yr Powered by Outblaze ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Installing
These might help. Good luck. How to use RPM http://www.redhat.com/docs/manuals/linux/RHL-7-Manual/ref-guide/s1-rpm-using .html Install instructions http://www.xfree.org/4.2.1/Install.html Cyn ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Hardware mouse cursor visual glitches
On Wed, 12 Feb 2003, Felipe Alfaro Solana wrote: > > > I have a laptop with an ATI RAGE Mobility M1 AGP 8MB video card > > > (Mach64-based) which is running Red Hat Phoebe2 beta distro (8.0.93), > > > based on XFree86 4.2.99.901 latest snapshot (Feb, 6th 2003). > > > I'm experiencing hardware mouse cursor visual glitches when the mouse > > > cursor shape is changed from, let's say, the standard black arrow > > > pointer, to another one, for example, the north-south, or west-east > > > resize arrow. When the mouse cursor shape is being changed, for a brief > > > period of time, I can see a 64x64 rectangle full of garbage instead of > > > the mouse cursor. After this brief lapse of time, the cursor returns to > > > its normal appearance automatically. > > Yes. This a known issue. I've started looking into this, but have so far > > been unable to duplicate the problem. I'll keep trying. With any luck, > > this'll be fixed in 4.3. > OK, Marc... Please, don't hesitate to contact with me for anything you > need: patching, latest CVS, testing scenarios, hardware description... > Whatever! :-) You can go for "b)", after cvsup has had a chance to catch up with what I've just committed to fix this. The problem was that the switching back-and-forth between the new "cutesy" cursors and the standard ones tickles a hardware bug in Mach64, Rage 128 and Radeon variants. Marc. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] Right-click popup menu in NEdit triggers the XFree86 DPMS screensaver
Regarding: Right-click popup menu in NEdit triggers the XFree86 DPMS screensaver Email: [EMAIL PROTECTED] XFree86 Version: 4.2.0 (Red Hat Linux release: 4.2.0-72) OS: RedHat 8.0, Linux kernel 2.4.18-18.8.0smp (RedHat Kernel) Area: Xserver? Server: XFree86 (The XFree86 4.x server) Video Card: NVIDIA GeForce 4 Ti4600 using NVIDIA's 'nvidia' X driver. Description: Right-clicking in the NEdit text window normally activates a popup menu. Sometimes, in addition to this menu appearing, the entire screen will go black and the monitor will eventually give a 'no signal message'. The screen goes back to normal as soon as I release the right mouse button or move the mouse. Because the screen blanking looked like the DPMS screensaver, I tried killing xscreensaver, but it still happened. I then tried 'xset -dpms' to turn off the XFree86 internal DPMS scrensaver. This worked, and the problem came back when I turned it back on later. The problem doesn't seem to occur soon after starting a new X session. It starts happening sometime later (I'm still not sure what starts it) and doesn't stop until I logout and restart 'GDM'. The NEdit folks say that NEdit is not the only program with this problem and that they can't even blame Motif. I have not been able to trigger this bug with another applications myself. The original bug report with comments can be found here: http://sourceforge.net/tracker/index.php?func=detail&aid=684780&group_id=11005&atid=111005 Btw, this has happened on my other computer with a Voodoo3 card so I don't think we can blame the NVIDIA driver. /var/log/XFree86.0.log: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-72) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 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/) Build Operating System: Linux 2.4.18-11smp i686 [ELF] Build Host: daffy.perf.redhat.com Module Loader present OS Kernel: Linux version 2.4.18-18.8.0smp ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 SMP Wed Nov 13 22:22:40 EST 2002 P Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Feb 13 15:12:08 2003 (==) Using config file: "/etc/X11/XF86Config" (==) ServerLayout "Default Layout" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Monitor0" (**) | |-->Device "NVIDIA GeForce 4" (**) |-->Input Device "Mouse0" (**) |-->Input Device "Keyboard0" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc105" (**) XKB: model: "pc105" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "DevInputMice" (**) FontPath set to "unix/:7100" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (==) ModulePath set to "/usr/X11R6/lib/modules" (--) using VT number 7 (WW) Open APM failed (/dev/apm_bios) (No such device) (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (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.2.0, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (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.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (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 1022,700c card , rev 11 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1022,700d card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1022,7440 card 1043,8044 rev 04 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1022,7441 card 1022,7441 rev 04 class 01,01,8a hdr 00 (II) PCI: 00:07:3: chip 1022,7443 card 1043,8044 rev 03 class 06,80,00 hdr 00 (II) PCI: 00:09:0: chip 8086,1001 card 8086,1003 rev 02 class 02,00,00 hdr 00 (II) PCI: 00:10:0: chip 1022,7448 card , rev 04 class 06,04,00 hdr 01 (II) PCI: 01:05:0: chip 10de,0250 card 10b0,03ea rev a3 class 03,00,00 hdr 00 (II) PCI: 02:05:0: chip 1102,0002 card 1102,8064 rev 07 class 04,01,00 hdr 80 (II) PCI: 02:05:1: chip 1102,7002 card 1102,0020 rev 07 class
[XFree86] legacy application - startup colormap
I am trying to use a legacy application on a Sun running SUNOS 5.6. I have been unable to get the startup window to load using any other X-windows host than a Sun. I get the same error message running a variety of X-windows hosts. My preferred implementation is Apple's version of xfree86. /usr11/users/DEMO/diag/diag% grsac_hmi Cannot allocate startup image colormap. could not Find #111266 could not Find #593458 could not Find #070699 could not Find #cc could not Find #0033ff could not Find #002bd4 could not Find #0066ff could not Find #1266cf could not Find #5150b2 could not Find #00ec24 could not Find #12ab52 could not Find #0ce39f could not Find #e60627 could not Find #a52f46 could not Find #cca824 could not Find #b08dcd X Error of failed request: BadName (named color or font does not exist) Major opcode of failed request: 45 (X_OpenFont) Serial number of failed request: 370 Current serial number in output stream: 375 How can I add these colors to my .Xdefaults-hostname file or more generally force my local display to accept the legacy x-windows settings? Thanks, David ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Installing
Hi, I am extreemly new to linux and unix type OSes. I really need to know the detailed method of installing a newer version of the xfree86 program. I cannot get into the Gnome X system. I need to install and config X from the prompt. Can any one direct me to a URL or tell me what method to use. I don't understand these rpm / tar.gz etc extensions and how to execute them. Any help is really appreciated, Thanks Schubert Missed your favourite TV serial last night? Try the new, Yahoo! TV. visit http://in.tv.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] helping setting up dvi connections, Please!
Has anyone been able to get a geforce 4 dvi output working with xfree86? I want to connect my flat panel to my freebsd 4.7 machine via DVI-D. Thanks in advance. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Red Hat 8 and X
It looks to me like your card isn't supported. As far as I can tell you've got an S3 card and you're using the S3 driver. But I'm thinking that the "S3 Trio64V2/DX (generic)" isn't a supported variety. If no one corrects me I'd say that's your problem. -- 28. S3 3.3.6: Support (accelerated) for the S3 911, 924, 801, 805, 928, 864, 868, 964, 968, Trio32, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the XF86_S3 server and the XF86_SVGA server with the s3_svga driver. Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+ is provided by the XF86_S3V server. Support (accelerated) for the ViRGE chipsets, as well as the Trio3D and Trio3D/2X, is provided by the XF86_SVGA server with the s3v driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, and Savage2000, is provided by the XF86_SVGA server with the s3_savage driver on some OSes (Linux, *BSD). 4.2.1: Support (accelerated) for the 964 (revisions 0 and 1), 968, Trio32, Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2, and PLATO/PX is provided by the "s3" driver (however, only models using the IBM RGB 524, Texas Instruments 3025, or an internal TrioDAC RAMDAC chip are supported). Support (accelerated) for the ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+, Trio3D and Trio3D/2X is provided by the "s3virge" driver. Support (accelerated) for the Savage3D, Savage3D/MV, Savage4, Savage2000, and SuperSavage, is provided by the "savage" driver. Support for the other S3 chipsets has not yet been ported. Summary: All hardware supported in 3.3.6 is also supported in 4.2.1 except for the 911, 924, 801, 805, 928, 864, and 868, and versions of the 964 and 968 that do not use the RAMDAC chips listed above. The SuperSavage chipset is supported only in 4.2.1. I definitely don't see a Trio64V2/DX. Since it doesn't appear to work I'm guessing that's not the same as a Trio64V2. Of course, I have been wrong. Maybe I'm wrong, Cyn ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Red Hat 8 and X
Hi, I recently installed Red Hat 8, please note that I previously did try older versions of Red Hat and each time experienced the same problem with X. Until now I used Caldera 2.3 (Something like Edesktop). It detected my settings correctly and installed without me having to modify anything else. However, with Red Hat I always had this one problem with X, it won't start. The settings detected by Caldera's installer was: Video Card: S3 Trio64 V2/DX or /GX rev 20 Mode clock programmable up to 170mhz 1mb Video Ram Monitor: Typical Monitors 800 X 600 60mhz Horizontal Khz: 31.5-37.9 Vertical khz: 55-90 Video Mode: 800 X 600 Refresh=56, Depth: 8-16bpp Horiz sync=35.15 Mode clock=36 Attached are the files needed for a possible solution. I also noticed this error on the config screen: "Server error: no screens found" Also note that I have an onboard screencard SIS 5598 which I don't use. I use the S3 card which is in a PCI slot. Maybe you could just sort-of modify the config file, I don't know-I really ain't a Linux expert, just a student. Should you need anymore info, let me know. Thanks for your help and time. Regards, P Botha XFree86.0.log Description: Binary data XF86Config Description: Binary data <<< text/plain; charset="us-ascii"; format=flowed: Unrecognized >>>
[XFree86] bjr
je suis novice en informatique, je recherche un driver pour une carte graphique Silicon Motion LynxEM version 5.1.20001.0 en date du 06/06/2001 merci
Re: [XFree86] [XFree86(TM) Bug Report] NVidia Riva TNT2 M64 - appropriate data has not been added to xf86PciInfo.h
I am also having trouble trying to GET Xserver running with this PCI card on a Compaq Proliant 5500 and am reaching a point of despair!!! Could someone on the development team please advise David - Original Message - From: "BSD Baby" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, February 12, 2003 11:27 PM Subject: [XFree86] [XFree86(TM) Bug Report] NVidia Riva TNT2 M64 - appropriate data has not been added to xf86PciInfo.h > Regarding: NVidia Riva TNT2 M64 - appropriate data has not been added to xf86PciInfo.h > Email: [EMAIL PROTECTED] > -- -- > XFree86 Version: 4.2.1 > > OS: FreeBSD 4.7-RELEASE i386 > > Area: Xserver > > Server: XFree86 (The XFree86 4.x server) > > Video Card: > > pci bus 0x cardnum 0x0c function 0x00: vendor 0x10de device 0x002d > NVidia Riva TNT2 M64 > STATUS0x02b0 COMMAND 0x0007 > CLASS 0x03 0x00 0x00 REVISION 0x15 > BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00 > BASE0 0xde00 addr 0xde00 MEM > BASE1 0xdc08 addr 0xdc00 MEM PREFETCHABLE > MAX_LAT 0x01 MIN_GNT 0x05 INT_PIN 0x01 INT_LINE 0x0a > > > Description: > > XFree86 Version 4.2.1 / X Window System > (protocol Version 11, revision 0, vendor release 6600) > Release Date: 3 September 2002 > 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/) > Build Operating System: FreeBSD 4.7-RELEASE i386 [ELF] > Module Loader present > Markers: (--) probed, (**) from config file, (==) default setting, > (++) from command line, (!!) notice, (II) informational, > (WW) warning, (EE) error, (NI) not implemented, (??) unknown. > (==) Log file: "/var/log/XFree86.0.log", Time: Wed Feb 12 23:16:43 2003 > (--) Using syscons driver with X support (version 2.0) > (--) using VT number 9 > > (II) Module ABI versions: > XFree86 ANSI C Emulation: 0.1 > XFree86 Video Driver: 0.5 > XFree86 XInput driver : 0.3 > XFree86 Server Extension : 0.1 > XFree86 Font Renderer : 0.3 > (II) Loader running on freebsd > (II) LoadModule: "bitmap" > (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a > (II) Module bitmap: vendor="The XFree86 Project" > compiled for 4.2.1, module version = 1.0.0 > Module class: XFree86 Font Renderer > ABI class: XFree86 Font Renderer, version 0.3 > (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.2.1, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) PCI: Probing config type using method 1 > (II) PCI: Config type is 1 > (II) PCI: stages = 0x03, oldVal1 = 0x0cf8, mode1Res1 = 0x0cf8 > (II) PCI: PCI scan (all values are in hex) > (II) PCI: 00:00:0: chip 1039,0740 card 1039,0740 rev 01 class 06,00,00 hdr 80 > (II) PCI: 00:01:0: chip 1039,0001 card , rev 00 class 06,04,00 hdr 01 > (II) PCI: 00:02:0: chip 1039,0008 card , rev 00 class 06,01,00 hdr 80 > (II) PCI: 00:02:5: chip 1039,5513 card 1039,5513 rev d0 class 01,01,80 hdr 80 > (II) PCI: 00:0a:0: chip 13f6,0111 card 1297,f440 rev 10 class 04,01,00 hdr 00 > (II) PCI: 00:0b:0: chip 8086,1229 card 8086,0001 rev 02 class 02,00,00 hdr 00 > (II) PCI: 00:0c:0: chip 10de,002d card , rev 15 class 03,00,00 hdr 00 > (II) PCI: 00:0f:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 > (II) PCI: 00:10:0: chip 11c1,5811 card 1297,f024 rev 04 class 0c,00,10 hdr 00 > (II) PCI: 01:00:0: chip 1039,6325 card 1039,6325 rev 00 class 03,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.2.1, module version = 0.1.0 > ABI class: XFree86 Video Driver, version 0.5 > (II) UnloadModule: "scanpci" > (II) Unloading /usr/X11R6/lib/modules/libscanpci.a > (II) Host-to-PCI bridge: > (II) PCI-to-ISA bridge: > (II) PCI-to-PCI bridge: > (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) > (II) Bus 0 I/O range: > [0] -1 0x - 0x (0x1) IX[B] > (II) Bus 0 non-prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus 0 prefetchable memory range: > [0] -1 0x - 0x (0x0) MX[B] > (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x04 (VGA_EN is cleared) > (II) Bus 1 I/O range: > [0] -1 0xd000 - 0xd0ff (0x100) IX[B] > [1] -1 0xd400 - 0xd4ff (0x100) IX[B] > [2] -1 0xd800 - 0xd8ff (0x100) IX[B] > [3] -1 0xdc00 - 0xdcff (0x100) IX[B] > (II) Bus 1 non-prefetchable memory range: > [0] -1 0xe010 - 0xe01f (
Re: [XFree86] Dynamically change X server resolution
David Chow writes: > Hi all, > > I am new to Xfree86 development. Is it possible to implement an X server > that can dynamically changing the physical resolution (resolution in the > framebuffer, not virtual). Please comment. Thanks. > Yes, use the RandR extension on the upcoming 4.3 release. Try xrandr. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XRandR and Xinerama
Noted the other day that RandR explictly doesnt initialse when panoramix is on. Whats the issue? are there fundamental probelems with using the two together, or is there just some work left to do? I've probably got some time to throw at it if its just a matter of code. Thanks, Rob Taylor ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Dynamically change X server resolution
> I am new to Xfree86 development. Is it possible to implement an X server > that can dynamically changing the physical resolution (resolution in the > framebuffer, not virtual). Please comment. Thanks. You mean the Xvm video mode changing extensions? -- -- Lewin A.R.W. Edwards Work: http://www.digi-frame.com/ Personal: http://www.larwe.com/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Dynamically change X server resolution
Hi all, I am new to Xfree86 development. Is it possible to implement an X server that can dynamically changing the physical resolution (resolution in the framebuffer, not virtual). Please comment. Thanks. regards, David Chow ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Blender and XFree86 Version 4.2.99.901
Hello, Blender's render feature doesn't work with newest xfree. I have XFree86 Version 4.2.99.901 (I downloaded it today), blender 2.26 and ati radeon videocard. When I push the render button I get this message: blender: radeon_vtxfmt.c:1045: radeonVtxfmtUnbindContext: Assertion `vb.context == ctx' failed. Aborted Blender works fine with xfree 4.2.0. Thanks -- Lauri Hintsala <[EMAIL PROTECTED]> http://www.webcell.fi/lauri ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Savage 3D Problem on Red Hat 7.0
Hi, After have installed Red Hat 7.0 on a Pentium Machine I've faced a strange problem regarding the screen. Every time I move some window or even some widget inside a window, I get a completelly messed screen. To fix everything, I need to to a manual refresh using an option on a popup menu of the desktop environment. It seems like the aplications are not doing their work to refresh the screen. More intersting is that since the very beggining, I mean, during the instalation process using graphic interface, I was already having this sort of problem. I don't know if may be something regarding the BIOS setup or the viceo card itself. On Windows 98 everything works fine, at least so far. My video card driver was detected as being a S3 Inc I86c794 [Savage 3D]. My monitor was detected as being a SAM1055 (Samsung SyncMaster 550b). I've searched in your site (http://www.faqs.org/faqs/x-faq/xfree86/) without success. Hope you can help me. Regards, Roger _ Advertência: Esta mensagem não implica a assunção de obrigações em nome da Itaipu Binacional, cujo Estatuto dispõe, em seu Artigo 15: A ITAIPU somente poderá assumir obrigações ou constituir procuradores mediante a assinatura conjunta dos dois Diretores Gerais. (D.O.U. de 20.02.86, págs. 2073/6) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Re: Security in new drivers
> Anything short of a specific example of a real security problem > is nothing more than heresy. > A quibble really, but I think you mean "hearsay" although I concede that heresy could be appropriate too. :) I'm sorry, I just couldn't resist... Cyn > -Original Message- > From: Mike A. Harris [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, February 12, 2003 8:20 PM > To: [EMAIL PROTECTED] > Subject: [XFree86] Re: Security in new drivers > > > On Wed, 12 Feb 2003, John Bartoszewski wrote: > > >I've heard comments from various people that in some drivers for > >new cards that there are local security problems. The example > >that was brought up was the driver for the Radeon 7000 being > >able to write any where in memory and therefor compromise > >security. > > Heard comments from whom? And what specific security problems? > What source code files are these problems in? Or are they just > what-if rumors? > > Seriously, if someone has a claim that one of the drivers is > insecure, then they would know the exact area of the driver > source that such security problems exist, and one would expect > that they would report the problems in a responsible manner to > appropriate developers privately to be examined. > > Anything short of a specific example of a real security problem > is nothing more than heresy. > > > >Without actually reading the drivers is there any place where > >these security problems are discussed and archived? > > You assume that there are known security issues which are also > not fixed. That is not the case however, but I urge anyone who > believes they know of such a security issue to report it > privately to [EMAIL PROTECTED], [EMAIL PROTECTED], > [EMAIL PROTECTED] > > > >Is there a good forum to ask if a driver is secure? > > If a driver wasn't secure, it would be either fixed, or likely > disabled and removed. > > >Have there been audits on drivers directly from Nvidia, Matrox > >or ATI? > > How exactly would someone audit a binary only driver that there > is no publically available source code for? I'm not sure a heck > of a lot could be done without the source code. You'd have to > ask those vendors directly however if they've audited their own > source code for security issues. > > > > -- > Mike A. Harris > > > ___ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 > ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] xserver freeze
hi, i have trouble with freezing x-servers on thinclients. sometimes while using a application (any) the x-server freeze. after rebooting the terminal i cannot login into the terminal server the next few minutes. 1. why i cannot login after crash ? 2. how can i collect data for analysing this situation ? 3 are there any bugs known in this situation ? regards claus rosenberger ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] keymap on sparc - sun/type{4,5}
Hi. I compiled the CVS checkout from "2003-02-01" on my SPARC (Linux, gcc-3.2.2). It runs, but has a problem with XKB or the keymap in a way that pressing "l" results in an "b" (also the capital "L" -> "B"). I took a look into the keymaps but they seem to look right. Also the Funtion key do not work correctly, they produce incorrect keypress events and also switching the VT via Strg-Alt-F? is impossible ... Is this a known problem, wich might already be fixed? (I currently have a 56kBit connection so I try to avoid large data-transfers ...) Thanks - René -- René Rebe - Europe/Germany/Berlin e-mail: [EMAIL PROTECTED], [EMAIL PROTECTED] web: www.rocklinux.org, drocklinux.dyndns.org/rene/ Anyone sending unwanted advertising e-mail to this address will be charged $25 for network traffic and computing time. By extracting my address from this message or its header, you agree to these terms. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Linux 8.0
wtf? yer watching this? ok... SUCK MAH BALLS :-D On Wednesday 12 February 2003 09:09 pm, Daniel Stone wrote: > On Wed, Feb 12, 2003 at 09:13:15PM -0800, C. Brewer scrawled: > > This entire domain and all associated e-mail addresses are located in > > the State of Washington,and sending mail to addresses at this domain is > > subject to the provisions of the Revised Code of Washington. > > Not really; that's a completely bogus assertion. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Can someone help me please!
Hello all, I have a question! If i install the last xfree86 in my desktop, but how can i find out or detect my video card? exist any tool that do it? in the old xfree86 3.3.6 has a tool, i used the command Superproble! What is the new tool that realize this work? thanks anyway, -- +-+ + Marcos Luiz Onisto - ICQ: 11190434 + + SysAdmin at UOL - Universo OnLine + + mailatjob: [EMAIL PROTECTED] + + mailathome: [EMAIL PROTECTED] + + phone: +55 11 3858-0075+ + cell: +55 11 9365-0971+ +-+ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Does XFree86-4.2.1 support GB18030.2000?
On Thu, 13 Feb 2003, [GB2312] ÌÀÊ«Óï wrote: > Dear sir, > I have a question that does XFree86-4.2.1 support GB18030.2000,the new > Chinese Standard?TurboLinux has released a patch for XFree86-4.2.0.You > caould find it here: > http://pkgcvs.turbolinux.co.jp/cgi-bin/cvsweb.cgi/XFree86/4.2.0/?hideattic=0 There are very few changes between XFree86 4.2.0 and 4.2.1, so I would be suprised if GB18030.2000 was added. I wasn't paying much attention, but I think that GB18030.2000 has been discussed on [EMAIL PROTECTED] Try googling for archives of that list, and if that fails ask them whether that encoding made it into current CVS, in which case it will be available in XFree86 v4.3. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: Security in new drivers
Ar an 12ú lá de mí 2, scríobh Mike A. Harris : > Anything short of a specific example of a real security problem > is nothing more than heresy. Don't get all dogmatic about it, Mike :-) . (Yes, you meant hearsay.) -- "I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet." -- T. Samant, 29 June 1997 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] I have a problem with GF4MX440 AGP8x under 5.0 Release
Hi, Please help. Where I can find info about this problem? Andrew Panov XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 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/) Build Operating System: FreeBSD 5.0-CURRENT i386 [ELF] Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/XFree86.0.log", Time: Thu Feb 13 11:01:59 2003 (--) Using syscons driver with X support (version 2.0) (--) using VT number 9 (II) Module ABI versions: XFree86 ANSI C Emulation: 0.1 XFree86 Video Driver: 0.5 XFree86 XInput driver : 0.3 XFree86 Server Extension : 0.1 XFree86 Font Renderer : 0.3 (II) Loader running on freebsd (II) LoadModule: "bitmap" (II) Loading /usr/X11R6/lib/modules/fonts/libbitmap.a (II) Module bitmap: vendor="The XFree86 Project" compiled for 4.2.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (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.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (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,1a30 card 1043,8088 rev 11 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,1a31 card , rev 11 class 06,04,00 hdr 01 (II) PCI: 00:1d:0: chip 8086,24c2 card 1043,8089 rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 1043,8089 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 1043,8089 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 1043,8089 rev 01 class 0c,03,20 hdr 00 (II) PCI: 00:1e:0: chip 8086,244e card , rev 81 class 06,04,00 hdr 01 (II) PCI: 00:1f:0: chip 8086,24c0 card , rev 01 class 06,01,00 hdr 80 (II) PCI: 00:1f:1: chip 8086,24cb card 1043,8089 rev 01 class 01,01,8a hdr 00 (II) PCI: 01:00:0: chip 10de,0181 card 1043,806f rev a2 class 03,00,00 hdr 00 (II) PCI: 02:03:0: chip 13f6,0111 card 1043,80e2 rev 10 class 04,01,00 hdr 00 (II) PCI: 02:0b:0: chip 10b7,9200 card 10b7,1000 rev 74 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.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: "scanpci" (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) PCI-to-PCI bridge: (II) PCI-to-PCI 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 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x08 (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xf200 - 0xf3df (0x1e0) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xf3f0 - 0xf7ff (0x410) MX[B] (II) Bus 2: bridge is at (0:30:0), (0,2,2), BCTRL: 0x06 (VGA_EN is cleared) (II) Bus 2 I/O range: [0] -1 0xb000 - 0xb0ff (0x100) IX[B] [1] -1 0xb400 - 0xb4ff (0x100) IX[B] [2] -1 0xb800 - 0xb8ff (0x100) IX[B] [3] -1 0xbc00 - 0xbcff (0x100) IX[B] (II) Bus 2 non-prefetchable memory range: [0] -1 0xf100 - 0xf17f (0x80) MX[B] (II) Bus 2 prefetchable memory range: [0] -1 0xf3e0 - 0xf3ef (0x10) MX[B] (II) Bus -1: bridge is at (0:31:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(1:0:0) NVidia unknown chipset (0x0181) rev 162, Mem @ 0xf200/24, 0xf400/26, BIOS @ 0xf3fe/17 List of video drivers: atimisc r128 radeon ati glint mga nv rendition s3 s3virge savage siliconmotion tdfx tga vga apm ark chips cirrus cyrix fbdev i740 i128 i810 ne
