[gentoo-amd64] SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[gentoo-amd64] SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Mark Knecht]

It turns out that for me the problem was the ati-drivers package.
Switching to the radeon driver today lowered the CPU usage back to the
9% range that I was used to:

mark@lightning ~ $ top

top - 12:35:05 up  4:07,  3 users,  load average: 0.02, 0.05, 0.16
Tasks:  91 total,   1 running,  89 sleeping,   0 stopped,   1 zombie
Cpu(s): 12.3% us,  2.7% sy,  0.0% ni, 85.0% id,  0.0% wa,  0.0% hi,  0.0% si
Mem:   1025944k total,   431836k used,   594108k free,    19672k buffers
Swap:  2008084k total,        0k used,  2008084k free,   167108k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
11115 mark      15   0  247m 100m  30m S  9.6 10.1  18:13.38 mythfrontend
10794 root      15   0  208m  34m  20m S  3.7  3.5   7:40.66 X
  912 root     -42  -5     0    0    0 S  0.7  0.0   0:50.06 IRQ 217

Cheers,
Mark

On 9/14/06, Mark Knecht <markknecht@gmail.com> wrote:
> Hi,
>    I'm just curious whether anyone besides me is noticing their
> machine feeling somewhat sluggish since doing the gcc-4.1 upgrade?
> Mine seems ot be using a lot of memory. Alt-tabbing between windows
> seems slow. Ethernet traffic in my browser is causing pretty
> noticeable interruptions in things like MythTV.
>
>    I noticed that the rtirq scripts were not setting one of my sound
> cards priorities correctly after the upgrade so I changed the config
> file and fixed that, but I don't think it should have changed at all.
>
>    The machine is still quite usable, but it doesn't feel as snappy as
> it did last week.
>
>    I made no changes in /etc/make.conf for the upgrade. Everything is
> pretty basic as far as I can tell:
>
> CFLAGS="-march=k8 -O2 -pipe"
> CHOST="x86_64-pc-linux-gnu"
> USE="dri radeon mmx mmxext sse sse2 3dnow 3dnowext gnome kde -esd
> -arts ladspa nptl nptlonly audiofile gimp gimpprint ppds usb alsa cdr
> dvd dvdr dvdread jack jack-tmpfs fluidsynth tcltk sndfile v4l v4l2
> mysql flac xscreensaver -samba i8x0 mythtv apache2 -lirc mjpeg xvid
> real cjk unicode vorbis ogg truetype java -eds"
> CXXFLAGS="${CFLAGS}"
> MAKEOPTS="-j2"
>
>    3GHz AMD64 with 1GB & NVidia chipset/SATA drives.
>
> Mark
>
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Duncan]

"Mark Knecht" <markknecht@gmail.com> posted
5bdc1c8b0609221235i2270bbenf016d5fa7a1998ec@mail.gmail.com, excerpted
below, on  Fri, 22 Sep 2006 12:35:47 -0700:

> It turns out that for me the problem was the ati-drivers package.
> Switching to the radeon driver today lowered the CPU usage back to the 9%
> range that I was used to:

Thanks!  Always nice to see freedomware win. =8^)

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Mark Knecht]

On 9/22/06, Duncan <1i5t5.duncan@cox.net> wrote:
> "Mark Knecht" <markknecht@gmail.com> posted
> 5bdc1c8b0609221235i2270bbenf016d5fa7a1998ec@mail.gmail.com, excerpted
> below, on  Fri, 22 Sep 2006 12:35:47 -0700:
>
> > It turns out that for me the problem was the ati-drivers package.
> > Switching to the radeon driver today lowered the CPU usage back to the 9%
> > range that I was used to:
>
> Thanks!  Always nice to see freedomware win. =8^)
>

I agree Duncan.

Now, the one issue left for complete world domination would be to
better understand how to get DRI working with this video adapter. Am I
correct that DRI==3D? Or does DRI go further than just basic 3D and
help other things like MythTV or something else I'm not thinking of at
all?

I do see these messages in xorg.0.log:

(**) RADEON(0): RADEONSaveMode returns 0x709390
(WW) RADEON(0): Enabling DRM support

        *** Direct rendering support is highly experimental for Radeon 9500
        *** and newer cards. The 3d mesa driver is not provided in this tree.
        *** A very experimental (and incomplete) version is available
from Mesa CVS.
        *** Additional information can be found on http://r300.sourceforge.net
        *** This message has been last modified on 2005-08-07.

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 6, (OK)

I do NOT do ANY Linux-based 3D stuff today. My workload is Mainly
music applications - Ardour, etc., which do not care about 3D, web
browsing, MythTV and Xine to watch movies.  Do I / should I care about
DRI?

I do occasionally play Windows games under Cedega. Would DRI ever help
that sort of application?

Anyway, things seem to be in pretty good shape. Maybe I should just
leave good enough alone. ;-)

Cheers,
Mark

P.S. - I'm still curious about trying your compiler flags but now
there is no pressing timeframe to do it in on this machine. - MWK
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Christoph Mende]

