June 2005 - openSUSE X.org - openSUSE Mailing Lists

Re: [suse-xfree86] 9.3: Keyboard keymaps and xorg
by AmigaPhil＠ping.be 18 Jun '05

18 Jun '05

Carlos E. R. (robin1.listas(a)tiscali.es) wrote something I wish to comment : (news:<Pine.LNX.4.61.0506172247260.11566(a)nimrodel.valinor> posted on 17-juin-05 21:50:01) >> So in the end, it seems the files were not missing as I thought, >> just "unavailable" (???) >> How could it be that Konqueror is hidding files to root ? >> How could it be that root is refused access to some files ? > > If your partition is reiser, it is a known problem. You need to boot from > the dvd, and run a "reiserfsck" on it. It is known that when a reiserfs > part. gets corrupted, one of the symptoms is the "Permission denied" > message to root. Oh s..t. At installation time, I was thinking to use ext3 partitions instead. But then I saw the ReiserFS was default with Suse, and I opted for it. Thanks, I'm going to try that. [Back for report] *SOLVED* !!! (The whole thing was a ReiserFS issue) 1st step: Repairing the damaged partition I booted the DVD, and first try to repair the partition with the repair function from the installation program. The program found effectively that my /dev/sda2 ReiserFS partition was corrupted (did not have a chance to spot that the last time I used the install/repair function. See underneath why.) I click on "Repair", and in a fraction of a second, I briefly saw a small windows poping up. It ran so fast that I sounded suspect. I ran the detection again to discover that the partition was still corrupted. *WORST*, I could then no more boot from HD ! So the only thing left to do was to launch the rescue mode. From there, I ran reiserfsck --check /dev/sda2 and I was told to fix the partition with the --rebuild-tree option. So I did it: reiserfsck --rebuild-tree --logfile rebuild.log /dev/sda2 After a moment of PANIC when I saw the warning to perform a backup first (I have none and could not do one), but everything went fine. 2nd step: Repair the system (in case...) The Suse install/repair process ran flawlessly, no more corrupted FS. I replaced a few packages as suggested (xorg was not one of them). And reboot again, now from HD. ... a quick check: the "unavailable" files were not in place, but the directories were clean. (The retrieved files were in a newly created lost+found directory) So, step 3: re-install the xorg package again with yast. No problem this time, the package was installed properly. Step 4: Run Yast Online Update (YOU) At least to make sure the packages replaced during the system repair process are up-to-date. Step 5: Configure X11 and the keyboard with Yast > Sax2 Hey, I can now print the missing keys in the test key gadget ! AND *DONE* ! My keyboard configuration issue is closed now. Thanks to all ! (I wonder if I'll take the assle to switch from ReiserFS to Ext3. Is there a tool which perform a backup, format the partition, and restore the backup to it without much pain ?) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN CARNIVORE TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. MUAWOEF3HcrhtER1pIlIP5FUvlapvVOJSVvVHvHABAyFHBHytIpzoUvMOz5SaSVTIGyWJHqM ykVEVIHLtnyzyxOp6Rtxt2FOOKlypRCGfJztLltMSHWbyYODxdjvIOOcnpDtEMyMjazDDIMn lFt0SW1vAFVzq5VODRzFLVlavqVldETxHEFR5ttKJpIJIpqqDHORU0FEIOVVvMNuRPb3tG== -----END CARNIVORE TEASER-----

1 0

Re: [suse-xfree86] 9.3: Keyboard keymaps and xorg
by AmigaPhil＠ping.be 17 Jun '05

17 Jun '05

