[Xpert]Can XVideo work on 3dfx Voodoo 3 3000?
Hi Please, can anybody help me with the following question? I am watching DVD's with xine in my Slackware 8.1. However, I can only watch them in BlackWhite because I can't adjust the Hue, Sat or Ctr controls. I have read that I must use the XVideo extension to be able to change these settings. Is this correct? I have XFree86 4.2.0 and a 3dfx Voodoo 3 3000 AGP video card, both of which are said to support the XVideo. The output of xdpyinfo | grep XVideo is: XVideo However, the output of xvinfo is: X-Video Extension version 2.2 screen #0 no adaptors present I have read that this means that my video card doesn't support the XVideo. Is this correct? Is there anybody running XVideo on the 3dfx Voodoo 3 3000? I can think of two possibilities to solve my problem: 1. Installing some software or libraries to activate the XVideo. Is this possible? 2. Buying a new video card. Can you recommend me one? I have the following hardware and software: Pentium III 800 MHz. 3dfx Voodoo 3 3000 AGP video card (16MB memory). 128 MB RAM Linux Slackware 8.1 with Kernel 2.4.18 3dfx Banshee/Voodoo3+ compiled in the kernel (CONFIG_DRM_TDFX option). XFree86 4.2.0 Thanks for your help ___ Yahoo! Messenger Nueva versión: Webcam, voz, y mucho más ¡Gratis! Descárgalo ya desde http://messenger.yahoo.es ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]RandR rotation support
On Fri, Nov 08, 2002 at 05:38:07 -0800, Keith Packard wrote: I've implemented rotation and reflection support in the core XFree86 server; it was less invasive than I'd feared and seems to work just fine. For most devices, it does it's work by substituting a whole new rendering mechanism based on the shadow frame buffer when the screen is rotated or reflected. Right now, this means that video and DRI won't work right if the screen is rotated; they'll hit the regular frame buffer and mangle things badly. It also permits drivers to support rotation themselves as the siliconmotion hardware seems capable of. It's possible to provide video support in this rotated world; I've implemented that for the Mach64 chipset in Tiny-X (mostly because I could), we could do that for the regular XFree86 servers too with some additional work. On the other hand, DRI probably won't ever work on a rotated screen; you'd have to transmit the rotation information to the application and let them convert transformation matrices and clip lists. That'd be a real adventure. I haven't yet committed the changes to CVS as I'm curious of two things: 1)It hooks into some seemingly silly places -- it needs two initialization steps, one right before acceleration is pushed on top of fb and another right before the software cursor is pushed on top of the acceleration. The first is done by sticking a call inside xf86SetBackingStore, the second by placing a call inside xf86GetPointerScreenFuncs. Those two functions happen to need to be called at precisely the same moment as the RandR hooks, but are obviously not exactly semantically intended for this purpose. The alternative is to require every driver to add calls to RandR, which I'll do if people think it's the right think to do. The driver is meant to be in control of everything, so I'd opt for the last option here. 2)Permitting rotation incurs an additional layer along several paths inside the X server -- the usual rendering paths all need to get redirected when the system switches from hardware to software rendering, so the screen functions CreateGC, PaintWindow* and the like all get wrapped by the layer module. This new layer is implemented by the 'layer' and 'shadow' modules, both of which must be loaded when the server starts for rotation to ever be possible. It seems reasonable, therefore, that this dynamic rotation mechanism should be selectable. Should I add an option to enable or disable this? Should it be disabled by default? Disabled by default. Alan. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]S3 Trio 3d
No, I don't believe the Trio3d hardware supports anything above 24 bit color. The chipset supports a 32 bit wide mode, but that is 24 bits of color in sparse packing, meaning it stores the 24 color bits in 32 bits of memory. No, vrefresh and hsync are monitor limits. Your log file shows that these are not set. I'd suggest trying to add the options: HorizSync 10 - 12 VertRefresh 12 - 14 Option noddc to your Monitor section in the config file. You must change the numbers to match the monitor you have installed. -- Kevin Jørn Christensen wrote: Hi Let me know when you have had a chance of looking on the driver... I have no expertise in this area, but I think it might be a problem for the driver to allocate enough memory; as I said before the screen reduces in size when I sellect 24 bpp and is perfect in 8bpp x 1280 x 960! Could you explain to me why there's no advantage of 32 bit? It might be me, but on Win98 I thought I could tell the difference between a 24bit gradient and a 32 bit gradient - or have I fooled myself??? Setting the vrefresh and hsync is done by Modelines... right? Well I found some different modelines for 1024 x 768 and the only difference was where on the screen the picture was placed... (oh well and the refresh rate...) but I thought it had no effect on the driver generating the picture...!?!?!? ~Jørn Christensen On Thu, 2002-11-07 at 00:53, Kevin Brosius wrote: Well, don't know any other reason, other than there is a problem with the driver. I'll have to take a look and see. I do see you don't have the monitor settings in the config file, you might try setting vrefresh and hsync in the Monitor section. Also, there's no real advantage to 32 bit, and 24 bit is generally faster. (I noticed you mentioned that before.) -- Kevin Jørn Christensen wrote: Yes... tried that (alogn with XVideo 0)... didn't work... Attached the log and the config file... ~Jørn On Tue, 2002-11-05 at 12:36, Kevin Brosius wrote: Jørn Christensen wrote: Hi I have a Trio 3d vidoe card (4mb) and really really want to get a higher resolution than 1024x768. I've just upgraded to XFree86 4.2.1. The problem is that when I try to set a higher ersolution (16bpp) it only draws a correct width at 1024. The rest (from 1025 to e.g. 1152) is copied from the right side of the perfectly drawn screen. I've tried many settings - even rising the bpp to 24 (I really wanted 32, but the s3virge driver doesn't allow this...) but this width to the correctly drawn screen only reduces to 800 or 640 (not quite sure...). I would send you a screen shot to illustrate, but my X-window manger sees the full desktop and the screen shot does not illustrate the problem. I attach 3 log files from X (-verbos): - 1024-768-16.log The current working setup (read: 1024 * 768; 16bit) - 1024-768-24.log Broken... - 1152-864-16.log Broken... Please help - Its very frustrating on a 17... What happens if you add the noxvideo option to the driver section? -- Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Matrox G550 and DDC problem
On Wed, Oct 30, 2002 at 07:22:28AM +, Dr Andrew C Aitchison wrote: On Wed, 16 Oct 2002, Scott Lampert wrote: I'm having trouble getting DDC to work with my Dell P1110 and my Matrox G550. No matter what options I add or remove from my device section I get output similar to: Oddly enough, when I run X -configure it reads the EDID information successfully and puts the information it garners about the monitor into the XF86Config.new file. There was dispute about whether the mga driver should use the VBE code to interrogation, or do it itself, and the current state is that both methods are implemented (in MGAProbeDDC(..) and MGAdoDDC(...)) and one is used by X -configure and the other in normal use. There are people who claim that one method upsets their system, while others claim that the other method doesn't work for them. I was involved in the orginal, direct, implementation, before the VBE method was added (when the mga driver was the only one to support DDC). Since both methods work for me on my original Millennium I've not had any incentive to persue that matter. Inertia seems to have left the current state for a couple of years. Does DDC require OS support, such as loaded I2C drivers? Kurt -- The problem with the gene pool is that there is no lifeguard. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]S3 Trio 3d
Just tried that... same result... (Asumed that Horisync was in khz and VertRefresh was in hz) ~Jørn Christensen On Sat, 2002-11-09 at 13:39, Kevin Brosius wrote: No, I don't believe the Trio3d hardware supports anything above 24 bit color. The chipset supports a 32 bit wide mode, but that is 24 bits of color in sparse packing, meaning it stores the 24 color bits in 32 bits of memory. No, vrefresh and hsync are monitor limits. Your log file shows that these are not set. I'd suggest trying to add the options: HorizSync 10 - 12 VertRefresh 12 - 14 Option noddc to your Monitor section in the config file. You must change the numbers to match the monitor you have installed. -- Kevin Jørn Christensen wrote: Hi Let me know when you have had a chance of looking on the driver... I have no expertise in this area, but I think it might be a problem for the driver to allocate enough memory; as I said before the screen reduces in size when I sellect 24 bpp and is perfect in 8bpp x 1280 x 960! Could you explain to me why there's no advantage of 32 bit? It might be me, but on Win98 I thought I could tell the difference between a 24bit gradient and a 32 bit gradient - or have I fooled myself??? Setting the vrefresh and hsync is done by Modelines... right? Well I found some different modelines for 1024 x 768 and the only difference was where on the screen the picture was placed... (oh well and the refresh rate...) but I thought it had no effect on the driver generating the picture...!?!?!? ~Jørn Christensen On Thu, 2002-11-07 at 00:53, Kevin Brosius wrote: Well, don't know any other reason, other than there is a problem with the driver. I'll have to take a look and see. I do see you don't have the monitor settings in the config file, you might try setting vrefresh and hsync in the Monitor section. Also, there's no real advantage to 32 bit, and 24 bit is generally faster. (I noticed you mentioned that before.) -- Kevin Jørn Christensen wrote: Yes... tried that (alogn with XVideo 0)... didn't work... Attached the log and the config file... ~Jørn On Tue, 2002-11-05 at 12:36, Kevin Brosius wrote: Jørn Christensen wrote: Hi I have a Trio 3d vidoe card (4mb) and really really want to get a higher resolution than 1024x768. I've just upgraded to XFree86 4.2.1. The problem is that when I try to set a higher ersolution (16bpp) it only draws a correct width at 1024. The rest (from 1025 to e.g. 1152) is copied from the right side of the perfectly drawn screen. I've tried many settings - even rising the bpp to 24 (I really wanted 32, but the s3virge driver doesn't allow this...) but this width to the correctly drawn screen only reduces to 800 or 640 (not quite sure...). I would send you a screen shot to illustrate, but my X-window manger sees the full desktop and the screen shot does not illustrate the problem. I attach 3 log files from X (-verbos): - 1024-768-16.log The current working setup (read: 1024 * 768; 16bit) - 1024-768-24.log Broken... - 1152-864-16.log Broken... Please help - Its very frustrating on a 17... What happens if you add the noxvideo option to the driver section? -- Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]S3 Trio 3d
With vesa or s3virge? It isn't going to help on vesa. Jørn Christensen wrote: Just tried that... same result... (Asumed that Horisync was in khz and VertRefresh was in hz) ~Jørn Christensen On Sat, 2002-11-09 at 13:39, Kevin Brosius wrote: No, I don't believe the Trio3d hardware supports anything above 24 bit color. The chipset supports a 32 bit wide mode, but that is 24 bits of color in sparse packing, meaning it stores the 24 color bits in 32 bits of memory. No, vrefresh and hsync are monitor limits. Your log file shows that these are not set. I'd suggest trying to add the options: HorizSync 10 - 12 VertRefresh 12 - 14 Option noddc to your Monitor section in the config file. You must change the numbers to match the monitor you have installed. -- Kevin Jørn Christensen wrote: Hi Let me know when you have had a chance of looking on the driver... I have no expertise in this area, but I think it might be a problem for the driver to allocate enough memory; as I said before the screen reduces in size when I sellect 24 bpp and is perfect in 8bpp x 1280 x 960! Could you explain to me why there's no advantage of 32 bit? It might be me, but on Win98 I thought I could tell the difference between a 24bit gradient and a 32 bit gradient - or have I fooled myself??? Setting the vrefresh and hsync is done by Modelines... right? Well I found some different modelines for 1024 x 768 and the only difference was where on the screen the picture was placed... (oh well and the refresh rate...) but I thought it had no effect on the driver generating the picture...!?!?!? ~Jørn Christensen On Thu, 2002-11-07 at 00:53, Kevin Brosius wrote: Well, don't know any other reason, other than there is a problem with the driver. I'll have to take a look and see. I do see you don't have the monitor settings in the config file, you might try setting vrefresh and hsync in the Monitor section. Also, there's no real advantage to 32 bit, and 24 bit is generally faster. (I noticed you mentioned that before.) -- Kevin Jørn Christensen wrote: Yes... tried that (alogn with XVideo 0)... didn't work... Attached the log and the config file... ~Jørn On Tue, 2002-11-05 at 12:36, Kevin Brosius wrote: Jørn Christensen wrote: Hi I have a Trio 3d vidoe card (4mb) and really really want to get a higher resolution than 1024x768. I've just upgraded to XFree86 4.2.1. The problem is that when I try to set a higher ersolution (16bpp) it only draws a correct width at 1024. The rest (from 1025 to e.g. 1152) is copied from the right side of the perfectly drawn screen. I've tried many settings - even rising the bpp to 24 (I really wanted 32, but the s3virge driver doesn't allow this...) but this width to the correctly drawn screen only reduces to 800 or 640 (not quite sure...). I would send you a screen shot to illustrate, but my X-window manger sees the full desktop and the screen shot does not illustrate the problem. I attach 3 log files from X (-verbos): - 1024-768-16.log The current working setup (read: 1024 * 768; 16bit) - 1024-768-24.log Broken... - 1152-864-16.log Broken... Please help - Its very frustrating on a 17... What happens if you add the noxvideo option to the driver section? -- Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]S3 Trio 3d
With s3virge... Went back from vesa to virge because the modelines did not seem to have any effect on the vesa driver and even though I wanted a higher resolution, I would not suffer the low refresh rate that the vesa gave me! ~Jørn Christensen On Sat, 2002-11-09 at 16:46, Kevin Brosius wrote: With vesa or s3virge? It isn't going to help on vesa. Jørn Christensen wrote: Just tried that... same result... (Asumed that Horisync was in khz and VertRefresh was in hz) ~Jørn Christensen On Sat, 2002-11-09 at 13:39, Kevin Brosius wrote: No, I don't believe the Trio3d hardware supports anything above 24 bit color. The chipset supports a 32 bit wide mode, but that is 24 bits of color in sparse packing, meaning it stores the 24 color bits in 32 bits of memory. No, vrefresh and hsync are monitor limits. Your log file shows that these are not set. I'd suggest trying to add the options: HorizSync 10 - 12 VertRefresh 12 - 14 Option noddc to your Monitor section in the config file. You must change the numbers to match the monitor you have installed. -- Kevin Jørn Christensen wrote: Hi Let me know when you have had a chance of looking on the driver... I have no expertise in this area, but I think it might be a problem for the driver to allocate enough memory; as I said before the screen reduces in size when I sellect 24 bpp and is perfect in 8bpp x 1280 x 960! Could you explain to me why there's no advantage of 32 bit? It might be me, but on Win98 I thought I could tell the difference between a 24bit gradient and a 32 bit gradient - or have I fooled myself??? Setting the vrefresh and hsync is done by Modelines... right? Well I found some different modelines for 1024 x 768 and the only difference was where on the screen the picture was placed... (oh well and the refresh rate...) but I thought it had no effect on the driver generating the picture...!?!?!? ~Jørn Christensen On Thu, 2002-11-07 at 00:53, Kevin Brosius wrote: Well, don't know any other reason, other than there is a problem with the driver. I'll have to take a look and see. I do see you don't have the monitor settings in the config file, you might try setting vrefresh and hsync in the Monitor section. Also, there's no real advantage to 32 bit, and 24 bit is generally faster. (I noticed you mentioned that before.) -- Kevin Jørn Christensen wrote: Yes... tried that (alogn with XVideo 0)... didn't work... Attached the log and the config file... ~Jørn On Tue, 2002-11-05 at 12:36, Kevin Brosius wrote: Jørn Christensen wrote: Hi I have a Trio 3d vidoe card (4mb) and really really want to get a higher resolution than 1024x768. I've just upgraded to XFree86 4.2.1. The problem is that when I try to set a higher ersolution (16bpp) it only draws a correct width at 1024. The rest (from 1025 to e.g. 1152) is copied from the right side of the perfectly drawn screen. I've tried many settings - even rising the bpp to 24 (I really wanted 32, but the s3virge driver doesn't allow this...) but this width to the correctly drawn screen only reduces to 800 or 640 (not quite sure...). I would send you a screen shot to illustrate, but my X-window manger sees the full desktop and the screen shot does not illustrate the problem. I attach 3 log files from X (-verbos): - 1024-768-16.log The current working setup (read: 1024 * 768; 16bit) - 1024-768-24.log Broken... - 1152-864-16.log Broken... Please help - Its very frustrating on a 17... What happens if you add the noxvideo option to the driver section? -- Kevin ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Matrox G550 and DDC problem
On Sat, 9 Nov 2002 [EMAIL PROTECTED] wrote: Does DDC require OS support, such as loaded I2C drivers? There are two versions: DDC1 and DDC2. These are not the same as the EDID version reported in the DDC info, and DDC2 is split into at least three). Some monitors support DDC1 but not DDC2 and vice-versa. For our mga driver there are actually three DDC implementations: DDC1, DDC2 and DDCvbe. Each can be turned off separately in the Monitor Section of the config file, with one of: Option noDDC1 Option noDDC2 Option noDDCvbe DDCvbe uses the video BIOS to return the DDC info. DDC2 requires the XFree86 I2C module, but not I think kernel I2C support. It does use a micro-second delay function; if you don't provide anything better it can revert to an uncalibrated loop which is probably far too fast current hardware. As far as I know the DDC1 code requires no specific operating system support, but it doesn't support DDC2 only monitors, and may fail if called after the DDC2 support (the monitor can get stuck in DDC2 mode). -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Linux input patch.
This patch (attached) add support under Linux for talking to mice
directly from the event interface, IE, /dev/input/eventn.
It is stashed as a os specific protocol, evdev, the Device option is not
a device, but instead is the device name, such as
'A4Tech USB Optical Mouse'.
It has some limits, specificly if you unplug a USB mouse and plug it
back in you have to cause it to be deactivated and reactivated, a good
way of doing that is to change VTs away from X, and then change back.
Also if you have two identical mice with the same label it is somewhat
indeterminate which you will get, this could be improved.
Another item to be improved is that it should attempt to handle all
forms of mice, such as tables (absolute positions, with pressure
sensitive readings), that said, I can't quite do that without the
hardware, so, someone else will have to.
The big gain from this at the moment is the second mouse wheel.
Comments appreciated.
Zephaniah E. Hull.
--
1024D/E65A7801 Zephaniah E. Hull [EMAIL PROTECTED]
92ED 94E4 B1E6 3624 226D 5727 4453 008B E65A 7801
CCs of replies from mailing lists are requested.
There are mushrooms that can survive weeks, months without air or
food. They just dry out and when water comes back, they wake up
again. And call the helldesk about their password expiring.
-- after Jens Benecke and Tanuki the Raccoon-dog, in ASR:
diff -ur build-tree/xc/programs/Xserver/hw/xfree86/os-support/linux/Imakefile
build-tree.mine/xc/programs/Xserver/hw/xfree86/os-support/linux/Imakefile
--- xc/programs/Xserver/hw/xfree86/os-support/linux/Imakefile 2000-11-16
14:45:03.0 -0500
+++ xc/programs/Xserver/hw/xfree86/os-support/linux/Imakefile 2002-11-09
+06:06:23.0 -0500
@@ -50,7 +50,8 @@
$(AXP_OBJ) lnx_kmod.o lnx_agp.o
INCLUDES = -I$(XF86COMSRC) -I$(XF86OSSRC) -I. -I$(SERVERSRC)/include \
- -I$(XINCLUDESRC) -I$(EXTINCSRC) -I$(XF86OSSRC)/shared
+ -I$(XINCLUDESRC) -I$(EXTINCSRC) -I$(XF86OSSRC)/shared \
+ -I$(SERVERSRC)/mi
RESDEFINES = -DUSESTDRES
diff -ur build-tree/xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_mouse.c
build-tree.mine/xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_mouse.c
--- xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_mouse.c 1999-05-17
09:17:18.0 -0400
+++ xc/programs/Xserver/hw/xfree86/os-support/linux/lnx_mouse.c 2002-11-09
+11:21:23.0 -0500
@@ -6,8 +6,24 @@
#include X.h
#include xf86.h
+#include xf86Priv.h
+#include xf86_OSlib.h
#include xf86Xinput.h
#include xf86OSmouse.h
+#include mipointer.h
+#include linux/input.h
+
+#define BITS_PER_LONG (sizeof(long) * 8)
+#define NBITS(x) x)-1)/BITS_PER_LONG)+1)
+#define OFF(x) ((x)%BITS_PER_LONG)
+#define LONG(x) ((x)/BITS_PER_LONG)
+#define test_bit(bit, array)((array[LONG(bit)] OFF(bit)) 1)
+
+/* Names of protocols that are handled internally here. */
+static const char *internalNames[] = {
+ evdev,
+ NULL
+};
static int
SupportedInterfaces(void)
@@ -15,6 +31,260 @@
return MSE_SERIAL | MSE_BUS | MSE_PS2 | MSE_XPS2 | MSE_AUTO;
}
+static const char **
+BuiltinNames(void)
+{
+return internalNames;
+}
+
+static Bool
+CheckProtocol(const char *protocol)
+{
+int i;
+
+for (i = 0; internalNames[i]; i++)
+ if (xf86NameCmp(protocol, internalNames[i]) == 0)
+ return TRUE;
+return FALSE;
+}
+
+typedef struct _evdevMseRec {
+int packetSize;
+int buttons;
+} evdevMseRec, *evdevMsePtr;
+
+static int
+evdevFindMouse (const char *want)
+{
+char dev[20];
+char name[256] = ;
+int fd, i;
+
+i = 0;
+while (1) {
+ snprintf(dev, sizeof(dev), /dev/input/event%d, i);
+ SYSCALL(fd = open (dev, O_RDWR | O_NONBLOCK));
+ if (fd == -1)
+ return -1;
+ ioctl(fd, EVIOCGNAME(sizeof(name)), name);
+ if (xf86NameCmp(name, want) == 0) {
+ return fd;
+ }
+ close(fd);
+}
+return -1;
+}
+
+static void
+evdevReadInput(InputInfoPtr pInfo)
+{
+MouseDevPtr pMse;
+evdevMsePtr evdevMse;
+struct input_event *ev;
+int n, bit;
+
+pMse = pInfo-private;
+ev = (struct input_event *) pMse-buffer;
+evdevMse = pMse-mousePriv;
+
+if (pInfo-fd == -1)
+ return;
+
+do {
+ int dx = 0, dy = 0, dz = 0, dw = 0;
+ n = read(pInfo-fd, pMse-buffer, sizeof(struct input_event));
+ if (n == -1) {
+ xf86Msg(X_ERROR, %s: Error in reading! (%s) Disabiling.\n,
+ pInfo-name, strerror(errno));
+ RemoveEnabledDevice(pInfo-fd);
+ xf86RemoveSIGIOHandler(pInfo-fd);
+ close (pInfo-fd);
+ pMse-device-public.on = FALSE;
+ pInfo-fd = -1;
+ return;
+ }
+ if (n != sizeof(struct input_event)) {
+ xf86Msg(X_WARNING, %s: incomplete packet, size %d\n, pInfo-name, n);
+ return;
+ }
+
+ switch (ev-type) {
+ case
[Xpert]Re: Can XVideo work on 3dfx Voodoo 3 3000?
[EMAIL PROTECTED] wrote: I am watching DVD's with xine in my Slackware 8.1. However, I can only watch them in BlackWhite because I can't adjust the Hue, Sat or Ctr controls. I have read that I must use the XVideo extension to be able to change these settings. Is this correct? Not exactly. The Voodoo3 doesn't support Hue, Saturation, and Contrast controls. Most other modern video cards do, but not the Voodoo3. [xdpyinfo reports that the XVideo extension is supported, but xvinfo reports no adaptors present.] I have read that this means that my video card doesn't support the XVideo. Is this correct? Is there anybody running XVideo on the 3dfx Voodoo 3 3000? It works for me. Like you, I have a Voodoo3 3000 AGP. I'm running XFree86 4.1 though. Are you running your Voodoo3 in a 16-bits-per-pixel mode? Most of the Voodoo3 acceleration features only work when the depth is 16 planes, and I think that includes XVideo. ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Can XVideo work on 3dfx Voodoo 3 3000?
On Sat, 9 Nov 2002, Steve Kirkendall wrote: It works for me. Like you, I have a Voodoo3 3000 AGP. I'm running XFree86 4.1 though. Are you running your Voodoo3 in a 16-bits-per-pixel mode? Most of the Voodoo3 acceleration features only work when the depth is 16 planes, and I think that includes XVideo. Hi, tdfx driver for voodoo card certains supports XVideo, though you will need a recent XFree. XVideo also definitely works in 24 bit mode. Steve ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]Support for the VLB bus.
Hello, It is my understanding that 4.2.1 does not support the VLB bus. Am I correct? Are there other people who would be interested in having this bus supported? Is there work in progress to have this bus supported? Can I help by testing what was being done so far? Are there any pointers for reading material for a beginner who want to get his VLB card supported? How difficult it would be to import the VLB supporting code from 3.3.6 to 4.2.1? My hardware is an S3 Trio32 VLB card: Miro CRYSTAL 12sd. The card works well with 3.3.6 but not with 4.2.1. The platform is i386 Linux 2.4.19. I can post the output of X when it starts if this is of interest to someone. -- Shaul Karl, [EMAIL PROTECTED] e t ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
[Xpert]X widgets callable from shell scripts?
Hello, I am looking for the source code of the XScript utilities mentioned here: http://jan.netcomp.monash.edu.au/SW.html#XScript or for something equivalent. That source code seems to have vanished. The only relatively modern similar thing I have found is xask. Does anybody know: * where the xscript source code is * (preferred) if the same thing has been remade more recently, with more modern libraries/toolkits? By same thing I mean small *standalone* programs taking input from STDIN, displaying file selection/prompts/menus windows in X, and echoing the selection to STDOUT, for use in shell scripts. TIA, Marco Fioretti ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Radeon VE w/ dual monitors not loading
On Mit, 2002-11-06 at 05:37, Ryan Oertel wrote: I've seen this posted many times to this list, so I know it's not an uncommon problem, I've scoured the mailing lists and google's groups for anything, but none of the configuration files and tips seem to work for me. I'm trying to get two monitors working in X with my Radeon VE card. When I start X, both monitors go to sleep. I can CTRL+ALT+F6 to bring them back. Screen 0 is connected to the digital port and Screen 0 to the analog. Here's the system setup: -RedHat 7.2 (with updates from updates.redhat.com) -XFree86 4.1.0-25 (from rpms) I have been working at this on and off for several days with little progress. Attached, are copies of my XF86Config-4 and XFree86.0.log. Look fine to me; you may need the driver from current CVS, I think that's the case for OEM cards in particular. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast from News and Sport to Email and Music Charts http://uk.my.yahoo.com That did the trick! I upgraded to RedHat 8.0 and got both working. I also had the wrong H and V sync rates set. I must have mis-keyed it. Thank you! ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
Re: [Xpert]Re: Can XVideo work on 3dfx Voodoo 3 3000?
On Sat, 9 Nov 2002 21:08:41 + (GMT) Stephen Davies [EMAIL PROTECTED] wrote: On Sat, 9 Nov 2002, Steve Kirkendall wrote: It works for me. Like you, I have a Voodoo3 3000 AGP. I'm running XFree86 4.1 though. Are you running your Voodoo3 in a 16-bits-per-pixel mode? Most of the Voodoo3 acceleration features only work when the depth is 16 planes, and I think that includes XVideo. Hi, tdfx driver for voodoo card certains supports XVideo, though you will need a recent XFree. XVideo also definitely works in 24 bit mode. Another thought might be to make sure that load extmod is in the XF86Config.(think that's where the Xvideo extension gets included?) ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