[-- Attachment #1: Type: text/plain, Size: 2459 bytes --]

DRI is hardware accelerated 3D rendering. You don't need it for music apps,
but you most probably need it for your Windows games, without direct
rendering you will use software rendering and get most likely get <5 fps in
OpenGL games. It may be nice to have direct rendering for xine too, since
xine can output its videos through OpenGL - don't know about MythTV though.

2006/9/23, Mark Knecht <markknecht@gmail.com>:
>
> On 9/22/06, Duncan <1i5t5.duncan@cox.net> wrote:
> > "Mark Knecht" <markknecht@gmail.com> posted
> > 5bdc1c8b0609221235i2270bbenf016d5fa7a1998ec@mail.gmail.com, excerpted
> > below, on  Fri, 22 Sep 2006 12:35:47 -0700:
> >
> > > It turns out that for me the problem was the ati-drivers package.
> > > Switching to the radeon driver today lowered the CPU usage back to the
> 9%
> > > range that I was used to:
> >
> > Thanks!  Always nice to see freedomware win. =8^)
> >
>
> I agree Duncan.
>
> Now, the one issue left for complete world domination would be to
> better understand how to get DRI working with this video adapter. Am I
> correct that DRI==3D? Or does DRI go further than just basic 3D and
> help other things like MythTV or something else I'm not thinking of at
> all?
>
> I do see these messages in xorg.0.log:
>
> (**) RADEON(0): RADEONSaveMode returns 0x709390
> (WW) RADEON(0): Enabling DRM support
>
>         *** Direct rendering support is highly experimental for Radeon
> 9500
>         *** and newer cards. The 3d mesa driver is not provided in this
> tree.
>         *** A very experimental (and incomplete) version is available
> from Mesa CVS.
>         *** Additional information can be found on
> http://r300.sourceforge.net
>         *** This message has been last modified on 2005-08-07.
>
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 6, (OK)
>
> I do NOT do ANY Linux-based 3D stuff today. My workload is Mainly
> music applications - Ardour, etc., which do not care about 3D, web
> browsing, MythTV and Xine to watch movies.  Do I / should I care about
> DRI?
>
> I do occasionally play Windows games under Cedega. Would DRI ever help
> that sort of application?
>
> Anyway, things seem to be in pretty good shape. Maybe I should just
> leave good enough alone. ;-)
>
> Cheers,
> Mark
>
> P.S. - I'm still curious about trying your compiler flags but now
> there is no pressing timeframe to do it in on this machine. - MWK
> --
> gentoo-amd64@gentoo.org mailing list
>
>

[-- Attachment #2: Type: text/html, Size: 3313 bytes --]

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Greg Bur]

On 9/22/06, Mark Knecht <markknecht@gmail.com> wrote:
> On 9/22/06, Duncan <1i5t5.duncan@cox.net> wrote:
> > "Mark Knecht" <markknecht@gmail.com> posted
> > 5bdc1c8b0609221235i2270bbenf016d5fa7a1998ec@mail.gmail.com, excerpted
> > below, on  Fri, 22 Sep 2006 12:35:47 -0700:

> P.S. - I'm still curious about trying your compiler flags but now
> there is no pressing timeframe to do it in on this machine. - MWK
> --

I put my workstation through its paces last weekend using Duncan's
flags and so far I've only run across one package that gave me
problems and that was Evolution.  It didn't like the
LDFLAGS="-Wl,-z,now"

I can't really say if I've noticed a huge difference in performance
because I use Windowmaker which is already pretty snappy but some of
my apps such as Firefox seem to be a few steps quicker but that might
all be in my head.  Altogether it took about 18 hours to recompile the
whole mess and nothing fell apart other than a slight issue with
Evolution.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Mark Knecht]

On 9/23/06, Greg Bur <greg.bur@gmail.com> wrote:
> On 9/22/06, Mark Knecht <markknecht@gmail.com> wrote:
> > On 9/22/06, Duncan <1i5t5.duncan@cox.net> wrote:
> > > "Mark Knecht" <markknecht@gmail.com> posted
> > > 5bdc1c8b0609221235i2270bbenf016d5fa7a1998ec@mail.gmail.com, excerpted
> > > below, on  Fri, 22 Sep 2006 12:35:47 -0700:
>
> > P.S. - I'm still curious about trying your compiler flags but now
> > there is no pressing timeframe to do it in on this machine. - MWK
> > --
>
> I put my workstation through its paces last weekend using Duncan's
> flags and so far I've only run across one package that gave me
> problems and that was Evolution.  It didn't like the
> LDFLAGS="-Wl,-z,now"
>
> I can't really say if I've noticed a huge difference in performance
> because I use Windowmaker which is already pretty snappy but some of
> my apps such as Firefox seem to be a few steps quicker but that might
> all be in my head.  Altogether it took about 18 hours to recompile the
> whole mess and nothing fell apart other than a slight issue with
> Evolution.

Cool. So you did essentially the

emerge -e system
emerge -e system
emerge -e world

steps that you did when upgrading gcc to get there?

Thanks,
Mark
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Greg Bur]

On 9/23/06, Mark Knecht <markknecht@gmail.com> wrote:
> Cool. So you did essentially the
>
> emerge -e system
> emerge -e system
> emerge -e world
>
> steps that you did when upgrading gcc to get there?
>
> Thanks,
> Mark