columbo (columbo(a)wowway.com) wrote something I wish to comment : (news:<200506171129.04491.columbo(a)wowway.com> posted on 17-juin-05 16:29:04) > Just curious if you went into YAST->System->etc/sysconfig > editor->Keyboards to eliminate or identify any potential conflicts in > your keyboard setup. Hadn't noticed in the threads whether or not you > did. No, but I have now. I don't see anything abnormal in Hardware > Keyboard Maybe I could change the YAST_KEYBOARD from "belgian,pc104" to "belgian,pc105", but that won't help to solve the whole keyboard / xorg / permissions issue. In my previous post, I wrote: > For the record, I've just receive news from the Suse installation > support team. I can no more count on solution clues from them as > "...the configuration of Belgian keyboards is not covered under the > terms of the free installation support." :-(( Despite not being covered by the free installation support, someone on the Suse team is still trying to help. :-)) Here is a paste of our recent discussion: ----- paste ----- > The rpm failures you were having would explain some (or all) of the > problems you are experiencing. > So, I would suggest copying the xorg-x11 off CD/DVD (if the DVD rpm > fails then try the CD one) I've compared the xorg rpm from the DVD and from the CD-ROM, in case the one I used from the DVD during installation is corrupted: both have the same size (10 743 701 bytes). I tried to list the content with rpm --query -p xorg.x11-6.8.2-30.i586.rpm --list But, as I read in the man pages, the -p argument make the --list only show the files that are patched (so no "geometry" there). However, using the KRPMView preview from Konqueror, I saw the mysterious missing files are really in the RPM. (Strangely (?), when I tried: rpm --query xorg-x11-6.8.2-30.i586.rpm --state I was told that the package is not installed. But when I tried: rpm -i --test xorg.x11-6.8.2-30.i586.rpm I was told the package is already installed. Confusing.) > then, with in runlevel 3, rpm --force -ivh package.rpm may be enough to > install it. If it succeeds then execute: > > SuSEconfig > > Now modify the /etc/X11/xorg.conf file once again. > After that switch back to runlevel 5. rpm failed the same way as when I tried to install the package with yast: error: unpacking of archive failed on file /etc/X11/xkb/compat/accessx: cpio: rename failed - Permission denied As I was curious as to what the accessx file looks like and what are the permissions set to, I looked in /etc/X11/xkb/compat There are several occurences of the file (I think one for each time I tried to re-install the xorg package), each with a ";" suffix followed by what seems to be a checksum number. I wanted to show that list to you, and as to easily cut-and-paste a list, I opened a terminal and run "ls -l". I discovered something very interesting: Linux1:/etc/X11/xkb/compat # ls -l /bin/ls: pc: Permission denied /bin/ls: leds: Permission denied /bin/ls: misc: Permission denied /bin/ls: pc98: Permission denied /bin/ls: default: Permission denied /bin/ls: mousekeys: Permission denied /bin/ls: norepeat: Permission denied /bin/ls: basic: Permission denied /bin/ls: japan: Permission denied /bin/ls: xtest: Permission denied /bin/ls: complete: Permission denied /bin/ls: keypad: Permission denied /bin/ls: accessx: Permission denied /bin/ls: group_led: Permission denied /bin/ls: iso9995: Permission denied /bin/ls: xfree86: Permission denied total 33 drwxr-xr-x 2 root root 696 Jun 17 15:06 . drwxr-xr-x 10 root root 576 Jun 17 15:06 .. -r--r--r-- 1 root root 1720 Mar 22 18:29 README -rw-r--r-- 1 root root 1184 Jun 13 23:03 accessx;42adf487 -rw-r--r-- 1 root root 1184 Jun 13 23:04 accessx;42adf4ca -rw-r--r-- 1 root root 1184 Jun 15 10:59 accessx;42afedec -rw-r--r-- 1 root root 1184 Jun 15 11:06 accessx;42afefa0 -rw-r--r-- 1 root root 1184 Jun 17 14:59 accessx;42b2c930 -rw-r--r-- 1 root root 1184 Jun 17 15:01 accessx;42b2c9bc -rw-r--r-- 1 root root 1184 Jun 17 15:06 accessx;42b2cac2 Linux1:/etc/X11/xkb # ls -l /bin/ls: geometry.dir: Permission denied /bin/ls: geometry: Permission denied /bin/ls: compiled: Permission denied total 96 drwxr-xr-x 10 root root 576 Jun 17 15:06 . drwxr-xr-x 15 root root 960 Jun 17 15:38 .. -r--r--r-- 1 root root 983 Mar 22 18:29 README -r--r--r-- 1 root root 7448 Mar 22 18:29 README.config -r--r--r-- 1 root root 23337 Mar 22 18:29 README.enhancing drwxr-xr-x 2 root root 696 Jun 17 15:06 compat -r--r--r-- 1 root root 689 Mar 22 18:29 compat.dir drwxr-xr-x 4 root root 424 Jun 4 23:17 keycodes -r--r--r-- 1 root root 2401 Mar 22 18:29 keycodes.dir drwxr-xr-x 5 root root 296 Jun 4 23:17 keymap -r--r--r-- 1 root root 8698 Mar 22 18:29 keymap.dir drwxr-xr-x 2 root root 392 Jun 4 23:17 rules drwxr-xr-x 2 root root 144 Jun 4 23:17 semantics drwxr-xr-x 12 root root 3024 Jun 4 23:17 symbols -r--r--r-- 1 root root 31967 Mar 22 18:29 symbols.dir drwxr-xr-x 2 root root 296 Jun 4 23:17 types -r--r--r-- 1 root root 463 Mar 22 18:29 types.dir lrwxrwxrwx 1 root root 22 Jun 4 23:17 xkbcomp -> /usr/X11R6/bin/xkbcomp So in the end, it seems the files were not missing as I thought, just "unavailable" (???) How could it be that Konqueror is hidding files to root ? How could it be that root is refused access to some files ? >> (There is also these two line in SaX.log : >> >> sh: -c: line 0: unexpected EOF while looking for matching `'' >> sh: -c: line 1: syntax error: unexpected end of file >> >> but I don't know yet which file is causing this error.) ----- end of paste ----- AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN PRIVACY SHIELD----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. 3UHlJEplttvtVRtRljIOrvDzFqV5aPtyIxOavCt2DVGayDSSoRnzzRSpFtIFvRIMSHAAyETR OSpFjKlEDavxWDLkcMIAJOxRaFV6yWWBUGOzVH5AHfcpOPlzFWIJKtxHpJOBVIbdOnptFA0D yAYOMIvTLIEOHFMDzHl5HOAvOzxEvVnt15aVFUVpyU1OMEqyVHEtHHh0HqIVVNMRyVqMuybV qlLpPqJGHMtd3v= -----END PRIVACY SHIELD----- Locks only keep honest people out.

