December 2009 - openSUSE X.org - openSUSE Mailing Lists

[opensuse-xorg] Xorg freezes under openSUSE 11.2 with Intel 855GM
by User66 09 Nov '10

09 Nov '10

Hi openSUSE community, I have a strange problem with X under openSUSE 11.2. After starting KDE 4.x or Gnome, the Xorg system freezes after 5-15 minutes. If that occurs I can still move the mouse, but any click or keyboard event is not recognized any more. Can't switch to console. But the system itself works, since I can login by ssh. All running (server) applications like Apache and MySQL still work. In order to use X again, I have to reboot (init 6 does not work, I have to type "reboot " twice). init 3 and init 5 does not work after logging in by ssh, killing X process does also not fix it. I really have to reboot. I have an Intel 855GM Integrated Graphics Device on board. I have already checked the RAM with memtest, everything okay. There are no error messages in syslog. I have tried disabling DRI, but no effect. Disabling Video cache in BIOS or reducing the video buffer size did also not help. Without logging in to KDE or Gnome the system runs stable for weeks, so I am pretty sure that Xorg is the problem. I guess that these problems are caused by the Intel graphics driver. I can remember that I had similar problems 1-2 years ago (freezes only with KDE 3 and 4, not Gnome). I am pretty sure, that the first problems started after switching to the Intel driver (from the old 810 driver), but in openSUSE 11.1 it was running fine. Now in openSUSE 11.2 the X system freezes after some minutes working. == System Info == lspci -v: 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Subsystem: Intel Corporation 82852/855GM Integrated Graphics Device Flags: fast devsel Memory at 80000000 (32-bit, prefetchable) [disabled] [size=128M] Memory at 7e100000 (32-bit, non-prefetchable) [disabled] [size=512K] Capabilities: [d0] Power Management version 1 ---- xorg.conf: Section "Module" Load "dri" Load "dbe" Load "extmod" Load "glx" EndSection Section "ServerFlags" Option "AIGLX" "on" Option "AllowMouseOpenFail" "on" Option "ZapWarning" "on" EndSection Section "Device" BoardName "855 GM" Driver "intel" Identifier "Device[0]" Option "EXANoComposite" Option "monitor-VGA" "Monitor[0]" VendorName "Intel" EndSection ---- cat /proc/mtrr: reg00: base=0x000000000 ( 0MB), size= 2048MB, count=1: write-back reg01: base=0x07e000000 ( 2016MB), size= 32MB, count=1: uncachable reg02: base=0x07ff00000 ( 2047MB), size= 1MB, count=1: write-back ---- See also Xorg log attached. Any ideas ? Thanks in advance Ralf

5 6

[opensuse-xorg] gui like gsynaptics for kde4
by Robert Riemann 12 Jan '10

12 Jan '10

Hi all, I have thought about creating a gui like gsynaptics for kde4/opensuse11.3 that allows to simply change the settings for tapping or scrolling on a touchpad. I found out, that synclient might work. It requires shm, but this seems to be default for automatic configured touchpads (without xorg.conf), but settings need to be reset after a new boot. I tried also to create a config file for hal (*.fdi), but it didn't have any effect for me (can someone confirm that?). http://fedorasolved.org/Members/khaytsus/configuring-synaptics-using-hal So which way should a gui go? hal? synclient? something else? I am going to write the gui using ruby with kde4 bindings. Greets Robert -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

1 1

[opensuse-xorg] fglrx as of December / openSUSE 11.1
by Dr. Ing. Dieter Jurzitza 21 Dec '09

21 Dec '09

Dear listmembers, in "sync" with my previous message I can report a failure of this driver with openSUSE 11.1 & AMD 64 as well. Graphics Card is a HD4670, I performed (as always) the following steps: ./ati-driver-installer-9-12-x86.x86_64.run --buildpkg SuSE/SUSE111-AMD64 and uninstall the previous installation of fglrx, unload module fglrx and then perform a startx (same xorg.conf as before). The result is a black screen of death. Returning to the old driver brings functionality back. This is just to let you know, take care Dieter Jurzitza -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) ----------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