Yes, although I used emerge -eav system just so I had one more chance
to think before diving in for a swim.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Peter Humphrey]

On Saturday 23 September 2006 10:03, Mark Knecht wrote:

> So you did essentially the
>
> emerge -e system
> emerge -e system
> emerge -e world
>
> steps that you did when upgrading gcc to get there?

Er, the GCC upgrade guide [1] only mentions a single emerge -e system to go 
from 3.4.4 to 4.1.1, and that's what I'm doing just now. I hope I don't 
need the second step.

1.	http://www.gentoo.org/doc/en/gcc-upgrading.xml

-- 
Rgds
Peter
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Mark Knecht]

On 9/23/06, Peter Humphrey <prh@gotadsl.co.uk> wrote:
> On Saturday 23 September 2006 10:03, Mark Knecht wrote:
>
> > So you did essentially the
> >
> > emerge -e system
> > emerge -e system
> > emerge -e world
> >
> > steps that you did when upgrading gcc to get there?
>
> Er, the GCC upgrade guide [1] only mentions a single emerge -e system to go
> from 3.4.4 to 4.1.1, and that's what I'm doing just now. I hope I don't
> need the second step.
>
> 1.      http://www.gentoo.org/doc/en/gcc-upgrading.xml
>
> --
> Rgds
> Peter

Peter,
   I take it back. I was thinking of something else. Here is the set
of instructions I asked about on this list and was told were correct:

# emerge -uav gcc
# gcc-config i686-pc-linux-gnu-4.1.1
# source /etc/profile
# fix_libtool_files.sh 3.4.6
# emerge --oneshot -av libtool
# emerge -eav system
# emerge -eav world

I actually asked whether the emerge -eav world was necessary or
whether the system was usable after the emerge system was complete.
Boyd said that some folks had had problems so I did the emerge -eav
world and didn't use the system until it was complete.

NOTE: emerge --resume --skipfirst was my friend as a number of
packages didn't build the first time. I picked them up later.

Sorry for the confusion. I shouldn't work from memory! ;-)

Cheers,
Mark

Cheers,
Mark
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Duncan]

"Greg Bur" <greg.bur@gmail.com> posted
976cb44f0609230255s14bcc37dj36d53f90cbf765bc@mail.gmail.com, excerpted
below, on  Sat, 23 Sep 2006 05:55:59 -0400:

> I put my workstation through its paces last weekend using Duncan's flags
> and so far I've only run across one package that gave me problems and that
> was Evolution.  It didn't like the LDFLAGS="-Wl,-z,now"

That's reasonable, since I don't use Evolution.  (I use kmail for mail,
pan for news, and don't need Evolution's other features.)

You may wish to file a bug on that, altho I can't say you'll get a good
reception.  See my related bug on modular-X:

http://bugs.gentoo.org/show_bug.cgi?id=116698

If evolution has anything setuid, as was the case with xorg, it may help,
since portage's handling of that was one thing that eventually turned the
above bug toward satisfactory resolution.  I have no idea whether
evolution has anything setuid or not.

As for that ldflag, it's not major, more a personal preference.  In most
cases, what it does is force library resolution and function loading at
load time instead of waiting until the functionality is required in some
cases.  This results in a slightly longer load time, particularly shortly
after a reboot when nothing's yet in cache or loaded by other apps, and
slightly higher memory usage as well.  That's the negatives, along with
the occasional app that has problems with it. The positives are that if the
library isn't found, you know about it at load time instead of possibly
having the app crash later when it tries to load the functions, a bit more
responsiveness after load the first time those functions are used (when
the system would otherwise be loading the library and linking in the
functions on demand), and a bit better security.

All in all, as I said, it's a personal preference.  I don't specifically
recommend it as an optimization, and in fact, for those with less than a
gig of memory (as well as those who don't want the occasional hassle with
an app allergic to the setting), I'd tend to recommend NOT using it.

As for LDFLAGS in general, I've mentioned previously that I'm looking for
more documentation on them.  There's some others I've seen in bug
reports or mentioned in passing that look interesting, but I simply don't
/begin/ to know enough about them to even /consider/ using them at this
point. Until that changes, I leave well enough alone.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Sergio Polini]

Mark Knecht:
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is 6, (OK)

Great! ;-)

I've lost DRI when I've switched to modular X.
I see in Xorg.0.log:

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: open result is -1, (No such device)
drmOpenDevice: Open failed
...
(EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
[dri] Disabling DRI.

Please, could you tell me:
i) kernel version;
ii) the relevant settings in your kernel .config, for instance:
  CONFIG_MTRR
  CONFIG_AGP
  CONFIG_AGP_AMD64
  CONFIG_AGP_INTEL
  CONFIG_DRM
iii) mesa version;
iv) have you emerged x11-drm?
v) your "Device" section in xorg.conf;
vi) whatever info you think could help me ;-)

Thanks
Sergio


