Go Back   openSUSE Forums > Archives > SLS Archives > ARCHIVES - SuSE Linux > ARCHIVES - Desktop Environments
Forums FAQ Members List Search Today's Posts Mark Forums Read


ARCHIVES - Desktop Environments KDE, GNOME, FVWM, etc.. all those window manager related questions get in here.

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 16-May-2008, 03:50
shadychris
Guest
 
Posts: n/a
Smile

Since making my biggest mistake of the year by trying to get Compiz working - a complete waste of time since despite trying every driver ever written by nvidia I still get terrible screen flickering - I have been left with an incorrect keyboard layout and I can find no way to reconfigure it.
I thiink for some reason I now have a US keyboard instead of a UK version as special characters such as " and @ seem to have swapped keys - a little annoying when typing email addresses....
If I try to configure the keyboard using Yast sax2 fails to open and I get dropped to a shell login. I then have to init 3 and init 5 and startx to get back to the gui...
I have also tried running sax2 from command prompt but still get the same result - it just wont launch properly and drops me to a shell - also if I do not quickly login and init3 init5 and startx to get the gui back, the screen simply blacks out after maybe 15 seconds and I can do nothing except hit reset.... :-(
Can anyone advise me of how to either get sax2 working again, or how I can manually edit my config files to give me a proper UK keyboard.
Thanks,
Chris
  #2 (permalink)  
Old 16-May-2008, 04:13
deltaflyer
Guest
 
Posts: n/a
Default

try running sax2 from failsafe,should sort it out

Andy
  #3 (permalink)  
Old 16-May-2008, 05:18
shadychris
Guest
 
Posts: n/a
Default

Failsfafe huh?? sounds a bit Windowsy to me ;-)
Well I gave it a try Andy, but with no great success.....
Here's what happens:-
boot failsafe takes me to runlevel3 with a few skipped services - samba ACPI etc
login as root
run sax2 and get following output
Sax: initializing please wait
Sax: your current config will not be read in
Sax: no Xserver is running
Sax: will start own server if needed

then I wait for about 45 seconds with nothing happening, then about 15 seconds of epilepsy inducing flickering
Finally the nice blue sax screen appears showing AutoGraphicSetup suggestion prompt box with 3 options - accept gfx configuration, change or cancel - my hopes were raised but sadly regardless of which of these 3 options I select Sax disappears and I am left back at the command prompt which will now not accept any input...
I seem to remember somewhere along the way when I was wasting time with Compiz,
reading that sax2 has problems recognising the Nvidia Xserver - could this be why I am unable to now use sax2?
  #4 (permalink)  
Old 16-May-2008, 05:30
deltaflyer
Guest
 
Posts: n/a
Default

have you tried editing /etc/sysconfig/desktop/display manager & changed it to Xorg ? might solve the problem

Andy
  #5 (permalink)  
Old 16-May-2008, 05:52
shadychris
Guest
 
Posts: n/a
Default

well this is very bizarre....
since playing around with running sax from failsafe my keyboard is now back to UK layout!!!

I had a look at doing your last suggestion - my path is slightly different to your suggestion - I dont have the desktop folder just /etc/sysconfig/displaymanager whcih looks like this:-

## Path: Desktop/Display manager
## Description: settings to generate a proper displaymanager config
## Type: string(kdm,xdm,gdm,wdm,console)
## Default: ""
## Config: xdm,kdm,gdm
#
# Here you can set the default Display manager (kdm/xdm/gdm/wdm/console).
# all changes in this file require a restart of the displaymanager
#
DISPLAYMANAGER="kdm"

## Type: yesno
## Default: no
#
# Allow remote access (XDMCP) to your display manager (xdm/kdm/gdm). Please note
# that a modified kdm or xdm configuration, e.g. by KDE control center
# will not be changed. For gdm, values will be updated after change.
# XDMCP service should run only on trusted networks and you have to disable
# firewall for interfaces, where you want to provide this service.
#
DISPLAYMANAGER_REMOTE_ACCESS="no"

## Type: yesno
## Default: no
#
# Allow remote access of the user root to your display manager. Note
# that root can never login if DISPLAYMANAGER_SHUTDOWN is "auto" and
# System/Security/Permissions/PERMISSION_SECURITY is "paranoid"
#
DISPLAYMANAGER_ROOT_LOGIN_REMOTE="no"

## Type: yesno
## Default: yes
#
# Let the displaymanager start a local Xserver.
# Set to "no" for remote-access only.
# Set to "no" on architectures without any Xserver (e.g. s390/s390x).
#
DISPLAYMANAGER_STARTS_XSERVER="yes"

## Type: yesno
## Default: no
#
# TCP port 6000 of Xserver. When set to "no" (default) Xserver is
# started with "-nolisten tcp". Only set this to "yes" if you really
# need to. Remote X service should run only on trusted networks and
# you have to disable firewall for interfaces, where you want to
# provide this service. Use ssh X11 port forwarding whenever possible.
#
DISPLAYMANAGER_XSERVER_TCP_PORT_6000_OPEN="no"

## Type: string
## Default:
#
# Define the user whom should get logged in without request. If string
# is empty, display standard login dialog.
#
DISPLAYMANAGER_AUTOLOGIN=""

