CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 12:12:01 Log message: Fix random crashes when running xkbcomp -C to generate a C source xkb description due incorrect buffer size calculation. strlen(tmp+1) = strlen(tmp)+1 Modified files: xc/lib/xkbfile/: cout.c Revision ChangesPath 3.8 +2 -2 xc/lib/xkbfile/cout.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 17:45:22 Log message: 819. Build fix for the DRM on FreeBSD 5.0-current (#5603, Eric Anholt). Modified files: xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/: drm_os_freebsd.h Revision ChangesPath 1.3 +4 -0 xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_os_freebsd.h ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 17:48:38 Log message: 821. Work around an AGP bug in the AlphaServer ES45 by padding each ring buffer packet in the radeon drm with NOPs to cache line boundaries. This is only done for Alpha platforms (#5605, Jeff Wiedemeier). Modified files: xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/: radeon_cp.c radeon_drv.h Revision ChangesPath 1.5 +1 -0 xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/radeon_cp.c 1.2 +37 -3 xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/radeon_drv.h ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 18:18:19 Log message: 823. Add an Ethiopic TTF and OTF font (#A.1549, Daniel Yacob). Modified files: xc/config/cf/: X11.tmpl xc/fonts/scaled/: Imakefile Added files: xc/fonts/scaled/Ethiopic/: GohaTibebZemen.otf GohaTibebZemen.ttf Imakefile license.txt Revision ChangesPath 1.192 +4 -1 xc/config/cf/X11.tmpl 3.5 +7 -3 xc/fonts/scaled/Imakefile ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 18:22:14 Log message: 825. Add some locales required for the OpenI18N compliance test (#A.1550, Leon Ho). Modified files: xc/nls/: locale.alias Revision ChangesPath 1.61 +7 -1 xc/nls/locale.alias ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 18:32:01 Log message: 826. Define Alt/Meta modifiers for the jp106 XKB layout, and include server control definitions (#A.1562, Jens Petersen). Modified files: xc/programs/xkbcomp/symbols/: jp Revision ChangesPath 3.8 +3 -2 xc/programs/xkbcomp/symbols/jp ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 18:32:48 Log message: 827. Include server control definitions in some XKB maps that were missing them (based on #A.1562, Jens Petersen). Modified files: xc/programs/xkbcomp/symbols/: czsk dvorak vn Revision ChangesPath 1.9 +2 -1 xc/programs/xkbcomp/symbols/czsk 3.9 +2 -1 xc/programs/xkbcomp/symbols/dvorak 1.5 +3 -1 xc/programs/xkbcomp/symbols/vn ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 18:40:24 Log message: 829. R128 build fix on big endian platforms (#A.1565, George Staikos). Modified files: xc/programs/Xserver/hw/xfree86/drivers/ati/: r128_video.c Revision ChangesPath 1.25 +9 -9 xc/programs/Xserver/hw/xfree86/drivers/ati/r128_video.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/03 19:02:00 Log message: 831. Resync with DRI mesa-4-0-4 branch: - Don't inflate relative vblank sequence numbers on repeated calls (e.g., when interrupted by a signal) (Michel Dänzer). - Fix size of VERTEX2 ioctl struct (Egbert Eich). Modified files: xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/: drm_dma.h xc/programs/Xserver/hw/xfree86/os-support/linux/drm/: xf86drm.c xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/: drm_dma.h xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/: radeon_drm.h Revision ChangesPath 1.4 +55 -14 xc/programs/Xserver/hw/xfree86/os-support/bsd/drm/kernel/drm_dma.h 1.31 +2 -1 xc/programs/Xserver/hw/xfree86/os-support/linux/drm/xf86drm.c 1.7 +1 -0 xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/drm_dma.h 1.2 +1 -1 xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/radeon_drm.h ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: SunRay driver for XFree86
Hi Markus, That's good to hear. I'll be glad to read through your docs when I have some time. MK So the question I'd like to ask here is, can someone provide us with a MK few pointers to get started with understanding how a SunRay driver could/ MK should possibly interface with the XFree86 X server. I think you want to start with a dumb X server with either Mark's or Keith's shadowfb code. You'd simply blit to the FreeRay in the shadowfb update code. If the 'Ray provides primitives for Screen-Screen blits or similar, you'd probably also want to wrap some of the GCOps after they get through shadowfb. /I/'d start with the KDrive server and either of the fbdev or the vesa drivers and then change all the accel code. But I know that some people on this list would differ. Good luck, Juliusz ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Keys missing from fr mapping on XFree86 CVS
Hi, Well, replying my own mail, for the record, it appears that I was missing Option XkbRules xfree86 From the XF86Config Dunno why it works before though. It works fine now anyway. Cheers, Olivier. On Sun, 2003-02-02 at 23:09, Olivier Fourdan wrote: 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
Patch: hang in multithreaded mode when keymap changes
Hi, here is a fix for the hang described in the subject line. I have difficulties to make a simple reproducer program, from source code inspection is it clear enough that the UnlockDisplay is required at the end of the XkbGetMapChanges ? Thanks Jose Luu *** xc/lib/X11/XKBGetMap.c Mon Feb 3 17:51:13 2003 --- xc/lib/X11/XKBGetMap.c.old Mon Feb 3 19:31:13 2003 *** *** 974,979 --- 974,980 UnlockDisplay(dpy); return status; } + UnlockDisplay(dpy); return Success; } ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xterm can hang, CPU bound
| From: Thomas Dickey [EMAIL PROTECTED] | On Sun, Feb 02, 2003 at 03:42:35AM -0500, D. Hugh Redelmeier wrote: | 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). | hmm - running on Slackware 7.1, I don't see any CPU load. Interesting. I would not expect this to depend on which OS you used (unless it was VMS -- there are #ifdefs for vms in the relevant xterm code). But I didn't track down all possible OS dependencies. One possible system dependency: the echo command may not generate an escape on your all systems. When you run the command, the console should show a blank like and a prompt for the next shell command. If you see anything on that blank line, the echo didn't generate the sequence I intended. When you do the mouse click, you will get a few random characters echoed. I just tried KNOPPIX. It hangs burning CPU. It uses XFree86 4.2.1.1 (Debian 4.2.1-4). It hangs on all the Red Hats that I've tried here (7.0, 7.2, 7.3, 8.0, phoebe). I tried to install OpenBSD 3.0 to test it but wasted half a day on installation issues I haven't solved :-) | I'm using | a test-screen in vttest to exercise this feature. Do you mean the feature of hanging, or the feature used properly? | But I do have a | Redhat 8.0 for testing - will see if I can reproduce this problem there. I suspect that any Red Hat would do. | 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. The feature is used by the JOVE text editor. That is how I stumbled across this problem. What do you think about the approach I suggested (act as if a default CSI...T sequence had been received until the real one is)? Perhaps the default should only be used after some timeout. I suspect that the CPU-burning loop happens between the sending of the mouse message and the receipt of the CSI...T even when all is well. If so, I'd say this is a bug too. Thanks, Hugh Redelmeier [EMAIL PROTECTED] voice: +1 416 482-8253 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: What happened to CVSWeb?
Mark Vojkovich wrote: It's not there anymore. Mark. Seems to be there now, temporary problem? http://cvsweb.xfree86.org/cvsweb/ -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Xcursor.h path in 4.2.99.4?
It seems that Xcursor.h is installed in /usr/include/X11/Xcursor/Xcursor.h in 4.2.99.4. Is this intentional? Why isn't it directly in X11? -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Xcursor.h path in 4.2.99.4?
Around 19 o'clock on Feb 3, Kevin Brosius wrote: It seems that Xcursor.h is installed in /usr/include/X11/Xcursor/Xcursor.h in 4.2.99.4. Is this intentional? Why isn't it directly in X11? Many libraries create separate directories for their include files, and so I just followed this convention. I can see arguments that this library shouldn't ever need additional headers and so might reasonably live at the top level. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xterm can hang, CPU bound
| From: Thomas Dickey [EMAIL PROTECTED]
| hmm - running on Slackware 7.1, I don't see any CPU load.
A friend just confirmed this problem (100% cpu) on his Slackware 7.1.0
system. strace says:
select(5, [3 4], [], NULL, {0, 0}) = 1 (in [3], left {0, 0})
select(4, [3], [], [], {0, 0}) = 1 (in [3], left {0, 0})
select(4, [3], [], [], {0, 0}) = 1 (in [3], left {0, 0})
select(4, [3], [], [], {0, 0}) = 1 (in [3], left {0, 0})
over and over.
Perhaps you use a shell with a different echo.
Hugh Redelmeier
[EMAIL PROTECTED] voice: +1 416 482-8253
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: [patch for 4.3] define Alt/Meta modifiers for jp106 kbd
On Mon, Feb 03, 2003 at 12:04:12PM +0900, Jens Petersen wrote: 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? I've committed it -- thanks. I've also added the Ctrl-Alt-* maps to a few others that were missing them. I'm not sure if any more need them. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: xterm can hang, CPU bound
| From: Thomas Dickey [EMAIL PROTECTED]
| Reply-To: [EMAIL PROTECTED]
| To: [EMAIL PROTECTED]
| Subject: Re: xterm can hang, CPU bound
|
| On Mon, Feb 03, 2003 at 07:59:49PM -0500, D. Hugh Redelmeier wrote:
| Might be worth doing an strace. On RHL8.0, I get:
|
| select(5, [3 4], [], NULL, {0, 0}) = 1 (in [3], left {0, 0})
| select(4, [3], [], [], {0, 0}) = 1 (in [3], left {0, 0})
| select(4, [3], [], [], {0, 0}) = 1 (in [3], left {0, 0})
| select(4, [3], [], [], {0, 0}) = 1 (in [3], left {0, 0})
|
| Notice that each of these select calls has a timeout specified, and
| that timeout is 0 seconds. So these calls never block. Besides that,
| there is something available on file descriptor 3 but it is never
| being accessed.
|
| What does strace show on your older system?
|
| I guess the comparable chunks are like this:
|
| select(6, [4 5], [], NULL, {0, 0}) = 1 (in [4], left {0, 0})
| select(5, [4], [], [], {0, 0}) = 1 (in [4], left {0, 0})
| select(5, [4], [], [], {0, 0}) = 1 (in [4], left {0, 0})
| select(5, [4], [], [], {0, 0}) = 1 (in [4], left {0, 0})
That sure looks like it ought to eat all available CPU.
None of those calls should block.
| | What do you think about the approach I suggested (act as if a default
| | CSI...T sequence had been received until the real one is)? Perhaps
| | the default should only be used after some timeout.
| |
| | it's not entirely clear to me what the sequence would be here.
|
| Two obvious ones: the whole xterm region, or an empty region at the
| point of the cursor. I'd vote for the empty region: no information
| about a subsequent click is lost (the answer will be forced to be the
| long form).
|
| Clearly func should be non zero in either case: we don't want to
| cancel the mode.
|
| I do suggest that the default only be installed after a brief timeout.
| How long? A tenth of a second feels about right.
|
| I also suggest that the default be replaced if and when the explicit
| CSI...T sequence is received.
|
| It sounds as if you're proposing to make it return a dummy escape sequence -
| or make the escape sequence terminate automatically after a short time -
| but it's not clear to me
Sorry, I'll try to be clearer.
When a button is pressed in mouse hilite tracking mode,
xterm sends ESC [ M Cb Cx Cy to the PTY
xterm awaits ESC ... T from the PTY, doing nothing else.
The ESC [ Ps ; Ps ; Ps ; Ps ; Ps T informs xterm:
func: non zero to initiate hilite tracking and 0 to abort
startx, starty: starting location for highlighted region
firstrow, lastrow: limits for tracking
I'm proposing that until the ESC ... T message is received from
through the PTY, the xterm should act as if it had received something
like: ESC [ 1 ; curx ; cury ; currow ; currow T
This would be provisional. When (if) an ESC ... T is actually received,
it should override this default.
Thus xterm would not hang. There should be no compatibility problem
UNLESS the button release arrives before the actual ESC ... T. The
reason I suggested a small delay before acting on the default is to
avoid the race most times.
The ESC ... T is not sent from xterm. So no, I'm not suggesting that
it send it now. Only that it act as if it received one.
Note: the provisional ESC ... T sequence I propose has not been
tested. Maybe something is not quite right. I hope the idea is OK.
Perhaps the firstrow/lastrow should cover the whole xterm window.
Hugh Redelmeier
[EMAIL PROTECTED] voice: +1 416 482-8253
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
XCursor: left_ptr_watch does not change with theme
With my attempts at theming Xcursor I have run into a deadlock. No matter what themes I use or create, none of them correctly change left_ptr_watch. Instead, the theme will default onto the left_ptr_watch from whiteglass. I did notice that in xc/lib/Xcursor/library.c that left_ptr_watch seems to be missing from the array that contains the other defined cursors. Is this a known problem? ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
ANSI trigraphs enabled by default in X sources
Is there anywhere in the X source code that *gasp* uses ANSI trigraphs and relies on this broken^Wwonderful feature of ANSI C being enabled? ;o) I ask because I just discovered that by default trigraphs are enabled in the sources. I patch I am applying contains the string (???) which is how I discovered this. I'm wondering wether disabling trigraphs by default in stock sources is considered OK, or if I should have my patch escape the trigraph sequences to not be tokenized instead? Changing the (???) to something else is also an option, but I'd prefer to do one of the above instead, and just wondered what common consensus might be. TIA -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: ANSI trigraphs enabled by default in X sources
Around 0 o'clock on Feb 4, Mike A. Harris wrote: Is there anywhere in the X source code that *gasp* uses ANSI trigraphs and relies on this broken^Wwonderful feature of ANSI C being enabled? ;o) I sure hope not. I've certainly never seen any such code (and would have fixed it if I had). I'm wondering wether disabling trigraphs by default in stock sources is considered OK, or if I should have my patch escape the trigraph sequences to not be tokenized instead? You should fix your patch to not use that trigraph. Does GCC have a mode that pukes if it finds any trigraphs? That would be a better option than disabling them; X gets built with other compilers still, some of which might not have an option to disable trigraphs. -keith ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: [XFree86] [Xfree86]X server crash
we would need you full XF86Config-4 in order to help... The message means that in the screen section there are no display subsection corresponding to the combination graphic device / monitor / default depth Lionel --- Sowmya Adiga [EMAIL PROTECTED] wrote: 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. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XF86Config error
The problem is rather clear: your input device section for your mouse must be revised... snip (**) Option Protocol IMPS/2 (**) Mouse0: Protocol: IMPS/2 (**) Option CorePointer (**) Mouse0: Core Pointer (**) Option Device /dev/input/mice (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such device. (EE) Mouse0: cannot open input device (EE) PreInit failed for input device Mouse0 (II) UnloadModule: mouse (II) Keyboard Keyboard0 handled by legacy driver (WW) No core pointer registered No core pointer /snip Lionel --- [EMAIL PROTECTED] wrote: I'm encountering the following error with Redhat Linux 7.0. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] [Xfree86]X server crash
Hi Lionel, I am sending the log file Sowmya adiga -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Lionel Lecoq Sent: Monday, February 03, 2003 3:00 PM To: [EMAIL PROTECTED] Subject: RE: [XFree86] [Xfree86]X server crash we would need you full XF86Config-4 in order to help... The message means that in the screen section there are no display subsection corresponding to the combination graphic device / monitor / default depth Lionel --- Sowmya Adiga [EMAIL PROTECTED] wrote: 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. ** ** __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 XF86Config-4 Description: Binary data **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] DDC problem with g550
Hello everybody. I have a problem with my Matrox G550 and Nokia 445Xpro monitor. Xfree86 (4.2.1) on Linux (slackware 8.1) and FreeBSD 4.7 doesn't detect monitor info. Nokia 445xpro is connected to the analog output. (II) MGA(0): I2C bus DDC initialized. (II) MGA(0): I2C device DDC:ddc2 registered. (II) MGA(0): I2C device DDC:ddc2 removed. (II) MGA(0): I2C Monitor info: (nil) (II) MGA(0): end of I2C Monitor info (--) MGA(0): No DDC signal (II) MGA(0): DDC Monitor info: (nil) (II) MGA(0): end of DDC Monitor info I have searched with google and I have found the following thread http://www.spinics.net/lists/xf-xpert/msg06036.html I would like to know if this problem will be solved in 4.3.0 release. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] DDC problem with g550
On Mon, 3 Feb 2003, Marco Berizzi wrote: Hello everybody. I have a problem with my Matrox G550 and Nokia 445Xpro monitor. Xfree86 (4.2.1) on Linux (slackware 8.1) and FreeBSD 4.7 doesn't detect monitor info. Nokia 445xpro is connected to the analog output. (II) MGA(0): I2C bus DDC initialized. (II) MGA(0): I2C device DDC:ddc2 registered. (II) MGA(0): I2C device DDC:ddc2 removed. (II) MGA(0): I2C Monitor info: (nil) (II) MGA(0): end of I2C Monitor info (--) MGA(0): No DDC signal (II) MGA(0): DDC Monitor info: (nil) (II) MGA(0): end of DDC Monitor info I have searched with google and I have found the following thread http://www.spinics.net/lists/xf-xpert/msg06036.html I would like to know if this problem will be solved in 4.3.0 release. It is likely that it will. I discovered that I had the problem too, so my incentive to fix it increased. If the first two methods of DDC detection fail on normal operation, X now attempts the method used by X -configure, which seems to work on most of the problem systems. If this breaks your setup, then Option NoDDC will make the server behave the way it did before. -- 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] Trident cyber 9385 still not works in 4.2.99
Hello, I have just tried xfree 4.2.99 on my thinkpad with trident cyber 9385. The bug that causes scrambled screen is still there. The bug started in Xfree 4 (xfree 3.3.x works fine). The screen is scrambled due to wrong refresh rates sent to lcd. I have tried with an external monitor. If eg. I use 800x600x60hz I obtain a 800x600107hz which is wrong. Please correct this bug or disable support for cyber 9385 forever. Do not say a chip is supported if in reality is not. Thanks in advance for interest. -- Mario Giammarco [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Radeon VE and only a pal TV output.
Hello, I have a computer with Radeon VE and only a pal TV set as output. I am trying to configure it but I have not yet found the right options (eg.: crtscreen) and right modeline to view xfree on my TV. Has someone already do it? Thanks you in advance! -- Mario Giammarco [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident cyber 9385 still not works in 4.2.99
On Mon, Feb 03, 2003 at 12:31:43 +0100, Mario Giammarco wrote: Hello, I have just tried xfree 4.2.99 on my thinkpad with trident cyber 9385. Which 4.2.99 ? The bug that causes scrambled screen is still there. Scrambled screen - not heard of that one. The bug started in Xfree 4 (xfree 3.3.x works fine). The screen is scrambled due to wrong refresh rates sent to lcd. I have tried with an external monitor. If eg. I use 800x600x60hz I obtain a 800x600107hz which is wrong. Please correct this bug or disable support for cyber 9385 forever. Do not say a chip is supported if in reality is not. I'm afraid it works on a lot of 9385's so it's not gonna get removed. Make sure your trying the current CVS, and send me a log if you've still got problems. Alan. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] xserver
Hi, Álvaro Castro wrote: Hi! I'm having problems with my debian... I don't know if this is a server crash or what it is, but I've been trying different combinations of values and it doesn't work... I followed Nvidia's instructions for their drivers... Take a look at: http://www.mail-archive.com/xfree86@xfree86.org/msg00758.html Best Regards Hans Öfverbeck ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Trident cyber 9385 still not works in 4.2.99
Mario Giammarco wrote: I have just tried xfree 4.2.99 on my thinkpad with trident cyber 9385. I've got one of them - at least I think I have. Is it a 760ED? The bug that causes scrambled screen is still there. There's some problems, but they're in stretching and Xvideo, nothing as bad as a scrambled screen. The bug started in Xfree 4 (xfree 3.3.x works fine). I had some problems when upgrading to version 4. You might need to tweak your XF86Config-4. Here's the important parts of mine, which are working for 4.2.99.3 (4.2.99.4 has an additional bug in it): Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model HorizSync 31.5-48.5 EndSection Section Device ### Available Driver options are:- ### Values: i: integer, f: float, bool: True/False, ### string: String, freq: f Hz/kHz/MHz ### [arg]: arg optional #Option SWcursor # [bool] #Option PciRetry # [bool] #Option NoAccel # [bool] #Option SetMClk # freq #Option MUXThreshold # i #Option ShadowFB # [bool] #Option Rotate# [str] #Option VideoKey # i #Option NoMMIO# [bool] #Option NoPciBurst# [bool] #Option MMIOonly # [bool] #Option CyberShadow # [bool] #Option CyberStretch # [bool] #Option XvHsync # i #Option XvVsync # i #Option XvBskew # i #Option XvRskew # i #Option FpDelay # i #Option Display1400 # [bool] #Option Display # [str] #Option GammaBrightness # [str] Identifier Card0 Driver trident VendorName Trident Microsystems Option XvHsync 9 # (6-7 gets rid of the blue strip. 8-9 brings it on at right, # but 9 fixes fullscreen wrapping problem on left) BoardName TGUI 9660/938x/968x BusID PCI:0:3:0 EndSection Section Screen Identifier Screen0 Device Card0 MonitorMonitor0 DefaultDepth 16 SubSection Display Depth 1 EndSubSection SubSection Display Depth 4 EndSubSection SubSection Display Depth 8 EndSubSection SubSection Display Depth 15 EndSubSection SubSection Display Depth 16 Modes 1024x768 640x480 EndSubSection SubSection Display Depth 24 EndSubSection EndSection Glyn -- Mad Eddie makes exceedingly good cakes ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Rules for an Autoreply bot
Don writes: We need a FAQ more urgently than a bot. bah Andrew is right. An FAQ would be a better start. Hell current man pages would also be nice :) The MGA(4) man page mentions nothing about HAL and does not even mention the G450 and G550 graphics cards. I would be happy to document anything people feel should be documented. I would like to thank John that he stepped forward and started a project to help us cope with the load of support mails we receive. An auto reply bot is nice, but it will require a lot of tuning before it gets really useful. For example the message: (WW) Open APM failed (/dev/apm_bios)... appears in the log of any desktop if APM isn't enabled. However it is completely harmless in almost any case. Setting up a FAQ can be the step prior to setting up a bot. John, if you don't mind you could convert the entries in the bot into a FAQ which we can be easily be extended. When we have a well established FAQ you can start building a bot pointing people to the correct entry. A while ago somebody had set up a Wiki for XFree86. I'm not sure if it is still working, in fact I've nver tried it. This may be a good starting point to build the FAQ. I do agree with the call for better man pages ;-) Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Lockup with xvideo in i810 driver
I guess this is some kind of design fault in i810 driver. Generally it happens when load on X is high enough (or is it peak load that's high enough?). Usually KDE is involved, but there was someone running StarOffice. I've seen this on FreeBSD. Other people've seen this on Linuxes. XFree86 can be 4.2.* or CVS. Disabling Acceleration helps but is not an ultimate solution. Disabling SolidFillRects (advised here once or twice) didn't help me. I get this always when switching to text console and anything KDE'ish being active. And there're always messages lockup/server: lockup and (space) wanted 65528. Leif Jensen wrote: 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. [...] [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 ... ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Re: DDC problem with g550
On Mon, 3 Feb 2003, Marco Berizzi wrote: Thanks a lot Andrew for the reply. I'm available to test any patch. It is in CVS. It is change number 764, and made it in before the 4.2.99.4 tag (20 January 2003), so any CVS version which reports XFree86 Version 4.2.99.5 will include it. If the log file reports XFree86 Version 4.2.99.4 it probably doesn't include this patch. -- 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] Bug: mga_hal and latest X
John Tapsell writes: % 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. This looks very much like the required loading code is not compiled in. The hal lib is not required when compiling the driver with support for it. It is also not required to have it at run time. Therefore I don't see a reason not to compile in hal support. On the other hand there have been several issues with hal lib in the past which may have caused distros to drop support for it to reduce the support load. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Volunteering
Dr Andrew C Aitchison writes: 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 For creating or extending README files this may actually be necessary. Although I'd strongly vote for replacing SGML for something less awkward - less meta, more text. In my opinion it is the biggest obstacle in getting people to write documentation. For a FAQ it is clearly overkill. I'd suggest to start with something simple. I just checked: we have a wiki set up which hasn't been used at all so far. My suggestion is to use the Wiki to get started on an FAQ. It can be amended and modified by more than one person. Once entries have become stable they can be set up to be read only. For the beginning I'd suggset to watch the xfree86@ maling list and see what are the most common problems - and their solution. 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. Hm, atually the few people involved in committing patches don't find the time to do anything else any more. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] XFree86 on Shuttle SV25 (VIA PN133 Twister chipset, S3 Savage 4 onboard)
Regarding: XFree86 on Shuttle SV25 (VIA PN133 Twister chipset, S3 Savage 4 onboard) Email: [EMAIL PROTECTED] XFree86 Version: XFree86 Version 4.2.1 OS: FreeBSD 5.0-Rel. Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: Integrated video on VIA PN133 chipset (S3 Savage 4) Description: XFree doesn't recognize the video card, though it should imho actually be supported: 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-RC 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: Fri Jan 31 16:52:30 2003 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 neomagic sis trident tseng vesa vmware Fatal server error: XFree86 has found a valid card configuration. Unfortunately the appropriate data has not been added to xf86PciInfo.h. Please forward 'scanpci -v' output to XFree86 support team. scanpci -v gives the following: pci bus 0x cardnum 0x00 function 0x00: vendor 0x1106 device 0x0605 VIA Device unknown STATUS0x2210 COMMAND 0x0006 CLASS 0x06 0x00 0x00 REVISION 0x00 BASE0 0xe808 addr 0xe800 MEM PREFETCHABLE pci bus 0x cardnum 0x01 function 0x00: vendor 0x1106 device 0x8605 VIA Device unknown STATUS0x2230 COMMAND 0x0007 CLASS 0x06 0x04 0x00 REVISION 0x00 HEADER0x01 LATENCY 0x00 PRIBUS0x00 SECBUS 0x01 SUBBUS 0x01 SECLT 0x00 IOBASE0xf000 IOLIM 0xfff SECSTATUS 0x NOPREFETCH_MEMBASE 0xec00 MEMLIM 0xedff PREFETCH_MEMBASE 0xe000 MEMLIM 0xe7ff NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT VGA_EN ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x07 function 0x00: vendor 0x1106 device 0x0686 VIA VT 82C686 MVP4 ISA Bridge CardVendor 0x1106 card 0x (VIA, Card unknown) STATUS0x0210 COMMAND 0x0087 CLASS 0x06 0x01 0x00 REVISION 0x40 BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00 BYTE_00x108 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x07 function 0x01: vendor 0x1106 device 0x0571 VIA VT 82C586 MVP3 IDE Bridge CardVendor 0x1106 card 0x0571 (VIA, Card unknown) STATUS0x0290 COMMAND 0x0007 CLASS 0x01 0x01 0x8a REVISION 0x06 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00 BASE4 0xc001 addr 0xc000 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x00 INT_LINE 0xff BYTE_00x3a09f20b BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x07 function 0x02: vendor 0x1106 device 0x3038 VIA VT 82C586 MVP3 USB Controller CardVendor 0x0925 card 0x1234 (Card unknown) STATUS0x0210 COMMAND 0x0007 CLASS 0x0c 0x03 0x00 REVISION 0x1a BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x08 BASE4 0xc401 addr 0xc400 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x04 INT_LINE 0x0b BYTE_00x31000 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x07 function 0x03: vendor 0x1106 device 0x3038 VIA VT 82C586 MVP3 USB Controller CardVendor 0x0925 card 0x1234 (Card unknown) STATUS0x0210 COMMAND 0x0007 CLASS 0x0c 0x03 0x00 REVISION 0x1a BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x08 BASE4 0xc801 addr 0xc800 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x04 INT_LINE 0x0b BYTE_00x31000 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x07 function 0x04: vendor 0x1106 device 0x3057 VIA VT 8501 MVP4 ACPI Bridge CardVendor 0x1106 card 0x3057 (VIA, Card unknown) STATUS0x0290 COMMAND 0x CLASS 0x06 0x80 0x00 REVISION 0x40 BYTE_00x598420 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x07 function 0x05: vendor 0x1106 device 0x3058 VIA VT 8501 MVP4 MultiMedia CardVendor 0x1297 card 0xf125 (Card unknown) STATUS0x0210 COMMAND 0x0001 CLASS 0x04 0x01 0x00 REVISION 0x50 BASE0 0xcc01 addr 0xcc00 I/O BASE1 0xd001 addr 0xd000 I/O BASE2 0xd401 addr 0xd400 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x03 INT_LINE 0x03 BYTE_00x1c45c901 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00
[XFree86] Gratis aber nicht umsonst!
ALLES GRATIS!! Aber nur wenn Du schon über 18 bist. Free Video of the week http://www.fun-www.com Hardcore Movie http://www.fun-www.com/movie_win.html http://www.fun-www.com/movie_real.html Remove from mailinglist: http://www.fun-www.com/newsletter.php ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Error Starting X
Ignore me if you want. The bottom of the enclosed log file suggested sending it to you. If you have any suggestions for fixing the problem, I, of course, would appreciate them. A friend of mime suggests it is something to do with fonts installation and nothing to do with the X-server. Note that everything ran well for quite a while before the X-server failed on a reboot of RedHat 8. Thanks for all your nice work, Willy Bertiger -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-19.8.0 ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Thu Dec 12 05:39:29 EST 2002 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: Sun Feb 2 21:05:47 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Anaconda Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device ATI Mach64 (**) |--Input Device Mouse0 (**) |--Input Device Mouse1 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc105 (**) XKB: model: pc105 (**) Option XkbLayout us (**) XKB: layout: us (==) 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 (II) Open APM successful (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 8086,7190 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 02 class 06,80,00 hdr 00 (II) PCI: 00:0b:0: chip 1013,6001 card 8086,8080 rev 01 class 04,01,00 hdr 00 (II) PCI: 00:0d:0: chip 10b7,9055 card 10b7,9055 rev 24 class 02,00,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4742 card 1002,0084 rev 5c 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.0, 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: 0x8c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0x9000 - 0x90ff (0x100) IX[B] [1] -1 0x9400 - 0x94ff (0x100) IX[B] [2] -1 0x9800 - 0x98ff (0x100) IX[B] [3] -1 0x9c00 - 0x9cff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0xf420 - 0xf5ff (0x1e0) MX[B] (II) Bus 1 prefetchable memory range: (II) Bus -1: bridge is at (0:7: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: (--)
Re: [XFree86] [BUG] The /*-+ keys on the numeric keypad won't repeatin current CVS
On Mon, 3 Feb 2003, Mike A. Harris wrote: /*-+ on the numeric keypad won't repeat in current CVS. Other keys on the keypad do repeat, including numbers when numlock is turned on. /*-+ on the normal part of the keyboard do repeat. Tried xset r on with no change. This occurs on pc105 keyboard with us map, and others as well, so it seems to be something generic. I'm getting it on a GB (102? key) keyboard. NumLock and Scroll Lock keys are disabled too. It might also be worth checking that the magic-sysreq stuff is OK ? -- 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] Graphical User Login and Desktop Unavailable
Dear Sir/Madam, My name is Amitabh Singh and i installed RedHat 8.0 last week. When i was working on RedHat linux , the computer got hung as a result of which I had to powerdown the computer. After which when i restart my computer i don't get Graphical User Interface and i get a text login. Here is the error message from my XFree86.0.log Could not init font path element unix/:7100, removing from list ! Fatal server error: Could not open default font 'fixed' If you can help me in getting back to graphical login and get my GUI working it would be invaluable to me. Thanks Amitabh Singh __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Graphical User Login and Desktop Unavailable
My name is Amitabh Singh and i installed RedHat 8.0 last week. When i was working on RedHat linux , the computer got hung as a result of which I had to powerdown the computer. After which when i restart my computer i don't get Graphical User Interface and i get a text login. Here is the error message from my XFree86.0.log Could not init font path element unix/:7100, removing from list ! Fatal server error: Could not open default font 'fixed' If you can help me in getting back to graphical login and get my GUI working it would be invaluable to me. xfs (The X Font Server) is not running. Start it with xfs -Don ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] 4.2.99.4 and mga dualhead
Hi I've upgraded from 4.2.99.3 to .4. My setup consists of a Matrox G450 DualHead card with two screens (analog) attached. With the old version it worked fine but with the new version the X server crashes on startup (signal 11). Xinerama on or off doesn't make a difference. When I configure only one screen it works without any problems. On both systems I used exactly the same kernel (Linux 2.4.20) and the same XF86Config file. Below you'll find the full log of the crash. I can supply the log of the working 4.2.99.3 and/or the XF86Config if this could help solving the problem. Thx for any responses Jürg Billeter PS: Sorry, if this gets posted twice, but gmane didn't post my mail as I checked. 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 / 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] 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: Mon Feb 3 17:27:55 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Screen Screen1 (1) (**) | |--Monitor Monitor1 (**) | |--Device Card1 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X1 1R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X1 1/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts /TTF/ (**) 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 file or directory) (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 8086,1a30 card 8086,1a30 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 8086,5032 rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 8086,5032 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 8086,5032 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 8086,5032 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 8086,5032 rev 01 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 8086,5032 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24c5 card 8086,0102 rev 01 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 102b,0525 card 102b,0641 rev 82 class 03,00,00 hdr 00 (II) PCI: 02:00:0: chip 9004,8178 card , rev 00 class 01,00,00 hdr 00 (II) PCI: 02:08:0: chip 8086,1039 card 8086,3005 rev 81 class 02,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,2), 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: 0x000a (VGA_EN is set) (II)
Re: [XFree86] Trident cyber 9385 still not works in 4.2.99
On Mon, Feb 03, 2003 at 09:53:58 +0100, Mario Giammarco wrote: Hello, I have just tried xfree 4.2.99 on my thinkpad with trident cyber 9385. Which 4.2.99 ? 4.2.99.3 That's not the latest version. Please get 4.2.99.4. The bug that causes scrambled screen is still there. Scrambled screen - not heard of that one. I am sorry to say that I have at least 20 email from you and Egbert Eich about this bug. I am complaining of this problem from 4.0.0. I offered my self to collaborate. I have sent you the result of test programs you sent to me. I have collected mails of many other people that had my same problem. You concluded that you will continue to work on it. I hope you have not forgotted it. Then I must of. For the fact I don't own a 9385 laptop, things sometimes do get forgotten. The bug started in Xfree 4 (xfree 3.3.x works fine). The screen is scrambled due to wrong refresh rates sent to lcd. I have tried with an external monitor. If eg. I use 800x600x60hz I obtain a 800x600107hz which is wrong. Please correct this bug or disable support for cyber 9385 forever. Do not say a chip is supported if in reality is not. I'm afraid it works on a lot of 9385's so it's not gonna get removed. I can mail you with a lot of 9385 that not works. Well, there's source code for you to plough into and try to fix the problem yourself rather than bitching about it. It's open-source you know. Make sure your trying the current CVS, and send me a log if you've still got problems. I sent you a lot of things... Then refresh my memory. Alan. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] 4.2.99.4 and mga dualhead - crash
Regarding: 4.2.99.4 and mga dualhead - crash Email: [EMAIL PROTECTED] XFree86 Version: 4.2.99.4 OS: Linux 2.4.20 / glibc 2.3.1 / gcc 3.2.1 Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: Matrox Millennium G450 AGP, 32MB mga driver Description: X server crashes on startup with a mga dual head setup (single head setup with the same card is no problem). In 4.2.99.3 with exactly the same configuration file and linux kernel, everything has been ok. I think the problem is the following: Since 4.2.99.4 the mga driver loads the vbe submodule. If there are more than one cards defined, the mga driver tries to load vbe more than once. This results in a crash. I removed the libvbe.a manually and now everything works fine again. Full log follows. 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 / 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] 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: Mon Feb 3 17:27:55 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout XFree86 Configured (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Card0 (**) |--Screen Screen1 (1) (**) | |--Monitor Monitor1 (**) | |--Device Card1 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/CID/,/usr/X11R6/lib/X11/fonts/100dpi/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/TTF/ (**) 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 file or directory) (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 8086,1a30 card 8086,1a30 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 8086,5032 rev 01 class 0c,03,00 hdr 80 (II) PCI: 00:1d:1: chip 8086,24c4 card 8086,5032 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:2: chip 8086,24c7 card 8086,5032 rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:1d:7: chip 8086,24cd card 8086,5032 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 8086,5032 rev 01 class 01,01,8a hdr 00 (II) PCI: 00:1f:3: chip 8086,24c3 card 8086,5032 rev 01 class 0c,05,00 hdr 00 (II) PCI: 00:1f:5: chip 8086,24c5 card 8086,0102 rev 01 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 102b,0525 card 102b,0641 rev 82 class 03,00,00 hdr 00 (II) PCI: 02:00:0: chip 9004,8178 card , rev 00 class 01,00,00 hdr 00 (II) PCI: 02:08:0: chip 8086,1039 card 8086,3005 rev 81 class 02,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,2), 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
Re: [XFree86] Re: Driver for Radeon Mobility 7500
On Mon, 2003-02-03 at 11:02, Mark Collins wrote: I have tried using Redhat 8.0 and experienced similar problems. I was about to give 4.2.99 a go but read in the README that it the Radeon driver is still under development. Wherever you read that, it's probably outdated. The driver is still under active development, but it's been working well for quite a while. -- 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
Re: [XFree86] 4.2.99.4 no display, locked keyboard(Radeon7500Mobility)
- Original Message - From: Michel Dänzer [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: hy0 [EMAIL PROTECTED]; [EMAIL PROTECTED] Sent: Sunday, February 02, 2003 7:31 PM Subject: 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? Yes, this should work. Thanks. Hui -- 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