>
> I do NOT do ANY Linux-based 3D stuff today. My workload is Mainly
> music applications - Ardour, etc., which do not care about 3D, web
> browsing, MythTV and Xine to watch movies.  Do I / should I care
> about DRI?
>
> I do occasionally play Windows games under Cedega. Would DRI ever
> help that sort of application?
>
> Anyway, things seem to be in pretty good shape. Maybe I should just
> leave good enough alone. ;-)
>
> Cheers,
> Mark
>
> P.S. - I'm still curious about trying your compiler flags but now
> there is no pressing timeframe to do it in on this machine. - MWK
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Piotr Pruszczak]

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]


CONFIG_MTRR = YES
CONFIG_AGP = NO ?? I have PCI-E
CONFIG_AGP_AMD64 ??
CONFIG_AGP_INTEL NO ??
CONFIG_DRM NO


> iii) mesa version;

> iv) have you emerged x11-drm?
> v) your "Device" section in xorg.conf;
> vi) whatever info you think could help me ;-)
> 
> Thanks
> Sergio
> 
> 
>> I do NOT do ANY Linux-based 3D stuff today. My workload is Mainly
>> music applications - Ardour, etc., which do not care about 3D, web
>> browsing, MythTV and Xine to watch movies.  Do I / should I care
>> about DRI?
>>
>> I do occasionally play Windows games under Cedega. Would DRI ever
>> help that sort of application?
>>
>> Anyway, things seem to be in pretty good shape. Maybe I should just
>> leave good enough alone. ;-)
>>
>> Cheers,
>> Mark
>>
>> P.S. - I'm still curious about trying your compiler flags but now
>> there is no pressing timeframe to do it in on this machine. - MWK

