CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/02/04 16:23:15 Log message: 837. Resync with DRI mesa-4-0-4 branch: - radeon DRM: only acknowledge interrupts we handle -- others could be used outside the DRM (Michel Dänzer). - Fix PCI and AGP posting problems (based on testing by Chris Ison and suggestions by Benjamin Herrenschmidt and Arjan van de Ven). - Remove radeon_flush_write_combine() which has been unused for a while (Michel Dänzer). - Disable strict aliasing when building the DRM (Michel Dänzer). Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/: Makefile.linux xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/: radeon_drv.h radeon_irq.c Revision ChangesPath 3.2519+9 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG 1.32 +1 -1 xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel/Makefile.linux 1.3 +7 -9 xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/radeon_drv.h 1.3 +8 -5 xc/programs/Xserver/hw/xfree86/os-support/shared/drm/kernel/radeon_irq.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/04 16:26:58 Log message: Change the default cursor theme to core. Modified files: xc/config/cf/: X11.tmpl Revision ChangesPath 1.193 +2 -2 xc/config/cf/X11.tmpl ___ 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/04 16:54:30 Log message: 838. Add a check to xset for a NULL return from XkbGetKeyboard() (Tapani Utriainen). Modified files: xc/programs/Xserver/hw/xfree86/: CHANGELOG xf86Version.h xc/programs/xset/: xset.c Revision ChangesPath 3.2520+3 -1 xc/programs/Xserver/hw/xfree86/CHANGELOG 3.529 +2 -2 xc/programs/Xserver/hw/xfree86/xf86Version.h 3.29 +3 -1 xc/programs/xset/xset.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/04 17:21:12 Log message: Bigendian fix in the nv driver. Modified files: xc/programs/Xserver/hw/xfree86/drivers/nv/: riva_hw.c Revision ChangesPath 1.46 +3 -3 xc/programs/Xserver/hw/xfree86/drivers/nv/riva_hw.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
Re: xterm can hang, CPU bound
On Mon, 3 Feb 2003, D. Hugh Redelmeier wrote:
| 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.
well - it didn't. I was watching both xload and top. on the redhat8, I
could see that it fell into a pattern that eventually blew up, but not
on the slackware71.
| | 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.
ok - I can see what you're asking (sounds reasonable).
--
T.E.Dickey [EMAIL PROTECTED]
http://invisible-island.net
ftp://invisible-island.net
___
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
Re: [Bug 83284] New: Mouse cursor visual glitches with XFree86 (fwd)
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?
But these bits are cleared by DRM driver to acknowledge an interrupt.
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...
The thing is that we should not be getting any extra bits unless we (or
someone else like GATOS km) has asked for them. This makes sense as if
there was a bit set causing an interrupt before drm driver loaded and
nobody was servicing it the system would lock up.
The reason there are extra interrupts without km loaded is likely due to
IRQ sharing.
The simplest way would be to define a mask of interrupts and AND it with
the current values of GEN_INT_CNTL before clearing acknowledge bits.
best
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: A bug in xset and a fix for it
On Tue, Feb 04, 2003 at 05:15:59PM +0100, Tapani Utriainen wrote: Hi, currently xset can segfault when trying change the repeat rate using XKB. The problem is a missing null-pointer check and the fix is a one-liner appended below. I have no idea whether this is only an linux x86 issue since that is the only X-platform with XKB I have access to. Since the null pointer is dereferenced I can't see how this patch could break another platform. Have you looked into why XkbGetKeyboard() is returning NULL? 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: XCursor: left_ptr_watch does not change with theme
On Tue, 2003-02-04 at 00:04, Brandon Wright wrote: 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. left_ptr_watch isn't a standard X cursor. Instead, the way it works is that when Xlib gets a request to create a bitmap cursor, libXcursor creates a hash value from the bits, and sees if there is a cursor with that hash value as a name. This hack allows libXcursor to theme custom bitmap cursors from programs like Mozilla. So, your theme needs a symlink: [big long string of hex digts] = left_ptr_watch see the existing themes for how the right name. Regards, Owen [ There is an environment variable you can set to trace what the cursors and hash values are that a program is creating, if you want to figure it out the name for other bitmap cursors. Search for getenv in the Xcursor sources ] ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon7500Mobility)
Michel, could you remind me what is that xxx_SAVE bit ? best Vladimir Dergachev On Sun, 3 Feb 2003, Michel [ISO-8859-1] Dänzer wrote: 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 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: A question about this list
On Tue, 2003-02-04 at 15:21, Havoc Pennington wrote: On Tue, Feb 04, 2003 at 03:16:16PM -0300, Individual . . wrote: I joined this list because I have started programming with xlib.The questions I will probably ask will be quite basic. Is this a good list for this purpose? I googled quite a bit but could not find a mailing list dealing exclusively with programming for X11 for beginners. If anyone thinks I should try another list, I'd he happy to hear suggestions. Lesson one of programming with Xlib: 1. Don't. Use a GUI toolkit. Phew, the period after Don't came up very fine in my evolution. Kept staring at the sentence for a minut before I could get what you really mean :)) ;-) But, seriously. Havoc ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: A question about this list
On Tue, 4 Feb 2003 18:21:52 -0500 Havoc Pennington [EMAIL PROTECTED] babbled: On Tue, Feb 04, 2003 at 03:16:16PM -0300, Individual . . wrote: I joined this list because I have started programming with xlib.The questions I will probably ask will be quite basic. Is this a good list for this purpose? I googled quite a bit but could not find a mailing list dealing exclusively with programming for X11 for beginners. If anyone thinks I should try another list, I'd he happy to hear suggestions. Lesson one of programming with Xlib: 1. Don't. Use a GUI toolkit. ;-) But, seriously. well devel is more for development of xfree86 itself and the libs, not for helping people learn xlib programming as such. i know of no dedicated lists for this. to a small extent i agree with havoc. this is xlib. it's not a walk in the park. but on the other hand - it depends what you want to achieve. if you goal is to learn xlib so you can write your own toolkit or write things as close to the metal as possible for speed/efficiency reasons, or because you want to help with toolkit development - great. if you want to achieve a lot in a short space of time... forget it. main uses of xlib: * writing window managers * writing toolkits * insane monkeys * writing really small simple display programs that must require as little on the host system as possible. * testing x itself for performance/bugs * getting headaches maybe a few others... :) basically no book i've found is a REALLY good source of learning xlib - they cover some parts and skip others, none give you any real good tips and you generally need to have read a few good general graphics books first (ones that just deal with graphics algorithms and implementation) and combine this with what you can glean from a few xlib books and then the rest coming from the x manual pages, x header files and large chunks of existing x code out there. its very much a black art not many people get completely at home with and even fewer completely understand. -- --- Codito, ergo sum - I code, therefore I am The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] [EMAIL PROTECTED] Mobile Phone: +61 (0)413 451 899Home Phone: 02 9698 8615 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: A question about this list
On Tuesday, February 4, 2003, at 08:42 PM, Carsten Haitzler (The Rasterman) wrote: main uses of xlib: * writing window managers * writing toolkits * insane monkeys * writing really small simple display programs that must require as little on the host system as possible. BINGO! Yes, that's it, exactly. What is not helping me is that I am not a programmer, I am a person that likes programming and then sets himself these tasks and tries to achieve them based upon tutorials and simple examples (reprehensible, I know!) My first goal is to add a display function to a C++ class of mine that works with PNG images. It already relies on libpng, and I wanted to try and do it with xlib, instead of Gtk (more people will have X11 installed than those who have Gtk). Thanks for the comments. Paul ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: A bug in xset and a fix for it
On Tue, Feb 04, 2003 at 07:18:15PM +0100, Tapani Utriainen wrote: On Tue, 4 Feb 2003, David Dawes wrote: Have you looked into why XkbGetKeyboard() is returning NULL? Only briefly, the trail of the error led to a so dark place that I didn't dare to enter it :-) XkbGetKeyboard() calls XkbGetKeyboardByName(). That in turn uses _XReply() to fill in a xkbGetKbdByNameReply struct, and either that call fails, or the reported field of the struct is set to zero. (line 142 in XKBGetByName.c) Does the xset call actually change the repeat rate when this happens (with your fix)? Also, do you need to do anything special to reproduce this? A check for a NULL return value from XkbGetKeyboard() should be added (and I'll do that), but I'm wondering what ignoring it might be covering up. 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: ANSI trigraphs enabled by default in X sources
On Mon, 3 Feb 2003, Keith Packard 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. Yeppers, that's the most sensible solution, and the one I've decided to take as well. Thanks for the feedback Keith -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[Fonts] mkfontscale and family names which contain '-'
If a font has a family name containing '-', mkfontscale generates the
(Bfamily name exactly like that into fonts.scale.
(B
(BThis occurs for example with the GohaTibebZemen.{otf,ttf} fonts which
(Bgot included into XFree86 CVS recently:
(B
(Bmfabian@magellan:/usr/X11R6/lib/X11/fonts/truetype$ grep "^Goha.*" fonts.scale
(BGohaTibebZemen.otf -misc-Goha-Tibeb Zemen-medium-r-normal--0-0-0-0-p-0-iso10646-1
(BGohaTibebZemen.otf -misc-Goha-Tibeb
(BZemen-medium-r-normal--0-0-0-0-p-0-adobe-fontspecific
(BGohaTibebZemen.ttf -misc-Goha-Tibeb Zemen-medium-r-normal--0-0-0-0-p-0-iso10646-1
(Bmfabian@magellan:/usr/X11R6/lib/X11/fonts/truetype$ ftdump GohaTibebZemen.otf
(BThere is 1 face in this file.
(B
(B- Face number: 0 -
(B
(Bfont name entries
(B family: Goha-Tibeb Zemen
(B style: Regular
(B postscript: GohaTibebZemen
(B
(Bfont type entries
(B FreeType driver: cff
(B sfnt wrapped:yes
(B type:scalable
(B direction: horizontal
(B fixed width: no
(B glyph names: yes
(B EM size: 1000
(B global BBox: (11,-189):(1223,802)
(B ascent: 820
(B descent: -180
(B text height: 1150
(B
(Bcharmaps
(B 0: platform: 0, encoding: 3
(B 1: platform: 1, encoding: 0
(B 2: platform: 3, encoding: 1
(B 3: platform: 7, encoding: 3
(Bmfabian@magellan:/usr/X11R6/lib/X11/fonts/truetype$
(B
(BThe XLFD thus generated doesn't work of course. How should this be
(Bfixed? Should the fonts be fixed?
(B
(BBut maybe it is no reason for the font maker to remove a '-' only
(Bbecause it doesn't work in a XLFD. Is a family name with a '-'
(Ballowed or not?
(B
(BMaybe one should work around that problem in mkfontscale by replacing
(Bthe '-' characters with ' ', for example like that:
(B
(BIndex: mkfontscale.c
(B===
(BRCS file: /cvs/xc/programs/mkfontscale/mkfontscale.c,v
(Bretrieving revision 1.3
(Bdiff -u -r1.3 mkfontscale.c
(B--- mkfontscale.c 2003/01/26 02:20:41 1.3
(B+++ mkfontscale.c 2003/02/04 18:50:28
(B@@ -317,7 +317,8 @@
(B *spacing, *full_name;
(B ListPtr encoding, entries = NULL;
(B int i, found, rc;
(B-
(B+char *p;
(B+
(B i = strlen(dirname_given);
(B if(i == 0)
(B dirname = strcat_reliable(".", "/");
(B@@ -477,7 +478,14 @@
(B fprintf(stderr, "Couldn't get family name for %s\n", filename);
(B family = entry-d_name;
(B }
(B-
(B+
(B+ while((p = strpbrk(family, "-"))) {
(B+ *p = ' ';
(B+ }
(B+ while((p = strpbrk(foundry, "-"))) {
(B+ *p = ' ';
(B+ }
(B+
(B if(!weight) weight = "medium";
(B if(!slant) slant = "r";
(B if(!sWidth) sWidth = "normal";
(B
(B--
(BMike Fabian [EMAIL PROTECTED] http://www.suse.de/~mfabian
$B?gL2ITB-$O;E;v$NE($@!#(B
(B___
(BFonts mailing list
([EMAIL PROTECTED]
(Bhttp://XFree86.Org/mailman/listinfo/fonts
[XFree86] ATI Mach64 and -depth 16
I have an oldish Mach64 card with 2Mb of memory; the controller seems to be a GX88800-D. For some reason, any -depth other than 8 is not possible (the 4.2.0 'ati' driver says not supported through this adapter.) I say some reason, because, according to my limited understanding, 2Mb *should* be enough. Can anyone explain? Thank you, Sakari Aaltonen ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86(TM) Bug Report] 4.2.99.4 and mga dualhead -crash
On Mon, 3 Feb 2003, Jürg Billeter wrote: 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. I'll have a look at a proper fix, but does this workaround work: if you add: Option NoDDC to each Device section, and put back libvbe.a does it work ? -- 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] Intel 845 and Cursor color
El Mar 04 Feb 2003 06:35, Sudheer Parameswaran escribió: Hi, I am facing a small problem with the XFree86 4.2.99 version on Intel 845 graphics adapter. I am using kernel 2.4.18-14. on this setup. Everything works fine on this setup except the cursor color is always red. I am using the rpms from RawHide which were built on Dec 30. (These rpms looks new as it not giving any VT switching problems with i845 ). You Don't have any problem; in the 4.2.99 (and i think that un 4.3 too) the default cursor is red... :-) I tried to use HWCursor and SWCursor options in XF86Config, but were not helpful. Anybody could tell me how to fix this problem ? Thanks in advance, Sudheer ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] [XFree86(TM) Bug Report] 4.2.99.4 and mga dualhead - crash
-Original Message- From: Dr Andrew C Aitchison [mailto:[EMAIL PROTECTED]] I'll have a look at a proper fix, but does this workaround work: if you add: Option NoDDC to each Device section, and put back libvbe.a does it work ? Yes, that works. It even works if this option is set to only one device section. Thx Jürg Billeter ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Intel 845 and Cursor color
Alejandro Lorenzo Gallego wrote: El Mar 04 Feb 2003 06:35, Sudheer Parameswaran escribió: Hi, I am facing a small problem with the XFree86 4.2.99 version on Intel 845 graphics adapter. I am using kernel 2.4.18-14. on this setup. Everything works fine on this setup except the cursor color is always red. I am using the rpms from RawHide which were built on Dec 30. (These rpms looks new as it not giving any VT switching problems with i845 ). You Don't have any problem; in the 4.2.99 (and i think that un 4.3 too) the default cursor is red... :-) Thanks for your responce. But would like know whether I can use 4.2 style cursor with 4.2.99/4.3 ? Sudheer I tried to use HWCursor and SWCursor options in XF86Config, but were not helpful. Anybody could tell me how to fix this problem ? Thanks in advance, Sudheer ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Latest PS/2 mice initialization sequence code causes infinite loopwith Synaptics driver.
This shouldn't be an endless loop. It should give up after 10 unsuccessful retries. Unfortunately there are some lengthy timeouts in the code which make it look like an endless loop. I really don't know of any solution that is acceptable to everybody. The Xserver can't tell the difference between a 'repeater' ps/2 mouse and a physical ps/2 mouse. The current code now makes all broken physical ps/2 mice I was able to get my hands on happy. I does break 'repeater' mice if they don't respond to control sequences in the same way the ps/2 protocol specifies. I can add an option which disables any attempt to (re)initialize the mouse. However the entire concept is broken. Egbert. Aleksey Nogin writes: Summary: when the mouse input driver uses a named pipe as a device, the new PS2 initialization sequence code (added about two weeks ago) causes the server to go into infinite loop sending the initialization byte to the pipe. Details: I am using XFree86 with the Synaptics TouchPad Driver (http://mobilix.org/touchpad_driver.html). That driver has a repeater feature - whenever it detects that the touchpad is not being used (e.g. an external mice is attached), it would start piping all its input to the repeater pipe where another driver can take it and process it using a different protocol. E.g. the config file would look like: Section ServerLayout InputDeviceMouse0 CorePointer InputDeviceMouse-ps2 SendCoreEvents ... EndSection Section InputDevice Identifier Mouse0 Driver synaptics Option Device /dev/psaux Option Repeater /dev/ps2mouse ... EndSection Section InputDevice Identifier Mouse-ps2 Driver mouse Option Protocol PS/2 Option Device /dev/ps2mouse ... EndSection ... Where /dev/ps2mouse is just a named pipe (created using mkfifo). This used to work great until about two weeks ago. Now, with the same configuration X would just freeze on startup (right after the mouse drivers are initialized) eating up CPU. Strace shows, that X just keeps writing and reading a single byte to/from /dev/ps2mouse pipe. http://cvsweb.xfree86.org/cvsweb/xc/programs/Xserver/hw/xfree86/input/mouse/mouse.c lists for the revision 1.66: 756. PS/2 mice initialization sequence changed: rerun entire sequence when something goes wrong - this needs to be rewritten completely after 4.3 is out (Egbert Eich). So, I am guessing what happens is that the PS2 protocol of the mouse driver sends the initialization byte to the pipe, reads it back, thinks there must be some error (since the byte is not a valid mouse output) and decides it needs to initialize the mouse again! Of course, this results in an infinite loop of mouse initialization... Note - if I understand it correctly, this has nothing to do with the synaptics driver specifically - this would be the same, whenever the PS/2 protocol of the mouse driver is pointed to a named pipe instead of a real mouse device. What exactly is supposed to be supplying the pipe with data is irrelevant to this problem. -- Aleksey Nogin Home Page: http://nogin.org/ E-Mail: [EMAIL PROTECTED] (office), [EMAIL PROTECTED] (personal) Office: Jorgensen 70, tel: (626) 395-2907 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Error Starting X
I will try to give a more detailed answer as this should go into a FAQ and some people have volunteered to work on one. The Xserver needs at least the 'fixed' and the 'cursor' font to start up successfully. The 'cursor' font is required to be able to display a cursor symbol, the 'fixed' font is required so that an application is able to display text (an error message saying it cannot find the required set of fonts). The server checks if these two fonts are present in the FontPath which can be specified in the configuration file (- XF86Config(5)) or on the server command line (- Xserver(1)). If one of the two fonts isn't present the server fails to start printing an error message: Fatal server error: could not open default font 'fixed' If you see the above error message please make sure the fontpath is set correctly. You can find the currently configured path in the server log file. Please look for lines beginning with: FontPath set to: If the font path doesn't look like you expect it to be (in a default installation it is set to the subdirectories in /usr/X11R6/lib/X11/fonts/) you may edit your XF86Config file. Make sure that the fontpath directories exist and contain fonts. Check if all directories contain a file called 'fonts.dir'. If not you may run 'mkfontdir' in the font directory to create this file. Since fonts are listed by their XLFD name in 'fonts.dir' - not their abbreviated name - a file called 'fonts.alias' needs to exist in the font directory specifying the mapping of the abbreviated names to the XLFD names. In a default installation the both 'cursor' and 'fixed' font exist in the directory /usr/X11R6/lib/X11/fonts/misc. fonts.alias must at least contain the line: fixed -misc-fixed-medium-r-semicondensed--13-120-75-75-c-60-iso8859-1 for the 'fixed' font to be found. The files '6x13-ISO8859-1.pcf.gz' and cursor.pcf.gz need to be present. Font don't have to live in files in a local directory. They can be provided by a fontserver running on a remote machine (- XF86Config(5), X(7)). If you are using a font server please make sure it is running, that it is configured correctly and that it has access to the fonts. The above also applies to the font directories on font servers. The default font server for bitmapped fonts shipped with XFree86 is xfs (- xfs(1)). Starting with XFree86 4.3 there are plans to build both fonts into the Xserver. --- Now to your problem: It looks like you are using a font server: FontPath set to unix/:7100 on the local machine. Please make sure it is running. Egbert. Willy Bertiger writes: 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
RE: [XFree86] [XFree86(TM) Bug Report] 4.2.99.4 and mga dualhead - crash
-Original Message- From: Dr Andrew C Aitchison [mailto:[EMAIL PROTECTED]] Good. Now I know I'm looking in the right place for a proper fix. Does X -configure work ? Yes, but it doesn't configure more than one screen (I think this is intentional). ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Crash server X
XFree86.0.log XFree86.9.log XFree86.0.log Description: Binary data XFree86.9.log Description: Binary data
DDC on dual head - was Re: [XFree86] 4.2.99.4 and mga dualhead
On Tue, 4 Feb 2003, Egbert Eich wrote: Jürg Billeter writes: 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. There was a bug in the vbe DDC read code which is belived to be fixed in the current CVS now. To test this you need to check out CVS head. Ebgert's fix does seem to stop it crashing on my G550. While testing, I've noticed that the mga driver always reports DDC info for the first head. Are there any drivers which give correct DDC info for the second head, or does anyone else have suggestions as to how to fix 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
[XFree86] RentalCars.com-Updated Hot Deals
Rental Car Specials from RentalCars.com! Discounts, free upgrades and low prices from major and specialty rental car agencies. Book your car now for Spring Break and Easter! Plan for Summer. Some Black Out Dates may apply and offers may be limited, so Book Early! **Alamo: SUV Super Sale! $35/day $219/wk Airports until 4/9/03! http://alamo.com/hotdeals/template.asp?msg=rentalcars_us_offer ***Thrifty: Save 10% off Thrifty's Cars, PT Cruisers, Vans, SUVS and Pick-Up Trucks! Valid Worldwide for all of 2003! http://www.rentalcars.com/Untitled/Thrifty_/10percent.shtml *Budget: FREE Upgrade on mid-size or full-size cars through 7/2/03! http://comet.sparklist.com/scripts/nph-t.pl?U=1094M=11958316MS=1895728 *Alamo: Nationwide Compact Car Sale through 4/9/03 http://alamo.com/hotdeals/template.asp?msg=affil_rentalcarscom_og *Alamo: Nationwide Minivan Offer! Great Deals through 4/9/03 http://www.alamo.com/hotdeals/template.asp?msg=rd_minivan_rentalcars_offer **Alamo: Unbelievably low rates in Florida and Hawaii on Full Size Convertibles http://www.alamo.com/hotdeals/template.asp?msg=rentalcars_florida_hawaii_offer **Budget!! Additional $15 Off a 4 day or longer Rentals thru 7/2/03! http://www.budget.com/partners/rentalcars2002.html *Dollar: Great Vegas rates and 19 locations, including in most major casinos!Save an additional 10% with RentalCars.com! Why not pick up your car at your hotel? http://comet.sparklist.com/scripts/nph-t.pl?U=1096M=11958316MS=1895728 *Dollar-TerrificConvenient Locations What more do you need? http://tinyurl.com/4ka3 *Dollar-Dont miss the Minivan Sale through 4/15! Only $199/week! http://www.dollar.com/promotions/dol39_promo.asp?iatanbr=10003759 *Fox: Save up to 40% other companies rates in California and Phoenix plus FREE upgrade! http://comet.sparklist.com/scripts/nph-t.pl?U=1098M=11958316MS=1895728 *Enterprise: Low rates Locally and at the Airport! http://www.enterprise.com/car_rental/deeplinkmap.do?siteid=EMNDMarc=EMNDOM *Hertz: FREE Upgrade plus weekly and weekend discounts http://comet.sparklist.com/scripts/nph-t.pl?U=1100M=11958316MS=1895728 *National: Premium, SUVs and Minivans only $229/week http://www.nationalcar.com/servlet/DocHandler/directlinks/index_NHOL_offer3.jsp *Priceline: Let Priceline show you how to Get More Car for Your Money! Go Ahead! Make an Offer! Shop aroundsee if you can do better with Priceline! http://rentalcars.com/Untitled/priceline/ *Thrifty: Florida Super Saver for 1/1/03-6/30/03! Miami, Ft Lauderdale, Key West,W.Palm Beach-$199/week!/$39.99day! https://www.thrifty.com/res/main.asp?iata=00226600pc=27aa In Europe go for the best: Free One Car Class Upgrades In Select Countries In Europe! Book a compact, receive and intermediate! For additional details, visit: http://www.autoeurope.com/showspecial.cfm?specid=49aff=rentalcars ***Thrifty: Get A FRE Upgrade Worldwide thru 2003! http://comet.sparklist.com/scripts/nph-t.pl?U=1089M=11958316MS=1895728 Specials available as of Feb 4, 2003 Please confirm your reservation. Car Rental Hot Deals updated daily at http://www.rentalcars.com/ --- You are currently subscribed to rentalcars-specials as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] RE: [xfree86]2 mice - 2 pointer ?!?
Replying to this a bit late on in teh day, but i thought i'd give a more concrete example where more than one on-screen pointer is needed. We have a product that can have up to 4 touch screens and has a track-ball controlled pointer. Iften people operate the product in a two-handed manner, and occasionally more than one operator will use the product at a given time. the upshot of this is that ideally there would be a pointer for the trackball that isn't effected by touchscreen presses, and separate invisible pointers for each of the touchscreens. The setup is currently impossible in Xfree86. Another concrete example is when implementing a collaborative decktop in whcih you want a separate pointer for each of the users remotely viewing that desktop. Yours, Rob Taylor mailto:[EMAIL PROTECTED] FPShttp://www.flyingpig.com -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Dr Andrew C Aitchison Sent: 03 December 2002 18:05 To: [EMAIL PROTECTED] Subject: Re: [Xpert]2 mice - 2 pointer ?!? From: Dr Andrew C Aitchison [EMAIL PROTECTED] Where does the pointer come in ? I'm not saying that for a flight simulator it isn't useful to have more than one mouse or trackball; I'm all in favour of an X extension for that (I wouldn't be suprised to hear that there already is one) but that is 2 mice, not 2 pointers. I've been looking at xc/doc/hardcopy/Xi/lib.PS.gz the X Input Device Extension Library, which is implemented by XFree86 and some other X servers. Is the request for 2 pointers based on page 2, where it says All extension input devices are treated like the core X keyboard in determining their location and focus ? I think the next line, about explict focus, is your answer. As I understand it, an application can grab an input device and make it control anything it wishes. maybe I can add some examples: I am working on a container terminal simulation (might be any robotic type simulation in that regard...) where I visualize the crane movement during waggon loading and unloading movements (4 degrees of freedom: along tracks, transverse to tracks, lifting/lowering, rotation about z-axis). I'm using both a SpaceMouse _and_ a regular mouse for my user interface which already introduces the notion of distint foci: Spacemouse for crane interactive movement, 2D-Mouse for viewpoint manipulation at the same time. I can see why you want lots of degrees of freedom, and lots of inputs, but I don't really see why more of them are pointers in the sense I understand. It may be appropriate to show cursors for these independent actors, but they are application specific. In this case I think the fact that they are likely to be 3D is significant. I'm familiar with the idea of a mouse moving cross-hairs to rotate an object in 3D, but I'm not sure that I'd expect to see the cross-hairs if I had a track-ball - I'd just move the ball and expect the object to follow. Anyway, an application can take a device and draw its own cursor. I see an X pointer being as much connected with a keyboard as a mouse; what should the X server do with 2 pointers ? Shouldn't it leave the control of foci within an app up to that app. I don't know anything more about XInput, so I'll stop here, but I hope that I've given you a feeling for why some of us don't understand the request for more than one pointer as well as more than one mouse ? -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna ___ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Intel 845 and Cursor color
I don't use 4.2.99 yet, but I believe if you export XCURSOR_THEME=default, that should do the trick. There have been a lot of questions about this one, lately. If you want to know more, search the archives for a message by a Mr. Kurt Wall with the subject line as how do I set that red cursor back to something normal? where he explains a lot of environment variables that affect the pointer. Jesse On Tue, 4 Feb 2003, Sudheer Parameswaran wrote: Alejandro Lorenzo Gallego wrote: El Mar 04 Feb 2003 06:35, Sudheer Parameswaran escribió: Hi, I am facing a small problem with the XFree86 4.2.99 version on Intel 845 graphics adapter. I am using kernel 2.4.18-14. on this setup. Everything works fine on this setup except the cursor color is always red. I am using the rpms from RawHide which were built on Dec 30. (These rpms looks new as it not giving any VT switching problems with i845 ). You Don't have any problem; in the 4.2.99 (and i think that un 4.3 too) the default cursor is red... :-) Thanks for your responce. But would like know whether I can use 4.2 style cursor with 4.2.99/4.3 ? Sudheer I tried to use HWCursor and SWCursor options in XF86Config, but were not helpful. Anybody could tell me how to fix this problem ? Thanks in advance, Sudheer ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI Mach64 and -depth 16
I have an oldish Mach64 card with 2Mb of memory; the controller seems to be a GX88800-D. For some reason, any -depth other than 8 is not possible (the 4.2.0 'ati' driver says not supported through this adapter.) I tried an ATI Mach64 with chip labeled 21088GX00 and got the same results. I tested it on a PowerPC so the card was not initialized by BIOS, I thought this was the culprit but probably not. It barfed about unsupported depth on 16 and 24 bpp modes and gave another kind of error in 8bpp mode - the last was probably because of uninitalized card. -- Meelis Roos ([EMAIL PROTECTED]) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Intel 854g borad Redhat 7.2 Display problems
Hello I am unable start X (KDE) because I am unloable to configure display drivers Please advise so that I can configure the X server Sandeep, Sorry I don't have experience with RH7.2 , but here's my notes on how I got XFree86 4.2.99.x to work in RedHat 8.0 (Caution: this loads the whole CVS tree - you can read the docs to figure out how to download just the 4.2.99.x stuff): This procedure was successful on a fresh install of RedHat 8.0 - no claim the procedure will work on anything else is implied. 1. Get CVSup from ftp://ftp3.freebsd.org/pub/FreeBSD/development/CVSup/binaries/RedHat-6/ 2. Place the .tar.gz file in desired directory and extract contents (in KDE, right click on file and select Extract Here...) 3. Launch terminal and cd to /usr 4. create /xbuild and /sup under /usr (mkdir xbuild, mkdir sup) 5.create /xf86 under /sup (cd to sup, mkdir xf86) 6. with a text editor, create a text file named a.txt containing the following content: *default release=cvs host=anoncvs.xfree86.org base=/usr/sup/xf86 *default prefix=/usr/Xbuild delete use-rel-suffix *default compress *default tag=. cvs-base xc-all contrib-all xtest-all doctools-all utils-all 7. place a.txt in the directory where cvsup was extracted to 8. in terminal, cd to directory where cvsup was extracted to 9. run the command: ./cvsup a.txt 10. run the command several times, as necessary, until the last line in terminal says the transfer was completed successfully 11. run the command one more time to make sure. 12. in terminal, cd to /usr/xbuild 13. in terminal, run the command: make World 14. make World may take 1 to 2 hours to complete 15. shut down xFree86, if it is running - the easiest way to do this is to go to a terminal window and execute the command: shutdown now This will shutdown xFree86 and a few other processes and bring up a console prompt 16. with xFree86 not running and at a terminal prompt, cd /usr/xbuild 17. run the command: make install 18. make install will take 30min to an hour 19. reboot the machine 20. Under System Settings, Display, you should have more resolution and color depth choices under the Intel 845 chip. Tom Dolan ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] version mismatch after installation and configuration
Regarding: version mismatch after installation and configuration Email: [EMAIL PROTECTED] XFree86 Version: fglrx-glc22-4[1].2.0-2.5.1.i586.rpm OS: Mandrake Linux 9.0 Area: loading module fglrx - version mismatch Server: Other, specify below Description: XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: Linux 2.4.18-23mdkenterprise 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: Tue Feb 4 09:35:16 2003 (==) Using config file: /etc/X11/XF86Config-4 (==) ServerLayout Server Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device ATI Graphics Adapter (**) |--Input Device Mouse1 (**) |--Input Device Keyboard1 (**) Option AutoRepeat 500 30 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc104 (**) XKB: model: pc104 (**) Option XkbLayout us (**) XKB: layout: us (==) Keyboard: CustomKeycode disabled (**) FontPath set to /usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/75dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/75dpi/,/usr/X11R6/lib/X11/fonts/100dpi/ (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules Using vt 7 (--) 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.1, module version = 1.0.0 Module class: XFree86 Font Renderer ABI class: XFree86 Font Renderer, version 0.3 (II) Loading font Bitmap (II) LoadModule: pcidata (II) Loading /usr/X11R6/lib/modules/libpcidata.a (II) Module pcidata: vendor=The XFree86 Project compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) PCI: Probing config type using method 1 (II) PCI: Config type is 1 (II) PCI: stages = 0x03, oldVal1 = 0x8060, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0605 card , rev c4 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8605 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 40 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:07:2: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 1106,3038 card 0925,1234 rev 16 class 0c,03,00 hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card , rev 40 class 06,00,00 hdr 00 (II) PCI: 00:0a:0: chip 10ec,8029 card , rev 00 class 02,00,00 hdr 00 (II) PCI: 00:0f:0: chip 1013,6005 card , rev 01 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 1002,4966 card 174b,7197 rev 01 class 03,00,00 hdr 80 (II) PCI: 01:00:1: chip 1002,496e card 174b,7196 rev 01 class 03,80,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.1, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (II) UnloadModule: scanpci (II) Unloading /usr/X11R6/lib/modules/libscanpci.a (II) Host-to-PCI bridge: (II) PCI-to-ISA bridge: (II) Host-to-PCI bridge: (II) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 0x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 0x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x0c (VGA_EN is set) (II) Bus 1 I/O range: [0] -1 0xd000 - 0xd0ff (0x100) IX[B] [1] -1 0xd400 - 0xd4ff (0x100) IX[B] [2] -1 0xd800 - 0xd8ff (0x100) IX[B] [3] -1 0xdc00 - 0xdcff (0x100) IX[B] (II) Bus 1 non-prefetchable memory range: [0] -1 0xdc00 - 0xddff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xd400 - 0xdbff (0x800) MX[B] (II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x08
Re: [XFree86] Latest PS/2 mice initialization sequence code causes infinite loopwith Synaptics driver.
I've committed a patch to stop the endless loop. However since the mouse initialization routine reports that the mouse isn't initialized correctly mice on a repeater will still not work correctly if the protocol is set to PS/2 or its variants. One should either use GenericPS/2 or auto as protocol. I cannot test this as my gpm refuses to set the protocol on /dev/gpmdata to any ps/2 variant. Egbert. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] No DGA on SiS 6326 ?
Regarding: No DGA on SiS 6326 ? Email: [EMAIL PROTECTED] XFree86 Version: XFree86-4.2.99.3-20030115.0.i386.rpm OS: RedHat Linux 8.0.93 ( phoebe2 - beta ) Area: Xserver Server: XFree86 (The XFree86 4.x server) Video Card: SiS 6326 PCI 8 MB VRAM Description: [stein@localhost stein]$ xawtv -nodga This is xawtv-3.81, running on Linux/i686 (2.4.20-2.21) X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 136 (XFree86-DGA) Minor opcode of failed request: 1 (XF86DGAGetVideoLL) Serial number of failed request: 13 Current serial number in output stream: 13 WARNING: v4l and x11 disagree about the screen size WARNING: Is v4l-conf installed correctly? WARNING: v4l and x11 disagree about the color depth WARNING: fbuf.depth=16, x11 depth=32 WARNING: Is v4l-conf installed correctly? WARNING: overlay mode disabled Warning: Cannot convert string -*-ledfixed-medium-r-semicondensed--39-* to type FontStruct [stein@localhost stein]$ v4l-conf v4l-conf: using X11 display :0.0 dga: version 2.0 X Error of failed request: XF86DGANoDirectVideoMode Major opcode of failed request: 136 (XFree86-DGA) Minor opcode of failed request: 1 (XF86DGAGetVideoLL) Serial number of failed request: 13 Current serial number in output stream: 13 [stein@localhost stein]$ Repeat By: version : xawtv-3.81-2 video mode : 800x600x32 The problem goes away in 16bit mode. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: DDC on dual head - was Re: [XFree86] 4.2.99.4 and mga dualhead
I think that these two problems dont have anything in common but the ChangeLog reports (see below) that both issues are fixed in 4.2.99.901. Ive just checked out and will soon compile and try on my G450. 806. Fixed patch 760: VBEInit takes entity index, not screen index (Egbert Eich). Thats the crash fix. 818. xaaStateChange.c was not calling RestoreAccelState before doing CPUToScreenTexture and CPUToScreenAlphaTexture, which seems to be the reason why RENDER acceleration was broken on some dual-monitor MGA cards (#5602, Nolan Leake). Thats the fix for the font / cursor problem. Jürg Billeter ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] 4.2.99.4 no display, locked keyboard (Radeon7500Mobility)
Michel, could you remind me what is that xxx_SAVE bit ? best Vladimir Dergachev On Sun, 3 Feb 2003, Michel [ISO-8859-1] Dänzer wrote: 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 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Re: [Bug 83284] New: Mouse cursor visual glitches with XFree86(fwd)
On Die, 2003-02-04 at 15:43, Vladimir Dergachev wrote:
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?
But these bits are cleared by DRM driver to acknowledge an interrupt.
No, the RADEON_GEN_INT_STATUS register is used for interrupts.
You asked how CRTC{,2}_VBLANK_SAVE work, here you go: you clear those
bits by setting CRTC{,2}_VBLANK_SAVE_CLEAR in RADEON_CRTC{,2}_STATUS,
and they go back up on the next vertical blank.
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...
The thing is that we should not be getting any extra bits unless we (or
someone else like GATOS km) has asked for them. This makes sense as if
there was a bit set causing an interrupt before drm driver loaded and
nobody was servicing it the system would lock up.
The reason there are extra interrupts without km loaded is likely due to
IRQ sharing.
What do you mean?
The simplest way would be to define a mask of interrupts and AND it with
the current values of GEN_INT_CNTL before clearing acknowledge bits.
Yes, I've committed a fix along those lines to the DRI trunk and mesa-4-0-4-branch,
so it will hopefully go into 4.3.0.
--
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] Geode and doublescanned modes
Hi all, I've been trying for some time now to get low resolution doublescanned video modes working with XFree86 4.xxx. (currently 4.2.99.3). I'm playing back 352x288 MPEG video on this platform and it just isn't frisky enough to upscale to 640x480. Ideally I'd like to get 400x300 working. I found some old messages from the xpert list talking about this issue, but I can't fathom (a) if anyone got it to actually /work/, and (b) what is required. So I guess the bottom line is: does anyone know if there exists a nsc_drv.o that can actually use doublescanned modes? I've experimented with manually-created Modelines, I have a Virtual 1024 768 in my XF86Config to get around the must be 480 pixels tall whining from the driver, and I've asked in a couple of relevant newsgroups, with no useful answer. -- -- Lewin A.R.W. Edwards Work: http://www.digi-frame.com/ Personal: http://www.larwe.com/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] XFree86 on Alpha support doc
moonshine_religion wrote: You should provide more information on the problems you're seeing. It's not possible to diagnose what's wrong with so little information. Looking at /var/log/XFree86.0.log for obvious error messages is the first step. If you don't find anything obvious, send it to this list, along with other information that may be relevant (like are you using startx or xdm to launch the server, dmesg command output,...) Well here are the ugly details. Also what are all of the .debug_line messages? XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 5.0-CURRENT alpha [ELF] [...] Someone was reporting very similar problem (FreeBSD 4.7, Alpha box) before. Those someone also said that with RH7.2 the box worked fine. Wasn't that you? If so, did you actually try migrating config from RH7.2? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] video problems
Craig Blocker wrote: I am trying to load Red Hat Linux 7.1.1 on a new Dell Inspiron 4150 laptop. If I start in text mode, everything seems fine (except that only the central 20% of my screen is used for the text). *That* is normal. :) When I do a startx command, I get a Fatal server error: no screens found. The laptop has a ATI Radeon 7500 AGP (LW) video adapter with 16Mb of memory. I don't know what the display actually is - Dell specifies it as a 14.1 SXGA+ display. No matter what I try I get the same problem. Can you give me a clue as to what to do? I've included fragment of your log. Seems that DDC module isn't happy with your hardware? Try either: upgrading the X to more recent version (you seem to have 4.1.0, right?) or if that doesn't help by itself: switching off the DDC in your config (there are options NoDDC, NoDDC1, NoDDC2, but I'm not sure in what section of config should they go) and (or) tell X about panel dimensions yourself (sorry, I don't know the exact syntax) [...] (II) Loading sub module ddc (II) LoadModule: ddc (II) Loading /usr/X11R6/lib/modules/libddc.a (II) Module ddc: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.4 (II) Loading sub module i2c (II) LoadModule: i2c (II) Loading /usr/X11R6/lib/modules/libi2c.a (II) Module i2c: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.2.0 ABI class: XFree86 Video Driver, version 0.4 (II) Loading sub module vbe (II) LoadModule: vbe (II) Loading /usr/X11R6/lib/modules/libvbe.a (II) Module vbe: vendor=The XFree86 Project compiled for 4.1.0, module version = 1.0.0 ABI class: XFree86 Video Driver, version 0.4 (II) RADEON(0): VESA BIOS detected (II) RADEON(0): VESA VBE Version 2.0 (II) RADEON(0): VESA VBE Total Mem: 16384 kB (II) RADEON(0): VESA VBE OEM: ATI MOBILITY RADEON 7500 (II) RADEON(0): VESA VBE OEM Software Rev: 1.0 (II) RADEON(0): VESA VBE OEM Vendor: ATI Technologies Inc. (II) RADEON(0): VESA VBE OEM Product: P7 (II) RADEON(0): VESA VBE OEM Product Rev: 01.00 (II) Loading sub module ddc (II) LoadModule: ddc (II) Reloading /usr/X11R6/lib/modules/libddc.a (II) RADEON(0): VESA VBE DDC supported (II) RADEON(0): VESA VBE DDC Level none (II) RADEON(0): VESA VBE DDC transfer in appr. 2 sec. (II) RADEON(0): VESA VBE DDC read failed (==) RADEON(0): Write-combining range (0xe000,0x100) (EE) RADEON(0): Failed to detect the panel size. (II) UnloadModule: ati (II) UnloadModule: ddc (II) UnloadModule: vbe (II) Unloading /usr/X11R6/lib/modules/libvbe.a (II) UnloadModule: i2c (II) Unloading /usr/X11R6/lib/modules/libi2c.a (II) UnloadModule: ddc (II) Unloading /usr/X11R6/lib/modules/libddc.a (II) UnloadModule: int10 (II) Unloading /usr/X11R6/lib/modules/linux/libint10.a (II) UnloadModule: vgahw (II) Unloading /usr/X11R6/lib/modules/libvgahw.a (II) UnloadModule: radeon (EE) Screen(s) found, but none have a usable configuration. Fatal server error: no screens found ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] X problem
Replying to reply... Kevin Oberman wrote: First, XFree86 is not finding any fonts. Have you installed the standard font packages/ports? Under 4.7 of FreeBSD, V4.2 of XFree86 is the default. Second, host you build a new XF86Config file? The old file from V3.6 of XFree86 will not work very well with V4. I'd try using the built-in configuration generator to get a good starting point. XFree86 -configure Just see what he's got in his output: [...] (--) PCI:*(0:11:0) S3 Trio64V2/DX or /GX rev 22, Mem @ 0xe000/26 [...] (II) LoadModule: vga [...] (--) VGA(0): pixel clocks: 25.180 28.322 25.170 25.170 (II) VGA(0): My Monitor: Using hsync range of 30.00-70.00 kHz (II) VGA(0): My Monitor: Using vrefresh range of 50.00-120.00 Hz (II) VGA(0): Not using default mode 640x350 (insufficient memory for mode) (II) VGA(0): Not using default mode 640x400 (insufficient memory for mode) [...] (II) VGA(0): Not using mode 640x480 (no mode of this name) (II) VGA(0): Not using mode 800x600 (no mode of this name) (II) VGA(0): Not using mode 1024x768 (no mode of this name) (II) VGA(0): Not using mode 360x200 (no clock available for mode) (II) VGA(0): Not using mode 320x200 (no clock available for mode) (II) VGA(0): Not using mode 320x175 (no clock available for mode) (--) VGA(0): Virtual size is 416x312 (pitch 416) (**) VGA(0): Default mode 416x312: 28.3 MHz, 49.2 kHz, 73.8 Hz (D) Here. What kind of mode is this? I'm not sure you can get this mode even with s3 driver (which he seemingly does not use). ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] ATI FireGL / IBM RC1000 / GT1000 PCI
Is there, or will there, be any support for the above card... also marketted as FireGL 2 PRO PCI or HP GL-UX.. As far as i can see on the HP homepage below of the topic extreme 3D graphics cards it is a HP branded card with a 64 bit PCI slot that comes with drivers for HP-UX only. I assume that board is in some way tailored to its original machine design, e.g. PA-RISC little endian, LE-Bios, etc. Linux detects it as: Bus 0, device 11, function 0: VGA compatible controller: PCI device 1014:0170 (IBM) (rev 2). IRQ 28. Master Capable. Latency=32. Min Gnt=255.Max Lat=255. Non-prefetchable 32 bit memory at 0xa58 [0xa59]. Non-prefetchable 32 bit memory at 0xc00 [0xfff]. It is aparrently manufactured by ATI, uses an IBM chipset.. and is supplied on a 64bit pci card, a picture (890kb) is available at http://www.ev6.net/card.jpg Link is not working for me, according to yourvote.com it is an IBM chip. sub-vendor/sub-device would be quite interesting if set. right now i dont know who has really built that and on whichever design he based his layout. It looks somewhat similar to a FireGL 2 board, but it has some obvious differences as well. To all my knowledge there are not even Windows drivers for that board, at least i never heared of someone doing such development works for it. I must assume HP did design those drivers for HP-UX on their own, maybe they just used parts of the IBM-AIX drivers for a startup. *blink* As of now FireGL Linux drivers for the IBM based adapters are only availabel for Linux/x86. I do not expect that to change in any way because this is no longer a hot product. Its funny, i have seen experimental machines with x86 CPUs since about 4 years but i have never got a matching graphics boards to my hands for plugging it into there. All most recent were AGP or AGP-PRO based designs. I hear conflicting things, some people tell me this card is Radeon based/compatible, but the current CVS XF86 doesnt detect it as such, would it work if it recognised the PCI ID as a radeon card? or is it just not compatible atall? Its a grafics board that is based on an IBM asic. Its truely not a Radeon, those others are false. The ATI-supplied binary drivers should aparrently support this card, but the only machine i have which will take this card at all is an Alpha, and thus wont run the x86 binaries supplied by ATI. My 2nd best guess would be - leave it in the original box and run HP-UX with it. As others did already write, IBM has not released any asic specs. My #1 guess would be - trade it to someone who needs it, those boards are getting rarer day by day (= you can get _much_ money from a suddenly frozen HP-UX user) and buy some mainstram 8500 Radeon 9500 Pro or higher. At least I assume an AGP speed 4x/8x @ 32 bit card might operate faster than a PCI speed 1x @ 64 bit. -Alex. PS: not speaking for my copmany, i were just curios myselves about that device. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] ATI Rage 128 DRI
Now, the problem is that I install that XFree86 version: XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 With this version, when I active the DRI with last mentioned r128.o driver I get a Segmentation Fault with some applications. I think only the applications who need Open GL are crashing. Where did you get libGL.so.1.2 and radeon_dri.so from? I have a Gentoo 1.2 Linux. With the package manager I have installed the new version of XFree86 server. The emerge app downloads, compile and install the package dependences, then I think that libGL and _dri.so dinamic libraryes had been downloaded by the emerge. I can't download the x11-base/xfree-drm modules (they are masked): $emerge -s xfree * x11-base/xfree-drm [ Masked ] Latest version available: 4.2.99.4 Latest version installed: [ Not Installed ] Homepage: http://www.xfree.org Description: Xfree86 Kernel DRM modules Then I have compiled manually the drm-kernel modules from that package: -rw-r--r--1 root root 1557870 02-01 18:50 /stuff/kernel/rage128-20021022-linux.i386.tar.bz2 I compile drm packages (i686 compilation) and I only copy the r128.o driver to /lib/modules... (I remove last and I modprobe successfully the new module) -rw-r--r--1 root root 120625 02-03 16:32 /lib/modules/2.4.18-xfs/kernel/drivers/char/drm/r128.o All _dri.so and libGL.so.1.2 I think they have been installed by the emerge (i686 compiled): # dir /usr/X11R6/lib/modules/dri/ total 10556 drwxr-xr-x2 root root 133 02-01 11:46 . drwxr-xr-x9 root root 4096 01-30 22:15 .. -rwxr-xr-x1 root root 1707339 01-30 22:15 gamma_dri.so -rwxr-xr-x1 root root 1493389 01-30 22:15 i810_dri.so -rwxr-xr-x1 root root 1515684 01-30 22:15 i830_dri.so -rwxr-xr-x1 root root 1536876 01-30 22:15 mga_dri.so -rwxr-xr-x1 root root 1536959 01-30 22:15 r128_dri.so -rwxr-xr-x1 root root 1542162 01-30 22:15 radeon_dri.so -rwxr-xr-x1 root root 1457672 01-30 22:15 sis_dri.so # dir /usr/lib/opengl/xfree/lib/ total 1116 drwxr-xr-x2 root root 105 01-30 22:15 . drwxr-xr-x5 root root 47 01-30 22:15 .. -rw-r--r--1 root root 614990 01-30 22:15 libGL.a -rw-r--r--1 root root 777 01-30 22:15 libGL.la lrwxrwxrwx1 root root 12 01-30 22:15 libGL.so - libGL.so.1.2 lrwxrwxrwx1 root root 12 01-30 22:15 libGL.so.1 - libGL.so.1.2 -rwxr-xr-x1 root root 519209 01-30 22:15 libGL.so.1.2 lrwxrwxrwx1 root root 12 01-30 22:15 libMesaGL.so - libGL.so.1.2 Can you run a client in gdb and provide a backtrace? mmm Them most simple: glxinfo $ glxinfo name of display: :0.0 Segmentation fault $gdb glxinfo (gdb) run Starting program: /usr/X11R6/bin/glxinfo (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 1024 (LWP 20876)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... name of display: :0.0 (no debugging symbols found)...(no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 20876)] 0x400091db in _dl_relocate_object () from /lib/ld-linux.so.2 (gdb) bt #0 0x400091db in _dl_relocate_object () from /lib/ld-linux.so.2 #1 0x4033e374 in dl_open_worker () from /lib/libc.so.6 #2 0x4000ab00 in _dl_catch_error () from /lib/ld-linux.so.2 #3 0x4033e63f in _dl_open () from /lib/libc.so.6 #4 0x403bd387 in dlopen_doit () from /lib/libdl.so.2 #5 0x4000ab00 in _dl_catch_error () from /lib/ld-linux.so.2 #6 0x403bd7d0 in _dlerror_run () from /lib/libdl.so.2 #7 0x403bd3c6 in dlopen@@GLIBC_2.1 () from /lib/libdl.so.2 #8 0x4010d0a3 in OpenDriver () from /usr/lib/libGL.so.1 #9 0x4010d554 in register_extensions_on_screen () from /usr/lib/libGL.so.1 #10 0x4010d66c in __glXRegisterExtensions () from /usr/lib/libGL.so.1 #11 0x4010d101 in Find_CreateScreenFuncs () from /usr/lib/libGL.so.1 #12 0x4010d3ba in driCreateDisplay () from /usr/lib/libGL.so.1 #13 0x400f59e0 in __glXInitialize () from /usr/lib/libGL.so.1 #14 0x400f2ce7 in glXGetConfig () from /usr/lib/libGL.so.1 #15 0x400f3409 in glXChooseVisual () from /usr/lib/libGL.so.1 #16 0x0804c0f5 in strcpy () #17 0x40257671 in __libc_start_main () from /lib/libc.so.6 The /usr/lib/libGL are softlinks to /usr/lib/opengl/xfree/lib (Do you need an especial backtrace from any app?) $ dir /usr/lib/libGL* lrwxr-xr-x1 root root 38 01-30 22:16 /usr/lib/libGL.so - /usr/lib/opengl/xfree/lib/libGL.so.1.2 lrwxr-xr-x1 root root 38 01-30 22:16 /usr/lib/libGL.so.1 - /usr/lib/opengl/xfree/lib/libGL.so.1.2 -rw-r--r--1 root root 710028 01-30
RE: [XFree86] Radeon mobility U1
what if you configure it as it were a Mobility M6? please have a look after the XF86Config man page. there is a method to make X11 and the driver think that the chip ID of your board is that of a different one. -Alex. -Original Message- From: Nik A. Melchior [mailto:[EMAIL PROTECTED]] Sent: Saturday, February 01, 2003 20:27 To: [EMAIL PROTECTED] Subject: [XFree86] Radeon mobility U1 To the radeon driver maintainer, I recently tried out a beta of 4.3, and it doesn't support the graphics chip in my laptop (Radeon Mobility U1, chipID 4336). Will support be added for this chip? What can I do to help? Thank you, -- Nik Melchior Washington University GPG Key Fingerprint (see http://www.gnupg.org/): F824 BB7F 5424 04D0 0EBF 2AE7 7BB9 533C 380A 0462 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] ATI Radeon 9100 Support
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] I did go to the /lib/modules/fglrx/build_mod and executed make.sh. I got and error that the shell script could not interpret the proper library. Now what? Doug strange situation. libraries are binaries and wont get interpreted. there must be a log-file from the build in the same directory. some make.log or similiar, cant remember exactly right now. can you provide this? -Alex. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] DGA on OpenBSD (ATI)
On Thu, 30 Jan 2003 20:45:27 -0700 (MST) Marc Aurele La France [EMAIL PROTECTED] wrote: On Fri, 31 Jan 2003, Sam Thursfield wrote: Having enabled ext-mod completely in my xf86config, I noticed that the dga test program responded with XF86DGAGetVideo: failed to map video memory (Operation not allowed). I *am* running it as root. The card is an ATI Rage 128, though it breaks just the same on my 3D Pro Turbo. The attached might do the trick (untested). Thanks, but it still comes up with the same error. -sam ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] still having issues with 845g
I'm a happy man. That was it. On Fre, 2003-01-31 at 17:07, David Burge wrote: (II) I810(0): [drm] drmSetBusid failed (6, PCI:0:2:0), Permission denied (EE) I810(0): [dri] DRIScreenInit failed. Disabling DRI. Make sure the DRM was built with the same compiler as the kernel; in particular, if it was built with gcc 2.x, try building it with 3.x, or vice versa. -- 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 -- David Burge [EMAIL PROTECTED] ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Query on XFree86 Support for Intel 845GLLY Chipset
Hi, Just today I have subscribed to XFree86 list. I have recently installed Redhat Linux 8.0 release in my box. I am a Newbie to Linux. The problem I am facing right now is the Configuration of the View Card for the Intel Motherboard 845GLLY Chipset. Checked out on the same with the Linux User Groups and they directed me to XFree86.org for the latest CVS repository. Could someone let me know more info on support for Intel 845GLLY Chipset for Linux XServer. I would also like to know what source is to be downloaded and how to Install the same in my machine. The Linux Kernel used by me is 2.4.18-14, this is the kernel which came along with the Redhat Linux 8.0. Thanx, -Sriram Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com Buy the best in Movies at http://www.videos.indiatimes.com Bid for for Air Tickets @ Re.1 on Air Sahara Flights. Just log on to http://airsahara.indiatimes.com and Bid Now ! ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Dual head headaches
I have been having some issues lately with dual head that are about to drive me nuts. About a month ago I purchased an ATI Radeon 7500 PCI to replace the primary card on the first monitor, which was an ATI Rage 128 PCI. The old configuration looked like this: Rage 128 PCI with monitor 1, Matrox Millenium PCI with monitor 2. This configuration worked beautifully. Xinerama in Gnome was a joy. Well, the headaches began when I replaced the Rage 128 with the Radeon. New configuration: Radeon with monitor 1, Rage 128 with monitor 2, Matrox Millenium on the closet floor. I can not get these two cards to play nice together. I have tried just about everything. X refuses to start unless the Rage 128 is disabled, otherwise it craps out with the following message: xf86MapPciMem: could not nmap..blah, blah. I'm sure a few of you have seen this before. A search on Google turns up a limited number of pages; most asking how to fix this, but few offering solutions. Anyhow, the few solutions offered did help. I'm attaching my XF86Config file for all to dissect. I'm about to pull the Rage 128 out and put the old Matrox back in. I thought I would see what a few of you had to say first. Thanks! William ## Begin XF86Config Section Module Loaddbe # Double buffer extension SubSection extmod Optionomit xfree86-dga # don't initialise the DGA extension EndSubSection Loadtype1 Loadspeedo Loadfreetype Loadxtt Loadglx #lOADdri EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb #FontPath /usr/X11R6/lib/X11/fonts/local/ FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/100dpi/:unscaled FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/TrueType/ FontPath /usr/X11R6/lib/X11/fonts/freefont/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ ModulePath /usr/X11R6/lib/modules EndSection Section InputDevice Identifier Keyboard1 Driver Keyboard Option AutoRepeat 500 30 Option XkbRules xfree86 Option XkbModel logiitc Option XkbLayout us EndSection Section InputDevice Identifier Mouse1 Driver mouse Option ButtonNumber 5 Option Device /dev/psaux Option InputFashion Mouse Option Name Autodetection Option Protocol imps/2 Option Vendor Sysp Option ZAxisMapping 4 5 EndSection Section Monitor Identifier Monitor1 HorizSync 31.5 - 82.0 VertRefresh 48-160 EndSection Section Monitor Identifier Monitor3 HorizSync 31.5 - 82.0 VertRefresh 48-160 EndSection Section Device Identifier Device1 Driver radeon BusID PCI:0:14:0 EndSection Section Device Identifier Device2 Driver r128 BusID PCI:0:13:0 EndSection Section Screen Identifier Screen1 Device Device1 Monitor Monitor1 DefaultDepth 16 Subsection Display Depth 8 Modes ViewPort0 0 EndSubsection Subsection Display Depth 16 Modes 1024x768 ViewPort0 0 EndSubsection Subsection Display Depth 24 Modes ViewPort0 0 EndSubsection EndSection Section Screen Identifier Screen2 Device Device2 Monitor Monitor2 DefaultDepth 16 Subsection Display Depth 8 Modes ViewPort0 0 EndSubsection Subsection Display Depth 16 Modes 1024x768 ViewPort0 0 EndSubsection Subsection Display Depth 24 Modes ViewPort0 0 EndSubsection EndSection Section ServerLayout Identifier Simple Layout Screen Screen2 Screen Screen1 RightOf Screen2 Option Xinerama true InputDevice Mouse1 CorePointer InputDevice Keyboard1 CoreKeyboard EndSection # Section DRI #Mode 0666 # EndSection __ The NEW Netscape 7.0 browser is now available. Upgrade now! http://channels.netscape.com/ns/browsers/download.jsp Get your own FREE, personal Netscape Mail account today at http://webmail.netscape.com/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
