June 2004 - openSUSE X.org - openSUSE Mailing Lists

Question for the Xfree Experts.....SiS 661
by jomunoz 04 Jun '04

04 Jun '04

Mi name is Jorge and I´m studying english, so pardon any offense to your languaje. So let´s start: - I want to know if there is any driver for the SiS 661FX or MX graphic´s chipset. - ¿Does anyone has this graphic´s chip working on linux? Please reply. <spanish> Dios le pague a quien pueda ayudarme </spanish> :) :) -- ______________________________________ Get your free email from www.bolt.com! Powered by Outblaze

1 0

Memory draining fglrx drivers?
by Scott Ferguson 04 Jun '04

04 Jun '04

Maybe I'm the only one who's having this problem (and maybe somebody slipped funny drugs into my lunch), but it seems that my system resources are seriously out of whack since upgrading to 3.9.0 of the fglrx drivers. I can't start TV Time or Mplayer sometimes due to not enough system resources. This started on rare occasions with 3.7.6, but it wasn't nearly this frequent. Anybody else having this problem? --Scott

1 0

sliding xterms from one virtual desktop to the next
by Stanley Long 03 Jun '04

03 Jun '04

SuSE 9.0 with apt upgrades, Matrox G550 dual headed video, one OR two monitors. If only one monitor is connected during the install, SAX2 writes XF86Config with only one Monitor section (monitor[0], modes[0]) and only one screen section, and only one device section. In the single headed configuration, I can grab an xterm (shell ?) and slide it from one virtual desktop to the adjacent virtual desktop, whether above/below or right/left. If I perform an install with two monitors connected, then it is not possible to slide (drag) an xterm from one virtual desktop to the adjacent virtual desktop on the right. Going up/down or to the left is OK. In any case, the xterm can be pushed part way into the adjacent rightward virtual desktop. After switching into that virtual desktop to the right one can grab the xterm and drag it all the way in (left-->right motion). Where is this functionality controlled? It may be part of the edge-resistance adjustments for XFree86. I think this problem began with XFree86 version 4.3.0 Approximately similar differences show up in Debian + KDM + Windomaker and in SuSE + KDM + FVWM. Another change showed up with XFree86 v4.3: SaX2 is not able to expand a single-monitor install to handle dual monitors. It insists that there is no dual-headed capability! It appears to lock into the /etc/X11/XF86Config notation showing only device/monitor/modes/terminals [0]. It can't seem to see that the video card is dual-headed and then add new [1] sections. The practical solutions are: A) manually enter the missing sections and then let YAST call SAX2, or B) replace the single headed XF86Config with a dual headed version archived from a dual-headed install. Does SAX2 correct this in SuSE 9.1?

1 0

SuSE 9.1 and ThinkPad R50p
by Alexandru Codilean 03 Jun '04

03 Jun '04

All, I have followed the interesting discussions about the ATI drivers and SuSE 9.1, that were posted on this list. I have a ThinkPad R50p (with ATI's Fire GL T2) running SuSE 9.0 at the moment. I am considering getting the new 9.1 release, and was wondering if I will have the same issues as the other people who posted on the list. Does anyone know if this is the case? I'll download the live CD and have a look later but was curious to know! Thank you! Tibi ____________________________________________________ Alexandru Tiberiu CODILEAN PhD Student Hunter Hall East, Room 312 Department of Geography & Geomatics University of Glasgow Glasgow G12 8QQ Tel: +44 (0)141 339 8855 ext 0401 Fax: +44 (0)141 330 4894 Email: tcodilean(a)geog.gla.ac.uk Web: http://web.geog.gla.ac.uk/~tcodilean/

3 7

Re: [suse-xfree86] ATI 3.9.0 drivers and Suse 9.1 (somewhat solved?)
by r.maurizzi＠digitalpha.it 02 Jun '04

02 Jun '04

> As I said in the previous messages this is a problem of fglrx drivers > and the Xorg server. This is supposed to be fixed in the Xorg CVS so we > will see it in the next release. I use SUSE's XFree 4.3.99... and the funny thing is that when I tried with kernel 2.4, XFree 4.3 and driver 3.7.6 or older, xv worked... :-) Oh well, I'll wait for the new packages (or for enough free time to try learn how to build them :) ) Ciao, Roberto