1 0

RE: [suse-xfree86] Is it possible to force the xdm to reload settings?
by Black, Alain 17 Jun '05

17 Jun '05

Will it re-read it's config file if a 'kill -1 PidOfXdm' is run? -----Original Message----- From: Ingo Strauch [mailto:brack@the-one-brack.org] Sent: Friday, June 17, 2005 6:25 AM To: suse-xfree86(a)suse.com Subject: Re: [suse-xfree86] Is it possible to force the xdm to reload settings? On Fri, 17 Jun 2005 07:39:16 -0500 Patrick Shanahan <ptilopteri(a)gmail.com> wrote: > * Wilde, Martin <martin.wilde(a)atari.com> [06-17-05 02:41]: > > can anybody tell me, if it is possible to tell the xdm to reload its > > settings. I told the server to listen to tcp connections in > > /etc/X11/xdm/Xservers and if possible I do not want to restart the > > whole graphical system. > > sure, restart X, ie: "init 3", "init 5" But this then restarts the GUI which is what he wants to avoid. Cheers, Ingo -- Ingo Strauch ---- Registered Linux User #227900 (http://counter.li.org/) GPG Key Fingerprint = DEC8 1B12 9573 6BE7 7A99 C33F 809C 8C2C 772E 66A1 http://www.the-one-brack.org/

1 0

Is it possible to force the xdm to reload settings?
by Wilde, Martin 17 Jun '05

17 Jun '05

Hi everybody, can anybody tell me, if it is possible to tell the xdm to reload its settings. I told the server to listen to tcp connections in /etc/X11/xdm/Xservers and if possible I do not want to restart the whole graphical system. Probably a kill -HUP or kill -SIGUSR? will do that. Any ideas? Have a nice and sunny weekend. Martin

3 2

RE: [suse-xfree86] Is it possible to force the xdm to reload sett ings?
by Wilde, Martin 17 Jun '05

17 Jun '05

