Can't use CTRL-ATL-F* after upgrade - Slackware

This is a discussion on Can't use CTRL-ATL-F* after upgrade - Slackware ; Hello, I have manually upgraded to Slackware 12.0. The missing bit is getting X to work correctly. I can switch to graphical mode with 'startx' but, once there, I can't switch to console. The keys combination CRTL-ATL-F* don't work, although ...

+ Reply to Thread
Results 1 to 8 of 8

Thread: Can't use CTRL-ATL-F* after upgrade

  1. Can't use CTRL-ATL-F* after upgrade

    Hello,

    I have manually upgraded to Slackware 12.0. The missing bit is
    getting X to work correctly. I can switch to graphical mode
    with 'startx' but, once there, I can't switch to console.

    The keys combination CRTL-ATL-F* don't work, although I can kill
    X with CRTL-ALT-backspace.

    I have tried to change the 'Option XkbModel' to pc102 or pc105
    but I had no success.

    This is an extract from xorg.0.log:

    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/local/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/misc/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/Type1/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/Speedo/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    (WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic/" does not exist.
    (WW) FontPath is completely invalid. Using compiled-in default.
    (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
    directory)
    (WW) VESA(0): Failed to set up write-combining range
    (0xe0000000,0x400000)
    (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap

    It looks like it has something to do with the xkb keymap.
    What should I check now?

    Thanks

    --
    Ottavio
    http://www.pledgebank.com/boycottvista


  2. Re: Can't use CTRL-ATL-F* after upgrade

    On 2007-10-01, Ottavio Caruso wrote:
    > Hello,
    >
    > I have manually upgraded to Slackware 12.0. The missing bit is
    > getting X to work correctly. I can switch to graphical mode
    > with 'startx' but, once there, I can't switch to console.
    >
    > The keys combination CRTL-ATL-F* don't work, although I can kill
    > X with CRTL-ALT-backspace.
    >
    > I have tried to change the 'Option XkbModel' to pc102 or pc105
    > but I had no success.
    >
    > This is an extract from xorg.0.log:
    >
    > (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/local/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/misc/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/Type1/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/Speedo/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    > (WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic/" does not exist.
    > (WW) FontPath is completely invalid. Using compiled-in default.
    > (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
    > directory)
    > (WW) VESA(0): Failed to set up write-combining range
    > (0xe0000000,0x400000)
    > (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
    >
    > It looks like it has something to do with the xkb keymap.
    > What should I check now?



    Did you upgrade according to the instructions in UPGRADE.TXT?
    If so, you should not be getting these errors at all.
    If not, then plan on reinstalling - I'm sure it's *possible* to
    recover and get things back to normal, but I wouldn't want to
    try it...

    RW

  3. Re: Can't use CTRL-ATL-F* after upgrade

    Robby Workman wrote:
    > On 2007-10-01, Ottavio Caruso wrote:
    >> Hello,
    >>
    >> I have manually upgraded to Slackware 12.0. The missing bit is
    >> getting X to work correctly. I can switch to graphical mode
    >> with 'startx' but, once there, I can't switch to console.
    >>
    >> The keys combination CRTL-ATL-F* don't work, although I can kill
    >> X with CRTL-ALT-backspace.
    >>
    >> I have tried to change the 'Option XkbModel' to pc102 or pc105
    >> but I had no success.
    >>
    >> This is an extract from xorg.0.log:
    >>
    >> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/local/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/misc/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/Type1/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/Speedo/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    >> (WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic/" does not exist.
    >> (WW) FontPath is completely invalid. Using compiled-in default.
    >> (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
    >> directory)
    >> (WW) VESA(0): Failed to set up write-combining range
    >> (0xe0000000,0x400000)
    >> (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
    >>
    >> It looks like it has something to do with the xkb keymap.
    >> What should I check now?

    >
    >
    > Did you upgrade according to the instructions in UPGRADE.TXT?
    > If so, you should not be getting these errors at all.
    > If not, then plan on reinstalling - I'm sure it's *possible* to
    > recover and get things back to normal, but I wouldn't want to
    > try it...


    It shouldn't be too bad. Download *all* the xorg-* packages you will
    need. KDE and GUI apps shouldn't need changing. Back up (especially
    /etc and /home). Then close X and drop to the console, uninstall all
    the X11 and xorg packages (including libX*, xrander, xproto, ...), and
    finally install all the xorg packages in the correct order.

    Or something to that effect.

    Whether that's easier than a fresh install might be a personal call.

    - Daniel

  4. Re: Can't use CTRL-ATL-F* after upgrade

    Robby Workman wrote:
    > On 2007-10-01, Ottavio Caruso wrote:
    > > Hello,
    > >
    > > I have manually upgraded to Slackware 12.0. The missing bit is
    > > getting X to work correctly. I can switch to graphical mode
    > > with 'startx' but, once there, I can't switch to console.

    > [skip]


    > Did you upgrade according to the instructions in UPGRADE.TXT?
    > If so, you should not be getting these errors at all.
    > If not, then plan on reinstalling - I'm sure it's *possible* to
    > recover and get things back to normal, but I wouldn't want to
    > try it...
    >
    > RW


    I did, more or less, upgrade according to UPGRADE.TXT.
    What i added was:

    - I had to install aaa_terminfo and which (this was not mentioned
    in the upgrade file)

    - I had to run 'mkfontdir /usr/share/fonts*' or it wouldn't
    find the fonts.

    There's no mention in the upgrade file of what and how many new
    xorg* or libX* packages should be installed.
    I have remove all the X11* and fontconfig* and then used slackpkg to
    upgrade the existing packages, and then I had to do a bit of trial
    and error.

    I'd like to avoid reinstalling everything, it sound a bit too
    'Windows' style.

    --
    Ottavio
    http://www.pledgebank.com/boycottvista


  5. Re: Can't use CTRL-ATL-F* after upgrade

    D Herring wrote:
    > It shouldn't be too bad. Download *all* the xorg-* packages you will
    > need.


    I could do that and it's probably the best solution, but my challenge
    was
    to find which packages dealt specifically with the XKB keymap.
    And then I have limited space. I am running this system from a
    flash drive and I have only 71 MB left...

    >KDE and GUI apps shouldn't need changing. Back up (especially
    > /etc and /home). Then close X and drop to the console, uninstall all
    > the X11 and xorg packages (including libX*, xrander, xproto, ...), and
    > finally install all the xorg packages in the correct order.


    But what's the correct order? I can't find any official reference to
    this.
    Thank you anyway.

    --
    Ottavio
    http://www.pledgebank.com/boycottvista


  6. Re: Can't use CTRL-ATL-F* after upgrade

    D Herring wrote:
    > Robby Workman wrote:
    >> On 2007-10-01, Ottavio Caruso wrote:
    >>> Hello,
    >>>
    >>> I have manually upgraded to Slackware 12.0. The missing bit is
    >>> getting X to work correctly. I can switch to graphical mode
    >>> with 'startx' but, once there, I can't switch to console.
    >>>
    >>> The keys combination CRTL-ATL-F* don't work, although I can kill
    >>> X with CRTL-ALT-backspace.
    >>>
    >>> I have tried to change the 'Option XkbModel' to pc102 or pc105
    >>> but I had no success.
    >>>
    >>> This is an extract from xorg.0.log:
    >>>
    >>> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/local/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/misc/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/Type1/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/CID/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/Speedo/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/75dpi/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/100dpi/" does not exist.
    >>> (WW) The directory "/usr/X11R6/lib/X11/fonts/cyrillic/" does not exist.
    >>> (WW) FontPath is completely invalid. Using compiled-in default.
    >>> (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or
    >>> directory)
    >>> (WW) VESA(0): Failed to set up write-combining range
    >>> (0xe0000000,0x400000)
    >>> (WW) Couldn't load XKB keymap, falling back to pre-XKB keymap
    >>>
    >>> It looks like it has something to do with the xkb keymap.
    >>> What should I check now?

    >>
    >>
    >> Did you upgrade according to the instructions in UPGRADE.TXT?
    >> If so, you should not be getting these errors at all.
    >> If not, then plan on reinstalling - I'm sure it's *possible* to
    >> recover and get things back to normal, but I wouldn't want to
    >> try it...

    >
    > It shouldn't be too bad. Download *all* the xorg-* packages you will
    > need. KDE and GUI apps shouldn't need changing. Back up (especially
    > /etc and /home). Then close X and drop to the console, uninstall all
    > the X11 and xorg packages (including libX*, xrander, xproto, ...), and
    > finally install all the xorg packages in the correct order.
    >
    > Or something to that effect.
    >
    > Whether that's easier than a fresh install might be a personal call.
    >
    > - Daniel


    Ottavio,

    It sounds like you are using an old xorg.conf file. The location of the
    fonts have changed. Please note the following:

    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/lib/X11/fonts/local/"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/OTF"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi/:unscaled"
    FontPath "/usr/lib/X11/fonts/misc/"
    FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
    FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
    FontPath "/usr/lib/X11/fonts/Speedo/"
    FontPath "/usr/lib/X11/fonts/Type1/"
    FontPath "/usr/lib/X11/fonts/TTF/"
    FontPath "/usr/lib/X11/fonts/OTF/"
    FontPath "/usr/lib/X11/fonts/cyrillic/"
    FontPath "/usr/lib/X11/fonts/75dpi/"
    FontPath "/usr/lib/X11/fonts/100dpi/"
    EndSection

    Conversely, you might want to symlink the directory from
    /usr/lib/X11/fonts to /usr/X11R6/lib/X11/fonts.

    This should eliminate the font issue; however, you might find "other
    issues with your old xorg.conf file that may warrant you replacing it.

    As for the keyboard CTRL-ALT-F* issue, your input devices section should
    look like this:

    Section "InputDevice"
    Identifier "Keyboard1"
    Driver "kbd"
    Option "AutoRepeat" "500 30"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
    EndSection

    Section "InputDevice"
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "PS/2"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection

    For you viewing, the following one of my xorg.conf files for a Slackware
    workstation:

    # Xorg Conf File for Slackware Workstation
    #

    Section "ServerLayout"
    Identifier "NVidia 3D Layout"
    Screen 0 "VA1930wm" 0 0
    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"
    EndSection

    Section "Files"
    RgbPath "/usr/share/X11/rgb"
    ModulePath "/usr/lib/xorg/modules"
    FontPath "/usr/lib/X11/fonts/local/"
    FontPath "/usr/share/fonts/TTF"
    FontPath "/usr/share/fonts/OTF"
    FontPath "/usr/share/fonts/Type1"
    FontPath "/usr/share/fonts/misc"
    FontPath "/usr/share/fonts/75dpi/:unscaled"
    FontPath "/usr/lib/X11/fonts/misc/"
    FontPath "/usr/lib/X11/fonts/75dpi/:unscaled"
    FontPath "/usr/lib/X11/fonts/100dpi/:unscaled"
    FontPath "/usr/lib/X11/fonts/Speedo/"
    FontPath "/usr/lib/X11/fonts/Type1/"
    FontPath "/usr/lib/X11/fonts/TTF/"
    FontPath "/usr/lib/X11/fonts/OTF/"
    FontPath "/usr/lib/X11/fonts/cyrillic/"
    FontPath "/usr/lib/X11/fonts/75dpi/"
    FontPath "/usr/lib/X11/fonts/100dpi/"
    EndSection

    Section "Module"
    Load "type1"
    Load "dbe"
    SubSection "extmod"
    Option "omit xfree86-dga"
    EndSubSection
    Load "freetype"
    Load "glx"
    EndSection

    Section "ServerFlags"
    Option "Xinerama" "0"
    EndSection

    Section "InputDevice"
    Identifier "Keyboard1"
    Driver "kbd"
    Option "AutoRepeat" "500 30"
    Option "XkbRules" "xorg"
    Option "XkbModel" "pc105"
    Option "XkbLayout" "us"
    EndSection

    Section "InputDevice"
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "PS/2"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection

    Section "Monitor"
    Identifier "VA1930wm"
    VendorName "NVIDIA Corporation"
    ModelName "ViewSonic VA1930wm"
    HorizSync 24.0 - 82.0
    VertRefresh 50.0 - 75.0

    EndSection

    Section "Device"
    Identifier "GEForce7699GS"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7600 GS"
    Option "RenderAccel" "true"
    Option "AllowGLXWithComposite" "true"
    EndSection

    Section "Extensions"
    Option "Composite" "Enable"
    EndSection

    Section "InputDevice"
    Identifier "Mouse1"
    Driver "mouse"
    Option "Protocol" "PS/2"
    Option "Device" "/dev/input/mice"
    Option "ZAxisMapping" "4 5 6 7"
    EndSection

    Section "Monitor"
    Identifier "VA1930wm"
    VendorName "NVIDIA Corporation"
    ModelName "ViewSonic VA1930wm"
    HorizSync 24.0 - 82.0
    VertRefresh 50.0 - 75.0

    EndSection

    Section "Device"
    Identifier "GEForce7699GS"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7600 GS"
    Option "RenderAccel" "true"
    Option "AllowGLXWithComposite" "true"
    EndSection

    Section "Extensions"
    Option "Composite" "Enable"
    EndSection

    Section "Screen"
    Identifier "VA1930wm"
    Device "GEForce7699GS"
    Monitor "VA1930wm"
    Option "AddARGBGLXVisuals" "true"
    Option "DisableGLXRootClipping" "true"
    DefaultDepth 24
    Option "TwinView" "0"
    Option "metamodes" "1440x900 +0+0; 1152x864 +0+0; 1024x768
    +0+0"
    EndSection

    As an additional note, if you do not want to list the fonts directory in
    the future, you might want to try this script ...

    -----------------------------------8<-----------------------------------
    #!/bin/sh
    #------------------------------------------------------------------------
    # Description: /etc/rc.d/rc.xfs:
    # Purpose: Local Font Server Initialization script.
    # Author: Tom Neilson
    #------------------------------------------------------------------------
    #
    # Start X Font Server Service:
    if [ -x /usr/bin/xfs ]; then
    echo "Starting xfs Server"
    /usr/bin/xfs -config /etc/X11/fs/config -daemon &
    fi

    As well, you can change the Section "Files" to ....
    Section "Files"
    FontPath "unix/:7100"
    RgbPath "/usr/X11R6/lib/X11/rgb"
    ModulePath "/usr/X11R6/lib/modules"
    EndSection



    I hope you find this information of some value.

    Regards,

    Tom

  7. Re: Can't use CTRL-ATL-F* after upgrade

    Tom Neilson wrote:

    > As for the keyboard CTRL-ALT-F* issue, your input devices section should
    > look like this:


    You probably mean: If you're living in the US -or an other
    English speaking country- your input devices section might
    look like this: :-)

    > Section "InputDevice"
    > Identifier "Keyboard1"
    > Driver "kbd"
    > Option "AutoRepeat" "500 30"
    > Option "XkbRules" "xorg"
    > Option "XkbModel" "pc105"
    > Option "XkbLayout" "us"
    > EndSection


    A few months ago I noticed this CTRL-ALT-F* issue while
    I was playing with debian etch on a notebook and I could
    reproduce the issue on a slackware 12.0 desktop system.
    On both systems the error occured when I used the combination
    of these options:

    Option "XkbLayout" "us"
    Option "XkbVariant" "nodeadkeys"

    For a few more details see:
    http://groups.google.nl/group/alt.os...fa116babed21a9



    Regards,

    Kees.

    --
    Kees Theunissen.

  8. [SOLVED] Re: Can't use CTRL-ATL-F* after upgrade

    On 2 Oct, 23:35, Kees Theunissen wrote:
    > A few months ago I noticed this CTRL-ALT-F* issue while
    > I was playing with debian etch on a notebook and I could
    > reproduce the issue on a slackware 12.0 desktop system.
    > On both systems the error occured when I used the combination
    > of these options:
    >
    > Option "XkbLayout" "us"
    > Option "XkbVariant" "nodeadkeys"
    >
    > For a few more details see:http://groups.google.nl/group/alt.os...owse_thread/th...


    Oops, I missed that thread. Merging the two threads and adding a bit
    of my own, here what solved my problem:

    # slackpkg install xkeyboard-config xbbcomp libxbbui libxkbfile
    # mcedit /etc/X11/xorg.conf

    Option "XkbModel" "microsoft"
    Option "XkbLayout" "gb"
    Option "XkbVariant" "intl"


    Thank you all for your contributions.

    --
    Ottavio
    http://www.pledgebank.com/boycottvista


+ Reply to Thread