[-- Attachment #2: DRM.txt --]
[-- Type: text/plain, Size: 959 bytes --]

 
gentoo / # module-rebuild list
** Packages which I will emerge are:
        =media-libs/mesa-6.5.1
        =sys-fs/submount-0.9-r2
        =x11-base/x11-drm-20060608
        =sys-apps/realtime-lsm-0.8.5-r1
        =sys-fs/fuse-2.6.0_rc1

then modprobe drm radeon (and for me realtime)

gentoo / # emerge --info
Portage 2.1.2_pre1 (default-linux/amd64/2006.1/desktop, gcc-4.1.1/amd64-vanilla, glibc-2.4-r3, 2.6.17-gentoo-r8 x86_64)
=================================================================
System uname: 2.6.17-gentoo-r8 x86_64 Dual Core AMD Opteron(tm) Processor 165
Gentoo Base System version 1.12.5
Last Sync: Tue, 19 Sep 2006 20:30:09 +0000

NO DRM in kernel (but I have PCI-E) Radeon X 550

gentoo / # glxgears
14300 frames in 5.0 seconds = 2859.914 FPS
14191 frames in 5.0 seconds = 2838.017 FPS

gentoo / # glxinfo
name of display: :0.0
display: :0  screen: 0
direct rendering: Yes
server glx vendor string: SGI
server glx version string: 1.2

[-- Attachment #3: make.conf --]
[-- Type: text/plain, Size: 2007 bytes --]

# These settings were set by the catalyst build script that automatically built this stage
# Please consult /etc/make.conf.example for a more detailed example
USE="-arts X multilib jpeg jpeg2k jp2 lzw lzw-tiff yv12 zlib radeon caps nptl nptlonly jack-tmpfs gtk gnome qt kde alsa jack dvd cdr jpeg ogg opengl readline sdl directfb tiff truetype unicode vorbis xine xml xml2 xvid ieee1394 gtk2 ffmpeg fftw divx4linux dvdr dvdread avi a52 aac 3dnow sse cdparanoia dv ffmpeg gphoto2 multilib perl python portaudio ruby sndfile usb vorbis win32codecs wxwindows dri hal"
CFLAGS="-march=k8 -O2 -pipe -frename-registers -fweb -freorder-blocks
-freorder-blocks-and-partition -combine -funit-at-a-time -ftree-pre
-fgcse-sm -fgcse-las -fgcse-after-reload -fmerge-all-constants "
CHOST="x86_64-pc-linux-gnu"
#CXXFLAGS="${CFLAGS}"
CXXFLAGS="-march=k8 -O2 -pipe -frename-registers -fweb -freorder-blocks
-funit-at-a-time -ftree-pre -fgcse-sm -fgcse-las -fgcse-after-reload
-fmerge-all-constants"
MAKEOPTS="-j3"

PORTDIR_OVERLAY=/usr/local/portage

FEATURES="buildpkg ccache"
CCACHE_SIZE="2G"
ACCEPT_KEYWORDS="~amd64"
INPUT_DEVICES="keyboard mouse"
VIDEO_CARDS="radeon vesa fbdev"
LANG="en_US"
LINGUAS="pl,en"
ALSA_CARDS="ice1712"




GENTOO_MIRRORS="rsync://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ http://gentoo.osuosl.org/  ftp://ftp.oss.cc.gatech.edu/pub/linux ftp://sunsite.icm.edu.pl/pub/Linux/sunsite.unc.edu/ ftp://gentoo.arcticnetwork.ca/pub/gentoo/ ftp://ftp.tu-dresden.de/pub/Linux/sunsite/ http://distro.ibiblio.org/pub/linux/distributions/gentoo/ ftp://ftp.dtiltas.lt/mirror/gentoo/ http://mirror.uni-c.dk/pub/gentoo/ http://mirror.usu.edu/mirrors/gentoo/  ftp://cs.ubishops.ca/pub/gentoo  http://gd.tuwien.ac.at/opsys/linux/gentoo/ http://ftp.linux.ee/pub/gentoo/distfiles/ http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://src.gentoo.pl http://gentoo.prz.rzeszow.pl http://gentoo.zie.pg.gda.pl ftp://cs.ubishops.ca/pub/gentoo  "

[-- Attachment #4: xorg.conf --]
[-- Type: text/plain, Size: 16006 bytes --]

# File generated by xorgconfig.

#
# Copyright 2004 The X.Org Foundation
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy of this software and associated documentation files (the "Software"),
# to deal in the Software without restriction, including without limitation
# the rights to use, copy, modify, merge, publish, distribute, sublicense,
# and/or sell copies of the Software, and to permit persons to whom the
# Software is furnished to do so, subject to the following conditions:
# 
# The above copyright notice and this permission notice shall be included in
# all copies or substantial portions of the Software.
# 
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
# IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
# FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.  IN NO EVENT SHALL
# The X.Org Foundation BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
# WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF
# OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
# SOFTWARE.
# 
# Except as contained in this notice, the name of The X.Org Foundation shall
# not be used in advertising or otherwise to promote the sale, use or other
# dealings in this Software without prior written authorization from
# The X.Org Foundation.
#

# **********************************************************************
# Refer to the xorg.conf(5x) man page for details about the format of 
# this file.
# **********************************************************************

# **********************************************************************
# Module section -- this  section  is used to specify
# which dynamically loadable modules to load.
# **********************************************************************
#
Section "Module"

# This loads the DBE extension module.

    Load        "dbe"  	# Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
    #  Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
    Load       "dri"
	Load  "dbe"
#	    Load  "extmod"
		Load  "fbdevhw"
    Load        "drm"   # libdrm.a 

EndSection

# **********************************************************************
# Files section.  This allows default font and rgb paths to be set
# **********************************************************************

Section "Files"

# The location of the RGB database.  Note, this is the name of the
# file minus the extension (like ".txt" or ".db").  There is normally
# no need to change the default.


# Multiple FontPath entries are allowed (which are concatenated together),
# as well as specifying multiple comma-separated entries in one FontPath
# command (or a combination of both methods)
# 
# 

    FontPath   "/usr/share/fonts/misc"
    FontPath   "/usr/share/fonts/75dpi"
    FontPath   "/usr/share/fonts/100dpi"
    FontPath   "/usr/share/fonts/TTF"
    FontPath   "/usr/share/fonts/Type1"
    FontPath   "/usr/lib/X11/fonts/local/"
#    FontPath   "/usr/lib/X11/fonts/misc/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/100dpi/:unscaled"
#    FontPath   "/usr/lib/X11/fonts/Speedo/"
#    FontPath   "/usr/lib/X11/fonts/Type1/"
#    FontPath   "/usr/lib/X11/fonts/TrueType/"
#    FontPath   "/usr/lib/X11/fonts/freefont/"
#    FontPath   "/usr/lib/X11/fonts/75dpi/"
#    FontPath   "/usr/lib/X11/fonts/100dpi/"

# The module search path.  The default path is shown here.


EndSection

# **********************************************************************
# Server flags section.
# **********************************************************************

Section "ServerFlags"

# Uncomment this to cause a core dump at the spot where a signal is 
# received.  This may leave the console in an unusable state, but may
# provide a better stack trace in the core dump to aid in debugging

#    Option "NoTrapSignals"

# Uncomment this to disable the <Ctrl><Alt><Fn> VT switch sequence
# (where n is 1 through 12).  This allows clients to receive these key
# events.

#    Option "DontVTSwitch"

# Uncomment this to disable the <Ctrl><Alt><BS> server abort sequence
# This allows clients to receive this key event.

#    Option "DontZap"

# Uncomment this to disable the <Ctrl><Alt><KP_+>/<KP_-> mode switching
# sequences.  This allows clients to receive these key events.

#    Option "Dont Zoom"

# Uncomment this to disable tuning with the xvidtune client. With
# it the client can still run and fetch card and monitor attributes,
# but it will not be allowed to change them. If it tries it will
# receive a protocol error.

#    Option "DisableVidModeExtension"

# Uncomment this to enable the use of a non-local xvidtune client. 

#    Option "AllowNonLocalXvidtune"

# Uncomment this to disable dynamically modifying the input device
# (mouse and keyboard) settings. 

#    Option "DisableModInDev"

# Uncomment this to enable the use of a non-local client to
# change the keyboard or mouse settings (currently only xset).

#    Option "AllowNonLocalModInDev"

EndSection

# **********************************************************************
# Input devices
# **********************************************************************

# **********************************************************************
# Core keyboard's InputDevice section
# **********************************************************************

Section "InputDevice"

    Identifier	"Keyboard1"
    Driver	"kbd"

# For most OSs the protocol can be omitted (it defaults to "Standard").
# When using XQUEUE (only for SVR3 and SVR4, but not Solaris),
# uncomment the following line.

#    Option     "Protocol"      "Xqueue"

    Option "AutoRepeat" "500 30"

# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
#    Option	"Xleds"      "1 2 3"

#    Option "LeftAlt"     "Meta"
#    Option "RightAlt"    "ModeShift"

# To customise the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults).  For example, for a non-U.S.
# keyboard, you will probably want to use:
#    Option "XkbModel"    "pc105"
# If you have a US Microsoft Natural keyboard, you can use:
#    Option "XkbModel"    "microsoft"
#
# Then to change the language, change the Layout setting.
# For example, a german layout can be obtained with:
#    Option "XkbLayout"   "de"
# or:
#    Option "XkbLayout"   "de"
#    Option "XkbVariant"  "nodeadkeys"
#
# If you'd like to switch the positions of your capslock and
# control keys, use:
#    Option "XkbOptions"  "ctrl:swapcaps"

# These are the default XKB settings for Xorg
#    Option "XkbRules"    "xorg"
#    Option "XkbModel"    "pc105"
#    Option "XkbLayout"   "us"
#    Option "XkbVariant"  ""
#    Option "XkbOptions"  ""

#    Option "XkbDisable"

    Option "XkbRules"	"xorg"
    Option "XkbModel"	"pc105"
    Option "XkbLayout"	"pl"

EndSection


# **********************************************************************
# Core Pointer's InputDevice section
# **********************************************************************

Section "InputDevice"

# Identifier and driver

    Identifier	"Mouse1"
    Driver	"mouse"
    Option "Protocol"    "Auto"	# Auto detect
    Option "Device"      "/dev/input/mice"

# When using XQUEUE, comment out the above two lines, and uncomment
# the following line.

#    Option "Protocol"	"Xqueue"

# Mouse-speed setting for PS/2 mouse.

#    Option "Resolution"	"256"

# Baudrate and SampleRate are only for some Logitech mice. In
# almost every case these lines should be omitted.

#    Option "BaudRate"	"9600"
#    Option "SampleRate"	"150"

# Mouse wheel mapping.  Default is to map vertical wheel to buttons 4 & 5,
# horizontal wheel to buttons 6 & 7.   Change if your mouse has more than
# 3 buttons and you need to map the wheel to different button ids to avoid
# conflicts.

    Option "ZAxisMapping"   "4 5 6 7"

# Emulate3Buttons is an option for 2-button mice
# Emulate3Timeout is the timeout in milliseconds (default is 50ms)

    Option "Emulate3Buttons"
#    Option "Emulate3Timeout"    "50"

# ChordMiddle is an option for some 3-button Logitech mice

#    Option "ChordMiddle"

EndSection


# **********************************************************************
# Other input device sections 
# this is optional and is required only if you
# are using extended input devices.  This is for example only.  Refer
# to the xorg.conf man page for a description of the options.
# **********************************************************************
#
# Section "InputDevice" 
#    Identifier  "Mouse2"
#    Driver      "mouse"
#    Option      "Protocol"      "MouseMan"
#    Option      "Device"        "/dev/mouse2"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball"
#    Driver     "magellan"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "spaceball2"
#    Driver     "spaceorb"
#    Option     "Device"        "/dev/cua0"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen0"
#    Driver     "microtouch"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "1412"
#    Option     "MaxX"          "15184"
#    Option     "MinY"          "15372"
#    Option     "MaxY"          "1230"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection
#
# Section "InputDevice"
#    Identifier "touchscreen1"
#    Driver     "elo2300"
#    Option     "Device"        "/dev/ttyS0"
#    Option     "MinX"          "231"
#    Option     "MaxX"          "3868"
#    Option     "MinY"          "3858"
#    Option     "MaxY"          "272"
#    Option     "ScreenNumber"  "0"
#    Option     "ReportingMode" "Scaled"
#    Option     "ButtonThreshold"       "17"
#    Option     "ButtonNumber"  "1"
#    Option     "SendCoreEvents"
# EndSection

# **********************************************************************
# Monitor section
# **********************************************************************

# Any number of monitor sections may be present

Section "Monitor"

    Identifier  "fe770"

# HorizSync is in kHz unless units are specified.
# HorizSync may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    HorizSync   31.5 - 64.3

#    HorizSync	30-64         # multisync
#    HorizSync	31.5, 35.2    # multiple fixed sync frequencies
#    HorizSync	15-25, 30-50  # multiple ranges of sync frequencies

# VertRefresh is in Hz unless units are specified.
# VertRefresh may be a comma separated list of discrete values, or a
# comma separated list of ranges of values.
# NOTE: THE VALUES HERE ARE EXAMPLES ONLY.  REFER TO YOUR MONITOR'S
# USER MANUAL FOR THE CORRECT NUMBERS.

    VertRefresh 50-90

EndSection


# **********************************************************************
# Graphics device section
# **********************************************************************

# Any number of graphics device sections may be present

# Standard VGA Device:

Section "Device"
    Identifier	"rv370"
    VendorName	"ATI"
    BoardName	"RV370"

# The chipset line is optional in most cases.  It can be used to override
# the driver's chipset detection, and should not normally be specified.

#    Chipset	"radeon"

# The Driver line must be present.  When using run-time loadable driver
# modules, this line instructs the server to load the specified driver
# module.  Even when not using loadable driver modules, this line
# indicates which driver should interpret the information in this section.

    Driver     "radeon"
    
#    Option "AGPMode" "1"              # 1-8 Does not affect PCIE models.
    Option "AGPFastWrite" "1"         # 1/0 Does not affect PCIE models.
  #  Option "AGPFastwrite" "1"
#    Option "BusType" "PCIE"

Option          "AGPMode" "4" 
    Option "AccelMethod" 	"XAA"
          Option          "RenderAccel" "on" 
	            # This two lines are needed to prevent fonts from being scrambled 
		              Option "XaaNoScanlineImageWriteRect" 
			                Option "XaaNoScanlineCPUToScreenColorExpandFill" 
					          # Misc 
     
    Option "EnablePageFlip" "1"       # 1/0 Increases 3D performance substantially 
                                         # seemingly in XAA mode only
					 
     Option "ColorTiling" "1"          # 1/0 Increases 3D performance substantially 
                                         # affected stability only positively on my system
# The BusID line is used to specify which of possibly multiple devices
# this section is intended for.  When this line isn't present, a device
# section can only match up with the primary video device.  For PCI
# devices a line like the following could be used.  This line should not
# normally be included unless there is more than one video device
# intalled.

#    BusID      "PCI:0:10:0"

#    VideoRam	256

#    Clocks	25.2 28.3

EndSection

# Device configured by xorgconfig:

Section "Device"
    Identifier  "rv370"
    Driver      "r300"
    VideoRam    131072
    # Insert Clocks lines here if appropriate
EndSection


# **********************************************************************
# Screen sections
# **********************************************************************

# Any number of screen sections may be present.  Each describes
# the configuration of a single screen.  A single specific screen section
# may be specified from the X server command line with the "-screen"
# option.
Section "Screen"
    Identifier  "Screen 1"
    Device      "rv370"
    Monitor     "fe770"
    DefaultDepth 24

    Subsection "Display"
        Depth       8
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       16
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
    Subsection "Display"
        Depth       24
        Modes       "1280x1024" "1024x768" "800x600" "640x480"
        ViewPort    0 0
    EndSubsection
EndSection

# **********************************************************************
# ServerLayout sections.
# **********************************************************************

# Any number of ServerLayout sections may be present.  Each describes
# the way multiple screens are organised.  A specific ServerLayout
# section may be specified from the X server command line with the
# "-layout" option.  In the absence of this, the first section is used.
# When now ServerLayout section is present, the first Screen section
# is used alone.

Section "ServerLayout"

# The Identifier line must be present
    Identifier  "Simple Layout"

# Each Screen line specifies a Screen section name, and optionally
# the relative position of other screens.  The four names after
# primary screen name are the screens to the top, bottom, left and right
# of the primary screen.  In this example, screen 2 is located to the
# right of screen 1.

    Screen "Screen 1"

# Each InputDevice line specifies an InputDevice section name and
# optionally some options to specify the way the device is to be
# used.  Those options include "CorePointer", "CoreKeyboard" and
# "SendCoreEvents".

    InputDevice "Mouse1" "CorePointer"
    InputDevice "Keyboard1" "CoreKeyboard"

EndSection

 Section "DRI"
    Group	 "video"
    Mode	 0666
 EndSection

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Mark Knecht]

On 9/25/06, Sergio Polini <sp_rm_it@yahoo.it> wrote:
> Mark Knecht:
> > drmOpenDevice: node name is /dev/dri/card0
> > drmOpenDevice: open result is 6, (OK)
>
> Great! ;-)
>
> I've lost DRI when I've switched to modular X.
> I see in Xorg.0.log:
>
> drmOpenDevice: node name is /dev/dri/card0
> drmOpenDevice: open result is -1, (No such device)
> drmOpenDevice: open result is -1, (No such device)
> drmOpenDevice: Open failed
> ...
> (EE) RADEON(0): [dri] RADEONDRIGetVersion failed to open the DRM
> [dri] Disabling DRI.
>
> Please, could you tell me:
> i) kernel version;
> ii) the relevant settings in your kernel .config, for instance:
>   CONFIG_MTRR
>   CONFIG_AGP
>   CONFIG_AGP_AMD64
>   CONFIG_AGP_INTEL
>   CONFIG_DRM
> iii) mesa version;
> iv) have you emerged x11-drm?
> v) your "Device" section in xorg.conf;
> vi) whatever info you think could help me ;-)
>
> Thanks
> Sergio
>