Hi Patrick, of course I can do so but all open sessions will be killed in this case :-( Martin > -----Original Message----- > From: Patrick Shanahan [mailto:ptilopteri@gmail.com] > Sent: Friday, June 17, 2005 2:39 PM > To: suse-xfree86(a)suse.com > Subject: Re: [suse-xfree86] Is it possible to force the xdm > to reload settings? > > > * Wilde, Martin <martin.wilde(a)atari.com> [06-17-05 02:41]: > > can anybody tell me, if it is possible to tell the xdm to reload its > > settings. I told the server to listen to tcp connections in > > /etc/X11/xdm/Xservers and if possible I do not want to > restart the whole > > graphical system. > > sure, restart X, ie: "init 3", "init 5" > -- > Patrick Shanahan Registered Linux User #207535 > http://wahoo.no-ip.org @ http://counter.li.org > HOG # US1244711 Photo Album: http://wahoo.no-ip.org/gallery > > -- > To unsubscribe check the List-Unsubscribe header > For additional commands, email: suse-xfree86-help(a)suse.com >

1 0

Re: [suse-xfree86] 9.3: Keyboard keymaps and xorg
by AmigaPhil＠ping.be 16 Jun '05

16 Jun '05

Matthias Hopf (mhopf(a)suse.de) wrote something I wish to comment : (news:<20050616090018.GA30404(a)suse.de> posted on 16-juin-05 10:00:18) >> Here is a quick summary of a keyboard configuration problem I have >> exposed to the Suse support team, and the suse-linux-e mailing list >> (with so far, no solution on sight): For the record, I've just receive news from the Suse installation support team. I can no more count on solution clues from them as "...the configuration of Belgian keyboards is not covered under the terms of the free installation support." :-(( > Missing /etc/X11/xorg.conf. > And /var/log/Xorg.0.log. They are there. Would you like to see the files ? Please find them (in there latest state) attached below. EDIT: Xorg.0.log is 41Kb which is too big for the list (Would you like I privately mail it to you ?) Here is however what I think is the interesting part (last lines of the file): (II) Initializing built-in extension MIT-SHM (II) Initializing built-in extension XInputExtension (II) Initializing built-in extension XTEST (II) Initializing built-in extension XKEYBOARD (II) Initializing built-in extension LBX (II) Initializing built-in extension XC-APPGROUP (II) Initializing built-in extension SECURITY (II) Initializing built-in extension XINERAMA (II) Initializing built-in extension XFIXES (II) Initializing built-in extension XFree86-Bigfont (II) Initializing built-in extension RENDER (II) Initializing built-in extension RANDR (II) Initializing built-in extension COMPOSITE (II) Initializing built-in extension DAMAGE (II) Initializing built-in extension XEVIE (**) Option "CoreKeyboard" (**) Keyboard[0]: Core Keyboard (**) Option "Protocol" "Standard" (**) Keyboard[0]: Protocol: Standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "pc105" (**) Keyboard[0]: XkbModel: "pc105" (**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse[1]: Buttons: 3 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap (II) Mouse[1]: ps2EnableDataReporting: succeeded Could not init font path element /usr/X11R6/lib/X11/fonts/local, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/CID, removing from list! SetClientVersion: 0 8 SetClientVersion: 0 8 SetGrabKeysState - disabled SetGrabKeysState - enabled SetClientVersion: 0 8 SetGrabKeysState - disabled SetGrabKeysState - enabled SetClientVersion: 0 8 SetGrabKeysState - disabled SetGrabKeysState - enabled SetClientVersion: 0 8 SetGrabKeysState - disabled SetGrabKeysState - enabled SetClientVersion: 0 8 SetGrabKeysState - disabled SetGrabKeysState - enabled >> I cannot use SaX from runlevel 3 as I'm faced to black screen with >> just the mouse pointer showing up. When I left click, a small banner >> displaying "Desk: 0 geometry" pops up, but nothing else works, I have >> to reset the computer to get out. > > This sounds like you have an ATI card with two connectors. You could see > the SaX2 interface on the other connector. Indeed. I have a Matrox G400 DualHead board. During the first installation, I removed the "second" detected graphic board as I have no screen attached to this output, and as to disable multihead and gain access to the 3D acceleration. But after several attempts to configure X11, I'm now back with the detected hardware. (0) Matrox MGA G400 AGP (1) Matrox MGA G400 AGP I didn't changed the settings again as I thought I should better try to fix the keyboard problem first. Do you think that if remove the second display (1) again, I will be able to run Sax from runlevel 3. >> Setting verbose level to 10 >> locale is C >> Applied rules from xfree86: >> model: pc104 >> layout: be >> variant: basic >> Trying to build keymap using the following components: >> keycodes: sfree86+aliases(azerty) > > Hm - sfree86 - is this a typo, or a sax error? Marcus? Yes, it's a typo. I couldn't cut-and-paste at that moment, so I retyped it by hand. Sorry. (It's in fact "xfree86") >> types: complete >> compat: complete >> symbols: pc/pc(104)+pc/be(basic) >> geometry: pc(pc104) >> Error loading new keyboard description >> >> The XKEYBOARD keymap compiler (xkbcomp) reports: >> > Error: Can't find file "pc" for geometry include > > Check whether you have /usr/lib/X11/xkb/geometry/pc. > If not, there's something wrong with your installation. Well, /usr/lib/X11 is linked to /usr/X11R6/lib/X11 /usr//X11R6/lib/X11/xkb is linked to /etc/X11/xkb In /etc/X11/xkb there is no geometry directory. As I too suspected a bad xorg installation, I tried to re-install it, but it failed (See my previous mail for the error message output.) >> I also tried to change the >> >> Option "XkbLayout" "be" >> to >> Option "XkbLayout" "be-latin1" > > This will *not* work. Indeed. >> BTW, the "be-latin1" for XkbLayout is linked to the file >> /usr/share/kbd/keymaps/i386/azerty/be-latin1.map.gz Am I right ? >> I haven't found a be-latin1 file somewhere else.) > > The X keymaps have nothing to do with the console keymaps. At the > moment. Ha, right. That's why my keyboard works well from a console at runlevel 3, then ? >From KDE, i use to open a terminal to check if there are any improvement with the keyboard. Is it ok ? Thanks for your reply. AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN ECHELON KILLER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. VOVnIOR5DppprtGSyPDEKIyOLO3lMFltElFtzypVLpxho25FEjvAttRTHKcqRpnzJHyHWAxz MdtDaDYyIFIzpVvJUI0RA1HWAntOVHyDBHJVvIt5VbHvkRVTatxBHvHMFR5HOCOyayvptJMa tSWUVMOjOxFzEE6yIJOEFVUzGqvIWFvvcVqSzOfIDbE0MLFlNdl1IUROSlVSqPMMlq3tGu== -----END ECHELON KILLER----- # /.../ # SaX generated X11 config file # Created on: 2005-06-15T10:47:04+0200. # # Version: 4.8 # Contact: Marcus Schaefer <sax(a)suse.de>, 2002 # # Automatically generated by [ISaX] (4.8) # PLEASE DO NOT EDIT THIS FILE! # Section "Files" FontPath "/usr/X11R6/lib/X11/fonts/misc:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/local" FontPath "/usr/X11R6/lib/X11/fonts/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/Type1" FontPath "/usr/X11R6/lib/X11/fonts/URW" FontPath "/usr/X11R6/lib/X11/fonts/Speedo" FontPath "/usr/X11R6/lib/X11/fonts/PEX" FontPath "/usr/X11R6/lib/X11/fonts/cyrillic" FontPath "/usr/X11R6/lib/X11/fonts/latin2/misc:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/latin2/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/latin2/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/latin2/Type1" FontPath "/usr/X11R6/lib/X11/fonts/latin7/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/baekmuk:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/japanese:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/kwintv" FontPath "/usr/X11R6/lib/X11/fonts/truetype" FontPath "/usr/X11R6/lib/X11/fonts/uni:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/CID" FontPath "/usr/X11R6/lib/X11/fonts/ucs/misc:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/ucs/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/ucs/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/hellas/misc:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/hellas/75dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/hellas/100dpi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/hellas/Type1" FontPath "/usr/X11R6/lib/X11/fonts/misc/sgi:unscaled" FontPath "/usr/X11R6/lib/X11/fonts/xtest" FontPath "/opt/kde3/share/fonts" InputDevices "/dev/ttyS0" InputDevices "/dev/ttyS1" InputDevices "/dev/ttyS2" InputDevices "/dev/ttyS3" InputDevices "/dev/ttyS4" InputDevices "/dev/ttyS5" InputDevices "/dev/ttyS6" InputDevices "/dev/ttyS7" InputDevices "/dev/ttyS8" InputDevices "/dev/psaux" InputDevices "/dev/logibm" InputDevices "/dev/sunmouse" InputDevices "/dev/atibm" InputDevices "/dev/amigamouse" InputDevices "/dev/atarimouse" InputDevices "/dev/inportbm" InputDevices "/dev/gpmdata" InputDevices "/dev/mouse" InputDevices "/dev/usbmouse" InputDevices "/dev/adbmouse" InputDevices "/dev/input/mice" InputDevices "/dev/input/event0" InputDevices "/dev/pointer0" InputDevices "/dev/pointer1" InputDevices "/dev/pointer2" InputDevices "/dev/pointer3" EndSection Section "ServerFlags" Option "AllowMouseOpenFail" EndSection Section "Module" Load "dbe" Load "type1" Load "freetype" Load "extmod" Load "glx" Load "v4l" EndSection Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "be" Option "XkbModel" "pc105" Option "XkbRules" "xfree86" EndSection Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Device" "/dev/input/mice" Option "Name" "PS/2 Generic Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" EndSection Section "Monitor" HorizSync 31-38 Identifier "Monitor[0]" ModelName "800X600@60HZ" Option "DPMS" VendorName "--> VESA" VertRefresh 50-60 UseModes "Modes[0]" EndSection Section "Monitor" HorizSync 29-32 Identifier "Monitor[1]" ModelName "Unknown" VendorName "Unknown" VertRefresh 50-62 UseModes "Modes[1]" EndSection Section "Modes" Identifier "Modes[0]" Modeline "800x600" 36.88 800 832 912 1024 600 601 604 621 Modeline "800x600" 40.0 800 840 968 1056 600 601 605 628 +hsync +vsync EndSection Section "Modes" Identifier "Modes[1]" Modeline "640x480" 23.86 640 656 720 800 480 481 484 497 EndSection Section "Screen" DefaultDepth 16 SubSection "Display" Depth 15 Modes "800x600" EndSubSection SubSection "Display" Depth 16 Modes "800x600" EndSubSection SubSection "Display" Depth 24 Modes "800x600" EndSubSection SubSection "Display" Depth 32 Modes "800x600" EndSubSection SubSection "Display" Depth 8 Modes "800x600" EndSubSection Device "Device[0]" Identifier "Screen[0]" Monitor "Monitor[0]" EndSection Section "Screen" DefaultDepth 16 SubSection "Display" Depth 15 Modes "640x480" EndSubSection SubSection "Display" Depth 16 Modes "640x480" EndSubSection SubSection "Display" Depth 24 Modes "640x480" EndSubSection SubSection "Display" Depth 32 Modes "640x480" EndSubSection SubSection "Display" Depth 8 Modes "640x480" EndSubSection Device "Device[1]" Identifier "Screen[1]" Monitor "Monitor[1]" EndSection Section "Device" BoardName "MGA G400 AGP" BusID "1:0:0" Driver "mga" Identifier "Device[0]" Option "hwcursor" "off" Screen 0 VendorName "Matrox" EndSection Section "Device" BoardName "MGA G400 AGP" BusID "1:0:0" Driver "mga" Identifier "Device[1]" Option "hwcursor" "off" Screen 1 VendorName "Matrox" EndSection Section "ServerLayout" Identifier "Layout[all]" InputDevice "Keyboard[0]" "CoreKeyboard" InputDevice "Mouse[1]" "CorePointer" Option "Clone" "off" Option "Xinerama" "off" Screen "Screen[0]" Screen "Screen[1]" RightOf "Screen[0]" EndSection Section "DRI" Group "video" Mode 0660 EndSection Section "Extensions" EndSection

1 0

Re: [SLE] 9.3: Keyboard keymaps and xorg
by AmigaPhil＠ping.be 16 Jun '05

16 Jun '05

ken (gebser(a)speakeasy.net) wrote something I wish to comment : (news:<42B1569A.8070105(a)speakeasy.net> posted on 16-juin-05 11:38:18) >>>I saw there is also a file SaX.log there. I find it very informative >>>as to the trouble I have encountered while trying to configure the >>>keyboard with SaX2. Here are some lines I find interesting >>>(between "<" and ">" are comments I've added): >>> >>>13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ >>><content of xorg.conf here> >>>] >>>sh: -c: line 0: unexpected EOF while looking for matching `'' >>>sh: -c: line 1: syntax error: unexpected end of file >>>13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ >>>< ... > >>> > > It looks like there's a single quote somewhere which is causing the > parser some problems. I've just checked in xorg.conf, but haven't found any single quote in there. This error referer to another file/script ? (I'll attach my xorg.conf file in another post.) AmigaPhil, world citizen. /No MS-HTML mail please/ PGP key: 0x9C07F6C1 -----BEGIN PRIVATE MESSAGE----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. Tt0VtSLVpKVvSMyFppaIrHyOlFdSDAlvOJ3ycvxpOtc2ytpVUzIyWEanYOHAEyzIHMU6vIIV zHVFGvSIFpna5xBzOatFylxVUDMHAMCyHOTyEKHAjFRVpIqtz5JWthjSEtLFtRJkJVDbMalH zhHqvIOJO1ExR5GBRLtDRt0dOODlVVf1OEqKWqnzvoItqvPEFRlUMFRpdIWPMNlMRHOq5vDO OIbu3tVGt -----END PRIVATE MESSAGE----- That's not a bug! It's supposed to do that!---->*

1 0

9.3: Keyboard keymaps and xorg
by AmigaPhil＠ping.be 16 Jun '05

16 Jun '05

Here is a quick summary of a keyboard configuration problem I have exposed to the Suse support team, and the suse-linux-e mailing list (with so far, no solution on sight): I recently installed successfully the Suse 9.3 Pro distribution. During the installation, I choose and test with success an azerty, Belgium layout keyboard. All the installation went fine. But now the installation is completed (and online updates done), the keyboard is no more working properly under KDE (nor under FVWM). I can still use it as an AZERTY keyboard, but the Belgium layout is missing (I can not e.g. print the e acute or the aroba, located on the "2" key.) The keyboard is working properly from a console at runlevel 3 thought. There is no way I can configure the keyboard using yast as none of the changes I make are taken in account. From Yast > Monitor and Screen (Sax2), I got the following message after the test stage: (WW) MGA(0): Option "CalcAlgorithm" is not used (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap I cannot use SaX from runlevel 3 as I'm faced to black screen with just the mouse pointer showing up. When I left click, a small banner displaying "Desk: 0 geometry" pops up, but nothing else works, I have to reset the computer to get out. >From a console, the command "setxkbmap -v 10" return this: Setting verbose level to 10 locale is C Applied rules from xfree86: model: pc104 layout: be variant: basic Trying to build keymap using the following components: keycodes: sfree86+aliases(azerty) types: complete compat: complete symbols: pc/pc(104)+pc/be(basic) geometry: pc(pc104) Error loading new keyboard description I tried to re-install the main xorg package, but it failed. Here is the error output: ERROR(InstTarget:E_RpmDB_subprocess_failed) --- /etc/permissions.easy /etc/permissions.local setting /usr/X11R6/bin/Xorg to root:root 4711. (wrong permissions 0711) Finished. moving XF86Config to XF86Config-20050615 2005-06-15 11:06:43 xorg-x11-6.8.2-30.i586.rpm install failed rpm output: error: unpacking of archive failed on file /etc/X11/xkb/compat/accessx: cpio: rename failed - Permission denied I noticed these lines from /var/log/Xorg.0.log : (**) Option "CoreKeyboard" (**) Keyboard[0]: Core Keyboard (**) Option "Protocol" "Standard" (**) Keyboard[0]: Protocol: Standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "pc104" (**) Keyboard[0]: XkbModel: "pc104" (**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse[1]: Buttons: 3 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap And from /var/log/SaX.log : 13-Jun 23:23:57 <X> Logging File contents: /tmp/sax2-8841/xorg.conf [ <content of xorg.conf here> ] sh: -c: line 0: unexpected EOF while looking for matching `'' sh: -c: line 1: syntax error: unexpected end of file 13-Jun 23:24:10 <X> Logging File contents: /var/log/xlog [ < ... > (**) Option "CoreKeyboard" (**) Keyboard[0]: Core Keyboard (**) Option "Protocol" "Standard" (**) Keyboard[0]: Protocol: Standard (**) Option "AutoRepeat" "500 30" (**) Option "XkbRules" "xfree86" (**) Keyboard[0]: XkbRules: "xfree86" (**) Option "XkbModel" "pc104" (**) Keyboard[0]: XkbModel: "pc104" (**) Option "XkbLayout" "be" (**) Keyboard[0]: XkbLayout: "be" (**) Option "CustomKeycodes" "off" (**) Keyboard[0]: CustomKeycodes disabled (**) Option "Protocol" "explorerps/2" (**) Mouse[1]: Device: "/dev/input/mice" (**) Mouse[1]: Protocol: "explorerps/2" (**) Option "CorePointer" (**) Mouse[1]: Core Pointer (**) Option "Device" "/dev/input/mice" (==) Mouse[1]: Emulate3Buttons, Emulate3Timeout: 50 (==) Mouse[1]: Buttons: 3 (II) XINPUT: Adding extended input device "Mouse[1]" (type: MOUSE) (II) XINPUT: Adding extended input device "Keyboard[0]" (type: KEYBOARD) The XKEYBOARD keymap compiler (xkbcomp) reports: > Error: Can't find file "pc" for geometry include > Exiting > Abandoning geometry file "default" Errors from xkbcomp are not fatal to the X server (EE) Couldn't load XKB keymap, falling back to pre-XKB keymap < ... > ] I also tried to change the Option "XkbLayout" "be" to Option "XkbLayout" "be-latin1" in the files: /etc/X11/xorg.conf /etc/X11/xorg.conf-Linux1 /etc/X11/xorg.conf.saxsave /etc/X11/XF86Config hit CTRL-ALT-BACKSPACE and re-log in ... No improvement. (I restored everything to the initial "be" as to not further mess the X config, and because of the "Please do not edit this file" :-) ) BTW, the "be-latin1" for XkbLayout is linked to the file /usr/share/kbd/keymaps/i386/azerty/be-latin1.map.gz Am I right ? I haven't found a be-latin1 file somewhere else.) Any idea as to what is wrong here (and how to solve this) ? AmigaPhil, world citizen. _No MS-HTML mail please_ PGP key: 0x9C07F6C1 -----BEGIN NSA TEASER----- The following garbage may or may not contain crypted message. At least you now know I'm an advocate for the respect of privacy. StSlHpnWJvtpHrntyWyVtMbxHHCIvk5nayVYyqRza5FFHHtHvBLlROy0cVTAFFovAEpVDUH0 EUGzMxjUzMxOtVqOzUEVFPtdpShIlDTvtD1MVAJlpVyIRISlFRAOvEzqOB1tcKD3EIpqIlaF RyOVHjIVRJpttSJOWIzd5byIMVELFD6JW2xMOy5zILqOFODvMKRalGM3EHNtOVpvvOuPGf== -----END NSA TEASER----- DREAM: Just testing my brain!! zzzzzzzzzz

2 1

how to configure 4 monitors by two NVIDIA dualhead graphic cards
by GAO JIN 14 Jun '05

14 Jun '05

I am trying to configure 4 monitors by two NVIDIA dualhead graphic cards under SuSe9.2, but cannot make it anyhow. Can anyone give me some information about it or send me a xorg.conf file. Thank you very much!

3 2

framebuffer-size configuration
by Dieter Jurzitza 13 Jun '05

13 Jun '05

Dear listmembers, in the meantime I created a rpm that allows to set the required parameters for the mtrr settings via yast2 (System -> Editor for /etc/sysconfig -> Hardware -> Framebuffer -> Memory -> FRAMEBUFFERSIZE) Anybody who suffers from the mtrr errors and wants to test, please do so, I appreciate your feedback. Install the rpm attached to this message and set the configurations. I can supply the source - rpm, too, if anyone is interested. To refer to Alain Black's question: naturally you have to set the size accordingly - but what is accordingly the SuSE folks might know much better than I do, so, if someone of the SuSE folks could give a commentary I would highly appreciate. Take care Dieter Jurzitza -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) -----------------------------------------------------------

1 0

xhost: unable to open display
by Annette Bitz 08 Jun '05

08 Jun '05

Hi! On my new box installed with SuSE 9.2 prof. I got a really critical problem. When I say xhost + in a local shell I get the message: xhost: unable to open display "<name-of-box>:0.0" I also tried to do "xhost <name-of-remote-box>" with the same result. The display name is set correctly (as printenv says). This is very urgent, for we need to open windows from other, remote boxes on this machine. Without that, it can't be used. :-( Any ideas? Annette -- Geschenkt: 3 Monate GMX ProMail gratis + 3 Ausgaben stern gratis ++ Jetzt anmelden & testen ++ http://www.gmx.net/de/go/promail ++

5 4

RE: [suse-xfree86] fglrx-configuration
by Black, Alain 06 Jun '05

06 Jun '05

Dieter, I have one question, is 128 MB the size of memory on your video card? Mine has 256, so would I need to double that? -Alain -----Original Message----- From: Dieter Jurzitza [mailto:dieter.jurzitza@t-online.de] Sent: Friday, June 03, 2005 1:14 PM To: suse-xfree86(a)suse.com Subject: Re: [suse-xfree86] fglrx-configuration Dear Alain, dear listmembers, please find my personal README regarding the framebuffer issue attached to this file. If you find messages like "vmalloc error" on the F10 - console you have to add a parameter "vmalloc=SIZE" to the grub startup line in order to increase the size of the vmalloc buffer to SIZE. I use 192 [MB] what seems to be appropriate (default is 128 MB (?) as I found out) I am currently on the way to set up a package for SuSE one may configure via yast, I'll provide it to the list as soon as it is available. Take care Dieter Jurzitza Am Mittwoch, 1. Juni 2005 22:31 schrieb Black, Alain: > Please do. > > I have seen that error if xdm or twm attempted to start as my window ******************** -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) -----------------------------------------------------------

1 0

Slow
by Carl 05 Jun '05

05 Jun '05

What has happened there have been no messages since May 2 Is there now a replacement list relative to XORG which is on 9.2+ Sincerely Confused, -- ----------=====<<<<<CWSIV>>>>>=====----------- | \ /|\ || |\ / |~~\ /~~\ /~~| //~~\ | \ / | \ || | X |__/| || |( `--. |__ | | \| \_/ / \ | \ \__/ \__| \\__/ -------===<<<CWSIV(a)BLUEBOTTLE.COM>>>===-------

1 0

RE: [suse-xfree86] fglrx-configuration
by Black, Alain 03 Jun '05

03 Jun '05

Please do. I have seen that error if xdm or twm attempted to start as my window manager instead of gdm. Under gdm I do not see that error message. But it would be nice to double check my system anyways. -Alain. -----Original Message----- From: Dieter Jurzitza [mailto:dieter.jurzitza@t-online.de] Sent: Wednesday, June 01, 2005 1:28 PM To: suse-xfree86(a)suse.com Subject: [suse-xfree86] fglrx-configuration Dear listmembers, configuring fglrx (ATI Radeon 9600XT @ 128MB) I saw two types of error messages on the F10 - console: 1.) mtrr overlap issues. 2.) vmalloc error messages. After googling and reviewing the documentation I found a solution for this. I have not seen any reference to this on the list and would be interested if anyone out there saw similar issues. There are no references in the SuSE installation README, too. I prepared a documentation (for myself) how to cope with this, if anybody is interested I would post it to the list. Take care Dieter Jurzitza -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) ----------------------------------------------------------- -- To unsubscribe check the List-Unsubscribe header For additional commands, email: suse-xfree86-help(a)suse.com

