any accelerated/3d driver for ati radeon IGP 320m?
I can only get vesa working with this card, it seems. radeon.o doesn't seem to work(at least when i compiled it into kernel and used vga=792, it didnt work, but vesafb does), and i can't get any X driver besides vesa working. What to do? _ Tired of spam? Get advanced junk mail protection with MSN 8. http://join.msn.com/?page=features/junkmail ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: S3 968 documentation
Hi, i have a dead-tree edition of the 964 manual which I don't need anymore. If you still want one, i can send it to you. No need to cover shipping cost. rainer ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xterm can hang, CPU bound
On Sun, Feb 02, 2003 at 03:42:35AM -0500, D. Hugh Redelmeier wrote: This is a very old bug/feature. I spent some time looking into it. Not being very experienced at X coding, so I haven't attempted a fix. Demo of bug: - in an xterm running a shell, type: echo -e '\033[?1001h' - click in the window xterm now locks up (this is documented in ctlseqs.ms) and eats all available CPU (not documented). ... Confirmed by someone else on Xfree86 4.2.99.4. On Red Hat LINUX 8.0, I straced such a hung xterm. There was a cycle of 4 select system calls. It is all within one invocation of xc/programs/xterm/charproc.c:ip_put hmm - running on Slackware 7.1, I don't see any CPU load. I'm using a test-screen in vttest to exercise this feature. But I do have a Redhat 8.0 for testing - will see if I can reproduce this problem there. Now: what about avoiding the hang altogether? I've not understood the code well enough to know what I'd do. The hang is fundamental. The xterm does not know how to act until it gets the CSI...T sequence from the pty. Perhaps a better approach would be to act as if a default one had been received until the actual one arrives. well yes - the xterm doesn't pay attention to anything else when it's in that mode. That's why it's not much used. -- Thomas E. Dickey [EMAIL PROTECTED] http://invisible-island.net ftp://invisible-island.net ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: S3 968 documentation
i have a dead-tree edition of the 964 manual which I don't need anymore. If you still want one, i can send it to you. No need to cover shipping cost. If nobody else applies, I'm interested. I have only the 968 part, which is a 964 add-on (and thus which is not very interesting by itself). However I do not have much time for coding so that if anybody else needs it, s/he will do a better use of it (than me). Loïc ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Keys missing from fr mapping on XFree86 CVS
Hi all, Dunno if it's a known issue or not (I know there've been some discussion about ca_enhanced problems recently), but I'm using a french keyboard on a Toshiba laptop and the keys and are not mapped anymore when using this afternoon XFree86 CVS. On my keyboard, these keys are placed just on the tight of the space bar ( is accessible using Shift) It worked fine with XFree86 4.2 (same XF86Config) Lemme know if there is anything I can do to help, Best regards, -- Olivier Fourdan [EMAIL PROTECTED] http://www.xfce.org ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Bug 83284] New: Mouse cursor visual glitches with XFree86 (fwd)
On Sat, 1 Feb 2003, Michel [ISO-8859-1] Dänzer wrote: On Sam, 2003-02-01 at 19:46, Mike A. Harris wrote: The ATI drivers have been having mouse cursor artifact problems in current CVS on all Radeon hardware related to Xcursor being used. If swcursor is used, or if cursor themes are overridden by using core cursors, the problem goes away. The problems people have been reporting include visual artifacts while cursor shapes change at window borders, cursors disappearing for anywhere up to 10 seconds or so then reappearing, As I said in the thread '4.2.99.4 no display, locked keyboard (Radeon 7500Mobility)', the fix for the former problems causes the latter with DRI enabled because the DRM interrupt handler clears the bit RADEONWaitForVerticalSync() polls for. I'm working on a fix, basically my plan is to use the DRM vertical blank ioctl when appropriate. There is a patch I posted a while ago for the same problem that waits for retrace with a timeout - so even if the bit is cleared we timeout after 1/60 of sec (approx) and everything is fine anyway. Also, Michel, while you are at it - could you modify the irq handler in DRM to *only* clear bits that it is actually interested it ? Otherwise it clears capture and gui_dma IRQs which GATOS km driver needs and which are not used by drm at all. thank you Vladimir Dergachev -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [Bug 83284] New: Mouse cursor visual glitches with XFree86(fwd)
On Mon, 2003-02-03 at 00:38, Vladimir Dergachev wrote:
On Sat, 1 Feb 2003, Michel [ISO-8859-1] Dänzer wrote:
On Sam, 2003-02-01 at 19:46, Mike A. Harris wrote:
The ATI drivers have been having mouse cursor artifact problems
in current CVS on all Radeon hardware related to Xcursor being
used. If swcursor is used, or if cursor themes are overridden
by using core cursors, the problem goes away. The problems
people have been reporting include visual artifacts while cursor
shapes change at window borders, cursors disappearing for
anywhere up to 10 seconds or so then reappearing,
As I said in the thread '4.2.99.4 no display, locked keyboard (Radeon
7500Mobility)', the fix for the former problems causes the latter with
DRI enabled because the DRM interrupt handler clears the bit
RADEONWaitForVerticalSync() polls for. I'm working on a fix, basically
my plan is to use the DRM vertical blank ioctl when appropriate.
There is a patch I posted a while ago for the same problem that waits for
retrace with a timeout - so even if the bit is cleared we timeout after
1/60 of sec (approx) and everything is fine anyway.
I don't like that. Polling for CRTC{,2}_VBLANK_SAVE should be foolproof,
or am I missing something?
(Did you see the further discussion about this on the xfree86 list?)
Also, Michel, while you are at it - could you modify the irq handler in
DRM to *only* clear bits that it is actually interested it ? Otherwise it
clears capture and gui_dma IRQs which GATOS km driver needs and which are
not used by drm at all.
I wouldn't mind doing that at all, in fact that's how I did it
initially, but the code has since been changed with the following
comment:
/* Acknowledge all the bits in GEN_INT_STATUS -- seem to get
* more than we asked for...
*/
Your argument makes a lot of sense so I'll probably change it back in
DRI CVS, but I don't know if it'll make it for 4.3.0...
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
[patch for 4.3] define Alt/Meta modifiers for jp106 kbd
With current cvs, the Alt and Meta modifiers aren't defined
for Japanese keyboards, and further Ctrl-Alt-Fn doesn't
work. For Japanese users this is a bit of a showstopper for
4.3 IMHO. I have a feeling this also affects other non-US
keyboard files...
The patch below fixes this, adding Alt and Meta modifiers to
the Japanese jp106 keyboard symbols file and including the
definitions for Ctrl-Alt-Fn. Could it please applied for 4.3?
--- xc/programs/xkbcomp/symbols/jp~ 2003-01-27 20:00:44.0 +0900
+++ xc/programs/xkbcomp/symbols/jp 2003-02-03 11:45:21.0 +0900
@@ -6,7 +6,7 @@
// $XFree86: xc/programs/xkbcomp/symbols/jp,v 3.6 2001/01/17 23:45:58 dawes Exp $
default xkb_symbols jp106 {
-
+include srvr_ctrl(xfree86)
key ESC { [ Escape ] };
// Alphanumeric section
@@ -158,5 +158,6 @@
modifier_map Shift { Shift_L,Shift_R };
modifier_map Lock { Caps_Lock };
modifier_map Control{ Control_L,Control_R };
+modifier_map Mod1 { Alt_L, Alt_R, Meta_L, Meta_R };
};
Thanks, Jens
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] 4.2.99.4 no display, locked keyboard(Radeon7500Mobility)
On Son, 2003-02-02 at 12:51, Michel Dänzer wrote:
On Son, 2003-02-02 at 06:09, hy0 wrote:
Judging from current situation, we probably should take
RADEONWaitForVerticalSync and RADEONWaitForVerticalSync2 all out of the
cursor routines.
I'd prefer fixing those functions instead. After some more thought,
polling for _VBLANK_SAVE in both is probably safest for 4.3.0.
Here's what I'm talking about, what do you think?
--
Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer
XFree86 and DRI project member / CS student, Free Software enthusiast
Index: programs/Xserver/hw/xfree86/drivers/ati/radeon_reg.h
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_reg.h,v
retrieving revision 1.24
diff -p -u -r1.24 radeon_reg.h
--- programs/Xserver/hw/xfree86/drivers/ati/radeon_reg.h 2003/01/17 19:54:03 1.24
+++ programs/Xserver/hw/xfree86/drivers/ati/radeon_reg.h 2003/02/03 03:28:42
@@ -307,6 +307,10 @@
#define RADEON_CRTC2_PITCH 0x032c
#define RADEON_CRTC_STATUS 0x005c
# define RADEON_CRTC_VBLANK_SAVE (1 1)
+# define RADEON_CRTC_VBLANK_SAVE_CLEAR (1 1)
+#define RADEON_CRTC2_STATUS 0x03fc
+# define RADEON_CRTC2_VBLANK_SAVE (1 1)
+# define RADEON_CRTC2_VBLANK_SAVE_CLEAR (1 1)
#define RADEON_CRTC_V_SYNC_STRT_WID 0x020c
# define RADEON_CRTC_V_SYNC_STRT(0x7ff 0)
# define RADEON_CRTC_V_SYNC_STRT_SHIFT 0
Index: programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c
===
RCS file: /cvs/xc/programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c,v
retrieving revision 1.84
diff -p -u -r1.84 radeon_driver.c
--- programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 2003/01/30 05:31:31 1.84
+++ programs/Xserver/hw/xfree86/drivers/ati/radeon_driver.c 2003/02/03 03:28:46
@@ -671,9 +675,13 @@ void RADEONWaitForVerticalSync(ScrnInfoP
unsigned char *RADEONMMIO = info-MMIO;
inti;
-OUTREG(RADEON_GEN_INT_STATUS, RADEON_VSYNC_INT_AK);
-for (i = 0; i RADEON_TIMEOUT; i++) {
- if (INREG(RADEON_GEN_INT_STATUS) RADEON_VSYNC_INT) break;
+/* Clear the CRTC_VBLANK_SAVE bit */
+OUTREG(RADEON_CRTC_STATUS, RADEON_CRTC_VBLANK_SAVE_CLEAR);
+
+/* Wait for it to go back up */
+for (i = 0; i RADEON_TIMEOUT/1000; i++) {
+ if (INREG(RADEON_CRTC_STATUS) RADEON_CRTC_VBLANK_SAVE) break;
+ usleep(1);
}
}
@@ -683,10 +691,14 @@ void RADEONWaitForVerticalSync2(ScrnInfo
RADEONInfoPtr info = RADEONPTR(pScrn);
unsigned char *RADEONMMIO = info-MMIO;
inti;
+
+/* Clear the CRTC2_VBLANK_SAVE bit */
+OUTREG(RADEON_CRTC2_STATUS, RADEON_CRTC2_VBLANK_SAVE_CLEAR);
-OUTREG(RADEON_GEN_INT_STATUS, RADEON_VSYNC2_INT_AK);
-for (i = 0; i RADEON_TIMEOUT; i++) {
- if (INREG(RADEON_GEN_INT_STATUS) RADEON_VSYNC2_INT) break;
+/* Wait for it to go back up */
+for (i = 0; i RADEON_TIMEOUT/1000; i++) {
+ if (INREG(RADEON_CRTC2_STATUS) RADEON_CRTC2_VBLANK_SAVE) break;
+ usleep(1);
}
}
Re: [XFree86] Bug: mga_hal and latest X
On Sun, 2 Feb 2003, John Tapsell wrote: Anyone more ideas? Anyone else have any clues? I made the (minor) changes as you mention, but nothing chances. I've attached the two files again. Did you compile this server yourself ? I've noticed that RedHat 8.0 ships with a version of mga_drv.o whcih doesn't support the hal. You aren't using that version, but has yours been similarly nobbled ? This is what I get on a setup which does use the hal: % strings /usr/X11R6/lib/modules/drivers/mga_drv.o | grep -i hal NoHal Crtc2Half HALSetDisplayStart mga_hal Matrox HAL module used Matrox HAL module not loaded - using builtin mode setup instead This card requires the mga_hal module for dual-head operation HALLib not loaded! NOT using Merged Framebuffer mode. MGAValidateMode from HALlib found the mode to be invalid. MGAValidateMode from HALlib found the mode to be invalid. MGAValidateVideoParameters from HALlib found the mode to be invalid. MGAValidateMode from HALlib found the mode to be invalid. On Fri, 31 Jan 2003, John Tapsell wrote: Hi, I think that inXFree86 Version 4.2.99.4 there is a bug in the detection of mga_hal. I had a look through the changelog for 4.2.99.4 and someone added some code to detect and check whether the mga_hal module exists. I'm probably doing this wrong, but it does seem to me, naively, that I have the mga_hal module, loading it, yet it isn't being detected. Which item in the changelog is this ? -- 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
man pages - was Re: [XFree86] Rules for an Autoreply bot
On Sat, 1 Feb 2003, Don wrote: The MGA(4) man page mentions nothing about HAL and does not even mention the G450 and G550 graphics cards. The CVS version of the man page fixes this. -- 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] Volunteering
On Sun, 2 Feb 2003, Don wrote: Exactly how does one go about volunteering to work on the web site and other documentation? For documentation, just submit changes to [EMAIL PROTECTED] If you are doing it seriously, consider installing whatever sgml tool we are currently using (possibly docbook), since the master sources for some documentation is in sgml, eg xc/programs/Xserver/hw/xfree86/doc/README.MGA is built from xc/programs/Xserver/hw/xfree86/doc/sgml/MGA.sgml I hadn't realized that this file had slipped so far behind xc/programs/Xserver/hw/xfree86/drivers/mga/mga.man Sending an email to [EMAIL PROTECTED] does not seem to have resulted in anything :) I get the feeling that the management would rather spend the time receiving and integrating submitted documentation than registering people who are interested in doing something. Remember: as a volounteer they can't easily say Don do this, Andrew do that, so there is little point in keeping a list of who might do something. -- 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
[XFree86] ctrl+alt+backspace
With Xfree CVS + kernel 2.4.20 + window maker, it makes a poweroff. Is it a bug ? Thanks ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] No Screens Found Error
Hi, ive been getting this weird error with XFree86. im pretty sure its because of the monitor but since im kinda new to linux i dont really know how to fix it. First, i had Xfree 4.1 or something. then i downloaded the latest one and upgraded to 4.2.99.3. (I had the errors the first time too). It keeps saying Screens found, but none have a usable configuration. My monitor's lowest resolution is 800x600 @ 85Hz and the highest it can go is 1280x1024 @ 60Hz. I have a geforce2 and Im running Debian (I tried it out with Slackware too and I got the same error). Ive attached my log and the Xf86config-4 file. Thanks - George XF86Config-4 Description: Binary data XFree86.0.log Description: Binary data
Re: [XFree86] ATI FireGL / IBM RC1000 / GT1000 PCI
On Sun, Feb 02, 2003 at 02:41:33AM +, [EMAIL PROTECTED] wrote: Is there, or will there, be any support for the above card... also marketted as FireGL 2 PRO PCI or HP GL-UX.. Linux detects it as: Driver with 2D/3D support is on ATI website ... http://mirror.ati.com/products/workstation/firegl2/index.html Best regards, Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard(Radeon7500Mobility)
On Son, 2003-02-02 at 06:09, hy0 wrote: On Mon, 2003-01-27 at 10:14, Nathaniel Gray wrote: I guess this doesn't happen with DRI disabled? Looks like pure luck to me that RADEONWaitForVerticalSync() ever returns when the DRM handles vertical blank interrupts. I'll look into fixing that if noone beats me to it. True, the problem doesn't occur unless DRI is enabled. This patch works for me with DRI enabled, can you (or anyone seeing the problem, for that matter) try it? There could still be an even worse problem if the vertical blank interrupt stops working for some reason (I've seen that happen after some weird 3D client crashes). Another possibility would be polling the CRTC_VBLANK_SAVE bit in the CRTC_STATUS register. Kevin, Hui, anyone interested, what do you think? It appears RADEONWaitForVerticalSync can cause some race conditon with DRM WaitVBlank routine. Not specifically with that, the DRM installs an interrupt handler which acknowledges the interrupt flag. It's sheer luck that the X driver ever sees the flag before it's acknowledged. If this is the case, Michel's patch should work. Since the display driver can also use CRTC2 (different from CRTC1's vblank condition) when DRI is enabled, this makes things more complicated. The DRM doesn't deal with the CRTC2 vblank interrupt (yet :) so this isn't urgent. Judging from current situation, we probably should take RADEONWaitForVerticalSync and RADEONWaitForVerticalSync2 all out of the cursor routines. I'd prefer fixing those functions instead. After some more thought, polling for _VBLANK_SAVE in both is probably safest for 4.3.0. The WaitForVerticalSync functions were added for avoiding flickering problem when switching between ARGB and BW cursors. BTW, I still see that problem (if very rarely) with WaitForVerticalSync, is the idea to update the registers during vertical retrace? This problem is much less severe than having WaitForVerticalSync to time out, particularly if ARGB cursor is not used as default (has this been decided?). I hope there will be a less disruptive ARGB theme by default. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] X Window doen not start
Machine Compaq Evo D315 Monitor VGA 15 PROCESSOR : AMD Athlon^(TM) XP processor 1800+1 CHIPSET : NVIDIA® nForce^(TM) chipset with TwinBank^(TM) Memory architecture,DASP preprocessor, AMD Hypertransport^(TM) I/O bus delivering throughput speeds up to 800MB/sec.Graphic Card. Integrated NVIDIA® nForce^(TM) featuring GeForce2 graphics (AGP 4X) OS Linux with Mandrake 8.2 standard OEM edition Problem: X Window does not start Thanking you for your guidance. Ramacjandran.C ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI FireGL / IBM RC1000 / GT1000 PCI
But the driver on the ATI website is x86 only, as i said in the previous mail i`m attempting to use this in an alpha-based machine, since none of the x86 machines available to me have 64bit pci, and moreso they all have components immediately beyond the 32bit slots that prevent a 64bit card from fitting. On Sun, 2 Feb 2003, Stefan Dirsch wrote: Date: Sun, 2 Feb 2003 11:55:36 +0100 From: Stefan Dirsch [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [XFree86] ATI FireGL / IBM RC1000 / GT1000 PCI On Sun, Feb 02, 2003 at 02:41:33AM +, [EMAIL PROTECTED] wrote: Is there, or will there, be any support for the above card... also marketted as FireGL 2 PRO PCI or HP GL-UX.. Linux detects it as: Driver with 2D/3D support is on ATI website ... http://mirror.ati.com/products/workstation/firegl2/index.html Best regards, Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Bug: mga_hal and latest X
On Sunday 02 February 2003 9:27 am, Dr Andrew C Aitchison wrote: Did you compile this server yourself ? I've noticed that RedHat 8.0 ships with a version of mga_drv.o whcih doesn't support the hal. You aren't using that version, but has yours been similarly nobbled ? This is what I get on a setup which does use the hal: % strings /usr/X11R6/lib/modules/drivers/mga_drv.o | grep -i hal NoHal Crtc2Half HALSetDisplayStart mga_hal Matrox HAL module used Matrox HAL module not loaded - using builtin mode setup instead This card requires the mga_hal module for dual-head operation HALLib not loaded! NOT using Merged Framebuffer mode. MGAValidateMode from HALlib found the mode to be invalid. MGAValidateMode from HALlib found the mode to be invalid. MGAValidateVideoParameters from HALlib found the mode to be invalid. MGAValidateMode from HALlib found the mode to be invalid. % strings /usr/X11R6/lib/modules/drivers/mga_drv.o | grep -i hal Crtc2Half NoHal HALLib not loaded! NOT using Merged Framebuffer mode. This card requires the mga_hal module for dual-head operation Curious no? My X server is the one that comes with the mandrake cooker. Hi, I think that inXFree86 Version 4.2.99.4 there is a bug in the detection of mga_hal. I had a look through the changelog for 4.2.99.4 and someone added some code to detect and check whether the mga_hal module exists. I'm probably doing this wrong, but it does seem to me, naively, that I have the mga_hal module, loading it, yet it isn't being detected. Which item in the changelog is this ? Hmm, I think I got confused. The entry I saw was for XFree86 4.2.99.1 (March 2002), number 46, at: http://xfree86.desiato.de/xfree86/cvs/changes.html 46. Mga driver updates: - Don't try dual-head mode with the G400 unless the mga_hal module is loaded. - Distinguish between the G400 and G450 when showing the chipset in the log. - Update the mga man page for supported hardware and dual-head support. Futher updates are needed to document all of the drivers's options. JohnFlux ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Volunteering
I get the feeling that the management would rather spend the time receiving and integrating submitted documentation than registering people who are interested in doing something. Still, it would be nice to know that if one creates documentation, that it might actually get put somewhere :) There are definitely a few things I would like to change, but if noone on the development team is interested, then there isn't much point. Remember: as a volounteer they can't easily say Don do this, Andrew do that, so there is little point in keeping a list of who might do something. Actually, I would be all for this. The people involved in the project probably have a much better idea what needs to be documented than I do. -Don ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] query
hello, i have got an Intel p4 comp, with an intel 845glly original motherboard with a 256 SDRAM. I recently loaded linux 8.0 red-hat. The problem is the sound card has been detected,but unable to initialise the device. it gives some info., as i810, which i do not understand. Awaiting Help. Thanking You, Satish ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] (no subject)
confirm 221691 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Bug: mga_hal and latest X
On Sun, 2 Feb 2003, John Tapsell wrote: % strings /usr/X11R6/lib/modules/drivers/mga_drv.o | grep -i hal Crtc2Half NoHal HALLib not loaded! NOT using Merged Framebuffer mode. This card requires the mga_hal module for dual-head operation Curious no? My X server is the one that comes with the mandrake cooker. That is more strings than Red Hat 8.0, but I suspect that Mandrake have also disabled support for the Matrox binary HAL. If you have the source I suggest that you recompile mga_drv.o comparing with the cvs version - try the one at as a starter: http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/drivers/mga/mga_driver.c?rev=1.231content-type=text/x-cvsweb-markup Beyond that I think we have a may have a political problem as much as a technical one. -- 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] ATI FireGL / IBM RC1000 / GT1000 PCI
But, is the FireGL based on a radeon, or somewhat compatible chipset.. or will it need totally new drivers writing from scratch.. Will the fact that closed source drivers are available from ATI impede efforts by the xfree team to write an opensource driver, even tho only a single architecture is supported.. especially considering these cards are shipped primarily for use in HP PA-RISC workstations. On Sun, 2 Feb 2003, Stefan Dirsch wrote: Date: Sun, 2 Feb 2003 15:28:26 +0100 From: Stefan Dirsch [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: [XFree86] ATI FireGL / IBM RC1000 / GT1000 PCI On Sun, Feb 02, 2003 at 01:44:15PM +, [EMAIL PROTECTED] wrote: But the driver on the ATI website is x86 only, as i said in the previous mail i`m attempting to use this in an alpha-based machine, since none of the x86 machines available to me have 64bit pci, and moreso they all have components immediately beyond the 32bit slots that prevent a 64bit card from fitting. There is no FireGL2 driver for Alpha available and it is very unlikely that this will ever happen. Try to use vga or vesa driver. AFAIK the board isn't even fbdev compatible. I'm not sure if vesa or fbdev makes sense at all on Alpha. Best regards, Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Xfree Problem
Hi, Rafael Felix Correa wrote: Something really weird are happening with my Xfree86. Everytime I need to start it, I need also to configure first. It shouldn´t be this way! The right thing is to configure once and start it normally after that. When i start without configuring it, appears a message like this: Coudn´t find default font fixed. Anyway, i´m sending the log file attached with this message, for more details. Thanks = === Rafael Felix Take a look at http://www.mail-archive.com/xfree86@xfree86.org/msg00426.html where I believe that your problem is discussed in the end. Best Regards Hans Öfverbeck ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ctrl+alt+backspace
Yann Le Doaré [EMAIL PROTECTED] writes: With Xfree CVS + kernel 2.4.20 + window maker, it makes a poweroff. Is it a bug ? It's a known misfeature of your motherboard. Check the bios docs. -Harald -- Harald Nordgård-Hansen, Linpro AShttp://www.linpro.no/~hnh/ PB. 375, N-1601 Fredrikstad, NorwayPhone/Fax: +47 6935 2424/25 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] No Screens Found Error
On Sun, 2 Feb 2003, George FernandeZ wrote: Hi, ive been getting this weird error with XFree86. im pretty sure its because of the monitor but since im kinda new to linux i dont really know how to fix it. First, i had Xfree 4.1 or something. then i downloaded the latest one and upgraded to 4.2.99.3. (I had the errors the first time too). It keeps saying Screens found, but none have a usable configuration. My monitor's lowest resolution is 800x600 @ 85Hz and the highest it can go is 1280x1024 @ 60Hz. I have a geforce2 and Im running Debian (I tried it out with Slackware too and I got the same error). Ive attached my log and the Xf86config-4 file. Thanks You've got problems with your config file. 1) You are using the nv driver that comes with XFree86 but you are trying to load the glx module from NVIDIA's binary release (and an old one at that). Remove /usr/X11R6/lib/modules/extensions/libglx.so so that it will use the one from Mesa that comes with XFree86 instead. 2) You've specified Option UseFBDev true indicating that a framebuffer device should be used to setup the card rather than letting the nv driver do it, yet you don't have a framebuffer device in your kernel (I wouldn't recommend it either). Remove the UseFBDev option. Alternatively, you could install the binary drivers from NVIDIA's web site. I'd recommend version 3123 because 4191 had some problems. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X Window doen not start
On Sun, 2 Feb 2003, Ramachandran` wrote: Machine Compaq Evo D315 Monitor VGA 15 PROCESSOR : AMD Athlon^(TM) XP processor 1800+1 CHIPSET : NVIDIA® nForce^(TM) chipset with TwinBank^(TM) Memory architecture,DASP preprocessor, AMD Hypertransport^(TM) I/O bus delivering throughput speeds up to 800MB/sec.Graphic Card. Integrated NVIDIA® nForce^(TM) featuring GeForce2 graphics (AGP 4X) OS Linux with Mandrake 8.2 standard OEM edition Problem: X Window does not start Thanking you for your guidance. Ramacjandran.C I can't really comment on this much unless you provide the /var/log/XFree86.0.log. It may be that the version of XFree86 that ships with your distribution does not support nForce. I would recommend upgrading to 4.2.99.4 available from ftp.XFree86.org. It's definitely supported in that version. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI FireGL / IBM RC1000 / GT1000 PCI
On Sun, Feb 02, 2003 at 07:14:10PM +, [EMAIL PROTECTED] wrote: But, is the FireGL based on a radeon, or somewhat compatible chipset.. or will it need totally new drivers writing from scratch.. The new FireGL boards are Radeon based (FireGL 8x000 and later), the old FireGL boards like yours (FireGL 1 and FireGL /2/3/4) were IBM chipset based. Needs rewrite from scratch and it's unlikely that you'll get the documentation for this from IBM. :-( Will the fact that closed source drivers are available from ATI impede efforts by the xfree team to write an opensource driver, even tho only a single architecture is supported.. especially considering these cards are shipped primarily for use in HP PA-RISC workstations. Maybe you should better ask HP/ATI directly? Best regards, Stefan Public Key available Stefan Dirsch (Res. Dev.) SuSE Linux AG Tel: 0911-740530 Deutschherrnstr. 15-19 FAX: +49 911 741 77 55D-90429 Nuernberg http://www.suse.deGermany ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Matrox G550 + DVI + HAL + DPMS + ViewSonic LCD + FreeBSD
I have a Matrox G550 + 2 Matrox G450 PCI cards all with DVI output. All three are connected to Viewsonic LCD's via DVI. I am running 4.2.1 on FreeBSD 5.0 compiled from source with the Matrox HAL libraries. Any time I try to send the monitors into sleep or poweroff, they just end up displaying a series of colored vertical bands that vary depending on what my desktop looks like. I have Options DPMS in my config file. I know Andrew said that DPMS was working with his G550 and was wondering where the difference likely is. Does it work better with 4.2.99.x? I did not have this problem, to my knowledge, with the Radeon 7000 that was installed in this system previously. -Don ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] KDE screensaver causes X server abort on Savage
Regarding: KDE screensaver causes X server abort on Savage Email: [EMAIL PROTECTED] XFree86 Version: 4.2.99.4 (Custom Build: 4.2.99.4-20030121.4 Redhat) OS: RedHat Rawhide (post 8.0) Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: S3 Inc. VT8751 [ProSavageDDR P4M266] VGA Controller (--) SAVAGE(0): Chip: id 8d04, ProSavage DDR-K (--) SAVAGE(0): Engine: ProSavage (--) SAVAGE(0): mapping MMIO @ 0xdfe8 with size 0x8 (==) SAVAGE(0): Using gamma correction (1.0, 1.0, 1.0) (--) SAVAGE(0): probed videoram: 32768k (--) SAVAGE(0): Detected current MCLK value of 14.318 MHz Description: This is a pre-release version of XFree86, and is not supported in any way. Bugs may be reported to [EMAIL PROTECTED] and patches submitted to [EMAIL PROTECTED] Before reporting bugs in pre-release versions, please check the latest version in the XFree86 CVS repository (http://www.XFree86.Org/cvs) XFree86 Version 4.2.99.4 (Custom Build: 4.2.99.4-20030121.4) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 20 January 2003 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.20 i686 [ELF] Build Host: snape.local Module Loader present OS Kernel: Linux version 2.4.20 ([EMAIL PROTECTED]) (gcc version 3.2.1 20021207 (Red Hat Linux 8.0 3.2.1-2)) #1 Thu Dec 19 07:28:25 GMT 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: Mon Feb 3 01:51:56 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Targa (**) | |--Device Savage (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbLayout gb (**) XKB: layout: gb (==) Keyboard: CustomKeycode disabled (**) 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.2 XFree86 Video Driver: 0.6 XFree86 XInput driver : 0.4 XFree86 Server Extension : 0.2 XFree86 Font Renderer : 0.4 (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.99.4, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.4 (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.99.4, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.6 (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 1106,3116 card 1106, rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b091 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:11:0: chip 1106,3074 card 1106, rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:2: chip 1106,3038 card 0925,1234 rev 1b class 0c,03,00 hdr 00 (II) PCI: 00:11:3: chip 1106,3038 card 0925,1234 rev 1b class 0c,03,00 hdr 00 (II) PCI: 00:11:4: chip 1106,3038 card 0925,1234 rev 1b class 0c,03,00 hdr 00 (II) PCI: 00:11:5: chip 1106,3059 card 1106,4161 rev 30 class 04,01,00 hdr 00 (II) PCI: 00:12:0: chip 1106,3065 card 1106,0102 rev 70 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 5333,8d04 card 5333,8d04 rev 00 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0 0x - 0x (0x0) MX[B] (II) PCI-to-PCI bridge: (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x000c (VGA_EN is set) (II) Bus 1 non-prefetchable memory range: [0] -1 0 0xdfd0 - 0xdfef (0x20) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0 0xcfb0 - 0xdfbf (0x1010) MX[B] (II) PCI-to-ISA bridge: (II) Bus -1: bridge is at (0:17:0), (0,-1,-1), BCTRL: 0x0008 (VGA_EN is set) (--) PCI:*(1:0:0) S3 Inc. VT8751 [ProSavageDDR P4M266] VGA Controller rev 0, Mem @
[XFree86] problems with X
Hi, facts: Red Hat 8 Dell Precision 410 32mb fireGL AGP video Card Gateway FPD1520 Monitor Problem: When i try to start X, i get the following error message: Fatal server error: no screens found XIO: fatal IO error 104 (Connection reset by peer) on X server :0.0 after 0 requests (0 known proccessed) with 0 events remaining. Thanks, Kashif Mumtaz _ The new MSN 8: advanced junk mail protection and 2 months FREE* http://join.msn.com/?page=features/junkmail ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] [Xfree86]X server crash
Hi, sorry for delay. I changed Driver to vesa in XF86Config-4.Still there is problem. In log file it displays:-- VESA(0):No Display subsection in Screen section screen0 for depth/fbbpp 8/8 Screen(s) found,but none have a usable configuration. Actually what does it mean? - sowmya -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Ramesh K. Sistla Sent: Friday, January 31, 2003 5:17 PM To: [EMAIL PROTECTED] Subject: RE: [XFree86] [Xfree86]X server crash Hi! Change the Driver field to vesa and start your X. Section Device Identifier Intel 810 Driver i810 BoardName Unknown VideoRam 16384 This should work. Intel suggests this. Let me know. hth -- :-) ramesh k. sistla The Prayer of India: lokah samastah suKhino Bhavantu -- Let the entire world be in peace! ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 **Disclaimer** Information contained in this E-MAIL being proprietary to Wipro Limited is 'privileged' and 'confidential' and intended for use only by the individual or entity to which it is addressed. You are notified that any use, copying or dissemination of the information contained in the E-MAIL in any manner whatsoever is strictly prohibited.
[XFree86] Lockup with xvideo in i810 driver
I have been trying to resolve video problems on my i815em based laptop for a little while now. The main problem I see with XF86 from recent cvs is with xvideo. Trying to use a video player with xvideo output immediately crashes the X server and hangs the machine for a minute while it sends errors about i810_wait_ring to the syslog. Afterwards the server may need a cold reboot to restart. Sometimes reloading the i810 and agpgart modules is enough. The error messages are below. This is the same behavior I reported in the middle of December here: http://www.spinics.net/lists/xf-xpert/msg07993.html I am using kernel 2.4.20-rc1, but I saw similar behavior when testing even newer kernels. The lockup occurs with the i810.o kernel modules from both the kernel source and the XF86 source tree. The lockup is a new change from around November or early December. Before that time, there was no xvideo lockup, but I could not get the overlay in the correct position. See http://marc.theaimsgroup.com/?l=xfree-xpertm=103889406114561w=2 In addition to xvideo problems, I have long experienced pixmap corruption problems on the laptop's LCD, but curiously not when using the laptop's video output to an external monitor. Please let me know if there are any patches I can test or any way to help debug the problem. I am including parts of the syslog showing the lockup as well as attaching my config file and log file. Thanks, Leif = dmesg == Linux agpgart interface v0.99 (c) Jeff Hartmann agpgart: Maximum main memory to use for agp memory: 202M agpgart: agpgart: Detected an Intel i815 Chipset. agpgart: detected 4MB dedicated video ram. agpgart: AGP aperture is 64M @ 0xf800 [drm] AGP 0.99 aperture @ 0xf800 64MB [drm] Initialized i810 1.2.1 20020211 on minor 0 mtrr: base(0xf800) is not aligned on a size(0x18) boundary [drm:i810_wait_ring] *ERROR* space: 65520 wanted 65528 [drm:i810_wait_ring] *ERROR* lockup [drm:i810_wait_ring] *ERROR* space: 65512 wanted 65528 [drm:i810_wait_ring] *ERROR* lockup [drm:i810_wait_ring] *ERROR* space: 65504 wanted 65528 [drm:i810_wait_ring] *ERROR* lockup [drm:i810_wait_ring] *ERROR* space: 65496 wanted 65528 [drm:i810_wait_ring] *ERROR* lockup [drm:i810_wait_ring] *ERROR* space: 65488 wanted 65528 [drm:i810_wait_ring] *ERROR* lockup [drm:i810_wait_ring] *ERROR* space: 65480 wanted 65528 [drm:i810_wait_ring] *ERROR* lockup ... etc ... xfconfig.gz Description: GNU Zip compressed data xflog.gz Description: GNU Zip compressed data
