On Wed, 2010-08-25 at 17:55 -0400, Joe(theWordy)Philbrook wrote: > It would appear that on Aug 24, Ralf Mardorf did say: > > > Hahaha :D > > > > I still run openSUSE 11.2 and used sax to give me the needed xorg.conf > > lines for my Ubuntu installs, that came with this new, annoying > > configurations. > > > > Just 2 cents, to keep it easy, install a small Suse 11.2 or earlier > > openSUSE, run sax and add the result to your other Linux, with some > > tweaking, you can't copy it, but you'll be able to merge it manually. > > Well I take it from your description of manually merging the xorg.conf that > for those Linux distros that still have an xorg.conf with subsections like: > > SubSection "Display" > Depth 24 > EndSubSection > > there is at least some chance that adding a "Modes" line right after the > "Depth" line that lists the valid screen sizes my graphics card/monitor > support with the desired default screen size moved to the first listed > position, has a chance of working??? > > As far as getting the appropriate list of screen sizes for my set-up goes, I > don't need to install OpenSuSE 11.2 or before to get it. As I mentioned in > my initial message, While my PCLinuxOS installation doesn't offer e16, It's > xorg.conf does list the modes. so I can copy that stuff from there...
Trial and error and use Google (unfortunately still the best search engine when having issues with Linux) for Ubuntu Howtoes regarding to xorg.conf. My xorg.configs aren't perfect, just fit to my needs for most stuff. > > AFAIK there are no xorg.conf online calculators able to give the needed > > information. > > > > Phew, good to know, that I should keep my xorg.conf's, resp. to keep > > openSUSE 11.2 :D. > > > > I hate this new Linux X style that makes Linux for this thing more > > annoying than even Windows is. I'm a tube monitor user, because I prefer > > it to displays, when doing artwork and there are additional issues, if > > you need to set up the frequencies for an old tube monitor, that still > > has got a better quality regarding to colours. > > > > Bad, that Linux goes this new way, for the X configuration. > > Yes & No... I like the idea of good auto detection. But I can't think of > any reason why they couldn't have based it on a logic something like: > > if [ -e /etc/X11/xorg.conf ] > then > #insert code to use it here > else > #insert code to run autodetect and create xorg.conf here > fi > > And perhaps a kernel option for new hardware that automatically renames the > existing xorg.conf so that the above logic would create one for the new > hardware... Well, for GRUB2 they did something similar, anyway, I changed the grub updater script and edit grub.cfg, the new menu.lst, manually. There's no perfect auto-detection ;). > But instead they seem to think that anything they can auto detect doesn't > need to be in a configuration file anymore. which means a user who needs > to tweak the config for some reason, is out of luck. <<<SIGH>>> Full ACK! And it's impossible to google just 30 minutes to get the information what script is in which directory and even if you should find those scripts, not everybody is able to edit them and with an upgrade those scripts might be overwritten. > > GDM, KDM and frame based desktops, e.g. ION, sometimes need a good > > xorg.conf, whereas DEs like KDE and GNOME sometimes are able to do > > individual settings, anyway, very often with bad limitations. > > Now I'm confused. I thought GDM and KDM were the Display manager modules > for Gnome and KDE (respectively)... So if KDE doesn't need the xorg.conf > then KDM, it's Display manager component, shouldn't either??? Yesno :D, I guess for Hardy, resp. 64 Studio 3.0-beta3, didn't booted it for a long time, I've got a xorg.conf, that gives me the wanted resolution for GNOME, but GDM has got a different resolution, for Karmic, resp. 64 Studio 3.3 alpha the resolution for GDM and GNOME is the same. When I'm talking about GDM and KDM, I just guess of the login screen for sessions. > Though to me as a dedicated startx user that's a moot point, though with my > Xubuntu (Lucid) I had to install a "simple" display manager "slim" that > unlike the latest versions of KDM & GDM still listens to a root command > sequence of: > > update-rc.d -f slim remove > update-rc.d slim stop 20 2 3 4 5 . > > to let me boot to a NON-gui login screen and not have a running display > manager blocking my attempts to initialize X with startx... I keep GDM or KDM, as I keep PulseAudio, annoying because I'm a real-time audio user. We should use Gentoo, Arch etc. only and not install GDM, KDM, PulseAudio, DBUS etc. ... OTOH, well, those 'prefabricated' distros do have some advantages. > > So, it's not an E issue, but a modern distribution issue. > > Agreed, if the traditional way to set the screen resolution for e16 is to > set the default by editing the xorg.conf than the problem is the modern > configuration methods being adopted by many distros... > > > It would appear that on Aug 24, Ralf Mardorf also said: > > > PS: In addition this might help you to fix your configurations, but note > > that I didn't take care of ION and E ... > > > > spinymouse1...@suse11-2:~> cat /etc/X11/xorg.conf > > # nvidia-xconfig: X configuration file generated by nvidia-xconfig > > # nvidia-xconfig: version 1.0 (buildmeis...@builder58) Fri Mar 12 > > 02:12:40 PST 2010 > > > > # /.../ > > # SaX generated X11 config file > > # Created on: 2009-12-17T15:07:50+0100. > > # > > # Version: 8.1 > > # Contact: Marcus Schaefer <[email protected]>, 2005 > > # Contact: SaX-User list > > <https://lists.berlios.de/mailman/listinfo/sax-users> > > # > > # Automatically generated by [ISaX] (8.1) > > # PLEASE DO NOT EDIT THIS FILE! > > # > --<snip>-- > > I might find something useful in that included config file. But of course > sax would have written it for your hardware configuration, not mine... True, it's just might be a help to see some options for xorg.conf, that you might not remember from oldish installs. > However the above quoted portion includes two useful clues. > > I now know that while "which sax" finds nothing on my system "which isax" > does... as does "which nvidia-xconfig". Which did create an xorg.conf on my > OpenSuSE 11.3 (Though like most my other distros, it doesn't bother listing > any screen modes. Sigh.. Still it might work to insert said "Modes" line. > {see above} ) > > In any case I thank you for the information. > > > It would appear that on Aug 25, Kim Woelders did say: > > > On Tue, 24 Aug 2010 21:39:07 +0200, Joe(theWordy)Philbrook > > <[email protected]> wrote: > ---<snip>--- > > > Since I don't do well with fine print I tend to use vga=normal so that my > > > console screens are easy to deal with. This results in a default xserver > > > screen mode of 1280x1024, which with kde, xfce and e17 I can set to the > > > 1024x786 that works out well for my eyes. > > > > > > However if e16 has a screen resolution tool, I can't find it. > > ... > > > > E16 doesn't have a such a tool. IMO this thing is more a desktop > > environment or graphics card configuration utility than a WM feature. > > Yeah I'd agree with that assessment. > > > Maybe you can use nvidia-settings to re-write your xorg.conf for a > > permanent solution or use xrandr at session startup? > > Well I might risk manually editing my assorted xorg.conf files. I don't see > what it could hurt if I inserted the missing "Modes" line(s) Like I > described above as long as the said modes within it are valid for my > hardware. !!! To be safe I first would do a backup of the default xorg.conf. > > But it now looks like I might not have to. At least not on my OpenSuSE 11.3 > installation. You mentioned "xrandr" as a possible solution. Which led to a > quick scroogle Scroogle unfortunately isn't fin for all languages, at least the German Scroogle is a PITA and alternative search engines, e.g. ixquick, are less good, than Google is :(. I still recommend to use Google, when having issues. Just 2 cents. > search and the discovery that xrandr isn't some fancy > random value setting tool as my first guess from it's name suggested ;-) > > Then I checked and discovered that xrandr was already installed and with a > little tweaking I discovered that including "xrandr -s 3 &" in my > ~/.xinitrc causes e16 to open up with the desired resolution ( and unlike > calling it after e16 starts, all my virtual desktops wind up sized > properly. Though I did have to resize and re-remember a couple of windows > so that they would fit within the new desktop size... > > With any luck this one method will work for all my Linux distros. > > Thanks! I'll keep my fingers crossed. Ralf ------------------------------------------------------------------------------ Sell apps to millions through the Intel(R) Atom(Tm) Developer Program Be part of this innovative community and reach millions of netbook users worldwide. Take advantage of special opportunities to increase revenue and speed time-to-market. Join now, and jumpstart your future. http://p.sf.net/sfu/intel-atom-d2d _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
