Bug#164799: Small typo in generated XF86Config-4
Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. Warren On Tuesday 15 October 2002 09:05 pm, [EMAIL PROTECTED] wrote: No. It's too hard to parse the file reliably. I've asked for code to do it; no one has the time and/or courage. -- Treasurer, GOLUM, Inc. http://www.golum.org
Bug#164767: xlibs: altgr doesn't work on german keyboards with altwin:meta_win
Heyho, Branden Robinson [EMAIL PROTECTED] writes: I don't think this is exactly the right solution, but one of the reasons I moved the XKB files into /etc is so that people could resolve these issue for themselves, as you have. That's what I thought, but after the upgrade the keyboard isn't really usable for Germans anymore, so I think Debian should provide a solution to fix that. I don't think that we can expect every german debian-user to know how to fix this issues. Maybe we could give them a hint per debconf or at least per example in /usr/share/doc/. so long... David -- /\ Debian GNU/Linux - _The_ free oprating system David Spreen - [EMAIL PROTECTED] - C8B6823A (keyring.debian.org) \/
Bug#165055: xserver-xfree86: Using DDC breaks X
Package: xserver-xfree86 Version: 4.2.1-2 Severity: important Since the upgrade to X4.2, X is broken. When it starts up, my monitor turns off, and my PC doesn't react to input from the keyboard anymore. Using read/get-edid, I've figured out that the combination of my graphic card and my monitor doesn't support DDC properly (it reports a mode of [EMAIL PROTECTED]). Adding Option NoDDC to the Device-section of XF86Config-4 fixes the problem, but the line disappears after every X-update, forcing me to hard-reboot into single-user mode in order to fix it again :(. Please modify the package-configuration to at least honour this setting or let the user choose, if he/she wants to enable DDC during configuration! cheerio, --Chris BTW: The NVidia binary drivers are now broken, too, complaining about missing symbols in __GLsometing (I don't remember, sorry). This probably isn't your responsibility, so I'll have to fight it out with NVidia ;). -- 01:00.0 VGA compatible controller: nVidia Corporation NV5 [Riva TnT2] (rev 15) 01:00.0 Class 0300: 10de:0028 (rev 15) ### 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 FontPathunix/: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 Loadbitmap Loaddbe Loadextmod Loadfreetype Loadint10 Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/gpmdata Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier Generic Video Card Driver nv Option NoDDC EndSection Section Monitor Identifier Generic Monitor HorizSync 30-95 VertRefresh 50-150 Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 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 XFree86 Version 4.2.1 (Debian 4.2.1-2 20021008045526 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor
Bug#164767: xlibs: altgr doesn't work on german keyboards with altwin:meta_win
On Wed, Oct 16, 2002 at 12:34:48PM +0200, David Spreen wrote: Branden Robinson [EMAIL PROTECTED] writes: I don't think this is exactly the right solution, but one of the reasons I moved the XKB files into /etc is so that people could resolve these issue for themselves, as you have. That's what I thought, but after the upgrade the keyboard isn't really usable for Germans anymore, so I think Debian should provide a solution to fix that. I don't think that we can expect every german debian-user to know how to fix this issues. Maybe we could give them a hint per debconf or at least per example in /usr/share/doc/. I'm not saying Debian shouldn't fix it. I'm saying I lack the specific knowledge to fix it correctly. I don't know that the suggested fix is correct. I'm not going to apply it until I do know that. Therefore I'm asking for German users, especially ones with a clue about XKB, to help make this determination. -- G. Branden Robinson| Good judgement comes from Debian GNU/Linux | experience; experience comes from [EMAIL PROTECTED] | bad judgement. http://people.debian.org/~branden/ | -- Fred Brooks pgphJzkXg1KMd.pgp Description: PGP signature
Bug#164799: Small typo in generated XF86Config-4
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. We'd still have to reverse the transformation because of all the people who modify their XF86Config-4 files and refuse to read the comments at the top of the file. -- G. Branden Robinson|I have a truly elegant proof of the Debian GNU/Linux |above, but it is too long to fit [EMAIL PROTECTED] |into this .signature file. http://people.debian.org/~branden/ | pgpc6Bxd03cKw.pgp Description: PGP signature
Bug#165055: marked as done (xserver-xfree86: Using DDC breaks X)
Your message dated Wed, 16 Oct 2002 11:52:42 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#165055: xserver-xfree86: Using DDC breaks X has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 16 Oct 2002 16:03:50 + From [EMAIL PROTECTED] Wed Oct 16 11:03:49 2002 Return-path: [EMAIL PROTECTED] Received: from mailout08.sul.t-online.com [194.25.134.20] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 181qeC-000808-00; Wed, 16 Oct 2002 11:03:48 -0500 Received: from fwd08.sul.t-online.de by mailout08.sul.t-online.com with smtp id 181qe7-0005Hc-0G; Wed, 16 Oct 2002 18:03:43 +0200 Received: from caviar.taylor.vpn ([EMAIL PROTECTED]) by fmrl08.sul.t-online.com with esmtp id 181qe0-0D9K0eC; Wed, 16 Oct 2002 18:03:36 +0200 Received: from timrod by caviar.taylor.vpn with local (Exim 3.36 #1 (Debian)) id 181qdz-CU-00; Wed, 16 Oct 2002 18:03:35 +0200 From: Christopher Taylor [EMAIL PROTECTED] Subject: xserver-xfree86: Using DDC breaks X To: [EMAIL PROTECTED] X-Mailer: bug 3.3.10.2 Message-Id: [EMAIL PROTECTED] Date: Wed, 16 Oct 2002 18:03:35 +0200 X-Sender: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-1.7 required=5.0 tests=BALANCE_FOR_LONG_20K,SPAM_PHRASE_00_01,SUPERLONG_LINE version=2.41 X-Spam-Level: Package: xserver-xfree86 Version: 4.2.1-2 Severity: important Since the upgrade to X4.2, X is broken. When it starts up, my monitor turns off, and my PC doesn't react to input from the keyboard anymore. Using read/get-edid, I've figured out that the combination of my graphic card and my monitor doesn't support DDC properly (it reports a mode of [EMAIL PROTECTED]). Adding Option NoDDC to the Device-section of XF86Config-4 fixes the problem, but the line disappears after every X-update, forcing me to hard-reboot into single-user mode in order to fix it again :(. Please modify the package-configuration to at least honour this setting or let the user choose, if he/she wants to enable DDC during configuration! cheerio, --Chris BTW: The NVidia binary drivers are now broken, too, complaining about missing symbols in __GLsometing (I don't remember, sorry). This probably isn't your responsibility, so I'll have to fight it out with NVidia ;). -- 01:00.0 VGA compatible controller: nVidia Corporation NV5 [Riva TnT2] (rev 15) 01:00.0 Class 0300: 10de:0028 (rev 15) ### 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 FontPathunix/: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 Loadbitmap Loaddbe Loadextmod Loadfreetype Loadint10 Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/gpmdata
Re: [XF86 4.2.1] Blackdown JVM and Japanese Menu.
Dear Branden, I found Blackdown-Java 1.4.1beta (not deb'ed) can display KANJI at XF86 4.2.1-2, but 1.3.1 (deb'ed) can't display KANJI on menubar at XF86 4.2.1-2. Written by ChanChan KO [EMAIL PROTECTED] at Wed, 02 Oct 2002 01:56:06 +0900 (JST) : Subject: Re: [XF86 4.2.1] Blackdown JVM and Japanese Menu. chanchan Dear Branden, chanchan chanchan Written by Branden Robinson [EMAIL PROTECTED] chanchanat Tue, 1 Oct 2002 11:30:27 -0500 : chanchan Subject: Re: [XF86 4.2.1] Blackdown JVM and Japanese Menu. chanchan chanchan branden On Wed, Oct 02, 2002 at 12:56:57AM +0900, ChanChan KO wrote: chanchan branden Package: xserver-xfree86 chanchan branden Version: 4.2.1-0pre1v2 chanchan branden Architecture: i386 chanchan branden Severity: Normal chanchan (Snip) chanchan branden Is the JVM a setuid or setgid program? (Snip) Maybe, this isssue is not from XF86 , problem of older Blackdown JVM. Best Regards, ChanChan.
Bug#164799: Small typo in generated XF86Config-4
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. The code to parse the file has got to be somewhere in the xfree source. Somebody probably even knows where. Somebody might even know how. Surely we can ask him? You probably have never tried to use XML+XSLT on a pb1400... -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: Do not underestimate the value of print statements for debugging.
Bug#164799: Small typo in generated XF86Config-4
Well, there is actually a library for parsing the config file in xc/programs/Xserver/hw/xfree86/parser . Warren On Wednesday 16 October 2002 11:51 am, [EMAIL PROTECTED] wrote: On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. We'd still have to reverse the transformation because of all the people who modify their XF86Config-4 files and refuse to read the comments at the top of the file. -- Treasurer, GOLUM, Inc. http://www.golum.org
RE: XFree4.2 - unstable?
Hey, I was able to finally get my indy to boot at 1280x1024, with setenv monitor H in the prom. This is for my SGI Indy, Newport 24-bit graphics, and my monitor is a Radius PrecisionColor Display/20 a.k.a. Sony GDM-1971. I hope 1024x768 will be supported eventually, though. -brad -Original Message- From: Guido Guenther [mailto:[EMAIL PROTECTED] Behalf Of Guido Guenther Sent: Thursday, September 19, 2002 3:29 PM To: Bradley Bell Cc: [EMAIL PROTECTED] Subject: Re: XFree4.2 - unstable? On Thu, Sep 19, 2002 at 03:16:07PM -0700, Bradley Bell wrote: NG1: Revision 6, 24 bitplanes, REX3 revision B, VC2 revision A, xmap9 revision A, cmap revision D, bt9445 revision D NG1: Screensize 1024x768 Console: colour SGI Newport 128x48 I'm pretty sure the monitor can support 1280x1024. (Radius PrecisionColor Display/20 a.k.a. Sony GDM-1971). any ideas? Maybe I've found the problem. Did you boot with console=d1 set in the PROM. I'll get 1024x768 when I do that and 1280x1024 when I boot with console=g1. I'll fix that, but don't hold your breath. Regards, -- Guido P.S.: and let's move this off -private and to -x or something.
Re: XFree4.2 - unstable?
On Wed, Oct 16, 2002 at 03:35:57PM -0700, Bradley Bell wrote: Hey, I was able to finally get my indy to boot at 1280x1024, with setenv monitor H in the prom. Great! Where did you get that info from? I know there's a place in the nvram that stores the monitor type, but I didn't know one can set it from within the prom monitor. Do you know what other monitor types one can set? Maybe (H=high res, L=low res)? [..snip..] I hope 1024x768 will be supported eventually, though. It will. As soon as I get around to work on X again. Regards, -- Guido
Bug#164917: xlibs-dev: moving away from Xmd.h arch dependencies
Here is a patch that includes the move toward arch independence and includes a major cleanup of the preprocessor directives in Xmd.h. It converts all #ifdef to #if defined(symbol) and #ifndef to #if !defined(symbol) except for the header test at the top. Warren --- /usr/include/X11/Xmd.h 2002-10-08 01:05:41.0 -0500 +++ Xmd2.h 2002-10-15 23:28:16.0 -0500 @@ -55,20 +55,24 @@ /* * Special per-machine configuration flags. */ -#ifdef CRAY -#define WORD64 /* 64-bit architecture */ +#if !defined(WORD64) defined(CRAY) +# define WORD64/* 64-bit architecture */ #endif -#if defined(__alpha) || defined(__alpha__) || \ + +#if !defined(LONG64) +# if defined(__alpha) || defined(__alpha__) || \ defined(__ia64__) || defined(ia64) || \ defined(__sparc64__) || \ defined(__s390x__) || \ (defined(__hppa__) defined(__LP64__)) -#define LONG64 /* 32/64-bit architecture */ -#endif -#ifdef __sgi -#if (_MIPS_SZLONG == 64) -#define LONG64 +# define LONG64 /* 32/64-bit architecture */ +# endif #endif + +#if !defined(LONG64) defined(__sgi) +# if (_MIPS_SZLONG == 64) +# define LONG64 +# endif #endif /* @@ -76,7 +80,7 @@ * on a 32-bit machine and must coorespond to the protocol. */ #ifdef WORD64 -#define MUSTCOPY +# define MUSTCOPY #endif /* WORD64 */ @@ -95,10 +99,10 @@ * expand correctly before the concatenation, rather than afterward. */ #if ((defined(__STDC__) || defined(__cplusplus) || defined(c_plusplus)) !defined(UNIXCPP)) || defined(ANSICPP) -#define _SIZEOF(x) sz_##x -#define SIZEOF(x) _SIZEOF(x) +# define _SIZEOF(x) sz_##x +# define SIZEOF(x) _SIZEOF(x) #else -#define SIZEOF(x) sz_/**/x +# define SIZEOF(x) sz_/**/x #endif /* if ANSI C compiler else not */ /* @@ -106,32 +110,32 @@ * need them. Note that bitfields are not guarranteed to be signed * (or even unsigned) according to ANSI C. */ -#ifdef WORD64 +#if defined(WORD64) typedef long INT64; typedef unsigned long CARD64; -#define B32 :32 -#define B16 :16 -#ifdef UNSIGNEDBITFIELDS +# define B32 :32 +# define B16 :16 +# if defined(UNSIGNEDBITFIELDS) typedef unsigned int INT32; typedef unsigned int INT16; -#else -#ifdef __STDC__ +# else +# if defined(__STDC__) typedef signed int INT32; typedef signed int INT16; -#else +# else typedef int INT32; typedef int INT16; -#endif -#endif +# endif +# endif #else -#define B32 -#define B16 -#ifdef LONG64 +# define B32 +# define B16 +# if defined(LONG64) typedef long INT64; typedef int INT32; -#else +# else typedef long INT32; -#endif +# endif typedef short INT16; #endif @@ -141,7 +145,7 @@ typedef char INT8; #endif -#ifdef LONG64 +#if defined(LONG64) typedef unsigned long CARD64; typedef unsigned int CARD32; #else @@ -153,7 +157,7 @@ typedef CARD32 BITS32; typedef CARD16 BITS16; -#ifndef __EMX__ +#if !defined(__EMX__) typedef CARD8 BYTE; typedef CARD8 BOOL; #else /* __EMX__ */ @@ -161,33 +165,33 @@ * This is bad style, but the central include file os2.h declares them * as well */ -#define BYTE CARD8 -#define BOOL CARD8 +# define BYTE CARD8 +# define BOOL CARD8 #endif /* __EMX__ */ /* * definitions for sign-extending bitfields on 64-bit architectures */ #if defined(WORD64) defined(UNSIGNEDBITFIELDS) -#define cvtINT8toInt(val) (((val) 0x0080) ? ((val) | 0xff00) : (val)) -#define cvtINT16toInt(val) (((val) 0x8000) ? ((val) | 0x) : (val)) -#define cvtINT32toInt(val) (((val) 0x8000) ? ((val) | 0x) : (val)) -#define cvtINT8toShort(val) cvtINT8toInt(val) -#define cvtINT16toShort(val) cvtINT16toInt(val) -#define cvtINT32toShort(val) cvtINT32toInt(val) -#define cvtINT8toLong(val) cvtINT8toInt(val) -#define cvtINT16toLong(val) cvtINT16toInt(val) -#define cvtINT32toLong(val) cvtINT32toInt(val) -#else -#define cvtINT8toInt(val) (val) -#define cvtINT16toInt(val) (val) -#define cvtINT32toInt(val) (val) -#define cvtINT8toShort(val) (val) -#define cvtINT16toShort(val) (val) -#define cvtINT32toShort(val) (val) -#define cvtINT8toLong(val) (val) -#define cvtINT16toLong(val) (val) -#define cvtINT32toLong(val) (val) +# define cvtINT8toInt(val) (((val) 0x0080) ? ((val) | 0xff00) : (val)) +# define cvtINT16toInt(val) (((val) 0x8000) ? ((val) | 0x) : (val)) +# define cvtINT32toInt(val) (((val) 0x8000) ? ((val) | 0x) : (val)) +# define cvtINT8toShort(val) cvtINT8toInt(val) +# define cvtINT16toShort(val) cvtINT16toInt(val) +# define cvtINT32toShort(val) cvtINT32toInt(val) +# define cvtINT8toLong(val) cvtINT8toInt(val) +# define cvtINT16toLong(val) cvtINT16toInt(val) +# define cvtINT32toLong(val) cvtINT32toInt(val) +#else +# define cvtINT8toInt(val) (val) +# define cvtINT16toInt(val) (val) +# define
Bug#164799: Small typo in generated XF86Config-4
Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. Warren On Tuesday 15 October 2002 09:05 pm, [EMAIL PROTECTED] wrote: No. It's too hard to parse the file reliably. I've asked for code to do it; no one has the time and/or courage. -- Treasurer, GOLUM, Inc. http://www.golum.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#164767: xlibs: altgr doesn't work on german keyboards with altwin:meta_win
Heyho, Branden Robinson [EMAIL PROTECTED] writes: I don't think this is exactly the right solution, but one of the reasons I moved the XKB files into /etc is so that people could resolve these issue for themselves, as you have. That's what I thought, but after the upgrade the keyboard isn't really usable for Germans anymore, so I think Debian should provide a solution to fix that. I don't think that we can expect every german debian-user to know how to fix this issues. Maybe we could give them a hint per debconf or at least per example in /usr/share/doc/. so long... David -- /\ Debian GNU/Linux - _The_ free oprating system David Spreen - [EMAIL PROTECTED] - C8B6823A (keyring.debian.org) \/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#165055: xserver-xfree86: Using DDC breaks X
Package: xserver-xfree86 Version: 4.2.1-2 Severity: important Since the upgrade to X4.2, X is broken. When it starts up, my monitor turns off, and my PC doesn't react to input from the keyboard anymore. Using read/get-edid, I've figured out that the combination of my graphic card and my monitor doesn't support DDC properly (it reports a mode of 4096x4096@9Hz!). Adding Option NoDDC to the Device-section of XF86Config-4 fixes the problem, but the line disappears after every X-update, forcing me to hard-reboot into single-user mode in order to fix it again :(. Please modify the package-configuration to at least honour this setting or let the user choose, if he/she wants to enable DDC during configuration! cheerio, --Chris BTW: The NVidia binary drivers are now broken, too, complaining about missing symbols in __GLsometing (I don't remember, sorry). This probably isn't your responsibility, so I'll have to fight it out with NVidia ;). -- 01:00.0 VGA compatible controller: nVidia Corporation NV5 [Riva TnT2] (rev 15) 01:00.0 Class 0300: 10de:0028 (rev 15) ### 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 FontPathunix/: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 Loadbitmap Loaddbe Loadextmod Loadfreetype Loadint10 Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device/dev/gpmdata Option Protocol ImPS/2 Option ZAxisMapping 4 5 EndSection Section Device Identifier Generic Video Card Driver nv Option NoDDC EndSection Section Monitor Identifier Generic Monitor HorizSync 30-95 VertRefresh 50-150 Option DPMS EndSection Section Screen Identifier Default Screen Device Generic Video Card Monitor Generic Monitor DefaultDepth24 SubSection Display Depth 1 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 4 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 8 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 15 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 16 Modes 1280x1024 1024x768 800x600 640x480 EndSubSection SubSection Display Depth 24 Modes 1280x1024 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 XFree86 Version 4.2.1 (Debian 4.2.1-2 20021008045526 [EMAIL PROTECTED]) / X Window System (protocol Version 11, revision 0, vendor release
Bug#164767: xlibs: altgr doesn't work on german keyboards with altwin:meta_win
On Wed, Oct 16, 2002 at 12:34:48PM +0200, David Spreen wrote: Branden Robinson [EMAIL PROTECTED] writes: I don't think this is exactly the right solution, but one of the reasons I moved the XKB files into /etc is so that people could resolve these issue for themselves, as you have. That's what I thought, but after the upgrade the keyboard isn't really usable for Germans anymore, so I think Debian should provide a solution to fix that. I don't think that we can expect every german debian-user to know how to fix this issues. Maybe we could give them a hint per debconf or at least per example in /usr/share/doc/. I'm not saying Debian shouldn't fix it. I'm saying I lack the specific knowledge to fix it correctly. I don't know that the suggested fix is correct. I'm not going to apply it until I do know that. Therefore I'm asking for German users, especially ones with a clue about XKB, to help make this determination. -- G. Branden Robinson| Good judgement comes from Debian GNU/Linux | experience; experience comes from [EMAIL PROTECTED] | bad judgement. http://people.debian.org/~branden/ | -- Fred Brooks msg04196/pgp0.pgp Description: PGP signature
Bug#164799: Small typo in generated XF86Config-4
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. We'd still have to reverse the transformation because of all the people who modify their XF86Config-4 files and refuse to read the comments at the top of the file. -- G. Branden Robinson|I have a truly elegant proof of the Debian GNU/Linux |above, but it is too long to fit [EMAIL PROTECTED] |into this .signature file. http://people.debian.org/~branden/ | msg04197/pgp0.pgp Description: PGP signature
Bug#165055: marked as done (xserver-xfree86: Using DDC breaks X)
Your message dated Wed, 16 Oct 2002 11:52:42 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#165055: xserver-xfree86: Using DDC breaks X has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 16 Oct 2002 16:03:50 + From [EMAIL PROTECTED] Wed Oct 16 11:03:49 2002 Return-path: [EMAIL PROTECTED] Received: from mailout08.sul.t-online.com [194.25.134.20] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 181qeC-000808-00; Wed, 16 Oct 2002 11:03:48 -0500 Received: from fwd08.sul.t-online.de by mailout08.sul.t-online.com with smtp id 181qe7-0005Hc-0G; Wed, 16 Oct 2002 18:03:43 +0200 Received: from caviar.taylor.vpn (520005476284-0001@[217.230.191.23]) by fmrl08.sul.t-online.com with esmtp id 181qe0-0D9K0eC; Wed, 16 Oct 2002 18:03:36 +0200 Received: from timrod by caviar.taylor.vpn with local (Exim 3.36 #1 (Debian)) id 181qdz-CU-00; Wed, 16 Oct 2002 18:03:35 +0200 From: Christopher Taylor [EMAIL PROTECTED] Subject: xserver-xfree86: Using DDC breaks X To: [EMAIL PROTECTED] X-Mailer: bug 3.3.10.2 Message-Id: [EMAIL PROTECTED] Date: Wed, 16 Oct 2002 18:03:35 +0200 X-Sender: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-1.7 required=5.0 tests=BALANCE_FOR_LONG_20K,SPAM_PHRASE_00_01,SUPERLONG_LINE version=2.41 X-Spam-Level: Package: xserver-xfree86 Version: 4.2.1-2 Severity: important Since the upgrade to X4.2, X is broken. When it starts up, my monitor turns off, and my PC doesn't react to input from the keyboard anymore. Using read/get-edid, I've figured out that the combination of my graphic card and my monitor doesn't support DDC properly (it reports a mode of 4096x4096@9Hz!). Adding Option NoDDC to the Device-section of XF86Config-4 fixes the problem, but the line disappears after every X-update, forcing me to hard-reboot into single-user mode in order to fix it again :(. Please modify the package-configuration to at least honour this setting or let the user choose, if he/she wants to enable DDC during configuration! cheerio, --Chris BTW: The NVidia binary drivers are now broken, too, complaining about missing symbols in __GLsometing (I don't remember, sorry). This probably isn't your responsibility, so I'll have to fight it out with NVidia ;). -- 01:00.0 VGA compatible controller: nVidia Corporation NV5 [Riva TnT2] (rev 15) 01:00.0 Class 0300: 10de:0028 (rev 15) ### 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 FontPathunix/: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 Loadbitmap Loaddbe Loadextmod Loadfreetype Loadint10 Loadspeedo Loadtype1 Loadvbe EndSection Section InputDevice Identifier Generic Keyboard Driver keyboard Option CoreKeyboard Option XkbRules xfree86 Option XkbModel pc105 Option XkbLayout de Option XkbVariantnodeadkeys EndSection Section InputDevice Identifier Configured Mouse Driver mouse Option CorePointer Option Device
Re: [XF86 4.2.1] Blackdown JVM and Japanese Menu.
Dear Branden, I found Blackdown-Java 1.4.1beta (not deb'ed) can display KANJI at XF86 4.2.1-2, but 1.3.1 (deb'ed) can't display KANJI on menubar at XF86 4.2.1-2. Written by ChanChan KO [EMAIL PROTECTED] at Wed, 02 Oct 2002 01:56:06 +0900 (JST) : Subject: Re: [XF86 4.2.1] Blackdown JVM and Japanese Menu. chanchan Dear Branden, chanchan chanchan Written by Branden Robinson [EMAIL PROTECTED] chanchanat Tue, 1 Oct 2002 11:30:27 -0500 : chanchan Subject: Re: [XF86 4.2.1] Blackdown JVM and Japanese Menu. chanchan chanchan branden On Wed, Oct 02, 2002 at 12:56:57AM +0900, ChanChan KO wrote: chanchan branden Package: xserver-xfree86 chanchan branden Version: 4.2.1-0pre1v2 chanchan branden Architecture: i386 chanchan branden Severity: Normal chanchan (Snip) chanchan branden Is the JVM a setuid or setgid program? (Snip) Maybe, this isssue is not from XF86 , problem of older Blackdown JVM. Best Regards, ChanChan. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#164799: Small typo in generated XF86Config-4
On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. The code to parse the file has got to be somewhere in the xfree source. Somebody probably even knows where. Somebody might even know how. Surely we can ask him? You probably have never tried to use XML+XSLT on a pb1400... -- John Lenton ([EMAIL PROTECTED]) -- Random fortune: Do not underestimate the value of print statements for debugging. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#164799: Small typo in generated XF86Config-4
Well, there is actually a library for parsing the config file in xc/programs/Xserver/hw/xfree86/parser . Warren On Wednesday 16 October 2002 11:51 am, [EMAIL PROTECTED] wrote: On Wed, Oct 16, 2002 at 03:12:51AM -0500, Warren Turkal wrote: Would XML be any easier to parse? We could have an XML config file and an XSLT to transform it into the real config file. We'd still have to reverse the transformation because of all the people who modify their XF86Config-4 files and refuse to read the comments at the top of the file. -- Treasurer, GOLUM, Inc. http://www.golum.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RE: XFree4.2 - unstable?
Hey, I was able to finally get my indy to boot at 1280x1024, with setenv monitor H in the prom. This is for my SGI Indy, Newport 24-bit graphics, and my monitor is a Radius PrecisionColor Display/20 a.k.a. Sony GDM-1971. I hope 1024x768 will be supported eventually, though. -brad -Original Message- From: Guido Guenther [mailto:[EMAIL PROTECTED]]On Behalf Of Guido Guenther Sent: Thursday, September 19, 2002 3:29 PM To: Bradley Bell Cc: [EMAIL PROTECTED] Subject: Re: XFree4.2 - unstable? On Thu, Sep 19, 2002 at 03:16:07PM -0700, Bradley Bell wrote: NG1: Revision 6, 24 bitplanes, REX3 revision B, VC2 revision A, xmap9 revision A, cmap revision D, bt9445 revision D NG1: Screensize 1024x768 Console: colour SGI Newport 128x48 I'm pretty sure the monitor can support 1280x1024. (Radius PrecisionColor Display/20 a.k.a. Sony GDM-1971). any ideas? Maybe I've found the problem. Did you boot with console=d1 set in the PROM. I'll get 1024x768 when I do that and 1280x1024 when I boot with console=g1. I'll fix that, but don't hold your breath. Regards, -- Guido P.S.: and let's move this off -private and to -x or something. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: XFree4.2 - unstable?
On Wed, Oct 16, 2002 at 03:35:57PM -0700, Bradley Bell wrote: Hey, I was able to finally get my indy to boot at 1280x1024, with setenv monitor H in the prom. Great! Where did you get that info from? I know there's a place in the nvram that stores the monitor type, but I didn't know one can set it from within the prom monitor. Do you know what other monitor types one can set? Maybe (H=high res, L=low res)? [..snip..] I hope 1024x768 will be supported eventually, though. It will. As soon as I get around to work on X again. Regards, -- Guido -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#165134: xlibs: [xkb] symbol change in us keyboard disables Meta and Compose key
Package: xlibs
Version: 4.2.1-2
Severity: normal
xlibs version 4.1.0-16 (Debian 3.0) contains:
// definition for the extra keys on 104-key Windows95 keyboards
xkb_symbols pc104 {
include us(generic101)
key LALT {[ Alt_L ] };
key RALT {[ Alt_R ] };
key LWIN {[ Meta_L ] };
key RWIN {[ Multi_key ] };
key MENU {[ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R };
modifier_map Mod4 { Meta_L, Meta_R };
};
whereas thone supplied in this version is:
xkb_symbols pc104 {
include us(generic101)
key LALT {[ Alt_L, Meta_L ] };
key RALT {[ Alt_R, Meta_R ] };
key LWIN {[ Super_L ] };
key RWIN {[ Super_R ] };
key MENU {[ Menu] };
// modifier mappings
modifier_map Mod1 { Alt_L, Alt_R, Meta_L, Meta_R };
modifier_map Mod4 { Super_L, Super_R };
};
The Windows keys on upgrade don't send Meta anymore. Personally I prefer
the definition supplied with Debian 3.0 (Left Windows is Meta, Right
Windows is Compose).
This breaks upgrades (and if it isn't going to be changed should be
noted on future release notes) and seem somewhat gratuitous. What is the
Super key and why do I need one?
Anand
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux clam 2.4.17 #13 Mon Mar 18 12:31:14 EST 2002 i686
Locale: LANG=C, LC_CTYPE=
Versions of packages xlibs depends on:
ii libc6 2.2.5-15 GNU C Library: Shared libraries an
ii libfreetype6 2.1.2-8FreeType 2 font engine, shared lib
ii xfree86-common4.2.1-2X Window System (XFree86) infrastr
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Problem with X 4.2.1 and Matrox G400 dual-head setup
Hi, I've been running a dual-head setup for some time with a 16 MB Matrox G400, but the last X upgrade (from 4.2.0 to 4.2.1) seems to have bonked the dual head support. Enclosed is a failure log and a copy of my XF86Config-4 file. Note that the line for the second screen in the Server Layout section is commented out, the log shows what happens when that line is enabled. Note that the Xinerama line is commented out, I don't use Xinerama. I'm glad to provide any other info, etc. Regards, PM -- Paul Mackinney [EMAIL PROTECTED] ---BeginMessage--- (WW) Open APM failed (/dev/apm_bios) (No such file or directory) (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 = 0x80010040, mode1Res1 = 0x8000 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 8086,7190 card , rev 03 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 8086,7191 card , rev 03 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 8086,7110 card , rev 02 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 8086,7111 card , rev 01 class 01,01,80 hdr 00 (II) PCI: 00:07:2: chip 8086,7112 card , rev 01 class 0c,03,00 hdr 00 (II) PCI: 00:07:3: chip 8086,7113 card , rev 02 class 06,80,00 hdr 00 (II) PCI: 00:09:0: chip 1011,0002 card , rev 23 class 02,00,00 hdr 00 (II) PCI: 00:0d:0: chip 9004,8178 card , rev 00 class 01,00,00 hdr 00 (II) PCI: 00:11:0: chip 1274,1371 card 1274,1371 rev 02 class 04,01,00 hdr 00 (II) PCI: 01:00:0: chip 102b,0525 card 102b,2159 rev 05 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) LoadModule: scanpci (II) Loading /usr/X11R6/lib/modules/libscanpci.a (II) Module scanpci: vendor=The XFree86 Project compiled for 4.2.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) PCI-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (-1,0,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus 0 I/O range: [0] -1 00x - 0x (0x1) IX[B] (II) Bus 0 non-prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 0 prefetchable memory range: [0] -1 00x - 0x (0x0) MX[B] (II) Bus 1: bridge is at (0:1:0), (0,1,1), BCTRL: 0x88 (VGA_EN is set) (II) Bus 1 I/O range: (II) Bus 1 non-prefetchable memory range: [0] -1 00xd400 - 0xd7ff (0x400) MX[B] (II) Bus 1 prefetchable memory range: [0] -1 00xd800 - 0xd9ff (0x200) MX[B] (II) Bus -1: bridge is at (0:7:0), (0,-1,0), BCTRL: 0x08 (VGA_EN is set) (II) Bus -1 I/O range: (II) Bus -1 non-prefetchable memory range: (II) Bus -1 prefetchable memory range: (--) PCI:*(1:0:0) Matrox MGA G400 AGP rev 5, Mem @ 0xd800/25, 0xd400/14, 0xd500/23 (II) Addressable bus resource ranges are [0] -1 00x - 0x (0x0) MX[B] [1] -1 00x - 0x (0x1) IX[B] (II) OS-reported resource ranges: [0] -1 00xffe0 - 0x (0x20) MX[B](B) [1] -1 00x0010 - 0x3fff (0x3ff0) MX[B]E(B) [2] -1 00x000f - 0x000f (0x1) MX[B] [3] -1 00x000c - 0x000e (0x3) MX[B] [4] -1 00x - 0x0009 (0xa) MX[B] [5] -1 00x - 0x (0x1) IX[B] [6] -1 00x - 0x00ff (0x100) IX[B] (II) Active PCI resource ranges: [0] -1 00xdb00 - 0xdb000fff (0x1000) MX[B] [1] -1 00xdb001000 - 0xdb00107f (0x80) MX[B] [2] -1 00xd000 - 0xd3ff (0x400) MX[B] [3] -1 00xd500 - 0xd57f (0x80) MX[B](B) [4] -1 00xd400 - 0xd4003fff (0x4000) MX[B](B) [5] -1 00xd800 - 0xd9ff (0x200) MX[B](B) [6] -1 00xec00 - 0xec3f (0x40) IX[B] [7] -1 00xe800 - 0xe8ff (0x100) IX[B] [8] -1 00xe400 - 0xe47f (0x80) IX[B] [9] -1 00xe000 -
