On Mon, 2008-04-21 at 10:54 -0400, Jim wrote: I'm curious as to why you need one? We're working ever toward not needing xorg config files. -- Jesse Keating Fedora -- All my bits are free, are yours?

Jesse Keating wrote: Well to tell you the truth Jesse I don't need one , but I do need to have my "USB" mouse detect properly.

On 21/04/2008, Jesse Keating <jkeating(a)redhat.com&gt; wrote: To set the default xrandr options (resolution, screen layout), and to define SHMConfig so I can configure my touchpad. MEF -- Mary Ellen Foster -- http://homepages.inf.ed.ac.uk/mef/ Informatik 6: Robotics and Embedded Systems, Technische Universität München and ICCS, School of Informatics, University of Edinburgh

Jesse Keating <jkeating <at> redhat.com> writes: Sometimes it might not be a question of being wrong but a personal preference. For example I like a certain speed of the cursor across my laptop screen when sliding my finger across the touchpad - but that speed may not suit everyone so I would guess that would still need to be configurable - I do that in xorg.conf (maybe there is a kde config for it somewhere, but also I would like to be able to set it when the dkm login screen is there before I log in so that the movement speed is always what I want - even if I switched desktops. For someone with unsteady hands this parameter would be preferred set for a slower screen transit.

Robert McBroom (TNWestTex) wrote, On 04/22/2008 11:34 AM: And even if it does work correctly, there are situations where you get newer hardware but the project REQUIRES certain things to stay the same[1]. With X the way it is now (pre F10) we can put a modeline in (probably captured from the auto config output) and tell X 'for all users' use THIS definition, and there is no tweaking around in each user's window manager configuration[2]. [1] i.e., that 19 inch 800X600 monitor you replaced (try buying a new one with that $#!^y of a spec today) with an 19 inch 1920x1200 LCD (multi sync that can do 800x600). [2] there were times I thought X configuration was difficult, but window manager configuration is a maze of twisty paths all different and some incapable! -- Todd Denniston Crane Division, Naval Surface Warfare Center (NSWC Crane) Harnessing the Power of Technology for the Warfighter

Anne Wilson wrote: Hum... I'm not having any xorg.conf file and I have not run into any problems. ( so far : ) T61p (x86_64bit ) and Dell inspiron 6000 ( i386 ) It would be good to have it posted here first I think and ajax ( or some other that might knows the status of things and could comment on what has been done and what remains or if things should not already been fixed.) A lot of this has already been fixed (some in git )I think ( correct me if i'm wrong ). You should not experience keyboard layout not being correct ( or the same as you chose in anaconda) when installing the preview release. ( you will experience that with previous releases and the preview live CD, ). If you are using any of the other previous releases, beta, rawhide iso's or the preview live cd then you need to. A. Use the tool in gnome or kde or system-config-keyboard from cli, to set the keyboard to the layout you choose in ( Gnome System --> Preference --> Hardware --> Keyboard --> layouts --> Add ) ( Somebody who uses can kde or xfce for can give the details for that. ) B. Add an section to xorg.conf ( IT IS GONNA BE REMOVED IN F10! TRY CONFIGURATION TOOLS FIRST ) If you dont like your mouse speed again use the corresponding tools in you desktop environment to increase it!!! If the tools available don't work, then file a bug!. Best regards. Johann B.

Anne Wilson wrote: To be on the safe side backup or simply mv /etc/X11/xorg.conf /etc/X11/xorg.conf.old and this is fully updated F9 right? And if something is not working and you have configured ( worst case try again after you removed xorg.conf ) using the tools provided in gnome/kde/cli report it back ( keyboard etc.. ) Best regards Johann B.

On Monday 21 April 2008 20:15, Jóhann B. Guðmundsson wrote: Experiment complete. Removing the stanza resulted in return to US keyboard. Running system-config-keyboard found UK keyboard already highlighted. OK'ing resulted in UK keyboard being used. Conclusion - bug in system-config-keyboard is fixed. Question - if s-c-k knows that UK keyboard is the right one, why do I have to tell it to accept it? Anne

On Mon, 2008-04-21 at 18:02 +0100, Mary Ellen Foster wrote: That can be a preference of your login session. -- Jesse Keating Fedora -- All my bits are free, are yours?