## Type: yesno
## Default: no
#
# Allow all users to login without password, but ask for the user, if
# DISPLAYMANAGER_AUTOLOGIN is empty.
#
DISPLAYMANAGER_PASSWORD_LESS_LOGIN="no"

## Type: yesno
## Default: no
#
# Display a combobox for Active Directory domains.
#
DISPLAYMANAGER_AD_INTEGRATION="no"

## Type: list(root,all,none,auto)
## Default: auto
#
# Determine who will be able to shutdown or reboot the system in kdm
# and gdm. Valid values are: "root" (only root can shutdown), "all"
# (everybody can shutdown), "none" (nobody can shutdown from
# displaymanager), "auto" (follow
# System/Security/Permissions/PERMISSION_SECURITY to decide: "easy
# local" is equal to "all", everything else is equal to "root"). Note
# that remote user can never shutdown in GDM.
#
DISPLAYMANAGER_SHUTDOWN="auto"
## Path: Desktop/Display manager
## Description: settings to generate a proper displaymanager config
## Type: string
## Default:
## Config: kdm3
#
# space separated list of users for which icons should be shown in KDM
# if empty, then take system defaults
#
KDM_USERS=""

## Type: string
## Default:
#
# Special greeting words in kdm
#
KDM_GREETSTRING=""

## Type: string
## Default: SUSE
#
# Define the theme to be used by kdm. If empty, the traditional login
# window is used (which lacks some features)
#
DISPLAYMANAGER_KDM_THEME="SUSE"
## Path: Desktop/Display manager
## Type: string(Xorg,Xgl)
## Default: "Xorg"
#
# Xgl is an experimental Xserver using OpenGL for rendering.
# Right now only the glx backend is supported, which runs on top of a
# standard Xorg server providing OpenGL.
# Set this to 'Xgl' and run SuSEconfig only if you want to run your
# displaymanager (kdm/gdm/xdm) on Xgl on top of Xorg.
# This setting is case sensitive.
# Warning! This is highly experimental.
#
DISPLAYMANAGER_XSERVER=Xorg
## Path: Desktop/Display manager
## Type: string
## Default: "-accel glxbuffer -accel xvbuffer"
#
# Xglx is an experimental Xserver using OpenGL for rendering.
# Additional options for startup when using a display manager.
# You can try
# "-accel glx"
# or
# "-accel glxbuffer"
# in order to get accelerated indirect OpenGL rendering for 3D applications.
# You can also try
# "-accel xv"
# to accelerate XVideo color space conversion and/or scaling.
#
# See also /usr/share/doc/packages/xgl/README.SUSE
#
DISPLAYMANAGER_XGL_OPTS="-accel glxbuffer -accel xvbuffer"

## Type: string
## Default: "auto"
#
# Mode to configure on output devices by default
# (RANDR 1.2 compatible drivers only).
#
# If set to "auto", DISPLAYMANAGER_RANDR_MODE_auto is used on laptops, and
# the empty string on workstations.
#
# The output is not explicitly enabled (read: disabled) if set to an empty
# string.
# If the variable contains a fully configured modeline (see default of
# DISPLAYMANAGER_RANDR_MODE_auto), the mode is defined and set.
# If the variable contains a mode name only, the mode has to be defined
# already.
#
# If a monitor is attached during Xstartup, or when invoking "xrandr --auto"
# during runtime, the output is correctly configured and a mode is
# automatically selected if none has been used so far.
#
# Variables are checked according to their extension for
# VGA DVI_I DVI_D DVI_A Composite S_Video Component LFP Proprietary
#
DISPLAYMANAGER_RANDR_MODE_VGA="auto"

## Type: string
## Default: "1024x768_60 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync"
#
# Mode to use for laptops for DISPLAYMANAGER_RANDR_MODE_* on laptops only,
# when the according variable is set to "auto".
# (RANDR 1.2 compatible drivers only).
#
DISPLAYMANAGER_RANDR_MODE_auto="1024x768_60 64.11 1024 1080 1184 1344 768 769 772 795 -HSync +Vsync"
#DISPLAYMANAGER_RANDR_MODE_DVI_I=""
#DISPLAYMANAGER_RANDR_MODE_DVI_D=""
#DISPLAYMANAGER_RANDR_MODE_DVI_A=""
#DISPLAYMANAGER_RANDR_MODE_Compsite=""
#DISPLAYMANAGER_RANDR_MODE_S_Video=""
#DISPLAYMANAGER_RANDR_MODE_Component=""
#DISPLAYMANAGER_RANDR_MODE_LFP=""
#DISPLAYMANAGER_RANDR_MODE_Proprietary=""

it looks like my displaymanager=kdm but displaymanager_xserver = xorg so I'm not really sure which, if any, if I should be changing here.

however under /etc/sysconfig I found my keyboard config file which is showing that I am using english-Uk pc104 - I 've copied it and put it somewhere safe in case I get the same problem in the future
  #6 (permalink)  
Old 16-May-2008, 06:05
deltaflyer
Guest
 
Posts: n/a
Default

if you have it working now, just leave things as is, best not to fiddle too much if you do, best to keep a copy of xorg.conf as well

Andy
 

Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2