Hi Sergio,
   Hope this helps. Let me knowif you need or want anything else.

Cheers,
Mark

   The kernel is from the proaudio overlay:

lightning src # uname -a
Linux lightning 2.6.17-rt5 #2 PREEMPT Mon Sep 11 10:54:03 PDT 2006
x86_64 AMD Athlon(tm) 64 Processor 3000+ GNU/Linux
lightning src #


lightning src # cat linux/.config | grep CONFIG_MTRR
CONFIG_MTRR=y
lightning src #

CONFIG_AGP_AMD64=y
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_VIA is not set
lightning src #

lightning src # cat linux/.config | grep CONFIG_AMD64
lightning src #

CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
# CONFIG_DRM_SAVAGE is not set
lightning src #

lightning src # eix drm
* games-arcade/ddrmat
     Available versions:  !0.12
     Installed:           none
     Homepage:            http://www.icculus.org/pyddr/
     Description:         Kernel module for parallel port Playstation
joystick (i.e. DDR mats) adapters

* x11-base/x11-drm
     Available versions:  !4.3.0-r7:2.6.14-hardened-r8
~20050502:2.6.14-hardened-r8 ~20050807 ~20051028 ~20051223 20060608
     Installed:           none
     Homepage:            http://dri.sf.net
     Description:         DRM Kernel Modules for X11

