CVS Update: xc (branch: trunk)
CVSROOT:/home/x-cvs Module name:xc Changes by: [EMAIL PROTECTED] 03/01/15 22:25:53 Log message: o Fixed a problem in the xedit regex library, was using wrong code to reallocate space when merging character matches in a single string match. The problem did not appear early because the buffer size is increased at 16 (or 32 for case insensitive) bytes at a time. o Added a new syntax-highlight definition to allow easier viewing XFree86 log files. It will highlight the XFree86 version, the release date, the build operating system as well as (WW) warning, (EE) error lines, and use a very pale background color for (==) default, (**) config and (--) probed lines. Log of command line options and uncommon (notice, not implemented and unknown) messages will be highlighted almost identically to warnings. Modified files: xc/programs/xedit/lisp/modules/: Imakefile xedit.lsp xc/programs/xedit/lisp/re/: rec.c Added files: xc/programs/xedit/lisp/modules/progmodes/: xlog.lsp Revision ChangesPath 1.13 +2 -1 xc/programs/xedit/lisp/modules/Imakefile 1.10 +3 -1 xc/programs/xedit/lisp/modules/xedit.lsp 1.4 +5 -5 xc/programs/xedit/lisp/re/rec.c ___ Cvs-commit mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/cvs-commit
auto-configuration vs imake
On Wed, Jan 15, 2003 at 01:03:04AM -0500, Vladimir Dergachev wrote: * I did say it was a _difficult_ change * I was not planning on doing it by hand - rather making a tool that would use Imakefiles as input * My take on it was that at the very least it would be an interesting exercise in using autoconf. I have converted a few of my other projects to it and things do not look that bad. The approach I've been thinking about for a while is to replace as much of the .cf data as possible with auto-generated data, and then have imake do it's usual thing. That would give a balance between automatic build configuration and compatibility with existing Imakefiles. I think it would also have the advantage of being a doable task. Imake already does some basic auto-detection, but it's limited and it does it every time it's run. When building something large like the XFree86 tree, it'd be better if that auto-detection was done once and the cached data used for the rest of the tree. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Debugging in RH8?
Anyone have any tips on how to debug XFree86 modules under RH8? It looks like GDB hacked for modules doesn't work on that platform, or at least the version I have doesn't. Mark. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Debugging in RH8?
On Wed, Jan 15, 2003 at 01:20:40PM -0800, Mark Vojkovich scrawled: Anyone have any tips on how to debug XFree86 modules under RH8? It looks like GDB hacked for modules doesn't work on that platform, or at least the version I have doesn't. Mark, Mike Harris is working on this in his latest package set, IIRC. -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne msg00152/pgp0.pgp Description: PGP signature
RE: Debugging in RH8?
On Thu, 16 Jan 2003, Alexander Stohr wrote: Date: Thu, 16 Jan 2003 01:26:18 +0100 From: Alexander Stohr [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Content-Type: multipart/alternative; boundary=--=_NextPart_ST_19_22_36_Wednesday_January_15_2003_25311 Subject: RE: Debugging in RH8? ftp://people.redhat.com/mharris/gdb-xfree86 Let me know if there are any problems. Can you please adjust user permissions there? Thanks. Which perms exactly? All dirs and files are world readable in there that I can see. Only thing that was out of the ordinary was an empty dir patches, but the patches are in the raw-sources dir instead. -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
RE: Debugging in RH8?
On Thu, 16 Jan 2003, Alexander Stohr wrote: Date: Thu, 16 Jan 2003 01:55:08 +0100 From: Alexander Stohr [EMAIL PROTECTED] To: Mike A. Harris [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Content-Type: multipart/alternative; boundary=--=_NextPart_ST_19_52_04_Wednesday_January_15_2003_12365 Subject: RE: Debugging in RH8? on 2nd try i got the listing now - the read error has vanished. Ah.. could be some weird firewall interaction issue. Some people have reported inability to use our people.redhat.com ftpsite in the past under rare circumstances. Could also just be a random net weirdness.. Take care, TTYL -- Mike A. Harris ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: LgProbe or AlpProbe undefined Symbol
Wayne Gowcher wrote (in a message from Wednesday 15) Can anyone tell me why dlopen is trying to resolve the sysmbols LgProbe and AlpProbe when module cirrus_drv.so is loaded ? Is it a problem with my compile ? With dlopen ? Any hints greatly appreciated. Please note if I comment both subprobe = LgProbe; and subprobe = AlpProbe; The cirrus module has sub-modules to handle alpine and laguna chipsets. It is supposed to load the appropriate sub-module once it has probed the chipset. For some reason the X server fails to load the sub-module in your case. I'm not familiar with Linux/mips so I don't know if it's expected that the X server uses the dlopen() based module loader instead of the internal XFree86 ELF loader on this platform. XFree86 modules don't work well with dlopen() and this method should be avoided if possible. On OpenBSD, I prefer to build a static X server (DoLoadableServer = NO) on architectures where the XFree86 loader doesn't work for some reason, than falling back to dlopen(). See section 17 of the DESIGN doc for more details. Matthieu ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
[Fonts] Re: Installation of Adobe's free Asian CID fonts
[EMAIL PROTECTED] (James A. Crippen) $B$5$s$O=q$-$^$7$?(B: (B (B JC There should be an automated tool like mkfontdir and mkcfm that knows (B JC how to read the CIDFonts and CMap directories and generates the proper (B JC fonts.scale file... (B (B Thanks for volunteering. (B (B I'll try a shell/sed/awk version first. If that doesn't end up too (B hard I might write a C version. But I have to get things working by (B hand before anything else... (^_^) (B (BI've added the attached perl script to SuSE Linux, which does (Bsomething like that. cidfont-x11-config Description: Binary data (B (B-- (BMike Fabian [EMAIL PROTECTED] http://www.suse.de/~mfabian $B?gL2ITB-$O;E;v$NE($@!#(B
Re: [I18n] locale.alias is missing en_GB.UTF-8
Also out of interest, I noticed that en was an alias of en_US, is there a reason for this? Historical reasons? Because Americans wrote the software? Because the population of America is larger then that of Britain? Because it doesn't really matter? In other cases where several countrys have adopted to speak the same language the origional country is the default, eg de == de_DE not de_AT or de_CH etc. Is modern-day Germany really the source of modern German? de is only German since 1500 (German from 1050 to 1500 is gmh), and doesn't include the spoken language of north Germany (nds - Low German)*. Did Austria speak a different language prior to recent times? How did a bunch of city states that didn't come together until the 1880's force Austria, the head of the Austrian-Hungary empire, to change its language? * Disputed by some Germans, but that's how the tags are assigned. I strongly suspect that the language covered by de didn't originate soley in Germany; that it's the union of several dialects over that whole area that have been converging and diverging for the past few centuries. Why does this matter? Because it makes it clear that language to country assignments are arbitrary, which they are in real life. For every case where you can point to one origin country, there are cases - Basque, German - where you can't point to one country as the origin. ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
[I18n] Re: multiple xkb layouts
Nerijus Baliunas wrote: If I have 2 layouts in one file, how KDE and Gnome applets (gswitchit for example) will show them? They should probably be adopted to new scheme? Now they let to choose from layout files in xkb/symbols directory as I understand it, yes? Regards, Nerijus For KDE 3.x I can advise you kkbswitch (apps.kde.com), so you don't need to use native kde tool for keyboard. Regards, Damir ___ I18n mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/i18n
Re: [XFree86] System crashes when initdefault=5
On Tue, 14 Jan 2003, C. Brewer wrote: Unlikely IMHO. It's most likely that you're just experiencing the reason that DRI is disabled by default on PCI Radeon. The best place to inquire about this though is the dri-devel mailing list on sourceforge. All DRI related topics are best covered there. And here I know Mike's just baiting me.. Baiting you? Geeze, you try to help someone and offer detailed information, and you're the enemy all of a sudden. it does work my Radeon 7000 PCI...but its not easy to make work. If it doesn't work automatically and work good, and work on the majority of hardware out there with various PCI Radeons, then for all intents and purposes, it does not work. It's very buggy, and not worthy of shipping with it enabled by default. I posted a fix to the Xpert list a while back and the short version entails changing a couple files and adding some stuff to the config...Im too tired to go into it..but its googleable...(try my name and site:xfree86.org). I'm aware of a few people who posted patches to one list or another, however I certainly didn't memorize their names, and I was just trying to be helpful to you. Anyways..It doesnt work on _all_ machines..but its better than the pessimistic it doesnt work at all reply that keeps open source down. If it doesn't work automatically and work good, and work on the majority of hardware out there with various PCI Radeons, then for all intents and purposes, it does not work. It's very buggy, and not worthy of shipping with it enabled by default. Hence it doesn't work. Something is considered to work, when it works on the majority of hardware that is out there, not when it sortof works on my system when I play around in agony for hours. If it worked, then you wouldn't have posted a message here in the first place. -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] X-window dont resize and mouse-mark dont work after systemclock change
Regarding: X-window dont resize and mouse-mark dont work after systemclock change Email: [EMAIL PROTECTED] XFree86 Version: XFree 4.2.0 (Redhat Linux release 4.2.0-72) OS: Linux Redhat v.8.0 (psyche) Kernel: 2.4.18-14 Area: Xlib, Xterm (all X-applications) Server: not server related Video Card: ATI Radeon Mobility 9000, but I dont think this is relevant to the problem. Description: Problemdescription: The Xterm windows and other windows become fixed in size and impossible to resize after the systemclock has changed back in time. If system clock is adjusted forward, the windows again became resizeable. Another problem is that it is impossible to mark a specific area (for copying for instance) using the mouse after clock is changed backwards. This error allso dissapear when clock is adjusted ahed in time (note: more ahed than since last X restart+ normal runtime). br These problems dissapear if restarting the X. br This problem has been around for a long time and I have tried to search for a resolution. The problem shows up for laptops which go to suspend mode. My three last laptops have had this problem, and that is two Compaq and now a Dell (Inspiron 8200). I think the problem is related to the fact that the system clock is not correct preserved after wakeup after suspend. This error is very anoying fro users of laptops. Repeat By: All Xterms and other X client application behave this way ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] XFree86 4.2.99.3
Hello, I recently upgraded to the 4.2.99.3 snapshot, and it all seems to be working fine for me. I was just wondering if anyone knew how to get rid of the red cursors that it uses, and get back the traditional black ones. I've searched the WWW for this sort of information, but haven't yet managed to find any usefull advice. I'm using the linux x68 version (I downloaded the binaries). If any other information is needed, just let me know. Thank you Steven ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Problem with Red Hat Linux
I have just installed Red Hat Linux on a Dell GX260 desktop computer with the standard video adapter which is integrated on the motherboard. I have attached a log file with the errors that have occurred. Thanks, Art Rathke [EMAIL PROTECTED] 586-977-1034 XFree86.0.log Description: Binary data XFree86.setup.log Description: Binary data
Re: [XFree86] XFree86 4.2.99.3
Steven Gurr wrote: I recently upgraded to the 4.2.99.3 snapshot, and it all seems to be working fine for me. I was just wondering if anyone knew how to get rid of the red cursors that it uses, and get back the traditional black ones. I've been looking at this myself. `man Xcursor` will give you a bit more information, but if you edit the file /usr/X11R6/lib/X11/icons/default/index.theme and remove the line Inherits=redglass or change it to Inherits= then startx again, it should revert to the solid cursor. I've just found a way to do this on a per-user basis, too. Create a ~/.icons/default/index.theme reading [Icon Theme] Inherits= Also, some window managers might be able to load their own cursors. YMMV. Glyn -- Her covering travelling career She can really move, Oh velveteen ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Beforelight screensaver is totally nonfunctional
For the last few XFree86 releases, the beforelight screensaver has been nonfunctional if ran with the XFree86 core server. [mharris@asdf mharris]$ beforelight X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 113 (X_KillClient) Value in failed request: 0x161 Serial number of failed request: 20 Current serial number in output stream: 22 It fails as far back as 4.0.3 at least. After a bit of debugging I just debugged this for a while and beforelight itself seems to work ok, but what is failing is the X server somehow it seems. If you do a clean X server startup, then do: xset s 5 xset s activate beforelight It will come on in 5 seconds time. However, if you kill the beforelight process, then start it up again, you will get the errors we've put above. This is also testable inside Xnest by doing: xinit -- $(which Xnest) :1 It seems to me like some resource is being allocated in the X server when beforelight starts up the first time, but isn't getting released when it is sent SIGINT (or some other signal). This problem is 100% reproduceable every time for all releases I've tested it on (4.0.3, 4.1.0, 4.2.0, 4.2.1, CVS), and occurs on x86, Alpha, ia64 platforms at least. A BSD user also acknowledged the problem on IRC too. I fiddled with it for a brief while, however similar screensaver exists in xscreensaver, so I decided it wasn't worth time fixing. Nonetheless, I thought someone else might be interested in knowing about the problem as it seems to be an X server bug. If anyone is interested in debugging/troubleshooting further, I can provide more info. Probably best to disable beforelight at build time otherwise. TTYL -- Mike A. Harris ftp://people.redhat.com/mharris OS Systems Engineer - XFree86 maintainer - Red Hat ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] System crashes when initdefault=5
On Mit, 2003-01-15 at 04:12, Mike A. Harris wrote: On Tue, 14 Jan 2003, Schultz, Dale C. wrote: I've been struggling with this for about a month now and thought someone could help me out. I have an AOpen motherboard with built-in AGP graphic chip. To get better 3D performance I installed and ATI Radeon 7000 PCI adapter. The default Radeon driver does not support direct rendering to PCI cards. So I used a hack to enable PCI and recompiled my complete xserver from cvs. All worked great until I rebooted my system with it still set to initdefault 5 in the inittab file. The system comes almost all the way up but when the screen switches from text mode to graphics mode the system hangs. The reset button is the only thing that can get it going again. Radeon PCI DRI is supported only on the Alpha processor. It does not work on x86 architecture, which is why it isn't enabled in XFree86 by default for x86. To enable it, requires a slight kernel modification, as well as a slight X server modification. The result however just shows why it is disabled by default. A few people have posted some patches that attempt to make Radeon PCI DRI also work on x86, however I don't believe that XFree86 sources have applied any of these patches, and I don't believe that they've been adequately tested in the wild yet. Mike, this is FUD. First of all, PCI GART has been enabled on powerpc as well for a while, and several people have reported it to work well with PCI cards on x86. Anyone interested in testing out these types of patches need not have a Radeon PCI though, you can just disable AGP and an AGP card should work as a PCI one for the purposes of testing and debugging. No, because that seems to be the reason why it's still disabled: it doesn't work well with AGP cards. Don't ask me why. Anyway, I don't think this is a good reason to keep it disabled because PCI GART will only be used with Option ForcePCIMode. But owners of PCI cards would at least have a chance to try it without having to modify the source. I've been meaning to rip out the ugly code that disables it for a long time but sadly haven't gotten around to it yet. The strange part is that if I set inittab to initdefault 3 and use the startx command all works fine. The biggest problem (not for me) is the login. When my kids boot up the system and don't see the graphical login screen they panic and shut the machine off (just about as bad as a crash). That's odd. Indeed. I've checked the Xfree86.log file and it ends abruptly when the system hangs around the area when the drm extensions(?) are being initialized. If I disable drm in the XF config file the system doesn't hang, but of course the 3D performance sucks, just ask Tuxracer... Sounds like the problem that occurs on x86 which caused Radeon PCI to be disabled by default. To me it rather sounds like using an X server where PCI GART is enabled with a DRM where it isn't. -- 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] remove
___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] System crashes when initdefault=5
On Mit, 2003-01-15 at 15:41, Schultz, Dale C. wrote: As I stated. The xserver and all apps do work fine and the system appears quite stable as long as I ONLY use startx to bring up x. Is it possible that somehow a different DRM is used with xdm? -- 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] startx fails
Hi I installed OpenBSD 3.2 on a PC (Asus AL440LX mainboard, Diamond Viper 330 graphic card). When I enter startx the following message appears: (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver in pcvt compatibility mode (version 3.32) (WW) GARTInit: AGPIOC_INFO failed (Device not configured) XFree86 Version 4.2.1 (for OpenBSD) / 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: OpenBSD 3.2 i386 Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Jan 15 16:34:34 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found ... Is there anybody who can help me fix the problem? Thanks Christian ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86(TM) Bug Report] X-window dont resize andmouse-mark dont work after systemclock change
On Mit, 2003-01-15 at 11:31, Jan Helge Salvesen wrote: Regarding: X-window dont resize and mouse-mark dont work after systemclock change [...] Server: not server related Yes, it is. This is a long standing server bug which has been fixed in CVS. -- 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] remove
Follow the link at the bottom of the page to unsubscribe yourself. Georgina - Original Message - From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, January 15, 2003 9:41 AM Subject: [XFree86] remove ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 == this one in particular ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] startx fails
Hi I installed OpenBSD 3.2 on a PC (Asus AL440LX mainboard, Diamond Viper 330 graphic card). When I enter startx the following message appears: (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver in pcvt compatibility mode (version 3.32) (WW) GARTInit: AGPIOC_INFO failed (Device not configured) XFree86 Version 4.2.1 (for OpenBSD) / 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: OpenBSD 3.2 i386 Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Jan 15 16:34:34 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found ... Is there anybody who can help me fix the problem? Thanks Christian ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] I'm sorry for spam
Hi there Ewerything is working ... /etc/rc.conf ... kernel_secure :) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] startx fails
Title: RE: [XFree86] startx fails not beeing that much familiar with BSD, but the messages do indicate to me that your mainboard chipset is not supported by your AGP(gart) implementation. Check what sort of PCI-PCI/AGP bridge you do have and find a matching driver for it, or find out why AGP does not load on your box. -Alex. -Original Message- From: (©¿©) [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 16:48 To: [EMAIL PROTECTED] Subject: [XFree86] startx fails Hi I installed OpenBSD 3.2 on a PC (Asus AL440LX mainboard, Diamond Viper 330 graphic card). When I enter startx the following message appears: (--) checkDevMem: using aperture driver /dev/xf86 (--) Using wscons driver in pcvt compatibility mode (version 3.32) (WW) GARTInit: AGPIOC_INFO failed (Device not configured) XFree86 Version 4.2.1 (for OpenBSD) / 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: OpenBSD 3.2 i386 Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/XFree86.0.log, Time: Wed Jan 15 16:34:34 2003 (EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Fatal server error: no screens found ... Is there anybody who can help me fix the problem? Thanks Christian ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] I subscribed to the xpert group but I am still not getting any e-mail ???
Title: RE: [XFree86] I subscribed to the xpert group but I am still not getting any e-mail ??? xpert group got merged with XFree86 mailing list and does no longer exist. subscribe to devel @ xfree86.com if you do want the developer talks. -Alex. -Original Message- From: Herman Buel [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 17:34 To: [EMAIL PROTECTED] Subject: [XFree86] I subscribed to the xpert group but I am still not getting any e-mail ??? Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now
[XFree86] X86Config
Scusate ma non parlo l'inglese e non lo so scrivere ma un po' lo capisco soprattutto i termini tecnici. Ho una scheda video Matrox Millenium che non riesce a riconoscere il sistema Slackware Linux, che ho installato sulla mia macchina assieme ad altri sistemi. Potreste darmi indicazioni precise come configurare il display dato che con X86cfg non ci sono riuscito ci sono dei parametri che riconoscano la scheda Matrox Millenium 400 Tomaso Satta ? ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] sis 6325 s-video(TV-OUT) problem
Like I said: Google is your friend. www.winischhofer.net/linuxsisvga.shtml or wait for 4.3 Thomas Wang Jun wrote: I'm new to this list, and first of all want to thank you all for such a nice graphic system. I have a laptop which video chipset is sis 6325, this video device also has s-video(TV-OUT) output. I wanna to use this port but I don't know does this s-video(TV-OUT) port could worked under linux or not. Does somebody know about this issue? my os is turbolinux workstation 7 and XFree86 version is 4.1.0 If cvs head of XFree86 could solve this problem, I'd like to try it. I attach three file - lspci.txt XF86Config and XFree86.0.log Best Regards, Wang Jun 00:00.0 Host bridge: Silicon Integrated Systems [SiS]: Unknown device 0650 (rev 01) Flags: bus master, medium devsel, latency 32 Memory at e000 (32-bit, non-prefetchable) [size=64M] Capabilities: [c0] AGP version 2.0 00: 39 10 50 06 07 00 10 22 01 00 00 06 00 20 80 00 10: 00 00 00 e0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 00:01.0 PCI bridge: Silicon Integrated Systems [SiS] 5591/5592 AGP (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 9000-9fff Memory behind bridge: dfe0-dfef Prefetchable memory behind bridge: cfc0-dfcf 00: 39 10 01 00 07 01 00 00 00 00 04 06 00 40 01 00 10: 00 00 00 00 00 00 00 00 00 01 01 00 90 90 00 20 20: e0 df e0 df c0 cf c0 df 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 00:02.0 ISA bridge: Silicon Integrated Systems [SiS] 85C503/5513 Flags: bus master, medium devsel, latency 0 00: 39 10 08 00 0f 00 00 02 00 00 01 06 00 00 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:02.2 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07) (prog-if 10 [OHCI]) Subsystem: Uniwill Computer Corp: Unknown device 7001 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at dfffa000 (32-bit, non-prefetchable) [size=4K] 00: 39 10 01 70 17 01 80 02 07 10 03 0c 08 40 00 00 10: 00 a0 ff df 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 84 15 01 70 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 04 00 50 00:02.3 USB Controller: Silicon Integrated Systems [SiS] 7001 (rev 07) (prog-if 10 [OHCI]) Subsystem: Uniwill Computer Corp: Unknown device 7001 Flags: bus master, medium devsel, latency 64, IRQ 11 Memory at dfffb000 (32-bit, non-prefetchable) [size=4K] 00: 39 10 01 70 17 01 80 02 07 10 03 0c 08 40 00 00 10: 00 b0 ff df 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 84 15 01 70 30: 00 00 00 00 00 00 00 00 00 00 00 00 0b 01 00 50 00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0) (prog-if 80 [Master]) Subsystem: Silicon Integrated Systems [SiS] SiS5513 EIDE Controller (A,B step) Flags: bus master, fast devsel, latency 128 [virtual] I/O ports at 01f0 [virtual] I/O ports at 03f4 [virtual] I/O ports at 0170 [virtual] I/O ports at 0374 I/O ports at ff00 [size=16] 00: 39 10 13 55 05 00 00 00 d0 80 01 01 00 80 80 00 10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 20: 01 ff 00 00 00 00 00 00 00 00 00 00 39 10 13 55 30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00:02.6 Modem: Silicon Integrated Systems [SiS]: Unknown device 7013 (rev a0) (prog-if 00 [Generic]) Subsystem: Uniwill Computer Corp: Unknown device 4003 Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at d400 [size=256] I/O ports at d000 [size=128] Capabilities: [48] Power Management version 2 00: 39 10 13 70 05 01 90 02 a0 00 03 07 00 40 00 00 10: 01 d4 00 00 01 d0 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 84 15 03 40 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 03 34 0b 00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]: Unknown device 7012 (rev a0) Subsystem: Uniwill Computer Corp: Unknown device 5101 Flags: bus master, medium devsel, latency 64, IRQ 10 I/O ports at dc00 [size=256] I/O ports at d800 [size=128] Capabilities: [48] Power Management version 2 00: 39 10 12 70 05 01 90 02 a0 00 01 04 00 40 00 00 10: 01 dc 00 00 01 d8 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 84 15 01 51 30: 00 00 00 00 48 00 00 00 00 00 00 00 0a 03 34 0b 00:03.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 10/100 Ethernet (rev 90) Subsystem: Uniwill Computer Corp: Unknown device 5100 Flags: bus master, medium devsel, latency 64, IRQ 5 I/O ports at cc00 [size=256] Memory at dfff9000 (32-bit, non-prefetchable) [size=4K] Expansion ROM at dffc [disabled] [size=128K] Capabilities: [40] Power Management version 2
Re: [XFree86] need xf86PciInfo.h for sis650 on board video
Clary Harridge wrote: Hi can you advise on this problem please ? I need xf86PciInfo.h mods for a sis650 on board video chipset using X 4.2.1 on a p4 Asus motherboard. No, you don't. Don't you guys ever use google or any other search engine? Number one on google on this topic: www.winischhofer.net/linuxsisvga.shtml Thomas X -configure shows XFree86 Version 4.2.1 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 3 September 2002 If the server is older than 6-12 months, or if your card is newer than the above date, look for a newer version before reporting problems. (See http://www.XFree86.Org/) Build Operating System: FreeBSD 4.4-RELEASE-p1 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: Tue Jan 14 17:49:40 2003 List of video drivers: atimisc r128 radeon mga glint nv tga s3 s3virge sis rendition neomagic i740 tdfx savage cirrus vmware tseng trident chips apm fbdev i128 ati i810 ark cyrix siliconmotion vesa vga 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. When reporting a problem related to a server crash, please send the full server output, not just the last messages. This can be found in the log file /var/log/XFree86.0.log. Please report problems to [EMAIL PROTECTED] scanpci output: pci bus 0x cardnum 0x00 function 0x00: vendor 0x1039 device 0x0650 SiS Device unknown CardVendor 0x1043 card 0x8079 (Card unknown) STATUS0x2210 COMMAND 0x0007 CLASS 0x06 0x00 0x00 REVISION 0x01 BIST 0x00 HEADER 0x80 LATENCY 0x20 CACHE 0x00 BASE0 0xe800 addr 0xe800 MEM pci bus 0x cardnum 0x01 function 0x00: vendor 0x1039 device 0x0001 SiS SG86C201 STATUS0x COMMAND 0x0007 CLASS 0x06 0x04 0x00 REVISION 0x00 HEADER0x01 LATENCY 0x00 PRIBUS0x00 SECBUS 0x01 SUBBUS 0x01 SECLT 0x00 IOBASE0xd000 IOLIM 0xdfff SECSTATUS 0x2000 NOPREFETCH_MEMBASE 0xe780 MEMLIM 0xe7ff PREFETCH_MEMBASE 0xf000 MEMLIM 0xfebf NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT VGA_EN NO_ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x02 function 0x00: vendor 0x1039 device 0x0961 SiS Device unknown STATUS0x0200 COMMAND 0x000f CLASS 0x06 0x01 0x00 REVISION 0x10 BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00 BYTE_00x30a0bd8 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x02 function 0x02: vendor 0x1039 device 0x7001 SiS Device unknown CardVendor 0x1043 card 0x807a (Card unknown) STATUS0x8280 COMMAND 0x0017 CLASS 0x0c 0x03 0x10 REVISION 0x07 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x08 BASE0 0xe700 addr 0xe700 MEM MAX_LAT 0x50 MIN_GNT 0x00 INT_PIN 0x04 INT_LINE 0x05 pci bus 0x cardnum 0x02 function 0x03: vendor 0x1039 device 0x7001 SiS Device unknown CardVendor 0x1043 card 0x807a (Card unknown) STATUS0x8280 COMMAND 0x0017 CLASS 0x0c 0x03 0x10 REVISION 0x07 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x08 BASE0 0xe680 addr 0xe680 MEM MAX_LAT 0x50 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x09 pci bus 0x cardnum 0x02 function 0x05: vendor 0x1039 device 0x5513 SiS Device unknown CardVendor 0x1043 card 0x807a (Card unknown) STATUS0x COMMAND 0x0007 CLASS 0x01 0x01 0x80 REVISION 0xd0 BIST 0x00 HEADER 0x80 LATENCY 0x20 CACHE 0x00 BASE4 0xb801 addr 0xb800 I/O BYTE_00x87318331 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x02 function 0x07: vendor 0x1039 device 0x7012 SiS Device unknown CardVendor 0x1043 card 0x8072 (Card unknown) STATUS0x0290 COMMAND 0x0005 CLASS 0x04 0x01 0x00 REVISION 0xa0 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00 BASE0 0xa801 addr 0xa800 I/O BASE1 0xa401 addr 0xa400 I/O MAX_LAT 0x0b MIN_GNT 0x34 INT_PIN 0x03 INT_LINE 0x09 BYTE_00x04 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x03 function 0x00: vendor 0x1039 device 0x0900 SiS Device unknown CardVendor 0x1043 card 0x807c (Card unknown) STATUS0x0290 COMMAND 0x0007 CLASS 0x02 0x00 0x00 REVISION 0x90 BIST 0x00 HEADER 0x00 LATENCY 0x20 CACHE 0x00 BASE0 0xa001 addr 0xa000 I/O BASE1 0xe600 addr 0xe600 MEM MAX_LAT 0x0b MIN_GNT 0x34 INT_PIN 0x01 INT_LINE 0xff
[XFree86] [XFree86(TM) Bug Report] Configuration Card and Monitor
Regarding: Configuration Card and Monitor Email: [EMAIL PROTECTED] XFree86 Version: XFree86 OS: Linux Slackware 8.1 Area: X86cfg or X86Config Server: XF86_SVGA Server: Non riesco a visualizzare graficamente Video Card: Matrox G400 series Vers 5 Description: A Xserver non Repeat By: ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Unable to start X in linux platform
Alexander Stohr wrote: Actually this is a SiS315PRO. It will be fully supported in 4.3, and a driver for 4.1 and 4.2 is available at www.winischhofer.net i do feel like cross links to ongoing development projects are somewhat missing from the XFree86.org web page. at least most users that do have troubles finding a driver for their brand new hardware would not be helped with 1-year old xfree86 release notes. Could not agree more. Especially since people seem to have forgotten the benefits of a simple search engine. Thomas -- Thomas Winischhofer Vienna/Austria mailto:[EMAIL PROTECTED]http://www.winischhofer.net/ ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] URGENT: Settings for Nvidia Riva TNT2 M 64
Dear all, I have installed a Debian Linux and with the startx command I receive messages like : Not using default mode (insufficient memory for mode) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] Missing XFree86 DGA Extension
I am running VMware on my Linux box, running Red Hat 8.0. This software (which runs Windows under Linux) has a full-screen mode, which I successfully used under Red Hat 7.3. Now, when I start VMware, I get the message: XFree86 DGA extension not present. Either your X Server is built without this extension, or it is not configured to use it. XFree86 direct graphics (DGA extension) initialization failed. I'm using XFree86 Version 4.20, with an nVidia Quadro2 EX card. Any help in sorting this out would be appreciated. Steve -- Steven P. Auerbach [EMAIL PROTECTED] SAIC
[XFree86] Problems when using dual headed mode (i815 + S3-Virge)
I have a problem when using dual headed mode. I have a i815 motherboard an a S3-Virge PCI card. Both alone work faultless. When I start the PCI card first I have a V_BIOS not found message and nothing works. Therefore I start the AGP (on board chip) first and get two grey X-windows, but sending a x command to the i815 card ends in a restart of the X-server and nothing is displayed. The PCI card works ok. I have a 2.4.20 kernel with agpgart enabled, the /dev/agpgart device is there (if the PCI card is not in the system the i815 is working ok without the xf86AllocateGARTMemory: allocation of 1024 pages failed warning. I think this warning is critical and is actually an error. Why did the allocation of the GART memory only fail if an additional PCI card is put in the motherboard? What can I do to debug this failure? I use a recent version of XFree86, but it didn't work on older versions either. XFree86 Version 4.2.99.3 / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 6 January 2003 Here is the XF86 log file: Solid Horizontal and Vertical Lines Image Writes Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 18 256x256 slots 6 512x512 slots (==) S3VIRGE(0): Backing store disabled (==) S3VIRGE(0): Silken mouse enabled (==) I810(1): Write-combining range (0xe000,0x400) (II) I810(1): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) I810(1): Setting dot clock to 92.0 MHz [ 0x15 0x4 0x20 ] [ 23 6 2 ] (II) I810(1): chose watermark 0x22008000: (tab.freq 94.0) (II) I810(1): xf86BindGARTMemory: bind key 0 at 0x (pgoffset 0) (WW) I810(1): xf86AllocateGARTMemory: allocation of 1024 pages failed (Cannot allocate memory) (II) I810(1): No physical memory available for 4194304 bytes of DCACHE (II) I810(1): xf86BindGARTMemory: bind key 1 at 0x0100 (pgoffset 4096) (II) I810(1): Adding 384 scanlines for pixmap caching (II) I810(1): Allocated Scratch Memory (II) I810(1): Using XFree86 Acceleration Architecture (XAA) Screen to screen bit blits Solid filled rectangles 8x8 mono pattern filled rectangles Indirect CPU to Screen color expansion Solid Horizontal and Vertical Lines Offscreen Pixmaps Setting up tile and stipple cache: 32 128x128 slots 16 256x256 slots (==) I810(1): Backing store disabled (==) I810(1): Silken mouse enabled (==) I810(1): Direct rendering disabled This is the message when a server restart occurs. (II) Screen 0 shares mem io resources (II) Screen 1 shares mem io resources (II) I810(1): xf86UnbindGARTMemory: unbind key 0 (II) I810(1): xf86UnbindGARTMemory: unbind key 1 (II) Screen 0 shares mem io resources (II) Screen 1 shares mem io resources (WW) Open APM failed (/dev/apm_bios) (Operation not supported by device) (II) Screen 0 shares mem io resources (II) Screen 1 shares mem io resources (==) S3VIRGE(0): Write-combining range (0xe400,0x40) (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) S3VIRGE(0): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x invalid frequency 0.025 MHz [freq = 16.875 MHz] (**) S3VIRGE(0): Using FB (==) I810(1): Write-combining range (0xe000,0x400) (II) I810(1): vgaHWGetIOBase: hwp-IOBase is 0x03d0, hwp-PIOOffset is 0x (II) I810(1): Setting dot clock to 92.0 MHz [ 0x15 0x4 0x20 ] [ 23 6 2 ] (II) I810(1): chose watermark 0x22008000: (tab.freq 94.0) (II) I810(1): xf86BindGARTMemory: bind key 0 at 0x (pgoffset 0) (WW) I810(1): xf86AllocateGARTMemory: allocation of 1024 pages failed (Cannot allocate memory) (II) I810(1): No physical memory available for 4194304 bytes of DCACHE (II) I810(1): xf86BindGARTMemory: bind key 1 at 0x0100 (pgoffset 4096) (II) I810(1): Adding 384 scanlines for pixmap caching (II) I810(1): Allocated Scratch Memory (==) I810(1): Direct rendering disabled (II) Entity 0 shares no resources (II) Entity 1 shares no resources Thanks for your help in advance. Peter Kunzmann ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] URGENT: Settings for Nvidia Riva TNT2 M 64
Those aren't actually errors, as long as X starts. Those are just warnings, indicating that some mode that X could concievably (sp?) use, but there's not enough VRAM or some such to use them. Not harmful unless you want to use those modes. --- [EMAIL PROTECTED] wrote: Dear all, I have installed a Debian Linux and with the startx command I receive messages like : Not using default mode (insufficient memory for mode) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] URGENT: Settings for Nvidia Riva TNT2 M 64
Under Debian there is a program for configuring XF86Config-4 called dpkg-reconfigure. It can be used to configure lots of Debian packages. Just type dpkg-reconfigure xserver-xfree86 and you should have not problem getting a working xserver up. On Wed, 15 Jan 2003 [EMAIL PROTECTED] wrote: Dear all, I have installed a Debian Linux and with the startx command I receive messages like : Not using default mode (insufficient memory for mode) ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86 ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] Beforelight screensaver is totally nonfunctional
On Wed, 15 Jan 2003, Mike A. Harris wrote: For the last few XFree86 releases, the beforelight screensaver has been nonfunctional if ran with the XFree86 core server. [mharris@asdf mharris]$ beforelight X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 113 (X_KillClient) Value in failed request: 0x161 Serial number of failed request: 20 Current serial number in output stream: 22 I did the following sequence: 1) run xprop on root window. There is no _MIT_SCREEN_SAVER_ID property. 2) verify clients with http://www.xfree86.org/~mvojkovi/restest.c. 3) run beforelight. 4) Observe new client with restest and verify that there is now a _MIT_SCREEN_SAVER_ID root property belonging to that client ID. 5) Kill beforelight. 6) Note that the root window property still exists, and so does the client, but the client no longer has any resources. Therefore, trying to free the _MIT_SCREEN_SAVER_ID should fail. I don't know what's supposed to have happened here, but I'm wondering why the client didn't go away when it was killed. Mark. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] locale.alias is missing en_GB.UTF-8
Hi, I've noticed that /usr/X11R6/lib/X11/locale/locale.alias is missing en_GB.UTF-8, I think this should be added, as it is present in other locales. Also out of interest, I noticed that en was an alias of en_US, is there a reason for this? I would have expected en to be an alias of en_GB. In other cases where several countrys have adopted to speak the same language the origional country is the default, eg de == de_DE not de_AT or de_CH etc. fr is an alias of fr_FR not fr_BE or fr_CA etc. Regards JG Please cc me in any replies. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
[XFree86] [XFree86(TM) Bug Report] server fails to load with more than 512 mb of system ram runs fine with 512MB or less
Regarding: server fails to load with more than 512 mb of system ram runs fine with 512MB or less Email: [EMAIL PROTECTED] XFree86 Version: XFree86 4.2.0 (Redhat linux release 4.2.9-72 )revision 0 vendor release 6600 OS: redhat linux 8.0 kernel 2.4.18-14 or kernel 2.4.18-19.8.0 Area: Xserver (I think) Server: XFree86 (The XFree86 4.x server) Video Card: chipset: nVidia GeForce 4 MX440 (NV17) series multi display GPU Dual 350MHz DACs 64MB DDR RAM Description: 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-14 ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 12:13:11 EDT 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.1.log, Time: Wed Jan 15 14:07:59 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc102 (**) XKB: model: pc102 (**) Option XkbLayout it (**) XKB: layout: it (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (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 = 0x8000480c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3099 card 1106,3099 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b099 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:09:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0a:0: chip 1274,5880 card 1274,2000 rev 02 class 04,01,00 hdr 00 (II) PCI: 00:11:0: chip 1106,3147 card 1106,3147 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:2: chip 1106,3038 card 0925,1234 rev 23 class 0c,03,00 hdr 00 (II) PCI: 00:11:3: chip 1106,3038 card 0925,1234 rev 23 class 0c,03,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0171 card , rev a3 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: 0x0c (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 0xe400 - 0xe5ff (0x200) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 0xd000 - 0xdfff (0x1000) MX[B] (II) Bus -1: bridge is at (0:17:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(1:0:0) NVidia 0x0171 rev 163, Mem @ 0xe400/24, 0xd000/27, 0xd800/19 (II) Addressable bus
RE: [XFree86] Trouble with Upgrade to Red Hat Linux release: 4.2.0-72
On Wed, 15 Jan 2003, Alexander Stohr wrote: Date: Wed, 15 Jan 2003 16:22:13 +0100 From: Alexander Stohr [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Reply-To: [EMAIL PROTECTED] Content-Type: multipart/alternative; boundary=--=_NextPart_ST_10_19_09_Wednesday_January_15_2003_22030 Subject: RE: [XFree86] Trouble with Upgrade to Red Hat Linux release: 4.2. 0-72 (II) Loading sub module ramdac (II) LoadModule: ramdac (II) Loading /usr/X11R6/lib/modules/libramdac.a (II) Module ramdac: vendor=The XFree86 Project compiled for 4.2.0, module version = 0.1.0 ABI class: XFree86 Video Driver, version 0.5 (--) s3(0): Attached RAMDAC is IBM 526 (--) s3(0): This IBM RAMDAC is NOT supported by this driver, aborting (EE) s3(0): Ramdac probe failed your RAMDAC is not supported. must be a problem of the package maintainer if it worked formerly. maybe you want to contact RedHat first? The problem here is that this specific video card is not supported with the s3 driver, however when switching from 3.3.6+4.x with prior releases, where this card used 3.3.6, the default was changed to the 4.x native driver, and in 4+ months of beta testing, not one person reported the card not working with the s3 driver. The workaround, is to use the vesa driver for unsupported hardware. If anyone has unsupported hardware like this, they should file a bug report in Red Hat bugzilla: http://bugzilla.redhat.com/bugzilla This allows me to more easily troubleshoot the problem and come up with a fix or a workaround which is adequate, and make that the default for the future. Hope this helps. TTYL -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] startx fails
(EE) Unable to locate/open config file (EE) Error from xf86HandleConfigFile() Perhaps, there is no config file for X on your system? Look for /etc/X11/XF86Config If in doubt, you can reconfigure your X with xf86configure. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] [XFree86(TM) Bug Report] server fails to load withmore than 512 mb of system ram runs fine with 512MB or less
(WW) INVALID MEM ALLOCATION b: 0xe400 e: 0xe4ff correcting (EE) Cannot find a replacement memory range This looks like a problem with your motherboard bios. Try flashing a newer bios on it. Windows can probably do a better job of resolving conflicts than XFree86 can. Mark. On Wed, 15 Jan 2003 [EMAIL PROTECTED] wrote: Regarding: server fails to load with more than 512 mb of system ram runs fine with 512MB or less Email: [EMAIL PROTECTED] XFree86 Version: XFree86 4.2.0 (Redhat linux release 4.2.9-72 )revision 0 vendor release 6600 OS: redhat linux 8.0 kernel 2.4.18-14 or kernel 2.4.18-19.8.0 Area: Xserver (I think) Server: XFree86 (The XFree86 4.x server) Video Card: chipset: nVidia GeForce 4 MX440 (NV17) series multi display GPU Dual 350MHz DACs 64MB DDR RAM Description: 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-14 ([EMAIL PROTECTED]) (gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7)) #1 Wed Sep 4 12:13:11 EDT 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.1.log, Time: Wed Jan 15 14:07:59 2003 (==) Using config file: /etc/X11/XF86Config (==) ServerLayout Default Layout (**) |--Screen Screen0 (0) (**) | |--Monitor Monitor0 (**) | |--Device Videocard0 (**) |--Input Device Mouse0 (**) |--Input Device Keyboard0 (**) Option XkbRules xfree86 (**) XKB: rules: xfree86 (**) Option XkbModel pc102 (**) XKB: model: pc102 (**) Option XkbLayout it (**) XKB: layout: it (==) Keyboard: CustomKeycode disabled (**) |--Input Device DevInputMice (**) FontPath set to unix/:7100 (**) RgbPath set to /usr/X11R6/lib/X11/rgb (==) ModulePath set to /usr/X11R6/lib/modules (++) using VT number 7 (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 = 0x8000480c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,3099 card 1106,3099 rev 00 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,b099 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:09:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0a:0: chip 1274,5880 card 1274,2000 rev 02 class 04,01,00 hdr 00 (II) PCI: 00:11:0: chip 1106,3147 card 1106,3147 rev 00 class 06,01,00 hdr 80 (II) PCI: 00:11:1: chip 1106,0571 card 1106,0571 rev 06 class 01,01,8a hdr 00 (II) PCI: 00:11:2: chip 1106,3038 card 0925,1234 rev 23 class 0c,03,00 hdr 00 (II) PCI: 00:11:3: chip 1106,3038 card 0925,1234 rev 23 class 0c,03,00 hdr 00 (II) PCI: 01:00:0: chip 10de,0171 card , rev a3 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: 0x0c (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range:
Re: [XFree86] XFree86 4.2.99.3
On Wed, Jan 15, 2003 at 01:24:37PM +, Glyn scrawled: Steven Gurr wrote: I recently upgraded to the 4.2.99.3 snapshot, and it all seems to be working fine for me. I was just wondering if anyone knew how to get rid of the red cursors that it uses, and get back the traditional black ones. I've been looking at this myself. `man Xcursor` will give you a bit more information, but if you edit the file /usr/X11R6/lib/X11/icons/default/index.theme and remove the line Inherits=redglass or change it to Inherits= then startx again, it should revert to the solid cursor. I've just found a way to do this on a per-user basis, too. Create a ~/.icons/default/index.theme reading [Icon Theme] Inherits= Also, some window managers might be able to load their own cursors. YMMV. Or export XCURSOR_THEME=default. -- Daniel Stone [EMAIL PROTECTED] Developer, Trinity College, University of Melbourne msg00367/pgp0.pgp Description: PGP signature
[XFree86] X doesn't start and keyboard is lost [ATI Rage XL]
Redhat 7.3 Video Card: ATI Technologies Inc Rage XL AGP 2X (from /proc/ioports) XFree86 -version: XFree86 Version 4.2.0 (Red Hat Linux release: 4.2.0-8) / X Window System (protocol Version 11, revision 0, vendor release 6600) Release Date: 23 January 2002 I dont currently have a mouse attached, and so the mouse device is set to /dev/null. I have tried the -allowMouseOpenFail but it didn't help. I start the XFree86 -xf86config ./XFree86.conf.new after running XFree86 -configure and all that happens is the screen goes black, and the keyboard stops responding. Ctl-Alt-Backspace doesn't do anything. The caps light test fails as well. I have to kill the Xfree86 process with a kill -9. The machine continues to respond to the network (ie, the kernel is fine) To get the console back I must reboot. XFree86 -scanpci shows: (1:0:0) ATI card using a ATI Mach64 GM any ideas? = Jacob Hawkes, B. Eng (CSE) [EMAIL PROTECTED] http://www.infinitylimited.net/ __ 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] System crashes when initdefault=5
On 15 Jan 2003, Michel Dänzer wrote: A few people have posted some patches that attempt to make Radeon PCI DRI also work on x86, however I don't believe that XFree86 sources have applied any of these patches, and I don't believe that they've been adequately tested in the wild yet. Mike, this is FUD. First of all, PCI GART has been enabled on powerpc as well for a while, and several people have reported it to work well with PCI cards on x86. I enabled Radeon PCI for x86 in Red Hat Linux 7.3. The result was people who did have Radeon PCI filing bug reports, or email/IRC traffic showing that people were experiencing problems. I did not receive any comments from people who did actually get it working on x86, and so I disabled it. Discussions on dri-devel later showed that other people had attempted this as well and it did not work. Some patches came floating around that some people claimed worked. I never tried them, however my recollection was that the patches did not get into CVS and weren't explored much further by anyone. I contacted ATI to get some PCI Radeon hardware, and have planned on experimenting with it. It hasn't been the highest priority to me however, but I did test the Radeon PCI hardware I have out with the 4.2.0 and 4.2.1 releases to no avail. So it most definitely is not FUD. If it worked for as many people as are claiming it does now, then I'd assume it wouldn't be disabled in CVS by default. It'd also likely work on one of the 4 machines I've tested it on - but doesn't. Anyone interested in testing out these types of patches need not have a Radeon PCI though, you can just disable AGP and an AGP card should work as a PCI one for the purposes of testing and debugging. No, because that seems to be the reason why it's still disabled: it doesn't work well with AGP cards. Don't ask me why. I can confirm that. I received many bug reports on AGP cards due to this as well, since some users recompile their own kernels, not all users remember or are aware enough to also compile agpgart. That, coupled with a glitch in our installer which caused K5/K6/Cyrix systems to get an i386 kernel with no AGP support, created extra problems with PCIGART enabled. Anyway, I don't think this is a good reason to keep it disabled because PCI GART will only be used with Option ForcePCIMode. But owners of PCI cards would at least have a chance to try it without having to modify the source. Instead of giving them the chance... Lets just fix it if we can. ;o) I'd much prefer to fix it. I don't know when I'll have the time to poke at it though, but it is high on my personal todo list, along with other Radeon things. I've been meaning to rip out the ugly code that disables it for a long time but sadly haven't gotten around to it yet. I can send you my patch if you like. I've checked the Xfree86.log file and it ends abruptly when the system hangs around the area when the drm extensions(?) are being initialized. If I disable drm in the XF config file the system doesn't hang, but of course the 3D performance sucks, just ask Tuxracer... Sounds like the problem that occurs on x86 which caused Radeon PCI to be disabled by default. To me it rather sounds like using an X server where PCI GART is enabled with a DRM where it isn't. Yeah, could be that I suppose also. Do you have PCI Radeon hardware to fiddle with? -- Mike A. Harris ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
Re: [XFree86] System crashes when initdefault=5
On Don, 2003-01-16 at 00:11, Mike A. Harris wrote: On 15 Jan 2003, Michel Dänzer wrote: A few people have posted some patches that attempt to make Radeon PCI DRI also work on x86, however I don't believe that XFree86 sources have applied any of these patches, and I don't believe that they've been adequately tested in the wild yet. Mike, this is FUD. First of all, PCI GART has been enabled on powerpc as well for a while, and several people have reported it to work well with PCI cards on x86. I enabled Radeon PCI for x86 in Red Hat Linux 7.3. The result was people who did have Radeon PCI filing bug reports, or email/IRC traffic showing that people were experiencing problems. I did not receive any comments from people who did actually get it working on x86, and so I disabled it. Discussions on dri-devel later showed that other people had attempted this as well and it did not work. Some patches came floating around that some people claimed worked. I never tried them, however my recollection was that the patches did not get into CVS and weren't explored much further by anyone. I contacted ATI to get some PCI Radeon hardware, and have planned on experimenting with it. It hasn't been the highest priority to me however, but I did test the Radeon PCI hardware I have out with the 4.2.0 and 4.2.1 releases to no avail. Of course 4.2 was more broken, e.g. it only enabled bus mastering in the AGP case. So it most definitely is not FUD. If it worked for as many people as are claiming it does now, then I'd assume it wouldn't be disabled in CVS by default. It'd also likely work on one of the 4 machines I've tested it on - but doesn't. Have you or any of those people tried with current CVS? Anyone interested in testing out these types of patches need not have a Radeon PCI though, you can just disable AGP and an AGP card should work as a PCI one for the purposes of testing and debugging. No, because that seems to be the reason why it's still disabled: it doesn't work well with AGP cards. Don't ask me why. I can confirm that. I received many bug reports on AGP cards due to this as well, since some users recompile their own kernels, not all users remember or are aware enough to also compile agpgart. That, coupled with a glitch in our installer which caused K5/K6/Cyrix systems to get an i386 kernel with no AGP support, created extra problems with PCIGART enabled. How so, when it never uses PCI GART automatically? Or did you change that as well? I've been meaning to rip out the ugly code that disables it for a long time but sadly haven't gotten around to it yet. I can send you my patch if you like. Thanks, but I think I know what to do. :) Do you have PCI Radeon hardware to fiddle with? No. -- 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] System crashes when initdefault=5
On Don, 2003-01-16 at 00:35, Michel Dänzer wrote: Anyone interested in testing out these types of patches need not have a Radeon PCI though, you can just disable AGP and an AGP card should work as a PCI one for the purposes of testing and debugging. No, because that seems to be the reason why it's still disabled: it doesn't work well with AGP cards. Don't ask me why. I can confirm that. I received many bug reports on AGP cards due to this as well, since some users recompile their own kernels, not all users remember or are aware enough to also compile agpgart. That, coupled with a glitch in our installer which caused K5/K6/Cyrix systems to get an i386 kernel with no AGP support, created extra problems with PCIGART enabled. How so, when it never uses PCI GART automatically? Or did you change that as well? Actually, it does fall back to PCI GART when PCIGART_ENABLED is defined. My intention is to require Option ForcePCIMode (at least until there's a way to tell the slot type), see http://penguinppc.org/~daenzer/DRI/radeon-pcigart.diff . -- 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] Missing XFree86 DGA Extension
On 15 Jan 2003, Steven P. Auerbach wrote: I am running VMware on my Linux box, running Red Hat 8.0. This software (which runs Windows under Linux) has a full-screen mode, which I successfully used under Red Hat 7.3. Now, when I start VMware, I get the message: XFree86 DGA extension not present. Either your X Server is built without this extension, or it is not configured to use it. ^^ XFree86 direct graphics (DGA extension) initialization failed. I'm using XFree86 Version 4.20, with an nVidia Quadro2 EX card. So, what /is/ your configuration? And what does the logfile look like? (/var/log/XFree86.0.log or something like it -- it will tell us if it was compiled in or not, whether it tried to initialize it or not, etc.) And what version of VMWare are we talking about? Could it be an old one that can only use DGA 1 and RH 7.3 used an X server that supported DGA 1 whereas your current one only supports DGA 2? Just an idea... -Peter ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] XFree crashes ...
Title: RE: [XFree86] XFree crashes ... do you see any chance for disabling DRI/DRM module loading and so letting the card run with less hardware support? -Original Message- From: Ingmar Koecher [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 22:12 To: [EMAIL PROTECTED] Subject: [XFree86] XFree crashes ... I already posted to this list yesterday with the same problem, only this time I do have a log file! Hopefully this will encourage somebody to try and help my situation here, I'd appreciate it!!! ;-) I am running Gentoo Linux 1.4rc2 with XFree 4.2.1 on a Compaq laptop with iP133, a 1Mb Cirrus Logic GD7548. The base Linux box runs just fine. However when I start X with startx, the following happens: 1) I see garbage on the screen 2) I see the normal/standard X background (black/white) 3) I see the X windows X cursor 4) That same cursor changes to a mouse-type arrow-cursor 5) The whole system freezes - I have do a cold reboot I looked at the logfile but I'm not able to get any hints out of it. If somebody has a minute and might see something obvious then I would certainly appreciate it. Many thanks in advance, Ingmar Koecher.
RE: [XFree86] Fwd: Fatal Server Error
Title: RE: [XFree86] Fwd: Fatal Server Error the fatal error relates to the fixed font. either of this: - the font server xfs is not running - access rights have changed to root only by some bogus update package. i hope that helps. -Alex. -Original Message- From: Nikhil Tamhane [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 08:15 To: [EMAIL PROTECTED] Subject: [XFree86] Fwd: Fatal Server Error Note: Forwarded message attached -- Orignal Message -- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Fatal Server Error
Re: [XFree86] XFree86 4.2.99.3
Daniel Stone wrote: On Wed, Jan 15, 2003 at 01:24:37PM +, Glyn scrawled: information, but if you edit the file /usr/X11R6/lib/X11/icons/default/index.theme and remove the line Inherits=redglass Or export XCURSOR_THEME=default. Ah, that does the job even better. (`Admirably' is probably the word I'm looking for.) What manpage have you been reading that I missed? Glyn -- You can keep your flags and emblems, I don't need them anymore So just take your age-old hatred and then walk out of the door ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] Fatal Server Error
Title: RE: [XFree86] Fatal Server Error check xfs running check access rights to font paths -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 07:53 To: [EMAIL PROTECTED] Subject: [XFree86] Fatal Server Error (See attached file: XFree86.0.log) when starting the X server there is a fatal server error message and the X server crashes the error reads a follows: Fatal Server error: could not open default font 'fixed' Do let me know the solution for this problem. Looking forward for your reply Please find the XFree86.0.log file. Regards, Nikhil.T
[XFree86] Problem configuring VESA mode on Suse 8.1 Pro with an ATI IGP-340 card
I have an HP Pavilion Laptop (ZE4100) with a SXGA+ screen (1400x1050) that I am triple booting with Solaris 9, XP and Suse 8.1. I found a mode line for the screen to use with a script that converts to Solaris format, and VESA mode is working fine in Solaris, at 1400x1050, 24-bit. However, Suse 8.1 just refuses to go above 1024x768 in 16-bit, regardless of how I configure the monitor. I've tried both VESA and LCD settings, and have not had any success. The SaX2 interface will let me use a higher resolution setting, but when it comes down to testing, it just goes to 1024x768. The ATI IGP-340 is a new, and not yet supported card, which is why I'm using the VESA mode. I would have thought if I could get Solaris to do it, that it would be a cinch with Linux. Thoughts or ideas? Thanks, Ben _ The new MSN 8 is here: Try it free* for 2 months http://join.msn.com/?page=dept/dialup ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
RE: [XFree86] XFree crashes ...
Title: RE: [XFree86] XFree crashes ... Dear Alex, First thanks for your help! Well honestly I do not know how to disable that module, I looked in XF86Config but couldn't find anything relating to DRI/DRM. I did disable a few things I found in there though (dbe,type1,freetype) but that didn't seem to help. Should I post my XF86Config file? I forgot to mention that X once did start up when I had my laptop in a docking station - the only thing that didn't work 100% was the resolution. However I have taken it out since I don't use the docking station - I only needed it to install Gentoo ... I now saw in the log file that there are dozens of other modules loaded during startup - should and can I try to disable some of them (even though I didn't find them in the XF86Config file)? Thank you! Ingmar. -Original Message-From: Alexander Stohr [mailto:[EMAIL PROTECTED]]Sent: Wednesday, January 15, 2003 7:40 PMTo: [EMAIL PROTECTED]Cc: [EMAIL PROTECTED]Subject: RE: [XFree86] XFree crashes ... do you see any chance for disabling DRI/DRM module loading and so letting the card run with less hardware support? -Original Message- From: Ingmar Koecher [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 15, 2003 22:12 To: [EMAIL PROTECTED] Subject: [XFree86] XFree crashes ...I already posted to this list yesterday with the same problem, only this time I do have a log file! Hopefully this will encourage somebody to try and help my situation here, I'd appreciate it!!! ;-) I am running Gentoo Linux 1.4rc2 with XFree 4.2.1 on a Compaq laptop with iP133, a 1Mb Cirrus Logic GD7548. The base Linux box runs just fine. However when I start X with startx, the following happens: 1) I see garbage on the screen 2) I see the normal/standard X background (black/white) 3) I see the X windows "X" cursor 4) That same cursor changes to a mouse-type arrow-cursor 5) The whole system freezes - I have do a cold reboot I looked at the logfile but I'm not able to get any hints out of it. If somebody has a minute and might see something obvious then I would certainly appreciate it.Many thanks in advance, Ingmar Koecher.
[XFree86] Multihead failure with 3 ATI Radeon 7000 (VE)
I have been beating my head against this problem for 3 days now and felt it was time to head to the experts. I have a system with 1 AGP Radeon 7000 and 2 PCI ATI Radeon 7000's. These cards are (I believe) from Saphire and powered by ATI. They have a VGA output, a DVI output and an S-video output. I can display on each monitor individually. They will not work at the same time however. I have tried a number of variations on this configuration file. I have tried disabling every option I can think of and nothing has helped. The specific error is: (EE) Screen 1 deleted because of no matching config section. As far as I can tell, however, there is a perfectly valid config section for Screen 1. If I alter the ServerLayout section to only reflect one screen, and I specify only one card and test it, that card/monitor will work fine. I have tested all three in this way and each one works. I have tried disabling DRI, disabling DGA, etc. and nothing has helped. I have searched on Google for similar problems but I have failed to find one that matches mine. This is probably because I lack search technique. This is version 4.2.1, 3 September 2002 running on FreeBSD 5.0-RC3 Attached is my XF86Config file and the log file. Any help you can provide would be greatly appreciated. Thanks in advance, -Don Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 Screen 1 Screen1 RightOf Screen0 Screen 2 Screen2 RightOf Screen1 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section Files RgbPath /usr/X11R6/lib/X11/rgb ModulePath /usr/X11R6/lib/modules FontPath /usr/X11R6/lib/X11/fonts/misc/ FontPath /usr/X11R6/lib/X11/fonts/Speedo/ FontPath /usr/X11R6/lib/X11/fonts/Type1/ FontPath /usr/X11R6/lib/X11/fonts/75dpi/ FontPath /usr/X11R6/lib/X11/fonts/100dpi/ EndSection Section ServerFlags Options Xinerama True EndSection Section Module Load dbe Load dri Load extmod Load glx Load pex5 Load record Load xie Load xtrap Load speedo Load type1 EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Section InputDevice Identifier Mouse0 Driver mouse Option Protocol MouseSystems Option Device /dev/sysmouse EndSection Section Monitor Identifier Monitor0 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor1 VendorName Monitor Vendor ModelNameMonitor Model EndSection Section Monitor Identifier Monitor2 VendorName Monitor Vendor ModelNameMonitor Model 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 NoAccel # [bool] #Option SWcursor # [bool] #Option Dac6Bit # [bool] #Option Dac8Bit # [bool] #Option ForcePCIMode # [bool] #Option CPPIOMode # [bool] #Option CPusecTimeout # i #Option AGPMode # i #Option AGPSize # i #Option RingSize # i #Option BufferSize# i #Option EnableDepthMoves # [bool] #Option CrtScreen # [bool] #Option PanelSize # [str] #Option UseFBDev # [bool] Identifier Card0 Driver ati VendorName ATI BoardName Radeon VE QY BusID PCI:0:8:0 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 NoAccel # [bool] #Option SWcursor # [bool] #Option Dac6Bit # [bool] #Option Dac8Bit # [bool] #Option ForcePCIMode # [bool] #Option CPPIOMode # [bool] #Option CPusecTimeout # i #Option AGPMode # i #Option AGPSize # i #Option RingSize # i #Option BufferSize# i #Option EnableDepthMoves # [bool] #Option CrtScreen # [bool] #Option PanelSize
[XFree86] startx problems.
I have been having a ton of problems with my RH 8.0 associated with my i845 chipset on my motherboard. I have put in the 4.2.20 kernel - just fine now. I installed the XFree86 4.2.99.3 binaries and things stopped. I just did a XFree86 -configure and put the resulting configuration file in /etc/X11/XF86Config. I restarted the system. I did a startx. Nothing but blank screen. Edited the config file and replaced the i810 driver with vesa. restarted the system again. I did a startx. This time I got something. I'm not sure what it was, but it wasn't my pretty interface before the binary install. It a desktop for lack of a better term. It had a clock (hard to read, but analog format). It had two terminal windows with dark backgrounds and one terminal window with a light background. exiting the light one exits everything. 1) How do I get my pretty interface back (GNOME)? I tried switchdesk GNOME, but I got the same stuff. 2) Must I always reboot after I stop a startx? If I don't I just get a blank screen. Please help! Any answer to any of these questions will be welcome. -g To Do: Get GNOME back. Get startx to restart without a reboot. Get correct drivers in place. ___ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
