Bug#163622: xfree86-common: Error starting X, using Matrox G200
On Tue, 8 Oct 2002, Branden Robinson wrote: >Date: Tue, 8 Oct 2002 11:52:19 -0500 >From: Branden Robinson <[EMAIL PROTECTED]> >To: [EMAIL PROTECTED] >Reply-To: [EMAIL PROTECTED], [EMAIL PROTECTED] >Content-Type: multipart/signed; micalg=pgp-sha1; >protocol="application/pgp-signature"; >boundary="0iSpYRf9rOurbk0+" >Subject: Bug#163622: xfree86-common: Error starting X, using Matrox G200 > >On Mon, Oct 07, 2002 at 08:55:26PM -0400, Ian Bicking wrote: >> Here's the backtrace, tell me if there's anything more you need: >[...] >> #7 0x0807f3c8 in xf86SigHandler (signo=11) at xf86Events.c:1085 >> signo = 11 >> #8 0x4007e518 in sigaction () from /lib/libc.so.6 >> No symbol table info available. >> #9 0x40197cdc in ?? () >> No symbol table info available. >> #10 0x0852b478 in ?? () >> No symbol table info available. >> #11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5, >> argv=0xbdf4) >> at xf86Init.c:528 >> i = 1075228112 >> j = 0 >> k = 1074540038 >> scr_index = 1074540038 >> No symbol table info available. > >Figures. Died in one of the modules, which are invisible to gdb. > >The only way to nail this down is to use the specially-hacked version of >gdb that understand XFree86 server modules. > >Unfortunately, Debian's gdb does not contain this hack. > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=119028&repeatmerged=yes > >Maybe someone on the debian-x list has a xfree86-gdb binary that you can >use. ftp://people.redhat.com/mharris/gdb-xfree86 It's there in source code and patches. If someone wants to make debs of it also, I'll put them there too. Hope this helps, TTYL -- Mike A. Harris -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > tag 163892 patch Bug#163892: C++ support in libGLU (patch, upstream problem) Tags added: patch > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#163892: C++ support in libGLU (patch, upstream problem)
Package: xfree86 Version: 4.2.1-1 Severity: normal This patch defines a SharedDepCplusplusLibraryTarget for FreeBSD and NetBSD. While the ELF section in bsdLib.rules is noted as having been copied from the Linux version, this clearly predated the addition of C++ code and support, and the target appears to have never been added to the BSD ruleset, making it impossible to compile cleanly using GCC 3.x (libGLU is linked without a dependancy on libstdc++, and any attempt to compile a normal C program which calls libGLU will fail). Patch authored by Joel Baker <[EMAIL PROTECTED]>, based on the rules already present in lnxLib.rules. -- *** Joel Baker System Administrator - lightbearer.com [EMAIL PROTECTED] http://users.lightbearer.com/lucifer/ This patch defines a SharedDepCplusplusLibraryTarget for FreeBSD and NetBSD. While the ELF section in bsdLib.rules is noted as having been copied from the Linux version, this clearly predated the addition of C++ code and support, and the target appears to have never been added to the BSD ruleset, making it impossible to compile cleanly using GCC 3.x (libGLU is linked without a dependancy on libstdc++, and any attempt to compile a normal C program which calls libGLU will fail). Patch authored by Joel Baker <[EMAIL PROTECTED]>, based on the rules already present in lnxLib.rules. diff -ur xc-dist/config/cf/bsdLib.rules xc/config/cf/bsdLib.rules --- xc-dist/config/cf/bsdLib.rules 2002-01-17 23:29:05.0 + +++ xc/config/cf/bsdLib.rules 2002-10-09 01:26:13.0 + @@ -306,6 +306,34 @@ #endif /* SharedDepLibraryTarget */ +/* + * SharedDepCplusplusLibraryTarget - generate rules to create a shared library. + */ +#ifndef SharedDepCplusplusLibraryTarget +#define SharedDepCplusplusLibraryTarget(libname,rev,deplist,solist,down,up) @@\ +AllTarget(Concat(lib,libname.so.rev)) @@\ + @@\ +Concat(lib,libname.so.rev): deplist @@\ + $(RM) [EMAIL PROTECTED] @@\ + @SONAME=`echo $@ | sed 's/\.[^\.]*$$//'`; set -x; \ @@\ + (cd down; $(CXX) -o up/[EMAIL PROTECTED] $(SHLIBLDFLAGS) -Wl,-soname,$$SONAME solist $(REQUIREDLIBS) BaseShLibReqs); \ @@\ + $(RM) $$SONAME; $(LN) $@ $$SONAME; \@@\ + LinkBuildSonameLibrary($$SONAME)@@\ + $(RM) $@@@\ + $(MV) [EMAIL PROTECTED] $@ @@\ + $(RM) Concat(lib,libname.so)@@\ + $(LN) $@ Concat(lib,libname.so) @@\ + LinkBuildLibrary($@)@@\ + LinkBuildLibrary(Concat(lib,libname.so))@@\ + @@\ +clean:: @@\ + @SONAME=`echo Concat(lib,libname.so.rev) | sed 's/\.[^\.]*$$//'`; \ @@\ + set -x; $(RM) $$SONAME @@\ + $(RM) Concat(lib,libname.so)@@\ + $(RM) Concat(lib,libname.so.rev) + +#endif /* SharedDepCplusplusLibraryTarget */ + #ifndef SharedDepModuleTarget #define SharedDepModuleTarget(name,deps,solist) @@\ AllTarget(name) @@\
Re: xserver-xfree86 replacing /etc/X11/XF86Config-4
On Tue, 2002-10-08 at 22:14, Branden Robinson wrote: > On Tue, Oct 08, 2002 at 08:52:43PM -0400, David N Kordonowy wrote: > > When upgrading X, xserver-xfree86 replaces my/etc/X11/XF86Config-4 file > > even though it has been modified by me. My /etc/X11/XF86Config-4 is a > > link to another file (in this case it is /etc/X11/XF86Config-4.sun). > > The package xserver-xfree86 replaces this link with its file, thus > > breaking X. > > > > Is this normal behavior for packages or is this simply a result of my > > nontypical setup? > > Have you read the very top of the generated XF86Config-4 file? Yup. > > ### BEGIN DEBCONF SECTION > # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the > # Debian X Configuration tool, using values from the debconf database. > # > # Edit this file with caution, and see the XF86Config-4 manual page. > # (Type "man XF86Config-4" at the shell prompt.) > # > # If you want your changes to this file preserved by dexconf, only make > changes > # before the "### BEGIN DEBCONF SECTION" line above, and/or after the > # "### END DEBCONF SECTION" line below. > # > # To change things within the debconf section, run the command: > # dpkg-reconfigure xserver-xfree86 > # as root. Also see "How do I add custom sections to a dexconf-generated > # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. > > In what way does the above not make the situation clear? Well, I suppose I thought that xserver-xfree86 would change the debconf section that /etc/X11/XF86Config-4 pointed to (in this case /etc/X11/XF86Config-4.sun), and not erase the link and replace it with a new file. Is this policy part of debconf? > > This behavior is controlled by a debconf question: > > Template: xserver-xfree86/manage_config_with_debconf > Type: boolean > Default: true > Description: Manage XFree86 4.x server configuration file with debconf? > The /etc/X11/XF86Config-4 file, which contains the configuration information > for the XFree86 version 4 X server, can be handled automatically by debconf, > or manually by you. > . > Note that only specific, marked sections of the configuration file will be > handled by debconf if you select this option; if those markers are absent, > the configuration file will not be updated automatically, and you will have > to update the file manually, or move or delete the file. > > To shut this off, "dpkg-reconfigure xserver-xfree86". > > -- > G. Branden Robinson|If a man ate a pound of pasta and a > Debian GNU/Linux |pound of antipasto, would they > [EMAIL PROTECTED] |cancel out, leaving him still > http://people.debian.org/~branden/ |hungry? -- Scott Adams Thanks, David Kordonowy
Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
severity 163885 normal thanks This is the worst bug report I've seen in a long time, but then I've grown accustomed to such from the person who hides behind the nom de annoyance "Lazarus Long". On Wed, Oct 09, 2002 at 12:54:01AM +, Lazarus Long wrote: > Package: xserver-xfree86 > Version: N/A Horse puckey. I don't support Red Hat packages. Tell me which version of the official Debian packages you're running or see your report closed. > Severity: important > > (Probably higher severity, due to hardware threat, but ... ?) "hardware threat"? What the heck is that? > (Invoked as user, with a plain "startx" command line) > > (protocol Version 11, revision 0, vendor release 6600) I notice you excised the line that reveals the build information. Furthermore, your server log is missing a *lot* of information. Did you trim this down? Where is the unadulterated /var/log/XFree86.*.log file? Have you read XF86Config(7)? Why have you not supplied the information that is requested, and required for the resolution of most bug reports? If it is too much trouble for you to gather the requisite information, I recommend the "reportbug" package and command; it will gather it for you. > (EE) R128(0): [dri] R128DRIScreenInit failed because of a version mismatch. > [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is > needed. > [dri] Disabling the DRI. Okay, so souped-up 3D acceleration won't work because your kernel is too old. This is in no way an "important" bug. We have people who can't even start the X server because it coredumps. That's "important". > (EE) R128(0): [drm] failed to remove DRM signal handler > DRIUnlock called when not locked I'll note to no one in particular that the X server should probably set a global variable tracking whether drm was initialized, and not bother to remove a signal handler that never got established. But this is a pretty minor complaint. > (EE) xf86OpenSerial: Cannot open device /dev/input/mice > No such file or directory. > (EE) Generic Mouse: cannot open input device > (EE) PreInit failed for input device "Generic Mouse" These are harmless and simply the result of my efforts to support USB mice without any intervention on the part of the user. Blisfully, it's evidence that you are actually running Debian, and not trying to trick me into supporting Red Hat or SuSE. > _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root > SESSION_MANAGER=local/farm:/tmp/.ICE-unix/5500 > SetKbdSettings - type: 2 rate: 30 delay: 500 snumlk: 0 > SetKbdSettings - Succeeded > Warning: This version of gmix was compiled with > OSS version 3.8.2, and your system is running > version 3.8.16. > X connection to :0.0 broken (explicit kill or server shutdown). > Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). > xinit: connection to X server lost. > X connection to :0.0 broken (explicit kill or server shutdown). > xscreensaver-gl-helper: couldn't open display :0.0 > X connection to :0.0 broken (explicit kill or server shutdown). These all have to do with your X clients and aren't germane to your bug report. > (I Alt-Ctrl-Backspace'd here, due to the screen mess and fear of hardware > damage.) Fear of hardware damage? What are you smoking? XFree86 and the kernel couldn't agree on a protocol for melting the heat sink on your 3D-accelerated graphics card to slag while animating multitextured NURBS porn. You should be grateful; not using DRI probably keeps your computer chassis ten degrees cooler. > The kernel is 2.4.19, so I'm not sure how to get any more recent version > of this kernel module. Did you compile this against a 2.5.X box perhaps? No. > Hmmm, no, I see "Build Operating System: Linux 2.4.18 i686 [ELF]" > so that's not it. Where did you manage to get something more recent > than what's in the current stable kernel, while running a current-1 > kernel version? Odd, at best. XFree86 periodically does CVS merges from the DRI project at SourceForge. Those guys also develop the DRM modules that live inside the kernel, so the Linux kernel hackers periodically sync up with them as well. The release cycles of XFree86 and the Linux kernel are not in sync. There is not a lot that Debian can do about this. It was my understanding that DRI on the XFree86 side was supposed to maintain backward compatibility, but apparently that didn't happen. Not sure what's going on here. Michel D?nzer reads the debian-x list; perhaps he knows. > I had hoped 4.2.1-2 would fix this, so held off on filing until trying > that, but it still has the same problem. This problem was not present > in 4.1.0-whatever (sarge) versions and only showed up in 4.2.1-1, to > my awareness. > > What further info would you like? What would you like me to test? I'd like to see the information described in XF86Config(7). Other than that this problem probably isn't easily resolvable. I don't recommend that you run a 2.5.x kernel. For
Bug#163885: additional info -- [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
On Wed, Oct 09, 2002 at 01:18:03AM +, Lazarus Long wrote: > Additional info: > The same errors occur when rebooting to an old kernel, 2.4.18, from way > back in March. (I thought perhaps for some strange reason the module > version had been reverted in the current kernel. That's not the case, > apparently, saving you looking into that.) No, if the modules in kernel 2.4.19 didn't support DRI version 2.2, the modules in 2.4.18 almost certainly wouldn't. > XFree86 Version 4.2.1 (Debian 4.2.1-2 20021008045526 [EMAIL PROTECTED]) / X > Window System Well, this is an improvement. It would still be nice to see the information described in XF86Config(7), though. -- G. Branden Robinson| What influenced me to atheism was Debian GNU/Linux | reading the Bible cover to cover. [EMAIL PROTECTED] | Twice. http://people.debian.org/~branden/ | -- J. Michael Straczynski pgpvcbX1LEIvo.pgp Description: PGP signature
Processed: Re: Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
Processing commands for [EMAIL PROTECTED]: > severity 163885 normal Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed. Severity set to `normal'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#163837: startx: hostname version is displayed
On Tue, Oct 08, 2002 at 09:58:14PM +0200, Beat Bolli wrote: > Well, the question is if Debian has the GNU hostname command. Since the grep > doesn't match, I deduced that I don't have GNU hostname, based on the > assumption that the person who coded this knew that GNU hostname would > output its version string on stdout... I prefer John's patch. Consolidate stdout and stderr and grep them together. * if it's a GNU program, "GNU" is bound to show up somewhere * no chance of grep blocking to wait for input unless hostname itself hangs * GNU can change its mind about where to send the version string and the code still works -- G. Branden Robinson| "Why do we have to hide from the Debian GNU/Linux | police, Daddy?" [EMAIL PROTECTED] | "Because we use vi, son. They use http://people.debian.org/~branden/ | emacs." pgphskGaRFx83.pgp Description: PGP signature
Re: xserver-xfree86 replacing /etc/X11/XF86Config-4
On Tue, Oct 08, 2002 at 08:52:43PM -0400, David N Kordonowy wrote: > When upgrading X, xserver-xfree86 replaces my/etc/X11/XF86Config-4 file > even though it has been modified by me. My /etc/X11/XF86Config-4 is a > link to another file (in this case it is /etc/X11/XF86Config-4.sun). > The package xserver-xfree86 replaces this link with its file, thus > breaking X. > > Is this normal behavior for packages or is this simply a result of my > nontypical setup? Have you read the very top of the generated XF86Config-4 file? ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. In what way does the above not make the situation clear? This behavior is controlled by a debconf question: Template: xserver-xfree86/manage_config_with_debconf Type: boolean Default: true Description: Manage XFree86 4.x server configuration file with debconf? The /etc/X11/XF86Config-4 file, which contains the configuration information for the XFree86 version 4 X server, can be handled automatically by debconf, or manually by you. . Note that only specific, marked sections of the configuration file will be handled by debconf if you select this option; if those markers are absent, the configuration file will not be updated automatically, and you will have to update the file manually, or move or delete the file. To shut this off, "dpkg-reconfigure xserver-xfree86". -- G. Branden Robinson|If a man ate a pound of pasta and a Debian GNU/Linux |pound of antipasto, would they [EMAIL PROTECTED] |cancel out, leaving him still http://people.debian.org/~branden/ |hungry? -- Scott Adams pgpg8aw1aJKRX.pgp Description: PGP signature
Bug#163815: reportbug not attaching your XFree86 log files?
On Wed, Oct 09, 2002 at 12:49:42AM +0100, Paul Martin wrote: > Reportbug *did* include an XFree86.0.log. However, it was from the > working 4.1.0-16 I was running at the time, so I removed it... > > Flame away. Aha. Sorry for the false positive, Chris. Not sure about the other yet, though. > If you really do want the XFree86.0.log from 4.2.1, I'll provide it. > There didn't seem to be anything clueful in there (nothing that I > don't see in the log from 4.1.0). Yes, please do always include it. I've never yet had to flame anyone for including the server output. :) Sometimes it is superfluous, but it isn't for *most* of the bug reports I against the package. -- G. Branden Robinson| Debian GNU/Linux | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://people.debian.org/~branden/ | pgpWWFQjxNNpE.pgp Description: PGP signature
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 08:07:39PM -0500, Branden Robinson wrote: > On Tue, Oct 08, 2002 at 04:45:18PM -0600, Joel Baker wrote: > > > > @@ -356,0 +355 @@ > > > > +usr/X11R6/bin/kbd_mode > > > > > > I used to see this on Sun machines. You sure it's necessary with modern > > > BSD kernels? > > > > I'm not sure it is. I mostly don't know where/how to check whether it is, > > or what it's supposed to do. > > It changes the tty keyboard reading mode, e.g., from "raw" to "cooked" > and vice versa. > > I think Linux doesn't have this because a keyboard state is specific to > each virtual terminal, so the kernel knows to put the keyboard state > back after the X server crashes and gives up its VT. > > On Sun boxen, you often had to telnet[1] into the box after X crashed and > run "kbd_mode -a". Ah. Yes, I remember doing that now. And I suspect it's obsolete on modern NetBSD, then, because it also has virtual terminals (albeit of a different sort, but the same concept) with which X interacts directly. Two different versions thereof, even. I'll see if I can convince it to stop building. > > > > @@ -5543,2 +5539,0 @@ > > > > -usr/X11R6/lib/libI810XvMC.a > > > > -usr/X11R6/lib/libI810XvMC_pic.a > > > > > > This is new to XFree86 4.2. My guess is that it does something to hook > > > into the (Linux) kernel to speak foul magic to the hardware. XvMC is > > > Mark Vojkovich's motion compensation interface on top of the XVideo (Xv) > > > extension. I'll cautiously assume that *BSD shouldn't be building this. > > > > We can always put it back in if someone can show that it should build/work > > on NetBSD platforms. However, at the moment, this is not listed as being > > supportd on the NetBSD arch page in XFree86 docs. Will yank it. > > I forgot to mention that you *should* have libXvMC. Just probably not > this I810 thing. Left those in; only the I810 files were removed from the MANIFEST. > > > Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer > > > understands better how this stuff works. (I.e., I don't know *why* it's > > > called the "offscreen" Mesa library, or why 3D-accelerated GL rendering > > > is considered "off-the-screen". Maybe it means the rendering isn't done > > > into the framebuffer, a.k.a. "screen"?) > > > > Er. Is that 'not building DRI implies not building libOSMesa' - IE, it > > should be removed for non-Linux platforms? > > Correct, as I understand it. Okay. Makes sense to me. > > > > @@ -5602,0 +5595 @@ > > > > +usr/X11R6/lib/liboldX.so.6.0 > > > > > > This goes in xlibs-dev.files. Already listed there. > > > > Huh. xlibs-dev.files (and all of the MANIFESTs) have a static library > > (/usr/X11R6/lib/liboldX.a) rather than a dynamic one. Maybe I need to tweak > > a suitable part of the system and tell it to build a static liboldX? > > Sorry, I failed to pay attention. Please don't ship a shared liboldX > unless for some insane reason you need it for binary compatiblity with > other BSDs. It would be preferable to turn of building of the shared > version. I'll see if I can figure out why it's doing so and whack it into a static instead. > > > > @@ -5608 +5600,0 @@ > > > > -usr/X11R6/lib/libxrx.so.6.3 > > > > > > Another extension no one uses. This is the Netscape Navigator plug in > > > that lets you render the X server inside a browser window or some lunacy > > > like that. I'm not sure there's a good reason it shouldn't build on > > > *BSD versus Linux, but on the other hand there's probably not a good > > > reason for *anyone* to build it. > > > > Hmmm. I'll look into it, but after I do other things, then; tentatively > > left in place, until I can figure out what is up with it on NetBSD. > > Maybe the Netscape plugin code is Linux-specific? I have no idea. I'm > sure no one cares about this thing. I'm sure, too, but *iff* it compiles, well, it would be nice to make it available. But low priority. :) > > Now, the explanation for glxinfo (and it probably has much deeper > > reprecussions): NetBSD includes bsdLib.rules, which does not have a number > > of things from lnxLib.rules (the thing which made me realize this matters > > is that it lacks SharedDepCplusplusLib, causing libGLU to be linked with > > 'gcc' instead of 'g++', causing glxinfo to fail when it tried to link > > against the .so because the .so couldn't find various C++ system library > > things). > > > > Nor can I just drop in lnxLib.rules (unsuprisingly), because it wreaks a > > lot of havoc in other places. So I'm going to have to general a patch set > > for bsdLib, providing the bits from lnxLib that are required to make things > > compile in a Debian-happy way. > > I don't have very much useful to offer here. I have some facility with > Imake after fighting with it for so many years, but I phear the > *Lib.rules files. I think I found it. The bsdLib.rules ELF rules are 'copied mostly from the linux rules' - but lacked a SharedDepCplusplusLibraryTarge
Bug#163885: additional info -- [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
Additional info: The same errors occur when rebooting to an old kernel, 2.4.18, from way back in March. (I thought perhaps for some strange reason the module version had been reverted in the current kernel. That's not the case, apparently, saving you looking into that.) Linux phoenix 2.4.18 #1 Thu Mar 14 01:51:04 UTC 2002 i686 unknown unknown GNU/Linux Paste follow, but nothing appears changed (other than being shorter, since I Alt-Ctrl-Backspace'd earlier.) XFree86 Version 4.2.1 (Debian 4.2.1-2 20021008045526 [EMAIL PROTECTED]) / 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 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: Wed Oct 9 01:00:32 2002 (==) Using config file: "/etc/X11/XF86Config-4" (EE) R128(0): [dri] R128DRIScreenInit failed because of a version mismatch. [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed. [dri] Disabling the DRI. (EE) R128(0): [drm] failed to remove DRM signal handler DRIUnlock called when not locked (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such file or directory. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device "Generic Mouse" xinit: connection to X server lost. -- Please (OpenPGP) encrypt all mail whenever possible. Request the following Public Keys for Lazarus Long <[EMAIL PROTECTED]> TypeBits/KeyIDFingerprint DSA KeyID: ElGamal: 2048g/CCB09D64 8270 4B79 CB1E 433B 6214 64EB 9D58 28A9 E8B1 27F4 pgpok5zS67o62.pgp Description: PGP signature
Processed: your mail
Processing commands for [EMAIL PROTECTED]: > tag 163892 patch Bug#163892: C++ support in libGLU (patch, upstream problem) Tags added: patch > -- Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 04:45:18PM -0600, Joel Baker wrote: > > > @@ -356,0 +355 @@ > > > +usr/X11R6/bin/kbd_mode > > > > I used to see this on Sun machines. You sure it's necessary with modern > > BSD kernels? > > I'm not sure it is. I mostly don't know where/how to check whether it is, > or what it's supposed to do. It changes the tty keyboard reading mode, e.g., from "raw" to "cooked" and vice versa. I think Linux doesn't have this because a keyboard state is specific to each virtual terminal, so the kernel knows to put the keyboard state back after the X server crashes and gives up its VT. On Sun boxen, you often had to telnet[1] into the box after X crashed and run "kbd_mode -a". > > > @@ -5543,2 +5539,0 @@ > > > -usr/X11R6/lib/libI810XvMC.a > > > -usr/X11R6/lib/libI810XvMC_pic.a > > > > This is new to XFree86 4.2. My guess is that it does something to hook > > into the (Linux) kernel to speak foul magic to the hardware. XvMC is > > Mark Vojkovich's motion compensation interface on top of the XVideo (Xv) > > extension. I'll cautiously assume that *BSD shouldn't be building this. > > We can always put it back in if someone can show that it should build/work > on NetBSD platforms. However, at the moment, this is not listed as being > supportd on the NetBSD arch page in XFree86 docs. Will yank it. I forgot to mention that you *should* have libXvMC. Just probably not this I810 thing. > > Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer > > understands better how this stuff works. (I.e., I don't know *why* it's > > called the "offscreen" Mesa library, or why 3D-accelerated GL rendering > > is considered "off-the-screen". Maybe it means the rendering isn't done > > into the framebuffer, a.k.a. "screen"?) > > Er. Is that 'not building DRI implies not building libOSMesa' - IE, it > should be removed for non-Linux platforms? Correct, as I understand it. > > > @@ -5602,0 +5595 @@ > > > +usr/X11R6/lib/liboldX.so.6.0 > > > > This goes in xlibs-dev.files. Already listed there. > > Huh. xlibs-dev.files (and all of the MANIFESTs) have a static library > (/usr/X11R6/lib/liboldX.a) rather than a dynamic one. Maybe I need to tweak > a suitable part of the system and tell it to build a static liboldX? Sorry, I failed to pay attention. Please don't ship a shared liboldX unless for some insane reason you need it for binary compatiblity with other BSDs. It would be preferable to turn of building of the shared version. > > > @@ -5608 +5600,0 @@ > > > -usr/X11R6/lib/libxrx.so.6.3 > > > > Another extension no one uses. This is the Netscape Navigator plug in > > that lets you render the X server inside a browser window or some lunacy > > like that. I'm not sure there's a good reason it shouldn't build on > > *BSD versus Linux, but on the other hand there's probably not a good > > reason for *anyone* to build it. > > Hmmm. I'll look into it, but after I do other things, then; tentatively > left in place, until I can figure out what is up with it on NetBSD. Maybe the Netscape plugin code is Linux-specific? I have no idea. I'm sure no one cares about this thing. > Policy says FHS; Debian/NetBSD, at least, is basically NetBSD kernel, libc, > and other required system libraries, but Debian-package-pure userspace, > filesystem arrangement, et al. The only exception so far is that, on the > 1.6 port, ld.so and family live in /usr/libexec, but NetBSD native moved > this to /lib (as well as making /lib dynamic) in -current immediately after > the 1.6 release, so even that will probably go away before it requires a > Policy adjustment. > > As such, I'll change the patch and tweak said symbol to put it where the > FHS says. Okay. /var/lib instead of /var/db for Debian/NetBSD it is, then. > Now, the explanation for glxinfo (and it probably has much deeper > reprecussions): NetBSD includes bsdLib.rules, which does not have a number > of things from lnxLib.rules (the thing which made me realize this matters > is that it lacks SharedDepCplusplusLib, causing libGLU to be linked with > 'gcc' instead of 'g++', causing glxinfo to fail when it tried to link > against the .so because the .so couldn't find various C++ system library > things). > > Nor can I just drop in lnxLib.rules (unsuprisingly), because it wreaks a > lot of havoc in other places. So I'm going to have to general a patch set > for bsdLib, providing the bits from lnxLib that are required to make things > compile in a Debian-happy way. I don't have very much useful to offer here. I have some facility with Imake after fighting with it for so many years, but I phear the *Lib.rules files. > Anyway, I'll be back once I beat on it some more. Any suggestions on what > to check to find out if kdb_mode is relevant would be appreciated. If the keyboard is generally hosed after the X server exits (test it under a crash too -- kill -SEGV the X server) then you probably don't need it. If existing userspace to
Bug#163622: xfree86-common: Error starting X, using Matrox G200
On Wed, Oct 09, 2002 at 12:31:01AM +0200, Michel Dänzer wrote: > Well, you can call LoaderPrintSymbol for each address with a ??, e.g. > > call LoaderPrintSymbol(0x40197cdc) > > Beware that the output goes to the server log only. Gee, thanks, I just tried that and cored my X server. Okay, so what are people *actually* supposed to do? > > Unfortunately, Debian's gdb does not contain this hack. > > Hopefully, the patch will be cleaned up and applied soon; it would > certainly make debugging X much easier. > > PS: I hope the submitter doesn't get this twice? The submitter only gets mail to -submitter and -done. > PPS: Quite some additional traffic on the list... http://lists.debian.org/debian-x/2002/debian-x-200210/msg00054.html -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy [EMAIL PROTECTED] |spot on the pavement, where used to http://people.debian.org/~branden/ |lie the carcass of a dead horse. pgpWum2kfMp9W.pgp Description: PGP signature
Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
Package: xserver-xfree86 Version: N/A Severity: important (Probably higher severity, due to hardware threat, but ... ?) (Invoked as user, with a plain "startx" command line) (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 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: Wed Oct 9 00:39:15 2002 (==) Using config file: "/etc/X11/XF86Config-4" (EE) R128(0): [dri] R128DRIScreenInit failed because of a version mismatch. [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed. [dri] Disabling the DRI. (EE) R128(0): [drm] failed to remove DRM signal handler DRIUnlock called when not locked (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such file or directory. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device "Generic Mouse" _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root SESSION_MANAGER=local/farm:/tmp/.ICE-unix/5500 SetKbdSettings - type: 2 rate: 30 delay: 500 snumlk: 0 SetKbdSettings - Succeeded Warning: This version of gmix was compiled with OSS version 3.8.2, and your system is running version 3.8.16. X connection to :0.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). xinit: connection to X server lost. X connection to :0.0 broken (explicit kill or server shutdown). xscreensaver-gl-helper: couldn't open display :0.0 X connection to :0.0 broken (explicit kill or server shutdown). (I Alt-Ctrl-Backspace'd here, due to the screen mess and fear of hardware damage.) The kernel is 2.4.19, so I'm not sure how to get any more recent version of this kernel module. Did you compile this against a 2.5.X box perhaps? Hmmm, no, I see "Build Operating System: Linux 2.4.18 i686 [ELF]" so that's not it. Where did you manage to get something more recent than what's in the current stable kernel, while running a current-1 kernel version? Odd, at best. I had hoped 4.2.1-2 would fix this, so held off on filing until trying that, but it still has the same problem. This problem was not present in 4.1.0-whatever (sarge) versions and only showed up in 4.2.1-1, to my awareness. What further info would you like? What would you like me to test? -- System Information Debian Release: post-3.0(+) Kernel Version: Linux phoenix 2.4.19 #1 Tue Sep 17 20:34:42 UTC 2002 i586 unknown unknown GNU/Linux
Bug#163892: C++ support in libGLU (patch, upstream problem)
Package: xfree86 Version: 4.2.1-1 Severity: normal This patch defines a SharedDepCplusplusLibraryTarget for FreeBSD and NetBSD. While the ELF section in bsdLib.rules is noted as having been copied from the Linux version, this clearly predated the addition of C++ code and support, and the target appears to have never been added to the BSD ruleset, making it impossible to compile cleanly using GCC 3.x (libGLU is linked without a dependancy on libstdc++, and any attempt to compile a normal C program which calls libGLU will fail). Patch authored by Joel Baker <[EMAIL PROTECTED]>, based on the rules already present in lnxLib.rules. -- *** Joel Baker System Administrator - lightbearer.com [EMAIL PROTECTED] http://users.lightbearer.com/lucifer/ This patch defines a SharedDepCplusplusLibraryTarget for FreeBSD and NetBSD. While the ELF section in bsdLib.rules is noted as having been copied from the Linux version, this clearly predated the addition of C++ code and support, and the target appears to have never been added to the BSD ruleset, making it impossible to compile cleanly using GCC 3.x (libGLU is linked without a dependancy on libstdc++, and any attempt to compile a normal C program which calls libGLU will fail). Patch authored by Joel Baker <[EMAIL PROTECTED]>, based on the rules already present in lnxLib.rules. diff -ur xc-dist/config/cf/bsdLib.rules xc/config/cf/bsdLib.rules --- xc-dist/config/cf/bsdLib.rules 2002-01-17 23:29:05.0 + +++ xc/config/cf/bsdLib.rules 2002-10-09 01:26:13.0 + @@ -306,6 +306,34 @@ #endif /* SharedDepLibraryTarget */ +/* + * SharedDepCplusplusLibraryTarget - generate rules to create a shared library. + */ +#ifndef SharedDepCplusplusLibraryTarget +#define SharedDepCplusplusLibraryTarget(libname,rev,deplist,solist,down,up)@@\ +AllTarget(Concat(lib,libname.so.rev)) @@\ + @@\ +Concat(lib,libname.so.rev): deplist @@\ + $(RM) $@~ @@\ + @SONAME=`echo $@ | sed 's/\.[^\.]*$$//'`; set -x; \ @@\ + (cd down; $(CXX) -o up/$@~ $(SHLIBLDFLAGS) -Wl,-soname,$$SONAME solist +$(REQUIREDLIBS) BaseShLibReqs); \ @@\ + $(RM) $$SONAME; $(LN) $@ $$SONAME; \@@\ + LinkBuildSonameLibrary($$SONAME)@@\ + $(RM) $@@@\ + $(MV) $@~ $@@@\ + $(RM) Concat(lib,libname.so)@@\ + $(LN) $@ Concat(lib,libname.so) @@\ + LinkBuildLibrary($@)@@\ + LinkBuildLibrary(Concat(lib,libname.so))@@\ + @@\ +clean::@@\ + @SONAME=`echo Concat(lib,libname.so.rev) | sed 's/\.[^\.]*$$//'`; \ @@\ + set -x; $(RM) $$SONAME @@\ + $(RM) Concat(lib,libname.so)@@\ + $(RM) Concat(lib,libname.so.rev) + +#endif /* SharedDepCplusplusLibraryTarget */ + #ifndef SharedDepModuleTarget #define SharedDepModuleTarget(name,deps,solist)@@\ AllTarget(name)@@\
xserver-xfree86 replacing /etc/X11/XF86Config-4
Hi, When upgrading X, xserver-xfree86 replaces my/etc/X11/XF86Config-4 file even though it has been modified by me. My /etc/X11/XF86Config-4 is a link to another file (in this case it is /etc/X11/XF86Config-4.sun). The package xserver-xfree86 replaces this link with its file, thus breaking X. Is this normal behavior for packages or is this simply a result of my nontypical setup? Please cc: me to any responses as I'm not subscribed to this mailing list. If this is the incorrect mailing list to question, then accept my apologies. Thanks, David Kordonowy [pre-upgrade] $ ls -l /etc/X11/XF86Config-4 lrwxrwxrwx1 root root 16 Oct 8 20:09 /etc/X11/XF86Config-4 -> XF86Config-4.sun [post-upgrade] $ ls -l /etc/X11/XF86Config-4 -rw-r--r--1 root root 2748 Oct 8 20:12 /etc/X11/XF86Config-4
Re: xserver-xfree86 replacing /etc/X11/XF86Config-4
On Tue, 2002-10-08 at 22:14, Branden Robinson wrote: > On Tue, Oct 08, 2002 at 08:52:43PM -0400, David N Kordonowy wrote: > > When upgrading X, xserver-xfree86 replaces my/etc/X11/XF86Config-4 file > > even though it has been modified by me. My /etc/X11/XF86Config-4 is a > > link to another file (in this case it is /etc/X11/XF86Config-4.sun). > > The package xserver-xfree86 replaces this link with its file, thus > > breaking X. > > > > Is this normal behavior for packages or is this simply a result of my > > nontypical setup? > > Have you read the very top of the generated XF86Config-4 file? Yup. > > ### BEGIN DEBCONF SECTION > # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the > # Debian X Configuration tool, using values from the debconf database. > # > # Edit this file with caution, and see the XF86Config-4 manual page. > # (Type "man XF86Config-4" at the shell prompt.) > # > # If you want your changes to this file preserved by dexconf, only make changes > # before the "### BEGIN DEBCONF SECTION" line above, and/or after the > # "### END DEBCONF SECTION" line below. > # > # To change things within the debconf section, run the command: > # dpkg-reconfigure xserver-xfree86 > # as root. Also see "How do I add custom sections to a dexconf-generated > # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. > > In what way does the above not make the situation clear? Well, I suppose I thought that xserver-xfree86 would change the debconf section that /etc/X11/XF86Config-4 pointed to (in this case /etc/X11/XF86Config-4.sun), and not erase the link and replace it with a new file. Is this policy part of debconf? > > This behavior is controlled by a debconf question: > > Template: xserver-xfree86/manage_config_with_debconf > Type: boolean > Default: true > Description: Manage XFree86 4.x server configuration file with debconf? > The /etc/X11/XF86Config-4 file, which contains the configuration information > for the XFree86 version 4 X server, can be handled automatically by debconf, > or manually by you. > . > Note that only specific, marked sections of the configuration file will be > handled by debconf if you select this option; if those markers are absent, > the configuration file will not be updated automatically, and you will have > to update the file manually, or move or delete the file. > > To shut this off, "dpkg-reconfigure xserver-xfree86". > > -- > G. Branden Robinson|If a man ate a pound of pasta and a > Debian GNU/Linux |pound of antipasto, would they > [EMAIL PROTECTED] |cancel out, leaving him still > http://people.debian.org/~branden/ |hungry? -- Scott Adams Thanks, David Kordonowy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
severity 163885 normal thanks This is the worst bug report I've seen in a long time, but then I've grown accustomed to such from the person who hides behind the nom de annoyance "Lazarus Long". On Wed, Oct 09, 2002 at 12:54:01AM +, Lazarus Long wrote: > Package: xserver-xfree86 > Version: N/A Horse puckey. I don't support Red Hat packages. Tell me which version of the official Debian packages you're running or see your report closed. > Severity: important > > (Probably higher severity, due to hardware threat, but ... ?) "hardware threat"? What the heck is that? > (Invoked as user, with a plain "startx" command line) > > (protocol Version 11, revision 0, vendor release 6600) I notice you excised the line that reveals the build information. Furthermore, your server log is missing a *lot* of information. Did you trim this down? Where is the unadulterated /var/log/XFree86.*.log file? Have you read XF86Config(7)? Why have you not supplied the information that is requested, and required for the resolution of most bug reports? If it is too much trouble for you to gather the requisite information, I recommend the "reportbug" package and command; it will gather it for you. > (EE) R128(0): [dri] R128DRIScreenInit failed because of a version mismatch. > [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed. > [dri] Disabling the DRI. Okay, so souped-up 3D acceleration won't work because your kernel is too old. This is in no way an "important" bug. We have people who can't even start the X server because it coredumps. That's "important". > (EE) R128(0): [drm] failed to remove DRM signal handler > DRIUnlock called when not locked I'll note to no one in particular that the X server should probably set a global variable tracking whether drm was initialized, and not bother to remove a signal handler that never got established. But this is a pretty minor complaint. > (EE) xf86OpenSerial: Cannot open device /dev/input/mice > No such file or directory. > (EE) Generic Mouse: cannot open input device > (EE) PreInit failed for input device "Generic Mouse" These are harmless and simply the result of my efforts to support USB mice without any intervention on the part of the user. Blisfully, it's evidence that you are actually running Debian, and not trying to trick me into supporting Red Hat or SuSE. > _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root > SESSION_MANAGER=local/farm:/tmp/.ICE-unix/5500 > SetKbdSettings - type: 2 rate: 30 delay: 500 snumlk: 0 > SetKbdSettings - Succeeded > Warning: This version of gmix was compiled with > OSS version 3.8.2, and your system is running > version 3.8.16. > X connection to :0.0 broken (explicit kill or server shutdown). > Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). > xinit: connection to X server lost. > X connection to :0.0 broken (explicit kill or server shutdown). > xscreensaver-gl-helper: couldn't open display :0.0 > X connection to :0.0 broken (explicit kill or server shutdown). These all have to do with your X clients and aren't germane to your bug report. > (I Alt-Ctrl-Backspace'd here, due to the screen mess and fear of hardware > damage.) Fear of hardware damage? What are you smoking? XFree86 and the kernel couldn't agree on a protocol for melting the heat sink on your 3D-accelerated graphics card to slag while animating multitextured NURBS porn. You should be grateful; not using DRI probably keeps your computer chassis ten degrees cooler. > The kernel is 2.4.19, so I'm not sure how to get any more recent version > of this kernel module. Did you compile this against a 2.5.X box perhaps? No. > Hmmm, no, I see "Build Operating System: Linux 2.4.18 i686 [ELF]" > so that's not it. Where did you manage to get something more recent > than what's in the current stable kernel, while running a current-1 > kernel version? Odd, at best. XFree86 periodically does CVS merges from the DRI project at SourceForge. Those guys also develop the DRM modules that live inside the kernel, so the Linux kernel hackers periodically sync up with them as well. The release cycles of XFree86 and the Linux kernel are not in sync. There is not a lot that Debian can do about this. It was my understanding that DRI on the XFree86 side was supposed to maintain backward compatibility, but apparently that didn't happen. Not sure what's going on here. Michel Dänzer reads the debian-x list; perhaps he knows. > I had hoped 4.2.1-2 would fix this, so held off on filing until trying > that, but it still has the same problem. This problem was not present > in 4.1.0-whatever (sarge) versions and only showed up in 4.2.1-1, to > my awareness. > > What further info would you like? What would you like me to test? I'd like to see the information described in XF86Config(7). Other than that this problem probably isn't easily resolvable. I don't recommend that you run a 2.5.x kernel. For t
Bug#163885: additional info -- [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
On Wed, Oct 09, 2002 at 01:18:03AM +, Lazarus Long wrote: > Additional info: > The same errors occur when rebooting to an old kernel, 2.4.18, from way > back in March. (I thought perhaps for some strange reason the module > version had been reverted in the current kernel. That's not the case, > apparently, saving you looking into that.) No, if the modules in kernel 2.4.19 didn't support DRI version 2.2, the modules in 2.4.18 almost certainly wouldn't. > XFree86 Version 4.2.1 (Debian 4.2.1-2 20021008045526 [EMAIL PROTECTED]) / X Window >System Well, this is an improvement. It would still be nice to see the information described in XF86Config(7), though. -- G. Branden Robinson| What influenced me to atheism was Debian GNU/Linux | reading the Bible cover to cover. [EMAIL PROTECTED] | Twice. http://people.debian.org/~branden/ | -- J. Michael Straczynski msg04060/pgp0.pgp Description: PGP signature
Processed: Re: Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
Processing commands for [EMAIL PROTECTED]: > severity 163885 normal Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed. Severity set to `normal'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163837: startx: hostname version is displayed
On Tue, Oct 08, 2002 at 09:58:14PM +0200, Beat Bolli wrote: > Well, the question is if Debian has the GNU hostname command. Since the grep > doesn't match, I deduced that I don't have GNU hostname, based on the > assumption that the person who coded this knew that GNU hostname would > output its version string on stdout... I prefer John's patch. Consolidate stdout and stderr and grep them together. * if it's a GNU program, "GNU" is bound to show up somewhere * no chance of grep blocking to wait for input unless hostname itself hangs * GNU can change its mind about where to send the version string and the code still works -- G. Branden Robinson| "Why do we have to hide from the Debian GNU/Linux | police, Daddy?" [EMAIL PROTECTED] | "Because we use vi, son. They use http://people.debian.org/~branden/ | emacs." msg04058/pgp0.pgp Description: PGP signature
Re: xserver-xfree86 replacing /etc/X11/XF86Config-4
On Tue, Oct 08, 2002 at 08:52:43PM -0400, David N Kordonowy wrote: > When upgrading X, xserver-xfree86 replaces my/etc/X11/XF86Config-4 file > even though it has been modified by me. My /etc/X11/XF86Config-4 is a > link to another file (in this case it is /etc/X11/XF86Config-4.sun). > The package xserver-xfree86 replaces this link with its file, thus > breaking X. > > Is this normal behavior for packages or is this simply a result of my > nontypical setup? Have you read the very top of the generated XF86Config-4 file? ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. In what way does the above not make the situation clear? This behavior is controlled by a debconf question: Template: xserver-xfree86/manage_config_with_debconf Type: boolean Default: true Description: Manage XFree86 4.x server configuration file with debconf? The /etc/X11/XF86Config-4 file, which contains the configuration information for the XFree86 version 4 X server, can be handled automatically by debconf, or manually by you. . Note that only specific, marked sections of the configuration file will be handled by debconf if you select this option; if those markers are absent, the configuration file will not be updated automatically, and you will have to update the file manually, or move or delete the file. To shut this off, "dpkg-reconfigure xserver-xfree86". -- G. Branden Robinson|If a man ate a pound of pasta and a Debian GNU/Linux |pound of antipasto, would they [EMAIL PROTECTED] |cancel out, leaving him still http://people.debian.org/~branden/ |hungry? -- Scott Adams msg04057/pgp0.pgp Description: PGP signature
Bug#163815: reportbug not attaching your XFree86 log files?
On Wed, Oct 09, 2002 at 12:49:42AM +0100, Paul Martin wrote: > Reportbug *did* include an XFree86.0.log. However, it was from the > working 4.1.0-16 I was running at the time, so I removed it... > > Flame away. Aha. Sorry for the false positive, Chris. Not sure about the other yet, though. > If you really do want the XFree86.0.log from 4.2.1, I'll provide it. > There didn't seem to be anything clueful in there (nothing that I > don't see in the log from 4.1.0). Yes, please do always include it. I've never yet had to flame anyone for including the server output. :) Sometimes it is superfluous, but it isn't for *most* of the bug reports I against the package. -- G. Branden Robinson| Debian GNU/Linux | kernel panic -- causal failure [EMAIL PROTECTED] | universe will now reboot http://people.debian.org/~branden/ | msg04056/pgp0.pgp Description: PGP signature
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 08:07:39PM -0500, Branden Robinson wrote: > On Tue, Oct 08, 2002 at 04:45:18PM -0600, Joel Baker wrote: > > > > @@ -356,0 +355 @@ > > > > +usr/X11R6/bin/kbd_mode > > > > > > I used to see this on Sun machines. You sure it's necessary with modern > > > BSD kernels? > > > > I'm not sure it is. I mostly don't know where/how to check whether it is, > > or what it's supposed to do. > > It changes the tty keyboard reading mode, e.g., from "raw" to "cooked" > and vice versa. > > I think Linux doesn't have this because a keyboard state is specific to > each virtual terminal, so the kernel knows to put the keyboard state > back after the X server crashes and gives up its VT. > > On Sun boxen, you often had to telnet[1] into the box after X crashed and > run "kbd_mode -a". Ah. Yes, I remember doing that now. And I suspect it's obsolete on modern NetBSD, then, because it also has virtual terminals (albeit of a different sort, but the same concept) with which X interacts directly. Two different versions thereof, even. I'll see if I can convince it to stop building. > > > > @@ -5543,2 +5539,0 @@ > > > > -usr/X11R6/lib/libI810XvMC.a > > > > -usr/X11R6/lib/libI810XvMC_pic.a > > > > > > This is new to XFree86 4.2. My guess is that it does something to hook > > > into the (Linux) kernel to speak foul magic to the hardware. XvMC is > > > Mark Vojkovich's motion compensation interface on top of the XVideo (Xv) > > > extension. I'll cautiously assume that *BSD shouldn't be building this. > > > > We can always put it back in if someone can show that it should build/work > > on NetBSD platforms. However, at the moment, this is not listed as being > > supportd on the NetBSD arch page in XFree86 docs. Will yank it. > > I forgot to mention that you *should* have libXvMC. Just probably not > this I810 thing. Left those in; only the I810 files were removed from the MANIFEST. > > > Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer > > > understands better how this stuff works. (I.e., I don't know *why* it's > > > called the "offscreen" Mesa library, or why 3D-accelerated GL rendering > > > is considered "off-the-screen". Maybe it means the rendering isn't done > > > into the framebuffer, a.k.a. "screen"?) > > > > Er. Is that 'not building DRI implies not building libOSMesa' - IE, it > > should be removed for non-Linux platforms? > > Correct, as I understand it. Okay. Makes sense to me. > > > > @@ -5602,0 +5595 @@ > > > > +usr/X11R6/lib/liboldX.so.6.0 > > > > > > This goes in xlibs-dev.files. Already listed there. > > > > Huh. xlibs-dev.files (and all of the MANIFESTs) have a static library > > (/usr/X11R6/lib/liboldX.a) rather than a dynamic one. Maybe I need to tweak > > a suitable part of the system and tell it to build a static liboldX? > > Sorry, I failed to pay attention. Please don't ship a shared liboldX > unless for some insane reason you need it for binary compatiblity with > other BSDs. It would be preferable to turn of building of the shared > version. I'll see if I can figure out why it's doing so and whack it into a static instead. > > > > @@ -5608 +5600,0 @@ > > > > -usr/X11R6/lib/libxrx.so.6.3 > > > > > > Another extension no one uses. This is the Netscape Navigator plug in > > > that lets you render the X server inside a browser window or some lunacy > > > like that. I'm not sure there's a good reason it shouldn't build on > > > *BSD versus Linux, but on the other hand there's probably not a good > > > reason for *anyone* to build it. > > > > Hmmm. I'll look into it, but after I do other things, then; tentatively > > left in place, until I can figure out what is up with it on NetBSD. > > Maybe the Netscape plugin code is Linux-specific? I have no idea. I'm > sure no one cares about this thing. I'm sure, too, but *iff* it compiles, well, it would be nice to make it available. But low priority. :) > > Now, the explanation for glxinfo (and it probably has much deeper > > reprecussions): NetBSD includes bsdLib.rules, which does not have a number > > of things from lnxLib.rules (the thing which made me realize this matters > > is that it lacks SharedDepCplusplusLib, causing libGLU to be linked with > > 'gcc' instead of 'g++', causing glxinfo to fail when it tried to link > > against the .so because the .so couldn't find various C++ system library > > things). > > > > Nor can I just drop in lnxLib.rules (unsuprisingly), because it wreaks a > > lot of havoc in other places. So I'm going to have to general a patch set > > for bsdLib, providing the bits from lnxLib that are required to make things > > compile in a Debian-happy way. > > I don't have very much useful to offer here. I have some facility with > Imake after fighting with it for so many years, but I phear the > *Lib.rules files. I think I found it. The bsdLib.rules ELF rules are 'copied mostly from the linux rules' - but lacked a SharedDepCplusplusLibraryTarg
Bug#163885: additional info -- [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
Additional info: The same errors occur when rebooting to an old kernel, 2.4.18, from way back in March. (I thought perhaps for some strange reason the module version had been reverted in the current kernel. That's not the case, apparently, saving you looking into that.) Linux phoenix 2.4.18 #1 Thu Mar 14 01:51:04 UTC 2002 i686 unknown unknown GNU/Linux Paste follow, but nothing appears changed (other than being shorter, since I Alt-Ctrl-Backspace'd earlier.) XFree86 Version 4.2.1 (Debian 4.2.1-2 20021008045526 [EMAIL PROTECTED]) / 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 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: Wed Oct 9 01:00:32 2002 (==) Using config file: "/etc/X11/XF86Config-4" (EE) R128(0): [dri] R128DRIScreenInit failed because of a version mismatch. [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed. [dri] Disabling the DRI. (EE) R128(0): [drm] failed to remove DRM signal handler DRIUnlock called when not locked (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such file or directory. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device "Generic Mouse" xinit: connection to X server lost. -- Please (OpenPGP) encrypt all mail whenever possible. Request the following Public Keys for Lazarus Long <[EMAIL PROTECTED]> TypeBits/KeyIDFingerprint DSA KeyID: ElGamal: 2048g/CCB09D64 8270 4B79 CB1E 433B 6214 64EB 9D58 28A9 E8B1 27F4 msg04054/pgp0.pgp Description: PGP signature
Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
On Die, 2002-10-08 at 17:41, Matt Filizzi wrote: > > After upgrading to 4.2.1 and typing startx, it would fail and give me an > error that the screen color depth is incorrect (24) It would be interesting to see why it fails there, I seem to remember problems when not explicitly specifying fbbpp. > after setting to 16 it works, however everything becomes a green tint. > This is able to be fixed by removing the fbdev setings (and > recompiling the kernel to not use fbdev). If it works with depth 15, the framebuffer device is probably broken. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 05:04:18PM -0500, Branden Robinson wrote: > On Tue, Oct 08, 2002 at 01:33:38PM -0600, Joel Baker wrote: > > The good: > > > > After a bit of banging on things to force the circular dependancy path > > between freetype and xfree86, and cribbing from the patches written for > > 4.1.0, I'm close (very close) to having a set of patches to make xfree86 > > compile cleanly on the netbsd-i386 arch. > > Cool! > > > The bad: > > > > It requires some extensive patching. Some of this (strnlen portability > > in xserver-wrapper.c, etc) has already been filed; the rest is waiting > > on me getting the last bits hammered out. I've tried to make the patches > > something that would be acceptable to upstream, but I have no idea if > > they really will be. The most extensive, unsuprisingly, are to NetBSD.cf, > > and are largely cribbed from linux.cf; however, changes to imake and > > other things also need to happen. > > I gather that xc/config/cf/bsdLib.rules is going to be painful as well. So I'm finding out. Not sure whether to patch this extensively, or just generate a completely new file and patch NetBSD.cf to include that. Probably patch. > > The ugly: > > > > --- debian/MANIFEST.netbsd-i386 2002-10-08 07:23:56.0 + > > +++ debian/MANIFEST.netbsd-i386.new 2002-10-08 18:50:48.0 > > + > > @@ -197 +196,0 @@ > > -etc/X11/xkb/symbols/alt > > Obsolete. See changelog. Okay. > > @@ -353 +351,0 @@ > > -usr/X11R6/bin/glxinfo > > I can't think of a reason this shouldn't be built. It should be > possible to build the GLX extension, and therefore this client, even > without DRI stuff. See below. > > @@ -356,0 +355 @@ > > +usr/X11R6/bin/kbd_mode > > I used to see this on Sun machines. You sure it's necessary with modern > BSD kernels? I'm not sure it is. I mostly don't know where/how to check whether it is, or what it's supposed to do. > > @@ -838,2 +836,0 @@ > > -usr/X11R6/include/X11/extensions/xf86rush.h > > -usr/X11R6/include/X11/extensions/xf86rushstr.h > > Looks okay. This is the never-used Voodoo Rush extension. It builds on > Linux/i386 but I've never heard of anyone using it for anything. Okay. I'll yank those then. > > @@ -5543,2 +5539,0 @@ > > -usr/X11R6/lib/libI810XvMC.a > > -usr/X11R6/lib/libI810XvMC_pic.a > > This is new to XFree86 4.2. My guess is that it does something to hook > into the (Linux) kernel to speak foul magic to the hardware. XvMC is > Mark Vojkovich's motion compensation interface on top of the XVideo (Xv) > extension. I'll cautiously assume that *BSD shouldn't be building this. We can always put it back in if someone can show that it should build/work on NetBSD platforms. However, at the moment, this is not listed as being supportd on the NetBSD arch page in XFree86 docs. Will yank it. > > @@ -5547,2 +5541,0 @@ > > -usr/X11R6/lib/libOSMesa.a > > -usr/X11R6/lib/libOSMesa.so.3.3 > > Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer > understands better how this stuff works. (I.e., I don't know *why* it's > called the "offscreen" Mesa library, or why 3D-accelerated GL rendering > is considered "off-the-screen". Maybe it means the rendering isn't done > into the framebuffer, a.k.a. "screen"?) Er. Is that 'not building DRI implies not building libOSMesa' - IE, it should be removed for non-Linux platforms? > > @@ -5593 +5585,0 @@ > > -usr/X11R6/lib/libXxf86rush.a > > Voodoo Rush extension; see above. Removed. > > @@ -5602,0 +5595 @@ > > +usr/X11R6/lib/liboldX.so.6.0 > > This goes in xlibs-dev.files. Already listed there. Huh. xlibs-dev.files (and all of the MANIFESTs) have a static library (/usr/X11R6/lib/liboldX.a) rather than a dynamic one. Maybe I need to tweak a suitable part of the system and tell it to build a static liboldX? > > @@ -5608 +5600,0 @@ > > -usr/X11R6/lib/libxrx.so.6.3 > > Another extension no one uses. This is the Netscape Navigator plug in > that lets you render the X server inside a browser window or some lunacy > like that. I'm not sure there's a good reason it shouldn't build on > *BSD versus Linux, but on the other hand there's probably not a good > reason for *anyone* to build it. Hmmm. I'll look into it, but after I do other things, then; tentatively left in place, until I can figure out what is up with it on NetBSD. > > @@ -5752,0 +5745 @@ > > +usr/X11R6/man/man1/kbd_mode.1x > > See above. > > > @@ -5754 +5746,0 @@ > > -usr/X11R6/man/man1/libxrx.1x > > See above. Si. > > @@ -7449 +7441 @@ > > -var/lib/xkb/README > > +var/db/xkb/README > > I gather that *BSD cares not for the FHS. I remember having to persuade > David Dawes to switch Linux back to /var/lib. Apparently the BSDs had > already had enough. True, mostly I just need to find the relevant thing and tweak it, I think. > > DRI support is, of course, not relevant on the NetBSD kernel, and is not > > present (and
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 04:45:18PM -0600, Joel Baker wrote: > > > @@ -356,0 +355 @@ > > > +usr/X11R6/bin/kbd_mode > > > > I used to see this on Sun machines. You sure it's necessary with modern > > BSD kernels? > > I'm not sure it is. I mostly don't know where/how to check whether it is, > or what it's supposed to do. It changes the tty keyboard reading mode, e.g., from "raw" to "cooked" and vice versa. I think Linux doesn't have this because a keyboard state is specific to each virtual terminal, so the kernel knows to put the keyboard state back after the X server crashes and gives up its VT. On Sun boxen, you often had to telnet[1] into the box after X crashed and run "kbd_mode -a". > > > @@ -5543,2 +5539,0 @@ > > > -usr/X11R6/lib/libI810XvMC.a > > > -usr/X11R6/lib/libI810XvMC_pic.a > > > > This is new to XFree86 4.2. My guess is that it does something to hook > > into the (Linux) kernel to speak foul magic to the hardware. XvMC is > > Mark Vojkovich's motion compensation interface on top of the XVideo (Xv) > > extension. I'll cautiously assume that *BSD shouldn't be building this. > > We can always put it back in if someone can show that it should build/work > on NetBSD platforms. However, at the moment, this is not listed as being > supportd on the NetBSD arch page in XFree86 docs. Will yank it. I forgot to mention that you *should* have libXvMC. Just probably not this I810 thing. > > Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer > > understands better how this stuff works. (I.e., I don't know *why* it's > > called the "offscreen" Mesa library, or why 3D-accelerated GL rendering > > is considered "off-the-screen". Maybe it means the rendering isn't done > > into the framebuffer, a.k.a. "screen"?) > > Er. Is that 'not building DRI implies not building libOSMesa' - IE, it > should be removed for non-Linux platforms? Correct, as I understand it. > > > @@ -5602,0 +5595 @@ > > > +usr/X11R6/lib/liboldX.so.6.0 > > > > This goes in xlibs-dev.files. Already listed there. > > Huh. xlibs-dev.files (and all of the MANIFESTs) have a static library > (/usr/X11R6/lib/liboldX.a) rather than a dynamic one. Maybe I need to tweak > a suitable part of the system and tell it to build a static liboldX? Sorry, I failed to pay attention. Please don't ship a shared liboldX unless for some insane reason you need it for binary compatiblity with other BSDs. It would be preferable to turn of building of the shared version. > > > @@ -5608 +5600,0 @@ > > > -usr/X11R6/lib/libxrx.so.6.3 > > > > Another extension no one uses. This is the Netscape Navigator plug in > > that lets you render the X server inside a browser window or some lunacy > > like that. I'm not sure there's a good reason it shouldn't build on > > *BSD versus Linux, but on the other hand there's probably not a good > > reason for *anyone* to build it. > > Hmmm. I'll look into it, but after I do other things, then; tentatively > left in place, until I can figure out what is up with it on NetBSD. Maybe the Netscape plugin code is Linux-specific? I have no idea. I'm sure no one cares about this thing. > Policy says FHS; Debian/NetBSD, at least, is basically NetBSD kernel, libc, > and other required system libraries, but Debian-package-pure userspace, > filesystem arrangement, et al. The only exception so far is that, on the > 1.6 port, ld.so and family live in /usr/libexec, but NetBSD native moved > this to /lib (as well as making /lib dynamic) in -current immediately after > the 1.6 release, so even that will probably go away before it requires a > Policy adjustment. > > As such, I'll change the patch and tweak said symbol to put it where the > FHS says. Okay. /var/lib instead of /var/db for Debian/NetBSD it is, then. > Now, the explanation for glxinfo (and it probably has much deeper > reprecussions): NetBSD includes bsdLib.rules, which does not have a number > of things from lnxLib.rules (the thing which made me realize this matters > is that it lacks SharedDepCplusplusLib, causing libGLU to be linked with > 'gcc' instead of 'g++', causing glxinfo to fail when it tried to link > against the .so because the .so couldn't find various C++ system library > things). > > Nor can I just drop in lnxLib.rules (unsuprisingly), because it wreaks a > lot of havoc in other places. So I'm going to have to general a patch set > for bsdLib, providing the bits from lnxLib that are required to make things > compile in a Debian-happy way. I don't have very much useful to offer here. I have some facility with Imake after fighting with it for so many years, but I phear the *Lib.rules files. > Anyway, I'll be back once I beat on it some more. Any suggestions on what > to check to find out if kdb_mode is relevant would be appreciated. If the keyboard is generally hosed after the X server exits (test it under a crash too -- kill -SEGV the X server) then you probably don't need it. If existing userspace t
Bug#163622: xfree86-common: Error starting X, using Matrox G200
On Wed, Oct 09, 2002 at 12:31:01AM +0200, Michel Dänzer wrote: > Well, you can call LoaderPrintSymbol for each address with a ??, e.g. > > call LoaderPrintSymbol(0x40197cdc) > > Beware that the output goes to the server log only. Gee, thanks, I just tried that and cored my X server. Okay, so what are people *actually* supposed to do? > > Unfortunately, Debian's gdb does not contain this hack. > > Hopefully, the patch will be cleaned up and applied soon; it would > certainly make debugging X much easier. > > PS: I hope the submitter doesn't get this twice? The submitter only gets mail to -submitter and -done. > PPS: Quite some additional traffic on the list... http://lists.debian.org/debian-x/2002/debian-x-200210/msg00054.html -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy [EMAIL PROTECTED] |spot on the pavement, where used to http://people.debian.org/~branden/ |lie the carcass of a dead horse. msg04052/pgp0.pgp Description: PGP signature
Bug#163885: xserver-xfree86: [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed.
Package: xserver-xfree86 Version: N/A Severity: important (Probably higher severity, due to hardware threat, but ... ?) (Invoked as user, with a plain "startx" command line) (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 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: Wed Oct 9 00:39:15 2002 (==) Using config file: "/etc/X11/XF86Config-4" (EE) R128(0): [dri] R128DRIScreenInit failed because of a version mismatch. [dri] r128.o kernel module version is 2.1.6 but version 2.2 or greater is needed. [dri] Disabling the DRI. (EE) R128(0): [drm] failed to remove DRM signal handler DRIUnlock called when not locked (EE) xf86OpenSerial: Cannot open device /dev/input/mice No such file or directory. (EE) Generic Mouse: cannot open input device (EE) PreInit failed for input device "Generic Mouse" _IceTransmkdir: Owner of /tmp/.ICE-unix should be set to root SESSION_MANAGER=local/farm:/tmp/.ICE-unix/5500 SetKbdSettings - type: 2 rate: 30 delay: 500 snumlk: 0 SetKbdSettings - Succeeded Warning: This version of gmix was compiled with OSS version 3.8.2, and your system is running version 3.8.16. X connection to :0.0 broken (explicit kill or server shutdown). Gdk-ERROR **: X connection to :0.0 broken (explicit kill or server shutdown). xinit: connection to X server lost. X connection to :0.0 broken (explicit kill or server shutdown). xscreensaver-gl-helper: couldn't open display :0.0 X connection to :0.0 broken (explicit kill or server shutdown). (I Alt-Ctrl-Backspace'd here, due to the screen mess and fear of hardware damage.) The kernel is 2.4.19, so I'm not sure how to get any more recent version of this kernel module. Did you compile this against a 2.5.X box perhaps? Hmmm, no, I see "Build Operating System: Linux 2.4.18 i686 [ELF]" so that's not it. Where did you manage to get something more recent than what's in the current stable kernel, while running a current-1 kernel version? Odd, at best. I had hoped 4.2.1-2 would fix this, so held off on filing until trying that, but it still has the same problem. This problem was not present in 4.1.0-whatever (sarge) versions and only showed up in 4.2.1-1, to my awareness. What further info would you like? What would you like me to test? -- System Information Debian Release: post-3.0(+) Kernel Version: Linux phoenix 2.4.19 #1 Tue Sep 17 20:34:42 UTC 2002 i586 unknown unknown GNU/Linux -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163622: xfree86-common: Error starting X, using Matrox G200
On Die, 2002-10-08 at 18:52, Branden Robinson wrote: > On Mon, Oct 07, 2002 at 08:55:26PM -0400, Ian Bicking wrote: > > Here's the backtrace, tell me if there's anything more you need: > [...] > > #7 0x0807f3c8 in xf86SigHandler (signo=11) at xf86Events.c:1085 > > signo = 11 > > #8 0x4007e518 in sigaction () from /lib/libc.so.6 > > No symbol table info available. > > #9 0x40197cdc in ?? () > > No symbol table info available. > > #10 0x0852b478 in ?? () > > No symbol table info available. > > #11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5, > > argv=0xbdf4) > > at xf86Init.c:528 > > i = 1075228112 > > j = 0 > > k = 1074540038 > > scr_index = 1074540038 > > No symbol table info available. > > Figures. Died in one of the modules, which are invisible to gdb. > > The only way to nail this down is to use the specially-hacked version of > gdb that understand XFree86 server modules. Well, you can call LoaderPrintSymbol for each address with a ??, e.g. call LoaderPrintSymbol(0x40197cdc) Beware that the output goes to the server log only. > Unfortunately, Debian's gdb does not contain this hack. Hopefully, the patch will be cleaned up and applied soon; it would certainly make debugging X much easier. PS: I hope the submitter doesn't get this twice? PPS: Quite some additional traffic on the list... -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
xserver-xfree86 replacing /etc/X11/XF86Config-4
Hi, When upgrading X, xserver-xfree86 replaces my/etc/X11/XF86Config-4 file even though it has been modified by me. My /etc/X11/XF86Config-4 is a link to another file (in this case it is /etc/X11/XF86Config-4.sun). The package xserver-xfree86 replaces this link with its file, thus breaking X. Is this normal behavior for packages or is this simply a result of my nontypical setup? Please cc: me to any responses as I'm not subscribed to this mailing list. If this is the incorrect mailing list to question, then accept my apologies. Thanks, David Kordonowy [pre-upgrade] $ ls -l /etc/X11/XF86Config-4 lrwxrwxrwx1 root root 16 Oct 8 20:09 /etc/X11/XF86Config-4 -> XF86Config-4.sun [post-upgrade] $ ls -l /etc/X11/XF86Config-4 -rw-r--r--1 root root 2748 Oct 8 20:12 /etc/X11/XF86Config-4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 01:33:38PM -0600, Joel Baker wrote:
> The good:
>
> After a bit of banging on things to force the circular dependancy path
> between freetype and xfree86, and cribbing from the patches written for
> 4.1.0, I'm close (very close) to having a set of patches to make xfree86
> compile cleanly on the netbsd-i386 arch.
Cool!
> The bad:
>
> It requires some extensive patching. Some of this (strnlen portability
> in xserver-wrapper.c, etc) has already been filed; the rest is waiting
> on me getting the last bits hammered out. I've tried to make the patches
> something that would be acceptable to upstream, but I have no idea if
> they really will be. The most extensive, unsuprisingly, are to NetBSD.cf,
> and are largely cribbed from linux.cf; however, changes to imake and
> other things also need to happen.
I gather that xc/config/cf/bsdLib.rules is going to be painful as well.
> The ugly:
>
> --- debian/MANIFEST.netbsd-i386 2002-10-08 07:23:56.0 +
> +++ debian/MANIFEST.netbsd-i386.new 2002-10-08 18:50:48.0
> +
> @@ -197 +196,0 @@
> -etc/X11/xkb/symbols/alt
Obsolete. See changelog.
> @@ -353 +351,0 @@
> -usr/X11R6/bin/glxinfo
I can't think of a reason this shouldn't be built. It should be
possible to build the GLX extension, and therefore this client, even
without DRI stuff.
> @@ -356,0 +355 @@
> +usr/X11R6/bin/kbd_mode
I used to see this on Sun machines. You sure it's necessary with modern
BSD kernels?
> @@ -838,2 +836,0 @@
> -usr/X11R6/include/X11/extensions/xf86rush.h
> -usr/X11R6/include/X11/extensions/xf86rushstr.h
Looks okay. This is the never-used Voodoo Rush extension. It builds on
Linux/i386 but I've never heard of anyone using it for anything.
> @@ -5543,2 +5539,0 @@
> -usr/X11R6/lib/libI810XvMC.a
> -usr/X11R6/lib/libI810XvMC_pic.a
This is new to XFree86 4.2. My guess is that it does something to hook
into the (Linux) kernel to speak foul magic to the hardware. XvMC is
Mark Vojkovich's motion compensation interface on top of the XVideo (Xv)
extension. I'll cautiously assume that *BSD shouldn't be building this.
> @@ -5547,2 +5541,0 @@
> -usr/X11R6/lib/libOSMesa.a
> -usr/X11R6/lib/libOSMesa.so.3.3
Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer
understands better how this stuff works. (I.e., I don't know *why* it's
called the "offscreen" Mesa library, or why 3D-accelerated GL rendering
is considered "off-the-screen". Maybe it means the rendering isn't done
into the framebuffer, a.k.a. "screen"?)
> @@ -5593 +5585,0 @@
> -usr/X11R6/lib/libXxf86rush.a
Voodoo Rush extension; see above.
> @@ -5602,0 +5595 @@
> +usr/X11R6/lib/liboldX.so.6.0
This goes in xlibs-dev.files. Already listed there.
> @@ -5608 +5600,0 @@
> -usr/X11R6/lib/libxrx.so.6.3
Another extension no one uses. This is the Netscape Navigator plug in
that lets you render the X server inside a browser window or some lunacy
like that. I'm not sure there's a good reason it shouldn't build on
*BSD versus Linux, but on the other hand there's probably not a good
reason for *anyone* to build it.
> @@ -5752,0 +5745 @@
> +usr/X11R6/man/man1/kbd_mode.1x
See above.
> @@ -5754 +5746,0 @@
> -usr/X11R6/man/man1/libxrx.1x
See above.
> @@ -7449 +7441 @@
> -var/lib/xkb/README
> +var/db/xkb/README
I gather that *BSD cares not for the FHS. I remember having to persuade
David Dawes to switch Linux back to /var/lib. Apparently the BSDs had
already had enough.
> DRI support is, of course, not relevant on the NetBSD kernel, and is not
> present (and the related files have been removed already); the same goes
> for the video4linux drivers. libGL and company, which didn't compile under
> 4.1.0, now work (I think this is largely because the NetBSD port has
> upgraded to version 1.6 in the meanwhile, and this is a major cleanup of
> the NetBSD base system).
You can build libGL without DRI support. Several Linux architectures do
it.
> I'm assuming that I can find a way to weak the /var/{lib,db}/xkb/README
> location somewhere; I haven't dug into it yet.
The answer to this question depends on which altar at which Debian/*BSD
decides to worship; the FHS, or the other BSDs. Once that decision is
made I'm happy to help you out with it. There's an Imake symbol called
VarDbDirectory, I believe, which reflects the BSD experience of the
XFree86 Core Team. :)
Thanks for working on this!
--
G. Branden Robinson|Men use thought only to justify
Debian GNU/Linux |their wrong doings, and speech only
[EMAIL PROTECTED] |to conceal their thoughts.
http://people.debian.org/~branden/ |-- Voltaire
pgpeAHTXqPxFf.pgp
Description: PGP signature
Re: m68k buildd's without 1.5GB of free disk should not attempt xfree86
On Tue, Oct 08, 2002 at 05:00:21PM -0300, John Lenton wrote: > I don't know XDirectFB, but the kdrive servers are probably > better served being compiled against a uclibc (yes they compile > cleanly against the newer uclibcs). Unless the idea is to use > Xvesa as a failsafe X server for intel. Else what's the point? > the libs are bigger than the execs anyway. Noted. Jim Gettys is the one who asked for it so I guess I'll ask his opinion. -- G. Branden Robinson|I'm sorry if the following sounds Debian GNU/Linux |combative and excessively personal, [EMAIL PROTECTED] |but that's my general style. http://people.debian.org/~branden/ |-- Ian Jackson pgpiAX0bKA7yP.pgp Description: PGP signature
Re: Xvideo extension, radeon mobility Xfree 4.2.1
On Die, 2002-10-08 at 22:35, Matija Grabnar wrote: > I was looking forward to this version of Xfree because it is supposed > to support the more advanced features of my laptop's Radeon Mobility > card. > > Specificaly, I want/need hardware scaling for video. > > I would like to emphasize here that I'm probably overlooking something > stupid. This is an appeal for help, not a bug report. > I'm running Debian Sid, obviously. > > I can see in the xfree log that the Xvideo extension gets loaded, but > it's not visible to xvinfo or to mplayer -vo xv. > > I am hoping this means I overlooked some setting, configuration file > or some other obvious thing I should change in my setting and not > some deficiency in the support for Radeon mobility. The vesa driver doesn't support the XVideo extension, you need the ati driver. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
Re: Xvideo extension, radeon mobility Xfree 4.2.1
On Tue, 08 Oct 2002, Matija Grabnar wrote: > I was looking forward to this version of Xfree because it is supposed > to support the more advanced features of my laptop's Radeon Mobility > card. It looks like you're using the 'vesa' driver: > (--) Chipset vesa found You should switch to the ATI Radeon driver (manually or using the dpkg-reconfigure xserver-xfree86 command). Martijn -- And Billy Joel? He hasn't had a hit since Usenet started. - The Internet Oracle
Re: m68k buildd's without 1.5GB of free disk should not attempt xfree86
On Tue, Oct 08, 2002 at 02:49:53PM -0500, Branden Robinson wrote: > > XFree86 was always huge but now it's huger thanks to the static > debugging X server build, and with people snapping at my heels to build > XDirectFB and TinyX X servers as well, it's only going to get huger. I don't know XDirectFB, but the kdrive servers are probably better served being compiled against a uclibc (yes they compile cleanly against the newer uclibcs). Unless the idea is to use Xvesa as a failsafe X server for intel. Else what's the point? the libs are bigger than the execs anyway. -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: People who make no mistakes do not usually make anything.
Bug#163815: reportbug not attaching your XFree86 log files?
Hi guys, You gentlemen both reported bugs against xserver-xfree86 recently, but neglected to include your XFree86.0.log files as requested by XF86Config(7). I was about to flame you for setting a bad precedent, but the thought occurred that this may not have been a deliberate act of provocation on you guys' part. :) I notice that you're both using reportbug 2.2. I didn't get/haven't yet gotten any bug reports filed by reportbug 2.1, but I notice that reports filed with 2.0 *did* include people's log files. I do not think this is a coincidence, and the fact that these two bugs from different people had exactly same the context excised in exactly the same way leads me to believe that this is reportbug's fault. So I have a couple of requests: 1) Can you guys send your bug numbers your /var/log/XFree86.0.log files if you haven't already? 2) Can the reportbug maintainer look into this? I don't yet have enough data for a bug report. I don't know what would cause parts of xserver-xfree86's "bug" script to work, and other parts to fail. Here's what it looks like: #!/bin/sh PATH=/sbin:$PATH if command -v lspci > /dev/null 2>&1; then LC_ALL=C lspci | grep 'VGA compatible controller:' >&3 LC_ALL=C lspci -n | grep 'Class 0300:' >&3 printf "\n" >&3 fi if [ -e /etc/X11/XF86Config-4 ]; then cat /etc/X11/XF86Config-4 >&3 printf "\n" >&3 fi if [ -e /var/log/XFree86.0.log ]; then cat /var/log/XFree86.0.log >&3 printf "\n" >&3 fi ls -d -l /var/log/XFree86.*.log >&3 2> /dev/null -- G. Branden Robinson| I suspect Linus wrote that in a Debian GNU/Linux | complicated way only to be able to [EMAIL PROTECTED] | have that comment in there. http://people.debian.org/~branden/ | -- Lars Wirzenius pgp2f3Vu1g9gB.pgp Description: PGP signature
Xvideo extension, radeon mobility Xfree 4.2.1
I was looking forward to this version of Xfree because it is supposed to support the more advanced features of my laptop's Radeon Mobility card. Specificaly, I want/need hardware scaling for video. I would like to emphasize here that I'm probably overlooking something stupid. This is an appeal for help, not a bug report. I'm running Debian Sid, obviously. I can see in the xfree log that the Xvideo extension gets loaded, but it's not visible to xvinfo or to mplayer -vo xv. I am hoping this means I overlooked some setting, configuration file or some other obvious thing I should change in my setting and not some deficiency in the support for Radeon mobility. xvinfo: xvinfo X-Video Extension version 2.2 screen #0 no adaptors present xdpyinfo: name of display::0.0 version number:11.0 vendor string:The XFree86 Project, Inc vendor release number:40201000 XFree86 version: 4.2.1 maximum request size: 4194300 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x12a, revert to Parent number of extensions:27 BIG-REQUESTS DOUBLE-BUFFER DPMS Extended-Visual-Information FontCache GLX LBX MIT-SCREEN-SAVER MIT-SHM MIT-SUNDRY-NONSTANDARD RECORD RENDER SECURITY SGI-GLX SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XFree86-Bigfont XFree86-DGA XFree86-Misc XFree86-VidModeExtension XInputExtension XKEYBOARD XTEST XVideo default screen number:0 number of screens:1 screen #0: dimensions:1400x1050 pixels (356x267 millimeters) resolution:100x100 dots per inch depths (7):16, 1, 4, 8, 15, 24, 32 root window id:0x36 depth of root window:16 planes number of colormaps:minimum 1, maximum 1 default colormap:0x20 default number of colormap cells:64 preallocated pixels:black 0, white 65535 options:backing-store NO, save-unders NO largest cursor:1400x1050 current input event mask:0xf87f3f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMaskEnterWindowMask LeaveWindowMask Button1MotionMaskButton2MotionMaskButton3MotionMask Button4MotionMaskButton5MotionMaskButtonMotionMask KeymapStateMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask ColormapChangeMask number of visuals:2 default visual id: 0x22 visual: visual id:0x22 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits visual: visual id:0x23 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits cat /var/log/XFree86.0.log XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 19:56:55 2002 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "Default Layout" (**) |-->Screen "StandAlone" (0) (**) | |-->Monitor "LaptopLCD" (**) | |-->Device "Vesa" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc101" (**) XKB: model: "pc101" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Configured Mouse" (**) |-->Input Device "Generic Mouse" (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fon
Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
On Die, 2002-10-08 at 17:41, Matt Filizzi wrote: > > After upgrading to 4.2.1 and typing startx, it would fail and give me an > error that the screen color depth is incorrect (24) It would be interesting to see why it fails there, I seem to remember problems when not explicitly specifying fbbpp. > after setting to 16 it works, however everything becomes a green tint. > This is able to be fixed by removing the fbdev setings (and > recompiling the kernel to not use fbdev). If it works with depth 15, the framebuffer device is probably broken. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 05:04:18PM -0500, Branden Robinson wrote: > On Tue, Oct 08, 2002 at 01:33:38PM -0600, Joel Baker wrote: > > The good: > > > > After a bit of banging on things to force the circular dependancy path > > between freetype and xfree86, and cribbing from the patches written for > > 4.1.0, I'm close (very close) to having a set of patches to make xfree86 > > compile cleanly on the netbsd-i386 arch. > > Cool! > > > The bad: > > > > It requires some extensive patching. Some of this (strnlen portability > > in xserver-wrapper.c, etc) has already been filed; the rest is waiting > > on me getting the last bits hammered out. I've tried to make the patches > > something that would be acceptable to upstream, but I have no idea if > > they really will be. The most extensive, unsuprisingly, are to NetBSD.cf, > > and are largely cribbed from linux.cf; however, changes to imake and > > other things also need to happen. > > I gather that xc/config/cf/bsdLib.rules is going to be painful as well. So I'm finding out. Not sure whether to patch this extensively, or just generate a completely new file and patch NetBSD.cf to include that. Probably patch. > > The ugly: > > > > --- debian/MANIFEST.netbsd-i386 2002-10-08 07:23:56.0 + > > +++ debian/MANIFEST.netbsd-i386.new 2002-10-08 18:50:48.0 > > + > > @@ -197 +196,0 @@ > > -etc/X11/xkb/symbols/alt > > Obsolete. See changelog. Okay. > > @@ -353 +351,0 @@ > > -usr/X11R6/bin/glxinfo > > I can't think of a reason this shouldn't be built. It should be > possible to build the GLX extension, and therefore this client, even > without DRI stuff. See below. > > @@ -356,0 +355 @@ > > +usr/X11R6/bin/kbd_mode > > I used to see this on Sun machines. You sure it's necessary with modern > BSD kernels? I'm not sure it is. I mostly don't know where/how to check whether it is, or what it's supposed to do. > > @@ -838,2 +836,0 @@ > > -usr/X11R6/include/X11/extensions/xf86rush.h > > -usr/X11R6/include/X11/extensions/xf86rushstr.h > > Looks okay. This is the never-used Voodoo Rush extension. It builds on > Linux/i386 but I've never heard of anyone using it for anything. Okay. I'll yank those then. > > @@ -5543,2 +5539,0 @@ > > -usr/X11R6/lib/libI810XvMC.a > > -usr/X11R6/lib/libI810XvMC_pic.a > > This is new to XFree86 4.2. My guess is that it does something to hook > into the (Linux) kernel to speak foul magic to the hardware. XvMC is > Mark Vojkovich's motion compensation interface on top of the XVideo (Xv) > extension. I'll cautiously assume that *BSD shouldn't be building this. We can always put it back in if someone can show that it should build/work on NetBSD platforms. However, at the moment, this is not listed as being supportd on the NetBSD arch page in XFree86 docs. Will yank it. > > @@ -5547,2 +5541,0 @@ > > -usr/X11R6/lib/libOSMesa.a > > -usr/X11R6/lib/libOSMesa.so.3.3 > > Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer > understands better how this stuff works. (I.e., I don't know *why* it's > called the "offscreen" Mesa library, or why 3D-accelerated GL rendering > is considered "off-the-screen". Maybe it means the rendering isn't done > into the framebuffer, a.k.a. "screen"?) Er. Is that 'not building DRI implies not building libOSMesa' - IE, it should be removed for non-Linux platforms? > > @@ -5593 +5585,0 @@ > > -usr/X11R6/lib/libXxf86rush.a > > Voodoo Rush extension; see above. Removed. > > @@ -5602,0 +5595 @@ > > +usr/X11R6/lib/liboldX.so.6.0 > > This goes in xlibs-dev.files. Already listed there. Huh. xlibs-dev.files (and all of the MANIFESTs) have a static library (/usr/X11R6/lib/liboldX.a) rather than a dynamic one. Maybe I need to tweak a suitable part of the system and tell it to build a static liboldX? > > @@ -5608 +5600,0 @@ > > -usr/X11R6/lib/libxrx.so.6.3 > > Another extension no one uses. This is the Netscape Navigator plug in > that lets you render the X server inside a browser window or some lunacy > like that. I'm not sure there's a good reason it shouldn't build on > *BSD versus Linux, but on the other hand there's probably not a good > reason for *anyone* to build it. Hmmm. I'll look into it, but after I do other things, then; tentatively left in place, until I can figure out what is up with it on NetBSD. > > @@ -5752,0 +5745 @@ > > +usr/X11R6/man/man1/kbd_mode.1x > > See above. > > > @@ -5754 +5746,0 @@ > > -usr/X11R6/man/man1/libxrx.1x > > See above. Si. > > @@ -7449 +7441 @@ > > -var/lib/xkb/README > > +var/db/xkb/README > > I gather that *BSD cares not for the FHS. I remember having to persuade > David Dawes to switch Linux back to /var/lib. Apparently the BSDs had > already had enough. True, mostly I just need to find the relevant thing and tweak it, I think. > > DRI support is, of course, not relevant on the NetBSD kernel, and is not > > present (and
Bug#163622: xfree86-common: Error starting X, using Matrox G200
On Die, 2002-10-08 at 18:52, Branden Robinson wrote: > On Mon, Oct 07, 2002 at 08:55:26PM -0400, Ian Bicking wrote: > > Here's the backtrace, tell me if there's anything more you need: > [...] > > #7 0x0807f3c8 in xf86SigHandler (signo=11) at xf86Events.c:1085 > > signo = 11 > > #8 0x4007e518 in sigaction () from /lib/libc.so.6 > > No symbol table info available. > > #9 0x40197cdc in ?? () > > No symbol table info available. > > #10 0x0852b478 in ?? () > > No symbol table info available. > > #11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5, > > argv=0xbdf4) > > at xf86Init.c:528 > > i = 1075228112 > > j = 0 > > k = 1074540038 > > scr_index = 1074540038 > > No symbol table info available. > > Figures. Died in one of the modules, which are invisible to gdb. > > The only way to nail this down is to use the specially-hacked version of > gdb that understand XFree86 server modules. Well, you can call LoaderPrintSymbol for each address with a ??, e.g. call LoaderPrintSymbol(0x40197cdc) Beware that the output goes to the server log only. > Unfortunately, Debian's gdb does not contain this hack. Hopefully, the patch will be cleaned up and applied soon; it would certainly make debugging X much easier. PS: I hope the submitter doesn't get this twice? PPS: Quite some additional traffic on the list... -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163837: startx: hostname version is displayed
On Tue, Oct 08, 2002 at 04:46:40PM -0300, John Lenton wrote: > On Tue, Oct 08, 2002 at 08:57:06PM +0200, Beat Bolli wrote: > > > > When starting X, the hostname version string is displayed. This comes from > > the Xauth setup in startx. The Debian version of hostname outputs its > > version > > string to stderr. The following patch suppresses this error: > > > > --- startx.orig 2002-10-04 22:49:05.0 +0200 > > +++ startx 2002-10-08 20:27:31.0 +0200 > > @@ -116,7 +116,7 @@ > > # set up default Xauth info for this machine > > case `uname` in > > Linux*) > > - if [ -z "`hostname --version | grep GNU`" ]; then > > + if [ -z "`hostname --version 2>/dev/null | grep GNU`" ]; then > > actually no, what happens is that it outputs its version to > STDERR and nothing at all to STDOUT, so the right thing (apart > from fixing hostname, which would be better IMHO) would be to do > > hostname --version 2>&1 | grep GNU > > else stdin will be empty and it'll never grep. Well, the question is if Debian has the GNU hostname command. Since the grep doesn't match, I deduced that I don't have GNU hostname, based on the assumption that the person who coded this knew that GNU hostname would output its version string on stdout... Beat Bolli -- mail: `echo '<[EMAIL PROTECTED]>' | sed -e 's/[A-S]//g'` pgp: 0x506A903A; 49D5 794A EA77 F907 764F D89E 304B 93CF 506A 903A icbm: 47° 02' 43.0" N, 07° 16' 17.5" E (WGS84)
m68k buildd's without 1.5GB of free disk should not attempt xfree86
Hi guys, You admins of buildd's without about a gig and a half of free disk space for autobuilding should set xfree86 to "weak_no_autobuild" or whatever the jargon is that means "don't grab xfree86 off the stack on your own initiative". XFree86 was always huge but now it's huger thanks to the static debugging X server build, and with people snapping at my heels to build XDirectFB and TinyX X servers as well, it's only going to get huger. Sorry, I don't really *mean* do to an impression of vtk or whatever. -- G. Branden Robinson| What influenced me to atheism was Debian GNU/Linux | reading the Bible cover to cover. [EMAIL PROTECTED] | Twice. http://www.deadbeast.net/~branden/ | -- J. Michael Straczynski pgpdWuBSL6fed.pgp Description: PGP signature
Bug#163837: startx: hostname version is displayed
On Tue, Oct 08, 2002 at 08:57:06PM +0200, Beat Bolli wrote: > > When starting X, the hostname version string is displayed. This comes from > the Xauth setup in startx. The Debian version of hostname outputs its version > string to stderr. The following patch suppresses this error: > > --- startx.orig 2002-10-04 22:49:05.0 +0200 > +++ startx2002-10-08 20:27:31.0 +0200 > @@ -116,7 +116,7 @@ > # set up default Xauth info for this machine > case `uname` in > Linux*) > - if [ -z "`hostname --version | grep GNU`" ]; then > + if [ -z "`hostname --version 2>/dev/null | grep GNU`" ]; then actually no, what happens is that it outputs its version to STDERR and nothing at all to STDOUT, so the right thing (apart from fixing hostname, which would be better IMHO) would be to do hostname --version 2>&1 | grep GNU else stdin will be empty and it'll never grep. -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: "How do I love thee? My accumulator overflows."
Re: xfree86 4.2.1 on NetBSD/i386
On Tue, Oct 08, 2002 at 01:33:38PM -0600, Joel Baker wrote:
> The good:
>
> After a bit of banging on things to force the circular dependancy path
> between freetype and xfree86, and cribbing from the patches written for
> 4.1.0, I'm close (very close) to having a set of patches to make xfree86
> compile cleanly on the netbsd-i386 arch.
Cool!
> The bad:
>
> It requires some extensive patching. Some of this (strnlen portability
> in xserver-wrapper.c, etc) has already been filed; the rest is waiting
> on me getting the last bits hammered out. I've tried to make the patches
> something that would be acceptable to upstream, but I have no idea if
> they really will be. The most extensive, unsuprisingly, are to NetBSD.cf,
> and are largely cribbed from linux.cf; however, changes to imake and
> other things also need to happen.
I gather that xc/config/cf/bsdLib.rules is going to be painful as well.
> The ugly:
>
> --- debian/MANIFEST.netbsd-i386 2002-10-08 07:23:56.0 +
> +++ debian/MANIFEST.netbsd-i386.new 2002-10-08 18:50:48.0
> +
> @@ -197 +196,0 @@
> -etc/X11/xkb/symbols/alt
Obsolete. See changelog.
> @@ -353 +351,0 @@
> -usr/X11R6/bin/glxinfo
I can't think of a reason this shouldn't be built. It should be
possible to build the GLX extension, and therefore this client, even
without DRI stuff.
> @@ -356,0 +355 @@
> +usr/X11R6/bin/kbd_mode
I used to see this on Sun machines. You sure it's necessary with modern
BSD kernels?
> @@ -838,2 +836,0 @@
> -usr/X11R6/include/X11/extensions/xf86rush.h
> -usr/X11R6/include/X11/extensions/xf86rushstr.h
Looks okay. This is the never-used Voodoo Rush extension. It builds on
Linux/i386 but I've never heard of anyone using it for anything.
> @@ -5543,2 +5539,0 @@
> -usr/X11R6/lib/libI810XvMC.a
> -usr/X11R6/lib/libI810XvMC_pic.a
This is new to XFree86 4.2. My guess is that it does something to hook
into the (Linux) kernel to speak foul magic to the hardware. XvMC is
Mark Vojkovich's motion compensation interface on top of the XVideo (Xv)
extension. I'll cautiously assume that *BSD shouldn't be building this.
> @@ -5547,2 +5541,0 @@
> -usr/X11R6/lib/libOSMesa.a
> -usr/X11R6/lib/libOSMesa.so.3.3
Nobody who builds DRI builds the offscreen Mesa library. Michel Dänzer
understands better how this stuff works. (I.e., I don't know *why* it's
called the "offscreen" Mesa library, or why 3D-accelerated GL rendering
is considered "off-the-screen". Maybe it means the rendering isn't done
into the framebuffer, a.k.a. "screen"?)
> @@ -5593 +5585,0 @@
> -usr/X11R6/lib/libXxf86rush.a
Voodoo Rush extension; see above.
> @@ -5602,0 +5595 @@
> +usr/X11R6/lib/liboldX.so.6.0
This goes in xlibs-dev.files. Already listed there.
> @@ -5608 +5600,0 @@
> -usr/X11R6/lib/libxrx.so.6.3
Another extension no one uses. This is the Netscape Navigator plug in
that lets you render the X server inside a browser window or some lunacy
like that. I'm not sure there's a good reason it shouldn't build on
*BSD versus Linux, but on the other hand there's probably not a good
reason for *anyone* to build it.
> @@ -5752,0 +5745 @@
> +usr/X11R6/man/man1/kbd_mode.1x
See above.
> @@ -5754 +5746,0 @@
> -usr/X11R6/man/man1/libxrx.1x
See above.
> @@ -7449 +7441 @@
> -var/lib/xkb/README
> +var/db/xkb/README
I gather that *BSD cares not for the FHS. I remember having to persuade
David Dawes to switch Linux back to /var/lib. Apparently the BSDs had
already had enough.
> DRI support is, of course, not relevant on the NetBSD kernel, and is not
> present (and the related files have been removed already); the same goes
> for the video4linux drivers. libGL and company, which didn't compile under
> 4.1.0, now work (I think this is largely because the NetBSD port has
> upgraded to version 1.6 in the meanwhile, and this is a major cleanup of
> the NetBSD base system).
You can build libGL without DRI support. Several Linux architectures do
it.
> I'm assuming that I can find a way to weak the /var/{lib,db}/xkb/README
> location somewhere; I haven't dug into it yet.
The answer to this question depends on which altar at which Debian/*BSD
decides to worship; the FHS, or the other BSDs. Once that decision is
made I'm happy to help you out with it. There's an Imake symbol called
VarDbDirectory, I believe, which reflects the BSD experience of the
XFree86 Core Team. :)
Thanks for working on this!
--
G. Branden Robinson|Men use thought only to justify
Debian GNU/Linux |their wrong doings, and speech only
[EMAIL PROTECTED] |to conceal their thoughts.
http://people.debian.org/~branden/ |-- Voltaire
msg04046/pgp0.pgp
Description: PGP signature
Re: m68k buildd's without 1.5GB of free disk should not attempt xfree86
On Tue, Oct 08, 2002 at 05:00:21PM -0300, John Lenton wrote: > I don't know XDirectFB, but the kdrive servers are probably > better served being compiled against a uclibc (yes they compile > cleanly against the newer uclibcs). Unless the idea is to use > Xvesa as a failsafe X server for intel. Else what's the point? > the libs are bigger than the execs anyway. Noted. Jim Gettys is the one who asked for it so I guess I'll ask his opinion. -- G. Branden Robinson|I'm sorry if the following sounds Debian GNU/Linux |combative and excessively personal, [EMAIL PROTECTED] |but that's my general style. http://people.debian.org/~branden/ |-- Ian Jackson msg04045/pgp0.pgp Description: PGP signature
xfree86 4.2.1 on NetBSD/i386
The good:
After a bit of banging on things to force the circular dependancy path
between freetype and xfree86, and cribbing from the patches written for
4.1.0, I'm close (very close) to having a set of patches to make xfree86
compile cleanly on the netbsd-i386 arch.
The bad:
It requires some extensive patching. Some of this (strnlen portability
in xserver-wrapper.c, etc) has already been filed; the rest is waiting
on me getting the last bits hammered out. I've tried to make the patches
something that would be acceptable to upstream, but I have no idea if
they really will be. The most extensive, unsuprisingly, are to NetBSD.cf,
and are largely cribbed from linux.cf; however, changes to imake and
other things also need to happen.
The ugly:
--- debian/MANIFEST.netbsd-i386 2002-10-08 07:23:56.0 +
+++ debian/MANIFEST.netbsd-i386.new 2002-10-08 18:50:48.0
+
@@ -197 +196,0 @@
-etc/X11/xkb/symbols/alt
@@ -353 +351,0 @@
-usr/X11R6/bin/glxinfo
@@ -356,0 +355 @@
+usr/X11R6/bin/kbd_mode
@@ -838,2 +836,0 @@
-usr/X11R6/include/X11/extensions/xf86rush.h
-usr/X11R6/include/X11/extensions/xf86rushstr.h
@@ -5543,2 +5539,0 @@
-usr/X11R6/lib/libI810XvMC.a
-usr/X11R6/lib/libI810XvMC_pic.a
@@ -5547,2 +5541,0 @@
-usr/X11R6/lib/libOSMesa.a
-usr/X11R6/lib/libOSMesa.so.3.3
@@ -5593 +5585,0 @@
-usr/X11R6/lib/libXxf86rush.a
@@ -5602,0 +5595 @@
+usr/X11R6/lib/liboldX.so.6.0
@@ -5608 +5600,0 @@
-usr/X11R6/lib/libxrx.so.6.3
@@ -5752,0 +5745 @@
+usr/X11R6/man/man1/kbd_mode.1x
@@ -5754 +5746,0 @@
-usr/X11R6/man/man1/libxrx.1x
@@ -7449 +7441 @@
-var/lib/xkb/README
+var/db/xkb/README
MANIFEST check failed; please see debian/README
DRI support is, of course, not relevant on the NetBSD kernel, and is not
present (and the related files have been removed already); the same goes
for the video4linux drivers. libGL and company, which didn't compile under
4.1.0, now work (I think this is largely because the NetBSD port has
upgraded to version 1.6 in the meanwhile, and this is a major cleanup of
the NetBSD base system).
I have not yet looked into glxinfo to find out why it isn't building,
but it's on my list. I would appreciate hints on the following, though,
and whether I should expect them to build on NetBSD or remove them from
the MANIFEST:
* /etc/X11/xkb/symbols/alt (err...)
* kdb_mode (this used to be there, and was removed from most ports,
according to the old changelog?)
* xf86rush
* I810XvMC (Intel 810 board support?)
* OSMesa (OS-specific MESA libraries?)
* liboldX
* libxrx
I'm assuming that I can find a way to weak the /var/{lib,db}/xkb/README
location somewhere; I haven't dug into it yet.
--
***
Joel Baker System Administrator - lightbearer.com
[EMAIL PROTECTED] http://users.lightbearer.com/lucifer/
pgpwUje5QCnny.pgp
Description: PGP signature
Re: Xvideo extension, radeon mobility Xfree 4.2.1
On Die, 2002-10-08 at 22:35, Matija Grabnar wrote: > I was looking forward to this version of Xfree because it is supposed > to support the more advanced features of my laptop's Radeon Mobility > card. > > Specificaly, I want/need hardware scaling for video. > > I would like to emphasize here that I'm probably overlooking something > stupid. This is an appeal for help, not a bug report. > I'm running Debian Sid, obviously. > > I can see in the xfree log that the Xvideo extension gets loaded, but > it's not visible to xvinfo or to mplayer -vo xv. > > I am hoping this means I overlooked some setting, configuration file > or some other obvious thing I should change in my setting and not > some deficiency in the support for Radeon mobility. The vesa driver doesn't support the XVideo extension, you need the ati driver. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163815: colour issues with 4.2.1
well at a guess it seems to be a trident 9397 only problem so far. I have a laptop with the *same* graphics card (Trident Cyber 9397) and get the same problem, however when I cold reboot, yes it sorts out the problem however the gamma is up for some reason and it looks like I am peering through a fog at my laptop screenits usable but a real pain Before I cold rebooted I spent time rebuilding my XF86Config-4 file but had no luck. I use 'wdm' to fire up X however this is not the source of the problem as if I fire up X on its own (via 'startx') I get the same problem... In every detail you described your problem, seems to be the same as mine... any ideas Alex -- ___ < A day without sunshine is like night. > --- \ ^__^ \ (oo)\___ (__)\ )\/\ ||w | || || XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 20:09:58 2002 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Laptop LCD 800x600" (**) | |-->Device "Trident Cyber 9397" (**) |-->Input Device "Synaptics Touchpad" (**) |-->Input Device "Laptop Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "gb" (**) XKB: layout: "gb" (**) Option "XkbOptions" "altwin:left_meta_win,compose:ralt" (**) XKB: options: "altwin:left_meta_win,compose:ralt" (==) Keyboard: CustomKeycode disabled (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist. Entry deleted from font path. (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (++) using VT number 5 (WW) Open APM failed (/dev/apm_bios) (No such device) (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 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7192 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 1023,9397 card 0002,e320 rev f3 class 03,00,00 hdr 00 (II) PCI: 00:03:0: chip 1217,6836 card 0001, rev 62 class 06,07,00 hdr 82 (II) PCI: 00:03:1: chip 1217,6836 card 0001, rev 62 class 06,07,00 hdr 82 (II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 02 class 06,80,00 hdr 00 (II) PCI: 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) 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 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x
Re: Xvideo extension, radeon mobility Xfree 4.2.1
On Tue, 08 Oct 2002, Matija Grabnar wrote: > I was looking forward to this version of Xfree because it is supposed > to support the more advanced features of my laptop's Radeon Mobility > card. It looks like you're using the 'vesa' driver: > (--) Chipset vesa found You should switch to the ATI Radeon driver (manually or using the dpkg-reconfigure xserver-xfree86 command). Martijn -- And Billy Joel? He hasn't had a hit since Usenet started. - The Internet Oracle -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163837: startx: hostname version is displayed
Package: xbase-clients Version: 4.2.1-1 Severity: minor Tags: sid patch When starting X, the hostname version string is displayed. This comes from the Xauth setup in startx. The Debian version of hostname outputs its version string to stderr. The following patch suppresses this error: --- startx.orig 2002-10-04 22:49:05.0 +0200 +++ startx 2002-10-08 20:27:31.0 +0200 @@ -116,7 +116,7 @@ # set up default Xauth info for this machine case `uname` in Linux*) - if [ -z "`hostname --version | grep GNU`" ]; then + if [ -z "`hostname --version 2>/dev/null | grep GNU`" ]; then hostname=`hostname -f` else hostname=`hostname` -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux gw.bolli.homeip.net 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002 i586 Locale: LANG=C, LC_CTYPE=C Versions of packages xbase-clients depends on: ii cpp 2:2.95.4-17 The GNU C preprocessor. ii debconf 1.2.10 Debian configuration management sy ii libc62.2.5-15GNU C Library: Shared libraries an ii libdps1 4.2.1-1 Display PostScript (DPS) client li ii libfreetype6 2.1.2-7 FreeType 2 font engine, shared lib ii libncurses5 5.2.20020112a-8 Shared libraries for terminal hand ii libxaw7 4.2.1-1 X Athena widget set library ii xlibmesa3 [libgl1] 4.2.1-1 XFree86 version of Mesa 3D graphic ii xlibs4.2.1-1 X Window System client libraries -- debconf information: * xbase-clients/default_100dpi: * xbase-clients/default_nolisten_tcp:
Re: m68k buildd's without 1.5GB of free disk should not attempt xfree86
On Tue, Oct 08, 2002 at 02:49:53PM -0500, Branden Robinson wrote: > > XFree86 was always huge but now it's huger thanks to the static > debugging X server build, and with people snapping at my heels to build > XDirectFB and TinyX X servers as well, it's only going to get huger. I don't know XDirectFB, but the kdrive servers are probably better served being compiled against a uclibc (yes they compile cleanly against the newer uclibcs). Unless the idea is to use Xvesa as a failsafe X server for intel. Else what's the point? the libs are bigger than the execs anyway. -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: People who make no mistakes do not usually make anything. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163815: reportbug not attaching your XFree86 log files?
Hi guys, You gentlemen both reported bugs against xserver-xfree86 recently, but neglected to include your XFree86.0.log files as requested by XF86Config(7). I was about to flame you for setting a bad precedent, but the thought occurred that this may not have been a deliberate act of provocation on you guys' part. :) I notice that you're both using reportbug 2.2. I didn't get/haven't yet gotten any bug reports filed by reportbug 2.1, but I notice that reports filed with 2.0 *did* include people's log files. I do not think this is a coincidence, and the fact that these two bugs from different people had exactly same the context excised in exactly the same way leads me to believe that this is reportbug's fault. So I have a couple of requests: 1) Can you guys send your bug numbers your /var/log/XFree86.0.log files if you haven't already? 2) Can the reportbug maintainer look into this? I don't yet have enough data for a bug report. I don't know what would cause parts of xserver-xfree86's "bug" script to work, and other parts to fail. Here's what it looks like: #!/bin/sh PATH=/sbin:$PATH if command -v lspci > /dev/null 2>&1; then LC_ALL=C lspci | grep 'VGA compatible controller:' >&3 LC_ALL=C lspci -n | grep 'Class 0300:' >&3 printf "\n" >&3 fi if [ -e /etc/X11/XF86Config-4 ]; then cat /etc/X11/XF86Config-4 >&3 printf "\n" >&3 fi if [ -e /var/log/XFree86.0.log ]; then cat /var/log/XFree86.0.log >&3 printf "\n" >&3 fi ls -d -l /var/log/XFree86.*.log >&3 2> /dev/null -- G. Branden Robinson| I suspect Linus wrote that in a Debian GNU/Linux | complicated way only to be able to [EMAIL PROTECTED] | have that comment in there. http://people.debian.org/~branden/ | -- Lars Wirzenius msg04041/pgp0.pgp Description: PGP signature
Xvideo extension, radeon mobility Xfree 4.2.1
I was looking forward to this version of Xfree because it is supposed to support the more advanced features of my laptop's Radeon Mobility card. Specificaly, I want/need hardware scaling for video. I would like to emphasize here that I'm probably overlooking something stupid. This is an appeal for help, not a bug report. I'm running Debian Sid, obviously. I can see in the xfree log that the Xvideo extension gets loaded, but it's not visible to xvinfo or to mplayer -vo xv. I am hoping this means I overlooked some setting, configuration file or some other obvious thing I should change in my setting and not some deficiency in the support for Radeon mobility. xvinfo: xvinfo X-Video Extension version 2.2 screen #0 no adaptors present xdpyinfo: name of display::0.0 version number:11.0 vendor string:The XFree86 Project, Inc vendor release number:40201000 XFree86 version: 4.2.1 maximum request size: 4194300 bytes motion buffer size: 256 bitmap unit, bit order, padding:32, LSBFirst, 32 image byte order:LSBFirst number of supported pixmap formats:7 supported pixmap formats: depth 1, bits_per_pixel 1, scanline_pad 32 depth 4, bits_per_pixel 8, scanline_pad 32 depth 8, bits_per_pixel 8, scanline_pad 32 depth 15, bits_per_pixel 16, scanline_pad 32 depth 16, bits_per_pixel 16, scanline_pad 32 depth 24, bits_per_pixel 32, scanline_pad 32 depth 32, bits_per_pixel 32, scanline_pad 32 keycode range:minimum 8, maximum 255 focus: window 0x12a, revert to Parent number of extensions:27 BIG-REQUESTS DOUBLE-BUFFER DPMS Extended-Visual-Information FontCache GLX LBX MIT-SCREEN-SAVER MIT-SHM MIT-SUNDRY-NONSTANDARD RECORD RENDER SECURITY SGI-GLX SHAPE SYNC TOG-CUP XC-APPGROUP XC-MISC XFree86-Bigfont XFree86-DGA XFree86-Misc XFree86-VidModeExtension XInputExtension XKEYBOARD XTEST XVideo default screen number:0 number of screens:1 screen #0: dimensions:1400x1050 pixels (356x267 millimeters) resolution:100x100 dots per inch depths (7):16, 1, 4, 8, 15, 24, 32 root window id:0x36 depth of root window:16 planes number of colormaps:minimum 1, maximum 1 default colormap:0x20 default number of colormap cells:64 preallocated pixels:black 0, white 65535 options:backing-store NO, save-unders NO largest cursor:1400x1050 current input event mask:0xf87f3f KeyPressMask KeyReleaseMask ButtonPressMask ButtonReleaseMaskEnterWindowMask LeaveWindowMask Button1MotionMaskButton2MotionMaskButton3MotionMask Button4MotionMaskButton5MotionMaskButtonMotionMask KeymapStateMask SubstructureNotifyMask SubstructureRedirectMask FocusChangeMask PropertyChangeMask ColormapChangeMask number of visuals:2 default visual id: 0x22 visual: visual id:0x22 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits visual: visual id:0x23 class:TrueColor depth:16 planes available colormap entries:64 per subfield red, green, blue masks:0xf800, 0x7e0, 0x1f significant bits in color specification:6 bits cat /var/log/XFree86.0.log XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 19:56:55 2002 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "Default Layout" (**) |-->Screen "StandAlone" (0) (**) | |-->Monitor "LaptopLCD" (**) | |-->Device "Vesa" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc101" (**) XKB: model: "pc101" (**) Option "XkbLayout" "us" (**) XKB: layout: "us" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Configured Mouse" (**) |-->Input Device "Generic Mouse" (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fo
Bug#163837: startx: hostname version is displayed
On Tue, Oct 08, 2002 at 04:46:40PM -0300, John Lenton wrote: > On Tue, Oct 08, 2002 at 08:57:06PM +0200, Beat Bolli wrote: > > > > When starting X, the hostname version string is displayed. This comes from > > the Xauth setup in startx. The Debian version of hostname outputs its version > > string to stderr. The following patch suppresses this error: > > > > --- startx.orig 2002-10-04 22:49:05.0 +0200 > > +++ startx 2002-10-08 20:27:31.0 +0200 > > @@ -116,7 +116,7 @@ > > # set up default Xauth info for this machine > > case `uname` in > > Linux*) > > - if [ -z "`hostname --version | grep GNU`" ]; then > > + if [ -z "`hostname --version 2>/dev/null | grep GNU`" ]; then > > actually no, what happens is that it outputs its version to > STDERR and nothing at all to STDOUT, so the right thing (apart > from fixing hostname, which would be better IMHO) would be to do > > hostname --version 2>&1 | grep GNU > > else stdin will be empty and it'll never grep. Well, the question is if Debian has the GNU hostname command. Since the grep doesn't match, I deduced that I don't have GNU hostname, based on the assumption that the person who coded this knew that GNU hostname would output its version string on stdout... Beat Bolli -- mail: `echo '<[EMAIL PROTECTED]>' | sed -e 's/[A-S]//g'` pgp: 0x506A903A; 49D5 794A EA77 F907 764F D89E 304B 93CF 506A 903A icbm: 47° 02' 43.0" N, 07° 16' 17.5" E (WGS84) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163799: xlibs: [xkb] bogus mapping in us_intl
retitle 163799 xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" on alternate group severity 163799 minor tag 163799 + moreinfo upstream thanks On Tue, Oct 08, 2002 at 04:03:56PM +0200, Ivan Kanis wrote: > When switching group the key 6 prints "^" instead of 6. Clearly a typo. I disagree that it's a typo. The intent of the us_intl symbols file appears to be making alternate keysyms available when the group is toggled. To make the change you request would be inconsistent with the rest of the definitions in the symbols file. However, I'll admit that I know little about the actual intentions of the us_intl symbols file, its relationship to ISO 9995-3, and so forth. I'm leaving this bug open until I get more information. Also setting severity to minor since the current behavior doesn't prevent you from doing anything. -- G. Branden Robinson|The best place to hide something is Debian GNU/Linux |in documentation. [EMAIL PROTECTED] |-- Ethan Benson http://people.debian.org/~branden/ | pgp4E6Yth7M0S.pgp Description: PGP signature
Processed: Re: Bug#163799: xlibs: [xkb] bogus mapping in us_intl
Processing commands for [EMAIL PROTECTED]: > retitle 163799 xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" > on alternate group Bug#163799: xlibs: [xkb] bogus mapping in us_intl Changed Bug title. > severity 163799 minor Bug#163799: xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" on alternate group Severity set to `minor'. > tag 163799 + moreinfo upstream Bug#163799: xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" on alternate group Tags added: moreinfo, upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
m68k buildd's without 1.5GB of free disk should not attempt xfree86
Hi guys, You admins of buildd's without about a gig and a half of free disk space for autobuilding should set xfree86 to "weak_no_autobuild" or whatever the jargon is that means "don't grab xfree86 off the stack on your own initiative". XFree86 was always huge but now it's huger thanks to the static debugging X server build, and with people snapping at my heels to build XDirectFB and TinyX X servers as well, it's only going to get huger. Sorry, I don't really *mean* do to an impression of vtk or whatever. -- G. Branden Robinson| What influenced me to atheism was Debian GNU/Linux | reading the Bible cover to cover. [EMAIL PROTECTED] | Twice. http://www.deadbeast.net/~branden/ | -- J. Michael Straczynski msg04038/pgp0.pgp Description: PGP signature
Bug#163837: startx: hostname version is displayed
On Tue, Oct 08, 2002 at 08:57:06PM +0200, Beat Bolli wrote: > > When starting X, the hostname version string is displayed. This comes from > the Xauth setup in startx. The Debian version of hostname outputs its version > string to stderr. The following patch suppresses this error: > > --- startx.orig 2002-10-04 22:49:05.0 +0200 > +++ startx2002-10-08 20:27:31.0 +0200 > @@ -116,7 +116,7 @@ > # set up default Xauth info for this machine > case `uname` in > Linux*) > - if [ -z "`hostname --version | grep GNU`" ]; then > + if [ -z "`hostname --version 2>/dev/null | grep GNU`" ]; then actually no, what happens is that it outputs its version to STDERR and nothing at all to STDOUT, so the right thing (apart from fixing hostname, which would be better IMHO) would be to do hostname --version 2>&1 | grep GNU else stdin will be empty and it'll never grep. -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: "How do I love thee? My accumulator overflows." -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree86 -configure failure
On Tue, Oct 08, 2002 at 11:23:08AM +0200, Mikael Andersson wrote: > I'm not sure if I should report this her, or to the upstream, but in the > of the output the debian-x maillinglist was mentioned. > > I run XFree86 -configure and got this > > 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. You should use "dpkg-reconfigure xserver-xfree86" to configure the XFree86 X server on Debian. The "discover" package can help you determine what X server and driver is appropriate for your card. # apt-get install discover discover-data -- G. Branden Robinson| Never attribute to malice that Debian GNU/Linux | which can be adequately explained [EMAIL PROTECTED] | by stupidity. http://people.debian.org/~branden/ | pgp8QpbzbSa0I.pgp Description: PGP signature
Re: Lots of problems with Debian unstable on Matrox G200
Simon Hepburn wrote: > Would that be the mga_drv.o that came with X 4.2.1 or the one that came in > the matrox tarball ? I think you need the matrox version to use > mga_hal_drv.o. Did you copy back the matrox mga_drv.o after you upgraded X I should have thought some more...from your log file: (II) Loading /usr/X11R6/lib/modules/drivers/mga_hal_drv.o (II) Module mga_hal: vendor="The XFree86 Project" compiled for 4.0.3, module version = 1.0.0 You are trying to use a module compiled for X4.0.3. In the latest matrox tarball you will find a dir containing modules compiled for X4.2. The mga_drv_hal.o in that dir works fine with either version of mga_drv.o. At least that's my experience with a G450. YMMV. -- Simon Hepburn.
xfree86 4.2.1 on NetBSD/i386
The good:
After a bit of banging on things to force the circular dependancy path
between freetype and xfree86, and cribbing from the patches written for
4.1.0, I'm close (very close) to having a set of patches to make xfree86
compile cleanly on the netbsd-i386 arch.
The bad:
It requires some extensive patching. Some of this (strnlen portability
in xserver-wrapper.c, etc) has already been filed; the rest is waiting
on me getting the last bits hammered out. I've tried to make the patches
something that would be acceptable to upstream, but I have no idea if
they really will be. The most extensive, unsuprisingly, are to NetBSD.cf,
and are largely cribbed from linux.cf; however, changes to imake and
other things also need to happen.
The ugly:
--- debian/MANIFEST.netbsd-i386 2002-10-08 07:23:56.0 +
+++ debian/MANIFEST.netbsd-i386.new 2002-10-08 18:50:48.0
+
@@ -197 +196,0 @@
-etc/X11/xkb/symbols/alt
@@ -353 +351,0 @@
-usr/X11R6/bin/glxinfo
@@ -356,0 +355 @@
+usr/X11R6/bin/kbd_mode
@@ -838,2 +836,0 @@
-usr/X11R6/include/X11/extensions/xf86rush.h
-usr/X11R6/include/X11/extensions/xf86rushstr.h
@@ -5543,2 +5539,0 @@
-usr/X11R6/lib/libI810XvMC.a
-usr/X11R6/lib/libI810XvMC_pic.a
@@ -5547,2 +5541,0 @@
-usr/X11R6/lib/libOSMesa.a
-usr/X11R6/lib/libOSMesa.so.3.3
@@ -5593 +5585,0 @@
-usr/X11R6/lib/libXxf86rush.a
@@ -5602,0 +5595 @@
+usr/X11R6/lib/liboldX.so.6.0
@@ -5608 +5600,0 @@
-usr/X11R6/lib/libxrx.so.6.3
@@ -5752,0 +5745 @@
+usr/X11R6/man/man1/kbd_mode.1x
@@ -5754 +5746,0 @@
-usr/X11R6/man/man1/libxrx.1x
@@ -7449 +7441 @@
-var/lib/xkb/README
+var/db/xkb/README
MANIFEST check failed; please see debian/README
DRI support is, of course, not relevant on the NetBSD kernel, and is not
present (and the related files have been removed already); the same goes
for the video4linux drivers. libGL and company, which didn't compile under
4.1.0, now work (I think this is largely because the NetBSD port has
upgraded to version 1.6 in the meanwhile, and this is a major cleanup of
the NetBSD base system).
I have not yet looked into glxinfo to find out why it isn't building,
but it's on my list. I would appreciate hints on the following, though,
and whether I should expect them to build on NetBSD or remove them from
the MANIFEST:
* /etc/X11/xkb/symbols/alt (err...)
* kdb_mode (this used to be there, and was removed from most ports,
according to the old changelog?)
* xf86rush
* I810XvMC (Intel 810 board support?)
* OSMesa (OS-specific MESA libraries?)
* liboldX
* libxrx
I'm assuming that I can find a way to weak the /var/{lib,db}/xkb/README
location somewhere; I haven't dug into it yet.
--
***
Joel Baker System Administrator - lightbearer.com
[EMAIL PROTECTED] http://users.lightbearer.com/lucifer/
msg04036/pgp0.pgp
Description: PGP signature
Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
# no crash, no coredump, no hang, no spontaneous reboot severity 163807 normal retitle 163807 xserver-xfree86: [fbdev] color depth disagreements with kernel tag 163807 + moreinfo thanks On Tue, Oct 08, 2002 at 11:41:48AM -0400, Matt Filizzi wrote: > After upgrading to 4.2.1 and typing startx, it would fail and give me an > error that the screen color depth is incorrect (24) after setting to 16 > it works, however everything becomes a green tint. This is able to be > fixed by removing the fbdev setings (and recompiling the kernel to not > use fbdev). You did not supply your XFree86.0.log file; this information is needed for proper analysis of your bug report. See, e.g., XF86Config(7). -- G. Branden Robinson| Organized religion is a sham and a Debian GNU/Linux | crutch for weak-minded people who [EMAIL PROTECTED] | need strength in numbers. http://people.debian.org/~branden/ | -- Jesse Ventura pgpaaXsjjhGBn.pgp Description: PGP signature
Bug#163622: xfree86-common: Error starting X, using Matrox G200
On Mon, Oct 07, 2002 at 08:55:26PM -0400, Ian Bicking wrote: > Here's the backtrace, tell me if there's anything more you need: [...] > #7 0x0807f3c8 in xf86SigHandler (signo=11) at xf86Events.c:1085 > signo = 11 > #8 0x4007e518 in sigaction () from /lib/libc.so.6 > No symbol table info available. > #9 0x40197cdc in ?? () > No symbol table info available. > #10 0x0852b478 in ?? () > No symbol table info available. > #11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5, > argv=0xbdf4) > at xf86Init.c:528 > i = 1075228112 > j = 0 > k = 1074540038 > scr_index = 1074540038 > No symbol table info available. Figures. Died in one of the modules, which are invisible to gdb. The only way to nail this down is to use the specially-hacked version of gdb that understand XFree86 server modules. Unfortunately, Debian's gdb does not contain this hack. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=119028&repeatmerged=yes Maybe someone on the debian-x list has a xfree86-gdb binary that you can use. -- G. Branden Robinson|A committee is a life form with six Debian GNU/Linux |or more legs and no brain. [EMAIL PROTECTED] |-- Robert Heinlein http://people.debian.org/~branden/ | pgp0xTCY2BXfP.pgp Description: PGP signature
Processed: Re: Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
Processing commands for [EMAIL PROTECTED]: > severity 163807 normal Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth Severity set to `normal'. > retitle 163807 xserver-xfree86: [fbdev] color depth disagreements with kernel Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth Changed Bug title. > tag 163807 + moreinfo Bug#163807: xserver-xfree86: [fbdev] color depth disagreements with kernel Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#163815: colour issues with 4.2.1
well at a guess it seems to be a trident 9397 only problem so far. I have a laptop with the *same* graphics card (Trident Cyber 9397) and get the same problem, however when I cold reboot, yes it sorts out the problem however the gamma is up for some reason and it looks like I am peering through a fog at my laptop screenits usable but a real pain Before I cold rebooted I spent time rebuilding my XF86Config-4 file but had no luck. I use 'wdm' to fire up X however this is not the source of the problem as if I fire up X on its own (via 'startx') I get the same problem... In every detail you described your problem, seems to be the same as mine... any ideas Alex -- ___ < A day without sunshine is like night. > --- \ ^__^ \ (oo)\___ (__)\ )\/\ ||w | || || XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 20:09:58 2002 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "XFree86 Configured" (**) |-->Screen "Screen0" (0) (**) | |-->Monitor "Laptop LCD 800x600" (**) | |-->Device "Trident Cyber 9397" (**) |-->Input Device "Synaptics Touchpad" (**) |-->Input Device "Laptop Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "gb" (**) XKB: layout: "gb" (**) Option "XkbOptions" "altwin:left_meta_win,compose:ralt" (**) XKB: options: "altwin:left_meta_win,compose:ralt" (==) Keyboard: CustomKeycode disabled (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist. Entry deleted from font path. (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist. Entry deleted from font path. (**) FontPath set to "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/Speedo/,/usr/X11R6/lib/X11/fonts/Type1/,/usr/X11R6/lib/X11/fonts/75dpi/" (**) RgbPath set to "/usr/X11R6/lib/X11/rgb" (**) ModulePath set to "/usr/X11R6/lib/modules" (++) using VT number 5 (WW) Open APM failed (/dev/apm_bios) (No such device) (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 = 0x, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7192 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:02:0: chip 1023,9397 card 0002,e320 rev f3 class 03,00,00 hdr 00 (II) PCI: 00:03:0: chip 1217,6836 card 0001, rev 62 class 06,07,00 hdr 82 (II) PCI: 00:03:1: chip 1217,6836 card 0001, rev 62 class 06,07,00 hdr 82 (II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 02 class 06,80,00 hdr 00 (II) PCI: 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) 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 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x00
Bug#163815: xserver-xfree86: [trident cyber9397] colour palette screwed up, requiring power off
Package: xserver-xfree86 Version: 4.2.1-1 Severity: important Tags: sid On starting XFree86 4.2.1, the video palette in all depths (8/15/16/24) is screwed up. It appears that the colours are being mapped to the VGA palette, in that only 16 colours are available, and they are repeated through the rest of the palette. This condition persists, even if you reboot to Windows 98SE, or revert to 4.1.0-17, and is only fixed by a complete hard reset. The hardware is an IBM Thinkpad 770 (type 9548) laptop. -- Package-specific info: 00:03.0 VGA compatible controller: Trident Microsystems Cyber 9397 (rev f3) 00:03.0 Class 0300: 1023:9397 (rev f3) Section "Files" FontPath"unix/:7100"# local font server FontPath"unix/:7101"# xfs-xtt server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/defoma/CID" FontPath"/usr/X11R6/lib/X11/fonts/defoma/TrueType" FontPath"/usr/local/lib/X11/fonts/truetype" EndSection ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc101" Option "XkbLayout" "intl" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/gpmdata" Option "Protocol" "PS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Cyber 9397" Driver "trident" EndSection Section "Monitor" Identifier "LCD Screen" HorizSync 28-49 VertRefresh 43-72 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Cyber 9397" Monitor "LCD Screen" DefaultDepth16 SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Section "DRI" Mode0666 EndSection ### END DEBCONF SECTION -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux manlap 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002 i586 Locale: LANG=en_GB, LC_CTYPE=en_GB Ver
Bug#163837: startx: hostname version is displayed
Package: xbase-clients Version: 4.2.1-1 Severity: minor Tags: sid patch When starting X, the hostname version string is displayed. This comes from the Xauth setup in startx. The Debian version of hostname outputs its version string to stderr. The following patch suppresses this error: --- startx.orig 2002-10-04 22:49:05.0 +0200 +++ startx 2002-10-08 20:27:31.0 +0200 @@ -116,7 +116,7 @@ # set up default Xauth info for this machine case `uname` in Linux*) - if [ -z "`hostname --version | grep GNU`" ]; then + if [ -z "`hostname --version 2>/dev/null | grep GNU`" ]; then hostname=`hostname -f` else hostname=`hostname` -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux gw.bolli.homeip.net 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002 i586 Locale: LANG=C, LC_CTYPE=C Versions of packages xbase-clients depends on: ii cpp 2:2.95.4-17 The GNU C preprocessor. ii debconf 1.2.10 Debian configuration management sy ii libc62.2.5-15GNU C Library: Shared libraries an ii libdps1 4.2.1-1 Display PostScript (DPS) client li ii libfreetype6 2.1.2-7 FreeType 2 font engine, shared lib ii libncurses5 5.2.20020112a-8 Shared libraries for terminal hand ii libxaw7 4.2.1-1 X Athena widget set library ii xlibmesa3 [libgl1] 4.2.1-1 XFree86 version of Mesa 3D graphic ii xlibs4.2.1-1 X Window System client libraries -- debconf information: * xbase-clients/default_100dpi: * xbase-clients/default_nolisten_tcp: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Accepted xfree86 4.2.1-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 7 Oct 2002 22:38:45 -0500 Source: xfree86 Binary: xserver-common libxaw7-dbg xbase-clients twm xlibmesa3-dbg xfonts-scalable xfonts-75dpi libdps1-dbg xlib6g-dev xmh libxaw6-dbg xfwp xlibs xlibosmesa3-dbg libdps-dev xserver-xfree86-dbg xlibmesa-dev xserver-xfree86 libdps1 proxymngr xfonts-base-transcoded libxaw6-dev lbxproxy xfonts-cyrillic x-window-system-core xlib6g xutils xspecs xlibs-pic x-window-system xfree86-common xfs xfonts-base xlibmesa3 xlibs-dbg libxaw7-dev xnest xfonts-100dpi-transcoded libxaw6 xfonts-100dpi xterm xfonts-75dpi-transcoded xprt xlibosmesa-dev xvfb libxaw7 xlibosmesa3 xdm xlibs-dev Architecture: source i386 all Version: 4.2.1-2 Distribution: unstable Urgency: low Maintainer: Branden Robinson <[EMAIL PROTECTED]> Changed-By: Branden Robinson <[EMAIL PROTECTED]> Description: lbxproxy - Low Bandwidth X (LBX) proxy server libdps-dev - Display PostScript (DPS) client library development files libdps1- Display PostScript (DPS) client library libdps1-dbg - Display PostScript (DPS) client library (unstripped) libxaw6- X Athena widget set library (version 6) libxaw6-dbg - X Athena widget set library (version 6) (unstripped) libxaw6-dev - X Athena widget set library development files (version 6) libxaw7- X Athena widget set library libxaw7-dbg - X Athena widget set library (unstripped) libxaw7-dev - X Athena widget set library development files proxymngr - X proxy services manager twm- Tab window manager x-window-system - X Window System x-window-system-core - X Window System core components xbase-clients - miscellaneous X clients xdm- X display manager xfonts-100dpi - 100 dpi fonts for X xfonts-100dpi-transcoded - 100 dpi fonts for X (transcoded from ISO 10646-1) xfonts-75dpi - 75 dpi fonts for X xfonts-75dpi-transcoded - 75 dpi fonts for X (transcoded from ISO 10646-1) xfonts-base - standard fonts for X xfonts-base-transcoded - standard fonts for X (transcoded from ISO 10646-1) xfonts-cyrillic - Cyrillic fonts for X xfonts-scalable - scalable fonts for X xfree86-common - X Window System (XFree86) infrastructure xfs- X font server xfwp - X firewall proxy server xlib6g - pseudopackage providing X libraries xlib6g-dev - pseudopackage providing X library development files xlibmesa-dev - XFree86 version of Mesa 3D graphics library development files xlibmesa3 - XFree86 version of Mesa 3D graphics library xlibmesa3-dbg - XFree86 version of Mesa 3D graphics library (unstripped) xlibosmesa-dev - Mesa/XFree86 off-screen rendering library development files xlibosmesa3 - Mesa/XFree86 off-screen rendering library xlibosmesa3-dbg - Mesa/XFree86 off-screen rendering library (unstripped) xlibs - X Window System client libraries xlibs-dbg - X Window System client libraries (unstripped) xlibs-dev - X Window System client library development files xlibs-pic - X Window System client extension library PIC archives xmh- X interface to the MH mail system xnest - nested X server xprt - X print server xserver-common - files and utilities common to all X servers xserver-xfree86 - the XFree86 X server xserver-xfree86-dbg - the XFree86 X server (static version with debugging symbols) xspecs - X protocol, extension, and library technical specifications xterm - X terminal emulator xutils - X Window System utility programs xvfb - virtual framebuffer X server Closes: 163359 163522 Changes: xfree86 (4.2.1-2) unstable; urgency=low . * patch #000_post421: resynced with xf-4_2-branch as of 2002-10-06 + Xdm patches: realloc usage, zero malloc()ated memory, enable /dev/urandom on NetBSD 1.4 and later (#5345, Mike A. Harris, #5401, Matthias Scheler) (Matthieu Herrb) + Fix crash in the TextWidget reported by Hans Wilmer. The bug is fixed in the TextAction.c patch (actually it was fixed in head, but I forgot to update the 4.2 branch, that is what most people are using). Also synced some other bug fixes only in CVS head. (Paulo Cesar Pereira de Andrade) . * patch #002: resynced with xf-4_2-branch updates * patch #024: new; fix for hangs upon VT switch back to XFree86 on Rage128 and Radeon cards due to failure to set and reset PCI busmastering properly (thanks, Michel Dänzer) (Closes: #163359) * patch #026: new; patch from Steven Davies to implement double-buffering support for the XVideo extension in the tdfx driver; he wanted testers, so I'm sticking this code in to test it. Welcome to Debian unstable! . * debian/control: - update versioned Replaces in xdm to not reference a version of xbase-clients that only existed when woody was unstable - update xbase-clients's extended description to mention xf86cfg, xf86config, xrandr, xtrapchar, xtrapin, xtrapinfo, xtrapout, xtrapproto, xtrapreset, and
Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
Package: xserver-xfree86 Version: 4.2.1-1 Severity: important Tags: sid After upgrading to 4.2.1 and typing startx, it would fail and give me an error that the screen color depth is incorrect (24) after setting to 16 it works, however everything becomes a green tint. This is able to be fixed by removing the fbdev setings (and recompiling the kernel to not use fbdev). -- Package-specific info: ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" # Option "Device""/dev/input/mice" Option "Device""/dev/gpmdata" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Generic Video Card" Driver "fbdev" VideoRam8192 Option "UseFBDev" "true" EndSection Section "Monitor" Identifier "Generic Monitor" HorizSync 30-100 VertRefresh 50-160 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Depth 1 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Section "DRI" Mode0666 EndSection ### END DEBCONF SECTION --w---1 root root52324 Oct 7 22:35 /var/log/XFree86.0.log --w---1 root root51522 Aug 5 21:53 /var/log/XFree86.8.log -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux beyond.hjsoft.com 2.4.20-pre7 #2 Mon Oct 7 18:17:52 EDT 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf 1.2.10 Debian configuration manage
Bug#163799: xlibs: [xkb] bogus mapping in us_intl
retitle 163799 xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" on alternate group severity 163799 minor tag 163799 + moreinfo upstream thanks On Tue, Oct 08, 2002 at 04:03:56PM +0200, Ivan Kanis wrote: > When switching group the key 6 prints "^" instead of 6. Clearly a typo. I disagree that it's a typo. The intent of the us_intl symbols file appears to be making alternate keysyms available when the group is toggled. To make the change you request would be inconsistent with the rest of the definitions in the symbols file. However, I'll admit that I know little about the actual intentions of the us_intl symbols file, its relationship to ISO 9995-3, and so forth. I'm leaving this bug open until I get more information. Also setting severity to minor since the current behavior doesn't prevent you from doing anything. -- G. Branden Robinson|The best place to hide something is Debian GNU/Linux |in documentation. [EMAIL PROTECTED] |-- Ethan Benson http://people.debian.org/~branden/ | msg04033/pgp0.pgp Description: PGP signature
Processed: Re: Bug#163799: xlibs: [xkb] bogus mapping in us_intl
Processing commands for [EMAIL PROTECTED]: > retitle 163799 xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" on >alternate group Bug#163799: xlibs: [xkb] bogus mapping in us_intl Changed Bug title. > severity 163799 minor Bug#163799: xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" on alternate group Severity set to `minor'. > tag 163799 + moreinfo upstream Bug#163799: xlibs: [xkb] us_intl maps AE06 to "asciicircum" instead of "6" on alternate group Tags added: moreinfo, upstream > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XFree86 -configure failure
On Tue, Oct 08, 2002 at 11:23:08AM +0200, Mikael Andersson wrote: > I'm not sure if I should report this her, or to the upstream, but in the > of the output the debian-x maillinglist was mentioned. > > I run XFree86 -configure and got this > > 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. You should use "dpkg-reconfigure xserver-xfree86" to configure the XFree86 X server on Debian. The "discover" package can help you determine what X server and driver is appropriate for your card. # apt-get install discover discover-data -- G. Branden Robinson| Never attribute to malice that Debian GNU/Linux | which can be adequately explained [EMAIL PROTECTED] | by stupidity. http://people.debian.org/~branden/ | msg04031/pgp0.pgp Description: PGP signature
Re: Lots of problems with Debian unstable on Matrox G200
Simon Hepburn wrote: > Would that be the mga_drv.o that came with X 4.2.1 or the one that came in > the matrox tarball ? I think you need the matrox version to use > mga_hal_drv.o. Did you copy back the matrox mga_drv.o after you upgraded X I should have thought some more...from your log file: (II) Loading /usr/X11R6/lib/modules/drivers/mga_hal_drv.o (II) Module mga_hal: vendor="The XFree86 Project" compiled for 4.0.3, module version = 1.0.0 You are trying to use a module compiled for X4.0.3. In the latest matrox tarball you will find a dir containing modules compiled for X4.2. The mga_drv_hal.o in that dir works fine with either version of mga_drv.o. At least that's my experience with a G450. YMMV. -- Simon Hepburn. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
# no crash, no coredump, no hang, no spontaneous reboot severity 163807 normal retitle 163807 xserver-xfree86: [fbdev] color depth disagreements with kernel tag 163807 + moreinfo thanks On Tue, Oct 08, 2002 at 11:41:48AM -0400, Matt Filizzi wrote: > After upgrading to 4.2.1 and typing startx, it would fail and give me an > error that the screen color depth is incorrect (24) after setting to 16 > it works, however everything becomes a green tint. This is able to be > fixed by removing the fbdev setings (and recompiling the kernel to not > use fbdev). You did not supply your XFree86.0.log file; this information is needed for proper analysis of your bug report. See, e.g., XF86Config(7). -- G. Branden Robinson| Organized religion is a sham and a Debian GNU/Linux | crutch for weak-minded people who [EMAIL PROTECTED] | need strength in numbers. http://people.debian.org/~branden/ | -- Jesse Ventura msg04029/pgp0.pgp Description: PGP signature
Bug#163622: xfree86-common: Error starting X, using Matrox G200
On Mon, Oct 07, 2002 at 08:55:26PM -0400, Ian Bicking wrote: > Here's the backtrace, tell me if there's anything more you need: [...] > #7 0x0807f3c8 in xf86SigHandler (signo=11) at xf86Events.c:1085 > signo = 11 > #8 0x4007e518 in sigaction () from /lib/libc.so.6 > No symbol table info available. > #9 0x40197cdc in ?? () > No symbol table info available. > #10 0x0852b478 in ?? () > No symbol table info available. > #11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5, > argv=0xbdf4) > at xf86Init.c:528 > i = 1075228112 > j = 0 > k = 1074540038 > scr_index = 1074540038 > No symbol table info available. Figures. Died in one of the modules, which are invisible to gdb. The only way to nail this down is to use the specially-hacked version of gdb that understand XFree86 server modules. Unfortunately, Debian's gdb does not contain this hack. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=119028&repeatmerged=yes Maybe someone on the debian-x list has a xfree86-gdb binary that you can use. -- G. Branden Robinson|A committee is a life form with six Debian GNU/Linux |or more legs and no brain. [EMAIL PROTECTED] |-- Robert Heinlein http://people.debian.org/~branden/ | msg04028/pgp0.pgp Description: PGP signature
Processed: Re: Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
Processing commands for [EMAIL PROTECTED]: > severity 163807 normal Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth Severity set to `normal'. > retitle 163807 xserver-xfree86: [fbdev] color depth disagreements with kernel Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth Changed Bug title. > tag 163807 + moreinfo Bug#163807: xserver-xfree86: [fbdev] color depth disagreements with kernel Tags added: moreinfo > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ARCHSUPPORTS.NET
Dear Sir / Madam, ARCHSUPPORTS.NET - USD $610 Please note that after years, the registration on the domain name ARCHSUPPORTS.NET was not renewed and this domain became available to register. Consequently, we have been approached to market this domain name that has been tracked and registered by a client. As a result, ARCHSUPPORTS.NET is now available from us for IMMEDIATE transfer. With so many companies using these initials along with what many would consider to be a genuine investment, we expect to find an interested party for this excellent .net. This is a VALUABLE and HIGH PROFILE domain and we believe that this development could be of genuine interest and benefit to your operation. Please note that the domain name market is extremely solid at the moment and similar domains are currently selling on afternic.com, greatdomains.com (domain auction sites) and by domain name brokers, in some cases, for many thousands of US dollars. Please note that transfers take just 15 minutes and are extremely straightforward - absolutely NO technical knowledge is required! For our client's peace of mind, we use an escrow service for all transactions and domains are ALWAYS secured by the buyer prior to us receiving any fund. We pay all fees connected with the escrow process. If you would like to use WWW.ARCHSUPPORTS.NET for your online business, please contact us at your earliest convenience - we will be on hand should you require any further assistance or information. We thank you for your attention and sincerely apologise if this e-mail has not been of interest to you. Sincerely Yours Lara Marketing ThePortal.net
Bug#163815: xserver-xfree86: [trident cyber9397] colour palette screwed up, requiring power off
Package: xserver-xfree86 Version: 4.2.1-1 Severity: important Tags: sid On starting XFree86 4.2.1, the video palette in all depths (8/15/16/24) is screwed up. It appears that the colours are being mapped to the VGA palette, in that only 16 colours are available, and they are repeated through the rest of the palette. This condition persists, even if you reboot to Windows 98SE, or revert to 4.1.0-17, and is only fixed by a complete hard reset. The hardware is an IBM Thinkpad 770 (type 9548) laptop. -- Package-specific info: 00:03.0 VGA compatible controller: Trident Microsystems Cyber 9397 (rev f3) 00:03.0 Class 0300: 1023:9397 (rev f3) Section "Files" FontPath"unix/:7100"# local font server FontPath"unix/:7101"# xfs-xtt server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" FontPath"/usr/X11R6/lib/X11/fonts/defoma/CID" FontPath"/usr/X11R6/lib/X11/fonts/defoma/TrueType" FontPath"/usr/local/lib/X11/fonts/truetype" EndSection ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc101" Option "XkbLayout" "intl" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" Option "Device""/dev/gpmdata" Option "Protocol" "PS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Cyber 9397" Driver "trident" EndSection Section "Monitor" Identifier "LCD Screen" HorizSync 28-49 VertRefresh 43-72 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Cyber 9397" Monitor "LCD Screen" DefaultDepth16 SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Section "DRI" Mode0666 EndSection ### END DEBCONF SECTION -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux manlap 2.4.18-586tsc #1 Sun Apr 14 10:57:57 EST 2002 i586 Locale: LANG=en_GB, LC_CTYPE=en_GB Ve
Bug#163799: xlibs: [xkb] bogus mapping in us_intl
Package: xlibs
Version: 4.1.0-16
Severity: normal
Tags: patch
When switching group the key 6 prints "^" instead of 6. Clearly a typo.
Cheers,
Ivan
*** xc/programs/xkbcomp/symbols/us_intl Tue Oct 8 15:50:03 2002
--- xc-ivan/programs/xkbcomp/symbols/us_intlTue Oct 8 15:50:30 2002
***
*** 15,19
[ grave, asciitilde ] };
key { [ 6,dead_circumflex ],
! [ asciicircum, asciicircum ] };
key { [ dead_acute, dead_diaeresis ],
[ apostrophe, quotedbl] };
--- 15,19
[ grave, asciitilde ] };
key { [ 6,dead_circumflex ],
! [ 6,asciicircum ] };
key { [ dead_acute, dead_diaeresis ],
[ apostrophe, quotedbl] };
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux zen 2.4.19c #1 Fri Sep 20 10:35:46 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages xlibs depends on:
ii libc6 2.2.5-11.2 GNU C Library: Shared libraries an
ii libfreetype6 2.0.9-1FreeType 2 font engine, shared lib
ii xfree86-common4.1.0-16 X Window System (XFree86) infrastr
ii xlibs 4.1.0-16 X Window System client libraries
xfree packages for woody
Hello, after I found a new flat my xfree 4.2 packages are back online. I will build new packages as soon as possible. I am still looking for someone to mirror these packages, because my connection is quite slow. You can find mor information here: http://zoidberg.dnsalias.org/xfree/ Cheers, -- Philipp Huegelmeyer <[EMAIL PROTECTED]> Box was rebooted at stardate:2669.0 --- pgp-fingerprint: D008 BB2B 0B48 80EC CDF0 CBF0 D665 8CFF 63D9 DF8A
Accepted xfree86 4.2.1-2 (i386 source all)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 7 Oct 2002 22:38:45 -0500 Source: xfree86 Binary: xserver-common libxaw7-dbg xbase-clients twm xlibmesa3-dbg xfonts-scalable xfonts-75dpi libdps1-dbg xlib6g-dev xmh libxaw6-dbg xfwp xlibs xlibosmesa3-dbg libdps-dev xserver-xfree86-dbg xlibmesa-dev xserver-xfree86 libdps1 proxymngr xfonts-base-transcoded libxaw6-dev lbxproxy xfonts-cyrillic x-window-system-core xlib6g xutils xspecs xlibs-pic x-window-system xfree86-common xfs xfonts-base xlibmesa3 xlibs-dbg libxaw7-dev xnest xfonts-100dpi-transcoded libxaw6 xfonts-100dpi xterm xfonts-75dpi-transcoded xprt xlibosmesa-dev xvfb libxaw7 xlibosmesa3 xdm xlibs-dev Architecture: source i386 all Version: 4.2.1-2 Distribution: unstable Urgency: low Maintainer: Branden Robinson <[EMAIL PROTECTED]> Changed-By: Branden Robinson <[EMAIL PROTECTED]> Description: lbxproxy - Low Bandwidth X (LBX) proxy server libdps-dev - Display PostScript (DPS) client library development files libdps1- Display PostScript (DPS) client library libdps1-dbg - Display PostScript (DPS) client library (unstripped) libxaw6- X Athena widget set library (version 6) libxaw6-dbg - X Athena widget set library (version 6) (unstripped) libxaw6-dev - X Athena widget set library development files (version 6) libxaw7- X Athena widget set library libxaw7-dbg - X Athena widget set library (unstripped) libxaw7-dev - X Athena widget set library development files proxymngr - X proxy services manager twm- Tab window manager x-window-system - X Window System x-window-system-core - X Window System core components xbase-clients - miscellaneous X clients xdm- X display manager xfonts-100dpi - 100 dpi fonts for X xfonts-100dpi-transcoded - 100 dpi fonts for X (transcoded from ISO 10646-1) xfonts-75dpi - 75 dpi fonts for X xfonts-75dpi-transcoded - 75 dpi fonts for X (transcoded from ISO 10646-1) xfonts-base - standard fonts for X xfonts-base-transcoded - standard fonts for X (transcoded from ISO 10646-1) xfonts-cyrillic - Cyrillic fonts for X xfonts-scalable - scalable fonts for X xfree86-common - X Window System (XFree86) infrastructure xfs- X font server xfwp - X firewall proxy server xlib6g - pseudopackage providing X libraries xlib6g-dev - pseudopackage providing X library development files xlibmesa-dev - XFree86 version of Mesa 3D graphics library development files xlibmesa3 - XFree86 version of Mesa 3D graphics library xlibmesa3-dbg - XFree86 version of Mesa 3D graphics library (unstripped) xlibosmesa-dev - Mesa/XFree86 off-screen rendering library development files xlibosmesa3 - Mesa/XFree86 off-screen rendering library xlibosmesa3-dbg - Mesa/XFree86 off-screen rendering library (unstripped) xlibs - X Window System client libraries xlibs-dbg - X Window System client libraries (unstripped) xlibs-dev - X Window System client library development files xlibs-pic - X Window System client extension library PIC archives xmh- X interface to the MH mail system xnest - nested X server xprt - X print server xserver-common - files and utilities common to all X servers xserver-xfree86 - the XFree86 X server xserver-xfree86-dbg - the XFree86 X server (static version with debugging symbols) xspecs - X protocol, extension, and library technical specifications xterm - X terminal emulator xutils - X Window System utility programs xvfb - virtual framebuffer X server Closes: 163359 163522 Changes: xfree86 (4.2.1-2) unstable; urgency=low . * patch #000_post421: resynced with xf-4_2-branch as of 2002-10-06 + Xdm patches: realloc usage, zero malloc()ated memory, enable /dev/urandom on NetBSD 1.4 and later (#5345, Mike A. Harris, #5401, Matthias Scheler) (Matthieu Herrb) + Fix crash in the TextWidget reported by Hans Wilmer. The bug is fixed in the TextAction.c patch (actually it was fixed in head, but I forgot to update the 4.2 branch, that is what most people are using). Also synced some other bug fixes only in CVS head. (Paulo Cesar Pereira de Andrade) . * patch #002: resynced with xf-4_2-branch updates * patch #024: new; fix for hangs upon VT switch back to XFree86 on Rage128 and Radeon cards due to failure to set and reset PCI busmastering properly (thanks, Michel Dänzer) (Closes: #163359) * patch #026: new; patch from Steven Davies to implement double-buffering support for the XVideo extension in the tdfx driver; he wanted testers, so I'm sticking this code in to test it. Welcome to Debian unstable! . * debian/control: - update versioned Replaces in xdm to not reference a version of xbase-clients that only existed when woody was unstable - update xbase-clients's extended description to mention xf86cfg, xf86config, xrandr, xtrapchar, xtrapin, xtrapinfo, xtrapout, xtrapproto, xtrapreset, and
Bug#163807: xserver-xfree86: FBDev Green Screen and Invalid Color Depth
Package: xserver-xfree86 Version: 4.2.1-1 Severity: important Tags: sid After upgrading to 4.2.1 and typing startx, it would fail and give me an error that the screen color depth is incorrect (24) after setting to 16 it works, however everything becomes a green tint. This is able to be fixed by removing the fbdev setings (and recompiling the kernel to not use fbdev). -- Package-specific info: ### BEGIN DEBCONF SECTION # XF86Config-4 (XFree86 server configuration file) generated by dexconf, the # Debian X Configuration tool, using values from the debconf database. # # Edit this file with caution, and see the XF86Config-4 manual page. # (Type "man XF86Config-4" at the shell prompt.) # # If you want your changes to this file preserved by dexconf, only make changes # before the "### BEGIN DEBCONF SECTION" line above, and/or after the # "### END DEBCONF SECTION" line below. # # To change things within the debconf section, run the command: # dpkg-reconfigure xserver-xfree86 # as root. Also see "How do I add custom sections to a dexconf-generated # XF86Config or XF86Config-4 file?" in /usr/share/doc/xfree86-common/FAQ.gz. Section "Files" FontPath"unix/:7100"# local font server # if the local font server has problems, we can fall back on these FontPath"/usr/lib/X11/fonts/misc" FontPath"/usr/lib/X11/fonts/cyrillic" FontPath"/usr/lib/X11/fonts/100dpi/:unscaled" FontPath"/usr/lib/X11/fonts/75dpi/:unscaled" FontPath"/usr/lib/X11/fonts/Type1" FontPath"/usr/lib/X11/fonts/Speedo" FontPath"/usr/lib/X11/fonts/100dpi" FontPath"/usr/lib/X11/fonts/75dpi" EndSection Section "Module" Load"GLcore" Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" Load"freetype" Load"glx" Load"int10" Load"record" Load"speedo" Load"type1" Load"vbe" EndSection Section "InputDevice" Identifier "Generic Keyboard" Driver "keyboard" Option "CoreKeyboard" Option "XkbRules" "xfree86" Option "XkbModel" "pc104" Option "XkbLayout" "us" EndSection Section "InputDevice" Identifier "Configured Mouse" Driver "mouse" Option "CorePointer" # Option "Device""/dev/input/mice" Option "Device""/dev/gpmdata" Option "Protocol" "ImPS/2" Option "ZAxisMapping" "4 5" EndSection Section "Device" Identifier "Generic Video Card" Driver "fbdev" VideoRam8192 Option "UseFBDev" "true" EndSection Section "Monitor" Identifier "Generic Monitor" HorizSync 30-100 VertRefresh 50-160 Option "DPMS" EndSection Section "Screen" Identifier "Default Screen" Device "Generic Video Card" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Depth 1 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 24 Modes "1152x864" "1024x768" "800x600" "640x480" EndSubSection EndSection Section "ServerLayout" Identifier "Default Layout" Screen "Default Screen" InputDevice "Generic Keyboard" InputDevice "Configured Mouse" EndSection Section "DRI" Mode0666 EndSection ### END DEBCONF SECTION --w---1 root root52324 Oct 7 22:35 /var/log/XFree86.0.log --w---1 root root51522 Aug 5 21:53 /var/log/XFree86.8.log -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux beyond.hjsoft.com 2.4.20-pre7 #2 Mon Oct 7 18:17:52 EDT 2002 i686 Locale: LANG=C, LC_CTYPE=C Versions of packages xserver-xfree86 depends on: ii debconf 1.2.10 Debian configuration manag
ARCHSUPPORTS.NET
Dear Sir / Madam, ARCHSUPPORTS.NET - USD $610 Please note that after years, the registration on the domain name ARCHSUPPORTS.NET was not renewed and this domain became available to register. Consequently, we have been approached to market this domain name that has been tracked and registered by a client. As a result, ARCHSUPPORTS.NET is now available from us for IMMEDIATE transfer. With so many companies using these initials along with what many would consider to be a genuine investment, we expect to find an interested party for this excellent .net. This is a VALUABLE and HIGH PROFILE domain and we believe that this development could be of genuine interest and benefit to your operation. Please note that the domain name market is extremely solid at the moment and similar domains are currently selling on afternic.com, greatdomains.com (domain auction sites) and by domain name brokers, in some cases, for many thousands of US dollars. Please note that transfers take just 15 minutes and are extremely straightforward - absolutely NO technical knowledge is required! For our client's peace of mind, we use an escrow service for all transactions and domains are ALWAYS secured by the buyer prior to us receiving any fund. We pay all fees connected with the escrow process. If you would like to use WWW.ARCHSUPPORTS.NET for your online business, please contact us at your earliest convenience - we will be on hand should you require any further assistance or information. We thank you for your attention and sincerely apologise if this e-mail has not been of interest to you. Sincerely Yours Lara Marketing ThePortal.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163799: xlibs: [xkb] bogus mapping in us_intl
Package: xlibs
Version: 4.1.0-16
Severity: normal
Tags: patch
When switching group the key 6 prints "^" instead of 6. Clearly a typo.
Cheers,
Ivan
*** xc/programs/xkbcomp/symbols/us_intl Tue Oct 8 15:50:03 2002
--- xc-ivan/programs/xkbcomp/symbols/us_intlTue Oct 8 15:50:30 2002
***
*** 15,19
[ grave, asciitilde ] };
key { [ 6,dead_circumflex ],
! [ asciicircum, asciicircum ] };
key { [ dead_acute, dead_diaeresis ],
[ apostrophe, quotedbl] };
--- 15,19
[ grave, asciitilde ] };
key { [ 6,dead_circumflex ],
! [ 6,asciicircum ] };
key { [ dead_acute, dead_diaeresis ],
[ apostrophe, quotedbl] };
-- System Information
Debian Release: 3.0
Architecture: i386
Kernel: Linux zen 2.4.19c #1 Fri Sep 20 10:35:46 CEST 2002 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages xlibs depends on:
ii libc6 2.2.5-11.2 GNU C Library: Shared libraries an
ii libfreetype6 2.0.9-1FreeType 2 font engine, shared lib
ii xfree86-common4.1.0-16 X Window System (XFree86) infrastr
ii xlibs 4.1.0-16 X Window System client libraries
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't get my ATI Radeon 7500 with dri package to work
> I assume you mean a binary snapshot from dri.sf.net? They currently > suffer from binary compatibility issues, see the dri-devel archives for > details. > > However, there's a much better solution: > > deb http://penguinppc.org/~daenzer/debian/dri-trunk/./ > > Install the xserver-xfree86-dri-trunk package and build the DRM from the > drm-trunk-module-src package. > Thanks! It works! Greetings, Roman -- www: http://www.romanofski.de email: [EMAIL PROTECTED]
xfree packages for woody
Hello, after I found a new flat my xfree 4.2 packages are back online. I will build new packages as soon as possible. I am still looking for someone to mirror these packages, because my connection is quite slow. You can find mor information here: http://zoidberg.dnsalias.org/xfree/ Cheers, -- Philipp Huegelmeyer <[EMAIL PROTECTED]> Box was rebooted at stardate:2669.0 --- pgp-fingerprint: D008 BB2B 0B48 80EC CDF0 CBF0 D665 8CFF 63D9 DF8A -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: can't get my ATI Radeon 7500 with dri package to work
On Die, 2002-10-08 at 12:19, Roman Joost wrote: > I don't know why, but i can't get my ati radeon 7500 working with X. I tried > to > install the GATOS ati.2 drivers. After a failure, i purged the xserver-xfree86 > package and installed the dri package. The radeon drm module loaded perfectly > into the kernel, but the X Server won't start. I assume you mean a binary snapshot from dri.sf.net? They currently suffer from binary compatibility issues, see the dri-devel archives for details. However, there's a much better solution: deb http://penguinppc.org/~daenzer/debian/dri-trunk/./ Install the xserver-xfree86-dri-trunk package and build the DRM from the drm-trunk-module-src package. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast
can't get my ATI Radeon 7500 with dri package to work
I don't know why, but i can't get my ati radeon 7500 working with X. I tried to install the GATOS ati.2 drivers. After a failure, i purged the xserver-xfree86 package and installed the dri package. The radeon drm module loaded perfectly into the kernel, but the X Server won't start. I attached the XFree log and Config. Maybe its the framebuffer, that causes the problems with the dri package. I don't know. Im using the 2.4.19 debian kernel. If you need more logs, configs or somthing related to my XFree failure, tell me. now iam using the GATOS drivers. It works, but glxinfo says: name of display: :0.0 Radeon DRI driver: Compatibility mode for DRM driver version 1.2.0 TCL will be disabled, expect reduced performance (prefer DRM radeon.o 1.3.x or newer) disabling TCL support display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context client glx vendor string: SGI client glx version string: 1.2 client glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI Radeon 20020611 AGP 4x x86/MMX/3DNow! DRM-COMPAT NO-TCL OpenGL version string: 1.2 Mesa 4.0.4 OpenGL extensions: ... I think the GATOS drivers are older one. If someone has an idea regarding the failure of my X start, please let me know. I used the dri package before i tried the GATOS drivers and they run perfectly. Thanks for your help. Roman -- www: http://www.romanofski.de email: [EMAIL PROTECTED] XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 11:45:39 2002 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Samtron 96P" (**) | |-->Device "ATI Radeon 7500" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "de" (**) XKB: layout: "de" (**) Option "XkbVariant" "nodeadkeys" (**) XKB: variant: "nodeadkeys" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Configured Mouse" (**) |-->Input Device "pen1" (**) |-->Input Device "eraser1" (**) |-->Input Device "cursor1" (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (**) FontPath set to "unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,unix/:7101" (==) 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.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 = 0x8000700c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1022,7006 card , rev 25 class 06,00,00 hdr 80 (II) PCI: 00:01:0: chip 1022,7007 card , rev 01 class 06,04,00 hdr 81 (II) PCI: 00:04:0: chip 1106,0686 card 1043,800d rev 1b class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:04:2: chip 1106,3038 card 0925,1234 rev 0e class 0c,03,00 hdr 00 (II) PCI: 0
Re: can't get my ATI Radeon 7500 with dri package to work
> I assume you mean a binary snapshot from dri.sf.net? They currently > suffer from binary compatibility issues, see the dri-devel archives for > details. > > However, there's a much better solution: > > deb http://penguinppc.org/~daenzer/debian/dri-trunk/./ > > Install the xserver-xfree86-dri-trunk package and build the DRM from the > drm-trunk-module-src package. > Thanks! It works! Greetings, Roman -- www: http://www.romanofski.de email: [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
XFree86 -configure failure
Hi! I'm not sure if I should report this her, or to the upstream, but in the of the output the debian-x maillinglist was mentioned. I run XFree86 -configure and got this 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] The output from scanpci -v is attached in scanpci.out and the logfile in XFree86.0.log. I have a working XF86Config (also attached), wished worked both in 4.1 (with patched savage driver version 1.1.23t) and now in 4.2.1. My Computer is an IBM Thinkpad T23, with a supersavage chipset Another problem, XFree86 -configure report an error about glide. Thanks for your new version, now my X working without downloading a separate savage driver. If you want any more information, please let me know. Sincerely Mikael -- Email: [EMAIL PROTECTED]mobile: +46 70 740 1585 PGP: 1024D/20E93E8E 76F9 E895 1073 12B8 A281 8144 5A1E 4BDD 20E9 3E8E pci bus 0x cardnum 0x00 function 0x00: vendor 0x8086 device 0x3575 Intel i830M Bridge CardVendor 0x1014 card 0x021d (IBM, Card unknown) STATUS0x2010 COMMAND 0x0106 CLASS 0x06 0x00 0x00 REVISION 0x02 BASE0 0xd008 addr 0xd000 MEM PREFETCHABLE BYTE_00x105a009 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x01 function 0x00: vendor 0x8086 device 0x3576 Intel Device unknown STATUS0x0020 COMMAND 0x0107 CLASS 0x06 0x04 0x00 REVISION 0x02 HEADER0x01 LATENCY 0x60 PRIBUS0x00 SECBUS 0x01 SUBBUS 0x01 SECLT 0x40 IOBASE0xf000 IOLIM 0xfff SECSTATUS 0x02a0 NOPREFETCH_MEMBASE 0xc010 MEMLIM 0xc01f PREFETCH_MEMBASE 0xe000 MEMLIM 0xebff NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT VGA_EN ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x1d function 0x00: vendor 0x8086 device 0x2482 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0005 CLASS 0x0c 0x03 0x00 REVISION 0x01 BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00 BASE4 0x1801 addr 0x1800 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b pci bus 0x cardnum 0x1d function 0x01: vendor 0x8086 device 0x2484 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0005 CLASS 0x0c 0x03 0x00 REVISION 0x01 BASE4 0x1821 addr 0x1820 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0x0b pci bus 0x cardnum 0x1d function 0x02: vendor 0x8086 device 0x2487 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0005 CLASS 0x0c 0x03 0x00 REVISION 0x01 BASE4 0x1841 addr 0x1840 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x03 INT_LINE 0x0b pci bus 0x cardnum 0x1e function 0x00: vendor 0x8086 device 0x2448 Intel Device unknown STATUS0x0080 COMMAND 0x0107 CLASS 0x06 0x04 0x00 REVISION 0x41 HEADER0x01 LATENCY 0x00 PRIBUS0x00 SECBUS 0x02 SUBBUS 0x08 SECLT 0x40 IOBASE0x3000 IOLIM 0x7fff SECSTATUS 0x2280 NOPREFETCH_MEMBASE 0xc020 MEMLIM 0xcfff PREFETCH_MEMBASE 0xec00 MEMLIM 0xf7ff NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT NO_VGA_EN ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x1f function 0x00: vendor 0x8086 device 0x248c Intel Device unknown STATUS0x0280 COMMAND 0x000f CLASS 0x06 0x01 0x00 REVISION 0x01 BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00 BYTE_00x1001 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x1f function 0x01: vendor 0x8086 device 0x248a Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0007 CLASS 0x01 0x01 0x8a REVISION 0x01 BASE0 0x01f1 addr 0x01f0 I/O BASE1 0x03f5 addr 0x03f4 I/O BASE2 0x0171 addr 0x0170 I/O BASE3 0x0375 addr 0x0374 I/O BASE4 0x1861 addr 0x1860 I/O BASE5 0x1800 addr 0x1800 MEM MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0xff BYTE_00x8000a307 BYTE_1 0x00 BYTE_2 0x80732b8 BYTE_3 0x pci bus 0x cardnum 0x1f function 0x03: vendor 0x8086 device 0x2483 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0001 CLASS 0x0c 0x05 0x00 REVISION 0x01 BASE4 0x1881 addr 0x1880 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0x0b BYTE_00x01 BYTE_1 0x00 BYTE_2 0x8073630 BYTE_3 0x pci bus 0x cardnum 0x1f function 0x05: vendor 0x8086 device 0x2485
Re: can't get my ATI Radeon 7500 with dri package to work
On Die, 2002-10-08 at 12:19, Roman Joost wrote: > I don't know why, but i can't get my ati radeon 7500 working with X. I tried to > install the GATOS ati.2 drivers. After a failure, i purged the xserver-xfree86 > package and installed the dri package. The radeon drm module loaded perfectly > into the kernel, but the X Server won't start. I assume you mean a binary snapshot from dri.sf.net? They currently suffer from binary compatibility issues, see the dri-devel archives for details. However, there's a much better solution: deb http://penguinppc.org/~daenzer/debian/dri-trunk/./ Install the xserver-xfree86-dri-trunk package and build the DRM from the drm-trunk-module-src package. -- Earthling Michel Dänzer (MrCooper)/ Debian GNU/Linux (powerpc) developer XFree86 and DRI project member / CS student, Free Software enthusiast -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163699: xserver-xfree86: Xserver crashes in QUake3
On Mon, Oct 07, 2002 at 02:16:17PM -0500, Branden Robinson wrote: > Those are some pretty aggressive options you've got going there. The > fbdev layer plus PCI retries plus AGPMode 4. I wouldn't be surprised if > you'd get more stability by backing off on some of those. However, a > bug's a bug. I'll see if backing them off makes a difference. > Welcome to the new, improved for XFree86 4.2 SEGV club; I need you to do > the following: > > 1) apt-get install xserver-xfree86-dbg gdb; > 2) Run the XFree86-debug server in an environment where the coredumpsize >is unlimited; > 3) gdb /usr/X11R6/bin/XFree86-debug core; > 4) Type "bt full" at the gdb prompt; > 5) Send this bug the output. Have downloaded, but haven't had time yet. Meanwhile, the following output from X, which comes from just starting and quitting X, seems suspicious. Especially the penultimate line: XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 09:03:28 2002 (==) Using config file: "/etc/X11/XF86Config-4" (EE) Failed to load module "pex5" (module does not exist, 0) (EE) Failed to load module "xie" (module does not exist, 0) (EE) MGA: Failed to load module "mga_hal" (module does not exist, 0) DRIUnlock called when not locked waiting for X server to shut down cheers, Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt
can't get my ATI Radeon 7500 with dri package to work
I don't know why, but i can't get my ati radeon 7500 working with X. I tried to install the GATOS ati.2 drivers. After a failure, i purged the xserver-xfree86 package and installed the dri package. The radeon drm module loaded perfectly into the kernel, but the X Server won't start. I attached the XFree log and Config. Maybe its the framebuffer, that causes the problems with the dri package. I don't know. Im using the 2.4.19 debian kernel. If you need more logs, configs or somthing related to my XFree failure, tell me. now iam using the GATOS drivers. It works, but glxinfo says: name of display: :0.0 Radeon DRI driver: Compatibility mode for DRM driver version 1.2.0 TCL will be disabled, expect reduced performance (prefer DRM radeon.o 1.3.x or newer) disabling TCL support display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 server glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context client glx vendor string: SGI client glx version string: 1.2 client glx extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context GLX extensions: GLX_EXT_visual_info, GLX_EXT_visual_rating, GLX_EXT_import_context OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI Radeon 20020611 AGP 4x x86/MMX/3DNow! DRM-COMPAT NO-TCL OpenGL version string: 1.2 Mesa 4.0.4 OpenGL extensions: ... I think the GATOS drivers are older one. If someone has an idea regarding the failure of my X start, please let me know. I used the dri package before i tried the GATOS drivers and they run perfectly. Thanks for your help. Roman -- www: http://www.romanofski.de email: [EMAIL PROTECTED] XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 11:45:39 2002 (==) Using config file: "/etc/X11/XF86Config-4" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Samtron 96P" (**) | |-->Device "ATI Radeon 7500" (**) |-->Input Device "Generic Keyboard" (**) Option "XkbRules" "xfree86" (**) XKB: rules: "xfree86" (**) Option "XkbModel" "pc104" (**) XKB: model: "pc104" (**) Option "XkbLayout" "de" (**) XKB: layout: "de" (**) Option "XkbVariant" "nodeadkeys" (**) XKB: variant: "nodeadkeys" (==) Keyboard: CustomKeycode disabled (**) |-->Input Device "Configured Mouse" (**) |-->Input Device "pen1" (**) |-->Input Device "eraser1" (**) |-->Input Device "cursor1" (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (**) FontPath set to "unix/:7100,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/100dpi/:unscaled,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/lib/X11/fonts/Type1,/usr/lib/X11/fonts/Speedo,/usr/lib/X11/fonts/100dpi,/usr/lib/X11/fonts/75dpi,unix/:7101" (==) 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.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 = 0x8000700c, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1022,7006 card , rev 25 class 06,00,00 hdr 80 (II) PCI: 00:01:0: chip 1022,7007 card , rev 01 class 06,04,00 hdr 81 (II) PCI: 00:04:0: chip 1106,0686 card 1043,800d rev 1b class 06,01,00 hdr 80 (II) PCI: 00:04:1: chip 1106,0571 card , rev 06 class 01,01,8a hdr 00 (II) PCI: 00:04:2: chip 1106,3038 card 0925,1234 rev 0e class 0c,03,00 hdr 00 (II) PCI:
XFree86 -configure failure
Hi! I'm not sure if I should report this her, or to the upstream, but in the of the output the debian-x maillinglist was mentioned. I run XFree86 -configure and got this 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] The output from scanpci -v is attached in scanpci.out and the logfile in XFree86.0.log. I have a working XF86Config (also attached), wished worked both in 4.1 (with patched savage driver version 1.1.23t) and now in 4.2.1. My Computer is an IBM Thinkpad T23, with a supersavage chipset Another problem, XFree86 -configure report an error about glide. Thanks for your new version, now my X working without downloading a separate savage driver. If you want any more information, please let me know. Sincerely Mikael -- Email: [EMAIL PROTECTED] mobile: +46 70 740 1585 PGP: 1024D/20E93E8E 76F9 E895 1073 12B8 A281 8144 5A1E 4BDD 20E9 3E8E pci bus 0x cardnum 0x00 function 0x00: vendor 0x8086 device 0x3575 Intel i830M Bridge CardVendor 0x1014 card 0x021d (IBM, Card unknown) STATUS0x2010 COMMAND 0x0106 CLASS 0x06 0x00 0x00 REVISION 0x02 BASE0 0xd008 addr 0xd000 MEM PREFETCHABLE BYTE_00x105a009 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x01 function 0x00: vendor 0x8086 device 0x3576 Intel Device unknown STATUS0x0020 COMMAND 0x0107 CLASS 0x06 0x04 0x00 REVISION 0x02 HEADER0x01 LATENCY 0x60 PRIBUS0x00 SECBUS 0x01 SUBBUS 0x01 SECLT 0x40 IOBASE0xf000 IOLIM 0xfff SECSTATUS 0x02a0 NOPREFETCH_MEMBASE 0xc010 MEMLIM 0xc01f PREFETCH_MEMBASE 0xe000 MEMLIM 0xebff NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT VGA_EN ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x1d function 0x00: vendor 0x8086 device 0x2482 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0005 CLASS 0x0c 0x03 0x00 REVISION 0x01 BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00 BASE4 0x1801 addr 0x1800 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0x0b pci bus 0x cardnum 0x1d function 0x01: vendor 0x8086 device 0x2484 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0005 CLASS 0x0c 0x03 0x00 REVISION 0x01 BASE4 0x1821 addr 0x1820 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0x0b pci bus 0x cardnum 0x1d function 0x02: vendor 0x8086 device 0x2487 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0005 CLASS 0x0c 0x03 0x00 REVISION 0x01 BASE4 0x1841 addr 0x1840 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x03 INT_LINE 0x0b pci bus 0x cardnum 0x1e function 0x00: vendor 0x8086 device 0x2448 Intel Device unknown STATUS0x0080 COMMAND 0x0107 CLASS 0x06 0x04 0x00 REVISION 0x41 HEADER0x01 LATENCY 0x00 PRIBUS0x00 SECBUS 0x02 SUBBUS 0x08 SECLT 0x40 IOBASE0x3000 IOLIM 0x7fff SECSTATUS 0x2280 NOPREFETCH_MEMBASE 0xc020 MEMLIM 0xcfff PREFETCH_MEMBASE 0xec00 MEMLIM 0xf7ff NO_FAST_B2B NO_SEC_BUS_RST NO_M_ABRT NO_VGA_EN ISA_EN NO_SERR_EN NO_PERR_EN pci bus 0x cardnum 0x1f function 0x00: vendor 0x8086 device 0x248c Intel Device unknown STATUS0x0280 COMMAND 0x000f CLASS 0x06 0x01 0x00 REVISION 0x01 BIST 0x00 HEADER 0x80 LATENCY 0x00 CACHE 0x00 BYTE_00x1001 BYTE_1 0x00 BYTE_2 0x00 BYTE_3 0x00 pci bus 0x cardnum 0x1f function 0x01: vendor 0x8086 device 0x248a Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0007 CLASS 0x01 0x01 0x8a REVISION 0x01 BASE0 0x01f1 addr 0x01f0 I/O BASE1 0x03f5 addr 0x03f4 I/O BASE2 0x0171 addr 0x0170 I/O BASE3 0x0375 addr 0x0374 I/O BASE4 0x1861 addr 0x1860 I/O BASE5 0x1800 addr 0x1800 MEM MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x01 INT_LINE 0xff BYTE_00x8000a307 BYTE_1 0x00 BYTE_2 0x80732b8 BYTE_3 0x pci bus 0x cardnum 0x1f function 0x03: vendor 0x8086 device 0x2483 Intel Device unknown CardVendor 0x1014 card 0x0220 (IBM, Card unknown) STATUS0x0280 COMMAND 0x0001 CLASS 0x0c 0x05 0x00 REVISION 0x01 BASE4 0x1881 addr 0x1880 I/O MAX_LAT 0x00 MIN_GNT 0x00 INT_PIN 0x02 INT_LINE 0x0b BYTE_00x01 BYTE_1 0x00 BYTE_2 0x8073630 BYTE_3 0x pci bus 0x cardnum 0x1f function 0x05: vendor 0x8086 device 0x2485 In
Bug#163699: xserver-xfree86: Xserver crashes in QUake3
On Mon, Oct 07, 2002 at 02:16:17PM -0500, Branden Robinson wrote: > Those are some pretty aggressive options you've got going there. The > fbdev layer plus PCI retries plus AGPMode 4. I wouldn't be surprised if > you'd get more stability by backing off on some of those. However, a > bug's a bug. I'll see if backing them off makes a difference. > Welcome to the new, improved for XFree86 4.2 SEGV club; I need you to do > the following: > > 1) apt-get install xserver-xfree86-dbg gdb; > 2) Run the XFree86-debug server in an environment where the coredumpsize >is unlimited; > 3) gdb /usr/X11R6/bin/XFree86-debug core; > 4) Type "bt full" at the gdb prompt; > 5) Send this bug the output. Have downloaded, but haven't had time yet. Meanwhile, the following output from X, which comes from just starting and quitting X, seems suspicious. Especially the penultimate line: XFree86 Version 4.2.1 (Debian 4.2.1-1 20021004194022 [EMAIL PROTECTED]) / 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 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 Oct 8 09:03:28 2002 (==) Using config file: "/etc/X11/XF86Config-4" (EE) Failed to load module "pex5" (module does not exist, 0) (EE) Failed to load module "xie" (module does not exist, 0) (EE) MGA: Failed to load module "mga_hal" (module does not exist, 0) DRIUnlock called when not locked waiting for X server to shut down cheers, Phil -- http://www.kantaka.co.uk/ .oOo. public key: http://www.kantaka.co.uk/gpg.txt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#163622: xfree86-common: Error starting X, using Matrox G200
Here's the backtrace, tell me if there's anything more you need:
#0 0x4007e581 in kill () from /lib/libc.so.6
No symbol table info available.
#1 0x4007e394 in raise () from /lib/libc.so.6
No symbol table info available.
#2 0x4007f8d1 in abort () from /lib/libc.so.6
No symbol table info available.
#3 0x0806d5f9 in ddxGiveUp () at xf86Init.c:1094
No locals.
#4 0x0806d6a6 in AbortDDX () at xf86Init.c:1145
i = 1
#5 0x080d3468 in AbortServer () at utils.c:436
No locals.
#6 0x080d4906 in FatalError (
f=0x8174d40 "Caught signal %d. Server aborting\n") at utils.c:1399
beenhere = 1
#7 0x0807f3c8 in xf86SigHandler (signo=11) at xf86Events.c:1085
signo = 11
#8 0x4007e518 in sigaction () from /lib/libc.so.6
No symbol table info available.
#9 0x40197cdc in ?? ()
No symbol table info available.
#10 0x0852b478 in ?? ()
No symbol table info available.
#11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5,
argv=0xbdf4)
at xf86Init.c:528
i = 1075228112
j = 0
k = 1074540038
scr_index = 1074540038
No symbol table info available.
#9 0x40197cdc in ?? ()
No symbol table info available.
#10 0x0852b478 in ?? ()
No symbol table info available.
#11 0x0806cabb in InitOutput (pScreenInfo=0x81cbc00, argc=5,
argv=0xbdf4)
at xf86Init.c:528
i = 1075228112
j = 0
k = 1074540038
scr_index = 1074540038
generation = 1
modulelist = (char **) 0xb9ac
optionlist = (pointer *) 0x81f9890
layout = 0xb9ac
screenpix24 = 1074540038
pix24 = 3221224796
pix24From = X_DEFAULT
pix24Fail = 0
#12 0x080bed36 in main (argc=5, argv=, envp=)
at main.c:380
argv =
i = 256
j = 0
k = 1075228112
error = 1075228112
xauthfile = 0x0
alwaysCheckForInput = {0, 1}
