In M6 dont have a xorgconfig? Where I configure video and keyboard?
Thanks
Yes, 11.2 is doing away with xorg.conf. You can configure most things from the settings icon from the kickoff menu. Sax2 also has settings for video and keyboard.
Why do I have xorg.conf? (Using M6)
markcynt wrote:
> pilotgi;2035620 Wrote:
>> Yes, 11.2 is doing away with xorg.conf. You can configure most things
>> from the settings icon from the kickoff menu. Sax2 also has settings for
>> video and keyboard.
>
> Why do I have xorg.conf? (Using M6)
Did you update? If so, it was left over from the previous version.
It was a clean install downloaded and installed yesterday.
Oh really, so where would I configure my video chip driver and its option statements? I normally do that in xorg.conf, given that sax2 only supports those in the golden cage.
Oh really, so where would I configure my video chip driver and its option statements? I normally do that in xorg.conf, given that sax2 only supports those in the golden cage.
AFAIU, you can still choose to use xorg.conf for custom configurations if necessary, as many do with Fedora and Ubuntu (both using new Xorg release). Xorg is increasingly relying on hal for configuration, and so no (or minimal) xorg.conf is generated during installation. Some related reading:
[Phoronix] Persistent Configuration Options For X.Org Drivers](http://www.phoronix.com/scan.php?page=article&item=xorg_driver_persistent&num=1)
http://www.tuxradar.com/content/modify-xorgconf-better-performance
Distributions | kdedevelopers.org
I think it would be good idea to make sure you keep a working xorg.conf from openSUSE 11/11.1 just in case you need to use it with 11.2.
Thanks for the reply deano, that makes sense to me. I notice that kubuntu 9.04 has a minimal xorg.conf (relying on hal for k/b and mouse) compared to the dinosaur version in 11.1 - should have been spring-cleaned several releases back, e.g. deprecated font paths, useless modelines.
Quite right, I always keep a copy of my latest working xorg.conf, fstab, and menu.lst, etc on a separate data partition. 
I put into ~/.kde4/env/xrandr.sh
#! /bin/sh
if xrandr | grep "VGA-0 connected" ; then
xrandr --newmode 1400x1050ral 121 1400 1488 1632 1864 1050 1053 1057 1089 +HSync +VSync
xrandr --addmode VGA-0 1400x1050ral
xrandr --output LVDS --off --output VGA-0 --mode 1400x1050ral
else
xrandr --output VGA-0 --off --output LVDS --auto
fi
for autostart to ajust my non-auto-mode VGA monitor. But this leaves kdm login screen in an unconfigured state. Other distributions consider
/etc/kde4/kdm/Xsetup
to use for configuration of kdm. Allthough openSUSE has this file nothing happens when putting xrandr commands there. Where can I configure the kdm login screen?
I think you can use the ~/.xinitrc.template file for this. Edit this and save as .xinitrc
It then gets called when X starts AFAIK. Give it a go and let us know how it goes.
pilotgi wrote:
>
> Yes, 11.2 is doing away with xorg.conf. You can configure most things
> from the settings icon from the kickoff menu. Sax2 also has settings for
> video and keyboard.
>
>
SAX2 no longer has settings for keyboard.
Kickoff - Configure Desktop - Regional & Language - Keyboard Layout.
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
SAX2 no longer has settings for keyboard.
Thanks for correcting that, cloddy. They must have changed it when I wasn’t looking.
I don’t believe you:
How should a personal ~/file have any influence on a system start kdm?
If you want to execute the xrandr settings prior to login, you will need to edit ‘/etc/X11/xinit/xinitrc’. Take a look towards end of script:
Add your own lines here…
day planer deamon
pland &
finally start the window manager
unset WINDOW_MANAGER STARTUP
exec $WINDOWMANAGER
call failsafe
exit 0
I guess you can call your xrandr script (or add directly) from “Add your own lines here…”
pilotgi wrote:
>
>>
>> SAX2 no longer has settings for keyboard.
> Thanks for correcting that, cloddy. They must have changed it when I
> wasn’t looking.
>
This bugzilla gives a bit of the history:
https://bugzilla.novell.com/show_bug.cgi?id=483554
–
Graham P Davis, Bracknell, Berks., UK. E-mail: newsman not newsboy
“I wear the cheese. It does not wear me.”
I don’t believe you for xrandr needs a running X to work properly.
I never said it did. Its just another tool that permits dynamic X-server configuration. I just responded to your initial post in this thread which specifically mentioned adding some xrandr commands. You should have started your own thread in any case.
Bug resolved finally for me personally.