2 1

Problems with X with Intel graphic controler 82865 G (Chip i830) after update from 8.0 to 9.1
by Alexander Beck-Ratzka 02 Jun '05

02 Jun '05

Hello list, I can't start X after an update from SuSE professional 8.0 to SuSE professional 9.1, and I believe the problems arise, because I've installed an the XFree86 Version 4.3.99.902 (4.4.0 RC 2) on my former SuSE release. The reason for installing XFree86 Version 4.3.99.902 where problems with Intel graphic controler 82865 G (Chip i830). After an BIOS update, I've solved these problems, but after my update to 9.1, I cannot start X, even not in a low resolution :-( Before looking for errors reason, I like ot have a clear system environment. Therefore I like to deinstall XFree86 Version 4.3.99.902, and ot install the X-utilities from the SuSE 9.1 distribution. My question now is: what must I do to deinstall XFree86 Version 4.3.99.902 completely; that means: which directories must be removed (including fonts), how can I update the SuSE package description? A presentation of my logfiles in this email is not possible; attachments (I've tried an cong.tgz) will be removed from the emails to this list, and putting the XF86Config and the X-Logfile directly to the body makes the email to large to be put to the list. So if anyone likes to have these files, please send me an email to my address directly (can be seen with "reply to all" ), and you'll get these documents from me to your home address... Thanks in advance! Alexander