1 0

[opensuse-xorg] fglrx - driver / opensuse 10.3
by Dr. Ing. Dieter Jurzitza 21 Dec '09

21 Dec '09

Dear listmembers, though the driver generation is still enabled for opensuse 10.3 this is just to let you know that the latest fglrx - driver does not work any more on opensuse 10.3. No sense to create the apropriate rpm package, the only thing you get is a black screen of death .... Tested on opensuse 10.3 using a AGP Radeon 2600. To whom it might concern, take care Dieter Jurzitza -- ----------------------------------------------------------- | \ /\_/\ | | ~x~ |/-----\ / \ /- \_/ ^^__ _ / _ ____ / <°°__ \- \_/ | |/ | | || || _| _| _| _| if you really want to see the pictures above - use some font with constant spacing like courier! :-) ----------------------------------------------------------- -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

1 0

[opensuse-xorg] The Future of SaX2
by Egbert Eich 01 Dec '09

01 Dec '09

The Future of SaX2 ================== For many years now SUSE Linux came with a tool to configure the setup of the desktop which was second to none in the Linux and Free Software world: SaX2. It made it easy even for unexperienced users to configure video modes, screen layouts as well as keyboard and input devices for the X Window System. Meanwhile however the technology around the X Window System server as shipped by X.Org has evolved: hot pluggable input and output devices made a static configuration infeasible. Automatic configuration and dynamic reconfiguration mechanisms have been developed such that today most of the tasks that SaX2 was able to do are done fully automatically on the fly and can be modified from within a desktop session. Modern desktops like Gnome and KDE provide convenient user interfaces for that. A static configuration of the Xserver as done by SaX2 is still possible, yet it does not work well together with dynamic reconfiguration. The changes to SaX2 to improve this situation would be considerable and will require substantial changes in its design. Novell has decided to no longer invest in development maintenance of SaX2 but instead rely on the new automatic and dynamic configuration features and invest in desktop applets to perform dynamic changes. Federico Quintero for instance has created gnome-display-properties. The resources needed to keep SaX2 in sync with changes in X.Org will exceed what the people at Novell who have been maintaining SaX2 next to their normal work tasks in the past few years are able to spare. Thus starting with openSUSE 11.2 SaX2 will no longer be offered as a configuration option in YaST. It is still shipped and installed by default but it's likely to be deprecated further when it's usefulness diminishes further. People have raised objections to this decision by Novell's as they believe a static configuration is still crucial while auto configuration is still new and still fails in a few cases where SaX2 successfully produces a usable configuration. Yet, the decision was driven by what Novell sees its business needs and thus is not up for discussion. However the fate of SaX2 is not at all up to Novell: SaX2 has been Free Software all along and as with all Free Software it's up to each individual to help driving it in the direction they like to see it go - independently of corporate business needs and interests. All it needs is a dedicated bunch - a group of people who still believe in it's value and who are willing to drive it further - or the corollary to this: if there is no such community it's most likely not considered useful enough to warrant the effort. Thus if you think a configuration tool for X like SaX2 is still what the world and you need, it is now time to act: Don't sit there and complain about a decision you cannot influence, pick up and start driving SaX2 development yourself - the sky's the limit! Don't be shy altering even fundamental basics of the SaX2 code basis - the configuration system in X has vastly changed, so a configuration tool needs to change the same way. The resources to do so are there: The project is hosted at: http://developer.berlios.de/projects/sax/ The openSUSE Devel project is at: https://build.opensuse.org/package/show?package=sax2&project=X11%3AUtilities Please join the developers mailing list at https://lists.berlios.de/mailman/listinfo/sax-devel If you are interested to contribute to SaX2. Cheers, Egbert. -- To unsubscribe, e-mail: opensuse-xorg+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-xorg+help(a)opensuse.org

1 0