* x11-libs/libdrm
     Available versions:  2.0.1 ~2.0.2
     Installed:           2.0.1
     Homepage:            http://dri.freedesktop.org/
     Description:         X.Org libdrm library

Found 3 matches.
lightning src #


lightning src # eix -I mesa
* media-libs/mesa
     Available versions:  6.4.2-r2 ~6.5-r3 ~6.5-r4 ~6.5.1 ~6.5.1-r1
     Installed:           6.4.2-r2
     Homepage:            http://mesa3d.sourceforge.net/
     Description:         OpenGL-like graphic library for Linux

* x11-apps/mesa-progs
     Available versions:  6.4.2 ~6.5 ~6.5.1
     Installed:           6.4.2
     Homepage:            http://mesa3d.sourceforge.net/
     Description:         Mesa's OpenGL utility and demo programs
(like glxgears)

Found 2 matches.
lightning src #


Section "Module"

# This loads the DBE extension module.

    Load        "dbe"   # Double buffer extension

# This loads the miscellaneous extensions module, and disables
# initialisation of the XFree86-DGA extension within that module.
    SubSection  "extmod"
      Option    "omit xfree86-dga"   # don't initialise the DGA extension
    EndSubSection

# This loads the font modules
#    Load        "type1"
#    Load        "speedo"
    Load        "freetype"
