Bug#391052: xserver-xorg: Control-Alt-Keypad Plus/Minus not recognized
On Thu, Oct 05, 2006 at 12:04:44AM +0200, Denis Barbier wrote: > Does other Ctrl-Alt combinations work, like Ctrl-Alt-F1 to switch > to a console? Yes, all other Ctrl-Alt combinations appear to work including Ctrl-Alt-F# and Ctrl-Alt-Backspace. It's only Keypad-Plus and Minus that don't work. Check that, Ctrl-Alt-Keypad-Multiply and Divide appear dead to Xev also. David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#391052: xserver-xorg: Control-Alt-Keypad Plus/Minus not recognized
Package: xserver-xorg Version: 1:7.1.0-1 Severity: normal Sorry about not knowing which package to actually report this against. I've been trying to isolate it myself off and on and have been unable to do so. Since the xserver-xorg updates from around September 18, I've been unable to change resolutions using the control-alt-keypad plus/minus key combination. Running Xev shows all of the keys being recognized indidually and in combinations of any 2. Using control, alt and either keypad plus or minus together though isn't recognized by Xev. The only suspicious thing I've found in trying to isolate the problem is an error message in /var/log/Xorg.0.log. The following entry started appearing on some of my systems when this problem started. (EE) Error loading keymap /var/lib/xkb/server-0.xkm David [EMAIL PROTECTED] -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17.13 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xserver-xorg depends on: ii debconf 1.5.5 Debian configuration management sy ii nvidia-glx [xserver-xorg-vide 1.0.8774-3 NVIDIA binary XFree86 4.x driver ii x11-common1:7.1.0-1 X Window System (X.Org) infrastruc ii xbase-clients 1:7.1.ds-3 miscellaneous X clients ii xkb-data 0.8-16 X Keyboard Extension (XKB) configu ii xserver-xorg-core 2:1.1.1-9 X.Org X server -- core server ii xserver-xorg-input-all1:7.1.0-1 the X.Org X server -- input driver ii xserver-xorg-input-evdev [xse 1:1.1.2-3 X.Org X server -- evdev input driv ii xserver-xorg-input-kbd [xserv 1:1.1.0-3 X.Org X server -- keyboard input d ii xserver-xorg-input-mouse [xse 1:1.1.1-3 X.Org X server -- mouse input driv Versions of packages xserver-xorg recommends: pn discover1 | discover (no description available) pn laptop-detect (no description available) pn mdetect(no description available) pn xresprobe (no description available) -- debconf information: * xserver-xorg/multiple_possible_x-drivers: * xserver-xorg/config/monitor/use_sync_ranges: true * xserver-xorg/config/inputdevice/mouse/port: /dev/input/mice * xserver-xorg/config/monitor/lcd: false * xserver-xorg/config/doublequote_in_string_error: xserver-xorg/config/monitor/screen-size: 17 inches (430 mm) * shared/default-x-server: xserver-xorg xserver-xorg/config/device/default-identifier: * xserver-xorg/autodetect_monitor: true * xserver-xorg/config/inputdevice/mouse/protocol: ImPS/2 * shared/no_known_x-server: * xserver-xorg/config/display/default_depth: 24 * xserver-xorg/config/display/modes: 1280x960, 1152x864, 1024x768, 800x600, 640x480 * xserver-xorg/config/device/bus_id_error: * xserver-xorg/config/inputdevice/keyboard/internal: * xserver-xorg/config/monitor/vert-refresh: 48-170 * xserver-xorg/config/inputdevice/keyboard/options: * xserver-xorg/autodetect_keyboard: false * xserver-xorg/config/device/use_fbdev: false * xserver-xorg/config/inputdevice/keyboard/variant: * xserver-xorg/config/nonnumeric_string_error: xserver-xorg/config/fontpath/fontserver: * xserver-xorg/config/inputdevice/keyboard/layout: us * xserver-xorg/config/modules: bitmap, dbe, ddc, extmod, freetype, glx, int10, record, type1, vbe * xserver-xorg/config/monitor/identifier: Genric Monitor * xserver-xorg/config/inputdevice/mouse/emulate3buttons: false * xserver-xorg/autodetect_mouse: true * xserver-xorg/config/monitor/horiz-sync: 30-130 * xserver-xorg/config/device/video_ram: * xserver-xorg/config/monitor/range_input_error: * xserver-xorg/config/write_dri_section: false * xserver-xorg/config/inputdevice/keyboard/model: pc104 * xserver-xorg/config/device/driver: nvidia * xserver-xorg/config/device/identifier: NVIDIA Card * xserver-xorg/config/monitor/selection-method: Advanced * xserver-xorg/config/null_string_error: * shared/multiple_possible_x-servers: * xserver-xorg/config/device/bus_id: * xserver-xorg/config/write_files_section: true * xserver-xorg/autodetect_video_card: true * xserver-xorg/config/monitor/mode-list: 1280x960 @ 60Hz * xserver-xorg/config/inputdevice/keyboard/rules: xorg xserver-xorg/config/monitor/default-identifier: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Big fonts with KDE and X4v30
On Fri, Nov 03, 2000 at 01:53:30AM -0500, Branden Robinson wrote: > In an effort to impose some kind of consistency in the X font world, I have > made X's default dpi preference 100. I was able to go home for lunch and give this a try. It did the trick. Thanks. David -- David Engel [EMAIL PROTECTED]
Re: Big fonts with KDE and X4v30
On Fri, Nov 03, 2000 at 01:53:30AM -0500, Branden Robinson wrote: > In an effort to impose some kind of consistency in the X font world, I have > made X's default dpi preference 100. I was able to go home for lunch and give this a try. It did the trick. Thanks. David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Big fonts with KDE and X4v30
On Fri, Nov 03, 2000 at 01:53:30AM -0500, Branden Robinson wrote: > In an effort to impose some kind of consistency in the X font world, I have > made X's default dpi preference 100. > ... > You may also want to reorder the FontPaths in Dexter-generated XF86Config > files, if you have any. OK. I'll try these tonight when I get home. David -- David Engel [EMAIL PROTECTED]
Re: Big fonts with KDE and X4v30
On Fri, Nov 03, 2000 at 01:53:30AM -0500, Branden Robinson wrote: > In an effort to impose some kind of consistency in the X font world, I have > made X's default dpi preference 100. > ... > You may also want to reorder the FontPaths in Dexter-generated XF86Config > files, if you have any. OK. I'll try these tonight when I get home. David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Big fonts with KDE and X4v30
Is anyone else having problems with fonts in KDE apps in X4v30? I just upgraded to the v30 X packages and the fonts in all KDE apps are roughly 33% larger than they should be. For example, I have to choose an 18 pt font under KDE to get what is really a 24 pt font. I've tried wiping out my .kde directory, using the 75 dpi fonts instead of the 100 dpi fonts, using the libGLU from the mesag3 package instead of the new one from the xlibmesa3 package and using the nv driver instead of the nvidia driver and the problem persists. David -- David Engel [EMAIL PROTECTED]
Big fonts with KDE and X4v30
Is anyone else having problems with fonts in KDE apps in X4v30? I just upgraded to the v30 X packages and the fonts in all KDE apps are roughly 33% larger than they should be. For example, I have to choose an 18 pt font under KDE to get what is really a 24 pt font. I've tried wiping out my .kde directory, using the 75 dpi fonts instead of the 100 dpi fonts, using the libGLU from the mesag3 package instead of the new one from the xlibmesa3 package and using the nv driver instead of the nvidia driver and the problem persists. David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: I am a stupid idiot for posting a FAQ, but...
On Mon, Oct 30, 2000 at 09:38:45PM -0500, Buddha Buck wrote: > What I want to know is if anyone knows of a work-around until the > situation is fixed properly. I suspect that this has been answered > before, but I can't seem to find it. I extracted libGLU.so.1.1.030201 from the mesag3 package, put it in /usr/local/lib and then ran ldconfig. David -- David Engel [EMAIL PROTECTED]
Re: I am a stupid idiot for posting a FAQ, but...
On Mon, Oct 30, 2000 at 09:38:45PM -0500, Buddha Buck wrote: > What I want to know is if anyone knows of a work-around until the > situation is fixed properly. I suspect that this has been answered > before, but I can't seem to find it. I extracted libGLU.so.1.1.030201 from the mesag3 package, put it in /usr/local/lib and then ran ldconfig. David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: another app killed
On Mon, Oct 30, 2000 at 10:17:27PM +0100, Wichert Akkerman wrote: > jpilot doesn't work with X4: FWIW, I haven't had any prolems with jpilot and X4. I just did my weekly backup with 4.0.1-0phase2v27. David -- David Engel [EMAIL PROTECTED]
Re: another app killed
On Mon, Oct 30, 2000 at 10:17:27PM +0100, Wichert Akkerman wrote: > jpilot doesn't work with X4: FWIW, I haven't had any prolems with jpilot and X4. I just did my weekly backup with 4.0.1-0phase2v27. David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Trouble with DRI on G200
On Fri, Oct 06, 2000 at 11:59:28AM -0600, Joshua Shagam wrote: > Did you later see 'DMA initialization failed?' That would be the No. Here are the DMA messages I got: (II) MGA(0): [drm] Registers = 0xe400 [drm] drmAgpEnabled succeeded (II) MGA(0): WARP Microcode Loaded (II) MGA(0): [drm] calced backoffset: 0x22f000 (II) MGA(0): [drm] added 31 65536 byte DMA buffers (II) MGA(0): [drm] Mga Dma Initialization start (II) MGA(0): [drm] Mga Dma Initialization done (II) MGA(0): [drm] Initialized Dma Engine (II) MGA(0): [drm] dma control initialized, using IRQ 11 (II) MGA(0): visual configs initialized (II) MGA(0): Using 128 lines for offscreen memory. (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) This issue is mostly moot anyway. My main point in trying XFree86 4.0.x with the G200 was to smooth the transition when I move my hard disks to my new system which has a GeForce2/MX. > What I do is I use the libGL from xlibmesa3 and the libGLU compiled from > Mesa's sources (which I already have on-hand because of formerly using > Utah-GLX). I just copied libGLU from mesag3 to /usr/local/lib. On Fri, Oct 06, 2000 at 01:02:12PM -0500, Branden Robinson wrote: > The patches you're talking about aren't really Debian-specific: Debian-specifici was probably a poor choice of words. My intent was that the change was not in the plain 4.0.1 upstream version. > Please review my mini-FAQ, last posted to this list on Oct 1. Sorry about that. I read your mini-FAQ when it was sent, but I didn't understand the issue and I also didn't think I was using anything that needed libGLU either so I didn't worry about it. Anyway, have you considered using a dpkg-diversion? xlibmesa3 could divert any existing libGL out of the way but leave libGLU in place. David -- David Engel [EMAIL PROTECTED]
Re: Trouble with DRI on G200
On Fri, Oct 06, 2000 at 11:59:28AM -0600, Joshua Shagam wrote: > Did you later see 'DMA initialization failed?' That would be the No. Here are the DMA messages I got: (II) MGA(0): [drm] Registers = 0xe400 [drm] drmAgpEnabled succeeded (II) MGA(0): WARP Microcode Loaded (II) MGA(0): [drm] calced backoffset: 0x22f000 (II) MGA(0): [drm] added 31 65536 byte DMA buffers (II) MGA(0): [drm] Mga Dma Initialization start (II) MGA(0): [drm] Mga Dma Initialization done (II) MGA(0): [drm] Initialized Dma Engine (II) MGA(0): [drm] dma control initialized, using IRQ 11 (II) MGA(0): visual configs initialized (II) MGA(0): Using 128 lines for offscreen memory. (II) MGA(0): Using XFree86 Acceleration Architecture (XAA) This issue is mostly moot anyway. My main point in trying XFree86 4.0.x with the G200 was to smooth the transition when I move my hard disks to my new system which has a GeForce2/MX. > What I do is I use the libGL from xlibmesa3 and the libGLU compiled from > Mesa's sources (which I already have on-hand because of formerly using > Utah-GLX). I just copied libGLU from mesag3 to /usr/local/lib. On Fri, Oct 06, 2000 at 01:02:12PM -0500, Branden Robinson wrote: > The patches you're talking about aren't really Debian-specific: Debian-specifici was probably a poor choice of words. My intent was that the change was not in the plain 4.0.1 upstream version. > Please review my mini-FAQ, last posted to this list on Oct 1. Sorry about that. I read your mini-FAQ when it was sent, but I didn't understand the issue and I also didn't think I was using anything that needed libGLU either so I didn't worry about it. Anyway, have you considered using a dpkg-diversion? xlibmesa3 could divert any existing libGL out of the way but leave libGLU in place. David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Trouble with DRI on G200
Hi All, I'm trying to get DRI working on my Matrox G200 and not having much luck. Most of this is probably due to my ignorance of Linux 3d support, but since it involves Debian specific changes to X, I thought I'd ask here first. I first tried using the stock 4.0.1-0phase2v13 X packages with kernel 2.2.18pre15 and got the following message from the X server: (EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 1.0.0, expected 2.0.x). Disabling DRI. It seems the Debian diff for 4.0.1-0phase2v13 has patched the mga_drv X module to require a newer version of the mga kernel module, which AFAICT, is only available in the 2.4 kernel. I'd rather not switch to the 2.4 kernel yet. Does anyone know of a newer version of the mga kernel module for the 2.2 kernel? I then tried replacing the mga_drv X module with one from the Matrox ftp site that appeared to work with the 1.0.x mga kernel module and got the following messages: (0): [drm] installed DRM signal handler (0): [DRI] installation complete (II) MGA(0): direct rendering enabled However, glxinfo claimed direct rendering was not enabled, and sure enough, there was no improvement over software renedering when running 3d apps. FYI, another partly related problem I've run into is that the mesag3 package contains libGL and libGLU but the xlibmesa3 package only contains libGL. What package is supposed to provide libGLU when xlibmesa3 is used? David -- David Engel [EMAIL PROTECTED]
Trouble with DRI on G200
Hi All, I'm trying to get DRI working on my Matrox G200 and not having much luck. Most of this is probably due to my ignorance of Linux 3d support, but since it involves Debian specific changes to X, I thought I'd ask here first. I first tried using the stock 4.0.1-0phase2v13 X packages with kernel 2.2.18pre15 and got the following message from the X server: (EE) MGA(0): [drm] MGADRIScreenInit failed (DRM version = 1.0.0, expected 2.0.x). Disabling DRI. It seems the Debian diff for 4.0.1-0phase2v13 has patched the mga_drv X module to require a newer version of the mga kernel module, which AFAICT, is only available in the 2.4 kernel. I'd rather not switch to the 2.4 kernel yet. Does anyone know of a newer version of the mga kernel module for the 2.2 kernel? I then tried replacing the mga_drv X module with one from the Matrox ftp site that appeared to work with the 1.0.x mga kernel module and got the following messages: (0): [drm] installed DRM signal handler (0): [DRI] installation complete (II) MGA(0): direct rendering enabled However, glxinfo claimed direct rendering was not enabled, and sure enough, there was no improvement over software renedering when running 3d apps. FYI, another partly related problem I've run into is that the mesag3 package contains libGL and libGLU but the xlibmesa3 package only contains libGL. What package is supposed to provide libGLU when xlibmesa3 is used? David -- David Engel [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
