Bug 134906 - configuring the keymap in sax2 breaks the X11-Configuration for the external monitor
Summary: configuring the keymap in sax2 breaks the X11-Configuration for the external ...
Status: RESOLVED WORKSFORME
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Final
Hardware: i586 Other
: P5 - None : Normal
Target Milestone: ---
Assignee: Marcus Schaefer
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-22 14:47 UTC by Peter Gunreben
Modified: 2005-11-23 11:50 UTC (History)
0 users

See Also:
Found By: Customer
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
sax2 logfile (85.90 KB, text/plain)
2005-11-22 15:22 UTC, Peter Gunreben
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Gunreben 2005-11-22 14:47:53 UTC
Dell Latitude C640 in docking station with external TFT 1701FP.
In my fresh SuSE 10.0 installation, X11 was working fine, but the keymap was set to american ("us"). I tried to use yast2 to change the keymap into "de" and was asked to test the new configuration. The screen went black and the TFT-Monitor displayed the message "Cannot display video mode". 

I'll describe the next steps in short:
1) runlevel 3 - sax2 - save default - runlevel 5: everything was fine, but "us" keymap

2) runlevel 3 - sax2 - change keymap - test: "Cannot display video mode"

3) docked out (using panel display): runlevel 3 - sax2 - change keymap - test: everything fine - shutdown - docked in (using ext. TFT) - boot - "Cannot display video mode"

4) runlevel 3 - sax2 - save default - changed keymap in /etc/X11/xorg.conf manually - runlevel 5: everything fine

Whenever I changed a configuration using sax2, my external TFT monitor shows only "Cannot display video mode".
Comment 1 Marcus Schaefer 2005-11-22 15:04:05 UTC
Hmm, sounds really weird. In principal changing the keyboard configuration
is not the culprit I assume no matter what setting has been changed this
problem will occur. Well I need a log to see what happend. If you don't mind
follow the workflow below:

1) run "sax2 -r" from runlevel 3 as root from within the docking station
2) do the keymap change... and test
3) the problem should occur now according to your report
4) quit the test

--> send me the log file /var/log/SaX.log

Additionally you can try to use the current version available here:

  ftp://ftp.berlios.de/pub/sax/head-build/suse-10.0

Thanks
Comment 2 Peter Gunreben 2005-11-22 15:21:35 UTC
I followed the workflow as you've described it and the problem occured as expected. After the timeout, the gui of sax2 showed up again and I was able to quit sax2. I'll attach the logfile...
Comment 3 Peter Gunreben 2005-11-22 15:22:39 UTC
Created attachment 58105 [details]
sax2 logfile
Comment 4 Peter Gunreben 2005-11-22 15:38:32 UTC
The upgrade to the current sax2 version (7.1-28.1) doesn't solve the problem.
Comment 5 Peter Gunreben 2005-11-22 15:41:55 UTC
I had saved an image of /etc/X11 as it was working and made a diff to it after the configuration was broken by sax2. Would this help? Is there any sensitive information within /etc/X11 I shouldn't make publicly available? 
Comment 6 Marcus Schaefer 2005-11-23 10:17:13 UTC
Hmm I'm sorry but I cannot see that ever have configured the secondary
VGA of your laptop. I only see a configuration for one display the one
currently active. The diff you mentioned is already part of the logfile

--snip--

22-Nov 16:16:22 <T> Configuration: [NEXT SETUP DIFF]... [
	--- /var/lib/sax/xorg.conf.first2005-11-22 11:49:24.000000000 +0100
	+++ /var/lib/sax/xorg.conf	2005-11-22 16:16:12.000000000 +0100
	@@ -1,6 +1,6 @@
	 # /.../
	 # SaX generated X11 config file
	-# Created on: 2005-11-22T11:49:13+0100.
	+# Created on: 2005-11-22T16:16:11+0100.
	 #
	 # Version: 7.1
	 # Contact: Marcus Schaefer <sax@suse.de>, 2002
	@@ -73,11 +73,11 @@
	 EndSection
	 
	 Section "Module"
	-  Load         "glx"
	-  Load         "type1"
	-  Load         "extmod"
	   Load         "dbe"
	+  Load         "type1"
	   Load         "freetype"
	+  Load         "extmod"
	+  Load         "glx"
	   Load         "v4l"
	 EndSection
	 
	@@ -86,8 +86,9 @@
	   Identifier   "Keyboard[0]"
	   Option       "Protocol" "Standard"
	   Option       "XkbLayout" "de"
	-  Option       "XkbModel" "pc104"
	+  Option       "XkbModel" "pc105"
	   Option       "XkbRules" "xfree86"
	+  Option       "XkbVariant" "nodeadkeys"
	 EndSection
	 
	 
	@@ -171,7 +172,6 @@
	   BusID        "1:0:0"
	   Driver       "radeon"
	   Identifier   "Device[0]"
	-  Screen       0
	   VendorName   "ATI"
	 EndSection
	 
]

--snap--

as you can see the changes you made only affects the keyboard and
removes an unneeded Screen entry which is not set in a single head
setup. 

I'm a bit confused how it was possible to have internal and external
VGA working if there is no configuration setup for it :) As you may
have noticed there is a small checkbox to enable the dualhead mode if
you enable it the problems should fade away
Comment 7 Marcus Schaefer 2005-11-23 10:20:52 UTC
by the way thanks for the very good reporting style. maybe I missundersand
something. Could you check out the dualhead setup with the new version you
have installed, does it fix your problem ?
Comment 8 Peter Gunreben 2005-11-23 11:50:19 UTC
... I take all the blame! It *is* working if you activate the dualhead checkbox. However, I didn't expect that I'd need to change the display configuration in sax2 as the default configuration was already working.

Thanks for your help!