#    Load        "xtt"

# This loads the GLX module
    Load       "glx"
# This loads the DRI module
    Load       "dri"

EndSection


# Device configured by xorgconfig:

Section "Device"
    Identifier  "** ATI Radeon (generic)               [radeon]"
    Driver      "radeon"
    #VideoRam    65536
    # Insert Clocks lines here if appropriate
EndSection


Section "DRI"
   Mode 0666
EndSection



lightning src # glxgears
Unknown device ID 5B60, please report. Assuming plain R300.
*********************************WARN_ONCE*********************************
File r300_state.c function r300Enable line 456
TODO - double side stencil !
***************************************************************************
No ctx->FragmentProgram._Current!!
*********************************WARN_ONCE*********************************
File r300_render.c function r300_get_num_verts line 188
user error: Need more than 2 vertices to draw primitive QS !
***************************************************************************
6422 frames in 5.0 seconds = 1284.247 FPS
6420 frames in 5.0 seconds = 1283.953 FPS
6421 frames in 5.0 seconds = 1284.129 FPS
6415 frames in 5.0 seconds = 1282.975 FPS

lightning src #
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Sergio Polini]

Piotr Pruszczak:
> NO DRM in kernel (but I have PCI-E) Radeon X 550
 
Mark Knecht:
> Hi Sergio,
>  Hope this helps. Let me knowif you need or want anything else.
> ...
> Unknown device ID 5B60, please report. Assuming plain R300.300.

I thank you for your help, but I've found another solution ;-)
I have presented my daughter with my HP dv5000z, and so I've got rid 
of that irksome and ill-supported ATI Radeon XPRESS 200M.
I'm going to purchase a new HP dv2000 (Turion X2, Geforce 6150).
;-)

Thanks a lot!
Sergio
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: SOLVED: gcc 4.1 upgrade - bad desktop interactivity anyone?

[Peter Davoust]

Great solution. I wish my parents did that more often. I also have an
ati radeon xpress 200m. This is what I did to get it working: 

emerge ati-drivers
aticonfig --initial /etc/X11/xorg.conf

restart xorg. If that doesn't work, then I had to 
echo "x11-drivers/ati-drivers ~amd64" >> /etc/portage/package.keywords
emerge ati-drivers

You have to have DRM compiled as a module in the kernel. Sorry, I didn't
read the rest of the post, so I don't know what you tried, but I hope
that helps. 

-Peter
On Sun, 2006-10-08 at 20:44 +0200, Sergio Polini wrote:
> Piotr Pruszczak:
> > NO DRM in kernel (but I have PCI-E) Radeon X 550
>  
> Mark Knecht:
> > Hi Sergio,
> >  Hope this helps. Let me knowif you need or want anything else.
> > ...
> > Unknown device ID 5B60, please report. Assuming plain R300.300.
> 
> I thank you for your help, but I've found another solution ;-)
> I have presented my daughter with my HP dv5000z, and so I've got rid 
> of that irksome and ill-supported ATI Radeon XPRESS 200M.
> I'm going to purchase a new HP dv2000 (Turion X2, Geforce 6150).
> ;-)
> 
> Thanks a lot!
> Sergio

-- 
gentoo-amd64@gentoo.org mailing list