On Mon, Apr 21, 2008 at 11:13:28AM -0400, Jesse Keating wrote: For one, how about non-clone-mode XRandR? You need to set the maximum concatenated desktop size you expect to have with the "Virtual" option in xorg.conf. Section "Screen" Identifier "Screen0" Device "Videocard0" DefaultDepth 24 SubSection "Display" Viewport 0 0 Virtual 3200 1600 Depth 24 EndSubSection EndSection What are the plans to make this work automatically without requiring an xorg.conf?

On Mon, Apr 21, 2008 at 8:30 PM, Jesse Keating <jkeating(a)redhat.com&gt; wrote: Just to hijack this to some extent, did I read that support for tapping via Synaptics was deliberately removed? Either way, is there a supported way of getting it back? Scrolling on the pad works but tapping support has disappeared.

On Monday 21 April 2008 11:13:28 am Jesse Keating wrote: But you are going to need a configuration file to remember the preferred settings. It would be good to have a user preference and a global default, but it still needs to be accessable for editing. The problems that I have with the xorg configuration is that it is spread over too many files, documentation is hard to find (and not for a novice) and that the GUI's don't give enough control when they work. This evaluation is the result of several weeks of trying to get my dual head system to work in F9, without complete success. I have a Dell XPS with an nVidia GeForce 8600 GTS. One monitor is a 22" wide screen DVI (1680x1050), the other is a 17" normal VGA (1280x1024). The 17" is connected to the second DVI port through an adapter. I had hopes that the nv driver would handle the 8600, but I was disappointed. The nVidia driver available for F8 works (it took me a week to discover and configure it), but it is not available X consistently fails to properly detect the monitors that are attached. Until this thread I couldn't find any way to have it not operate in mirror mode. Bringing up krandrtray in KDE would make the menu bar disappear. The Display GUI in Gnome doesn't work since it can't detect the monitors, can't be told to not mirror, and can't be told which driver. xrandr is opaque and I still haven't found the right place to put it to have it configure the login screen. Last night I got the xorg.conf from the Xorg.0.log (thanks whoever it was who mentioned it in this list), which gave me a starting point. By editing it and using startx to test it, I was able to get both monitors to work at full resolution. Then I rebooted to run level 5, and the autodetection decided the 17" screen should operate at 1152x864 with a black band on the left. It also decided to change the dpi set up so now I have large text. KDE still doesn't use the monitors properly. Since there is now good way to change the dpi setting, I again have to start editing Xsessions to try to get the resolution I prefer. Even then it doesn't seem to have a direct effect. If you do away with xorg.conf you will need to put the configuration files (and there will have to be configuration files) in a single easily located place, and have an easily editable syntax. The documentation should also be easily accessable. You need to have GUI's that will allow the user to adjust everything and especially be able to override any of the auto-mis-detected settings. The GUI needs to list all the available options, and the effects should be seen immediately. Sorry for the long rant, but it has been a long frustrating trip. The almost operating xorg.conf. Anybody see how to get the 17" monitor to operate in a 1280x1024 mode? Anybody know why the KDE just ignores it? Section "Device" Identifier "Builtin Default nv Device 0" Driver "nv" EndSection Section "Screen" Identifier "Builtin Default nv Screen 0" Device "Builtin Default nv Device 0" SubSection "Display" Viewport 0 0 Depth 24 Virtual 2960 1050 Modes "1680x1050" EndSubSection EndSection Section "Device" Identifier "Builtin Default fbdev Device 0" Driver "fbdev" EndSection Section "Screen" Identifier "Builtin Default fbdev Screen 0" Device "Builtin Default fbdev Device 0" EndSection Section "Device" Identifier "Builtin Default vesa Device 1" # Driver "vesa" Driver "nv" EndSection Section "Screen" Identifier "Builtin Default vesa Screen 1" Device "Builtin Default vesa Device 1" SubSection "Display" Viewport 0 0 Depth 24 Virtual 2960 1050 Modes "1280x1024" EndSubSection EndSection Section "ServerLayout" Identifier "Builtin Default Layout" Screen "Builtin Default nv Screen 0" Screen "Builtin Default fbdev Screen 0" Screen "Builtin Default vesa Screen 1" EndSection I got the second monitor out of mirror mode by adding the Display subsections and changing the "vesa" screen and device identifiers to "1". Looking at it I wouldn't think that changing the identifier strings would have an effect, but xorg.conf is still black magic to me.