2 1

fglrx-configuration
by Dieter Jurzitza 01 Jun '05

01 Jun '05

Dear listmembers, configuring fglrx (ATI Radeon 9600XT @ 128MB) I saw two types of error messages on the F10 - console: 1.) mtrr overlap issues. 2.) vmalloc error messages. After googling and reviewing the documentation I found a solution for this. I have not seen any reference to this on the list and would be interested if anyone out there saw similar issues. There are no references in the SuSE installation README, too. I prepared a documentation (for myself) how to cope with this, if anybody is interested I would post it to the list. Take care Dieter Jurzitza -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) -----------------------------------------------------------

1 0

Problems with X with Intel graphic controler 82865 G (Chip i830) after update from 8.0 to 9.1
by alibeck＠berlinet.de 01 Jun '05

01 Jun '05

Hello list, again, this time with attachment... --------------------------------------- Hello list, once again, problems with X :-( I've updated my SuSE Professional from 8.0 to 9.1, and I've lost with this udate my X desktop enironment :-( It was quite hard to get run my SuSE 8.0 on a DELL computer using the Intel graphic controler 82865 G (Chip i830); an on board solution. Now, after my update I can't start X, and I don't know why. I hope for help. The configuration file, and the logfile are appended in the gzipped at the end of this email. Thanks in advance. Alexander

2 1

Problems with X with Intel graphic controler 82865 G (Chip i830) after update from 8.0 to 9.1
by alibeck＠berlinet.de 01 Jun '05

01 Jun '05

Hello list, once again, problems with X :-( I've updated my SuSE Professional from 8.0 to 9.1, and I've lost with this udate my X desktop enironment :-( It was quite hard to get run my SuSE 8.0 on a DELL computer using the Intel graphic controler 82865 G (Chip i830); an on board solution. Now, after my update I can't start X, and I don't know why. I hope for help. The configuration file, and the logfile are appended in the gzipped at the end of this email. Thanks in advance. Alexander (See attached file: data.tgz)

1 0