Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
2009/12/13 walt w41...@gmail.com: On 12/12/2009 04:20 PM, Mick wrote: ... I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? That twm session is the default (see end of /etc/X11/xinit/xinitrc) if you don't specify what you really want. The xdm display manager checks in ~/.xsession for the stuff you want to run (i.e. fluxbox), but startx uses the file ~/.xinitrc for the same purpose. You could probably just copy .xsession to .xinitrc for starters. OK, but I never had set up ~/.xsession or ~/.xinitrc files. This is a single user machine. As far as I can recall I had only set up in /etc/rc.conf the parameter XSESSION=fluxbox, which looked in /etc/X11/Sessions/ and ran the fluxbox configuration file that I had in there. Looking at /etc/conf.d/xdm I see this: = # What display manager do you use ? [ xdm | gdm | kdm | kdm-4.3 | gpe | entrance ] # NOTE: If this is set in /etc/rc.conf, that setting will override this one. = In that file I have specified DISPLAYMANAGER=xdm. Again as far as I recall this is how I had set things up, so I am not sure what has changed recently. Setting a ~/.xinitrc file with 'exec startfluxbox' in it starts fluxbox nicely if I run startx from the console - but this is not the same session that I would get which would also include xconsole. I found these messages now, but no significant errors: = Setting CPU scaling governor performance for CPU 1... could not open file /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor for writing! failed setting 'performance' CPUfreq governor! Failed to read: session.screen0.maxIgnoreIncrement Setting default value Failed to read: session.screen0.maxDisableMove Setting default value Failed to read: session.screen0.maxDisableResize Setting default value Failed to read: session.screen0.noFocusWhileTypingDelay Setting default value Failed to read: session.screen0.tooltipDelay Setting default value Failed to read: session.screen0.clientMenu.usePixmap Setting default value Failed to read: session.screen0.maxIgnoreIncrement Setting default value Failed to read: session.screen0.maxDisableMove Setting default value Failed to read: session.screen0.maxDisableResize Setting default value Failed to read: session.screen0.noFocusWhileTypingDelay Setting default value Failed to read: session.screen0.tooltipDelay Setting default value Failed to read: session.screen0.clientMenu.usePixmap Setting default value Failed to read: session.screen0.maxIgnoreIncrement Setting default value Failed to read: session.screen0.maxDisableMove Setting default value Failed to read: session.screen0.maxDisableResize Setting default value Failed to read: session.screen0.noFocusWhileTypingDelay Setting default value Failed to read: session.screen0.tooltipDelay Setting default value Failed to read: session.screen0.clientMenu.usePixmap Setting default value Failed to read: session.screen0.slit.acceptKdeDockapps Setting default value = So, what would be the way to start xdm and have xdm starting fluxbox? -- Regards, Mick
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
2009/12/11 Mick michaelkintz...@gmail.com: Hi All, I emerged xorg-server-1.6.5-r1, as well as x11-drivers/xf86-input-synaptics-1.2.0, xf86-input-keyboard-1.4.0, xf86-input-mouse-1.5.0 and xf86-input-evdev-2.3.1 and now I can't get past the xdm login screen. It is worth noting that I also emerged a load of apps including xkbcomp-1.1.1 and xinit-1.2.0-r3. When I enter my passwd at the xdm login it takes a couple of seconds and it drops me back into the login screen. The xdm.log mentions: === X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-gentoo-r6 i686 Current Operating System: Linux lappy 2.6.31-gentoo-r6 #1 Fri Nov 27 07:32:41 GMT 2009 i686 Build Date: 11 December 2009 11:36:44AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. 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/Xorg.0.log, Time: Fri Dec 11 20:10:50 2009 (==) Using default built-in configuration (30 lines) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) NTSC PAL PAL-M XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_DAC1 DDC reg: 0x60 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVDS DDC reg: 0x1a0 XRANDR name: S-video Connector: S-video TV1: INTERNAL_DAC2 DDC reg: 0x0 finished output detect: 0 finished output detect: 1 finished output detect: 2 finished all detect before xf86InitialConfiguration after xf86InitialConfiguration Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV expected keysym, got XF86TouchpadToggle: line 122 of inet The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server /etc/X11/xdm/Xresources:31:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:32:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:33:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:34:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:35:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:36:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:37:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:38:2: error: invalid preprocessing directive #xlogin XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 117 requests (109 known processed) with 0 events remaining. disable LVDS finished PLL2 Entering Restore TV Restore TV PLL Restore TVHV Restore TV Restarts Restore Timing Tables Restore TV standard Leaving Restore TV error setting MTRR (base = 0x4800, size = 0x0100, type = 1) Invalid argument (22) Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV (EE) XKB: No components provided for device Virtual core keyboard The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
2009/12/12 Mick michaelkintz...@gmail.com: 2009/12/11 Mick michaelkintz...@gmail.com: Hi All, I emerged xorg-server-1.6.5-r1, as well as x11-drivers/xf86-input-synaptics-1.2.0, xf86-input-keyboard-1.4.0, xf86-input-mouse-1.5.0 and xf86-input-evdev-2.3.1 and now I can't get past the xdm login screen. It is worth noting that I also emerged a load of apps including xkbcomp-1.1.1 and xinit-1.2.0-r3. When I enter my passwd at the xdm login it takes a couple of seconds and it drops me back into the login screen. The xdm.log mentions: === X.Org X Server 1.6.5 Release Date: 2009-10-11 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.31-gentoo-r6 i686 Current Operating System: Linux lappy 2.6.31-gentoo-r6 #1 Fri Nov 27 07:32:41 GMT 2009 i686 Build Date: 11 December 2009 11:36:44AM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. 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/Xorg.0.log, Time: Fri Dec 11 20:10:50 2009 (==) Using default built-in configuration (30 lines) (EE) Failed to load module vesa (module does not exist, 0) (EE) Failed to load module fbdev (module does not exist, 0) NTSC PAL PAL-M XRANDR name: VGA-0 Connector: VGA CRT1: INTERNAL_DAC1 DDC reg: 0x60 XRANDR name: LVDS Connector: LVDS LCD1: INTERNAL_LVDS DDC reg: 0x1a0 XRANDR name: S-video Connector: S-video TV1: INTERNAL_DAC2 DDC reg: 0x0 finished output detect: 0 finished output detect: 1 finished output detect: 2 finished all detect before xf86InitialConfiguration after xf86InitialConfiguration Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV expected keysym, got XF86TouchpadToggle: line 122 of inet The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server /etc/X11/xdm/Xresources:31:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:32:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:33:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:34:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:35:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:36:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:37:2: error: invalid preprocessing directive #xlogin /etc/X11/xdm/Xresources:38:2: error: invalid preprocessing directive #xlogin XIO: fatal IO error 11 (Resource temporarily unavailable) on X server :0.0 after 117 requests (109 known processed) with 0 events remaining. disable LVDS finished PLL2 Entering Restore TV Restore TV PLL Restore TVHV Restore TV Restarts Restore Timing Tables Restore TV standard Leaving Restore TV error setting MTRR (base = 0x4800, size = 0x0100, type = 1) Invalid argument (22) Entering TV Save Save TV timing tables saveTimingTables: reading timing tables TV Save done disable LVDS disable primary dac disable LVDS disable TV disable LVDS init memmap init common init crtc1 init pll1 restore memmap restore common restore crtc1 restore pll1 set RMX set LVDS enable LVDS disable primary dac disable TV (EE) XKB: No components provided for device Virtual core keyboard The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got XF86TouchpadToggle: line 122 of inet Errors from xkbcomp are not fatal to the X server The XKEYBOARD keymap compiler (xkbcomp) reports: Warning: Symbol map for key KPDL redefined Using last definition for conflicting fields expected keysym, got
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009 12:55 AM, Mick wrote: ... Not sure if it is related but I am getting this: Regenerating /etc/ld.so.cache... /sbin/ldconfig: /usr/lib/libltdl.so.3 is not a symbolic link What does this mean? revdep-rebuild does not show anything needing to be rebuilt. That must be a very old file. Here's what I have: -rw-r--r-- 1 root root 41652 2009-12-08 06:30 /usr/lib/libltdl.a -rw-r--r-- 1 root root 919 2009-12-08 06:30 /usr/lib/libltdl.la lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so - libltdl.so.7.2.1* lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so.7 - libltdl.so.7.2.1* -rwxr-xr-x 1 root root 34252 2009-12-08 06:30 /usr/lib/libltdl.so.7.2.1* If you also have these files then just delete the so.3 version. Otherwise, I've downgraded xkbcomp with no joy and now I am downgrading xorg-server to see if this has any effect. I'm struggling to understand all the keyboard stuff too. Do you still use an xorg.conf file? If you are using evdev then you should not be using the xf86-input-mouse or xf86-input-keyboard drivers, just the xf86-input-evdev driver. I have the entire input section of xorg.conf commented out and evdev seems to be the default input driver now. I'll bet xdm is hiding the really helpful error messages, so I would shut off xdm and use startx to see if you get any better information.
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009, walt w41...@gmail.com wrote: On 12/12/2009 12:55 AM, Mick wrote: ... Not sure if it is related but I am getting this: Regenerating /etc/ld.so.cache... /sbin/ldconfig: /usr/lib/libltdl.so.3 is not a symbolic link What does this mean? revdep-rebuild does not show anything needing to be rebuilt. That must be a very old file. Here's what I have: -rw-r--r-- 1 root root 41652 2009-12-08 06:30 /usr/lib/libltdl.a -rw-r--r-- 1 root root 919 2009-12-08 06:30 /usr/lib/libltdl.la lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so - libltdl.so.7.2.1* lrwxrwxrwx 1 root root16 2009-12-08 06:31 /usr/lib/libltdl.so.7 - libltdl.so.7.2.1* -rwxr-xr-x 1 root root 34252 2009-12-08 06:30 /usr/lib/libltdl.so.7.2.1* Mine are slightly different. I also have /usr/lib/lbltdl.so.0 - libltdl.so.0.1.2 and also have libltdl.so.0.1.2 libltdl.so.3 libltdl.so.3.1.0 If you also have these files then just delete the so.3 version. Thanks, I'll check for dependencies and then remove them. Otherwise, I've downgraded xkbcomp with no joy and now I am downgrading xorg-server to see if this has any effect. I'm struggling to understand all the keyboard stuff too. Do you still use an xorg.conf file? If you are using evdev then you should not be using the xf86-input-mouse or xf86-input-keyboard drivers, just the xf86-input-evdev driver. I have the entire input section of xorg.conf commented out and evdev seems to be the default input driver now. I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? I'll bet xdm is hiding the really helpful error messages, so I would shut off xdm and use startx to see if you get any better information. Thanks, will try that too. -- Regards, Mick
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009 03:14 PM, Mick wrote: ... I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I know nothing about the synaptics driver, so be careful about deleting it. Maybe rename it instead of deleting it? I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? That depends on what hardware you have -- a lot of the stuff that once went into xorg.conf can be put in an fdi file now. Here is an example: I have an unusual mouse with four buttons and no wheel, and I use one extra button to simulate a mouse wheel: $cat /etc/hal/fdi/policy/10-x11-logitech.fdi ?xml version=1.0 encoding=ISO-8859-1? deviceinfo version=0.2 device match key=info.product contains=ImExPS/2 merge key=input.x11_options.EmulateWheel type=stringtrue/merge merge key=input.x11_options.EmulateWheelButton type=string8/merge /match /device /deviceinfo The two lines with input.x11_options used to be in my xorg.conf in the Input section. Those lines do the same thing now that I've moved them into an fdi file.
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009, walt w41...@gmail.com wrote: On 12/12/2009 03:14 PM, Mick wrote: ... I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I know nothing about the synaptics driver, so be careful about deleting it. Maybe rename it instead of deleting it? Nope, unmerged it and deleted it from make.conf, then when I emerged xf86-video-ati and evdev all other drivers (mouse, keyboard, synaptics) were brought in as well. I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? That depends on what hardware you have -- a lot of the stuff that once went into xorg.conf can be put in an fdi file now. Here is an example: Thanks for that. I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? No /var/log/xdm.log or other errors were there this time. Trying to start xdm and I keep getting the same old errors: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0) and (EE) XKB: No components provided for device Virtual core keyboard. I am running out of things to try now. I don't have a recent enough back up otherwise I would roll back this bad experience. -- Regards, Mick
[gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
On 12/12/2009 04:20 PM, Mick wrote: ... I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? That twm session is the default (see end of /etc/X11/xinit/xinitrc) if you don't specify what you really want. The xdm display manager checks in ~/.xsession for the stuff you want to run (i.e. fluxbox), but startx uses the file ~/.xinitrc for the same purpose. You could probably just copy .xsession to .xinitrc for starters. No /var/log/xdm.log or other errors were there this time. Trying to start xdm and I keep getting the same old errors: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0) and (EE) XKB: No components provided for device Virtual core keyboard. I am running out of things to try now. I don't have a recent enough back up otherwise I would roll back this bad experience. I have these lines in my xorg.conf but I can't remember when or why I put them there. I believe it had something to do with evdev, though. Section ServerFlags Option AllowEmptyInput true Option AutoAddDevices true EndSection
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
Mick wrote: On 12/12/2009, walt w41...@gmail.com wrote: On 12/12/2009 03:14 PM, Mick wrote: ... I have had mouse, keyboard and synaptics along with evdev in my INPUT_DEVICES and have emerged relative drivers. I am now going to remove them and see what gives. I know nothing about the synaptics driver, so be careful about deleting it. Maybe rename it instead of deleting it? Nope, unmerged it and deleted it from make.conf, then when I emerged xf86-video-ati and evdev all other drivers (mouse, keyboard, synaptics) were brought in as well. I am not clear which /etc/hal/fdi/policy/* files I should have in there ... any ideas? That depends on what hardware you have -- a lot of the stuff that once went into xorg.conf can be put in an fdi file now. Here is an example: Thanks for that. I tried the startx trick. I recall that this would launch my WM (fluxbox), but now all I get is an X session with twm! Has something changed with /etc/rc.conf? Where should I specify fluxbox? No /var/log/xdm.log or other errors were there this time. Trying to start xdm and I keep getting the same old errors: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server (:0.0) and (EE) XKB: No components provided for device Virtual core keyboard. I am running out of things to try now. I don't have a recent enough back up otherwise I would roll back this bad experience. I haven't been following this thread a whole lot but this may help. Do a emerge -epv world and see if you see any changes there. It may be a USE flag change or it may be something else that you notice. It's just a pretend so it shouldn't take but a few minutes. May need to use 'less' or 'more' to scroll through the output easier. I hope that shows something that will help. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
walt wrote: I have these lines in my xorg.conf but I can't remember when or why I put them there. I believe it had something to do with evdev, though. Section ServerFlags Option AllowEmptyInput true Option AutoAddDevices true EndSection If I recall correctly, that disables evdev. I think the first Option disables it. I'm not real sure about the second one. I remember because I did that when I couldn't get evdev to work. Dale :-) :-)
Re: [gentoo-user] Re: xorg-server-1.6.5-r1 'Couldn't load XKB keymap, falling back to pre-XKB keymap'
091213 Mick wrote: I tried the startx trick. It's not a trick ! -- it's the normal sensible way to start X (smile). I recall that this would launch Fluxbox, but now all I get is an X session with twm ! Where should I specify fluxbox? You need a file ~/.xinitrc . Mine is # PP 091002 : for Fluxbox-1.1.1 + KDE 4 xscreensaver kdeinit4 startfluxbox It also starts Xscreensaver the KDE 4 libs, which I want. I just upgraded to Xorg-server 1.6.5-r1 without any problem beyond the need to update 82 pkgs in my own labor-intensive fashion. There was also an update to Hal Lvm2 Util-linux from my weekly 'eix-sync', which I made sure to get done before tackling X. HTH. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