1 0

Re: [suse-xfree86] ATI 3.9.0 drivers and Suse 9.1 (somewhat solved?)
by r.maurizzi＠digitalpha.it 02 Jun '04

02 Jun '04

> I get the same warnings/errors with using the 3.7.6 RPM built by SuSE > with Kernel 2.6.4-54.5-default (update kernel) Ok, some update since not trying new kernels it's not very time consuming. I've downloaded 3.9.0 packages, and configured them according to readme. I have the usual warnings in dmesg (Badness in ....), some errors 999 in trying to open /dev/dri/card0 but IT WORKS. Then, I tried to run fgl_glxgears, only to get a "Couldn't get fbconfig" error. Searching Google, I've found (http://odin.prohosting.com/wedge01/gentoo-radeon-faq.html#4_fbconfig question 4.6) that's this caused by a Mesa OpenGL library used instead of the ATI one. SUSE rpms do _not_ contains a libGL.so.1.2 library, so I downloaded ATI rpm, extracted the library and put it in a dir that's ahead of /usr/lib Now fgl_glxgears works :-) Did I miss something? Like, for example, the old switch2<something> scripts? But... there are a couple of troubles elsewhere: - dga doesn't work. If I'm lucky, the apps gives some warnings or errors. But wine, for example, causes a driver crash and the loss of video output from the card. The system is still running (and ACPI shutdown works too ;) but I can't get back the video without a reboot. - xv seems broken. it IS enabled, VideoOverlay parameter is On, OpenGLOverlay is Off, but mplayer for example can't zoom the window. - Celestia from SUSE's rpm segfaults - Self compiled Stellarium 0.5.2, using SDL, can works as expected with OpenGL Ciao, Roberto

2 1

Re: [suse-xfree86] compiling the kernel makes X go crazy
by r.maurizzi＠digitalpha.it 01 Jun '04

01 Jun '04

> > and/or that the relevant DRI module is build and is working (if you're > > using DRI). > > How can I check this (and how do I know if I'm using DRI)? I see you use swsuspend. From their pages at http://swsusp.sourceforge.net/status.html DRI doesn't work since it doesn't have support for power management. That said, when you're using DRI, you can see it in /var/log/XFree86.0.log : in there, there's usually a message about DRI enabled, or DRI failed to load. Besides, to actually have X trying to load the DRI module, in /etc/X11/XF86config there should be a DRI line in Section "Module", like: Section "Module" ... ... Load "glx" Load "dri" EndSection Hope that helps ^^; Ciao, Roberto

3 3

Re: [suse-xfree86] ATI 3.9.0 drivers and Suse 9.1
by r.maurizzi＠digitalpha.it 01 Jun '04

01 Jun '04

> kernel: Badness in do_no_page at mm/memory.c:1455 > or > kernel: Badness in copy_page_range at mm/memory.c:331 > > This seems to happen mostly is Suse 9.1 kernels and not to other > distributions. What do you think is the problem? I have the same messages with driver 3.76, kernel-default-2.6.4-54.5 (the last available from YOU). I'm starting to think this kernel and the patch or the drivers does not like each other. Sadly I don't have time to try a newer kernel in the next days, but maybe one of the new ones from ftp://ftp.suse.com/pub/projects/kernel/kotd/i386 will work... Ciao, Roberto

4 6

Re: [suse-xfree86] ATI 3.9.0 drivers and Suse 9.1
by r.maurizzi＠digitalpha.it 01 Jun '04

01 Jun '04

> Did you try the 3.7.6 fglrx/km_fglrx RPMs built from SuSE? > > ftp://ftp.suse.com/pub/suse/i386/supplementary/X/XFree86/ATI/suse91/fglrx/3… > > Required regparm patches for 9.1 are already applied for them. Yes, I tried those. But I must say I now have problem reproducing the problem, I may have a corrupted km_drm installed (I have a makefile error with km_drm-4.3.99.902-40, and a rpm -vV shows that Makefile has been altered...). Sorry but I can't be more useful since for now I don't have the time to do a proper check of the configuration. I'm about to leave for a trip and have some backlog to sort out. I'll be available for tests only after 13/6 :-( Ciao, Roberto

2 1